RFC 6552: Objective Function Zero for the Routing Protocol for Low-Power and Lossy Networks (RPL)
In plain English — editorial summary, not part of the RFC
The Routing Protocol for Low-Power and Lossy Networks (RPL) specification defines a generic Distance Vector protocol that is adapted to a variety of network types by the application of specific Objective Functions (OFs). An OF states the outcome of the process used by a RPL node to select and optimize routes within a RPL Instance based on the Information Objects available; an OF is not an algorithm. This document specifies a basic Objective Function that relies only on the objects that are defined in the RPL and does not use any protocol extensions. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6552
- Published
- March 2012
- Authors
- P. Thubert
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6550RPL: IPv6 Routing Protocol for Low-Power and Lossy NetworksUpdated
March 2012
- RFC 6606Problem Statement and Requirements for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) RoutingCurrent
May 2012
- RFC 9692RIFT: Routing in Fat TreesCurrent
April 2025
- 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 6130Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)Updated
April 2011
- 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
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?