%% You should probably cite rfc8724 instead of this I-D. @techreport{ietf-lpwan-ipv6-static-context-hc-10, number = {draft-ietf-lpwan-ipv6-static-context-hc-10}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-lpwan-ipv6-static-context-hc/10/}, author = {Ana Minaburo and Laurent Toutain and Carles Gomez}, title = {{LPWAN Static Context Header Compression (SCHC) and fragmentation for IPv6 and UDP}}, pagetotal = 60, year = 2018, month = feb, day = 28, abstract = {This document defines the Static Context Header Compression (SCHC) framework, which provides header compression and fragmentation functionality. SCHC has been tailored for Low Power Wide Area Networks (LPWAN). SCHC compression is based on a common static context stored in LPWAN devices and in the network. This document applies SCHC compression to IPv6/UDP headers. This document also specifies a fragmentation and reassembly mechanism that is used to support the IPv6 MTU requirement over LPWAN technologies. Fragmentation is mandatory for IPv6 datagrams that, after SCHC compression or when it has not been possible to apply such compression, still exceed the layer two maximum payload size. The SCHC header compression mechanism is independent of the specific LPWAN technology over which it will be used. Note that this document defines generic functionality. This document purposefully offers flexibility with regard to parameter settings and mechanism choices, that are expected to be made in other, technology-specific, documents.}, }