RFC 4356 on Mapping Between the Multimedia Messaging Service (MMS) and Internet Mail

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



A new Request for Comments is now available in online RFC libraries.


        RFC 4356

        Title:      Mapping Between the Multimedia Messaging Service
                    (MMS) and Internet Mail
        Author(s):  R. Gellens
        Status:     Standards Track
        Date:       January 2006
        Mailbox:    randy@qualcomm.com
        Pages:      31
        Characters: 69427
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-lemonade-mms-mapping-06.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4356.txt


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.

This document is a product of the Enhancements to Internet email to
support diverse service environments Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
<ftp://ftp.isi.edu/in-notes/rfc4356.txt>
_______________________________________________

IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux