%% You should probably cite rfc8724 instead of this I-D.
@techreport{ietf-lpwan-ipv6-static-context-hc-04,
    number =    {draft-ietf-lpwan-ipv6-static-context-hc-04},
    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/04/},
    author =    {Ana Minaburo and Laurent Toutain and Carles Gomez},
    title =     {{LPWAN Static Context Header Compression (SCHC) and fragmentation for IPv6 and UDP}},
    pagetotal = 36,
    year =      ** No value found for 'doc.pub_date.year' **,
    month =     ** No value found for 'doc.pub_date' **,
    day =       ** No value found for 'doc.pub_date.day' **,
    abstract =  {This document describes a header compression scheme and fragmentation functionality for very low bandwidth networks. These techniques are especially tailored for LPWAN (Low Power Wide Area Network) networks. The Static Context Header Compression (SCHC) offers a great level of flexibility when processing the header fields and must be used for this kind of networks. A common context stored in a LPWAN device and in the network is used. This context stores information that will not be transmitted in the constrained network. Static context means that information stored in the context which describes field values, does not change during packet transmission, avoiding complex resynchronization mechanisms, incompatible with LPWAN characteristics. In most of the cases, IPv6/UDP headers are reduced to a small identifier called Rule ID. But sometimes the SCHC header compression will not be enough to send the packet in one L2 PDU, so this document also describes a Fragmentation protocol that must be used when needed. This document describes the generic compression/decompression mechanism and applies it to IPv6/UDP headers. Similar mechanisms for other protocols such as CoAP will be described in separate documents. Moreover, this document specifies fragmentation and reassembly mechanims for SCHC compressed packets exceeding the L2 PDU size and for the case where the SCHC compression is not possible then the IPv6/UDP packet is sent using the fragmentation protocol.},
}