SCHC: Generic Framework for Static Context Header Compression and Fragmentation
RFC 8724, “SCHC: Generic Framework for Static Context Header Compression and Fragmentation”, is a Proposed Standard document published in April 2020 by A. Minaburo, L. Toutain, C. Gomez, D. Barthel, JC. Zuniga. It has since been updated by RFC 9441. The canonical text is published by the RFC Editor.
Abstract
This document defines the Static Context Header Compression and fragmentation (SCHC) framework, which provides both a header compression mechanism and an optional fragmentation mechanism. SCHC has been designed with Low-Power Wide Area Networks (LPWANs) in mind.
SCHC compression is based on a common static context stored both in the LPWAN device and in the network infrastructure side. This document defines a generic header compression mechanism and its application to compress IPv6/UDP headers.
This document also specifies an optional fragmentation and reassembly mechanism. It can be used to support the IPv6 MTU requirement over the LPWAN technologies. Fragmentation is needed for IPv6 datagrams that, after SCHC compression or when such compression was not possible, still exceed the Layer 2 maximum payload size.
The SCHC header compression and fragmentation mechanisms are independent of the specific LPWAN technology over which they are used. This document defines generic functionalities and offers flexibility with regard to parameter settings and mechanism choices. This document standardizes the exchange over the LPWAN between two SCHC entities. Settings and choices specific to a technology or a product are expected to be grouped into profiles, which are specified in other documents. Data models for the context and profiles are out of scope.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8724 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 8723 Double Encryption Procedures for the Secure Real-Time Transport Protocol
- RFC 8725 JSON Web Token Best Current Practices
- RFC 8722 Defining the Role and Function of IETF Protocol Parameter Registry Operators
- RFC 8726 How Requests for IANA Action Will Be Handled on the Independent Stream
- RFC 8721 Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents
- RFC 8727 JSON Binding of the Incident Object Description Exchange Format
- RFC 8720 Principles for Operation of Internet Assigned Numbers Authority Registries
- RFC 8728 RFC Editor Model