%% You should probably cite rfc8824 instead of this I-D.
@techreport{ietf-lpwan-coap-static-context-hc-19,
    number =    {draft-ietf-lpwan-coap-static-context-hc-19},
    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-coap-static-context-hc/19/},
    author =    {Ana Minaburo and Laurent Toutain and Ricardo Andreasen},
    title =     {{Static Context Header Compression (SCHC) for the Constrained Application Protocol (CoAP)}},
    pagetotal = 30,
    year =      2021,
    month =     mar,
    day =       8,
    abstract =  {This document defines how to compress Constrained Application Protocol (CoAP) headers using the Static Context Header Compression and fragmentation (SCHC) framework. SCHC defines a header compression mechanism adapted for Constrained Devices. SCHC uses a static description of the header to reduce the header's redundancy and size. While RFC 8724 describes the SCHC compression and fragmentation framework, and its application for IPv6/UDP headers, this document applies SCHC to CoAP headers. The CoAP header structure differs from IPv6 and UDP, since CoAP uses a flexible header with a variable number of options, themselves of variable length. The CoAP message format is asymmetric: the request messages have a header format different from the format in the response messages. This specification gives guidance on applying SCHC to flexible headers and how to leverage the asymmetry for more efficient compression Rules.},
}