RFC 8255: Multiple Language Content Type
In plain English — editorial summary, not part of the RFC
This document defines the 'multipart/multilingual' content type, which is an addition to the Multipurpose Internet Mail Extensions (MIME) standard. This content type makes it possible to send one message that contains multiple language versions of the same information. The translations would be identified by a language tag and selected by the email client based on a user's language settings.
Document record
- Document ID
- RFC8255
- Published
- October 2017
- Authors
- N. Tomkinson; N. Borenstein
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2077The Model Primary Content Type for Multipurpose Internet Mail ExtensionsUpdated
January 1997
- RFC 9078Reaction: Indicating Summary Reaction to a MessageCurrent
August 2021
- RFC 5598Internet Mail ArchitectureCurrent
July 2009
- RFC 5068Email Submission Operations: Access and Accountability RequirementsUpdated
November 2007
- RFC 2111Content-ID and Message-ID Uniform Resource LocatorsObsoleted
March 1997
- RFC 1894An Extensible Message Format for Delivery Status NotificationsObsoleted
January 1996
- RFC 1867Form-based File Upload in HTMLObsoleted
November 1995
- RFC 1544The Content-MD5 Header FieldObsoleted
November 1993
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?