IETF Logo Mail Archive

Re: [Sip] Support for Multipart/MIME

Paul Kyzivat <pkyzivat@cisco.com> Thu, 10 May 2007 17:22 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 1HmCLK-0004if-L7; Thu, 10 May 2007 13:22:18 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1HmCLI-0004iS-HB for sip-confirm+ok@megatron.ietf.org; Thu, 10 May 2007 13:22:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmCLI-0004iK-7f for sip@ietf.org; Thu, 10 May 2007 13:22:16 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmCLG-0004Ny-Ua for sip@ietf.org; Thu, 10 May 2007 13:22:16 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 10 May 2007 13:22:14 -0400
X-IronPort-AV: i="4.14,518,1170651600"; d="scan'208"; a="120778657:sNHT46816452"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l4AHMEFo000531; Thu, 10 May 2007 13:22:14 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l4AHLule014657; Thu, 10 May 2007 17:22:14 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 10 May 2007 13:22:11 -0400
Received: from [161.44.174.124] ([161.44.174.124]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 10 May 2007 13:22:10 -0400
Message-ID: <464354C1.6030003@cisco.com>
Date: Thu, 10 May 2007 13:22:09 -0400
From: Paul Kyzivat <pkyzivat@cisco.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: <0ee901c7931e$dd43f9b0$c4a36b80@amer.cisco.com>
In-Reply-To: <0ee901c7931e$dd43f9b0$c4a36b80@amer.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 May 2007 17:22:10.0827 (UTC) FILETIME=[BE40BDB0:01C79327]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=983; t=1178817734; x=1179681734; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com> |Subject:=20Re=3A=20[Sip]=20Support=20for=20Multipart/MIME |Sender:=20 |To:=20Dan=20Wing=20<dwing@cisco.com>; bh=c1FAgyxlcmaFfnrfl2Pipnj14WMWRIPZSb893qFMX8g=; b=yUITOFR5SiDEFphSl10FUkMtOdK678ZHRuki/Y6GXKXXifEYXRQhn9gRQbbteTqtZ+t1UE/v 6u5V90BnXecqFhexyUK7pk3gw0IIVyZ5LXOqHNglsjqTxftbOtgf7on4;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
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

I think it will be easier to make progress on multipart/mixed than 
multipart/alternative. It appears that making progress on alternative 
will be difficult without some use cases to help in defining what it 
means to "support" one of the alternatives.

	Paul

Dan Wing wrote:
>>> I have become convinced, through my efforts with RTPSEC, that 
>>> multipart/alternative is harmful if it contains multiple SDP parts.
>> Again, I am not in a position to disagree with you ,but is that
>> harmfulness documented somewhere?
> 
> Nope.  If we're going to move multipart/* forward in SIP, though,
> I'll be happy to write that section.
> 
> -d
> 
> 
> _______________________________________________
> 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
> 


_______________________________________________
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