Mapping Between the Multimedia Messaging Service (MMS) and Internet Mail
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 31
- Abstract
- 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]
- Publication Date
- 2006-01-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC4356- Link
- https://doi.org/10.17487/RFC4356
- Author(s)
- Randall Gellens
- Keyword(s)
- Cellular Telephone
Latest version of IETF RFC 4356
Document Versions — IETF RFC 4356
-
▶ IETF RFC 4356 (2006-01-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- OMA specifications are available at the OMA web site < http://www.openmobilealliance.org >. EXTERNAL
- "MMS MM1 Stage 3 using OMA/WAP", X.S0016-310 EXTERNAL
- "Multimedia Messaging Service: Functional description; Stage 2", TS 23.140 Release 5. EXTERNAL
- "MMS MM4 Stage 3 Inter-Carrier Interworking", X.S0016- 340 EXTERNAL
- OMA-WAP-MMS-ENC-V1_2-20040323-C EXTERNAL
- 3GPP specifications are available at the 3GPP (Third Generation Partnership Project) web site < http://www.3gpp.org > EXTERNAL
- 3GPP2 specifications are available at the 3GPP2 (Third Generation Partnership Project 2) web site < http://www.3gpp2.org >. EXTERNAL
- IETF RFC 2047 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 2616 [Superseded*]
- IETF RFC 2821 [Superseded*]
- IETF RFC 2822 [Superseded*]
- IETF RFC 3461 [Active*]
- IETF RFC 3462 [Superseded*]
- IETF RFC 3463 [Active*]
- IETF RFC 3464 [Active*]
- IETF RFC 3490 [Superseded*]
- IETF RFC 3798 [Superseded*]
Bibliographic Reference(s)
- "Multimedia Messaging Service (MMS); Stage 2", Functional Specification, April 2003, X.S0016-200. EXTERNAL
- "Multimedia Messaging Services (MMS); Stage 1", Requirements, October 2002, S.R0064-0. EXTERNAL
- "Multimedia Messaging Service; Media formats and codecs", TS26.140Release 5. EXTERNAL
- "Multimedia Messaging Services (MMS) Overview", X.S0016-000 EXTERNAL
- IETF RFC 2076 [Active*]
- IETF RFC 2476 [Superseded*]
- IETF RFC 2480 [Active*]
- IETF RFC 2852 [Active*]
- IETF RFC 3030 [Active*]
- IETF RFC 3156 [Active*]
- IETF RFC 3801 [Active*]
- IETF RFC 3851 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4356.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4356, Mapping Between the Multimedia Messaging Service (MMS) and Internet Mail. Available at https://doi.org/10.17487/RFC4356
Snippet:
IETF RFC 4356, Mapping Between the Multimedia Messaging Service (MMS) and Internet Mail. Available at https://doi.org/10.17487/RFC4356
HTML (ISO 690 compliant)
Preview:
IETF RFC 4356, Mapping Between the Multimedia Messaging Service (MMS) and Internet Mail. Available at https://doi.org/10.17487/RFC4356
Snippet:
<span class="citation"><cite>IETF RFC 4356</cite>, Mapping Between the Multimedia Messaging Service (MMS) and Internet Mail. Available at <a href="https://doi.org/10.17487/RFC4356" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4356</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4356, Mapping Between the Multimedia Messaging Service (MMS) and Internet Mail
doi: 10.17487/RFC4356
url: https://doi.org/10.17487/RFC4356
doi: 10.17487/RFC4356
url: https://doi.org/10.17487/RFC4356
Snippet:
<li> <cite id="bib-rfc4356">IETF RFC 4356</cite>, Mapping Between the Multimedia Messaging Service (MMS) and Internet Mail <span class="doi">10.17487/RFC4356</span> </li>
Referenced By
- IETF RFC 4355 [Active*]
- IETF RFC 5598 [Active*]