Re: [Sip] Support for Multipart/MIME

Paul Kyzivat <pkyzivat@cisco.com> Wed, 09 May 2007 21:55 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 1Hlu8U-0003a9-Nn; Wed, 09 May 2007 17:55:50 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Hlu8T-0003Zz-EL for sip-confirm+ok@megatron.ietf.org; Wed, 09 May 2007 17:55:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hlu8T-0003Zm-4a for sip@ietf.org; Wed, 09 May 2007 17:55:49 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hlu8R-0000ot-T8 for sip@ietf.org; Wed, 09 May 2007 17:55:49 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 09 May 2007 17:55:48 -0400
X-IronPort-AV: i="4.14,512,1170651600"; d="scan'208"; a="59841782:sNHT43090678"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l49LtlUW013111; Wed, 9 May 2007 17:55:47 -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 l49Lt1lm023761; Wed, 9 May 2007 21:55:39 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); Wed, 9 May 2007 17:55:34 -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); Wed, 9 May 2007 17:55:33 -0400
Message-ID: <46424354.3000905@cisco.com>
Date: Wed, 09 May 2007 17:55:32 -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: <0cd601c7927e$5971bff0$c4a36b80@amer.cisco.com>
In-Reply-To: <0cd601c7927e$5971bff0$c4a36b80@amer.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 May 2007 21:55:33.0614 (UTC) FILETIME=[C4A9A8E0:01C79284]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1013; t=1178747747; x=1179611747; c=relaxed/simple; s=rtpdkim1001; 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=c0RmvhBn8tp9p5KwQ7f/DruEn19FYuf/Oouu2OnuGQ4=; b=fYJaNm1H7r2GDX9HIyN64MsGHVbmtqkcqGM/Z5ESfAbiNKA3IOyPEp7U3MSOdH3hm9gi2h9/ KxIGoenrLFIXzB7eVTANDibG8jhZweltHETpJ5rXFKw4RSXF3IwFq5qM;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: sip@ietf.org, "'James M. Polk'" <jmpolk@cisco.com>, "'Christer Holmberg (JO/LMF)'" <christer.holmberg@ericsson.com>, 'Dean Willis' <dean.willis@softarmor.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


Dan Wing wrote:

> I agree that multipart/mixed makes sense when you're sending
> different content-types and you want the receiver to process each
> one that he understands.  This is useful if you're doing an Invite
> that includes your location (application/sdp and 
> application/pidf+xml [draft-ietf-sip-location-conveyance]).
> 
> However, if you're sending SDP and SDPng, multipart/mixed does not
> make sense.  If you're sending SDP and SDPng, you want the answerer 
> to pick one.  For the next decade, anyone that understands SDPng 
> will also need to continue to understand SDP.  And we don't want the
> receiver to creatively use both the SDP offer and the SDPng offer.

It seems that this issue is moot, since SDPng seems to have been 
declared dead.

> Email is similar:  if you configure Thunderbird or Outlook to send 
> messages with text/plain and text/html they are put inside 
> multipart/related, not multipart/mixed.

Don't you mean multipart/alternative?

	Paul


_______________________________________________
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