RFC 6551: Routing Metrics Used for Path Calculation in Low-Power and Lossy Networks
In plain English — editorial summary, not part of the RFC
Low-Power and Lossy Networks (LLNs) have unique characteristics compared with traditional wired and ad hoc networks that require the specification of new routing metrics and constraints. By contrast, with typical Interior Gateway Protocol (IGP) routing metrics using hop counts or link metrics, this document specifies a set of link and node routing metrics and constraints suitable to LLNs to be used by the Routing Protocol for Low-Power and Lossy Networks (RPL). [STANDARDS-TRACK]
Document record
- Document ID
- RFC6551
- Published
- March 2012
- Authors
- JP. Vasseur; M. Kim; K. Pister; N. Dejean; D. Barthel
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6719The Minimum Rank with Hysteresis Objective FunctionCurrent
September 2012
- RFC 6997Reactive Discovery of Point-to-Point Routes in Low-Power and Lossy NetworksCurrent
August 2013
- RFC 6998A Mechanism to Measure the Routing Metrics along a Point-to-Point Route in a Low-Power and Lossy NetworkCurrent
August 2013
- RFC 7416A Security Threat Analysis for the Routing Protocol for Low-Power and Lossy Networks (RPLs)Current
January 2015
- RFC 7731Multicast Protocol for Low-Power and Lossy Networks (MPL)Current
February 2016
- RFC 6552Objective Function Zero for the Routing Protocol for Low-Power and Lossy Networks (RPL)Current
March 2012
- RFC 5826Home Automation Routing Requirements in Low-Power and Lossy NetworksCurrent
April 2010
- RFC 5673Industrial Routing Requirements in Low-Power and Lossy NetworksCurrent
October 2009
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?