IETF Logo Mail Archive

Re: [Sip] Support for Multipart/MIME

Paul Kyzivat <pkyzivat@cisco.com> Wed, 23 May 2007 18:39 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 1HqvkB-0005XR-O0; Wed, 23 May 2007 14:39:31 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1HqvkA-0005OV-8Y for sip-confirm+ok@megatron.ietf.org; Wed, 23 May 2007 14:39:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hqvk9-0005O8-V7 for sip@ietf.org; Wed, 23 May 2007 14:39:29 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hqvk8-0004c7-JK for sip@ietf.org; Wed, 23 May 2007 14:39:29 -0400
Received: from sj-dkim-7.cisco.com ([171.68.10.88]) by sj-iport-5.cisco.com with ESMTP; 23 May 2007 11:39:27 -0700
X-IronPort-AV: i="4.14,571,1170662400"; d="scan'208"; a="156694780:sNHT48736890"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id l4NIdRcm015073; Wed, 23 May 2007 11:39:27 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l4NIdOVB018782; Wed, 23 May 2007 18:39:27 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 23 May 2007 14:39:20 -0400
Received: from [161.44.174.124] ([161.44.174.124]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 23 May 2007 14:39:19 -0400
Message-ID: <46548A53.8070005@cisco.com>
Date: Wed, 23 May 2007 14:39:15 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Francois Audet <audet@nortel.com>
Subject: Re: [Sip] Support for Multipart/MIME
References: <7374777208BDC7449D5620EF9423256703F85957@esealmw113.eemea.ericsson.se> <0ee901c7931e$dd43f9b0$c4a36b80@amer.cisco.com> <1ECE0EB50388174790F9694F77522CCF106564B4@zrc2hxm0.corp.nortel.com> <4643B58A.3060407@cisco.com> <464ABDD6.9000503@ericsson.com> <464AF68A.4010105@cisco.com> <1ECE0EB50388174790F9694F77522CCF10788B8C@zrc2hxm0.corp.nortel.com> <4653FA1F.7050008@ericsson.com> <1ECE0EB50388174790F9694F77522CCF10954E05@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF10954E05@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 May 2007 18:39:19.0893 (UTC) FILETIME=[ACC2E850:01C79D69]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=527; t=1179945567; x=1180809567; c=relaxed/simple; s=sjdkim7002; 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; bh=fgkJPaV6Wyh1s4MwNoJS+2Hjlr3BPmGfjePXNPEsT1E=; b=F8VDZuVSj9vpCeN33otXwJnaKSVySog/9bmdiJBQNN8rCQmQj/Uu0Wnj/peYlwUW9fvTswbP 1uf1CmaOFIefytXNnF3DCH0pe7gTcz2GFHU+qY6xdhkm7Yx1tawYyuhT;
Authentication-Results: sj-dkim-7; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/sjdkim7002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: sip@ietf.org, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Dan Wing <dwing@cisco.com>, "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

Francois Audet wrote:

>   I believe this is in line with RFC 3261/8.2.3. I will point out that 
>   we have found in the field that if a UAS does NOT send a 415 and just
>   "ignores" the Multipart body altogether, what happens is that the
>   receiver of the INVITE interprets the INVITE as having NO initial
>   Offer, and sends an an Offer of it's own in the 200/18X. This is
>   interpreted by the sender of the INVITE as an Answer, resulting in
>   all hell breaking loose.

This is great! I love it.

	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

v2.23.0 | Report a Bug | By Email