G05-LT: No
Rationale
No for the selected private-ipn singleton deployment. RFC 9758 reserves node numbers 1 through 0x3FFF for private use: at most 16383 distinct bundle nodes in one such domain. Private source/destination EIDs cannot cross administrative domains. Reusing that range in disconnected domains does not supply the connected ten-billion-device witness. Additional service numbers distinguish services on a node, not new independently identified nodes.
Assessment method
Documentary necessary-condition bound; no execution
Source context
RFC 9758 sections 3.4.3, 3.5, 5.5, 5.7 and 9.2
Outstanding qualification
This is a selected-profile namespace obstruction, not a claim that BPv7, CGR/SABR or LTP is intrinsically unable to scale globally. Global allocator identifiers, another endpoint naming scheme or a translating gateway composition require an explicit global profile and renewed analysis of routing, discovery, security bindings and resources. They are not silently added here. No performance experiment, hardware failure or global impossibility theorem is asserted. The private deployment remains useful and its other capabilities remain credited. The BP column also selects dtn collective names; its separate G05 question is not decided by this singleton-profile bound.
Public sources
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round409.html
- round409-bound.json