RFC 9008: Using RPI Option Type, Routing Header for Source Routes, and IPv6-in-IPv6 Encapsulation in the RPL Data Plane
In plain English — editorial summary, not part of the RFC
This document looks at different data flows through Low-Power and Lossy Networks (LLN) where RPL (IPv6 Routing Protocol for Low-Power and Lossy Networks) is used to establish routing. The document enumerates the cases where RPL Packet Information (RPI) Option Type (RFC 6553), RPL Source Route Header (RFC 6554), and IPv6-in-IPv6 encapsulation are required in the data plane. This analysis provides the basis upon which to design efficient compression of these headers. This document updates RFC 6553 by adding a change to the RPI Option Type. Additionally, this document updates RFC 6550 by defining a flag in the DODAG Information Object (DIO) Configuration option to indicate this change and updates RFC 8138 as well to consider the new Option Type when the RPL Option is decompressed.
Document record
- Document ID
- RFC9008
- Published
- April 2021
- Authors
- M.I. Robles; M. Richardson; P. Thubert
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 49
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7731Multicast Protocol for Low-Power and Lossy Networks (MPL)Current
February 2016
- RFC 9006TCP Usage Guidance in the Internet of Things (IoT)Current
March 2021
- RFC 8930On Forwarding 6LoWPAN Fragments over a Multi-Hop IPv6 NetworkCurrent
November 2020
- RFC 9159IPv6 Mesh over BLUETOOTH(R) Low Energy Using the Internet Protocol Support Profile (IPSP)Current
December 2021
- RFC 8724SCHC: Generic Framework for Static Context Header Compression and FragmentationUpdated
April 2020
- RFC 9354Transmission of IPv6 Packets over Power Line Communication (PLC) NetworksCurrent
January 2023
- RFC 9428Transmission of IPv6 Packets over Near Field CommunicationCurrent
July 2023
- RFC 8352Energy-Efficient Features of Internet of Things ProtocolsCurrent
April 2018
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?