RE: [Sip] Support for Multipart/MIME

"Francois Audet" <audet@nortel.com> Fri, 11 May 2007 16:13 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 1HmXkP-0002Dj-Pu; Fri, 11 May 2007 12:13:37 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1HmXkO-0002Db-13 for sip-confirm+ok@megatron.ietf.org; Fri, 11 May 2007 12:13:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmXkN-0002DR-NU for sip@ietf.org; Fri, 11 May 2007 12:13:35 -0400
Received: from zrtps0kp.nortel.com ([47.140.192.56]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmXkM-0001Ud-Gw for sip@ietf.org; Fri, 11 May 2007 12:13:35 -0400
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id l4BGDUh19170; Fri, 11 May 2007 16:13:30 GMT
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: Fri, 11 May 2007 11:13:28 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF106B9EFA@zrc2hxm0.corp.nortel.com>
In-reply-to: <115b01c79364$7f4d8d30$c4a36b80@amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] Support for Multipart/MIME
Thread-Index: AceTYW/Klv+XpbSFQYiKAzUiPWIulwAAeWJQACD4liA=
References: <4643B58A.3060407@cisco.com> <115b01c79364$7f4d8d30$c4a36b80@amer.cisco.com>
From: Francois Audet <audet@nortel.com>
To: Dan Wing <dwing@cisco.com>, Paul Kyzivat <pkyzivat@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
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

 

> > >   What we really need to say is that multipart/alternative may be 
> > > used only when we
> > >   are using alternative payload types for the same 
> information. For 
> > > example, text/html and
> > >   text/xml or whatever. It would be applicable if one day we 
> > > re-created another SDPng for example.
> > 
> > The perfect example for that is MESSAGE with text/plain and 
> text/html, 
> > quite analogous to an email message.
> 
> That is sufficient justification to include multipart/alternative.

Exactly what I had in mind. I was suggesting we replace the SRTP example
in 
the document with this example.


_______________________________________________
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