Back to matrix

G03-CG: Yes

Rationale

For a supplied destination EID, the selected aggregate-gateway configuration can forward by destination ranges rather than enumerating every final endpoint. RFC 9171 section 5.4 permits forwarding through another node; SABR Annex C.1.2 documents range-to-gateway rules and route calculation to the selected gateway. Local contact/neighbor information and aggregate exits therefore suffice at a forwarding node without a complete global identity catalog.

Assessment method

Primary documentary reassessment of configured aggregate gateway witness; no execution

Source context

RFC 9171 section 5.4 and SABR Annex C.1.2

Outstanding qualification

This is a configured known-EID capability, not arbitrary-name discovery or an automatic directory. SABR Annex C is informative implementation guidance, not a mandatory feature of every BP implementation. Gateways still need suitable onward routes; contact plans, boundary configuration, endpoint-key provisioning and resource costs remain. No G01/G05 verdict or execution result follows. This reuses the documented aggregate-gateway option already considered for the selected SABR composition; complete BPv7/SABR metadata and convergence-layer integration remain unqualified. The TCPCL/IP underlay retains its routing dependencies.

Public sources

• https://ccsds.org/Pubs/734x3b1.pdf
• https://www.rfc-editor.org/rfc/rfc9171.html#section-5.4

Editorial evidence references

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

• round497.html
• round497-sources.json