Update to the IANA CoAP Content-Formats Registration Procedures
draft-ietf-core-cf-reg-update-09

Constrained RESTful Environments                              T. Fossati
Internet-Draft                                                    Linaro
Updates: 7252 (if approved)                                      E. Dijk
Intended status: Standards Track                       IoTconsultancy.nl
Expires: 11 November 2025                                    10 May 2025

    Update to the IANA CoAP Content-Formats Registration Procedures
                    draft-ietf-core-cf-reg-update-09

Abstract

   This document updates RFC7252 regarding the registration procedures
   for the "CoAP Content-Formats" IANA registry, within the "Constrained
   RESTful Environments (CoRE) Parameters" registry group.  This
   document also introduces a new column, "Media Type", to the registry.
   Furthermore, this document reserves Content-Format identifiers 64998
   and 64999 for use in documentation.

About This Document

   This note is to be removed before publishing as an RFC.

   The latest revision of this draft can be found at https://core-
   wg.github.io/cf-reg-update/draft-ietf-core-cf-reg-update.html.
   Status information for this document may be found at
   https://datatracker.ietf.org/doc/draft-ietf-core-cf-reg-update/.

   Discussion of this document takes place on the Constrained RESTful
   Environments Working Group mailing list (mailto:core@ietf.org), which
   is archived at https://mailarchive.ietf.org/arch/browse/core/.
   Subscribe at https://www.ietf.org/mailman/listinfo/core/.

   Source for this draft and an issue tracker can be found at
   https://github.com/core-wg/cf-reg-update.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

Fossati & Dijk          Expires 11 November 2025                [Page 1]
Internet-Draft  CoAP Content-Format Registrations Update        May 2025

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 11 November 2025.

Copyright Notice

   Copyright (c) 2025 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions and Definitions . . . . . . . . . . . . . . . . .   3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  CoAP Content-Formats Registry . . . . . . . . . . . . . .   4
       4.1.1.  Temporary Content-Format Registrations  . . . . . . .   7
       4.1.2.  Adding the Media Type Column to the Registry  . . . .   7
       4.1.3.  Expert Review Procedure . . . . . . . . . . . . . . .   8
       4.1.4.  Preferred Format for the Content Type Field . . . . .   9
       4.1.5.  Examples for Invalid Registration Requests  . . . . .   9
     4.2.  Temporary Note Removal  . . . . . . . . . . . . . . . . .  12
     4.3.  New Note Addition . . . . . . . . . . . . . . . . . . . .  12
     4.4.  Reserving Content-Format Identifiers 64998 and 64999 for
           Documentation . . . . . . . . . . . . . . . . . . . . . .  13
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .  13
     5.2.  Informative References  . . . . . . . . . . . . . . . . .  14
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

Fossati & Dijk          Expires 11 November 2025                [Page 2]
Internet-Draft  CoAP Content-Format Registrations Update        May 2025

1.  Introduction

   Section 12.3 of [RFC7252] describes the registration procedures for
   the "CoAP Content-Formats" IANA registry within the "Constrained
   RESTful Environments (CoRE) Parameters" registry group
   [IANA.core-parameters].  (Note that the columns of this registry have
   been revised according to [Err4954].)  In particular, it defines the
   rules for obtaining CoAP Content-Format identifiers from the "IETF
   Review or IESG Approval" range of the registry (256-9999) as well as
   from the First Come First Served (FCFS) range of the registry
   (10000-64999).  For the FCFS range, these rules do not involve the
   Designated Expert (DE) and are managed solely by IANA personnel to
   finalize the registration.

   Unfortunately, the rules do not explicitly require checking that the
   combination of Content-Type (i.e., Media Type with optional
   parameters) and Content Coding associated with the requested CoAP
   Content-Format is semantically valid.  This task is generally non-
   trivial, requires knowledge from multiple documents and technologies,
   and should not be solely demanded from the registrar.  This lack of
   guidance may engender confusion in both the registering party and the
   registrar, and has already led to erroneous registrations.

   This document updates [RFC7252] by modifying the registration
   procedures for the "CoAP Content-Formats" registry to mitigate the
   risk of unintentional or malicious errors.  These updates amend the
   different ranges of the registry, introduce a review procedure to be
   performed for most ranges of the registry, and allow the registration
   of temporary Content-Format identifiers.  This document also
   introduces a new column, "Media Type", to the registry.  Furthermore,
   this document reserves Content-Format identifiers 64998 and 64999 for
   use in documentation.

2.  Conventions and Definitions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

   This document uses the terms "Media Type", "Content Coding",
   "Content-Type", and "Content Format" as defined in Section 2 of
   [RFC9193].  In this document, those terms are fully capitalized.

Fossati & Dijk          Expires 11 November 2025                [Page 3]
Internet-Draft  CoAP Content-Format Registrations Update        May 2025

3.  Security Considerations

   This document hardens the registration procedures of CoAP Content-
   Formats in ways that reduce the chances of malicious manipulation of
   the associated registry.

   Other than that, it does not change the Security Considerations of
   [RFC7252].

4.  IANA Considerations

   This document updates the IANA procedures defined in [RFC7252] for
   registering CoAP Content-Formats as described in Section 4.1.  It
   also removes a note that was added to the registry as a temporary
   patch (Section 4.2), adds a new note concerning temporary
   registrations (Section 4.3) and reserves Content-Format IDs 64998 and
   64999 for documentation (Section 4.4).

4.1.  CoAP Content-Formats Registry

   This section and its subsections replace Section 12.3 of [RFC7252].

   // RFC Editor: in this section, please replace RFCthis with the RFC
   // number assigned to this document and remove this note.

   Internet Media Types are identified by a string, such as
   "application/xml" [RFC2046].  In order to minimize the overhead of
   using Media Types to indicate the format of payloads, [RFC7252] has
   defined a registry for a subset of Internet Media Types to be used in
   CoAP and assigned each, in combination with a Content Coding, a
   numeric identifier.  The name of the registry is "CoAP Content-
   Formats", within the "CoRE Parameters" registry group.

   Each entry in the registry must include the Media Type registered
   with IANA, the numeric identifier in the range 0-65535 to be used for
   that Media Type in CoAP, the Content Coding associated with this
   identifier, and a reference to a document describing what a payload
   with that Media Type means semantically.

   CoAP does not include a separate way to convey Content Coding
   information with a request or response, and for that reason the
   Content Coding is also specified for each identifier (if any).  If
   multiple Content Codings will be used with a Media Type, then a
   separate Content-Format identifier for each is to be registered.
   Similarly, other parameters related to an Internet Media Type can be
   defined for a CoAP Content-Format entry.

Fossati & Dijk          Expires 11 November 2025                [Page 4]
Internet-Draft  CoAP Content-Format Registrations Update        May 2025

   The registration procedures for CoAP Content-Formats are described in
   Table 1.

   +=============+==============+======================================+
   | Range       | Registration | Notes                                |
   |             | Procedures   |                                      |
   +=============+==============+======================================+
   | 0-255       | Expert       | Review procedure described in        |
   |             | Review       | RFCthis, Section 4.1.3.              |
   +-------------+--------------+--------------------------------------+
   | 256-9999    | IETF Review  | Review procedure described in        |
   |             | with Expert  | RFCthis, Section 4.1.3               |
   |             | Review or    |                                      |
   |             | IESG         |                                      |
   |             | Approval     |                                      |
   |             | with Expert  |                                      |
   |             | Review       |                                      |
   +-------------+--------------+--------------------------------------+
   | 10000-19999 | Expert       | Review procedure described in        |
   |             | Review       | RFCthis, Section 4.1.3.              |
   +-------------+--------------+--------------------------------------+
   | 20000-32999 | First Come   | FCFS is allowed if the               |
   |             | First Served | registration:                        |
   |             | (FCFS)       | * has no parameters, and             |
   |             |              | * has an empty Content Coding, and   |
   |             |              | * the Media Type is not yet used     |
   |             |              | in this registry, and                |
   |             |              | * the Media Type is registered (or   |
   |             |              | approved for registration) in the    |
   |             |              | "Media Types" registry               |
   |             |              | [IANA.media-types].                  |
   +-------------+--------------+--------------------------------------+
   | 33000-64997 | Expert       | Review procedure described in        |
   |             | Review       | RFCthis, Section 4.1.3.              |
   +-------------+--------------+--------------------------------------+
   | 64998-64999 | -            | Reserved for Documentation           |
   +-------------+--------------+--------------------------------------+
   | 65000-65535 | Experimental | No operational use                   |
   |             | Use          |                                      |
   +-------------+--------------+--------------------------------------+

           Table 1: CoAP Content-Formats: Registration Procedures

   Because the namespace of single-byte identifiers is so small, the
   IANA policy for additions in the range 0-255 inclusive to the
   registry is "Expert Review" as described in Section 4.5 of [BCP26].
   For the handling of temporary allocations within the 0-255 range, see
   also Section 4.1.1, Paragraph 6.

Fossati & Dijk          Expires 11 November 2025                [Page 5]
Internet-Draft  CoAP Content-Format Registrations Update        May 2025

   The 256-9999 range has registration procedures requiring "IETF Review
   with Expert Review" or "IESG Approval with Expert Review."  In
   particular:

   *  All assignments according to "IETF Review with Expert Review" are
      made on an "IETF Review" basis per Section 4.8 of [BCP26] with
      "Expert Review" additionally required per Section 4.5 of [BCP26].

      The procedure for early IANA allocation of "standards track code
      points" defined in [RFC7120] also applies.  When such a procedure
      is used, IANA will ask the Designated Expert(s) to approve the
      early allocation before registration.  In addition, working group
      chairs are encouraged to consult the Expert(s) early during the
      process outlined in Section 3.1 of [RFC7120].

   *  All assignments according to "IESG Approval with Expert Review"
      are made on an "IESG Approval" basis per Section 4.10 of [BCP26]
      with "Expert Review" additionally required per Section 4.5 of
      [BCP26].

   The registration policy for the 10000-19999 and 33000-64997 ranges is
   "Expert Review", following the procedure described in Section 4.1.3.

   The registration policy for the 20000-32999 range is FCFS.  A
   registration request for this range must consist solely of a
   registered Media Type name in the "Content Type" field, without any
   parameter names or "Content Coding", and the Media Type must not have
   been used in this registry yet.  If the criteria do not apply, a
   registration for a different range (which requires Expert Review) can
   be requested.

   The identifiers between 65000 and 65535 inclusive are reserved for
   experiments.  They are not meant for vendor-specific use of any kind
   and MUST NOT be used in operational deployments.

   In machine-to-machine applications, it is not expected that generic
   Internet Media Types such as text/plain, application/xml or
   application/octet-stream are useful for real applications in the long
   term.  It is recommended that M2M applications making use of CoAP
   request new Internet Media Types from IANA indicating semantic
   information about how to create or parse a payload.  For example, a
   Smart Energy application payload carried as Concise Binary Object
   Representation (CBOR) might request a more specific type like
   application/se+cbor.

Fossati & Dijk          Expires 11 November 2025                [Page 6]
Internet-Draft  CoAP Content-Format Registrations Update        May 2025

4.1.1.  Temporary Content-Format Registrations

   This section clarifies that the "CoAP Content-Formats" registry
   allows temporary registrations within the 0-64998 range.

   A temporary registration may be created for example by an IANA early
   allocation action [RFC7120].  If the referenced Media Type is
   provisional (that is, included in the IANA "Provisional Standard
   Media Type" registry [IANA.provisional-standard-media-types]) then a
   created registration is always temporary.

   A temporary registration is marked as such by IANA in the
   corresponding registry entry.  Once the required registration
   procedure (defined in Table 1) for the temporary ID has successfully
   completed, and the referenced Media Type is included in the IANA
   Media Types registry [IANA.media-types], IANA must remove any
   indication about the temporary nature of the registration so that the
   entry becomes permanent.

   If a temporary registration does not successfully complete the
   registration procedure, IANA must remove the entry and set the
   Content-Format ID value back to "Unassigned".  This may happen for
   example when an Internet-Draft requesting a Content-Format ID is
   abandoned.  If a temporary registration (in any range) refers to a
   provisional Media Type that is abandoned, IANA must remove the entry
   and set the Content-Format ID value back to "Unassigned".

   Note that in the 10000-64998 range the abandonment of a document
   requesting a Content-Format ID does not cause an entry to be removed.
   That is because the required registration procedure for this range
   does not require completion of any standards process, nor does it
   require a registering document.

   Temporary registrations within the 0-255 range are exempt from the
   formal renewal process outlined in [RFC7120].  Specifically, IANA
   will not monitor the removal of registrations in this range.
   Instead, the Designated Experts direct IANA to carry out this task.

4.1.2.  Adding the Media Type Column to the Registry

   To assist users of the "CoAP Content-Formats" registry in finding
   detailed information about the Media Type associated with each CoAP
   Content-Format, and to ensure that a Media Type exists before a new
   entry can be registered, IANA is requested to add a new column "Media
   Type" to the registry.  This new column is placed directly to the
   right of the existing "Content Type" column.

Fossati & Dijk          Expires 11 November 2025                [Page 7]
Internet-Draft  CoAP Content-Format Registrations Update        May 2025

   The "Media Type" field for each entry lists the (base) Media Type
   name and provides a hyperlink to registration information for that
   Media Type as recorded by IANA.  If the Media Type is provisional,
   the hyperlink points to the IANA "Provisional Standard Media Type"
   registry [IANA.provisional-standard-media-types].  If a provisional
   Media Type becomes a permanent Media Type, IANA must update the
   "Media Type" field in the associated registry entries to ensure the
   hyperlink directs to the registration information for that Media
   Type.

   Note that the registration request procedure remains unchanged.  A
   requester does not need to fill out the "Media Type" field
   separately, as the necessary information is already provided in the
   "Content Type" field of the request.

4.1.3.  Expert Review Procedure

   The Designated Expert (DE) is instructed to perform the Expert
   Review, as described by the following checklist:

   1.  The combination of Content-Type and Content Coding for which the
       registration is requested must not be already present in the
       "CoAP Content-Formats" registry;

   2.  The Media Type associated with the requested Content-Format must
       either be registered in the "Media Types" registry
       [IANA.media-types] or approved for registration.  Alternatively,
       it may be listed in the "Provisional Standard Media Type"
       registry [IANA.provisional-standard-media-types].  The use of
       provisional standard Media Types is only permitted for Content-
       Format identifiers within the ranges of 0-255 and 256-9999;

   3.  The optional parameter names must have been defined in
       association with the Media Type, and any parameter values
       associated with such parameter names must be as permitted;

   4.  The Content Type must be in the preferred format defined in
       Section 4.1.4;

   5.  If a Content Coding is specified, it must exist (or must have
       been approved for registration) in the "HTTP Content Coding"
       registry of the "Hypertext Transfer Protocol (HTTP) Parameters"
       [IANA.http-parameters].

Fossati & Dijk          Expires 11 November 2025                [Page 8]
Internet-Draft  CoAP Content-Format Registrations Update        May 2025

   For the 0-255 range, in addition to the checks described above, the
   DE is instructed to also evaluate the requested codepoint concerning
   the limited availability of the 1-byte codepoint space.  For the
   ranges 256-9999, 10000-19999, and 33000-64997, a similar criterion
   may also apply where combinations of Media Type parameters and
   Content Coding choices consume considerable codepoint space.

4.1.4.  Preferred Format for the Content Type Field

   This section defines the preferred string format for including a
   requested Content Type into the "CoAP Content-Formats" registry.
   During the review process, the Designated Expert(s) or IANA may
   rewrite a requested Content Type into this preferred string format
   before approval.

   The preferred string format is as defined in Section 8.3.1 of
   [RFC9110] and follows these rules:

   1.  For any case-insensitive elements, lowercase characters are used.

   2.  Parameter values are only quoted if the value is such that it
       requires use of quoted-string per Section 5.6.6 of [RFC9110].
       Otherwise, a parameter value is included unquoted.

   3.  A single semicolon character without any adjacent whitespace
       characters is used as the separator between Media Type and
       parameters.

4.1.5.  Examples for Invalid Registration Requests

   This section provides examples of registration requests for the "CoAP
   Content-Formats" Registry that are invalid but would be approved
   under the procedure defined in Section 12.3 of [RFC7252].  The
   checklist defined in Section 4.1.3 should prevent any of these
   attempts from succeeding.  These examples serve as a representative,
   but not exhaustive, sample to train the DE's eye on invalid
   registration attempts.

   All the example registration requests use two CoAP Content-Format
   identifiers: 64998 and 64999.

   For each of the following example registration requests, one can
   create a similar instance where the requested registration is for a
   CoAP Content-Format identifier within the "IETF Review or IESG
   Approval" range.  Likewise, such registrations must not be allowed to
   succeed.

Fossati & Dijk          Expires 11 November 2025                [Page 9]
Internet-Draft  CoAP Content-Format Registrations Update        May 2025

4.1.5.1.  The Media Type is Unknown

   The registrant requests an FCFS Content-Format ID for an unknown
   Media Type:

   +==========================+================+=======+
   | Content Type             | Content Coding | ID    |
   +==========================+================+=======+
   | application/unknown+cbor | -              | 64999 |
   +--------------------------+----------------+-------+

       Table 2: Attempt at Registering Content-Format
                 for an Unknown Media Type

4.1.5.2.  The Media Type Parameter is Unknown

   The registrant requests an FCFS Content-Format ID for an existing
   Media Type with an unknown parameter:

   +======================================+================+=======+
   | Content Type                         | Content Coding | ID    |
   +======================================+================+=======+
   | application/cose;unknown-parameter=1 | -              | 64999 |
   +--------------------------------------+----------------+-------+

     Table 3: Attempt at Registering Content-Format for Media Type
                         with Unknown Parameter

4.1.5.3.  The Media Type Parameter Value is Invalid

   The registrant requests an FCFS Content-Format ID for an existing
   Media Type with an invalid parameter value:

   +====================================+================+=======+
   | Content Type                       | Content Coding | ID    |
   +====================================+================+=======+
   | application/cose;cose-type=invalid | -              | 64999 |
   +------------------------------------+----------------+-------+

       Table 4: Attempt at Registering Content-Format for Media
                  Type with Invalid Parameter Value

4.1.5.4.  The Content Coding is Unknown

   The registrant requests an FCFS Content-Format ID for an existing
   Media Type with an unknown Content Coding:

Fossati & Dijk          Expires 11 November 2025               [Page 10]
Internet-Draft  CoAP Content-Format Registrations Update        May 2025

   +========================+================+=======+
   | Content Type           | Content Coding | ID    |
   +========================+================+=======+
   | application/senml+cbor | inflate        | 64999 |
   +------------------------+----------------+-------+

      Table 5: Attempt at Registering Content-Format
               with Unknown Content Coding

4.1.5.5.  Duplicate Entry with Default Media Type Parameters

   The registrant requests an FCFS Content-Format ID for a Media Type
   that includes a parameter set to its default value, while a
   (hypothetical) Content-Format ID 64998 is already registered for this
   Media Type without that parameter.  As a result, this could lead to
   the creation of two separate Content-Format IDs for the same
   "logical" entry.

   +==================================+================+=======+
   | Content Type                     | Content Coding | ID    |
   +==================================+================+=======+
   | application/my                   | -              | 64998 |
   +----------------------------------+----------------+-------+
   | application/my;parameter=default | -              | 64999 |
   +----------------------------------+----------------+-------+

       Table 6: Attempt at Registering an Equivalent Logical
            Entry with a Different Content-Format ID (1)

4.1.5.6.  Duplicate Entry with Default Content Coding

   The registrant requests an FCFS Content-Format ID for the "identity"
   Content Coding, which is the default coding.  If accepted, this
   request would duplicate an entry with (hypothetical) Content-Format
   ID 64998 where the "Content Coding" field is left empty.

   +================+================+=======+
   | Content Type   | Content Coding | ID    |
   +================+================+=======+
   | application/my | -              | 64998 |
   +----------------+----------------+-------+
   | application/my | identity       | 64999 |
   +----------------+----------------+-------+

        Table 7: Attempt at Registering an
         Equivalent Logical Entry with a
         Different Content-Format ID (2)

Fossati & Dijk          Expires 11 November 2025               [Page 11]
Internet-Draft  CoAP Content-Format Registrations Update        May 2025

4.1.5.7.  Duplicate Entry with Equivalent Parameter

   The registrant requests an FCFS Content-Format ID for a Media Type
   that includes a parameter.  The value of this parameter appears
   distinct from that of a (hypothetical) previously registered Content-
   Format ID 64998 that also includes this parameter.  However, the
   semantics of the parameter value are identical to the existing
   registration.

   In this example, the eat_profile parameter value (which can be any
   URI) is set as a Uniform Resource Name (URN) [RFC8141].  Since for
   URNs, the Namespace Identifier (example in this example) is defined
   as case insensitive, the two registrations are semantically
   identical.

   +=====================================+================+=======+
   | Content Type                        | Content Coding | ID    |
   +=====================================+================+=======+
   | application/                        | -              | 64998 |
   | eat+cwt;eat_profile="urn:example:1" |                |       |
   +-------------------------------------+----------------+-------+
   | application/                        | -              | 64999 |
   | eat+cwt;eat_profile="urn:EXAMPLE:1" |                |       |
   +-------------------------------------+----------------+-------+

     Table 8: Attempt at Registering an Equivalent Logical Entry
                with a Different Content-Format ID (3)

4.2.  Temporary Note Removal

   This section is to be removed before publishing as an RFC.

   The following note has been added to the registry as a temporary fix:

      "Note: The validity of the combination of Content Coding, Content
      Type and parameters is checked prior to assignment."

   IANA is instructed to remove this note from the registry when this
   document is approved for publication.  RFC-Editor: please remove this
   section once the note has been removed.

4.3.  New Note Addition

   // RFC Editor: in this section, please replace RFCthis with the RFC
   // number assigned to this document and remove this note.

   IANA is instructed to add the following note to the registry:

Fossati & Dijk          Expires 11 November 2025               [Page 12]
Internet-Draft  CoAP Content-Format Registrations Update        May 2025

      "Note: As per RFCthis, temporary registrations within the 0-255
      range are approved by Designated Experts.  These registrations are
      not subject to the formal [RFC7120] renewal process."

4.4.  Reserving Content-Format Identifiers 64998 and 64999 for
      Documentation

   IANA is instructed to reserve Content-Format identifiers 64998 and
   64999 for use in documentation.

5.  References

5.1.  Normative References

   [BCP26]    Cotton, M., Leiba, B., and T. Narten, "Guidelines for
              Writing an IANA Considerations Section in RFCs", BCP 26,
              RFC 8126, DOI 10.17487/RFC8126, June 2017,
              <https://www.rfc-editor.org/rfc/rfc8126>.

   [IANA.core-parameters]
              IANA, "Constrained RESTful Environments (CoRE)
              Parameters",
              <https://www.iana.org/assignments/core-parameters>.

   [IANA.http-parameters]
              IANA, "Hypertext Transfer Protocol (HTTP) Parameters",
              <https://www.iana.org/assignments/http-parameters>.

   [IANA.media-types]
              IANA, "Media Types",
              <https://www.iana.org/assignments/media-types>.

   [IANA.provisional-standard-media-types]
              IANA, "Provisional Standard Media Type Registry",
              <https://www.iana.org/assignments/provisional-standard-
              media-types>.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/rfc/rfc2119>.

   [RFC7120]  Cotton, M., "Early IANA Allocation of Standards Track Code
              Points", BCP 100, RFC 7120, DOI 10.17487/RFC7120, January
              2014, <https://www.rfc-editor.org/rfc/rfc7120>.

Fossati & Dijk          Expires 11 November 2025               [Page 13]
Internet-Draft  CoAP Content-Format Registrations Update        May 2025

   [RFC7252]  Shelby, Z., Hartke, K., and C. Bormann, "The Constrained
              Application Protocol (CoAP)", RFC 7252,
              DOI 10.17487/RFC7252, June 2014,
              <https://www.rfc-editor.org/rfc/rfc7252>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/rfc/rfc8174>.

   [RFC9110]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
              Ed., "HTTP Semantics", STD 97, RFC 9110,
              DOI 10.17487/RFC9110, June 2022,
              <https://www.rfc-editor.org/rfc/rfc9110>.

   [RFC9193]  Keränen, A. and C. Bormann, "Sensor Measurement Lists
              (SenML) Fields for Indicating Data Value Content-Format",
              RFC 9193, DOI 10.17487/RFC9193, June 2022,
              <https://www.rfc-editor.org/rfc/rfc9193>.

5.2.  Informative References

   [Err4954]  RFC Errata Report 4954, RFC 7252,
              <https://www.rfc-editor.org/errata/eid4954>.

   [RFC2046]  Freed, N. and N. Borenstein, "Multipurpose Internet Mail
              Extensions (MIME) Part Two: Media Types", RFC 2046,
              DOI 10.17487/RFC2046, November 1996,
              <https://www.rfc-editor.org/rfc/rfc2046>.

   [RFC8141]  Saint-Andre, P. and J. Klensin, "Uniform Resource Names
              (URNs)", RFC 8141, DOI 10.17487/RFC8141, April 2017,
              <https://www.rfc-editor.org/rfc/rfc8141>.

Acknowledgments

   Thank you Amanda Baber, Carsten Bormann, Christer Holmberg, Éric
   Vyncke, Francesca Palombini, Ketan Talaulikar, Marco Tiloca, Mohamed
   Boucadair, Paul Wouters, Renzo Navas, and Rich Salz for your reviews,
   comments, suggestions, and fixes.

Authors' Addresses

   Thomas Fossati
   Linaro
   Email: thomas.fossati@linaro.org

Fossati & Dijk          Expires 11 November 2025               [Page 14]
Internet-Draft  CoAP Content-Format Registrations Update        May 2025

   Esko Dijk
   IoTconsultancy.nl
   Email: esko.dijk@iotconsultancy.nl

Fossati & Dijk          Expires 11 November 2025               [Page 15]