C06-LI: No
Rationale
RFC 9300 encapsulation places the EID-bearing inner IP packet after the outer RLOC, UDP and LISP headers. The selected composition does not encrypt the inner packet, so a transit packet observer can read both final EIDs rather than seeing only the tunnel-router locators.
Assessment method
Header/encapsulation assessment under revised C06; no traffic capture
Source context
Primary RFCs and pinned protocol/implementation headers
Outstanding qualification
The EID/RLOC separation is retained as a routing capability. It is not confidentiality of the EID pair. No LISP-SEC, IPsec or endpoint privacy layer is selected; the finding concerns visible network addresses, not real-world identities.
Public sources
- https://www.rfc-editor.org/rfc/rfc9300.html#section-5.1
- https://www.rfc-editor.org/rfc/rfc9300.html#section-5.3
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round490.html
- round490-sources.json