IETF Logo Mail Archive

RE: [Sip] Support for Multipart/MIME

"Elwell, John" <john.elwell@siemens.com> Thu, 24 May 2007 08:57 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 1Hr985-0005bK-E8; Thu, 24 May 2007 04:57:05 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Hr984-0005b8-Iv for sip-confirm+ok@megatron.ietf.org; Thu, 24 May 2007 04:57:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hr984-0005b0-8l for sip@ietf.org; Thu, 24 May 2007 04:57:04 -0400
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225] helo=bemg01.siemenscomms.co.uk) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hr982-0006B1-Vg for sip@ietf.org; Thu, 24 May 2007 04:57:04 -0400
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235]) by siemenscomms.co.uk (PMDF V6.0-24 #40642) with ESMTP id <0JIJ00J3ZFISG5@siemenscomms.co.uk> for sip@ietf.org; Thu, 24 May 2007 09:56:52 +0100 (BST)
Date: Thu, 24 May 2007 09:57:01 +0100
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [Sip] Support for Multipart/MIME
In-reply-to: <1ECE0EB50388174790F9694F77522CCF1095509E@zrc2hxm0.corp.nortel.com>
To: Francois Audet <audet@nortel.com>, Dan Wing <dwing@cisco.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D012F0D4@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Thread-Topic: [Sip] Support for Multipart/MIME
Thread-Index: AcedE7xDnn/4S1ijTdWu/Bynue9sgwATc2swAAIrF/AAAPUqIAABB/4AAADEa9AAAIzN4AAAR+nAABovpxA=
Content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
References: <1ECE0EB50388174790F9694F77522CCF10955027@zrc2hxm0.corp.nortel.com> <0bb501c79d78$6599e7d0$c6f0200a@amer.cisco.com> <1ECE0EB50388174790F9694F77522CCF1095509E@zrc2hxm0.corp.nortel.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@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

 

> -----Original Message-----
> From: Francois Audet [mailto:audet@nortel.com] 
> Sent: 23 May 2007 21:37
> To: Dan Wing; Gonzalo Camarillo
> Cc: sip@ietf.org; Paul Kyzivat; Christer Holmberg (JO/LMF)
> Subject: RE: [Sip] Support for Multipart/MIME
> 
> 
>  
> > In RFC3204, the QSIG or ISUP parts do not appear to have any 
> > meaning without the SDP.  Or do they?  For example, is it 
> > meaningful for me to send an INVITE that has only the QSIG 
> > part (and no SDP)?
> 
> Sure: it's just a delayed offer answer. 
[JRE]Moreover, QSIG or ISUP parts can be sent in other messages without
SDP, e.g., in an INFO request.

John


_______________________________________________
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