Proactively Assigning CoAP Content-Format Numbers to Registered Media Types
draft-bormann-core-proactive-ct-00

Document Type Active Internet-Draft (individual)
Last updated 2018-07-02
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
CoRE Working Group                                            C. Bormann
Internet-Draft                                   Universitaet Bremen TZI
Intended status: Best Current Practice                         K. Hartke
Expires: January 1, 2019                                        Ericsson
                                                           June 30, 2018

 Proactively Assigning CoAP Content-Format Numbers to Registered Media
                                 Types
                   draft-bormann-core-proactive-ct-00

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.

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/.

   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 January 1, 2019.

Copyright Notice

   Copyright (c) 2018 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

Bormann & Hartke         Expires January 1, 2019                [Page 1]
Internet-Draft  Proactively Assigning Content-Format IDs       June 2018

   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Media Types and Content-Format Numbers  . . . . . . . . . . .   3
   3.  Procedure . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Discussion  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Latency . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.2.  Potential Mishaps . . . . . . . . . . . . . . . . . . . .   4
       4.2.1.  Race Conditions . . . . . . . . . . . . . . . . . . .   4
       4.2.2.  Depletion of Pre-Registration Space . . . . . . . . .   5
   5.  Instructions to the Designated Expert . . . . . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   To identify representation formats in a concise form, the Constrained
   Application Protocol (CoAP) uses numeric identifiers, the Content-
   Format Numbers [RFC7252].  A Content-Format number identifies a media
   type [RFC6838] and a content coding (usually the identity coding).
   Content-Format numbers are assigned in the CoAP Content-Formats
   Registry, as defined in Section 12.3 of [RFC7252].

   At the time of writing, a couple dozen Content-Format numbers are
   registered.  Any new application that needs to register new media
   types for use with CoAP can define the Content-Format numbers for its
   media types as well.  However, using existing applications and their
   media types over CoAP is complicated by the need to register the
   Content-Format numbers for these media types.

   As of 2018, less than 2000 media types have been registered in the
   Media Type Registry managed by [RFC6838], in a registry established
   by [RFC1590] in 1994.  No trends significantly accelerating the
   growth of this registry are currently anticipated.

Bormann & Hartke         Expires January 1, 2019                [Page 2]
Internet-Draft  Proactively Assigning Content-Format IDs       June 2018
Show full document text