On Media-Types, Content-Types, and related terminology
draft-bormann-core-media-content-type-format-04

Document Type Active Internet-Draft (individual)
Authors Carsten Bormann  , Henk Birkholz 
Last updated 2021-02-22
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) htmlized 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)
Network Working Group                                         C. Bormann
Internet-Draft                                    Universit├Ąt Bremen TZI
Intended status: Standards Track                             H. Birkholz
Expires: 26 August 2021                                   Fraunhofer SIT
                                                        22 February 2021

         On Media-Types, Content-Types, and related terminology
            draft-bormann-core-media-content-type-format-04

Abstract

   There is a lot of confusion about media-types, content-types, and
   related terminology.

   This memo is an attempt at clearing it up, so we can use consistent
   terminology in CoRE and related specifications.  It also defines some
   ABNF that can be used in these specifications.

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 26 August 2021.

Copyright Notice

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

Bormann & Birkholz       Expires 26 August 2021                 [Page 1]
Internet-Draft                Content-Types                February 2021

   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 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
   2.  Media-Type  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Content-Type  . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Content-Coding  . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Content-Format  . . . . . . . . . . . . . . . . . . . . . . .   5
   6.  Remaining ABNF  . . . . . . . . . . . . . . . . . . . . . . .   6
   7.  Abbreviations . . . . . . . . . . . . . . . . . . . . . . . .   6
   8.  Discussion  . . . . . . . . . . . . . . . . . . . . . . . . .   7
   9.  Suggested usage . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  COSE  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.2.  SenML . . . . . . . . . . . . . . . . . . . . . . . . . .   8
     9.3.  ... . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   11. Security Considerations . . . . . . . . . . . . . . . . . . .   8
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     12.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     12.2.  Informative References . . . . . . . . . . . . . . . . .   8
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   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.

   [RFC1590] introduced media types and their registration.  That
   document took MIME types from [RFC1521] and gave them a new name.  At
   that time, the term "media type" was often used just for the major
   type ("text", "audio"), and what we call a media-type now was the
   combination of a type and a subtype.  This lives on in [RFC6838],
   which does not even have an ABNF [RFC5234] production for media type.
   [RFC6838]'s predecessor, [RFC4288], supplied the ABNF shown in
   (Figure 1).

Bormann & Birkholz       Expires 26 August 2021                 [Page 2]
Internet-Draft                Content-Types                February 2021

   |               type-name = reg-name
   |               subtype-name = reg-name
   |  
   |               reg-name = 1*127reg-name-chars
   |               reg-name-chars = ALPHA / DIGIT / "!" /
   |                                "#" / "$" / "&" / "." /
Show full document text