[lemonade] Document relationship question Re: Last Call: 'Mapping Between the Multimedia Messaging Service (MMS) and Internet Mail' to Proposed Standard
Harald Tveit Alvestrand <harald@alvestrand.no> Sun, 06 November 2005 16:11 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EYn7M-000264-RS; Sun, 06 Nov 2005 11:11:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EYn0r-0001na-GT; Sun, 06 Nov 2005 11:04:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04086; Sun, 6 Nov 2005 11:04:32 -0500 (EST)
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EYnGI-0005op-3K; Sun, 06 Nov 2005 11:20:54 -0500
Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id D47AA2596D1; Sun, 6 Nov 2005 17:04:00 +0100 (CET)
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06972-06; Sun, 6 Nov 2005 17:03:54 +0100 (CET)
Received: from halvestr-w2k02.emea.cisco.com (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id B93902596BF; Sun, 6 Nov 2005 17:03:52 +0100 (CET)
Date: Sun, 06 Nov 2005 07:27:16 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: iesg@ietf.org
Message-ID: <BA241D8166C72B810B486D26@B50854F0A9192E8EC6CDA126>
In-Reply-To: <E1EYXgV-0006TV-Fy@newodin.ietf.org>
References: <E1EYXgV-0006TV-Fy@newodin.ietf.org>
X-Mailer: Mulberry/4.0.3 (Win32)
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd
X-Mailman-Approved-At: Sun, 06 Nov 2005 11:11:40 -0500
Cc: lemonade@ietf.org
Subject: [lemonade] Document relationship question Re: Last Call: 'Mapping Between the Multimedia Messaging Service (MMS) and Internet Mail' to Proposed Standard
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Enhancements to Internet email to support diverse service enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1117067103=="
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org
One issue of documentation of relationship between documents that I'd like to be reassured about...... in May 2005, the IESG approved the URI scheme "mms" as part of its approval of draft-ietf-enum-msg-05. This document contains the statement: Enumservice Name: "mms" Enumservice Type: "mms" Enumservice Subtypes: "mailto" URI Scheme: 'mailto:' Functional Specification: This Enumservice indicates that the resource identified by the associated URI scheme is capable of receiving a message using an email protocol. MMS messages are sent over SMTP using the format specified by TS 23.140 [15] section 8.4.4 and TS 26.140 [16] section 4. Within and between MMS Environments (MMSE, network infrastructures that support the MultiMedia Service), other pieces of state data (for example, charging-significant information) are exchanged between MMS Relay Servers. Thus, although these servers use SMTP as the "bearer" for their application exchanges, they map their internal state to specialised headers carried in the SMTP message exchanges. The headers used in such MMSE are described in detail in [17]. Relevant references: [15] 3GPP, "Multimedia Messaging Service (MMS); Functional description; Stage 2 (Release 5)", 3GPP TS 23.140. [16] 3GPP, "Multimedia Messaging Service (MMS); Media formats and codecs; (Release 5)", 3GPP TS 26.140. [17] Gellens, R., "Mapping Between the Multimedia Messaging Service (MMS) and Internet Mail", draft-ietf-lemonade-mms-mapping-03 (Work in Progress), April 2005. In the draft under consideration, what may be the same references as the first two are formatted oddly: Normative: [Stage_3] "MMS MM1 Stage 3 using OMA/WAP", X.S0016-310 "MMS MM4 Stage 3 Inter-Carrier Interworking", X.S0016-340 "Multimedia Messaging Service: Functional description; Stage 2", TS 23.140 Release 5. Informative: [Stage_2] "Multimedia Messaging Service (MMS); Stage 2", Functional Specification, April 2003, X.S0016-200. "Multimedia Messaging Service; Media formats and codecs", TS26.140Release 5. My research at the time of draft-ietf-enum-msg-04 (September 2004 to February 2005) indicated that both these specifications were needed to have anything like a fully specified mapping; at that time, the -lemonade- document was not referred to at all. I'd like to have reassurance that: - between the -lemonade- document, the -enum- document and the TS 23.140/26.140 documents, we have one specification for how to carry MMS over email for any given context (the insertion of the cross reference in -enum--05 seems to indicate that such a desire is present). (It's possible that the context that -enum- describes, MMS/Internet gateways, is different from the one -enum- describes. But the -enum- doc is not clear to me on this.) - the TS 26.140 reference is indeed informative for the -lemonade- spec - if any component of 23.140 or 26.140 is being updated or obsoleted by the -lemonade- spec, it is properly noted in the -lemonade- document and known to the maintainers of the 3GPP documents. It would also be nice if the references in the -lemonade- document were formatted in a more standard fashion...... the current format suggests either that the reference covers a group of unrelated documents or that there is a [tag] missing for a couple of the documents. This is not a comment about the technical content of the document, which I have not reviewed; it's just a worry that we should document our specification relationships as clearly as possible. Regards, Harald Alvestrand --On 5. november 2005 18:42 -0500 The IESG <iesg-secretary@ietf.org> wrote: > A previous version of this document was approved by the IESG. After an > appeal by John Klensin, the document was returned to the working group. > The working group has made significant changes in response to the appeal > and in relation to the follow-on discussion. This version incorporates > those changes, and the Enhancements to Internet email to support diverse > service environments WG has requested the IESG to consider the following > document: > > - 'Mapping Between the Multimedia Messaging Service (MMS) and Internet > Mail ' <draft-ietf-lemonade-mms-mapping-06.txt> as a Proposed Standard > > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send any comments to the > iesg@ietf.org or ietf@ietf.org mailing lists by 2005-11-25. > > The file can be obtained via > http://www.ietf.org/internet-drafts/draft-ietf-lemonade-mms-mapping-06.txt > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce > >
_______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade
- [lemonade] Last Call: 'Mapping Between the Multim… The IESG
- [lemonade] Last Call: 'Mapping Between the Multim… The IESG
- [lemonade] Document relationship question Re: Las… Harald Tveit Alvestrand
- Re: [lemonade] Document relationship question Re:… Randall Gellens