IETF Logo Mail Archive

Re: [Sip] Support for Multipart/MIME

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Wed, 16 May 2007 08:04 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 1HoEV5-0004If-5L; Wed, 16 May 2007 04:04:47 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1HoEV4-0004IX-0D for sip-confirm+ok@megatron.ietf.org; Wed, 16 May 2007 04:04:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HoEV3-0004IG-IU for sip@ietf.org; Wed, 16 May 2007 04:04:45 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HoEV2-0006Hv-Pq for sip@ietf.org; Wed, 16 May 2007 04:04:45 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 40A0C2119D; Wed, 16 May 2007 10:04:44 +0200 (CEST)
X-AuditID: c1b4fb3e-ad1e9bb0000061ca-36-464abb1c7690
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 3788D20FD2; Wed, 16 May 2007 10:04:44 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 16 May 2007 10:04:44 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 16 May 2007 10:04:43 +0200
Received: from [131.160.36.58] (E000FB0F665DD.lmf.ericsson.se [131.160.36.58]) by mail.lmf.ericsson.se (Postfix) with ESMTP id AEAAC2495; Wed, 16 May 2007 11:04:43 +0300 (EEST)
Message-ID: <464ABB1A.3030305@ericsson.com>
Date: Wed, 16 May 2007 11:04:42 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
Subject: Re: [Sip] Support for Multipart/MIME
References: <0dd301c792ca$7dd21ec0$c4a36b80@amer.cisco.com>
In-Reply-To: <0dd301c792ca$7dd21ec0$c4a36b80@amer.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 May 2007 08:04:43.0911 (UTC) FILETIME=[DCD0E170:01C79790]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: sip@ietf.org, "'Christer Holmberg (JO/LMF)'" <christer.holmberg@ericsson.com>
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,

> I have become convinced, through my efforts with RTPSEC, that 
> multipart/alternative is harmful if it contains multiple SDP parts.

yes; alternatives, capabilities, etc., in SDP should be expressed using 
(potentially new) SDP mechanisms (e.g., SDP attributes). I agree that 
multipart/alternative should not be used for two SDP bodies.

Cheers,

Gonzalo



_______________________________________________
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

v2.23.0 | Report a Bug | By Email