Back to matrix

F26-LI: No

Rationale

The selected LISP data plane forwards through EID-to-RLOC mappings. Registration credentials authorize mapping updates, not individual data forwarding. No sender or adjacency admission credential is required before onward data transmission.

Assessment method

Primary normative source and selected adjacency-policy analysis; no execution

Source context

Primary RFC and selected profile; forwarding versus control/endpoint boundary

Outstanding qualification

RFC 9300 discusses optional source EID/RLOC consistency checks and anti-spoofing mitigations. Mapping consistency does not establish permission to send traffic. No applies to the selected base composition without added security gateways or filters.

Public sources

• https://www.rfc-editor.org/rfc/rfc9300.html#section-16
• https://www.rfc-editor.org/rfc/rfc9300.html#section-16
• https://www.rfc-editor.org/rfc/rfc6740.html

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.

• round450.html
• round450-sources.json