RFC 6997: Reactive Discovery of Point-to-Point Routes in Low-Power and Lossy Networks
In plain English — editorial summary, not part of the RFC
This document specifies a point-to-point route discovery mechanism, complementary to the Routing Protocol for Low-power and Lossy Networks (RPL) core functionality. This mechanism allows an IPv6 router to discover "on demand" routes to one or more IPv6 routers in a Low-power and Lossy Network (LLN) such that the discovered routes meet specified metrics constraints.
Document record
- Document ID
- RFC6997
- Published
- August 2013
- Authors
- M. Goyal; E. Baccelli; M. Philipp; A. Brandt; J. Martocci
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 40
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6998A Mechanism to Measure the Routing Metrics along a Point-to-Point Route in a Low-Power and Lossy NetworkCurrent
August 2013
- RFC 6551Routing Metrics Used for Path Calculation in Low-Power and Lossy NetworksCurrent
March 2012
- RFC 6719The Minimum Rank with Hysteresis Objective FunctionCurrent
September 2012
- RFC 7416A Security Threat Analysis for the Routing Protocol for Low-Power and Lossy Networks (RPLs)Current
January 2015
- RFC 6552Objective Function Zero for the Routing Protocol for Low-Power and Lossy Networks (RPL)Current
March 2012
- RFC 7731Multicast Protocol for Low-Power and Lossy Networks (MPL)Current
February 2016
- RFC 7733Applicability Statement: The Use of the Routing Protocol for Low-Power and Lossy Networks (RPL) Protocol Suite in Home Automation and Building ControlCurrent
February 2016
- RFC 5826Home Automation Routing Requirements in Low-Power and Lossy NetworksCurrent
April 2010
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?