RFC 4356: Mapping Between the Multimedia Messaging Service (MMS) and Internet Mail
In plain English — editorial summary, not part of the RFC
The cellular telephone industry has defined a service known as the Multimedia Messaging Service (MMS). This service uses formats and protocols that are similar to, but differ in key ways from, those used in Internet mail. One important difference between MMS and Internet Mail is that MMS uses headers that start with "X-Mms-" to carry a variety of user agent- and server-related information elements. This document specifies how to exchange messages between these two services, including mapping information elements as used in MMS X-Mms-* headers as well as delivery and disposition reports, to and from that used in SMTP and Internet message headers. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4356
- Published
- January 2006
- Authors
- R. Gellens
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 31
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4280Dynamic Host Configuration Protocol (DHCP) Options for Broadcast and Multicast Control ServersCurrent
December 2005
- RFC 4331Quota and Size Properties for Distributed Authoring and Versioning (DAV) CollectionsCurrent
February 2006
- RFC 4326Unidirectional Lightweight Encapsulation (ULE) for Transmission of IP Datagrams over an MPEG-2 Transport Stream (TS)Updated
December 2005
- RFC 4314IMAP4 Access Control List (ACL) ExtensionCurrent
December 2005
- RFC 4416Goals for Internet Messaging to Support Diverse Service EnvironmentsCurrent
February 2006
- RFC 4287The Atom Syndication FormatUpdated
December 2005
- RFC 4437Web Distributed Authoring and Versioning (WebDAV) Redirect Reference ResourcesCurrent
March 2006
- RFC 4259A Framework for Transmission of IP Datagrams over MPEG-2 NetworksCurrent
December 2005
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?