draft-ietf-lemonade-mms-mapping-04.txt   draft-ietf-lemonade-mms-mapping-05.txt 
Internet Draft: Mapping Between MMS and Internet Mail R. Gellens Internet Draft: Mapping Between MMS and Internet Mail R. Gellens
Document: draft-ietf-lemonade-mms-mapping-04.txt Qualcomm Document: draft-ietf-lemonade-mms-mapping-05.txt Qualcomm
Expires: November 2005 May 2005 Expires: March 2006 September 2005
Mapping Between the Multimedia Messaging Service (MMS) Mapping Between the Multimedia Messaging Service (MMS)
and Internet Mail and Internet Mail
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
By submitting this Internet-Draft, I accept the provisions of
Section 3 of RFC 3667 (BCP 78).
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
skipping to change at line 45 skipping to change at line 42
Copyright (C) The Internet Society (2005). All Rights Reserved. Copyright (C) The Internet Society (2005). All Rights Reserved.
Abstract Abstract
The cellular telephone industry has defined a service known as the The cellular telephone industry has defined a service known as the
Multimedia Messaging Service (MMS). This service uses formats and Multimedia Messaging Service (MMS). This service uses formats and
protocols which are similar to, but differ in key ways from, those protocols which are similar to, but differ in key ways from, those
used in Internet mail. used in Internet mail.
Gellens [Page 1] Expires November 2005 Gellens [Page 1] Expires March 2006
One important difference between MMS and Internet Mail is that MMS
uses headers which 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 This document specifies how to exchange messages between these two
services, including mapping information elements as used in MMS services, including mapping information elements as used in MMS
X-Mms-* headers as well as delivery and disposition reports, to and X-Mms-* headers as well as delivery and disposition reports, to and
from that used in ESMTP and Internet message headers. from that used in SMTP and Internet message headers.
Gellens [Page 2] Expires November 2005 Gellens [Page 2] Expires March 2006
Table of Contents Table of Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Conventions Used in this Document . . . . . . . . . . . . 3 1.1 Conventions Used in this Document . . . . . . . . . . . . 3
1.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3 Definitions . . . . . . . . . . . . . . . . . . . . . . . 4 1.3 Definitions . . . . . . . . . . . . . . . . . . . . . . . 4
1.4 Abbreviations . . . . . . . . . . . . . . . . . . . . . . 5 1.4 Abbreviations . . . . . . . . . . . . . . . . . . . . . . 5
1.5 Assumptions . . . . . . . . . . . . . . . . . . . . . . . 6 1.5 Assumptions . . . . . . . . . . . . . . . . . . . . . . . 6
2 Mapping Between MMS and Internet Mail . . . . . . . . . . . . 6 2 Mapping Between MMS and Internet Mail . . . . . . . . . . . . 6
2.1 Mapping Specification . . . . . . . . . . . . . . . . . . 6 2.1 Mapping Specification . . . . . . . . . . . . . . . . . . 6
2.1.1 MMS to Internet Mail . . . . . . . . . . . . . . . . . 6 2.1.1 MMS to Internet Mail . . . . . . . . . . . . . . . . . 6
2.1.2 Internet Mail to MMS . . . . . . . . . . . . . . . . 7 2.1.2 Internet Mail to MMS . . . . . . . . . . . . . . . . 7
2.1.3 MMS Information Element Mappings . . . . . . . . . . . 7 2.1.3 MMS Information Element Mappings . . . . . . . . . . . 7
2.1.3.1 Table 1: MM3 Mappings . . . . . . . . . . . . . . 8 2.1.3.1 Table 1: MM3 Mappings . . . . . . . . . . . . . . 8
2.1.3.2 Conversion of messages from MMS to Internet format 10 2.1.3.2 Conversion of messages from MMS to Internet format 10
2.1.3.2.1 Table 2: Importance Mappings (MMS to Internet 14 2.1.3.2.1 Table 2: Importance Mappings (MMS to Internet 13
2.1.3.2.2 Table 3: X-Priority Mappings (MMS to Internet 14 2.1.3.2.2 Table 3: X-Priority Mappings (MMS to Internet 14
2.1.3.3 Conversion of messages from Internet to MMS format 16 2.1.3.3 Conversion of messages from Internet to MMS format 16
2.1.3.3.1 Table 4: Priority Mappings (Internet Message t 18 2.1.3.3.1 Table 4: Priority Mappings (Internet Message t 18
2.1.4 Report Generation and Conversion . . . . . . . . . . 20 2.1.4 Report Generation and Conversion . . . . . . . . . . 19
2.1.4.1 Delivery Report Mapping from MMS to Internet Messa 20 2.1.4.1 Delivery Report Mapping from MMS to Internet Messa 20
2.1.4.1.1 Table 5: Delivery Report Mappings (MMS to Inte 21 2.1.4.1.1 Table 5: Delivery Report Mappings (MMS to Inte 20
2.1.4.2 Delivery Report Mapping from Internet Message to M 22 2.1.4.2 Delivery Report Mapping from Internet Message to M 21
2.1.4.2.1 Table 6: Delivery Report Mappings (Internet Me 23 2.1.4.2.1 Table 6: Delivery Report Mappings (Internet Me 22
2.1.4.3 Read Report Mapping from MMS to Internet Message . 24 2.1.4.3 Read Report Mapping from MMS to Internet Message . 23
2.1.4.3.1 Table 7: Read Report Mappings (MMS to Internet 25 2.1.4.3.1 Table 7: Read Report Mappings (MMS to Internet 24
2.1.4.4 Disposition Report Mapping from Internet Message t 26 2.1.4.4 Disposition Report Mapping from Internet Message t 25
2.1.4.4.1 Table 8: Disposition Report Mappings (Internet 26 2.1.4.4.1 Table 8: Disposition Report Mappings (Internet 25
2.1.5 Message Delivery . . . . . . . . . . . . . . . . . . . 27 2.1.5 Message Delivery . . . . . . . . . . . . . . . . . . . 26
3 Security Considerations . . . . . . . . . . . . . . . . . . . 27 3 Security Considerations . . . . . . . . . . . . . . . . . . . 26
4 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 4 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
5 Normative References . . . . . . . . . . . . . . . . . . . . 29 5 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 27
6 Informative References . . . . . . . . . . . . . . . . . . . . 30 6 Normative References . . . . . . . . . . . . . . . . . . . . . 27
7 Author's Address . . . . . . . . . . . . . . . . . . . . . . 31 7 Informative References . . . . . . . . . . . . . . . . . . . 28
Intellectual Property Statement . . . . . . . . . . . . . . . . 32 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 29
Full Copyright Statement . . . . . . . . . . . . . . . . . . . 32 Appendix A: Changes Since Last Version . . . . . . . . . . . . 30
Intellectual Property Statement . . . . . . . . . . . . . . . . 30
Full Copyright Statement . . . . . . . . . . . . . . . . . . . 31
1 Introduction 1 Introduction
1.1 Conventions Used in this Document 1.1 Conventions Used in this Document
The key words "REQUIRED", "MUST", "MUST NOT", "SHOULD", "SHOULD The key words "REQUIRED", "MUST", "MUST NOT", "SHOULD", "SHOULD
NOT", and "MAY" in this document are to be interpreted as described NOT", and "MAY" in this document are to be interpreted as described
in "Key words for use in RFCs to Indicate Requirement Levels" in "Key words for use in RFCs to Indicate Requirement Levels"
[KEYWORDS]. [KEYWORDS].
Gellens [Page 3] Expires November 2005 Gellens [Page 3] Expires March 2006
Note that in the text of this document, a distinction is made
between use of "SMTP" or "Simple Mail Transfer Protocol", and
"ESMTP" or "Extended Simple Mail Transfer Protocol": when the term
"ESMTP" or "Extended" is used, it indicates use of extended features
of SMTP; that is, those beyond the facilities of RFC 821. (These
extended facilities may be in RFC 2821 or in other RFCs, as
indicated by the specific RFC reference used; note that the name of
the RFC 2821 reference is "SMTP" because that is the official title
of the RFC.)
1.2 Scope 1.2 Scope
This document describes how to exchange messages between MMS systems This document describes how to exchange messages between MMS systems
(as defined by 3GPP/3GPP2/OMA) and Internet mail systems (that is, (as defined by 3GPP/3GPP2/OMA) and Internet mail systems (that is,
[SMTP] and [Msg-Fmt]). This includes the translation of message [SMTP] and [Msg-Fmt]). This includes the translation of message
formats, message header elements, message delivery reports and formats, message header elements, message delivery reports and
message disposition reports ([DSN-Msg] and [MDN]). message disposition reports ([DSN-Msg] and [MDN]).
The MMS architecture [Stage_2] and specifications [Stage_3] refer to The MMS architecture [Stage_2] and specifications [Stage_3] refer to
interfaces as reference points named MMx. For example, MM1 is the interfaces as reference points named MMx. For example, MM1 is the
client-server interface, MM4 is the server-server interface, and MM3 client-server interface, MM4 is the server-server interface, and MM3
is an interface to "external" or non-MMS systems. The specification is an interface to "external" or non-MMS systems. The specification
in this document can be used for message exchange between any system in this document can be used for message exchange between any system
which uses Internet Message formats and protocols and an MMS system; which uses Internet Message formats and protocols and an MMS system;
from the perspective of the MMS system, reference point MM3 is used. from the perspective of the MMS system, reference point MM3 is used.
This document includes support for voice messages specified by the This document includes support for voice messages specified by the
Voice Profile for Internet Mail [VPIM]. The VPIM specification Voice Profile for Internet Mail [VPIM]. The VPIM specification
allows voice messages to be exchanged between voice mail systems allows voice messages to be exchanged between voice mail systems
using Internet mail format [Msg-Fmt] and transported via Extended using Internet mail format [Msg-Fmt] and transported via [SMTP].
Simple Mail Transfer Protocol [SMTP]. Thus, the MMS MM3 interface Thus, the MMS MM3 interface supports the ability to exchange voice
supports the ability to exchange voice messages between an MMS messages between an MMS system and a voice mail system. Note that
system and a voice mail system. Note that such use is distinct from such use is distinct from voice media being part of a user-composed
voice media being part of a user-composed multimedia message. multimedia message.
Note that MM3 can also be used for interworking with "external" Note that MM3 can also be used for interworking with "external"
(non-MMS) systems other than Internet mail, such as Short Messaging (non-MMS) systems other than Internet mail, such as Short Messaging
Service (SMS) and access to external mail stores (such as a voice Service (SMS) and access to external mail stores (such as a voice
mail system). This specification does not address these other uses mail system). This specification does not address these other uses
or sub-interfaces of MM3; it is only concerned with Internet mail or sub-interfaces of MM3; it is only concerned with Internet mail
interworking and specifically exchange of messages. interworking and specifically exchange of messages.
All MM3 Stage 2 [Stage_2] functions are supported except for reply All MM3 Stage 2 [Stage_2] functions are supported except for reply
charging and sender address hiding, which may be addressed in future charging and sender address hiding.
extensions.
Gellens [Page 4] Expires November 2005
1.3 Definitions 1.3 Definitions
--------------------|---------------------------------------------- --------------------|----------------------------------------------
Anonymous Remailer |A service which accepts messages and resends Body |The portion of an [SMTP] message's Content
|them to their intended recipient, masking
|information about the original sender.
--------------------|----------------------------------------------
Body |The portion of an SMTP message's Content
|following the Header (that is, following the |following the Header (that is, following the
|first blank line). The Body may contain |first blank line). The Body may contain
|structured parts and sub-parts, each of which |structured parts and sub-parts, each of which
|may have their own Header and Body. The Body |may have their own Header and Body. The Body
|contains information intended for the message |contains information intended for the message
|recipient (human or software). |recipient (human or software).
--------------------|---------------------------------------------- --------------------|----------------------------------------------
Content |The portion of an SMTP message that is Content |The portion of an SMTP message that is
|delivered. The Content consists of a Header |delivered. The Content consists of a Header
Gellens [Page 4] Expires March 2006
|and a Body. |and a Body.
--------------------|---------------------------------------------- --------------------|----------------------------------------------
Disposition Report |Feedback information to an originator User Disposition Report |Feedback information to an originator User
|Agent by a recipient User Agent about |Agent by a recipient User Agent about
Message Disposition |handling of an original message. This may Message Disposition |handling of an original message. This may
Notification |include notification that the message was or Notification |include notification that the message was or
|was not read, was deleted unread, etc. |was not read, was deleted unread, etc.
--------------------|---------------------------------------------- --------------------|----------------------------------------------
Envelope |The portion of an SMTP message not included in Envelope |The portion of an SMTP message not included in
|the Content; that is, not in the Header nor in |the Content; that is, not in the Header nor in
skipping to change at line 186 skipping to change at line 175
|while the message is in transit, and contains |while the message is in transit, and contains
|information used by SMTP agents (MTAs). |information used by SMTP agents (MTAs).
--------------------|---------------------------------------------- --------------------|----------------------------------------------
Header |The first part of an SMTP message's Content. Header |The first part of an SMTP message's Content.
|The Header is separated from the Body by a |The Header is separated from the Body by a
|blank line. The Header consists of Fields |blank line. The Header consists of Fields
|(such as "To:"), also known as Header Fields |(such as "To:"), also known as Header Fields
|or Headers. The message Header contains |or Headers. The message Header contains
|information used by User Agents. |information used by User Agents.
--------------------|---------------------------------------------- --------------------|----------------------------------------------
Gateway Function |An agent which acts as both MMSC and MTA Gateway |See [SMTP], Section 2.3.8.
|and/or MSA.
--------------------|---------------------------------------------- --------------------|----------------------------------------------
User Agent |An MMS or Email user agent User Agent |An MMS or Email user agent
--------------------|---------------------------------------------- --------------------|----------------------------------------------
Gellens [Page 5] Expires November 2005 Gellens [Page 5] Expires March 2006
1.4 Abbreviations 1.4 Abbreviations
--------|---------------------------------------------------------- --------|----------------------------------------------------------
ESMTP |Extended Simple Mail Transfer Protocol. The use of
|features and capabilities added to SMTP since RFC 821.
--------|----------------------------------------------------------
MSA |Message Submission Agent. A server which accepts messages MSA |Message Submission Agent. A server which accepts messages
|from User Agents and processes them; either delivering |from User Agents and processes them; either delivering
|them locally or relaying to an MTA. |them locally or relaying to an MTA.
--------|---------------------------------------------------------- --------|----------------------------------------------------------
MTA |Mail Transfer Agent. A server which implements [SMTP]. MTA |Mail Transfer Agent. A server which implements [SMTP].
--------|---------------------------------------------------------- --------|----------------------------------------------------------
1.5 Assumptions 1.5 Assumptions
It is assumed that the reader is already familiar with the contents It is assumed that the reader is already familiar with the contents
of the 3GPP2 MMS Specification Overview [Overview], MMS Stage 1 of the 3GPP2 MMS Specification Overview [Overview], MMS Stage 1
(requirements) [Stage_1] and Stage 2 (architecture and abstract (requirements) [Stage_1] and Stage 2 (architecture and abstract
messages) [Stage_2], and 3GPP/3GPP2 Stage 3 (protocols) [Stage_3] messages) [Stage_2], and 3GPP/3GPP2 Stage 3 (protocols) [Stage_3]
documents. It is also assumed that the reader is familiar with documents. It is also assumed that the reader is familiar with
Internet mail, especially RFC 2821 [SMTP] and RFC 2822 [Msg-Fmt]. Internet mail, especially RFC 2821 [SMTP] and RFC 2822 [Msg-Fmt].
2 Mapping Between MMS and Internet Mail 2 Mapping Between MMS and Internet Mail
This section defines the interworking between MMS Relay/Servers and This section defines the interworking between MMS Relay/Servers and
External Servers using native ESMTP. That is, information elements External Servers using native [SMTP]. That is, information elements
are exchanged using standard Internet Message [Msg-Fmt] header are exchanged using standard Internet Message [Msg-Fmt] header
fields and standard [SMTP] elements. fields and standard [SMTP] elements.
SMTP and Internet mail extensions are used for features such as SMTP and Internet mail extensions are used for features such as
delivery reports, message expiration, discovery of server support delivery reports, message expiration, discovery of server support
for optional features, etc. for optional features, etc.
2.1 Mapping Specification 2.1 Mapping Specification
2.1.1 MMS to Internet Mail 2.1.1 MMS to Internet Mail
When sending a message to an Internet mail system the MMS When sending a message to an Internet mail system the MMS
Relay/Server MUST convert the MM if required, and MUST comply with Relay/Server MUST convert the MM if required, and MUST comply with
the requirements of [SMTP] (for example, use of a null return-path the requirements of [SMTP].
for automatically-generated messages).
The MMS Relay/Server SHOULD use the information elements associated The MMS Relay/Server SHOULD use the information elements associated
with the MM to define the control information (Internet Message with the MM to define the control information (Internet Message
header fields and ESMTP values) needed for the transfer protocol. header fields and SMTP envelope values) needed for the transfer
protocol.
Gellens [Page 6] Expires November 2005 Gellens [Page 6] Expires March 2006
Section 2.1.3 lists the mappings between X-Mms-* headers and Section 2.1.3 lists the mappings between X-Mms-* headers and
Internet Message header fields and ESMTP values. Internet Message header fields and SMTP values.
Delivery and read report MMs SHOULD be converted to standard Delivery and read report MMs SHOULD be converted to standard
Internet Message report format (multipart/report). In addition to Internet Message report format (multipart/report). In addition to
converting Internet Message reports, the MMS Relay/Server MUST converting Internet Message reports, the MMS Relay/Server MUST
generate delivery and read report MMs for received messages as generate delivery and read report MMs for received messages as
appropriate. See section 2.1.4 for more information. appropriate. See section 2.1.4 for more information.
2.1.2 Internet Mail to MMS 2.1.2 Internet Mail to MMS
When receiving a message from an Internet mail system the MMS When receiving a message from an Internet mail system the MMS
Relay/Server MAY convert incoming messages to the MM format used Relay/Server MAY convert incoming messages to the MM format used
within the receiving system. within the receiving system.
The MMS Relay/Server MAY convert control information received from The MMS Relay/Server MAY convert control information received from
the Internet mail server into appropriate information elements of an the Internet mail server into appropriate information elements of an
MM. MM.
Section 2.1.3 lists the mappings between X-Mms-* headers and Section 2.1.3 lists the mappings between X-Mms-* headers and
Internet Message header fields and ESMTP values. Internet Message header fields and SMTP values.
Standard Internet Message report format (multipart/report) messages Standard Internet Message report format (multipart/report) messages
MAY be converted to delivery or read report MMs, as appropriate. In MAY be converted to delivery or read report MMs, as appropriate. In
addition to converting report MMs, the MMS Relay/Server MUST addition to converting report MMs, implementations conforming to
generate standard Internet Message delivery and disposition reports this document MUST generate standard Internet Message delivery and
for received Internet messages as appropriate. See section 2.1.4 disposition reports for received Internet messages as appropriate.
for more information. See section 2.1.4 for more information.
Gellens [Page 7] Expires November 2005 Gellens [Page 7] Expires March 2006
2.1.3 MMS Information Element Mappings 2.1.3 MMS Information Element Mappings
The mappings between MMS elements and ESMTP/Internet Message The mappings between MMS elements and SMTP/Internet Message elements
elements (either [SMTP] parameters, [Msg-Fmt] headers, or both) are (either [SMTP] parameters, [Msg-Fmt] headers, or both) are
summarized in the table below, and detailed in subsequent sections. summarized in the table below, and detailed in subsequent sections.
The "MMS Headers" are from [OMA-MMS]. Note that only information The "MMS Headers" are from [OMA-MMS]. Note that only information
elements which need to be mapped are listed. [Msg-Fmt] headers not elements which need to be mapped are listed. [Msg-Fmt] headers not
listed here SHOULD be passed unaltered listed here SHOULD be passed unaltered
2.1.3.1 Table 1: MM3 Mappings 2.1.3.1 Table 1: MM3 Mappings
=================|=================|================|============== =================|=================|================|==============
Information Elem |[SMTP] Element |[Msg-Fmt] Header|MMS Header Information Elem |[SMTP] Element |[Msg-Fmt] Header|MMS Header
=================|=================|================|============== =================|=================|================|==============
3GPP MMS Version |N/A |N/A |X-Mms-3GPP-MMS 3GPP MMS Version |N/A |N/A |X-Mms-3GPP-MMS
| | | -Version: | | | -Version:
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Message Type |N/A |N/A |X-Mms-Message- Message Type |N/A |N/A |X-Mms-Message-
(of PDU) | | | Type: (of PDU) | | | Type:
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Transaction ID |N/A |N/A |X-Mms-Transact Transaction ID |N/A |N/A |X-Mms-Transact
| | | ion-Id: | | | ion-Id:
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Message ID |ENVID [DSN-SMTP] |Message-ID: |X-Mms-Message- Message ID |ENVID [DSN-SMTP] |Message-ID: |Message-ID:
| | | Id:
| | |Message-ID:
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Recipient |RCPT TO |To:, Cc:, or |To:, Cc:, Bcc: Recipient |RCPT TO |To:, Cc:, or |To:, Cc:, Bcc:
address(es) |address(es) |omitted (Bcc) | address(es) |address(es) |omitted (Bcc) |
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Sender's address |MAIL FROM |From: (MAY set |From: Sender's address |MAIL FROM |From: |From:
|address if |to locally-gen- | |address if | |
|user-originated; |erated value | |user-originated; | |
|MUST set MAIL |to hide sender | |MUST set MAIL | |
|FROM to null |identity) | |FROM to null | |
|("<>") for all | | |("<>") for all | |
|automatically- | | |automatically- | |
|generated MMs | | |generated MMs | |
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Content type |N/A |Content-Type: |Content-type: Content type |N/A |Content-Type: |Content-type:
| | | | | |
| |For voice mes- | | |For voice mes- |
| |sages compliant | | |sages compliant |
| |to [VPIM], see | | |to [VPIM], see |
| |Note 2 | | |Note 2 |
=================|=================|================|============== =================|=================|================|==============
Gellens [Page 8] Expires November 2005 Gellens [Page 8] Expires March 2006
=================|=================|================|============== =================|=================|================|==============
Information Elem |[SMTP] Element |[Msg-Fmt] Header|MMS Header Information Elem |[SMTP] Element |[Msg-Fmt] Header|MMS Header
=================|=================|================|============== =================|=================|================|==============
Message class |Class=auto: |MAY set 'Prece |X-Mms-Message- Message class |Class=auto: |MAY set 'Prece |X-Mms-Message-
|MUST set MAIL | dence: bulk' | Class: |MUST set MAIL | dence: bulk' | Class:
|FROM to null |on class=auto | |FROM to null |on class=auto |
|("<>"). | | |("<>"). | |
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Date and time |N/A |Date: |Date: Date and time |N/A |Date: |Date:
of submission | | | of submission | | |
skipping to change at line 346 skipping to change at line 329
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Delivery report |DSN [DSN-SMTP] |N/A |X-Mms-Delivery Delivery report |DSN [DSN-SMTP] |N/A |X-Mms-Delivery
request |SHOULD also | | -Report: request |SHOULD also | | -Report:
|specify recip- | | |specify recip- | |
|ient address as | | |ient address as | |
|ORCPT; SHOULD | | |ORCPT; SHOULD | |
|also specify | | |also specify | |
|ENVID | | |ENVID | |
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Importance (a/k/a|N/A |Importance: |X-Mms- Importance (a/k/a|N/A |Importance: |X-Mms-
"priority") | |X-Priority: | Priority: "priority") | | | Priority:
| | | | | |
| | | | | |
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Sender visib- |N/A |N/A |X-Mms-Sender- Sender visib- |(not currently |(not currently |X-Mms-Sender-
ility | | | Visibility: ility |supported) |supported) | Visibility:
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Read reply |N/A |Disposition- |X-Mms-Read- Read reply |N/A |Disposition- |X-Mms-Read-
request | | Notification | Reply: request | | Notification | Reply:
| | -To: [MDN] | | | -To: [MDN] |
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Reply-charging |(not currently |(not currently |X-Mms-Reply- Reply-charging |(not currently |(not currently |X-Mms-Reply-
permission |supported) |supported) | Charging: permission |supported) |supported) | Charging:
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Reply-charging |(not currently |(not currently |X-Mms-Reply- Reply-charging |(not currently |(not currently |X-Mms-Reply-
permission |supported) |supported) | Charging- permission |supported) |supported) | Charging-
deadline | | | Deadline: deadline | | | Deadline:
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Reply-charging |(not currently |(not currently |X-Mms-Reply- Reply-charging |(not currently |(not currently |X-Mms-Reply-
permission |supported) |supported) | Charging- permission |supported) |supported) | Charging-
limitation | | | Size: limitation | | | Size:
=================|=================|================|============== =================|=================|================|==============
Gellens [Page 9] Expires November 2005 Gellens [Page 9] Expires March 2006
=================|=================|================|============== =================|=================|================|==============
Information Elem |[SMTP] Element |[Msg-Fmt] Header|MMS Header Information Elem |[SMTP] Element |[Msg-Fmt] Header|MMS Header
=================|=================|================|============== =================|=================|================|==============
Reply-charging |(not currently |(not currently |X-Mms-Reply- Reply-charging |(not currently |(not currently |X-Mms-Reply-
usage request |supported) |supported) | Charging- usage request |supported) |supported) | Charging-
| | | Id: | | | Id:
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Reply-charging |(not currently |(not currently |X-Mms-Reply- Reply-charging |(not currently |(not currently |X-Mms-Reply-
usage reference |supported) |supported) | Charging: usage reference |supported) |supported) | Charging:
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Subject |N/A |Subject: |Subject: Subject |N/A |Subject: |Subject:
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Forward counter |N/A |Resent-Count: |(Not sup-
| | |ported)
_________________|_________________|________________|______________
Previously-sent- |N/A |Resent-From: |X-Mms-Previous Previously-sent- |N/A |Resent-From: |X-Mms-Previous
by | | | ly-Sent-By: by | | | ly-Sent-By:
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Previously-sent- |N/A |Resent-Date: |X-Mms- Previously-sent- |N/A |Resent-Date: |X-Mms-
date and-time | | | Previously- date and-time | | | Previously-
| | | Sent-Date: | | | Sent-Date:
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Hop/host trace |N/A |Received: |(Not sup- Hop/host trace |N/A |Received: |(Not sup-
| | |ported) | | |ported)
_________________|_________________|________________|______________ _________________|_________________|________________|______________
skipping to change at line 416 skipping to change at line 396
SHOULD NOT be sent to an MMS system. SHOULD NOT be sent to an MMS system.
Note 2: [VPIM] specifies how conforming messages are identified. Note 2: [VPIM] specifies how conforming messages are identified.
2.1.3.2 Conversion of messages from MMS to Internet format 2.1.3.2 Conversion of messages from MMS to Internet format
3GPP MMS Version 3GPP MMS Version
The 'X-Mms-3GPP-MMS-Version:' header, if present, SHOULD be removed. The 'X-Mms-3GPP-MMS-Version:' header, if present, SHOULD be removed.
Gellens [Page 10] Expires November 2005
Message Type (of PDU) Message Type (of PDU)
Gellens [Page 10] Expires March 2006
The 'X-Mms-Message-Type:' header, if present, SHOULD be removed. The 'X-Mms-Message-Type:' header, if present, SHOULD be removed.
Transaction ID Transaction ID
The 'X-Mms-Transaction-Id:' header, if present, SHOULD be removed. The 'X-Mms-Transaction-Id:' header, if present, SHOULD be removed.
Message ID Message ID
An 'X-Mms-Message-Id:' header, if present, SHOULD be retained in
order to facilitate the case where an MMS message traverses the
Internet prior to returning to an MMS system. Such systems should
be aware that X-headers might be removed during transit through
Internet MTAs.
The 'Message-Id:' header MUST be retained. If not present it MUST The 'Message-Id:' header MUST be retained. If not present it MUST
be created, with a unique value. If an 'X-Mms-Message-Id:' header be created, with a unique value, per [Msg-Fmt].
is present and a 'Message-Id:' header is not, the value of the
'X-Mms-Message-Id:' header MAY be used in creating the 'Message-Id:'
header.
The message ID SHOULD be transmitted in the ESMTP envelope as the The message ID SHOULD be transmitted in the [SMTP] envelope as the
ENVID parameter, as specified in [DSN-SMTP]. ENVID parameter, as specified in [DSN-SMTP].
To facilitate the case where an MMS message traverses the Internet
prior to returning to an MMS system, implementations might wish to
retain the 'X-Mms-Message-Id:' header. Such systems should be aware
that headers which begin with "X-" might be removed during transit
through Internet MTAs.
Recipient(s) address Recipient(s) address
The address of each recipient MUST be transmitted in the SMTP The address of each recipient MUST be transmitted in the [SMTP]
envelope as a RCPT TO value. All disclosed recipients SHOULD also envelope as a RCPT TO value. All disclosed recipients SHOULD also
appear in a 'To:' or 'Cc:' header. At least one 'To:' or 'Cc:' appear in a 'To:' or 'Cc:' header. At least one 'To:', 'Cc:', or
header MUST be present. If all recipients are undisclosed, a 'To:' 'Bcc:' header MUST be present. If all recipients are undisclosed, a
header MAY be created that contains a comment, for example 'To: 'To:' header SHOULD be created using empty group syntax whose name
(undisclosed recipients)'. The 'To:' header SHOULD NOT appear more gives an indication to a human reader, for example 'To:
than once. The 'Cc:' header SHOULD NOT appear more than once. undisclosed-recipients:;'.
The 'To:' header SHOULD NOT appear more than once. The 'Cc:' header
SHOULD NOT appear more than once.
Each recipient address MUST obey the length restrictions per [SMTP]. Each recipient address MUST obey the length restrictions per [SMTP].
Current Internet message format requires that only 7-bit US-ASCII Current Internet message format requires that only 7-bit US-ASCII
characters be present in addresses. Other characters (for example, characters be present in addresses. Other characters (for example,
non-7-bit characters in a phrase part of an address header) MUST be non-7-bit characters in a phrase part of an address header) MUST be
encoded according to [Hdr-Enc]. encoded according to [Hdr-Enc].
All recipient addresses in the [SMTP] envelope must be
fully-qualified in accordance with [SMTP]. In particular, messages
MUST NOT be sent to an Internet mail system with an E.164 numbers
instead of a fully-qualified domain name.
All addresses in 'To:', 'Cc:', and 'Bcc:' headers SHOULD be in the
form of fully-qualified domains. Unqualified E.164 numbers SHOULD
NOT be used.
Gellens [Page 11] Expires March 2006
Sender address Sender address
The address of the message sender SHOULD appear in the 'From:' The address of the message sender SHOULD appear in the 'From:'
header, unless address hiding has been requested. If address hiding header.
has been requested, the 'From:' header MAY contain a comment to this
effect, for example, 'From: (anonymous sender)'.
Gellens [Page 11] Expires November 2005
The address of the message sender for all user-generated messages The address of the message sender for all user-generated messages
('X-Mms-Message-Class: Personal') SHOULD be transmitted in the SMTP ('X-Mms-Message-Class: Personal') SHOULD be transmitted in the
envelope as the MAIL FROM value unless address hiding has been [SMTP] envelope as the MAIL FROM value.
requested and the receiving server is not known and trusted to
support address hiding.
The 'From:' header and the MAIL FROM value MAY be set to a The return addresses in the [SMTP] envelope must be fully-qualified
locally-generated value to hide the sender identity in anonymous in accordance with [SMTP]. In particular, messages MUST NOT be sent
messages when the receiving system does not support anonymous to an Internet mail system with an E.164 numbers instead of a
messages. Locally generated addresses MAY be internally mapped to fully-qualified domain name.
the actual address to allow replies to anonymous messages, but such
mapping is beyond the scope of this specification, as is a mechanism The address(es) in the 'From:' header SHOULD be in the form of
for discovering and requesting support for anonymous messages. fully-qualified domains. Unqualified E.164 numbers SHOULD NOT be
used.
Because of the risk of mail loops, it is critical that the MAIL FROM Because of the risk of mail loops, it is critical that the MAIL FROM
be set to null ("<>") for all automatically-generated MMs (such as be set to null ("<>") for all automatically-generated MMs (such as
'X-Mms-Message-Class: Auto'). The MAIL FROM value MUST be set to 'X-Mms-Message-Class: Auto'). The MAIL FROM value MUST be set to
null for all automatically-generated messages. This includes null for all automatically-generated messages. This includes
reports, "out-of-office" replies, etc. reports, "out-of-office" replies, etc.
Current Internet message format requires that only 7-bit US-ASCII Current Internet message format requires that only 7-bit US-ASCII
characters be present in addresses. Other characters (for example, characters be present in addresses. Other characters (for example,
non-7-bit characters in a phrase part of an address header) MUST be non-7-bit characters in a phrase part of an address header) MUST be
encoded according to [Hdr-Enc]. Note that it would be possible to encoded according to [Hdr-Enc]. Note that it would be possible to
define an SMTP extension to permit transmission of unencoded 8-bit define an [SMTP] extension to permit transmission of unencoded 8-bit
characters, but in the absence of such an extension [Hdr-Enc] MUST characters, but in the absence of such an extension [Hdr-Enc] MUST
be used. be used.
The sender address MUST obey the length restrictions of [SMTP]. The sender address MUST obey the length restrictions of [SMTP].
Content type Content type
The 'Content-Type:' header SHOULD be preserved. Content types not The 'Content-Type:' header SHOULD be preserved.
in widespread use in the Internet MAY be converted into those that
are, when such conversion can be done without significant loss of
content. For example, SMIL messages MAY be converted into
widely-supported multipart/related with multipart/html. When such
conversion is done, the 'Content-Type:' header MUST be updated if it
is no longer correct.
Message class Message class
The 'X-Mms-Message-Class:' header MAY be retained. A 'Precedence: The 'X-Mms-Message-Class:' header MAY be retained in order to
provide information on the source of the message. A 'Precedence:
bulk' header MAY be inserted for class=auto or class=advertisement. bulk' header MAY be inserted for class=auto or class=advertisement.
See 'Sender Address' above. (Class=personal and class=informational See 'Sender Address' above. (Class=personal and class=informational
do not require special handling.) do not require special handling.)
Gellens [Page 12] Expires November 2005 Gellens [Page 12] Expires March 2006
Time of Expiry Time of Expiry
The 'X-Mms-Expiry:' header, if present, SHOULD be removed. The 'X-Mms-Expiry:' header, if present, SHOULD be removed.
The remaining time until the message is considered expired SHOULD be The remaining time until the message is considered expired SHOULD be
transmitted in the ESMTP envelope by using the DELIVER-BY extension, transmitted in the [SMTP] envelope by using the DELIVER-BY
as specified in [Deliver-By]. extension, as specified in [Deliver-By].
Note that the ESMTP DELIVER-BY extension carries time remaining Note that the [SMTP] DELIVER-BY extension carries time remaining
until expiration; each server decrements the value by the amount of until expiration; each server decrements the value by the amount of
time it has possessed the message. The 'X-Mms-Expiry:' header may time it has possessed the message. The 'X-Mms-Expiry:' header may
contain either the absolute time at which the message is considered contain either the absolute time at which the message is considered
expired or the relative time until the message is considered expired or the relative time until the message is considered
expired. expired.
Earliest delivery time Earliest delivery time
The 'X-Mms-Delivery-Time:' header, if present, SHOULD be removed. The 'X-Mms-Delivery-Time:' header, if present, SHOULD be removed.
Future delivery is a message submission, not message relay feature. Future delivery is a message submission, not message relay feature.
Delivery report request Delivery report request
Requests for delivery status notifications (DSNs) SHOULD be Requests for delivery status notifications (DSNs) SHOULD be
transmitted in the ESMTP envelope by using the DSN extension as transmitted in the [SMTP] envelope by using the DSN extension as
specified in [DSN-SMTP] to request "success" or "none" notification specified in [DSN-SMTP] to request "success" or "none" notification
(depending on the value of the 'X-Mms-Delivery-Report' header). (depending on the value of the 'X-Mms-Delivery-Report' header).
When the NOTIFY extension is used, the unaltered recipient address When the NOTIFY extension is used, the unaltered recipient address
SHOULD be transmitted as the ORCPT value, and the original message SHOULD be transmitted as the ORCPT value, and the original message
ID SHOULD be transmitted as the ENVID value. ID SHOULD be transmitted as the ENVID value.
The 'X-Mms-Delivery-Report:' header, if present, SHOULD be removed. The 'X-Mms-Delivery-Report:' header, if present, SHOULD be removed.
Importance Importance
The message sender's importance value (also called "priority", The message sender's importance value (also called "priority",
although this can be confused with class-of-service values) SHOULD although this can be confused with class-of-service values) SHOULD
be transmitted using an 'Importance:' header (although currently not be transmitted using an 'Importance:' header.
all Internet mail clients support this header).
An 'X-Priority:' header MAY be used in addition. Although not
standardized, most email applications support the 'X-Priority:'
header, and use an 'X-Priority' value of 3 for messages with
"normal" priority. More important messages have lower values and
less important message have higher values. In most cases, urgent
messages have an X-Priority value of 1.
Gellens [Page 13] Expires November 2005
Suggested mappings: Suggested mappings:
2.1.3.2.1 Table 2: Importance Mappings (MMS to Internet Message) 2.1.3.2.1 Table 2: Importance Mappings (MMS to Internet Message)
---------------------------|------------------ ---------------------------|------------------
'X-Mms-Priority: High' |'Importance: High' 'X-Mms-Priority: High' |'Importance: High'
---------------------------|------------------ ---------------------------|------------------
'X-Mms-Priority: Normal' |[omit] 'X-Mms-Priority: Normal' |[omit]
---------------------------|------------------ ---------------------------|------------------
'X-Mms-Priority: Low' |'Importance: Low' 'X-Mms-Priority: Low' |'Importance: Low'
Gellens [Page 13] Expires March 2006
---------------------------|------------------ ---------------------------|------------------
Normal priority messages should omit the 'Importance:' header. Normal priority messages should omit the 'Importance:' header.
2.1.3.2.2 Table 3: X-Priority Mappings (MMS to Internet Message) 2.1.3.2.2 Table 3: X-Priority Mappings (MMS to Internet Message)
---------------------------|---------------------- ---------------------------|----------------------
'X-Mms-Priority: High' |'X-Priority: 2 (high)' 'X-Mms-Priority: High' |'X-Priority: 2 (high)'
---------------------------|---------------------- ---------------------------|----------------------
'X-Mms-Priority: Normal |[omit] 'X-Mms-Priority: Normal |[omit]
---------------------------|---------------------- ---------------------------|----------------------
'X-Mms-Priority: Low |'X-Priority: 4 (low)' 'X-Mms-Priority: Low |'X-Priority: 4 (low)'
---------------------------|---------------------- ---------------------------|----------------------
Normal priority messages SHOULD omit the 'X-Priority:' header. Normal priority messages SHOULD omit the 'X-Priority:' header.
The 'X-Mms-Priority:' header, if present, SHOULD be removed. The 'X-Mms-Priority:' header, if present, SHOULD be removed.
Sender visibility Sender visibility
Support for sender address hiding is not included in this version of Support for sender address hiding is not currently supported.
the mapping document.
The 'X-Mms-Sender-Visibility:' header, if present, SHOULD be The 'X-Mms-Sender-Visibility:' header, if present, SHOULD be
removed. removed.
Read reply request Read reply request
A request for a read reply SHOULD be transmitted using a A request for a read reply SHOULD be transmitted using a
'Disposition-Notification-To:' header as specified in [MDN]. 'Disposition-Notification-To:' header as specified in [MDN].
The 'X-Mms-Read-Reply:' header, if present, SHOULD be removed. The 'X-Mms-Read-Reply:' header, if present, SHOULD be removed.
Reply-charging Reply-charging
Reply charging permission and acceptance are complex issues Reply charging permission and acceptance are complex issues
requiring both user agent and server support. Misapplied reply requiring both user agent and server support. Misapplied reply
charging may cause incorrect billing. Until the security issues charging may cause incorrect billing. Until the security issues
have been properly addressed, reply charging SHOULD NOT be honored have been properly addressed, reply charging SHOULD NOT be honored
Gellens [Page 14] Expires November 2005
when using this interface. when using this interface.
The 'X-Mms-Reply-Charging:', 'X-Mms-Reply-Charging-Deadline:', The 'X-Mms-Reply-Charging:', 'X-Mms-Reply-Charging-Deadline:',
'X-Mms-Reply-Charging-Size:', and 'X-Mms-Reply-Charging-Id:' headers 'X-Mms-Reply-Charging-Size:', and 'X-Mms-Reply-Charging-Id:' headers
MAY be removed. Messages containing a reply-charging usage request MAY be removed. Messages containing a reply-charging usage request
('X-Mms-Reply-Charging-Id:' and 'X-Mms-Reply-Charging: accepted' or ('X-Mms-Reply-Charging-Id:' and 'X-Mms-Reply-Charging: accepted' or
'X-Mms-Reply-Charging: accepted (text only)' headers) SHOULD be 'X-Mms-Reply-Charging: accepted (text only)' headers) SHOULD be
rejected. rejected.
Gellens [Page 14] Expires March 2006
Subject Subject
The 'Subject:' header MUST be preserved. Current Internet message The 'Subject:' header MUST be preserved. Current Internet message
format requires that only 7-bit US-ASCII characters be present. format requires that only 7-bit US-ASCII characters be present.
Other characters must be encoded according to [Hdr-Enc]. Note that Other characters must be encoded according to [Hdr-Enc]. Note that
it would be possible to define an SMTP extension to permit it is possible for an [SMTP] extension to be defined which would
transmission of unencoded 8-bit characters, but in the absence of permit transmission of unencoded 8-bit characters, but in the
such an extension [Hdr-Enc] must be used. absence of such an extension [Hdr-Enc] must be used.
Resending/Forwarding
In MMS a message may be resent or forwarded, the difference being
that if the message has been downloaded then sending it to another
address is considered forwarding, while sending a message that has
not been downloaded is considered to be resending.
In Internet mail there are two primary ways of sending a previously Resending
received message to a new recipient: forwarding and resending.
Forwarding is when a user creates a new message containing the
original message, either simply embedded within the text, or
delineated. Embedded messages generally have each original line
preceded by a quote symbol ('>'), surround the original text with a
preceding and trailing line which starts with hyphens as per
[Msg-Encap], such as '--- begin forwarded text' and '--- end
forwarded text', or encapsulate the original message as a
'message/rfc822' content type, perhaps within a 'multipart/mixed'
message. (This last method offers more robust delineation.)
Resending is when the original message is unaltered except for the
addition of 'Resent-' headers to explain the resending to the new
recipient.
A message may be resent more than once; each time new 'Resent-' A message may be resent to one or more new recipients; it may be
headers SHOULD be added at the top of the message. Thus, if more resent more than once; each time new 'Resent-' headers SHOULD be
than one series of 'Resent-' headers are present, the original added at the top of the message. Thus, if more than one series of
series is the last; the most recent is the first. 'Resent-' headers are present, the original series is the last; the
most recent is the first.
Forward counter Forward counter
Gellens [Page 15] Expires November 2005
The 'Resent-Count:' header is NOT RECOMMENDED. Loop control is The 'Resent-Count:' header is NOT RECOMMENDED. Loop control is
usually done by counting 'Received' headers, which are more general usually done by counting 'Received' headers, which are more general
than 'Resent-' headers. than 'Resent-' headers.
Previously-sent Information Previously-sent Information
A 'Resent-From:' header MAY be added to indicate the address of the A 'Resent-From:' header MAY be added to indicate the address of the
user who directed the message to be resent. user who directed the message to be resent.
A 'Resent-Date:' header SHOULD be added to indicate the time and A 'Resent-Date:' header SHOULD be added to indicate the time and
skipping to change at line 688 skipping to change at line 640
the message SHOULD appear in the 'From:' header; the original the message SHOULD appear in the 'From:' header; the original
recipient(s) SHOULD appear in the 'To:' header; the time and date recipient(s) SHOULD appear in the 'To:' header; the time and date
the message was originally sent SHOULD appear in the 'Date:' header. the message was originally sent SHOULD appear in the 'Date:' header.
The most recent sender SHOULD appear in the top-most 'Resent-From:' The most recent sender SHOULD appear in the top-most 'Resent-From:'
header; the most recent recipient(s) SHOULD appear in the top-most header; the most recent recipient(s) SHOULD appear in the top-most
'Resent-To:' header; the time and date the message was most recently 'Resent-To:' header; the time and date the message was most recently
sent SHOULD appear in the top-most 'Resent-Date:' header. sent SHOULD appear in the top-most 'Resent-Date:' header.
'Received:' Headers 'Received:' Headers
Each system that processes a message SHOULD add a 'Received:' header When a message is gatewayed from MMS to Internet mail, a 'Received:'
as per [SMTP]. A message MAY be rejected if the number of header MUST be added as per [SMTP]. The "with" clause should
'Received:' headers exceeds a locally-defined maximum, which MUST specify "MMS".
conform to [SMTP] section 6.2 and SHOULD be no less than 100.
Gellens [Page 15] Expires March 2006
A message MAY be rejected if the number of 'Received:' headers
exceeds a locally-defined maximum, which MUST conform to [SMTP]
section 6.2 and SHOULD be no less than 100.
Privacy Privacy
Note that MMS systems do not currently support the 'Privacy' header Note that MMS systems do not currently support the 'Privacy' header
field as described by [VPIM]. field as described by [VPIM].
Content Content
The message content appears in the message body. Note that Internet The message content appears in the message body. Note that Internet
message format requires that line-endings be encoded as CR LF, thus message format requires that line-endings be encoded as CR LF, thus
charset encodings that do not have this property cannot be used in charset encodings that do not have this property cannot be used in
text/* body parts. (They MAY be used in other body parts, but only text/* body parts. (They may be used in other body parts, but only
when they are suitable encoded or when binary transmission has been when they are suitable encoded or when binary transmission has been
negotiated.) In particular, MMS allows UTF-16, while Internet negotiated.) In particular, MMS allows UTF-16, while Internet
message format does not. UTF-16 encoding MUST be translated to message format does not. UTF-16 encoding MUST be translated to
UTF-8 or another charset and encoding which is suitable for use in UTF-8 or another charset and encoding which is suitable for use in
Internet message format/protocols. Internet message format/protocols.
Gellens [Page 16] Expires November 2005
2.1.3.3 Conversion of messages from Internet to MMS format 2.1.3.3 Conversion of messages from Internet to MMS format
3GPP MMS Version 3GPP MMS Version
An 'X-Mms-3GPP-MMS-Version:' header SHOULD be added. An 'X-Mms-3GPP-MMS-Version:' header SHOULD be added.
Message Type (of PDU) Message Type (of PDU)
An 'X-Mms-Message-Type:' header SHOULD be used in accordance with An 'X-Mms-Message-Type:' header SHOULD be used in accordance with
the specific MMS interface (e.g., MM1, MM4). the specific MMS interface (e.g., MM1, MM4).
Transaction ID Transaction ID
An 'X-Mms-Transaction-Id:' header SHOULD be used in accordance with An 'X-Mms-Transaction-Id:' header SHOULD be used in accordance with
the specific MMS interface (e.g., MM1, MM4). the specific MMS interface (e.g., MM1, MM4).
Message ID Message ID
The 'Message-Id:' header MUST be retained. If not present it MUST The 'Message-Id:' header MUST be retained. If not present it MUST
be created, with a unique value. If the 'Message-Id:' header does be created, with a unique value.
not exist, but the SMTP envelop contains an ENVID value (as
specified in [DSN-SMTP]), it MAY be used to construct the value.
Recipient(s) address Recipient(s) address
'To:' and 'Cc:' headers MUST be retained. 'To:' and 'Cc:' headers MUST be retained.
Each recipient contained in the SMTP envelope (RCPT TO values) MUST Gellens [Page 16] Expires March 2006
be considered a recipient of the message. Recipients who appear in Each recipient contained in the [SMTP] envelope (RCPT TO values)
address headers but not the SMTP envelope MUST be ignored. MUST be considered a recipient of the message. Recipients who
Recipients who appear in the [SMTP] envelope but do not appear in appear in address headers but not the [SMTP] envelope MUST be
headers are considered "blind" (Bcc) recipients; such recipients ignored. Recipients who appear in the [SMTP] envelope but do not
MUST NOT be added to message headers (including address and trace appear in headers are considered "blind" (Bcc) recipients; such
headers) unless there is only one recipient total. recipients MUST NOT be added to message headers (including address
and trace headers) unless there is only one recipient total.
Sender address Sender address
The 'From:' header MUST be retained. The 'From:' header MUST be retained.
Content type Content type
The complete 'Content-Type:' header (including any parameters) The complete 'Content-Type:' header (including any parameters)
SHOULD be preserved. SHOULD be preserved.
Message class Message class
Gellens [Page 17] Expires November 2005 An 'X-Mms-Message-Class: personal' header MAY be created for all
An 'X-Mms-Message-Class: personal' header SHOULD be created for all
received messages with a non-null return path (MAIL FROM value in received messages with a non-null return path (MAIL FROM value in
the SMTP envelope). An 'X-Mms-Message-Class: auto' header MAY be the SMTP envelope). An 'X-Mms-Message-Class: auto' header MAY be
created for messages with a null return path. created for messages with a null return path.
Time of Expiry Time of Expiry
An 'X-Mms-Expiry:' header SHOULD be created if the message contains An 'X-Mms-Expiry:' header SHOULD be created if the message contains
a relative time to expiration in the DELIVER-BY extension, as a relative time to expiration in the DELIVER-BY extension, as
specified in [Deliver-By]. specified in [Deliver-By].
Earliest delivery time Earliest delivery time
An 'X-Mms-Delivery-Time:' header SHOULD NOT be created. If a An 'X-Mms-Delivery-Time:' header SHOULD NOT be created. If a
message arrives via ESMTP relay containing an earliest time of message arrives via [SMTP] relay containing an earliest time of
delivery in the AFTER extension, it MAY be rejected. If a message delivery in the AFTER extension, it MAY be rejected. If a message
is submitted via Message Submission [Submission] containing an is submitted via Message Submission [Submission] containing an
earliest time of delivery in the AFTER extension, it MUST either be earliest time of delivery in the AFTER extension, it MUST either be
retained until the delivery time arrives, or it may be immediately retained until the delivery time arrives, or it may be immediately
rejected. It MUST NOT be delivered or further relayed prior to the rejected. It MUST NOT be delivered or further relayed prior to the
delivery time. delivery time.
Delivery report request Delivery report request
An 'X-Mms-Delivery-Report:' header SHOULD be created for messages An 'X-Mms-Delivery-Report:' header SHOULD be created for messages
which request 'success' or 'none' delivery status notification by which request 'success' or 'none' delivery status notification by
use of the DSN extension as specified in [DSN-SMTP]. Requests for use of the DSN extension as specified in [DSN-SMTP]. Requests for
'delay' notifications or non-default actions, such as that only the 'delay' notifications or non-default actions, such as that only the
message headers should be returned, cannot be mapped onto MMS message headers should be returned, cannot be mapped onto MMS
headers and thus SHOULD be ignored. headers and thus SHOULD be ignored.
Gellens [Page 17] Expires March 2006
Priority Priority
An 'X-Priority:' or 'Importance:' header, if present, SHOULD be An 'X-Priority:' or 'Importance:' header, if present, SHOULD be
replaced with an 'X-Mms-Priority:' header. Suggested mappings: replaced with an 'X-Mms-Priority:' header. Suggested mappings:
2.1.3.3.1 Table 4: Priority Mappings (Internet Message to MMS) 2.1.3.3.1 Table 4: Priority Mappings (Internet Message to MMS)
-------------------------------|---------------------- -------------------------------|----------------------
'X-Priority: 1 (highest)' |'X-Mms-Priority: High' 'X-Priority: 1 (highest)' |'X-Mms-Priority: High'
-------------------------------|---------------------- -------------------------------|----------------------
'X-Priority: 2 (high)' |'X-Mms-Priority: High' 'X-Priority: 2 (high)' |'X-Mms-Priority: High'
-------------------------------|---------------------- -------------------------------|----------------------
'Importance: High' |'X-Mms-Priority: High' 'Importance: High' |'X-Mms-Priority: High'
-------------------------------|---------------------- -------------------------------|----------------------
'X-Priority: 3 (normal)' | [omitted] 'X-Priority: 3 (normal)' | [omitted]
-------------------------------|---------------------- -------------------------------|----------------------
'Importance: Normal' | [omitted] 'Importance: Normal' | [omitted]
-------------------------------|---------------------- -------------------------------|----------------------
Gellens [Page 18] Expires November 2005
'X-Priority: 4 (low)' |'X-Mms-Priority: Low' 'X-Priority: 4 (low)' |'X-Mms-Priority: Low'
-------------------------------|---------------------- -------------------------------|----------------------
'Importance: Low' |'X-Mms-Priority: Low' 'Importance: Low' |'X-Mms-Priority: Low'
-------------------------------|---------------------- -------------------------------|----------------------
'X-Priority: 5 (lowest)' |'X-Mms-Priority: Low' 'X-Priority: 5 (lowest)' |'X-Mms-Priority: Low'
-------------------------------|---------------------- -------------------------------|----------------------
Normal priority messages SHOULD omit the 'X-Mms-Priority:' header. Normal priority messages SHOULD omit the 'X-Mms-Priority:' header.
Sender visibility Sender visibility
skipping to change at line 833 skipping to change at line 784
Read reply request Read reply request
A request for a read reply contained in a A request for a read reply contained in a
'Disposition-Notification-To:' header as specified in [MDN] SHOULD 'Disposition-Notification-To:' header as specified in [MDN] SHOULD
be replaced with an 'X-Mms-Read-Reply:' header. be replaced with an 'X-Mms-Read-Reply:' header.
Subject Subject
The 'Subject:' header MUST be preserved. The 'Subject:' header MUST be preserved.
Resending/Forwarding Resending
One or more sets of 'Resent-' headers, if present, SHOULD be mapped One or more sets of 'Resent-' headers, if present, SHOULD be mapped
to 'To:', 'From:', 'Date:', and 'X-Mms-Previously-Sent-' headers. to 'To:', 'From:', 'Date:', and 'X-Mms-Previously-Sent-' headers.
Gellens [Page 18] Expires March 2006
'Received:' Headers 'Received:' Headers
Each system that processes a message SHOULD add a 'Received:' header Each system that processes a message SHOULD add a 'Received:' header
as per [SMTP]. A message MAY be rejected if the number of as per [SMTP]. A message MAY be rejected if the number of
'Received:' headers exceeds a locally-defined maximum, which MUST 'Received:' headers exceeds a locally-defined maximum, which MUST
conform to [SMTP] section 6.2 and SHOULD be no less than 100. conform to [SMTP] section 6.2 and SHOULD be no less than 100.
Sensitivity Sensitivity
The 'Sensitivity:' header field (value = "personal" or "private") The 'Sensitivity:' header field (value = "personal" or "private")
[VPIM] indicates the desire of a voice message originator to send [VPIM] indicates the desire of a voice message originator to send
the message contents to the original recipient list with assurance the message contents to the original recipient list with assurance
that the message will not be forwarded further by either the that the message will not be forwarded further by either the
messaging system or the actual message recipient(s). Since messaging system or the actual message recipient(s). Since
sensitivity is not an MMS feature, any messages which contain a sensitivity is not an MMS feature, any messages which contain a
'Sensitivity:' header SHOULD NOT be sent to an MMS system. An 'Sensitivity:' header MUST NOT be sent to an MMS system. The
appropriate extended error response code [RESP] SHOULD be used in associated negative delivery status report MUST include the extended
the associated negative delivery status report. status code [RESP] 5.6.0 as specified in [VPIM] ("Other or undefined
protocol status") indicating that privacy could not be assured.
Gellens [Page 19] Expires November 2005
Content Content
The message content appears in the message body. The message content appears in the message body.
2.1.4 Report Generation and Conversion 2.1.4 Report Generation and Conversion
Internet Message systems use the multipart/report MIME type for Internet Message systems use the multipart/report MIME type for
delivery and disposition reports as specified in [Report-Fmt]. This delivery and disposition reports as specified in [Report-Fmt]. This
format is a two- or three-part MIME message; one part is a format is a two- or three-part MIME message; one part is a
structured format describing the event being reported in an structured format describing the event being reported in an
easy-to-parse format. Specific reports have a format which is built easy-to-parse format. Specific reports have a format which is built
on [Report-Fmt]. Delivery reports are specified in [DSN-Msg]. on [Report-Fmt]. Delivery reports are specified in [DSN-Msg].
Message disposition reports, which include read reports, are Message disposition reports, which include read reports, are
specified in [MDN]. specified in [MDN].
By contrast, MMS reports are plain text, with no defined structure By contrast, MMS reports are plain text, with no defined structure
specified. This makes it difficult to convert from an MMS report to specified. This makes it difficult to convert from an MMS report to
a standard Internet report. a standard Internet report.
An MMS Relay/Server supporting Internet Message exchange using MM3 An implementation conforming to this specification MUST convert
MUST convert reports received from one side (MMS or Internet mail) reports received from one side (MMS or Internet mail) destined for
destined for the other. In addition, reports MUST be generated as the other. In addition, reports MUST be generated as appropriate
appropriate for messages received from either side of the MM3 for messages received from either side. For example, if an MM to be
interface. For example, if an MM to be sent via MM3 is not sent via Internet mail is not deliverable, a delivery status MM
deliverable, a delivery status MM shall be generated. Likewise, if shall be generated. Likewise, if an Internet message is received
an Internet message is received via MM3 that cannot be further that cannot be further relayed or delivered, a delivery status
relayed or delivered, a delivery status report [DSN-Msg] MUST be report [DSN-Msg] MUST be generated.
generated.
Gellens [Page 19] Expires March 2006
When creating delivery or disposition reports from MMS reports, the When creating delivery or disposition reports from MMS reports, the
MMS report should be parsed to determine the reported event and MMS report should be parsed to determine the reported event and
time, status, and the headers of the referenced (original) message. time, status, and the headers of the referenced (original) message.
These elements, once determined, are used to populate the subparts These elements, once determined, are used to populate the subparts
of the delivery or disposition report. The first subpart is of type of the delivery or disposition report. The first subpart is of type
text/plain, and contains a human-readable explanation of the event. text/plain, and contains a human-readable explanation of the event.
This text may include a statement that the report was synthesized This text may include a statement that the report was synthesized
based on an MMS report. The second subpart is of type based on an MMS report. The second subpart is of type
report/delivery-status (for delivery reports) or report/delivery-status (for delivery reports) or
report/disposition-notification (for disposition reports). This report/disposition-notification (for disposition reports). This
second part contains a structured itemization of the event. The second part contains a structured itemization of the event. The
third subpart is of type message/rfc822 and includes the headers and third subpart is of type message/rfc822 and includes the headers and
optionally the body of the referenced (original) message. optionally the body of the referenced (original) message.
2.1.4.1 Delivery Report Mapping from MMS to Internet Message 2.1.4.1 Delivery Report Mapping from MMS to Internet Message
Gellens [Page 20] Expires November 2005
The following table maps information elements from MMS delivery The following table maps information elements from MMS delivery
reports to the format specified in [DSN-Msg]. reports to the format specified in [DSN-Msg].
2.1.4.1.1 Table 5: Delivery Report Mappings (MMS to Internet Message) 2.1.4.1.1 Table 5: Delivery Report Mappings (MMS to Internet Message)
======================|============|=================================== ======================|============|===================================
Information Element |MMS Delivery|[DSN-Msg] Element Information Element |MMS Delivery|[DSN-Msg] Element
|Report Elem | |Report Elem |
======================|============|=================================== ======================|============|===================================
ID of message whose |Message-Id: |'Original-Envelope-ID' field of ID of message whose |Message-Id: |'Original-Envelope-ID' field of
delivery status is | |per-message fields (use value of delivery status is | |per-message fields (use value of
being reported | |ENVID from ESMTP envelope if avail- being reported | |ENVID from SMTP envelope if avail-
| |able, 'Message-ID:' otherwise). | |able, 'Message-ID:' otherwise).
----------------------|------------|----------------------------------- ----------------------|------------|-----------------------------------
Recipient address of |From: |'Final-Recipient' field of the Recipient address of |From: |'Final-Recipient' field of the
the original message | |per-recipient section the original message | |per-recipient section
(object of delivery | | (object of delivery | |
report) | | report) | |
----------------------|------------|----------------------------------- ----------------------|------------|-----------------------------------
Destination address of|To: |'To:' header field value of top- Destination address of|To: |'To:' header field value of top-
report | |level. report | |level.
| | | |
| |Value taken from [SMTP] envelope | |Value taken from [SMTP] envelope
| |return-path of message being | |return-path of message being
| |reported, not its 'From:' header | |reported, not its 'From:' header
| |field. | |field.
----------------------|------------|----------------------------------- ----------------------|------------|-----------------------------------
Date and time the |Date: |'Date:' header field value of top- Date and time the |Date: |'Date:' header field value of top-
message was handled | |level message was handled | |level
======================|============|=================================== ======================|============|===================================
Gellens [Page 21] Expires November 2005 Gellens [Page 20] Expires March 2006
======================|============|=================================== ======================|============|===================================
Information Element |MMS Delivery|[DSN-Msg] Element Information Element |MMS Delivery|[DSN-Msg] Element
|Report Elem | |Report Elem |
======================|============|=================================== ======================|============|===================================
Delivery status of |X-Mms- |Action and Status fields of Delivery status of |X-Mms- |Action and Status fields of
original message to | Status: |per-recipient section. original message to | Status: |per-recipient section.
each recipient | | each recipient | |
| |The 'Action' field indicates if the | |The 'Action' field indicates if the
| |message was delivered. | |message was delivered.
skipping to change at line 985 skipping to change at line 936
* Top-level header field 'To:' SHOULD be the [SMTP] return-path of * Top-level header field 'To:' SHOULD be the [SMTP] return-path of
the message whose status is being reported. the message whose status is being reported.
* Top-level header field 'From:' SHOULD be the address of the * Top-level header field 'From:' SHOULD be the address of the
recipient that the delivery-report concerns. recipient that the delivery-report concerns.
* The first part of the [DSN-Msg] SHOULD include the MM Status Text * The first part of the [DSN-Msg] SHOULD include the MM Status Text
field that would have been generated for an MM1 delivery-report. field that would have been generated for an MM1 delivery-report.
Gellens [Page 22] Expires November 2005 Gellens [Page 21] Expires March 2006
2.1.4.2 Delivery Report Mapping from Internet Message to MMS 2.1.4.2 Delivery Report Mapping from Internet Message to MMS
The following table maps information elements from a delivery report The following table maps information elements from a delivery report
as specified in [DSN-Msg] to the format of an MMS delivery report. as specified in [DSN-Msg] to the format of an MMS delivery report.
2.1.4.2.1 Table 6: Delivery Report Mappings (Internet Message to MMS) 2.1.4.2.1 Table 6: Delivery Report Mappings (Internet Message to MMS)
===================|==================|================================ ===================|==================|================================
Information Element|MMS Delivery |[DSN-Msg] Element Information Element|MMS Delivery |[DSN-Msg] Element
skipping to change at line 1022 skipping to change at line 973
-------------------|------------------|-------------------------------- -------------------|------------------|--------------------------------
Destination address|To: |'To:' header field value of Destination address|To: |'To:' header field value of
of report | |top-level. of report | |top-level.
| | | |
| |Value taken from [SMTP] envelope | |Value taken from [SMTP] envelope
| |return-path of message being | |return-path of message being
| |reported, not its 'From:' header | |reported, not its 'From:' header
| |field. | |field.
===================|==================|================================ ===================|==================|================================
Gellens [Page 23] Expires November 2005 Gellens [Page 22] Expires March 2006
===================|==================|================================ ===================|==================|================================
Information Element|MMS Delivery |[DSN-Msg] Element Information Element|MMS Delivery |[DSN-Msg] Element
|Report Element | |Report Element |
===================|==================|================================ ===================|==================|================================
Date and time the |Date: |'Date:' header field value of Date and time the |Date: |'Date:' header field value of
message was handled| |top-level message was handled| |top-level
-------------------|------------------|-------------------------------- -------------------|------------------|--------------------------------
Delivery status of |X-Mms-Status: |'Action' and 'Status' fields of Delivery status of |X-Mms-Status: |'Action' and 'Status' fields of
original message | |per-recipient section original message | |per-recipient section
skipping to change at line 1058 skipping to change at line 1009
|'deferred' MUST | |'deferred' MUST |
|NOT be used | |NOT be used |
|(ignore DSNs with | |(ignore DSNs with |
|'Action' value | |'Action' value |
|'delayed') | |'delayed') |
-------------------|------------------|-------------------------------- -------------------|------------------|--------------------------------
Status Text | |Text in first part (human- Status Text | |Text in first part (human-
| |readable part) | |readable part)
===================|==================|================================ ===================|==================|================================
Gellens [Page 24] Expires November 2005 Gellens [Page 23] Expires March 2006
2.1.4.3 Read Report Mapping from MMS to Internet Message 2.1.4.3 Read Report Mapping from MMS to Internet Message
The following table maps information elements from MMS read reports The following table maps information elements from MMS read reports
to the format specified in [MDN]. to the format specified in [MDN].
2.1.4.3.1 Table 7: Read Report Mappings (MMS to Internet Message) 2.1.4.3.1 Table 7: Read Report Mappings (MMS to Internet Message)
======================|============|=================================== ======================|============|===================================
Information Element |MMS Delivery|[MDN] Element Information Element |MMS Delivery|[MDN] Element
|Report Elem | |Report Elem |
======================|============|=================================== ======================|============|===================================
ID of the original |Message-Id: |'Original-Envelope-ID' field (use ID of the original |Message-Id: |'Original-Envelope-ID' field (use
message (object of | |value of ENVID from ESMTP envelope message (object of | |value of ENVID from [SMTP] envelope
read report) | |if available, 'Message-ID:' read report) | |if available, 'Message-ID:'
| |otherwise). | |otherwise).
----------------------|------------|----------------------------------- ----------------------|------------|-----------------------------------
Recipient address of |From: |'Final-Recipient' field Recipient address of |From: |'Final-Recipient' field
the original message | | the original message | |
----------------------|------------|----------------------------------- ----------------------|------------|-----------------------------------
Destination address of|To: |'To:' header field value of top- Destination address of|To: |'To:' header field value of top-
report | |level. report | |level.
| | | |
| |Value taken from 'Disposition- | |Value taken from 'Disposition-
skipping to change at line 1104 skipping to change at line 1055
| |'displayed'; for MMS-Read-Status | |'displayed'; for MMS-Read-Status
| |value 'Deleted without being read', | |value 'Deleted without being read',
| |use 'disposition-type' value | |use 'disposition-type' value
| |'deleted') | |'deleted')
----------------------|------------|----------------------------------- ----------------------|------------|-----------------------------------
Status Text | |Text in first part (human-readable Status Text | |Text in first part (human-readable
| |part) | |part)
======================|============|=================================== ======================|============|===================================
When an MMS Relay/Server generates an [MDN] in response to a message When an MMS Relay/Server generates an [MDN] in response to a message
received using ESMTP on MM3: received using [SMTP] on MM3:
Gellens [Page 25] Expires November 2005 Gellens [Page 24] Expires March 2006
* Top-level header field 'To:' SHOULD be the value of the * Top-level header field 'To:' SHOULD be the value of the
'Disposition-Notification-To:' header field of the message whose 'Disposition-Notification-To:' header field of the message whose
disposition is being reported . disposition is being reported .
* Top-level header field 'From:' SHOULD be the address of the * Top-level header field 'From:' SHOULD be the address of the
recipient that the read report concerns. recipient that the read report concerns.
2.1.4.4 Disposition Report Mapping from Internet Message to MMS 2.1.4.4 Disposition Report Mapping from Internet Message to MMS
The following table maps information elements from a disposition The following table maps information elements from a disposition
skipping to change at line 1146 skipping to change at line 1097
| | | |
| |Value taken from 'Disposition- | |Value taken from 'Disposition-
| |Notification-To:' header field | |Notification-To:' header field
| |of message being reported, not | |of message being reported, not
| |its 'From:' header field. | |its 'From:' header field.
-------------------|------------------|-------------------------------- -------------------|------------------|--------------------------------
Date and time the |Date: |'Date:' header field value of Date and time the |Date: |'Date:' header field value of
message was handled| |top-level message was handled| |top-level
===================|==================|================================ ===================|==================|================================
Gellens [Page 26] Expires November 2005 Gellens [Page 25] Expires March 2006
===================|==================|================================ ===================|==================|================================
Information Element|MMS Read Report |[MDN] Element Information Element|MMS Read Report |[MDN] Element
|Element | |Element |
===================|==================|================================ ===================|==================|================================
Disposition of |X-Mms-Read-Status:|disposition-field Disposition of |X-Mms-Read-Status:|disposition-field
message being | | message being | |
reported |Set to one of the | reported |Set to one of the |
|following values: | |following values: |
| | | |
skipping to change at line 1177 skipping to change at line 1128
|action-mode is | |action-mode is |
|'automatic- | |'automatic- |
|action') | |action') |
-------------------|------------------|-------------------------------- -------------------|------------------|--------------------------------
Status Text | |Text in first part (human- Status Text | |Text in first part (human-
| |readable part) | |readable part)
===================|==================|================================ ===================|==================|================================
2.1.5 Message Delivery 2.1.5 Message Delivery
Within Internet mail, when ESMTP is used and delivery reports are Within Internet mail, when [SMTP] is used and delivery reports are
requested [DSN-SMTP], delivery is considered to be acceptance of a requested [DSN-SMTP], delivery is considered to be acceptance of a
message by the final server, that is, the server closest to the message by the final server, that is, the server closest to the
recipient. When an MMS Relay/Server receives a message using ESMTP recipient. When an MMS Relay/Server receives a message using [SMTP]
and a delivery report is requested, the MMS Relay/Server MAY and a delivery report is requested, the MMS Relay/Server MAY
consider the message delivered when it has been sent to the MMS User consider the message delivered when it has been sent to the MMS User
Agent. Agent.
3 Security Considerations 3 Security Considerations
Data contained within messages should not be automatically trusted. Both MMS and Internet mail have their own set of security risks and
Even within a carrier's network, and certainly within the Internet, considerations. This document specifies how to exchange messages
various deliberate and accidental attacks or corruptions are between these two environments, so it is only appropriate to discuss
possible. For example, routers may contain vulnerabilities which considerations specific to this functionality, not those inherent in
may be exploited, IP traffic may be intercepted and/or modified, either environment.
etc.
Gellens [Page 27] Expires November 2005
The following messaging-related security threats can be identified:
* Misidentification of message source.
* Message interception (unauthorized disclosure of contents).
* Unauthorized disclosure of message sender or recipient.
* Message modification (by adversary).
* Message replay.
* Traffic analysis (determining who is communicating with whom).
There are existing mechanisms which can be used to protect email
traffic against some of these threats, such as:
* Use of SSL/TLS (via [StartTLS]) to address disclosure and
modification in transit between adjacent servers.
* SMTP Authentication [Auth] to protect against misidentification of
message source.
* Use of end-to-end security mechanisms such as [PGP] or S/MIME
[SMIME] to protect message contents.
* Use of [IPSec] to protect against disclosure or modification in
transit between servers.
Use of these mechanisms is encouraged. When a message uses
end-to-end security mechanisms such as [PGP] or S/MIME [SMIME],
servers MUST be careful not to accidently destroy the integrity of
the protected content (for example, by altering any text within the
region covered by a signature while mapping between MMS and email).
Since MMS does not include a clear separation between in-transit
envelope and message content, there are increased risks of
unauthorized disclosure of information, and additional challenges in
protecting data. For example, Bcc recipients do not normally appear
in the message content, only in the envelope; care MUST be taken in
the gateway function to ensure that Bcc recipients which do appear
are deleted from the message content.
Some MMS features contain inherently more risk than others. For Gellens [Page 26] Expires March 2006
example, reply charging and sender address hiding. The reply When a message uses end-to-end security mechanisms such as [PGP] or
charging mechanism requires a high degree of trust between entities S/MIME [SMIME], servers MUST be careful not to accidently destroy
with little technical basis. Deliberate or accidental abuse of this the integrity of the protected content (for example, by altering any
trust can result in unexpected or unauthorized charges. For text within the region covered by a signature while mapping between
example, a sender may be charged for unauthorized replies, or a MMS and email). [Mime-Sec-gw] discusses issues with use of such
mechanisms in gateways.
Gellens [Page 28] Expires November 2005 Some MMS features contain inherently more risk than others,
sender may be charged for a reply which the author thought would be including reply charging and sender address hiding. Support for
paid for by the recipient. A sender's identity may be disclosed in these mechanisms are not included in this document.
violation of a request for this to be blocked. The identity of
recipients may be disclosed to other recipients (or even
non-recipients) for a message in which the sender intended for the
recipients not to be disclosed.
It is possible to hide the sender's identity from non-recipients 4 IANA Considerations
using anonymous remailers. It is hard to hide the sender's identity
from recipients when the mail is cryptographically signed. In view
of anti-spam measures it may be undesirable to hide the sender's
identity.
Additional mechanisms can be developed to protect against various IANA is requested to add "MMS" as a "WITH protocol types" under its
threats, however, these are not included in this version of this "MAIL Parameters" registry. The description is "Multimedia
specification. It is strongly RECOMMENDED that features such as Messaging Service"; the referece is to this document.
reply charging and sender identity hiding not be used across carrier
domains, and be used within carrier domains only with full
understanding of the risks involved.
4 IANA Considerations 5 Acknowledgements
No actions are requested of IANA. A number of people contributed to this document, especially the
members of the IETF Lemonade group, including Greg Vaudreuil. John
Klensin did a very thorough and helpful review. Greg White caught a
large number of nits. Ted Hardie was very helpful.
5 Normative References 6 Normative References
IETF: IETF:
[DSN-Msg] "An Extensible Message Format for Delivery Status [DSN-Msg] "An Extensible Message Format for Delivery Status
Notifications", Moore, Vaudreuil, RFC 3464, January 2003. Notifications", Moore, Vaudreuil, RFC 3464, January 2003.
[DSN-SMTP] "SMTP Service Extension for Delivery Status [DSN-SMTP] "SMTP Service Extension for Delivery Status
Notifications", Moore, RFC 3461, January 2003. Notifications", Moore, RFC 3461, January 2003.
[Hdr-Enc] "MIME (Multipurpose Internet Mail Extensions) Part Three: [Hdr-Enc] "MIME (Multipurpose Internet Mail Extensions) Part Three:
Message Header Extensions for Non-ASCII Text", Moore, RFC 2047, Message Header Extensions for Non-ASCII Text", Moore, RFC 2047,
November 1996. November 1996.
[KEYWORDS] Bradner, "Key words for use in RFCs to Indicate [KEYWORDS] Bradner, "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, Harvard University, March 1997. Requirement Levels", RFC 2119, Harvard University, March 1997.
[MDN] "Message Disposition Notification", Hansen, Vaudreuil, RFC [MDN] "Message Disposition Notification", Hansen, Vaudreuil, RFC
3798, May 2004. 3798, May 2004.
Gellens [Page 29] Expires November 2005 Gellens [Page 27] Expires March 2006
[Msg-Fmt] "Internet Message Format", Resnick, RFC 2822, April 2001. [Msg-Fmt] "Internet Message Format", Resnick, RFC 2822, April 2001.
[Report-Fmt] "The Multipart/Report Content Type for the Reporting of [Report-Fmt] "The Multipart/Report Content Type for the Reporting of
Mail System Administrative Messages", Vaudreuil, RFC 3462, January Mail System Administrative Messages", Vaudreuil, RFC 3462, January
2003 2003
[RESP] "Enhanced Mail System Status Codes", Vaudreuil, RFC 3463, [RESP] "Enhanced Mail System Status Codes", Vaudreuil, RFC 3463,
January 2003. January 2003.
[SMTP] "Simple Mail Transfer Protocol", Klensin, RFC 2821, April [SMTP] "Simple Mail Transfer Protocol", Klensin, RFC 2821, April
2001. 2001.
6 Informative References OMA:
OMA specifications are available at the OMA web site
<http://www.openmobilealliance.org>.
[OMA-MMS] OMA-WAP-MMS-ENC-V1_2-20040323-C
3GPP2 and 3GPP:
3GPP2 specifications are available at the 3GPP2 (Third
Generation Partnership Project 2) web site
<http://www.3gpp2.org>.
3GPP specifications are available at the 3GPP (Third Generation
Partnership Project) web site <http://www.3gpp.org>
[Stage_3] "MMS MM1 Stage 3 using OMA/WAP", X.S0016-310
"MMS MM4 Stage 3 Inter-Carrier Interworking", X.S0016-340
"Multimedia Messaging Service: Functional description; Stage 2", TS
23.140 Release 5.
7 Informative References
IETF: IETF:
[Auth] "SMTP Service Extension for Authentication", Myers, RFC 2554, [Auth] "SMTP Service Extension for Authentication", Myers, RFC 2554,
March 1999 March 1999
[BINARY] SMTP Service Extensions for Transmission of Large and [BINARY] SMTP Service Extensions for Transmission of Large and
Binary MIME Messages", Vaudreuil, Parsons, RFC 3030, December 2000. Binary MIME Messages", Vaudreuil, Parsons, RFC 3030, December 2000.
Gellens [Page 28] Expires March 2006
[Codes] "SMTP Service Extension for Returning Enhanced Error Codes", [Codes] "SMTP Service Extension for Returning Enhanced Error Codes",
Freed, RFC 2034, October 1996. Freed, RFC 2034, October 1996.
[Deliver-By] "Deliver By SMTP Service Extension", Newman, RFC 2852, [Deliver-By] "Deliver By SMTP Service Extension", Newman, RFC 2852,
June 2000. June 2000.
[Msg-Encap] "Proposed Standard for Message Encapsulation", Rose,
Stefferud, RFC 934, January 1985.
[Hdrs] "Common Internet Message Headers", J. Palme, RFC 2076, [Hdrs] "Common Internet Message Headers", J. Palme, RFC 2076,
February 1997. February 1997.
[IPSec] "Security Architecture for the Internet Protocol", Kent, [IPSec] "Security Architecture for the Internet Protocol", Kent,
Atkinson, RFC 2401, November 1998 Atkinson, RFC 2401, November 1998
[Mime-Sec-gw] "Gateways and MIME Security Multiparts", N. Feed, RFC
2480, January 1999.
[PGP] "MIME Security with OpenPGP", Elkins, Del Torto, Levien, [PGP] "MIME Security with OpenPGP", Elkins, Del Torto, Levien,
Roessler, RFC 3156, August 2001 Roessler, RFC 3156, August 2001
[SMIME] "S/MIME Version 3 Message Specification", Ramsdell, RFC [SMIME] "S/MIME Version 3 Message Specification", Ramsdell, RFC
2633, June 1999 2633, June 1999
[StartTLS] "SMTP Service Extension for Secure SMTP over Transport [StartTLS] "SMTP Service Extension for Secure SMTP over Transport
Layer Security", Hoffman, RFC 3207, February 2002 Layer Security", Hoffman, RFC 3207, February 2002
Gellens [Page 30] Expires November 2005
[Submission] "Message Submission", Gellens, Klensin, RFC 2476, [Submission] "Message Submission", Gellens, Klensin, RFC 2476,
December 1998. December 1998.
[VPIM] "Voice Profile for Internet Mail - version 2 (VPIMv2)", [VPIM] "Voice Profile for Internet Mail - version 2 (VPIMv2)",
Vaudreuil, Parsons, RFC 3801, June 2004. Vaudreuil, Parsons, RFC 3801, June 2004.
OMA:
OMA specifications are available at the OMA web site
<http://www.openmobilealliance.org>.
[OMA-MMS] OMA-WAP-MMS-ENC-V1_2-20040323-C
3GPP2 and 3GPP:
3GPP2 specifications are available at the 3GPP2 (Third
Generation Partnership Project 2) web site
<http://www.3gpp2.org>.
3GPP specifications are available at the 3GPP (Third Generation
Partnership Project) web site <http://www.3gpp.org>
[Stage_3] "MMS MM1 Stage 3 using OMA/WAP", X.S0016-310
"MMS MM4 Stage 3 Inter-Carrier Interworking", X.S0016-340
"Multimedia Messaging Service: Functional description; Stage 2", TS
23.140 Release 5.
[Formats] "Multimedia Messaging Service (MMS) Media Format and [Formats] "Multimedia Messaging Service (MMS) Media Format and
Codecs for cdma2000 Spread Spectrum Systems", C.S0045 Codecs for cdma2000 Spread Spectrum Systems", C.S0045
[Overview] "Multimedia Messaging Services (MMS) Overview", [Overview] "Multimedia Messaging Services (MMS) Overview",
X.S0016-000 X.S0016-000
[Stage_1] "Multimedia Messaging Services (MMS); Stage 1", [Stage_1] "Multimedia Messaging Services (MMS); Stage 1",
Requirements, October 2002, S.R0064-0. Requirements, October 2002, S.R0064-0.
[Stage_2] "Multimedia Messaging Service (MMS); Stage 2", Functional [Stage_2] "Multimedia Messaging Service (MMS); Stage 2", Functional
Specification, April 2003, X.S0016-200. Specification, April 2003, X.S0016-200.
"Multimedia Messaging Service; Media formats and codecs", "Multimedia Messaging Service; Media formats and codecs",
TS26.140Release 5. TS26.140Release 5.
Gellens [Page 31] Expires November 2005 Gellens [Page 29] Expires March 2006
7 Author's Address 8 Author's Address
Randall Gellens Randall Gellens
QUALCOMM Incorporated QUALCOMM Incorporated
5775 Morehouse Drive 5775 Morehouse Drive
San Diego, CA 92121 San Diego, CA 92121
randy@qualcomm.com randy@qualcomm.com
Appendix A: Changes Since Last Version
[ This section to be deleted upon publication ]
Changes from -04 to -05:
o Abstract now mentions use of X-MMS-* headers in MMS.
o Deleted "(MAY set to locally-generated value to hide sender
identity)" from Table 1.
o Deleted X-Priority from Table 1.
o Replaced comment with empty group syntax' header in section
2.1.3.2.
o Added Acknowledgements section.
o Removed distinction between SMTP/821 and ESMTP/2821.
o Removed discussion of sender address hiding.
o Removed content transformation.
o Replaced "Gateway" with reference to RFC 2821 Section 2.3.8.
o Deleted 'Resent-Count:'
o Deleted background information on resending/forwarding.
o Changed 'Received:' headder generation to MUST on MMS->Internet.
o Specified response code for "sensitivity" as per [VPIM].
o Changed "sensitivity" response code from SHOULD to MUST.
o Removed reference to RFC 934.
o Removed definition and mentions of anonymous remailer.
o Rewrote and greatly simplified Security Considerations.
o Added "MMS" as a "WITH protocol type" and requested IANA to
register this in its "MAIL Parameters" registry.
o Moved MMS references from Informative to Normative.
o Removed hand-waving about Message-ID.
o Attempted to clarify responsibility for report generation.
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed Intellectual Property Rights or other rights that might be claimed
to pertain to the implementation or use of the technology described to pertain to the implementation or use of the technology described
in this document or the extent to which any license under such in this document or the extent to which any license under such
rights might or might not be available; nor does it represent that rights might or might not be available; nor does it represent that
it has made any independent effort to identify any such rights. it has made any independent effort to identify any such rights.
Information on the procedures with respect to rights in RFC Information on the procedures with respect to rights in RFC
Gellens [Page 30] Expires March 2006
documents can be found in BCP 78 and BCP 79. documents can be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use attempt made to obtain a general license or permission for the use
of such proprietary rights by implementers or users of this of such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository specification can be obtained from the IETF on-line IPR repository
at http://www.ietf.org/ipr. at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
skipping to change at line 1432 skipping to change at line 1363
retain all their rights. retain all their rights.
This document and the information contained herein are provided on This document and the information contained herein are provided on
an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Gellens [Page 32] Expires November 2005 Gellens [Page 31] Expires March 2006
 End of changes. 109 change blocks. 
331 lines changed or deleted 262 lines changed or added

This html diff was produced by rfcdiff 1.27, available from http://www.levkowetz.com/ietf/tools/rfcdiff/