< draft-ietf-lemonade-mms-mapping-05.txt   draft-ietf-lemonade-mms-mapping-06.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-05.txt Qualcomm Document: draft-ietf-lemonade-mms-mapping-06.txt Qualcomm
Expires: March 2006 September 2005 Expires: April 2006 October 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.
skipping to change at line 42 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 March 2006
One important difference between MMS and Internet Mail is that MMS One important difference between MMS and Internet Mail is that MMS
uses headers which start with "X-Mms-" to carry a variety of user uses headers which start with "X-Mms-" to carry a variety of user
agent and server related information elements. agent and server related information elements.
Gellens [Page 1] Expires April 2006
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 SMTP and Internet message headers. from that used in SMTP and Internet message headers.
Gellens [Page 2] Expires March 2006 Gellens [Page 2] Expires April 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 . . . . . . . . . . . . . . . . . . . . . . . . . . 3
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: Information Element 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 13 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.3 Conversion of messages from Internet to MMS format 17
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 19
2.1.3.3.1 Table 4: Priority Mappings (Internet Message t 18 2.1.4 Report Generation and Conversion . . . . . . . . . . . 22
2.1.4 Report Generation and Conversion . . . . . . . . . . 19 2.1.4.1 Delivery Report Mapping from MMS to Internet Messa 22
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 23
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 24
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 25
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 26
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 27
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 28
2.1.4.4 Disposition Report Mapping from Internet Message t 25 2.1.4.4.1 Table 8: Disposition Report Mappings (Internet 28
2.1.4.4.1 Table 8: Disposition Report Mappings (Internet 25 2.1.5 Message Delivery . . . . . . . . . . . . . . . . . . 29
2.1.5 Message Delivery . . . . . . . . . . . . . . . . . . . 26 3 Security Considerations . . . . . . . . . . . . . . . . . . . 29
3 Security Considerations . . . . . . . . . . . . . . . . . . . 26 4 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
4 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 5 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 30
5 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 27 6 Normative References . . . . . . . . . . . . . . . . . . . . 30
6 Normative References . . . . . . . . . . . . . . . . . . . . . 27 7 Informative References . . . . . . . . . . . . . . . . . . . . 31
7 Informative References . . . . . . . . . . . . . . . . . . . 28 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . 32
8 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 29 Appendix A: Changes Since Last Version . . . . . . . . . . . . 33
Appendix A: Changes Since Last Version . . . . . . . . . . . . 30 Intellectual Property Statement . . . . . . . . . . . . . . . 34
Intellectual Property Statement . . . . . . . . . . . . . . . . 30 Full Copyright Statement . . . . . . . . . . . . . . . . . . . 34
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 March 2006 Gellens [Page 3] Expires April 2006
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
skipping to change at line 148 skipping to change at line 147
--------------------|---------------------------------------------- --------------------|----------------------------------------------
Body |The portion of an [SMTP] message's Content 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).
--------------------|---------------------------------------------- --------------------|----------------------------------------------
Gellens [Page 4] Expires April 2006
--------------------|----------------------------------------------
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
|the Body. Envelope information only exists |the Body. While some of it may be copied into
|while the message is in transit, and contains |the Content on delivery, envelope information
|information used by SMTP agents (MTAs). |only exists while the message is in transit,
|and contains information used by SMTP agents
|(MTAs).
--------------------|----------------------------------------------
Gateway |See [SMTP], Section 2.3.8.
--------------------|---------------------------------------------- --------------------|----------------------------------------------
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 |See [SMTP], Section 2.3.8. Relay/Server |An MMS server. See [Stage_2]. For purposes
|of this document, an MMS Relay/Server acts as
|a gateway when it receives or sends messages
|via Internet mail.
--------------------|---------------------------------------------- --------------------|----------------------------------------------
User Agent |An MMS or Email user agent User Agent |An MMS or Email user agent
--------------------|---------------------------------------------- --------------------|----------------------------------------------
Gellens [Page 5] Expires March 2006 Gellens [Page 5] Expires April 2006
1.4 Abbreviations 1.4 Abbreviations
--------|---------------------------------------------------------- --------|----------------------------------------------------------
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].
--------|---------------------------------------------------------- --------|----------------------------------------------------------
skipping to change at line 222 skipping to change at line 229
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]. the requirements of [SMTP].
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 SMTP envelope values) needed for the transfer header fields and SMTP envelope values) needed for the transfer
protocol. protocol.
Gellens [Page 6] Expires March 2006 Gellens [Page 6] Expires April 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 SMTP 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 converts incoming messages to the MM format used within
within the receiving system. the receiving system.
The MMS Relay/Server MAY convert control information received from The MMS Relay/Server converts control information received from the
the Internet mail server into appropriate information elements of an 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 SMTP 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, implementations conforming to addition to converting report MMs, implementations conforming to
this document MUST generate standard Internet Message delivery and this document MUST generate standard Internet Message delivery and
disposition reports for received Internet messages as appropriate. disposition reports for received Internet messages as appropriate.
See section 2.1.4 for more information. See section 2.1.4 for more information.
Gellens [Page 7] Expires March 2006 Gellens [Page 7] Expires April 2006
2.1.3 MMS Information Element Mappings 2.1.3 MMS Information Element Mappings
The mappings between MMS elements and SMTP/Internet Message elements The mappings between MMS elements and SMTP/Internet Message elements
(either [SMTP] parameters, [Msg-Fmt] headers, or both) are ([SMTP] parameters, [Msg-Fmt] headers, and [Dsn-Msg] fields) 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: Information Element 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: |Message-ID: Message ID |N/A |Message-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: |From: Sender's address |MAIL FROM |From: |From:
|address if | | |address if | |
|user-originated; | | |user-originated; | |
|MUST set MAIL | | |MUST set MAIL | |
|FROM to null | | |FROM to null | |
|("<>") for all | | |("<>") for all | |
skipping to change at line 298 skipping to change at line 304
|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 March 2006 Gellens [Page 8] Expires April 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 348 skipping to change at line 354
_________________|_________________|________________|______________ _________________|_________________|________________|______________
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 March 2006 Gellens [Page 9] Expires April 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:
_________________|_________________|________________|______________ _________________|_________________|________________|______________
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 | | | Previously-
| | | Sent-Date: | | | Sent-Date-
| | | and-Time:
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Hop/host trace |N/A |Received: |(Not sup- Hop/host trace |N/A |Received: |(Not sup-
| | |ported) | | |ported)
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Sensitivity |N/A |Sensitivity: see|N/A Sensitivity |N/A |Sensitivity: see|N/A
| |Note 1 | | |Note 1 |
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Content |N/A |<message body> |<message body> Content |N/A |<message body> |<message body>
=================|=================|================|============== =================|=================|================|==============
skipping to change at line 394 skipping to change at line 401
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.
Message Type (of PDU) Message Type (of PDU)
Gellens [Page 10] Expires March 2006 Gellens [Page 10] Expires April 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
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, per [Msg-Fmt]. be created, with a unique value, per [Msg-Fmt].
The message ID SHOULD be transmitted in the [SMTP] envelope as the
ENVID parameter, as specified in [DSN-SMTP].
To facilitate the case where an MMS message traverses the Internet To facilitate the case where an MMS message traverses the Internet
prior to returning to an MMS system, implementations might wish to prior to returning to an MMS system, implementations might wish to
retain the 'X-Mms-Message-Id:' header. Such systems should be aware retain the 'X-Mms-Message-Id:' header. Such systems should be aware
that headers which begin with "X-" might be removed during transit that headers which begin with "X-" might be removed during transit
through Internet MTAs. 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:', 'Cc:', or appear in a 'To:' or 'Cc:' header. At least one 'To:', 'Cc:', or
'Bcc:' header MUST be present. If all recipients are undisclosed, a 'Bcc:' header MUST be present. If none are present, a 'To:' header
'To:' header SHOULD be created using empty group syntax whose name SHOULD be created using empty group syntax whose name gives an
gives an indication to a human reader, for example 'To: indication to a human reader, for example 'To:
undisclosed-recipients:;'. undisclosed-recipients:;'.
The 'To:' header SHOULD NOT appear more than once. The 'Cc:' header The 'To:' header SHOULD NOT appear more than once. The 'Cc:' header
SHOULD NOT appear more than once. 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 headers. Non-7-bit characters in an
non-7-bit characters in a phrase part of an address header) MUST be address domain must be encoded with [IDN]. If there are any
encoded according to [Hdr-Enc]. Non-7-bit characters in the local part of an address, the message
MUST be rejected. Non-7-bit characters elsewhere in a header MUST
be encoded according to [Hdr-Enc].
All recipient addresses in the [SMTP] envelope must be All recipient addresses in the [SMTP] envelope must be
fully-qualified in accordance with [SMTP]. In particular, messages fully-qualified in accordance with [SMTP]. In particular, messages
MUST NOT be sent to an Internet mail system with an E.164 numbers MUST NOT be sent to an Internet mail system with an unqualified
instead of a fully-qualified domain name. E.164 number (i.e., a number with no domain) instead of a
fully-qualified domain name.
All addresses in 'To:', 'Cc:', and 'Bcc:' headers SHOULD be in the All addresses in 'To:', 'Cc:', and 'Bcc:' headers MUST be in the
form of fully-qualified domains. Unqualified E.164 numbers SHOULD form of fully-qualified domains. Unqualified E.164 numbers MUST NOT
NOT be used. be used.
Gellens [Page 11] Expires March 2006 Gellens [Page 11] Expires April 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. header.
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 ('X-Mms-Message-Class: Personal') SHOULD be transmitted in the
[SMTP] envelope as the MAIL FROM value. [SMTP] envelope as the MAIL FROM value.
The return addresses in the [SMTP] envelope must be fully-qualified The return addresses in the [SMTP] envelope must be fully-qualified
in accordance with [SMTP]. In particular, messages MUST NOT be sent in accordance with [SMTP]. In particular, messages MUST NOT be sent
to an Internet mail system with an E.164 numbers instead of a to an Internet mail system with an E.164 number instead of a
fully-qualified domain name. fully-qualified domain name. Note that qualified E.164 numbers,
that is, those that contain an E.164 number as the local-part of an
address that also includes a domain, are acceptable.
The address(es) in the 'From:' header SHOULD be in the form of The address(es) in the 'From:' header SHOULD be in the form of
fully-qualified domains. Unqualified E.164 numbers SHOULD NOT be fully-qualified domains. Unqualified E.164 numbers SHOULD NOT be
used. 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 headers. Non-7-bit characters in an
non-7-bit characters in a phrase part of an address header) MUST be address domain must be encoded with [IDN]. If there are any
encoded according to [Hdr-Enc]. Note that it would be possible to Non-7-bit characters in the local part of an address, the message
define an [SMTP] extension to permit transmission of unencoded 8-bit MUST be rejected. Non-7-bit characters elsewhere in a header MUST
characters, but in the absence of such an extension [Hdr-Enc] MUST be encoded according to [Hdr-Enc]. Note that it would be possible
be used. to define an [SMTP] extension to permit transmission of unencoded
8-bit characters, but in the absence of such an extension [Hdr-Enc]
MUST 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. The 'Content-Type:' header SHOULD be preserved.
Message class Message class
The 'X-Mms-Message-Class:' header MAY be retained in order to The 'X-Mms-Message-Class:' header MAY be retained in order to
provide information on the source of the message. A 'Precedence: 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 March 2006 Gellens [Page 12] Expires April 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 [SMTP] envelope by using the DELIVER-BY transmitted in the [SMTP] envelope by using the DELIVER-BY extension
extension, as specified in [Deliver-By]. with a by-mode of "R", as specified in [Deliver-By].
Note that the [SMTP] 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
skipping to change at line 520 skipping to change at line 531
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 [SMTP] 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.
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. be transmitted using an 'Importance:' header.
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. Gellens [Page 13] Expires April 2006
Normal importance messages should omit the 'Importance:' header.
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: Normal |[omit]
---------------------------|----------------------
'X-Mms-Priority: Low |'X-Priority: 4 (low)'
---------------------------|----------------------
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 currently supported. Support for sender address hiding is not currently supported.
A message that contains an 'X-Mms-Sender-Visibility:' header with a
value of 'Hide' SHOULD be rejected.
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.
skipping to change at line 590 skipping to change at line 590
have been properly addressed, reply charging SHOULD NOT be honored have been properly addressed, reply charging SHOULD NOT be honored
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 is possible for an [SMTP] extension to be defined which would it is possible for an [SMTP] extension to be defined which would
permit transmission of unencoded 8-bit characters, but in the permit transmission of unencoded 8-bit characters, but in the
absence of such an extension [Hdr-Enc] must be used. absence of such an extension [Hdr-Enc] MUST be used.
Resending Resending
Gellens [Page 14] Expires April 2006
A message may be resent to one or more new recipients; it may be A message may be resent to one or more new recipients; it may be
resent more than once; each time new 'Resent-' headers SHOULD be resent more than once; each time new 'Resent-' headers are added at
added at the top of the message. Thus, if more than one series of the top of the existing headers. Thus, if more than one series of
'Resent-' headers are present, the original series is the last; the 'Resent-' headers are present, the original series is the last; the
most recent is the first. most recent is the first.
Forward counter Forward counter
An 'X-Mms-Forward-Counter:' header, if present, SHOULD be removed.
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
user who directed the message to be resent.
A 'Resent-Date:' header SHOULD be added to indicate the time and MMS lists the resending history of a message in two headers:
date that the message was resent. 'X-Mms-Previously-Sent-By:' and
'X-Mms-Previously-Sent-Date-and-Time:'. 'X-Mms-Previously-Sent-By:'
contains a number followed by one or more addresses.
'X-Mms-Previously-Sent-Date-and-Time:' contains a number followed by
a date-time. With both headers, the number "0" is used for the
entry that corresponds to the original submission of the message,
with higher values being used for each subsequent resending. The
final (most recent) resending information is in the 'From:' and
'Date:' headers. There is also an 'X-Mms-Forward-Counter:' that
indicates how many times the message has been resent.
Any 'X-Mms-Previously-Sent-By:' and 'X-Mms-Previously-Sent-Date' Any 'X-Mms-Previously-Sent-By:',
'X-Mms-Previously-Sent-Date-and-Time:', and 'X-Mms-Forward-Counter:'
headers, if present, SHOULD be removed. The information contained headers, if present, SHOULD be removed. The information contained
in them SHOULD be translated into 'From:', 'Resent-To:', in them SHOULD be translated into [Msg-Fmt] headers as follows:
'Resent-From:', and 'Resent-Date:' headers. The original sender of
the message SHOULD appear in the 'From:' header; the original The 'X-Mms-Previously-Sent-Date-and-Time:' header whose value starts
recipient(s) SHOULD appear in the 'To:' header; the time and date with "0" SHOULD be used to create a 'Date:' header, converting the
the message was originally sent SHOULD appear in the 'Date:' header. date and time from HTTP-date [HTTP] to date-time [Msg-Fmt]. The
The most recent sender SHOULD appear in the top-most 'Resent-From:' 'X-Mms-Previously-Sent-By:' header whose value starts with "0"
header; the most recent recipient(s) SHOULD appear in the top-most SHOULD be used to create a 'From:' header.
'Resent-To:' header; the time and date the message was most recently
sent SHOULD appear in the top-most 'Resent-Date:' header. A 'To:' header SHOULD be created using list syntax with a value of
"unrecoverable-recipients" and no mailboxes.
A 'Message-ID:' header SHOULD be created.
Any 'X-Mms-Previously-Sent-Date-and-Time:' headers whose value
starts with "1" or a larger value are mapped to 'Resent-Date:'
headers. Any 'X-Mms-Previously-Sent-By:' headers whose value starts
with "1" or a larger value are mapped to 'Resent-By:' headers.
Gellens [Page 15] Expires April 2006
The 'From:', 'To:', 'Date:', and 'Message-ID:' headers are mapped to
'Resent-From:', 'Resent-To:', 'Resent-Date:', and
'Resent-Message-ID:' headers in the top-most block of 'Resent-*'
headers.
Example:
The MMS message:
X-Mms-Forward-Counter: 2
X-Mms-Previously-Sent-Date-and-Time: 0, Fri, 01 Apr 2005 06:02:03 GMT
X-Mms-Previously-Sent-By: 0, General Failure <mfail@example.mil>
X-Mms-Previously-Sent-Date-and-Time: 1, Fri, 01 Apr 2005 08:02:03 GMT
X-Mms-Previously-Sent-By: 1, Colonel Corn <gcorn@example.mil>
Date: Fri, 1 Apr 2005 18:02:03 -0800
From: L. Eva Message <lem@example.org>
To: b1ff@mms.example.com
Message-ID: <99887766.112233@mail.example.org>
is mapped to an Internet mail message:
Resent-Date: Fri, 1 Apr 2005 18:02:03 -0800
Resent-From: L. Eva Message <lem@example.org>
Resent-To: b1ff@mms.example.com
Resent-Message-ID: <99887766.112233@mail.example.org>
Resent-Date: Fri, 1 Apr 2005 08:02:03 +0000
Resent-From: Colonel Corn <gcorn@example.mil>
Date: Fri, 1 Apr 2005 06:02:03 +0000
From: General Failure <mfail@example.mil>
To: Colonel Corn <gcorn@example.mil>
Message-ID: <000.000.000@gateway.example.org>
'Received:' Headers 'Received:' Headers
When a message is gatewayed from MMS to Internet mail, a 'Received:' When a message is gatewayed from MMS to Internet mail, a 'Received:'
header MUST be added as per [SMTP]. The "with" clause should header MUST be added as per [SMTP]. The "with" clause should
specify "MMS". specify "MMS".
Gellens [Page 15] Expires March 2006
A message MAY be rejected if the number of 'Received:' headers A message MAY be rejected if the number of 'Received:' headers
exceeds a locally-defined maximum, which MUST conform to [SMTP] exceeds a locally-defined maximum, which MUST conform to [SMTP]
section 6.2 and SHOULD be no less than 100. 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].
Gellens [Page 16] Expires April 2006
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 US-ASCII CR
charset encodings that do not have this property cannot be used in LF octets, thus charset encodings that do not have this property
text/* body parts. (They may be used in other body parts, but only cannot be used in text/* body parts. (They may be used in other body
when they are suitable encoded or when binary transmission has been parts, but only when they are suitably encoded or when binary
negotiated.) In particular, MMS allows UTF-16, while Internet transmission has been negotiated.) In particular, MMS allows UTF-16,
message format does not. UTF-16 encoding MUST be translated to while Internet message format does not. UTF-16 encoding MUST be
UTF-8 or another charset and encoding which is suitable for use in translated to UTF-8 or another charset and encoding which is
Internet message format/protocols. suitable for use in Internet message format/protocols.
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
skipping to change at line 687 skipping to change at line 736
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. be created, with a unique value.
Recipient(s) address Recipient(s) address
'To:' and 'Cc:' headers MUST be retained. 'To:' and 'Cc:' headers MUST be retained.
Gellens [Page 16] Expires March 2006
Each recipient contained in the [SMTP] envelope (RCPT TO values) Each recipient contained in the [SMTP] envelope (RCPT TO values)
MUST be considered a recipient of the message. Recipients who MUST be considered a recipient of the message. Recipients who
appear in address headers but not the [SMTP] envelope MUST be appear in address headers but not the [SMTP] envelope MUST be
ignored. Recipients who appear in the [SMTP] envelope but do not ignored. Recipients who appear in the [SMTP] envelope but do not
appear in headers are considered "blind" (Bcc) recipients; such appear in headers are considered "blind" (Bcc) recipients; such
recipients MUST NOT be added to message headers (including address recipients MUST NOT be added to message headers (including address
and trace headers) unless there is only one recipient total. and trace headers) unless there is only one recipient total.
Gellens [Page 17] Expires April 2006
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
An 'X-Mms-Message-Class: personal' header MAY be created for all An 'X-Mms-Message-Class: personal' header MAY 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 with a
specified in [Deliver-By]. by-mode of "R", as specified in [Deliver-By].
If the by-mode is "N", a "relayed" DSN MUST be issued per
[Deliver-By] and an 'X-Mms-Expiry:' header SHOULD NOT be created.
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.
message arrives via [SMTP] relay containing an earliest time of
delivery in the AFTER extension, it MAY be rejected. If a message
is submitted via Message Submission [Submission] containing an
earliest time of delivery in the AFTER extension, it MUST either be
retained until the delivery time arrives, or it may be immediately
rejected. It MUST NOT be delivered or further relayed prior to the
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 Importance
Priority
The message sender's importance value (also called "priority",
although this can be confused with class-of-service values) is
expressed with an 'Importance:' header. Historically, some clients
used the older and non-standard 'X-Priority:' header for this
purpose. As a result, some clients generate both.
Gellens [Page 18] Expires April 2006
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. If both headers are
present, 'Importance:' SHOULD be used. 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'
-------------------------------|---------------------- -------------------------------|----------------------
skipping to change at line 764 skipping to change at line 816
-------------------------------|---------------------- -------------------------------|----------------------
'Importance: Normal' | [omitted] 'Importance: Normal' | [omitted]
-------------------------------|---------------------- -------------------------------|----------------------
'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 importance messages SHOULD omit the 'X-Mms-Priority:' header.
Sender visibility Sender visibility
Support for sender address hiding is not currently supported. Support for sender address hiding is not currently supported.
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 Resending
One or more sets of 'Resent-' headers, if present, SHOULD be mapped Mapping from 'Resent-' and other [Msg-Fmt] headers to
to 'To:', 'From:', 'Date:', and 'X-Mms-Previously-Sent-' headers. 'X-Mms-Previously-Sent-' headers SHOULD be done as follows:
The original 'From:' header is mapped to an
'X-Mms-Previously-Sent-By:' header with a leading "0" value. The
value of the top-most 'Resent-From:' header is mapped to the 'From:'
header. The value of each subsequent 'Resent-From:' header is
Gellens [Page 19] Expires April 2006
mapped to an 'X-Mms-Previously-Sent-By:' header with the next larger
leading value.
The original 'Date:' header is mapped to
'X-Mms-Previously-Sent-Date-and-Time:' header with a leading "0"
value. Note that the value is also converted from date-time syntax
[Msg-Fmt] to HTTP-date syntax [HTTP]. The value of the top-most
'Resent-Date:' header is mapped to the 'Date:' header. The value of
each subsequent 'Date:' header is mapped to an
'X-Mms-Previously-Sent-Date-and-Time:' header with the next larger
leading value.
If one or more 'Resent-Message-ID:' headers are present, the
top-most one SHOULD be mapped to 'Message-ID:'; otherwise the
'Message-ID:' header should be retained.
An 'X-Mms-Forward-Counter:' header SHOULD be created when 'Resent-'
headers have been mapped to 'X-Mms-Previously-Sent-' headers. Its
value SHOULD be the number of 'Resent-' blocks that existed prior to
mapping.
Example:
The original message:
Date: Fri, 1 Apr 2005 14:02:03 -0800
From: General Failure <mfail@example.mil>
To: Colonel Corn <gcorn@example.mil>
Message-ID: <msg123@mail.example.mil>
Is resent by Colonel Corn to L. Eva Message:
Resent-Date: Fri, 1 Apr 2005 16:02:03 -0800
Resent-From: Colonel Corn <gcorn@example.mil>
Resent-To: L. Eva Message <lem@example.org>
Resent-Message-ID: <msg234@mail.example.mil>
Date: Fri, 1 Apr 2005 14:02:03 -0800
From: General Failure <mfail@example.mil>
To: Colonel Corn <gcorn@example.mil>
Message-ID: <msg123@mail.example.mil>
L. Eva then resends to her MMS device:
Resent-Date: Fri, 1 Apr 2005 18:02:03 -0800
Resent-From: L. Eva Message <lem@example.org>
Resent-To: b1ff@mms.example.com
Resent-Message-ID: <99887766.112233@mail.example.org>
Resent-Date: Fri, 1 Apr 2005 16:02:03 -0800
Resent-From: Colonel Corn <gcorn@example.mil>
Gellens [Page 20] Expires April 2006
Resent-To: L. Eva Message <lem@example.org>
Resent-Message-ID: <msg234@mail.example.mil>
Date: Fri, 1 Apr 2005 14:02:03 -0800
From: General Failure <mfail@example.mil>
To: Colonel Corn <gcorn@example.mil>
Message-ID: <msg123@mail.example.mil>
This would be mapped to an MMS message as:
X-Mms-Forward-Counter: 2
X-Mms-Previously-Sent-Date-and-Time: 0, Fri, 01 Apr 2005 06:02:03 GMT
X-Mms-Previously-Sent-By: 0, General Failure <mfail@example.mil>
X-Mms-Previously-Sent-Date-and-Time: 1, Fri, 01 Apr 2005 08:02:03 GMT
X-Mms-Previously-Sent-By: 1, Colonel Corn <gcorn@example.mil>
Date: Fri, 1 Apr 2005 18:02:03 -0800
From: L. Eva Message <lem@example.org>
To: b1ff@mms.example.com
Message-ID: <99887766.112233@mail.example.org>
Note that the original 'From:' and 'Date:' values were moved to
'X-Mms-Previously-Sent-By:' and
'X-Mms-Previously-Sent-Date-and-Time:' headers with a leading "0"
value. The first 'Resent-From:' and 'Resent-Date:' values were
moved to a second set of 'X-Mms-Previously-Sent-' headers, with a
leading "1" value. The third set of 'Resent-' headers were moved to
the 'Date:', 'To:', and 'From:' headers.
Note also that the format of the date and time differs between the
'Date:' / 'Resent-Date:' and the
'X-Mms-Previously-Sent-Date-and-Time:' headers, in that the latter
use HTTP-date [HTTP] instead of date-time [Msg-Fmt].
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 MUST NOT be sent to an MMS system. The 'Sensitivity:' header MUST NOT be sent to an MMS system. The
associated negative delivery status report MUST include the extended associated negative delivery status report MUST include the extended
Gellens [Page 21] Expires April 2006
status code [RESP] 5.6.0 as specified in [VPIM] ("Other or undefined status code [RESP] 5.6.0 as specified in [VPIM] ("Other or undefined
protocol status") indicating that privacy could not be assured. protocol status") indicating that privacy could not be assured.
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
skipping to change at line 834 skipping to change at line 976
An implementation conforming to this specification MUST convert An implementation conforming to this specification MUST convert
reports received from one side (MMS or Internet mail) destined for reports received from one side (MMS or Internet mail) destined for
the other. In addition, reports MUST be generated as appropriate the other. In addition, reports MUST be generated as appropriate
for messages received from either side. For example, if an MM to be for messages received from either side. For example, if an MM to be
sent via Internet mail is not deliverable, a delivery status MM sent via Internet mail is not deliverable, a delivery status MM
shall be generated. Likewise, if an Internet message is received shall be generated. Likewise, if an Internet message is received
that cannot be further relayed or delivered, a delivery status that cannot be further relayed or delivered, a delivery status
report [DSN-Msg] MUST be generated. report [DSN-Msg] MUST be 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 optional third subpart is of type message/rfc822 and includes the
optionally the body of the referenced (original) message. headers and optionally the body of the referenced (original)
message. Note that, per [Dsn-Msg], the 'DSN-Gateway:' field in
delivery reports MUST be created.
Gellens [Page 22] Expires April 2006
2.1.4.1 Delivery Report Mapping from MMS to Internet Message 2.1.4.1 Delivery Report Mapping from MMS to Internet Message
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: |'Message-ID:' preserved in third
delivery status is | |per-message fields (use value of delivery status is | |subpart of delivery report.
being reported | |ENVID from SMTP envelope if avail- being reported | |
| |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
| |return-path of message being
| |reported, not its 'From:' header
| |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 20] Expires March 2006 Gellens [Page 23] Expires April 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 931 skipping to change at line 1069
* 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 21] Expires March 2006 Gellens [Page 24] Expires April 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.
Note that a single DSN which reports multiple recipients will result
in several MMS delivery reports.
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
|Report Element | |Report Element |
===================|==================|================================ ===================|==================|================================
ID of the original |Message-Id: |'Original-Envelope-ID' field of ID of the original |Message-Id: |'Message-ID:' header preserved
message (object of | |per-message fields. If not message (object of | |in third sub-part of report.
delivery report) | |available, the 'Message-ID' delivery report) | |
| |header field of the message
| |being reported, if included in
| |the third part, may be
| |substituted.
-------------------|------------------|-------------------------------- -------------------|------------------|--------------------------------
Recipient address |From: |If available, the 'Original Recipient address |From: |If available, the 'Original
of the original | |-Recipient' field of the per- of the original | |-Recipient' field of the per-
message (object of | |recipient section should be message (object of | |recipient section should be
delivery report) | |used; otherwise the 'Final- delivery report) | |used; otherwise the 'Final-
| |Recipient' field of the per- | |Recipient' field of the per-
| |recipient section is used | |recipient section is used
-------------------|------------------|-------------------------------- -------------------|------------------|--------------------------------
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 22] Expires March 2006 Gellens [Page 25] Expires April 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
|Set to one of the | |Set to one of the |
skipping to change at line 1002 skipping to change at line 1138
|'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 23] Expires March 2006 Gellens [Page 26] Expires April 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: |'Message-ID:' header preserved in
message (object of | |value of ENVID from [SMTP] envelope message (object of | |third part of report.
read report) | |if available, 'Message-ID:' read report) | |
| |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-
| |Notification-To:' header field of | |Notification-To:' header field of
| |message being reported, not its | |message being reported, not its
| |'From:' header field. | |'From:' header 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
----------------------|------------|----------------------------------- ----------------------|------------|-----------------------------------
Disposition of message|X-Mms-Read- |Disposition-field Disposition of message|X-Mms-Read- |Disposition-field
being reported | Status: | being reported | Status: |
| |For MMS-Read-Status value 'read', | |For X-MMS-Read-Status value 'read',
| |use 'disposition-type' value | |use 'disposition-type' value
| |'displayed'; for MMS-Read-Status | |'displayed'; for X-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 [SMTP] on MM3: received using [SMTP] on MM3:
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 .
Gellens [Page 27] Expires April 2006
* 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
report as specified in [MDN] to the format of an MMS read report. report as specified in [MDN] to the format of an MMS read report.
2.1.4.4.1 Table 8: Disposition Report Mappings (Internet Message to 2.1.4.4.1 Table 8: Disposition Report Mappings (Internet Message to
MMS) MMS)
===================|==================|================================ ===================|==================|================================
Information Element|MMS Read Report |[MDN] Element Information Element|MMS Read Report |[MDN] Element
|Element | |Element |
===================|==================|================================ ===================|==================|================================
ID of the original |Message-Id: |'Original-Envelope-ID' field ID of the original |Message-Id: |'Message-ID:' header preserved
message (object of | | message (object of | |in third subpart of report.
disposition report)| | disposition report)| |
-------------------|------------------|-------------------------------- -------------------|------------------|--------------------------------
Recipient address |From: |'Final-Recipient' field Recipient address |From: |'Final-Recipient' field
of the original | | of the original | |
message | | message | |
-------------------|------------------|-------------------------------- -------------------|------------------|--------------------------------
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 '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 25] Expires March 2006 Gellens [Page 28] Expires April 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: |
| | | |
|'read' (used for | |'read' (used for |
skipping to change at line 1135 skipping to change at line 1270
Agent. Agent.
3 Security Considerations 3 Security Considerations
Both MMS and Internet mail have their own set of security risks and Both MMS and Internet mail have their own set of security risks and
considerations. This document specifies how to exchange messages considerations. This document specifies how to exchange messages
between these two environments, so it is only appropriate to discuss between these two environments, so it is only appropriate to discuss
considerations specific to this functionality, not those inherent in considerations specific to this functionality, not those inherent in
either environment. either environment.
Gellens [Page 26] Expires March 2006 Gellens [Page 29] Expires April 2006
When a message uses end-to-end security mechanisms such as [PGP] or When a message uses end-to-end security mechanisms such as [PGP] or
S/MIME [SMIME], servers MUST be careful not to accidently destroy S/MIME [SMIME], servers MUST be careful not to accidently destroy
the integrity of the protected content (for example, by altering any the integrity of the protected content (for example, by altering any
text within the region covered by a signature while mapping between text within the region covered by a signature while mapping between
MMS and email). [Mime-Sec-gw] discusses issues with use of such MMS and email). [Mime-Sec-gw] discusses issues with use of such
mechanisms in gateways. mechanisms in gateways.
Some MMS features contain inherently more risk than others, Some MMS features contain inherently more risk than others,
including reply charging and sender address hiding. Support for including reply charging and sender address hiding. Support for
these mechanisms are not included in this document. these mechanisms are not included in this document.
4 IANA Considerations 4 IANA Considerations
IANA is requested to add "MMS" as a "WITH protocol types" under its IANA is requested to add "MMS" as a "WITH protocol types" under its
"MAIL Parameters" registry. The description is "Multimedia "MAIL Parameters" registry. The description is "Multimedia
Messaging Service"; the referece is to this document. Messaging Service"; the reference is to this document.
5 Acknowledgements 5 Acknowledgments
A number of people contributed to this document, especially the A number of people contributed to this document, especially the
members of the IETF Lemonade group, including Greg Vaudreuil. John members of the IETF Lemonade group, including Greg Vaudreuil. John
Klensin did a very thorough and helpful review. Greg White caught a Klensin did a very thorough and helpful review. Greg White caught a
large number of nits. Ted Hardie was very helpful. large number of nits. Ted Hardie was very helpful. Alexey Melnikov
and Chris Newman sent very useful and detailed comments.
6 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.
[HTTP] "Hypertext Transfer Protocol -- HTTP/1.1", Fielding et al,
RFC 2616, June 1999.
[IDN] "Internationalizing Domain Names in Applications (IDNA)",
Faltstrom, Hoffman, Costello, RFC 3490, March 2003.
Gellens [Page 30] Expires April 2006
[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 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
skipping to change at line 1221 skipping to change at line 1363
"MMS MM4 Stage 3 Inter-Carrier Interworking", X.S0016-340 "MMS MM4 Stage 3 Inter-Carrier Interworking", X.S0016-340
"Multimedia Messaging Service: Functional description; Stage 2", TS "Multimedia Messaging Service: Functional description; Stage 2", TS
23.140 Release 5. 23.140 Release 5.
7 Informative References 7 Informative References
IETF: IETF:
[Auth] "SMTP Service Extension for Authentication", Myers, RFC 2554, Gellens [Page 31] Expires April 2006
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.
[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, [Mime-Sec-gw] "Gateways and MIME Security Multiparts", N. Freed, RFC
Atkinson, RFC 2401, November 1998
[Mime-Sec-gw] "Gateways and MIME Security Multiparts", N. Feed, RFC
2480, January 1999. 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
Layer Security", Hoffman, RFC 3207, February 2002
[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.
[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",
skipping to change at line 1274 skipping to change at line 1407
[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 29] Expires March 2006
8 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
Gellens [Page 32] Expires April 2006
randy@qualcomm.com randy@qualcomm.com
Appendix A: Changes Since Last Version Appendix A: Changes Since Last Version
[ This section to be deleted upon publication ] [ This section to be deleted upon publication ]
Changes from -05 to -06:
o Editorial cleanups
o Clarified that X-Priority is an older, non-standard header.
Clarified that if both X-Priority and Importance appear,
Importance SHOULD be used.
o Clarified text regarding E.164 numbers
o Changed SHOULD NOT to MUST NOT on unqualified E.164 numbers in
address headers (otherwise messages are non-replyable)
o Deleted X-Priority mapping table from MMS to Internet Mail
o Deleted wording (accidently pasted) in table on Delivery Report
Mappings (MMS to Internet Message)
o Deleted unused [Auth], [IPSec], and [StartTLS] references
o Rewrote text on mapping between Resent- and
X-Mms-Previously-Sent- headers.
o Corrected text that confused Envelope-ID and Message-ID.
Changes from -04 to -05: Changes from -04 to -05:
o Abstract now mentions use of X-MMS-* headers in MMS. o Abstract now mentions use of X-MMS-* headers in MMS.
o Deleted "(MAY set to locally-generated value to hide sender o Deleted "(MAY set to locally-generated value to hide sender
identity)" from Table 1. identity)" from Table 1.
o Deleted X-Priority from Table 1. o Deleted X-Priority from Table 1.
o Replaced comment with empty group syntax' header in section o Replaced comment with empty group syntax' header in section
2.1.3.2. 2.1.3.2.
o Added Acknowledgements section. o Added Acknowledgements section.
o Removed distinction between SMTP/821 and ESMTP/2821. o Removed distinction between SMTP/821 and ESMTP/2821.
o Removed discussion of sender address hiding. o Removed discussion of sender address hiding.
skipping to change at line 1313 skipping to change at line 1463
o Changed "sensitivity" response code from SHOULD to MUST. o Changed "sensitivity" response code from SHOULD to MUST.
o Removed reference to RFC 934. o Removed reference to RFC 934.
o Removed definition and mentions of anonymous remailer. o Removed definition and mentions of anonymous remailer.
o Rewrote and greatly simplified Security Considerations. o Rewrote and greatly simplified Security Considerations.
o Added "MMS" as a "WITH protocol type" and requested IANA to o Added "MMS" as a "WITH protocol type" and requested IANA to
register this in its "MAIL Parameters" registry. register this in its "MAIL Parameters" registry.
o Moved MMS references from Informative to Normative. o Moved MMS references from Informative to Normative.
o Removed hand-waving about Message-ID. o Removed hand-waving about Message-ID.
o Attempted to clarify responsibility for report generation. o Attempted to clarify responsibility for report generation.
Gellens [Page 33] Expires April 2006
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 1355 skipping to change at line 1504
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 31] Expires March 2006 Gellens [Page 34] Expires April 2006
 End of changes. 100 change blocks. 
200 lines changed or deleted 349 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/