RFC 9675: Delay-Tolerant Networking Management Architecture (DTNMA)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9675
- Published
- November 2024
- Authors
- E. Birrane, III; S. Heiner; E. Annis
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 49
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9713Bundle Protocol Version 7 Administrative Record Types RegistryCurrent
January 2025
- RFC 9758Updates to the 'ipn' URI SchemeCurrent
May 2025
- RFC 7388Definition of Managed Objects for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)Current
October 2014
- RFC 9891Automated Certificate Management Environment (ACME) Delay-Tolerant Networking (DTN) Node ID Validation ExtensionCurrent
November 2025
- RFC 9312Manageability of the QUIC Transport ProtocolCurrent
September 2022
- RFC 9166A YANG Data Model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) SnoopingCurrent
February 2022
- RFC 9128YANG Data Model for Protocol Independent Multicast (PIM)Current
October 2022
- RFC 8695A YANG Data Model for the Routing Information Protocol (RIP)Current
February 2020
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?