Delay-Tolerant Networking Management Architecture (DTNMA)
RFC 9675
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['DTN', 'Network Management']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "E. Annis": changed name from "Emery Annis" to "E. Annis", changed affiliation from "Johns Hopkins Applied Physics Laboratory" to "JHU/APL" |
|
2026-05-20
|
(System) | Changed author "S. Heiner": changed name from "Sarah Heiner" to "S. Heiner", changed affiliation from "Johns Hopkins Applied Physics Laboratory" to "JHU/APL" |
|
2026-05-20
|
(System) | Changed author "E. Birrane, III": changed name from "Edward Birrane" to "E. Birrane, III", changed affiliation from "Johns Hopkins Applied Physics Laboratory" to "JHU/APL" |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2024-11-07
|
(System) | Received changes through RFC Editor sync (created document RFC 9675, created became rfc relationship between draft-ietf-dtn-dtnma and RFC 9675, set title to 'Delay-Tolerant … Received changes through RFC Editor sync (created document RFC 9675, created became rfc relationship between draft-ietf-dtn-dtnma and RFC 9675, set title to 'Delay-Tolerant Networking Management Architecture (DTNMA)', set abstract to '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.', set pages to 49, set standardization level to Informational, added RFC published event at 2024-11-07) |
|
2024-11-07
|
(System) | RFC published |