RE: [Sip] Support for Multipart/MIME

"Christer Holmberg \(JO/LMF\)" <christer.holmberg@ericsson.com> Thu, 10 May 2007 05:59 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 1Hm1gg-0007fv-Qn; Thu, 10 May 2007 01:59:38 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Hm1gf-0007fX-7A for sip-confirm+ok@megatron.ietf.org; Thu, 10 May 2007 01:59:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hm1ge-0007fG-EC for sip@ietf.org; Thu, 10 May 2007 01:59:36 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hm1gc-0007Pz-SZ for sip@ietf.org; Thu, 10 May 2007 01:59:36 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 468C62152E; Thu, 10 May 2007 07:59:34 +0200 (CEST)
X-AuditID: c1b4fb3e-ad9eabb0000061ca-f1-4642b4c663d5
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 3669B214A1; Thu, 10 May 2007 07:59:34 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 10 May 2007 07:59:33 +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: Thu, 10 May 2007 07:59:30 +0200
Message-ID: <7374777208BDC7449D5620EF9423256703F225D1@esealmw113.eemea.ericsson.se>
In-Reply-To: <0dc501c792c2$87cf9ef0$c4a36b80@amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] Support for Multipart/MIME
Thread-Index: AceLQnkGjbn27+D9RPmgzW7CtVAiTwCLfMUAAT8wFTAADhBjIAAATZvgAABUtoAABLgJwAAA6cWwAAD+cyAAAS32gA==
References: <7374777208BDC7449D5620EF9423256703F224D6@esealmw113.eemea.ericsson.se> <0dc501c792c2$87cf9ef0$c4a36b80@amer.cisco.com>
From: "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com>
To: Dan Wing <dwing@cisco.com>, Dale.Worley@comcast.net
X-OriginalArrivalTime: 10 May 2007 05:59:33.0884 (UTC) FILETIME=[620333C0:01C792C8]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
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, 

>>The point is that, depending on what media the answerer chooses, 
>>different codecs can be used for chosen media streams.
>> 
>>Yes, "vanilla" SDP allows me to offer audio and video, and the 
>>answerer can incdicate what it does/doesn't support. But, vanilla SDP 
>>does not allow the offer to say: "Here is audio and video. If you 
>>accept both then let's use these codecs, but if you only choose audio 
>>then let's use theis other codec".
> 
>SDP Capabilities Negotiation does that, too -- and far better 
>than multipart/alternative.

I haven't seen any comparision between the mechanisms, so I can't
comment on the "far better" statement at this point.

But, in order to do the same thing with SDP CapNeg, I assume it does
require the remote terminal to actually support SDP CapNeg?

I agree that many terminals don't support multipart today, but wasn't
the initial issue of this thread that we want to mandate the support of
multipart (at least multipart/mixed)?

Also, my initial intention was not to compare multipart/alternative with
SDP CapNeg, but to give an example what multipart/alternative could be
used for.

Regards,

Christer


_______________________________________________
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