Media Type Maintenance M. Thomson Internet-Draft Mozilla Updates: 6838 (if approved) M. Nottingham Intended status: Best Current Practice Cloudflare Expires: 6 August 2025 2 February 2025 Obsoleting the Concept of Media Type Suffixes draft-mnt-mediaman-plus-minus-latest 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. 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. The '+' Character Has No Special Meaning in a Media Type 2. Consequences of Interpreting Media Types By Suffix 3. Conventions and Definitions 4. Security Considerations 5. IANA Considerations 6. Normative References Acknowledgments Authors' Addresses 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, March 1997, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . Acknowledgments TODO acknowledge. Authors' Addresses Martin Thomson Mozilla Email: mt@lowentropy.net Mark Nottingham Cloudflare Email: mnot@mnot.net