F39-LI: Yes
Rationale
The selected UDP application addresses an EID and port. LISP keeps EIDs separate from underlay RLOCs; the application does not select the remote tunnel endpoint. A locally assigned EID follows ordinary local delivery, while remote delivery uses the configured EID routing and EID-to-RLOC mapping beneath the same UDP interface.
Assessment method
Primary specifications, pinned source and explicit local-delivery composition; no runtime test
Source context
NET/ROM local dispatch, LISP EID separation and Tailscale Linux address assignment
Outstanding qualification
Architectural composition of RFC 9300 with ordinary host local delivery. EIDs remain provisioned host addresses and may have site-local subnet structure; they are not process keys or a promise of transparent process migration. The service binds its EID or wildcard and policy permits access. No executable LISP integration or local security-equivalence test is claimed.
Public sources
- https://www.rfc-editor.org/rfc/rfc9300.html#section-3
- https://www.rfc-editor.org/rfc/rfc9300.html#section-4
- https://man7.org/linux/man-pages/man8/ip-route.8.html
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round693.html