G03-HP: Yes
Rationale
The selected HIP composition starts with a known peer HIT and numeric locator. Hosts maintain bindings and security associations for communicating peers, while the IP underlay forwards using prefixes, default routes and local neighbors. No complete catalog of all Host Identities is required at every transit node.
Assessment method
Primary documentary reassessment; no runtime test
Source context
Selected routing and HIP specifications
Outstanding qualification
Known peer references are a declared composition prerequisite, as for the numeric-IP baseline. This does not provide semantic discovery of unknown peers, remove global IP routing dependencies or prove global scale. DNS and rendezvous services are not selected.
Public sources
- https://www.rfc-editor.org/rfc/rfc8046.html#section-3.1
- https://www.rfc-editor.org/rfc/rfc7402.html#section-3.2
- https://www.rfc-editor.org/rfc/rfc1812.html#section-5.2.4.3
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round493.html
- round493-sources.json