RFC 6971: Depth-First Forwarding (DFF) in Unreliable Networks
In plain English — editorial summary, not part of the RFC
This document specifies the Depth-First Forwarding (DFF) protocol for IPv6 networks, a data-forwarding mechanism that can increase reliability of data delivery in networks with dynamic topology and/or lossy links. The protocol operates entirely on the forwarding plane but may interact with the routing plane. DFF forwards data packets using a mechanism similar to a "depth-first search" for the destination of a packet. The routing plane may be informed of failures to deliver a packet or loops. This document specifies the DFF mechanism both for IPv6 networks (as specified in RFC 2460) and for "mesh-under" Low-Power Wireless Personal Area Networks (LoWPANs), as specified in RFC 4944. The design of DFF assumes that the underlying link layer provides means to detect if a packet has been successfully delivered to the Next Hop or not. It is applicable for networks with little traffic and is used for unicast transmissions only.
Document record
- Document ID
- RFC6971
- Published
- June 2013
- Authors
- U. Herberg; A. Cardenas; T. Iwao; M. Dow; S. Cespedes
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- —
- Pages
- 41
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8513A YANG Data Model for Dual-Stack Lite (DS-Lite)Current
January 2019
- RFC 7785Recommendations for Prefix Binding in the Context of Softwire Dual-Stack LiteCurrent
February 2016
- RFC 6957Duplicate Address Detection ProxyCurrent
June 2013
- RFC 6911RADIUS Attributes for IPv6 Access NetworksCurrent
April 2013
- RFC 7048Neighbor Unreachability Detection Is Too ImpatientCurrent
January 2014
- RFC 7219SEcure Neighbor Discovery (SEND) Source Address Validation Improvement (SAVI)Current
May 2014
- RFC 6706Asymmetric Extended Route Optimization (AERO)Current
August 2012
- RFC 6619Scalable Operation of Address Translators with Per-Interface BindingsCurrent
June 2012
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?