RE: [Sip] Support for Multipart/MIME

"Christer Holmberg \(JO/LMF\)" <christer.holmberg@ericsson.com> Mon, 14 May 2007 05:41 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HnTJh-00030b-6W; Mon, 14 May 2007 01:41:53 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1HnTJg-00030W-9T for sip-confirm+ok@megatron.ietf.org; Mon, 14 May 2007 01:41:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HnTJf-00030O-P6 for sip@ietf.org; Mon, 14 May 2007 01:41:51 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HnTJe-00009k-5R for sip@ietf.org; Mon, 14 May 2007 01:41:51 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id CBA8D211AB; Mon, 14 May 2007 07:41:42 +0200 (CEST)
X-AuditID: c1b4fb3e-ae1ebbb0000061ca-d6-4647f69645cf
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id B108B211A8; Mon, 14 May 2007 07:41:42 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 14 May 2007 07:41:42 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] Support for Multipart/MIME
Date: Mon, 14 May 2007 07:41:38 +0200
Message-ID: <7374777208BDC7449D5620EF9423256704076AA4@esealmw113.eemea.ericsson.se>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF106B9EFA@zrc2hxm0.corp.nortel.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] Support for Multipart/MIME
Thread-Index: AceTYW/Klv+XpbSFQYiKAzUiPWIulwAAeWJQACD4liAAJRcQwA==
References: <4643B58A.3060407@cisco.com> <115b01c79364$7f4d8d30$c4a36b80@amer.cisco.com> <1ECE0EB50388174790F9694F77522CCF106B9EFA@zrc2hxm0.corp.nortel.com>
From: "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com>
To: Francois Audet <audet@nortel.com>, Dan Wing <dwing@cisco.com>, Paul Kyzivat <pkyzivat@cisco.com>
X-OriginalArrivalTime: 14 May 2007 05:41:42.0443 (UTC) FILETIME=[8D0947B0:01C795EA]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: sip@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

Hi, 

> > > >   What we really need to say is that 
> multipart/alternative may be 
> > > > used only when we
> > > >   are using alternative payload types for the same
> > information. For
> > > > example, text/html and
> > > >   text/xml or whatever. It would be applicable if one day we 
> > > > re-created another SDPng for example.
> > > 
> > > The perfect example for that is MESSAGE with text/plain and
> > text/html,
> > > quite analogous to an email message.
> > 
> > That is sufficient justification to include multipart/alternative.
> 
> Exactly what I had in mind. I was suggesting we replace the 
> SRTP example in the document with this example.

I think the document should also describe SDP, and if someone thinks
alternative doesn't work (or that some other mechanism is far better)
with SDP it should be described.

Also, we now have a number SDP extensions, related to grouping,
alternatives and capabilities, so it would probably somehow be a good
idea to collect a description/comparition of them in some document.

Regards,

Chriser

 


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip