G03-IP: Yes
Rationale
IP forwarding can use prefix routes and a default next hop instead of a complete catalog of every final host address. Neighbor resolution concerns the attached next hop, and the selected profile already supplies numeric destinations. Thus neither discovering the local forwarding adjacency nor forwarding a remote packet requires each transit node to replicate a global hosts catalog.
Assessment method
Primary documentary assessment under revised criterion; no runtime experiment
Source context
Pinned PRP architecture worktree and IP RFCs
Outstanding qualification
This does not supply discovery of unknown application names. Global BGP reachability tables and provider dependency remain separate G01/G05 questions; a prefix routing table is not a complete per-host identity catalog. The result credits the revised per-node requirement, not zero state, bounded cache-miss cost or global capacity.
Public sources
- https://www.rfc-editor.org/rfc/rfc1812.html#section-5.2.4.3
- https://www.rfc-editor.org/rfc/rfc1812.html#section-3.3.2
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round488.html
- round488-sources.json