Re: [Sipping] MESSAGE Exploders draft
Miguel Garcia <Miguel.An.Garcia@nokia.com> Tue, 20 April 2004 17:18 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05521 for <sipping-archive@odin.ietf.org>; Tue, 20 Apr 2004 13:18:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFycu-0002kK-70 for sipping-archive@odin.ietf.org; Tue, 20 Apr 2004 13:01:40 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i3KH1e19010552 for sipping-archive@odin.ietf.org; Tue, 20 Apr 2004 13:01:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFyHj-0001a7-1v for sipping-web-archive@optimus.ietf.org; Tue, 20 Apr 2004 12:39:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02062 for <sipping-web-archive@ietf.org>; Tue, 20 Apr 2004 12:39:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BFyHh-0001KU-Ed for sipping-web-archive@ietf.org; Tue, 20 Apr 2004 12:39:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BFyGV-0000zS-00 for sipping-web-archive@ietf.org; Tue, 20 Apr 2004 12:38:32 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BFyFc-0000gt-00 for sipping-web-archive@ietf.org; Tue, 20 Apr 2004 12:37:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFxhF-00005n-OC; Tue, 20 Apr 2004 12:02:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFx6g-0002A7-Ny for sipping@optimus.ietf.org; Tue, 20 Apr 2004 11:24:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25109 for <sipping@ietf.org>; Tue, 20 Apr 2004 11:24:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BFx6f-00019t-T0 for sipping@ietf.org; Tue, 20 Apr 2004 11:24:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BFx5k-0000s2-00 for sipping@ietf.org; Tue, 20 Apr 2004 11:23:21 -0400
Received: from mgw-x3.nokia.com ([131.228.20.26]) by ietf-mx with esmtp (Exim 4.12) id 1BFx4w-0000az-00; Tue, 20 Apr 2004 11:22:30 -0400
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120]) by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i3KFMLm15100; Tue, 20 Apr 2004 18:22:21 +0300 (EET DST)
X-Scanned: Tue, 20 Apr 2004 18:22:07 +0300 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost) by esdks001.ntc.nokia.com (8.12.9/8.12.9) id i3KFM7u7006218; Tue, 20 Apr 2004 18:22:07 +0300
Received: from mgw-int2.ntc.nokia.com (172.21.143.97) by esdks001.ntc.nokia.com 00MseyvS; Tue, 20 Apr 2004 18:22:04 EEST
Received: from esebh001.NOE.Nokia.com (esebh001.ntc.nokia.com [172.21.138.28]) by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i3KFM2F24506; Tue, 20 Apr 2004 18:22:02 +0300 (EET DST)
Received: from nokia.com ([172.21.40.155]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Tue, 20 Apr 2004 18:22:04 +0300
Message-ID: <4085401C.2000008@nokia.com>
Date: Tue, 20 Apr 2004 18:22:04 +0300
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en, es-es
MIME-Version: 1.0
To: ext Paul Kyzivat <pkyzivat@cisco.com>
CC: SIMPLE mailing list <simple@ietf.org>, SIPPING mailing list <sipping@ietf.org>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Subject: Re: [Sipping] MESSAGE Exploders draft
References: <406DF1EC.4050400@cisco.com>
In-Reply-To: <406DF1EC.4050400@cisco.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Apr 2004 15:22:04.0911 (UTC) FILETIME=[3C99F7F0:01C426EB]
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Hi Paul: Thanks for your comments. Answers inline. ext Paul Kyzivat wrote: > Miguel, > > In general the approach in the draft seems reasonable to me. > > I see one area of ambiguity, having to do with how multipart bodies are > handled. The draft says to remove the list and include everything else. > But even your example doesn't do that - it also removes the > multipart/mixed wrapper. Of course in this particular example that makes > perfect sense, but it goes beyond what the draft says to do. We start from the the fact that there will be as a minimum, two bodies, the list, and the actual payload. There might be more bodies, such as multiple payloads, S/MIME signatures, etc. I guess the algorithm should be: - If there is any kind of security body for the exploder (e.g., signed with the public key of the exploder), then remove that body. - Remove the list itself (in a typical use case, unless an extension says the oposite; I am referring to Ben's suggestion to allow it). - If there is only one body left, then remove the multipart/mixed wrapper. - Send the remaining stuff. > > There are more complex cases: > > - for security there could be signed body parts. > > - The signature could be on the multipart containing the message > and list. It would have to be removed. > > - The signature could be on just the message. Presumably > it should remain. > I agree. > > - There could be other body parts referenced by cid: urls in > other headers in the message. Yes, they should remain. > > I think there needs to be a more prescriptive way of defining what gets > passed on in the exploded messages. This is really just a manifestation > of a more general problem of how to decide how different body parts > should be processed. It potentially exists in a normal, unexploded, MESSAGE. > > I think at least part of the answer lies with Content-Disposition. I > think there should be clarity about the content-disposition should be > for the body part(s) that MESSAGE interprets as message content. > Probably "render" (which is default for sip) would be an appropriate > content-disposition for message content. Agree so far. It may happen that some of this stuff is generic enough (not MESSAGE specific). > > Also, I think there should be some clarity about what the > content-disposition should be for various kinds of multipart containers > when used in the various ways they may be used in sip. I'm not quite > sure what the answer is here. > > The list itself is of course referenced from a cid: url. It is the url > and its placement that determines how the corresponding body part should > be processed. For these, the content-disposition should be some value > that doesn't imply some other sort of processing. I think it can't be > any of "session", "render", "alert", or "icon". Maybe it could be > "attachment". I will be happy to have a very clear deterministic way to find out what to pass and what to keep to the other side of the exploder, base on presumabley the content-disposition. Let's see if I can come up with something. Thanks, Miguel > > Paul > > > > Miguel Garcia wrote: > >>Hi: >> >>I have just submitted a draft that discusses a exploder of MESSAGEs. >> >>While it appears in the repository, you can download them from: >> >>http://people.nokia.net/~miguel/drafts/draft-garcia-simple-message-exploder-00.txt >> >>http://people.nokia.net/~miguel/drafts/draft-garcia-simple-message-exploder-00.html >> >> >>Since this is an area covered by SIMPLE (Instant Messaging) and SIPPING >>(exploders), I am copying both mailing lists. >> >>Regards, >> >> Miguel > > > > -- Miguel A. Garcia tel:+358-50-4804586 Nokia Research Center Helsinki, Finland _______________________________________________ Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@cs.columbia.edu for questions on current sip Use sip@ietf.org for new developments of core SIP
- [Sipping] MESSAGE Exploders draft Miguel Garcia
- [Sipping] Re: [Simple] MESSAGE Exploders draft Ben Campbell
- [Sipping] Re: [Simple] MESSAGE Exploders draft Ben Campbell
- Re: [Sipping] MESSAGE Exploders draft Paul Kyzivat
- [Sipping] Re: [Simple] MESSAGE Exploders draft Miguel Garcia
- [Sipping] Re: [Simple] MESSAGE Exploders draft Ben Campbell
- Re: [Sipping] MESSAGE Exploders draft Miguel Garcia
- [Sipping] Re: [Simple] MESSAGE Exploders draft Miguel Garcia
- Re: [Sipping] Re: [Simple] MESSAGE Exploders draft Niemi Aki (Nokia-M/Espoo)
- [Sipping] Managing multiple body parts Paul Kyzivat
- [Sipping] Re: Managing multiple body parts Gonzalo Camarillo
- [Sipping] Re: Managing multiple body parts Paul Kyzivat
- [Sipping] Re: [Simple] Re: Managing multiple body… Gonzalo Camarillo
- [Sipping] Re: [Simple] Re: Managing multiple body… Paul Kyzivat