@techreport{bormann-core-proactive-ct-00,
    number =    {draft-bormann-core-proactive-ct-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-bormann-core-proactive-ct/00/},
    author =    {Carsten Bormann and Klaus Hartke},
    title =     {{Proactively Assigning CoAP Content-Format Numbers to Registered Media Types}},
    pagetotal = 7,
    year =      2018,
    month =     jul,
    day =       2,
    abstract =  {In order to use a media type with the Constrained Application Protocol (CoAP), a numeric identifier needs to be registered for it, the Content-Format number. RFC 7252 defines registration procedures for Content-Format numbers. The present document defines a proactive procedure to register a Content-Format number for many of the media types that are registered and discusses the benefits and limitations of that approach.},
}