Search RFCs
RFC 9008
Using RPI Option Type, Routing Header for Source Routes, and IPv6-in-IPv6 Encapsulation in the RPL Data Plane,April 2021
- File formats:
- Also available:XML file for editing
- Status:
- PROPOSED STANDARD
- Updates:
- RFC 6553,RFC 6550,RFC 8138
- Authors:
- M.I. Robles
M. Richardson
P. Thubert - Stream:
- IETF
- Source:
- roll (rtg)
Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC9008
Discuss this RFC: Send questions or comments to the mailing listroll@ietf.org
Other actions:View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 9008
Abstract
This document looks at different data flows through Low-Power andLossy Networks (LLN) where RPL (IPv6 Routing Protocol for Low-Powerand Lossy Networks) is used to establish routing. The documentenumerates the cases where RPL Packet Information (RPI) Option Type(RFC 6553), RPL Source Route Header (RFC 6554), and IPv6-in-IPv6encapsulation are required in the data plane. This analysis providesthe basis upon which to design efficient compression of theseheaders. This document updates RFC 6553 by adding a change to the RPIOption Type. Additionally, this document updates RFC 6550 by defininga flag in the DODAG Information Object (DIO) Configuration option toindicate this change and updates RFC 8138 as well to consider the newOption Type when the RPL Option is decompressed.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.