@techreport{ietf-schc-protocol-numbers-06,
    number =    {draft-ietf-schc-protocol-numbers-06},
    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-schc-protocol-numbers/06/},
    author =    {Robert Moskowitz and Pascal Thubert and Carles Gomez and Ana Minaburo and Marc Blanchet},
    title =     {{Protocol Numbers for SCHC}},
    pagetotal = 13,
    year =      2025,
    month =     dec,
    day =       23,
    abstract =  {This document requests an Internet Protocol Number, an Ethertype assignment, a CCSDS (Consultative Committee for Space Data Systems) Encapsulation Number, and well known ports for SCHC. The SCHC architecture, the SCHC instance establishment, and the SCHC compression/decompression processes are simplified when SCHC is easily recognised. Well-known protocol and port numbers are needed. The Internet Protocol Number request is so that SCHC can be used for IP independent of other transports such as UDP and ESP. The Ethertype and the CCSDS Encapsulation Number are to support generic use of native SCHC over any IEEE 802 technology and CCSDS link layer technology, respectively, for IP and non-IP protocols.},
}