RFC 6693: Probabilistic Routing Protocol for Intermittently Connected Networks
In plain English — editorial summary, not part of the RFC
This document is a product of the Delay Tolerant Networking Research Group and has been reviewed by that group. No objections to its publication as an RFC were raised. This document defines PRoPHET, a Probabilistic Routing Protocol using History of Encounters and Transitivity. PRoPHET is a variant of the epidemic routing protocol for intermittently connected networks that operates by pruning the epidemic distribution tree to minimize resource usage while still attempting to achieve the \%best-case routing capabilities of epidemic routing. It is intended for use in sparse mesh networks where there is no guarantee that a fully connected path between the source and destination exists at any time, rendering traditional routing protocols unable to deliver messages between hosts. These networks are examples of networks where there is a disparity between the latency requirements of applications and the capabilities of the underlying network (networks often referred to as delay and disruption tolerant). The document presents an architectural overview followed by the protocol specification. This document defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC6693
- Published
- August 2012
- Authors
- A. Lindgren; A. Doria; E. Davies; S. Grasic
- Status
- EXPERIMENTAL
- Stream
- IRTF
- Area
- —
- Pages
- 113
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6260Compressed Bundle Header Encoding (CBHE)Updated
May 2011
- RFC 6259Delay-Tolerant Networking Previous-Hop Insertion BlockCurrent
May 2011
- RFC 6258Delay-Tolerant Networking Metadata Extension BlockCurrent
May 2011
- RFC 6256Using Self-Delimiting Numeric Values in ProtocolsCurrent
May 2011
- RFC 6255Delay-Tolerant Networking Bundle Protocol IANA RegistriesCurrent
May 2011
- RFC 6179The Internet Routing Overlay Network (IRON)Current
March 2011
- RFC 5050Bundle Protocol SpecificationCurrent
November 2007
- RFC 8763Deployment Considerations for Information-Centric Networking (ICN)Current
April 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?