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

Document Type Active Internet-Draft (individual)
Last updated 2020-08-18
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                          18 August 2020
Expires: 19 February 2021

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

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 19 February 2021.

Copyright Notice

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

Bormann                 Expires 19 February 2021                [Page 1]
Internet-Draft                Content-Types                  August 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Media-Type  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Content-Type  . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Content-Coding  . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Content-Format  . . . . . . . . . . . . . . . . . . . . . . .   5
   6.  Abbreviations . . . . . . . . . . . . . . . . . . . . . . . .   5
   7.  Discussion  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   6
     10.2.  Informative References . . . . . . . . . . . . . . . . .   6
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   [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).

                 type-name = reg-name
                 subtype-name = reg-name

                 reg-name = 1*127reg-name-chars
                 reg-name-chars = ALPHA / DIGIT / "!" /
                                  "#" / "$" / "&" / "." /
                                  "+" / "-" / "^" / "_"

             Figure 1: ABNF for type and subtype, from RFC 4288

   [RFC4288] contains the semantically equivalent ABNF in Figure 2,
   which also provides comments that limit the use of "." and "+".

Bormann                 Expires 19 February 2021                [Page 2]
Internet-Draft                Content-Types                  August 2020

   type-name = restricted-name
   subtype-name = restricted-name

   restricted-name = restricted-name-first *126restricted-name-chars
   restricted-name-first  = ALPHA / DIGIT
   restricted-name-chars  = ALPHA / DIGIT / "!" / "#" /
                            "$" / "&" / "-" / "^" / "_"
   restricted-name-chars =/ "." ; Characters before first dot always
                                ; specify a facet name
   restricted-name-chars =/ "+" ; Characters after last plus always
                                ; specify a structured syntax suffix
Show full document text