Delay/Disruption Tolerant Networking (dtn) Internet Drafts

      
 DTN Management Architecture
 
 draft-ietf-dtn-dtnma-13.txt
 Date: 18/03/2024
 Authors: Edward Birrane, Sarah Heiner, Emery Annis
 Working Group: Delay/Disruption Tolerant Networking (dtn)
 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 uni-directional links and other places where BP is the preferred transport.
 Update to the ipn URI scheme
 
 draft-ietf-dtn-ipn-update-10.txt
 Date: 21/02/2024
 Authors: Rick Taylor, Edward Birrane
 Working Group: Delay/Disruption Tolerant Networking (dtn)
 This document updates both the specification of the ipn URI scheme previously defined in RFC 7116 and the rules for encoding of these URIs when used as an Endpoint Identifier (EID) in Bundle Protocol Version 7 (BPv7) as defined in RFC 9171. These updates clarify the structure and behavior of the ipn URI scheme, define encodings of ipn scheme URIs, and establish the registries necessary to manage this scheme.
 DTN Bundle Protocol Security (BPSec) COSE Context
 
 draft-ietf-dtn-bpsec-cose-03.txt
 Date: 03/01/2024
 Authors: Brian Sipos
 Working Group: Delay/Disruption Tolerant Networking (dtn)
 This document defines a security context suitable for using CBOR Object Signing and Encryption (COSE) algorithms within Bundle Protocol Security (BPSec) integrity and confidentiality blocks. A profile for COSE, focused on asymmetric-keyed algorithms, and for PKIX certificates are also defined for BPSec interoperation.
 DTNMA Application Resource Identifier (ARI)
 
 draft-ietf-dtn-ari-00.txt
 Date: 22/02/2024
 Authors: Edward Birrane, Emery Annis, Brian Sipos
 Working Group: Delay/Disruption Tolerant Networking (dtn)
 This document defines the structure, format, and features of the naming scheme for the objects defined in the Delay-Tolerant Networking Management Architecture (DTNMA) Application Management Model (AMM), in support of challenged network management solutions described in the DTNMA document. This document defines the DTNMA Application Resource Identifier (ARI), using a text-form based on the common Uniform Resource Identifier (URI) and a binary-form based on Concise Binary Object Representation (CBOR). These meet the needs for a concise, typed, parameterized, and hierarchically organized set of managed data elements.
 DTNMA Application Management Model (AMM) and Data Models
 
 draft-ietf-dtn-adm-00.txt
 Date: 22/02/2024
 Authors: Edward Birrane, Brian Sipos, Justin Ethier
 Working Group: Delay/Disruption Tolerant Networking (dtn)
 This document defines a data model that captures the information necessary to asynchronously manage applications within the Delay- Tolerant Networking Management Architecture (DTNMA). This model provides a set of common type definitions, data structures, and a template for publishing standardized representations of model elements.

data-group-menu-data-url="/group/groupmenu.json">

Delay/Disruption Tolerant Networking (dtn)

WG Name Delay/Disruption Tolerant Networking
Acronym dtn
Area Internet Area (int)
State Active
Charter charter-ietf-dtn-02 Approved
Status update Show Changed 2016-10-31
Document dependencies
Additional resources Issue tracker, Wiki, Zulip Stream
Personnel Chairs Edward J. Birrane, Rick Taylor
Area Director Erik Kline
Secretary Adam Wiethuechter
Mailing list Address dtn@ietf.org
To subscribe https://www.ietf.org/mailman/listinfo/dtn
Archive https://mailarchive.ietf.org/arch/browse/dtn/
Chat Room address https://zulip.ietf.org/#narrow/stream/dtn

Charter for Working Group

The Delay/Disruption Tolerant Networking (DTN) Working Group specifies
mechanisms for data communications in the presence of long delays and/or
intermittent connectivity. The Working Group has published the Bundle Protocol
v7 (BPv7), corresponding Bundle Protocol Security protocol (BPSec) and an
interoperable Security Context, and the TCP Convergence Layer specifications
as standards track RFCs. Multiple independent implementations
exist for these technologies in both space and terrestrial
environments, and the technology is now used in production by governments and
commercial organizations world-wide.

This Working Group now focuses on the further work relevant to the area of
Delay/Disruption Tolerant Networking, dividing work items into 3
broad categories:

  • An architecture for Naming, Addressing and Forwarding

    The Bundle Protocol v7 defines an encoding of Names for use in DTN, but the
    detailed semantics have not been specified. The Working Group will define
    a common architecture for the delay/disruption tolerant assignment of
    names, and the late-binding of such names during bundle forwarding to
    end-points within a DTN. This architecture will define a model
    for the forwarding process of a Bundle Process Agent, providing an
    informational reference point for further specifications.

    The Working Group charter intentionally excludes topics related to Routing
    in DTNs. This does not preclude discussion of the subject, in coordination
    with the Routing Area, but no Working Group documents will be adopted under
    this charter.

  • The definition of an architecture and protocols in the areas of Operations,
    Administration, and Management (OAM), and Key Management

    Current DTN deployments rely on the use of pre-placed keys and
    configuration or bespoke tooling, and there is a growing demand for
    standards to improve the automation and reliability of DTN management.
    Existing IETF protocols for OAM and Key Management generally rely on a
    bi-directional end-to-end path between devices, and in Delay/Disruption
    Tolerant Networks (DTNs) such paths rarely exist. To enable OAM and Key
    Management in such cases, there may be a need to standardize an
    architecture supporting alternative methods and their supporting protocols
    and data models. The Working Group will liaise with relevant experts in
    the OPS Area to discover if there are existing standards that meet, or may
    be extended to meet, the DTN use-cases before standardizing new protocols.
    There is also believed to be cross-over between the use-cases for OAM and
    Key Management in DTNs and the use-cases in Mobile Ad-hoc Networks
    (MANETs); to this end the Working Group will coordinate with the MANET
    Working Group to explore potential synergies and avoid duplication of
    effort.

  • Extensions to and best practices for existing protocols

    Extensions to the Bundle Protocol to enable reliability signalling,
    tunnelling and Quality of Service indication are needed for the operational
    deployment of Delay/Disruption Tolerant Networks, and these capabilities
    will be standardized by the Working Group.

    Additional extensions to the Bundle Protocol, additional Security Context
    definitions for BPSec, and new Convergence Layer adapters will be
    considered on a case-by-case basis by the working group.

    The Working Group will also document best practices learned from existing
    deployments.

The Working Group will coordinate with other IETF Working Groups, especially in the Security, Routing, Operation and Management Areas, to ensure the quality of
peer review, the avoidance of duplication of effort, and alignment with
specifications produced in other Working Groups.

Milestones

Date Milestone Associated documents
Jul 2024 Key Management Protocol
Mar 2024 Delay-Tolerant Management Protocols draft-birrane-dtn-amp
Nov 2023 Neighbor/Peer Discovery Protocol Specification
Jul 2023 QoS/Flow Extension Block draft-burleigh-dtn-ecos
Jul 2023 Bundle-in-Bundle Encapsulation draft-ietf-dtn-bibect
Mar 2023 Bundle Progress Signalling
Mar 2023 Naming and Addressing Architecture Document
Jul 2022 Delay-Tolerant Management Architecture draft-ietf-dtn-ama