Internet-Draft Obsoleting the Concept of Media Type Suf February 2025
Thomson & Nottingham Expires 6 August 2025 [Page]
Workgroup:
Media Type Maintenance
Internet-Draft:
draft-mnt-mediaman-plus-minus-latest
Updates:
6838 (if approved)
Published:
Intended Status:
Best Current Practice
Expires:
Authors:
M. Thomson
Mozilla
M. Nottingham
Cloudflare

Obsoleting the Concept of Media Type Suffixes

Abstract

The use of a '+' character in media types was originally used to define media sub-types. The use of media type suffixes were never clearly defined.

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://martinthomson.github.io/mediaman-plus-minus/draft-mnt-mediaman-plus-minus.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-mnt-mediaman-plus-minus/.

Discussion of this document takes place on the Media Type Maintenance Working Group mailing list (mailto:media-types@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/media-types/. Subscribe at https://www.ietf.org/mailman/listinfo/media-types/.

Source for this draft and an issue tracker can be found at https://github.com/martinthomson/mediaman-plus-minus.

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 6 August 2025.

Table of Contents

1. The '+' Character Has No Special Meaning in a Media Type

2. Consequences of Interpreting Media Types By Suffix

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

4. Security Considerations

The potential for a piece of content to be interpreted in multiple ways can create security problems.

5. IANA Considerations

This document has no IANA actions.

6. Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/rfc/rfc2119>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/rfc/rfc8174>.

Acknowledgments

TODO acknowledge.

Authors' Addresses

Martin Thomson
Mozilla
Mark Nottingham
Cloudflare