Skip to main content

Proactively Assigning CoAP Content-Format Numbers to Registered Media Types

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Carsten Bormann , Klaus Hartke
Last updated 2019-01-03 (Latest revision 2018-07-02)
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


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.


Carsten Bormann
Klaus Hartke

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)