DTN (Delay/Disruption-Tolerant Networking), standardized primarily via the IETF’s DTN Working Group and CCSDS, uses the Bundle Protocol (BPv7 in RFC 9171 and related docs) with Endpoint Identifiers (EIDs) as URIs (e.g., dtn://example.com/app or the ipn: scheme for interplanetary use). These support late binding — name-to-address resolution happens close to the destination, not at the source. This is crucial because classic DNS lookups assume low latency and continuous connectivity, which DTN explicitly rejects.
datatracker.ietf.orgHowever, real-world DTN deployments (space, remote terrestrial, hybrid networks) often connect to or gateway through the Internet. Here’s where DNS shines and is already being extended:
- Convergence Layer discovery: Drafts propose new DNS Resource Records (RRs) so DTN nodes can discover how to reach each other over IP-based links (e.g., which CLA — Convergence Layer Adapter — to use). datatracker.ietf.org
- Interplanetary / hybrid DNS models: Proposals like “An Interplanetary DNS Model” suggest new TLDs or special zones (e.g., region-specific roots or .ipn.arpa-style delegation) with gateways. Remote “worlds” (Mars, lunar, etc.) get their own logical TLDs that resolve to gateways, avoiding the need to synchronize full DNS data across light-minutes. datatracker.ietf.org
- Peering and management: Work on DTN Peering Protocol and management architecture references DNS for endpoint discovery and identity. datatracker.ietf.org
Bottom line: DNS’s global stability, caching, hierarchy, and existing infrastructure make it the smart “bridge” layer. Pure DTN will keep using its own EID schemes + late binding for disconnected operation, while DNS (possibly extended) handles the connected/hybrid edges and service discovery. It’s complementary evolution, not replacement. The IETF drafts from 2024–2025 show this direction is already active.