Re: [Sip] Support for Multipart/MIME

Dean Willis <dean.willis@softarmor.com> Wed, 09 May 2007 20:54 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 1HltB6-0000gn-3V; Wed, 09 May 2007 16:54:28 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1HltB4-0000gf-Hn for sip-confirm+ok@megatron.ietf.org; Wed, 09 May 2007 16:54:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HltB4-0000fG-7w for sip@ietf.org; Wed, 09 May 2007 16:54:26 -0400
Received: from nylon.softarmor.com ([66.135.38.164]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HltB1-0000AK-Uc for sip@ietf.org; Wed, 09 May 2007 16:54:26 -0400
Received: from [64.101.172.158] ([64.101.172.158]) (authenticated bits=0) by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id l49JxPN6011166 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 9 May 2007 14:59:26 -0500
In-Reply-To: <p06240607c267dd30be52@[76.102.225.135]>
References: <7374777208BDC7449D5620EF9423256703CB4EDA@esealmw113.eemea.ericsson.se> <0c1401c7926e$6872f290$c4a36b80@amer.cisco.com> <XFE-RTP-201K4dz4oRq000054d1@xfe-rtp-201.amer.cisco.com> <p06240607c267dd30be52@[76.102.225.135]>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <D41AD8C9-B180-4EC6-B388-A326A7223B7D@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Support for Multipart/MIME
Date: Wed, 09 May 2007 15:52:01 -0500
To: Ted Hardie <hardie@qualcomm.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: sip@ietf.org, "James M. Polk" <jmpolk@cisco.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

On May 9, 2007, at 3:22 PM, Ted Hardie wrote:

> At 2:40 PM -0500 5/9/07, James M. Polk wrote:
>> It's possible/probable/obvious (depending on who you talk to) that  
>> multipart will have to be supported for emergency calling, in  
>> which there is an SDP body and a Location message body...
>>
>> This doesn't mean UAs that *don't* establish voice/video dialogs  
>> will have to support multipart, just for those UAs that do  
>> establish voice/video dialogs with emergency response centers  
>> (again, depending on who you talk to).
>
> That won't be multipart/alternative, though, as the location body  
> and the SDP body
> won't be alternatives but independent items.   I think they would be
> multipart/mixed.  See this from RFC 2046:

Right. Mixed is a far cleaner semantic problem than alternative. It  
means "Use all of these that you understand, to the best of your  
ability, and complain if there's nothing you understand."

--
Dean



_______________________________________________
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