RFC 6282: Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks
In plain English — editorial summary, not part of the RFC
This document updates RFC 4944, "Transmission of IPv6 Packets over IEEE 802.15.4 Networks". This document specifies an IPv6 header compression format for IPv6 packet delivery in Low Power Wireless Personal Area Networks (6LoWPANs). The compression format relies on shared context to allow compression of arbitrary prefixes. How the information is maintained in that shared context is out of scope. This document specifies compression of multicast addresses and a framework for compressing next headers. UDP header compression is specified within this framework. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6282
- Published
- September 2011
- Authors
- J. Hui; P. Thubert
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 24
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6606Problem Statement and Requirements for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) RoutingCurrent
May 2012
- RFC 74006LoWPAN-GHC: Generic Header Compression for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)Current
November 2014
- RFC 8724SCHC: Generic Framework for Static Context Header Compression and FragmentationUpdated
April 2020
- RFC 6553The Routing Protocol for Low-Power and Lossy Networks (RPL) Option for Carrying RPL Information in Data-Plane DatagramsUpdated
March 2012
- RFC 6554An IPv6 Routing Header for Source Routes with the Routing Protocol for Low-Power and Lossy Networks (RPL)Current
March 2012
- RFC 7228Terminology for Constrained-Node NetworksCurrent
May 2014
- RFC 7668IPv6 over BLUETOOTH(R) Low EnergyCurrent
October 2015
- RFC 8931IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Selective Fragment RecoveryCurrent
November 2020
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?