draft-ietf-lemonade-mms-mapping-03.txt   draft-ietf-lemonade-mms-mapping-04.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-03.txt Qualcomm Document: draft-ietf-lemonade-mms-mapping-04.txt Qualcomm
Expires: October 2005 April 2005 Expires: November 2005 May 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, I certify that any applicable By submitting this Internet-Draft, each author represents that any
patent or other IPR claims of which I am aware have been disclosed applicable patent or other IPR claims of which he or she is aware
and any of which I become aware will be disclosed, in accordance have been or will be disclosed, and any of which he or she becomes
with RFC 3668 (BCP 79). aware will be disclosed, in accordance with Section 6 of BCP 79.
By submitting this Internet-Draft, I accept the provisions of By submitting this Internet-Draft, I accept the provisions of
Section 3 of RFC 3667 (BCP 78). Section 3 of RFC 3667 (BCP 78).
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
skipping to change at line 36 skipping to change at line 36
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt The list of http://www.ietf.org/ietf/1id-abstracts.txt The list of
Internet-Draft Shadow Directories can be accessed at Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). 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 October 2005 Gellens [Page 1] Expires November 2005
This document specifies how to exchange messages between these two This document specifies how to exchange messages between these two
services, including mapping information elements as used in MMS services, including mapping information elements as used in MMS
X-Mms-* headers as well as delivery and disposition reports, to and X-Mms-* headers as well as delivery and disposition reports, to and
from that used in ESMTP and Internet message headers. from that used in ESMTP and Internet message headers.
Gellens [Page 2] Expires October 2005 Gellens [Page 2] Expires November 2005
Table of Contents Table of Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1 Conventions Used in this Document . . . . . . . . . . . . 3
1.2 Conventions Used in this Document . . . . . . . . . . . . 4 1.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3 Definitions . . . . . . . . . . . . . . . . . . . . . . . 4 1.3 Definitions . . . . . . . . . . . . . . . . . . . . . . . 4
1.4 Abbreviations . . . . . . . . . . . . . . . . . . . . . . 5 1.4 Abbreviations . . . . . . . . . . . . . . . . . . . . . . 5
1.5 Assumptions . . . . . . . . . . . . . . . . . . . . . . . 6 1.5 Assumptions . . . . . . . . . . . . . . . . . . . . . . . 6
2 Mapping Between MMS and Internet Mail . . . . . . . . . . . . 6 2 Mapping Between MMS and Internet Mail . . . . . . . . . . . . 6
2.1 Mapping Specification . . . . . . . . . . . . . . . . . . 6 2.1 Mapping Specification . . . . . . . . . . . . . . . . . . 6
2.1.1 MMS to Internet Mail . . . . . . . . . . . . . . . . . 6 2.1.1 MMS to Internet Mail . . . . . . . . . . . . . . . . . 6
2.1.2 Internet Mail to MMS . . . . . . . . . . . . . . . . 7 2.1.2 Internet Mail to MMS . . . . . . . . . . . . . . . . 7
2.1.3 MMS Information Element Mappings . . . . . . . . . . . 7 2.1.3 MMS Information Element Mappings . . . . . . . . . . . 7
2.1.3.1 Table 1: MM3 Mappings . . . . . . . . . . . . . . 8 2.1.3.1 Table 1: MM3 Mappings . . . . . . . . . . . . . . 8
2.1.3.2 Conversion of messages from MMS to Internet format 10 2.1.3.2 Conversion of messages from MMS to Internet format 10
2.1.3.2.1 Table 2: Importance Mappings (MMS to Internet 14 2.1.3.2.1 Table 2: Importance Mappings (MMS to Internet 14
2.1.3.2.2 Table 3: X-Priority Mappings (MMS to Internet 14 2.1.3.2.2 Table 3: X-Priority Mappings (MMS to Internet 14
2.1.3.3 Conversion of messages from Internet to MMS format 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 18 2.1.3.3.1 Table 4: Priority Mappings (Internet Message t 18
2.1.4 Report Generation and Conversion . . . . . . . . . . 20 2.1.4 Report Generation and Conversion . . . . . . . . . . 20
2.1.4.1 Delivery Report Mapping from MMS to Internet Messa 20 2.1.4.1 Delivery Report Mapping from MMS to Internet Messa 20
2.1.4.1.1 Table 5: Delivery Report Mappings (MMS to Inte 21 2.1.4.1.1 Table 5: Delivery Report Mappings (MMS to Inte 21
2.1.4.2 Delivery Report Mapping from Internet Message to M 22 2.1.4.2 Delivery Report Mapping from Internet Message to M 22
2.1.4.2.1 Table 6: Delivery Report Mappings (Internet Me 23 2.1.4.2.1 Table 6: Delivery Report Mappings (Internet Me 23
2.1.4.3 Read Report Mapping from MMS to Internet Message . 24 2.1.4.3 Read Report Mapping from MMS to Internet Message . 24
2.1.4.3.1 Table 7: Read Report Mappings (MMS to Internet 25 2.1.4.3.1 Table 7: Read Report Mappings (MMS to Internet 25
2.1.4.4 Disposition Report Mapping from Internet Message t 26 2.1.4.4 Disposition Report Mapping from Internet Message t 26
2.1.4.4.1 Table 8: Disposition Report Mappings (Internet 26 2.1.4.4.1 Table 8: Disposition Report Mappings (Internet 26
2.1.5 Message Delivery . . . . . . . . . . . . . . . . . . . 27 2.1.5 Message Delivery . . . . . . . . . . . . . . . . . . . 27
3 Security Considerations . . . . . . . . . . . . . . . . . . . 27 3 Security Considerations . . . . . . . . . . . . . . . . . . . 27
4 Normative References . . . . . . . . . . . . . . . . . . . . . 29 4 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29
5 Informative References . . . . . . . . . . . . . . . . . . . 30 5 Normative References . . . . . . . . . . . . . . . . . . . . 29
6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 31 6 Informative References . . . . . . . . . . . . . . . . . . . . 30
Intellectual Property Statement . . . . . . . . . . . . . . . 31 7 Author's Address . . . . . . . . . . . . . . . . . . . . . . 31
Intellectual Property Statement . . . . . . . . . . . . . . . . 32
Full Copyright Statement . . . . . . . . . . . . . . . . . . . 32 Full Copyright Statement . . . . . . . . . . . . . . . . . . . 32
Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . 32
1 Introduction 1 Introduction
1.1 Scope 1.1 Conventions Used in this Document
This document describes how to exchange messages with Internet mail The key words "REQUIRED", "MUST", "MUST NOT", "SHOULD", "SHOULD
systems. This includes translation between MMS (as defined by NOT", and "MAY" in this document are to be interpreted as described
3GPP/3GPP2/OMA) and Internet Mail messages using Extended Simple in "Key words for use in RFCs to Indicate Requirement Levels"
Mail Transfer Protocol [SMTP] and Internet message format [Msg-Fmt]. [KEYWORDS].
This also includes translation between delivery and disposition
reports as used in MMS and in Internet mail ([DSN-Msg] and [MDN]). Gellens [Page 3] Expires November 2005
Note that in the text of this document, a distinction is made
between use of "SMTP" or "Simple Mail Transfer Protocol", and
"ESMTP" or "Extended Simple Mail Transfer Protocol": when the term
"ESMTP" or "Extended" is used, it indicates use of extended features
of SMTP; that is, those beyond the facilities of RFC 821. (These
extended facilities may be in RFC 2821 or in other RFCs, as
indicated by the specific RFC reference used; note that the name of
the RFC 2821 reference is "SMTP" because that is the official title
of the RFC.)
1.2 Scope
This document describes how to exchange messages between MMS systems
(as defined by 3GPP/3GPP2/OMA) and Internet mail systems (that is,
[SMTP] and [Msg-Fmt]). This includes the translation of message
formats, message header elements, message delivery reports and
message disposition reports ([DSN-Msg] and [MDN]).
Gellens [Page 3] Expires October 2005
The MMS architecture [Stage_2] and specifications [Stage_3] refer to The MMS architecture [Stage_2] and specifications [Stage_3] refer to
interfaces as reference points named MMx. For example, MM1 is the interfaces as reference points named MMx. For example, MM1 is the
client-server interface, MM4 is the server-server interface, and MM3 client-server interface, MM4 is the server-server interface, and MM3
is an interface to "external" or non-MMS systems. The specification is an interface to "external" or non-MMS systems. The specification
in this document can be used for message exchange between any system in this document can be used for message exchange between any system
which uses Internet Message formats and protocols and an MMS system; which uses Internet Message formats and protocols and an MMS system;
from the perspective of the MMS system, reference point MM3 is used. from the perspective of the MMS system, reference point MM3 is used.
This document includes support for voice messages specified by the This document includes support for voice messages specified by the
Voice Profile for Internet Mail [VPIM]. The VPIM specification Voice Profile for Internet Mail [VPIM]. The VPIM specification
skipping to change at line 130 skipping to change at line 146
(non-MMS) systems other than Internet mail, such as Short Messaging (non-MMS) systems other than Internet mail, such as Short Messaging
Service (SMS) and access to external mail stores (such as a voice Service (SMS) and access to external mail stores (such as a voice
mail system). This specification does not address these other uses mail system). This specification does not address these other uses
or sub-interfaces of MM3; it is only concerned with Internet mail or sub-interfaces of MM3; it is only concerned with Internet mail
interworking and specifically exchange of messages. interworking and specifically exchange of messages.
All MM3 Stage 2 [Stage_2] functions are supported except for reply All MM3 Stage 2 [Stage_2] functions are supported except for reply
charging and sender address hiding, which may be addressed in future charging and sender address hiding, which may be addressed in future
extensions. extensions.
1.2 Conventions Used in this Document Gellens [Page 4] Expires November 2005
The key words "REQUIRED", "MUST", "MUST NOT", "SHOULD", "SHOULD
NOT", and "MAY" in this document are to be interpreted as described
in "Key words for use in RFCs to Indicate Requirement Levels"
[KEYWORDS].
Note that in the text of this document, a distinction is made
between use of "SMTP" or "Simple Mail Transfer Protocol", and
"ESMTP" or "Extended Simple Mail Transfer Protocol": when the term
"ESMTP" or "Extended" is used, it indicates use of extended features
of SMTP; that is, those beyond the facilities of RFC 821. (These
extended facilities may be in RFC 2821 or in other RFCs, as
indicated by the specific RFC reference used; note that the name of
the RFC 2821 reference is "SMTP" because that is the official title
of the RFC.)
Gellens [Page 4] Expires October 2005
1.3 Definitions 1.3 Definitions
--------------------|---------------------------------------------- --------------------|----------------------------------------------
Anonymous Remailer |A service which accepts messages and resends Anonymous Remailer |A service which accepts messages and resends
|them to their intended recipient, masking |them to their intended recipient, masking
|information about the original sender. |information about the original sender.
--------------------|---------------------------------------------- --------------------|----------------------------------------------
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
skipping to change at line 193 skipping to change at line 192
|(such as "To:"), also known as Header Fields |(such as "To:"), also known as Header Fields
|or Headers. The message Header contains |or Headers. The message Header contains
|information used by User Agents. |information used by User Agents.
--------------------|---------------------------------------------- --------------------|----------------------------------------------
Gateway Function |An agent which acts as both MMSC and MTA Gateway Function |An agent which acts as both MMSC and MTA
|and/or MSA. |and/or MSA.
--------------------|---------------------------------------------- --------------------|----------------------------------------------
User Agent |An MMS or Email user agent User Agent |An MMS or Email user agent
--------------------|---------------------------------------------- --------------------|----------------------------------------------
Gellens [Page 5] Expires October 2005 Gellens [Page 5] Expires November 2005
1.4 Abbreviations 1.4 Abbreviations
--------|---------------------------------------------------------- --------|----------------------------------------------------------
ESMTP |Extended Simple Mail Transfer Protocol. The use of ESMTP |Extended Simple Mail Transfer Protocol. The use of
|features and capabilities added to SMTP since RFC 821. |features and capabilities added to SMTP since RFC 821.
--------|---------------------------------------------------------- --------|----------------------------------------------------------
MSA |Message Submission Agent. A server which accepts messages MSA |Message Submission Agent. A server which accepts messages
|from User Agents and processes them; either delivering |from User Agents and processes them; either delivering
|them locally or relaying to an MTA. |them locally or relaying to an MTA.
skipping to change at line 241 skipping to change at line 240
When sending a message to an Internet mail system the MMS When sending a message to an Internet mail system the MMS
Relay/Server MUST convert the MM if required, and MUST comply with Relay/Server MUST convert the MM if required, and MUST comply with
the requirements of [SMTP] (for example, use of a null return-path the requirements of [SMTP] (for example, use of a null return-path
for automatically-generated messages). for automatically-generated messages).
The MMS Relay/Server SHOULD use the information elements associated The MMS Relay/Server SHOULD use the information elements associated
with the MM to define the control information (Internet Message with the MM to define the control information (Internet Message
header fields and ESMTP values) needed for the transfer protocol. header fields and ESMTP values) needed for the transfer protocol.
Gellens [Page 6] Expires October 2005 Gellens [Page 6] Expires November 2005
Section 2.1.3 lists the mappings between X-Mms-* headers and Section 2.1.3 lists the mappings between X-Mms-* headers and
Internet Message header fields and ESMTP values. Internet Message header fields and ESMTP 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
skipping to change at line 271 skipping to change at line 270
Section 2.1.3 lists the mappings between X-Mms-* headers and Section 2.1.3 lists the mappings between X-Mms-* headers and
Internet Message header fields and ESMTP values. Internet Message header fields and ESMTP values.
Standard Internet Message report format (multipart/report) messages Standard Internet Message report format (multipart/report) messages
MAY be converted to delivery or read report MMs, as appropriate. In MAY be converted to delivery or read report MMs, as appropriate. In
addition to converting report MMs, the MMS Relay/Server MUST addition to converting report MMs, the MMS Relay/Server MUST
generate standard Internet Message delivery and disposition reports generate standard Internet Message delivery and disposition reports
for received Internet messages as appropriate. See section 2.1.4 for received Internet messages as appropriate. See section 2.1.4
for more information. for more information.
Gellens [Page 7] Expires October 2005 Gellens [Page 7] Expires November 2005
2.1.3 MMS Information Element Mappings 2.1.3 MMS Information Element Mappings
The mappings between MMS elements and ESMTP/Internet Message The mappings between MMS elements and ESMTP/Internet Message
elements (either [SMTP] parameters, [Msg-Fmt] headers, or both) are elements (either [SMTP] parameters, [Msg-Fmt] headers, or both) are
summarized in the table below, and detailed in subsequent sections. summarized in the table below, and detailed in subsequent sections.
The "MMS Headers" are from [OMA-MMS]. Note that only information The "MMS Headers" are from [OMA-MMS]. Note that only information
elements which need to be mapped are listed. [Msg-Fmt] headers not elements which need to be mapped are listed. [Msg-Fmt] headers not
listed here SHOULD be passed unaltered listed here SHOULD be passed unaltered
2.1.3.1 Table 1: MM3 Mappings 2.1.3.1 Table 1: MM3 Mappings
=================|=================|================|============== =================|=================|================|==============
Information Elem |[SMTP] Element |[Msg-Fmt] Header|MMS Header Information Elem |[SMTP] Element |[Msg-Fmt] Header|MMS Header
=================|=================|================|============== =================|=================|================|==============
3GPP MMS Version |N/A |N/A |X-Mms-Version: 3GPP MMS Version |N/A |N/A |X-Mms-3GPP-MMS
| | | | | | -Version:
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Message Type |N/A |N/A |X-Mms-Message- Message Type |N/A |N/A |X-Mms-Message-
(of PDU) | | | Type: (of PDU) | | | Type:
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Transaction ID |N/A |N/A |X-Mms-Transact Transaction ID |N/A |N/A |X-Mms-Transact
| | | ion-Id: | | | ion-Id:
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Message ID |ENVID [DSN-SMTP] |Message-ID: |X-Mms-Message- Message ID |ENVID [DSN-SMTP] |Message-ID: |X-Mms-Message-
| | | Id: | | | Id:
| | |Message-ID: | | |Message-ID:
skipping to change at line 320 skipping to change at line 319
|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 October 2005 Gellens [Page 8] Expires November 2005
=================|=================|================|============== =================|=================|================|==============
Information Elem |RFC 2821 Element |RFC 2822 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 | | |
_________________|_________________|________________|______________ _________________|_________________|________________|______________
Time of expiry |DELIVER-BY |N/A |X-Mms-Expiry: Time of expiry |DELIVER-BY |N/A |X-Mms-Expiry:
skipping to change at line 370 skipping to change at line 369
_________________|_________________|________________|______________ _________________|_________________|________________|______________
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 October 2005 Gellens [Page 9] Expires November 2005
=================|=================|================|============== =================|=================|================|==============
Information Elem |RFC 2821 Element |RFC 2822 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:
_________________|_________________|________________|______________ _________________|_________________|________________|______________
skipping to change at line 404 skipping to change at line 403
| | |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>
=================|=================|================|============== =================|=================|================|==============
Note 1: The [VPIM] 'Sensitivity' header element indicates the Note 1: The [VPIM] 'Sensitivity' header element indicates the
privacy requested by the message originator (values are "personal" privacy requested by the message originator (values are "personal"
or "private"); a message recipient MUST NOT forward a message with a or "private"); per [VPIM], a message recipient MUST NOT forward a
'Sensitivity' header. message with a 'Sensitivity' header. Since sensitivity is not an
MMS feature, any messages which contain a 'Sensitivity:' header
SHOULD NOT be sent to an MMS system.
Note 2: A MIME-Version header with a comment of "Voice 2.0" Note 2: [VPIM] specifies how conforming messages are identified.
indicates that the voice message conforms to [VPIM].
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-Version:' header, if present, SHOULD be removed. The 'X-Mms-3GPP-MMS-Version:' header, if present, SHOULD be removed.
Gellens [Page 10] Expires October 2005 Gellens [Page 10] Expires November 2005
Message Type (of PDU) Message Type (of PDU)
The 'X-Mms-Message-Type:' header, if present, SHOULD be removed. The 'X-Mms-Message-Type:' header, if present, SHOULD be removed.
Transaction ID Transaction ID
The 'X-Mms-Transaction-Id:' header, if present, SHOULD be removed. The 'X-Mms-Transaction-Id:' header, if present, SHOULD be removed.
Message ID Message ID
An 'X-Mms-Message-Id:' header, if present, SHOULD be retained. An 'X-Mms-Message-Id:' header, if present, SHOULD be retained in
order to facilitate the case where an MMS message traverses the
Internet prior to returning to an MMS system. Such systems should
be aware that X-headers might be removed during transit through
Internet MTAs.
The 'Message-Id:' header MUST be retained. If not present it MUST The 'Message-Id:' header MUST be retained. If not present it MUST
be created, with a unique value. If an 'X-Mms-Message-Id:' header be created, with a unique value. If an 'X-Mms-Message-Id:' header
is present and a 'Message-Id:' header is not, the value of the is present and a 'Message-Id:' header is not, the value of the
'X-Mms-Message-Id:' header MAY be used in creating the 'Message-Id:' 'X-Mms-Message-Id:' header MAY be used in creating the 'Message-Id:'
header. header.
The message ID SHOULD be transmitted in the ESMTP envelope as the The message ID SHOULD be transmitted in the ESMTP envelope as the
ENVID parameter, as specified in [DSN-SMTP]. ENVID parameter, as specified in [DSN-SMTP].
skipping to change at line 453 skipping to change at line 457
header MUST be present. If all recipients are undisclosed, a 'To:' header MUST be present. If all recipients are undisclosed, a 'To:'
header MAY be created that contains a comment, for example 'To: header MAY be created that contains a comment, for example 'To:
(undisclosed recipients)'. The 'To:' header SHOULD NOT appear more (undisclosed recipients)'. The 'To:' header SHOULD NOT appear more
than once. The 'Cc:' header SHOULD NOT appear more than once. than once. The 'Cc:' header SHOULD NOT appear more than once.
Each recipient address MUST obey the length restrictions per [SMTP]. Each recipient address MUST obey the length restrictions per [SMTP].
Current Internet message format requires that only 7-bit US-ASCII Current Internet message format requires that only 7-bit US-ASCII
characters be present in addresses. Other characters (for example, characters be present in addresses. Other characters (for example,
non-7-bit characters in a phrase part of an address header) MUST be non-7-bit characters in a phrase part of an address header) MUST be
encoded according to [Hdr-Enc]. Note that it would be possible to encoded according to [Hdr-Enc].
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.
Sender address Sender address
The address of the message sender SHOULD appear in the 'From:' The address of the message sender SHOULD appear in the 'From:'
header, unless address hiding has been requested. If address hiding header, unless address hiding has been requested. If address hiding
has been requested, the 'From:' header MAY contain a comment to this has been requested, the 'From:' header MAY contain a comment to this
effect, for example, 'From: (anonymous sender)'. effect, for example, 'From: (anonymous sender)'.
Gellens [Page 11] Expires October 2005 Gellens [Page 11] Expires November 2005
The address of the message sender for all user-generated messages The address of the message sender for all user-generated messages
('X-Mms-Message-Class: Personal') SHOULD be transmitted in the SMTP ('X-Mms-Message-Class: Personal') SHOULD be transmitted in the SMTP
envelope as the MAIL FROM value unless address hiding has been envelope as the MAIL FROM value unless address hiding has been
requested and the receiving server is not known and trusted to requested and the receiving server is not known and trusted to
support address hiding. support address hiding.
The 'From:' header and the MAIL FROM value MAY be set to a The 'From:' header and the MAIL FROM value MAY be set to a
locally-generated value to hide the sender identity in anonymous locally-generated value to hide the sender identity in anonymous
messages when the receiving system does not support anonymous messages when the receiving system does not support anonymous
messages. Locally generated addresses MAY be internally mapped to messages. Locally generated addresses MAY be internally mapped to
skipping to change at line 513 skipping to change at line 514
conversion is done, the 'Content-Type:' header MUST be updated if it conversion is done, the 'Content-Type:' header MUST be updated if it
is no longer correct. is no longer correct.
Message class Message class
The 'X-Mms-Message-Class:' header MAY be retained. A 'Precedence: The 'X-Mms-Message-Class:' header MAY be retained. 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 October 2005 Gellens [Page 12] Expires November 2005
Time of Expiry Time of Expiry
The 'X-Mms-Expiry:' header, if present, SHOULD be removed. The 'X-Mms-Expiry:' header, if present, SHOULD be removed.
The remaining time until the message is considered expired SHOULD be The remaining time until the message is considered expired SHOULD be
transmitted in the ESMTP envelope by using the DELIVER-BY extension, transmitted in the ESMTP envelope by using the DELIVER-BY extension,
as specified in [Deliver-By]. as specified in [Deliver-By].
Note that the ESMTP DELIVER-BY extension carries time remaining Note that the ESMTP 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
skipping to change at line 561 skipping to change at line 562
be transmitted using an 'Importance:' header (although currently not be transmitted using an 'Importance:' header (although currently not
all Internet mail clients support this header). all Internet mail clients support this header).
An 'X-Priority:' header MAY be used in addition. Although not An 'X-Priority:' header MAY be used in addition. Although not
standardized, most email applications support the 'X-Priority:' standardized, most email applications support the 'X-Priority:'
header, and use an 'X-Priority' value of 3 for messages with header, and use an 'X-Priority' value of 3 for messages with
"normal" priority. More important messages have lower values and "normal" priority. More important messages have lower values and
less important message have higher values. In most cases, urgent less important message have higher values. In most cases, urgent
messages have an X-Priority value of 1. messages have an X-Priority value of 1.
Gellens [Page 13] Expires October 2005 Gellens [Page 13] Expires November 2005
Suggested mappings: Suggested mappings:
2.1.3.2.1 Table 2: Importance Mappings (MMS to Internet Message) 2.1.3.2.1 Table 2: Importance Mappings (MMS to Internet Message)
---------------------------|------------------ ---------------------------|------------------
'X-Mms-Priority: High' |'Importance: High' 'X-Mms-Priority: High' |'Importance: High'
---------------------------|------------------ ---------------------------|------------------
'X-Mms-Priority: Normal' |[omit] 'X-Mms-Priority: Normal' |[omit]
---------------------------|------------------ ---------------------------|------------------
'X-Mms-Priority: Low' |'Importance: Low' 'X-Mms-Priority: Low' |'Importance: Low'
skipping to change at line 612 skipping to change at line 613
The 'X-Mms-Read-Reply:' header, if present, SHOULD be removed. The 'X-Mms-Read-Reply:' header, if present, SHOULD be removed.
Reply-charging Reply-charging
Reply charging permission and acceptance are complex issues Reply charging permission and acceptance are complex issues
requiring both user agent and server support. Misapplied reply requiring both user agent and server support. Misapplied reply
charging may cause incorrect billing. Until the security issues charging may cause incorrect billing. Until the security issues
have been properly addressed, reply charging SHOULD NOT be honored have been properly addressed, reply charging SHOULD NOT be honored
Gellens [Page 14] Expires October 2005 Gellens [Page 14] Expires November 2005
when using this interface. when using this interface.
The 'X-Mms-Reply-Charging:', 'X-Mms-Reply-Charging-Deadline:', The 'X-Mms-Reply-Charging:', 'X-Mms-Reply-Charging-Deadline:',
'X-Mms-Reply-Charging-Size:', and 'X-Mms-Reply-Charging-Id:' headers 'X-Mms-Reply-Charging-Size:', and 'X-Mms-Reply-Charging-Id:' headers
MAY be removed. Messages containing a reply-charging usage request MAY be removed. Messages containing a reply-charging usage request
('X-Mms-Reply-Charging-Id:' and 'X-Mms-Reply-Charging: accepted' or ('X-Mms-Reply-Charging-Id:' and 'X-Mms-Reply-Charging: accepted' or
'X-Mms-Reply-Charging: accepted (text only)' headers) SHOULD be 'X-Mms-Reply-Charging: accepted (text only)' headers) SHOULD be
rejected. rejected.
Subject Subject
skipping to change at line 660 skipping to change at line 661
addition of 'Resent-' headers to explain the resending to the new addition of 'Resent-' headers to explain the resending to the new
recipient. recipient.
A message may be resent more than once; each time new 'Resent-' A message may be resent more than once; each time new 'Resent-'
headers SHOULD be added at the top of the message. Thus, if more headers SHOULD be added at the top of the message. Thus, if more
than one series of 'Resent-' headers are present, the original than one series of 'Resent-' headers are present, the original
series is the last; the most recent is the first. series is the last; the most recent is the first.
Forward counter Forward counter
Gellens [Page 15] Expires October 2005 Gellens [Page 15] Expires November 2005
The 'Resent-Count:' header MAY be used to track the number of times The 'Resent-Count:' header is NOT RECOMMENDED. Loop control is
the message has been resent. Note that loop control is often done usually done by counting 'Received' headers, which are more general
by counting 'Received' headers, which are more general than than 'Resent-' headers.
'Resent-' headers.
Previously-sent Information Previously-sent Information
A 'Resent-From:' header MAY be added to indicate the address of the A 'Resent-From:' header MAY be added to indicate the address of the
user who directed the message to be resent. user who directed the message to be resent.
A 'Resent-Date:' header SHOULD be added to indicate the time and A 'Resent-Date:' header SHOULD be added to indicate the time and
date that the message was resent. date that the message was resent.
Any 'X-Mms-Previously-Sent-By:' and 'X-Mms-Previously-Sent-Date' Any 'X-Mms-Previously-Sent-By:' and 'X-Mms-Previously-Sent-Date'
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 'From:', 'Resent-To:',
'Resent-From:', 'Resent-Date:', and 'Resent-Count:' headers. The 'Resent-From:', and 'Resent-Date:' headers. The original sender of
original sender of the message SHOULD appear in the 'From:' header; the message SHOULD appear in the 'From:' header; the original
the original recipient(s) SHOULD appear in the 'To:' header; the recipient(s) SHOULD appear in the 'To:' header; the time and date
time and date the message was originally sent SHOULD appear in the the message was originally sent SHOULD appear in the 'Date:' header.
'Date:' header. The most recent sender SHOULD appear in the The most recent sender SHOULD appear in the top-most 'Resent-From:'
top-most 'Resent-From:' header; the most recent recipient(s) SHOULD header; the most recent recipient(s) SHOULD appear in the top-most
appear in the top-most 'Resent-To:' header; the time and date the 'Resent-To:' header; the time and date the message was most recently
message was most recently sent SHOULD appear in the top-most sent SHOULD appear in the top-most 'Resent-Date:' header.
'Resent-Date:' header.
'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.
Privacy Privacy
skipping to change at line 711 skipping to change at line 710
The message content appears in the message body. Note that Internet The message content appears in the message body. Note that Internet
message format requires that line-endings be encoded as CR LF, thus message format requires that line-endings be encoded as CR LF, thus
charset encodings that do not have this property cannot be used in charset encodings that do not have this property cannot be used in
text/* body parts. (They MAY be used in other body parts, but only text/* body parts. (They MAY be used in other body parts, but only
when they are suitable encoded or when binary transmission has been when they are suitable encoded or when binary transmission has been
negotiated.) In particular, MMS allows UTF-16, while Internet negotiated.) In particular, MMS allows UTF-16, while Internet
message format does not. UTF-16 encoding MUST be translated to message format does not. UTF-16 encoding MUST be translated to
UTF-8 or another charset and encoding which is suitable for use in UTF-8 or another charset and encoding which is suitable for use in
Internet message format/protocols. Internet message format/protocols.
Gellens [Page 16] Expires October 2005 Gellens [Page 16] Expires November 2005
2.1.3.3 Conversion of messages from Internet to MMS format 2.1.3.3 Conversion of messages from Internet to MMS format
3GPP MMS Version 3GPP MMS Version
An 'X-Mms-Mms-Version:' header SHOULD be added. An 'X-Mms-3GPP-MMS-Version:' header SHOULD be added.
Message Type (of PDU) Message Type (of PDU)
An 'X-Mms-Message-Type:' header SHOULD be used in accordance with An 'X-Mms-Message-Type:' header SHOULD be used in accordance with
the specific MMS interface (e.g., MM1, MM4). the specific MMS interface (e.g., MM1, MM4).
Transaction ID Transaction ID
An 'X-Mms-Transaction-Id:' header SHOULD be used in accordance with An 'X-Mms-Transaction-Id:' header SHOULD be used in accordance with
the specific MMS interface (e.g., MM1, MM4). the specific MMS interface (e.g., MM1, MM4).
skipping to change at line 759 skipping to change at line 758
The 'From:' header MUST be retained. The 'From:' header MUST be retained.
Content type Content type
The complete 'Content-Type:' header (including any parameters) The complete 'Content-Type:' header (including any parameters)
SHOULD be preserved. SHOULD be preserved.
Message class Message class
Gellens [Page 17] Expires October 2005 Gellens [Page 17] Expires November 2005
An X-Mms-Message-Class: personal' header SHOULD be created for all An 'X-Mms-Message-Class: personal' header SHOULD be created for all
received messages with a non-null return path (MAIL FROM value in received messages with a non-null return path (MAIL FROM value in
the SMTP envelope). An X-Mms-Message-Class: auto' header MAY be the SMTP envelope). An 'X-Mms-Message-Class: auto' header MAY be
created for messages with a null return path. created for messages with a null return path.
Time of Expiry Time of Expiry
An 'x-Mms-Expiry:' header SHOULD be created if the message contains An 'X-Mms-Expiry:' header SHOULD be created if the message contains
a relative time to expiration in the DELIVER-BY extension, as a relative time to expiration in the DELIVER-BY extension, as
specified in [Deliver-By]. specified in [Deliver-By].
Earliest delivery time Earliest delivery time
An 'X-Mms-Delivery-Time:' header SHOULD NOT be created. If a An 'X-Mms-Delivery-Time:' header SHOULD NOT be created. If a
message arrives via ESMTP relay containing an earliest time of message arrives via ESMTP relay containing an earliest time of
delivery in the AFTER extension, it MAY be rejected. If a message delivery in the AFTER extension, it MAY be rejected. If a message
is submitted via Message Submission [Submission] containing an is submitted via Message Submission [Submission] containing an
earliest time of delivery in the AFTER extension, it MUST either be earliest time of delivery in the AFTER extension, it MUST either be
skipping to change at line 810 skipping to change at line 809
-------------------------------|---------------------- -------------------------------|----------------------
'X-Priority: 2 (high)' |'X-Mms-Priority: High' 'X-Priority: 2 (high)' |'X-Mms-Priority: High'
-------------------------------|---------------------- -------------------------------|----------------------
'Importance: High' |'X-Mms-Priority: High' 'Importance: High' |'X-Mms-Priority: High'
-------------------------------|---------------------- -------------------------------|----------------------
'X-Priority: 3 (normal)' | [omitted] 'X-Priority: 3 (normal)' | [omitted]
-------------------------------|---------------------- -------------------------------|----------------------
'Importance: Normal' | [omitted] 'Importance: Normal' | [omitted]
-------------------------------|---------------------- -------------------------------|----------------------
Gellens [Page 18] Expires October 2005 Gellens [Page 18] Expires November 2005
'X-Priority: 4 (low)' |'X-Mms-Priority: Low' 'X-Priority: 4 (low)' |'X-Mms-Priority: Low'
-------------------------------|---------------------- -------------------------------|----------------------
'Importance: Low' |'X-Mms-Priority: Low' 'Importance: Low' |'X-Mms-Priority: Low'
-------------------------------|---------------------- -------------------------------|----------------------
'X-Priority: 5 (lowest)' |'X-Mms-Priority: Low' 'X-Priority: 5 (lowest)' |'X-Mms-Priority: Low'
-------------------------------|---------------------- -------------------------------|----------------------
Normal priority messages SHOULD omit the 'X-Mms-Priority:' header. Normal priority messages SHOULD omit the 'X-Mms-Priority:' header.
Sender visibility Sender visibility
skipping to change at line 858 skipping to change at line 857
The 'Sensitivity:' header field (value = "personal" or "private") The 'Sensitivity:' header field (value = "personal" or "private")
[VPIM] indicates the desire of a voice message originator to send [VPIM] indicates the desire of a voice message originator to send
the message contents to the original recipient list with assurance the message contents to the original recipient list with assurance
that the message will not be forwarded further by either the that the message will not be forwarded further by either the
messaging system or the actual message recipient(s). Since messaging system or the actual message recipient(s). Since
sensitivity is not an MMS feature, any messages which contain a sensitivity is not an MMS feature, any messages which contain a
'Sensitivity:' header SHOULD NOT be sent to an MMS system. An 'Sensitivity:' header SHOULD NOT be sent to an MMS system. An
appropriate extended error response code [RESP] SHOULD be used in appropriate extended error response code [RESP] SHOULD be used in
the associated negative delivery status report. the associated negative delivery status report.
Gellens [Page 19] Expires October 2005 Gellens [Page 19] Expires November 2005
Content Content
The message content appears in the message body. The message content appears in the message body.
2.1.4 Report Generation and Conversion 2.1.4 Report Generation and Conversion
Internet Message systems use the multipart/report MIME type for Internet Message systems use the multipart/report MIME type for
delivery and disposition reports (often called "read reports") as delivery and disposition reports as specified in [Report-Fmt]. This
specified in [Report-Fmt]. This format is a two- or three-part MIME format is a two- or three-part MIME message; one part is a
message; one part is a structured format describing the event being structured format describing the event being reported in an
reported in an easy-to-parse format. Specific reports have a format easy-to-parse format. Specific reports have a format which is built
which is built on [Report-Fmt]. Delivery reports are specified in on [Report-Fmt]. Delivery reports are specified in [DSN-Msg].
[DSN-Msg]. Message disposition reports, which include read reports, Message disposition reports, which include read reports, are
are specified in [MDN]. specified in [MDN].
By contrast, MMS reports are plain text, with no defined structure By contrast, MMS reports are plain text, with no defined structure
specified. This makes it difficult to convert from an MMS report to specified. This makes it difficult to convert from an MMS report to
a standard Internet report. a standard Internet report.
An MMS Relay/Server supporting Internet Message exchange using MM3 An MMS Relay/Server supporting Internet Message exchange using MM3
MUST convert reports received from one side (MMS or Internet mail) MUST convert reports received from one side (MMS or Internet mail)
destined for the other. In addition, reports MUST be generated as destined for the other. In addition, reports MUST be generated as
appropriate for messages received from either side of the MM3 appropriate for messages received from either side of the MM3
interface. For example, if an MM to be sent via MM3 is not interface. For example, if an MM to be sent via MM3 is not
skipping to change at line 904 skipping to change at line 903
This text may include a statement that the report was synthesized This text may include a statement that the report was synthesized
based on an MMS report. The second subpart is of type based on an MMS report. The second subpart is of type
report/delivery-status (for delivery reports) or report/delivery-status (for delivery reports) or
report/disposition-notification (for disposition reports). This report/disposition-notification (for disposition reports). This
second part contains a structured itemization of the event. The second part contains a structured itemization of the event. The
third subpart is of type message/rfc822 and includes the headers and third subpart is of type message/rfc822 and includes the headers and
optionally the body of the referenced (original) message. optionally the body of the referenced (original) message.
2.1.4.1 Delivery Report Mapping from MMS to Internet Message 2.1.4.1 Delivery Report Mapping from MMS to Internet Message
Gellens [Page 20] Expires October 2005 Gellens [Page 20] Expires November 2005
The following table maps information elements from MMS delivery The following table maps information elements from MMS delivery
reports to the format specified in [DSN-Msg]. reports to the format specified in [DSN-Msg].
2.1.4.1.1 Table 5: Delivery Report Mappings (MMS to Internet Message) 2.1.4.1.1 Table 5: Delivery Report Mappings (MMS to Internet Message)
======================|============|=================================== ======================|============|===================================
Information Element |MMS Delivery|[DSN-Msg] Element Information Element |MMS Delivery|[DSN-Msg] Element
|Report Elem | |Report Elem |
======================|============|=================================== ======================|============|===================================
ID of message whose |Message-Id: |'Original-Envelope-ID' field of ID of message whose |Message-Id: |'Original-Envelope-ID' field of
skipping to change at line 936 skipping to change at line 935
| | | |
| |Value taken from [SMTP] envelope | |Value taken from [SMTP] envelope
| |return-path of message being | |return-path of message being
| |reported, not its 'From:' header | |reported, not its 'From:' header
| |field. | |field.
----------------------|------------|----------------------------------- ----------------------|------------|-----------------------------------
Date and time the |Date: |'Date:' header field value of top- Date and time the |Date: |'Date:' header field value of top-
message was handled | |level message was handled | |level
======================|============|=================================== ======================|============|===================================
Gellens [Page 21] Expires October 2005 Gellens [Page 21] Expires November 2005
======================|============|=================================== ======================|============|===================================
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 ======================|============|===================================
original message | Status: |per-recipient section. Delivery status of |X-Mms- |Action and Status fields of
| | original message to | Status: |per-recipient section.
each recipient | |
| |The 'Action' field indicates if the | |The 'Action' field indicates if the
| |message was delivered. | |message was delivered.
| | | |
| |For failed delivery an appropriate | |For failed delivery an appropriate
| |'Status' value shall be included | |'Status' value shall be included
| |per [DSN-Msg]. | |per [DSN-Msg].
| | | |
| |The Action field is set to one of | |The Action field is set to one of
| |the following values: | |the following values:
| | | |
skipping to change at line 985 skipping to change at line 985
* Top-level header field 'To:' SHOULD be the [SMTP] return-path of * Top-level header field 'To:' SHOULD be the [SMTP] return-path of
the message whose status is being reported. the message whose status is being reported.
* Top-level header field 'From:' SHOULD be the address of the * Top-level header field 'From:' SHOULD be the address of the
recipient that the delivery-report concerns. recipient that the delivery-report concerns.
* The first part of the [DSN-Msg] SHOULD include the MM Status Text * The first part of the [DSN-Msg] SHOULD include the MM Status Text
field that would have been generated for an MM1 delivery-report. field that would have been generated for an MM1 delivery-report.
Gellens [Page 22] Expires October 2005 Gellens [Page 22] Expires November 2005
2.1.4.2 Delivery Report Mapping from Internet Message to MMS 2.1.4.2 Delivery Report Mapping from Internet Message to MMS
The following table maps information elements from a delivery report The following table maps information elements from a delivery report
as specified in [DSN-Msg] to the format of an MMS delivery report. as specified in [DSN-Msg] to the format of an MMS delivery report.
2.1.4.2.1 Table 6: Delivery Report Mappings (Internet Message to MMS) 2.1.4.2.1 Table 6: Delivery Report Mappings (Internet Message to MMS)
===================|==================|================================ ===================|==================|================================
Information Element|MMS Delivery |[DSN=Msg] Element Information Element|MMS Delivery |[DSN-Msg] Element
|Report Element | |Report Element |
===================|==================|================================ ===================|==================|================================
ID of the original |Message-Id: |'Original-Envelope-ID' field of ID of the original |Message-Id: |'Original-Envelope-ID' field of
message (object of | |per-message fields. If not message (object of | |per-message fields. If not
delivery report) | |available, the 'Message-ID' delivery report) | |available, the 'Message-ID'
| |header field of the message | |header field of the message
| |being reported, if included in | |being reported, if included in
| |the third part, may be | |the third part, may be
| |substituted. | |substituted.
-------------------|------------------|-------------------------------- -------------------|------------------|--------------------------------
skipping to change at line 1020 skipping to change at line 1020
| |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 23] Expires October 2005 Gellens [Page 23] Expires November 2005
===================|==================|================================ ===================|==================|================================
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 |
|following values: | |following values: |
| | | |
skipping to change at line 1058 skipping to change at line 1058
|'deferred' MUST | |'deferred' MUST |
|NOT be used | |NOT be used |
|(ignore DSNs with | |(ignore DSNs with |
|'Action' value | |'Action' value |
|'delayed') | |'delayed') |
-------------------|------------------|-------------------------------- -------------------|------------------|--------------------------------
Status Text | |Text in first part (human- Status Text | |Text in first part (human-
| |readable part) | |readable part)
===================|==================|================================ ===================|==================|================================
Gellens [Page 24] Expires October 2005 Gellens [Page 24] Expires November 2005
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|[DSN-Msg] Element Information Element |MMS Delivery|[MDN] Element
|Report Elem | |Report Elem |
======================|============|=================================== ======================|============|===================================
ID of the original |Message-Id: |'Original-Envelope-ID' field (use ID of the original |Message-Id: |'Original-Envelope-ID' field (use
message (object of | |value of ENVID from ESMTP envelope message (object of | |value of ENVID from ESMTP envelope
read report) | |if available, 'Message-ID:' read report) | |if available, 'Message-ID:'
| |otherwise). | |otherwise).
----------------------|------------|----------------------------------- ----------------------|------------|-----------------------------------
Recipient address of |From: |'Final-Recipient' field Recipient address of |From: |'Final-Recipient' field
the original message | | the original message | |
----------------------|------------|----------------------------------- ----------------------|------------|-----------------------------------
skipping to change at line 1106 skipping to change at line 1106
| |use 'disposition-type' value | |use 'disposition-type' value
| |'deleted') | |'deleted')
----------------------|------------|----------------------------------- ----------------------|------------|-----------------------------------
Status Text | |Text in first part (human-readable Status Text | |Text in first part (human-readable
| |part) | |part)
======================|============|=================================== ======================|============|===================================
When an MMS Relay/Server generates an [MDN] in response to a message When an MMS Relay/Server generates an [MDN] in response to a message
received using ESMTP on MM3: received using ESMTP on MM3:
Gellens [Page 25] Expires October 2005 Gellens [Page 25] Expires November 2005
* Top-level header field 'To:' SHOULD be the value of the * Top-level header field 'To:' SHOULD be the value of the
'Disposition-Notification-To:' header field of the message whose 'Disposition-Notification-To:' header field of the message whose
disposition is being reported . disposition is being reported .
* Top-level header field 'From:' SHOULD be the address of the * Top-level header field 'From:' SHOULD be the address of the
recipient that the read report concerns. recipient that the read report concerns.
2.1.4.4 Disposition Report Mapping from Internet Message to MMS 2.1.4.4 Disposition Report Mapping from Internet Message to MMS
The following table maps information elements from a disposition The following table maps information elements from a disposition
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 |[DSN=Msg] 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: |'Original-Envelope-ID' field
message (object of | | message (object of | |
disposition report)| | disposition report)| |
-------------------|------------------|-------------------------------- -------------------|------------------|--------------------------------
Recipient address |From: |'Final-Recipient' field Recipient address |From: |'Final-Recipient' field
of the original | | of the original | |
message | | message | |
-------------------|------------------|-------------------------------- -------------------|------------------|--------------------------------
skipping to change at line 1146 skipping to change at line 1146
| | | |
| |Value taken from 'Disposition- | |Value taken from 'Disposition-
| |Notification-To:' header field | |Notification-To:' header field
| |of message being reported, not | |of message being reported, not
| |its 'From:' header field. | |its 'From:' header field.
-------------------|------------------|-------------------------------- -------------------|------------------|--------------------------------
Date and time the |Date: |'Date:' header field value of Date and time the |Date: |'Date:' header field value of
message was handled| |top-level message was handled| |top-level
===================|==================|================================ ===================|==================|================================
Gellens [Page 26] Expires October 2005 Gellens [Page 26] Expires November 2005
===================|==================|================================ ===================|==================|================================
Information Element|MMS Read Report |[DSN=Msg] 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 |
|disposition-type | |disposition-type |
|value 'displayed')| |value 'displayed')|
| | | |
|'Deleted without | |'Deleted without |
|being read' (used | |being read' (used |
skipping to change at line 1193 skipping to change at line 1194
3 Security Considerations 3 Security Considerations
Data contained within messages should not be automatically trusted. Data contained within messages should not be automatically trusted.
Even within a carrier's network, and certainly within the Internet, Even within a carrier's network, and certainly within the Internet,
various deliberate and accidental attacks or corruptions are various deliberate and accidental attacks or corruptions are
possible. For example, routers may contain vulnerabilities which possible. For example, routers may contain vulnerabilities which
may be exploited, IP traffic may be intercepted and/or modified, may be exploited, IP traffic may be intercepted and/or modified,
etc. etc.
Gellens [Page 27] Expires October 2005 Gellens [Page 27] Expires November 2005
The following messaging-related security threats can be identified: The following messaging-related security threats can be identified:
* Misidentification of message source. * Misidentification of message source.
* Message interception (unauthorized disclosure of contents). * Message interception (unauthorized disclosure of contents).
* Unauthorized disclosure of message sender or recipient. * Unauthorized disclosure of message sender or recipient.
* Message modification (by adversary). * Message modification (by adversary).
skipping to change at line 1244 skipping to change at line 1245
the gateway function to ensure that Bcc recipients which do appear the gateway function to ensure that Bcc recipients which do appear
are deleted from the message content. are deleted from the message content.
Some MMS features contain inherently more risk than others. For Some MMS features contain inherently more risk than others. For
example, reply charging and sender address hiding. The reply example, reply charging and sender address hiding. The reply
charging mechanism requires a high degree of trust between entities charging mechanism requires a high degree of trust between entities
with little technical basis. Deliberate or accidental abuse of this with little technical basis. Deliberate or accidental abuse of this
trust can result in unexpected or unauthorized charges. For trust can result in unexpected or unauthorized charges. For
example, a sender may be charged for unauthorized replies, or a example, a sender may be charged for unauthorized replies, or a
Gellens [Page 28] Expires October 2005 Gellens [Page 28] Expires November 2005
sender may be charged for a reply which the author thought would be sender may be charged for a reply which the author thought would be
paid for by the recipient. A sender's identity may be disclosed in paid for by the recipient. A sender's identity may be disclosed in
violation of a request for this to be blocked. The identity of violation of a request for this to be blocked. The identity of
recipients may be disclosed to other recipients (or even recipients may be disclosed to other recipients (or even
non-recipients) for a message in which the sender intended for the non-recipients) for a message in which the sender intended for the
recipients not to be disclosed. recipients not to be disclosed.
It is possible to hide the sender's identity from non-recipients It is possible to hide the sender's identity from non-recipients
using anonymous remailers. It is hard to hide the sender's identity using anonymous remailers. It is hard to hide the sender's identity
from recipients when the mail is cryptographically signed. In view from recipients when the mail is cryptographically signed. In view
of anti-spam measures it may be undesirable to hide the sender's of anti-spam measures it may be undesirable to hide the sender's
identity. identity.
Additional mechanisms can be developed to protect against various Additional mechanisms can be developed to protect against various
threats, however, these are not included in this version of this threats, however, these are not included in this version of this
specification. It is strongly RECOMMENDED that features such as specification. It is strongly RECOMMENDED that features such as
reply charging and sender identity hiding not be used across carrier reply charging and sender identity hiding not be used across carrier
domains, and be used within carrier domains only with full domains, and be used within carrier domains only with full
understanding of the risks involved. understanding of the risks involved.
4 Normative References 4 IANA Considerations
No actions are requested of IANA.
5 Normative References
IETF: IETF:
[DSN-Msg] "An Extensible Message Format for Delivery Status [DSN-Msg] "An Extensible Message Format for Delivery Status
Notifications", Moore, Vaudreuil, RFC 3464, January 2003. Notifications", Moore, Vaudreuil, RFC 3464, January 2003.
[DSN-SMTP] "SMTP Service Extension for Delivery Status [DSN-SMTP] "SMTP Service Extension for Delivery Status
Notifications", Moore, RFC 3461, January 2003. Notifications", Moore, RFC 3461, January 2003.
[Hdr-Enc] "MIME (Multipurpose Internet Mail Extensions) Part Three: [Hdr-Enc] "MIME (Multipurpose Internet Mail Extensions) Part Three:
Message Header Extensions for Non-ASCII Text", Moore, RFC 2047, Message Header Extensions for Non-ASCII Text", Moore, RFC 2047,
November 1996. November 1996.
[KEYWORDS] Bradner, "Key words for use in RFCs to Indicate [KEYWORDS] Bradner, "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, Harvard University, March 1997. Requirement Levels", RFC 2119, Harvard University, March 1997.
[MDN] "An Extensible Message Format for Message Disposition [MDN] "Message Disposition Notification", Hansen, Vaudreuil, RFC
Notifications", Fajman, RFC 2298, March 1998. 3798, May 2004.
Gellens [Page 29] Expires November 2005
[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
Gellens [Page 29] Expires October 2005 [RESP] "Enhanced Mail System Status Codes", Vaudreuil, RFC 3463,
[RESP] Enhanced Mail System Status Codes, Vaudreuil, RFC 1893, January 2003.
January 1996.
[SMTP] "Simple Mail Transfer Protocol", Klensin, RFC 2821, April [SMTP] "Simple Mail Transfer Protocol", Klensin, RFC 2821, April
2001. 2001.
5 Informative References 6 Informative References
IETF: IETF:
[Auth] "SMTP Service Extension for Authentication", Myers, RFC 2554, [Auth] "SMTP Service Extension for Authentication", Myers, RFC 2554,
March 1999 March 1999
[BINARY] SMTP Service Extensions for Transmission of Large and [BINARY] SMTP Service Extensions for Transmission of Large and
Binary MIME Messages", Vaudreuil, Parsons, RFC 3030, December 2000. Binary MIME Messages", Vaudreuil, Parsons, RFC 3030, December 2000.
[Codes] "SMTP Service Extension for Returning Enhanced Error Codes", [Codes] "SMTP Service Extension for Returning Enhanced Error Codes",
skipping to change at line 1332 skipping to change at line 1337
[PGP] "MIME Security with OpenPGP", Elkins, Del Torto, Levien, [PGP] "MIME Security with OpenPGP", Elkins, Del Torto, Levien,
Roessler, RFC 3156, August 2001 Roessler, RFC 3156, August 2001
[SMIME] "S/MIME Version 3 Message Specification", Ramsdell, RFC [SMIME] "S/MIME Version 3 Message Specification", Ramsdell, RFC
2633, June 1999 2633, June 1999
[StartTLS] "SMTP Service Extension for Secure SMTP over Transport [StartTLS] "SMTP Service Extension for Secure SMTP over Transport
Layer Security", Hoffman, RFC 3207, February 2002 Layer Security", Hoffman, RFC 3207, February 2002
Gellens [Page 30] Expires November 2005
[Submission] "Message Submission", Gellens, Klensin, RFC 2476, [Submission] "Message Submission", Gellens, Klensin, RFC 2476,
December 1998. December 1998.
[VPIM] "Voice Profile Internet Mail - Version 2", Vaudreuil, [VPIM] "Voice Profile for Internet Mail - version 2 (VPIMv2)",
Parsons, RFC 2421, September 1998. Vaudreuil, Parsons, RFC 3801, June 2004.
Gellens [Page 30] Expires October 2005
OMA: OMA:
OMA specifications are available at the OMA web site OMA specifications are available at the OMA web site
<http://www.openmobilealliance.org>. <http://www.openmobilealliance.org>.
[OMA-MMS] OMA-WAP-MMS-ENC-V1_2-20040323-C [OMA-MMS] OMA-WAP-MMS-ENC-V1_2-20040323-C
3GPP2 and 3GPP: 3GPP2 and 3GPP:
3GPP2 specifications are available at the 3GPP2 (Third 3GPP2 specifications are available at the 3GPP2 (Third
skipping to change at line 1363 skipping to change at line 1368
Partnership Project) web site <http://www.3gpp.org> Partnership Project) web site <http://www.3gpp.org>
[Stage_3] "MMS MM1 Stage 3 using OMA/WAP", X.S0016-310 [Stage_3] "MMS MM1 Stage 3 using OMA/WAP", X.S0016-310
"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.
[Formats] "Multimedia Messaging Service (MMS) Media Format and [Formats] "Multimedia Messaging Service (MMS) Media Format and
Codecs for cdma2000 Spread Spectrum Systems, C.S0045 Codecs for cdma2000 Spread Spectrum Systems", C.S0045
[Overview] "Multimedia Messaging Services (MMS) Overview", [Overview] "Multimedia Messaging Services (MMS) Overview",
X.S0016-000 X.S0016-000
[Stage_1] "Multimedia Messaging Services (MMS); Stage 1", [Stage_1] "Multimedia Messaging Services (MMS); Stage 1",
Requirements, October 2002, S.R0064-0. Requirements, October 2002, S.R0064-0.
[Stage_2] Multimedia Messaging Service (MMS); Stage 2", Functional [Stage_2] "Multimedia Messaging Service (MMS); Stage 2", Functional
Specification, April 2003, X.S0016-200. Specification, April 2003, X.S0016-200.
"Multimedia Messaging Service; Media formats and codecs", "Multimedia Messaging Service; Media formats and codecs",
TS26.140Release 5. TS26.140Release 5.
6 Author's Address Gellens [Page 31] Expires November 2005
7 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
USA
randy@qualcomm.com randy@qualcomm.com
Gellens [Page 31] Expires October 2005
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 or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed
pertain to the implementation or use of the technology described in to pertain to the implementation or use of the technology described
this document or the extent to which any license under such rights in this document or the extent to which any license under such
might or might not be available; neither does it represent that it rights might or might not be available; nor does it represent that
has made any effort to identify any such rights. Information on the it has made any independent effort to identify any such rights.
IETF's procedures with respect to rights in standards-track and Information on the procedures with respect to rights in RFC
standards-related documentation can be found in BCP-11. Copies of documents can be found in BCP 78 and BCP 79.
claims of rights made available for publication and any assurances
of licenses to be made available, or the result of an attempt made Copies of IPR disclosures made to the IETF Secretariat and any
to obtain a general license or permission for the use of such assurances of licenses to be made available, or the result of an
proprietary rights by implementors or users of this specification attempt made to obtain a general license or permission for the use
can be obtained from the IETF Secretariat. of such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository
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
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at
Director. ietf-ipr@ietf.org.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2004). Copyright (C) The Internet Society (2005).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
Disclaimer
This document and the information contained herein are provided on This document and the information contained herein are provided on
an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Gellens [Page 32] Expires October 2005 Gellens [Page 32] Expires November 2005
 End of changes. 

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