Delay-Tolerant Networking Management Architecture
RFC 9675, “Delay-Tolerant Networking Management Architecture”, is an Informational document published in November 2024 by E. Birrane, III, S. Heiner, E. Annis. The canonical text is published by the RFC Editor.
Abstract
The Delay-Tolerant Networking (DTN) architecture describes a type of challenged network in which communications may be significantly affected by long signal propagation delays, frequent link disruptions, or both. The unique characteristics of this environment require a unique approach to network management that supports asynchronous transport, autonomous local control, and a small footprint (in both resources and dependencies) so as to deploy on constrained devices.
This document describes a DTN Management Architecture (DTNMA) suitable for managing devices in any challenged environment but, in particular, those communicating using the DTN Bundle Protocol (BP). Operating over BP requires an architecture that neither presumes synchronized transport behavior nor relies on query-response mechanisms. Implementations compliant with this DTNMA should expect to successfully operate in extremely challenging conditions, such as over unidirectional links and other places where BP is the preferred transport.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 9675 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 9674 Same-Origin Policy for the RPKI Repository Delta Protocol
- RFC 9673 IPv6 Hop-by-Hop Options Processing Procedures
- RFC 9677 Content Delivery Network Interconnection Metadata for Delegated Credentials
- RFC 9672 Transferring Opportunistic Wireless Encryption to the IEEE 802.11 Working Group
- RFC 9671 Sieve Email Filtering: Extension for Processing Calendar Attachments
- RFC 9679 CBOR Object Signing and Encryption Key Thumbprint
- RFC 9670 JSON Meta Application Protocol Sharing
- RFC 9680 Antitrust Guidelines for IETF Participants