RE: [Sip] Support for Multipart/MIME

"Christer Holmberg \(JO/LMF\)" <christer.holmberg@ericsson.com> Thu, 03 May 2007 10:50 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 1HjYt1-0001mX-V0; Thu, 03 May 2007 06:50:11 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1HjYt1-0001mM-3s for sip-confirm+ok@megatron.ietf.org; Thu, 03 May 2007 06:50:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HjYt0-0001mC-Qd for sip@ietf.org; Thu, 03 May 2007 06:50:10 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HjYsy-0004vI-4F for sip@ietf.org; Thu, 03 May 2007 06:50:10 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 669B420959; Thu, 3 May 2007 12:50:07 +0200 (CEST)
X-AuditID: c1b4fb3c-a94ecbb0000073d5-dd-4639be5f4e67
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 59A5F20985; Thu, 3 May 2007 12:50:07 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 3 May 2007 12:50:07 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] Support for Multipart/MIME
Date: Thu, 03 May 2007 12:50:06 +0200
Message-ID: <7374777208BDC7449D5620EF9423256703CB4EDA@esealmw113.eemea.ericsson.se>
In-Reply-To: <200704301612.l3UGCwsM029162@dragon.ariadne.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] Support for Multipart/MIME
Thread-Index: AceLQnkGjbn27+D9RPmgzW7CtVAiTwCLfMUA
References: <075001c788fc$9f6a2be0$640fa8c0@cis.neustar.com><9D498630-D070-4E7B-8C94-0EF349C7D29B@cisco.com> <200704301612.l3UGCwsM029162@dragon.ariadne.com>
From: "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com>
To: Dale.Worley@comcast.net, sip@ietf.org
X-OriginalArrivalTime: 03 May 2007 10:50:07.0261 (UTC) FILETIME=[D0392CD0:01C78D70]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc:
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,

Multipart/alternative is interesting. I guess that, for SDP, it could be
used to provide different "offer alternatives". I think it would be good
to compare it against some of the other grouping/alternative mechanisms
we have defined for that purpose.

Regards,

Christer
 

> -----Original Message-----
> From: Dale.Worley@comcast.net [mailto:Dale.Worley@comcast.net] 
> Sent: 30. huhtikuuta 2007 19:13
> To: sip@ietf.org
> Subject: Re: [Sip] Support for Multipart/MIME
> 
>    From: Cullen Jennings <fluffy@cisco.com>
> 
>    I think the WG should consider an update to 3261 (likely 
> done through  
>    the process Keith has proposed) that makes this multipart/MIME  
>    mandatory to implement.
> 
> I assume that the requirement is that if a message has a 
> multipart/alternative body, and the UA is capable of 
> understanding one part of the body, then it must be able to 
> extract that part and use it to process the message.
> 
> Dale
> 
> 
> _______________________________________________
> 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