RFC 4838: Delay-Tolerant Networking Architecture
In plain English — editorial summary, not part of the RFC
This document describes an architecture for delay-tolerant and disruption-tolerant networks, and is an evolution of the architecture originally designed for the Interplanetary Internet, a communication system envisioned to provide Internet-like services across interplanetary distances in support of deep space exploration. This document describes an architecture that addresses a variety of problems with internetworks having operational and performance characteristics that make conventional (Internet-like) networking approaches either unworkable or impractical. We define a message- oriented overlay that exists above the transport (or other) layers of the networks it interconnects. The document presents a motivation for the architecture, an architectural overview, review of state management required for its operation, and a discussion of application design issues. This document represents the consensus of the IRTF DTN research group and has been widely reviewed by that group. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4838
- Published
- April 2007
- Authors
- V. Cerf; S. Burleigh; A. Hooke; L. Torgerson; R. Durst; K. Scott; K. Fall; H. Weiss
- Status
- INFORMATIONAL
- Stream
- IRTF
- Area
- —
- Pages
- 35
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5345Simple Network Management Protocol (SNMP) Traffic Measurements and Trace Exchange FormatsCurrent
October 2008
- RFC 5773Analysis of Inter-Domain Routing Requirements and HistoryCurrent
February 2010
- RFC 9775IRTF Code of ConductCurrent
March 2025
- RFC 2850Charter of the Internet Architecture Board (IAB)Updated
May 2000
- RFC 1601Charter of the Internet Architecture Board (IAB)Obsoleted
March 1994
- RFC 1358Charter of the Internet Architecture Board (IAB)Obsoleted
August 1992
- RFC 9281Entities Involved in the IETF Standards ProcessCurrent
June 2022
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?