RFC 8081: The "font" Top-Level Media Type
In plain English — editorial summary, not part of the RFC
This memo serves to register and document the "font" top-level media type, under which subtypes for representation formats for fonts may be registered. This document also serves as a registration application for a set of intended subtypes, which are representative of some existing subtypes already in use, and currently registered under the "application" tree by their separate registrations.
Document record
- Document ID
- RFC8081
- Published
- February 2017
- Authors
- C. Lilley
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8255Multiple Language Content TypeCurrent
October 2017
- RFC 6657Update to MIME regarding "charset" Parameter Handling in Textual Media TypesCurrent
July 2012
- RFC 6522The Multipart/Report Media Type for the Reporting of Mail System Administrative MessagesUpdated
January 2012
- RFC 9996Media Types for Protocol BuffersCurrent
July 2026
- RFC 3335MIME-based Secure Peer-to-Peer Business Data Interchange over the InternetCurrent
September 2002
- RFC 9078Reaction: Indicating Summary Reaction to a MessageCurrent
August 2021
- RFC 6922The application/sql Media TypeCurrent
April 2013
- RFC 9787Guidance on End-to-End Email SecurityCurrent
August 2025
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?