RE: [Sip] INFO message belongs only to INVITE dialog usage?

"Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com> Thu, 31 May 2007 20:44 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 1HtrVX-00073h-Q6; Thu, 31 May 2007 16:44:31 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1HtrVV-00073J-Iy for sip-confirm+ok@megatron.ietf.org; Thu, 31 May 2007 16:44:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HtrVV-00072m-7x for sip@ietf.org; Thu, 31 May 2007 16:44:29 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HtrVU-0004hO-JP for sip@ietf.org; Thu, 31 May 2007 16:44:29 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 08E71201F3; Thu, 31 May 2007 22:44:28 +0200 (CEST)
X-AuditID: c1b4fb3e-af1edbb0000061ca-d7-465f33abf753
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id EB0E020018; Thu, 31 May 2007 22:44:27 +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, 31 May 2007 22:44:27 +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] INFO message belongs only to INVITE dialog usage?
Date: Thu, 31 May 2007 22:44:26 +0200
Message-ID: <7374777208BDC7449D5620EF94232567049910DA@esealmw113.eemea.ericsson.se>
In-Reply-To: <B120B991-D607-4F44-ABB0-023C7FA3AFA3@softarmor.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] INFO message belongs only to INVITE dialog usage?
thread-index: AcejnY8yn2h1ODZpT+CeklJzvvJdsQAJWS0g
References: <465E9331.8070909@zesium.com> <B120B991-D607-4F44-ABB0-023C7FA3AFA3@softarmor.com>
From: "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com>
To: Dean Willis <dean.willis@softarmor.com>, Nina Garaca <nina.garaca@zesium.com>
X-OriginalArrivalTime: 31 May 2007 20:44:27.0620 (UTC) FILETIME=[7B052240:01C7A3C4]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: sip@ietf.org
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, 

>>I have read rfc2976 - The SIP INFO Method, but I haven't really 
>>understood that INFO message belongs only to INVITE dialog usage, 
>>which however draft-ietf-sipping-dialogusage-04 claims in its part
>>5.3:
>>
>>
>>      5.3. Matching requests to usages
>>
>>
>>
>>   For many mid-dialog requests, identifying the usage they  belong to

>>   is obvious.  A dialog can have at most one invite usage, so 
>>   any INVITE, UPDATE, PRACK, ACK, CANCEL, BYE, or INFO requests
belong to it.
>>
>> So my, question is:
>>    Can INFO message  belong to other usages, besides INVITE, such are
SUBSCRIBE  or REFER?
> >
> 
> 
>There was IIRC no intent in the writing of RFC 2976 to restrict INFO  
>to occurring within an INVITE dialog usage. So it could technically  
>be used outside of one, including in non-dialog cases.

Chapter 2 of 2976 says:

"The INFO method is used for communicating mid-session signaling
information along the signaling path for the call."

I think "mid-session" rules out the non-dialog cases, doesn't it?


On the other hand, chapter 4 says:

"There is potential that INFO messages could be forked by a SIP Proxy
Server."

That should not happen in a mid-dialo case, should it?

>However, RFC 2976 is considered to be somewhat underspecified, and so  
>far the only place we've further specified its usage is in the  
>context of transporting binary data for telephony protocol tunelling.  
>We have a standing consensus to NOT use it for arbitrary data 
>at this time. If we were to start using it, we'd need to do something
like  
>the event-packages model for INFO. So don't use it, and you won't  
>have to deal with this . . .

Eventhough not specified, in real life it IS used for sending DTMFs
(which is also listed in 2976 as an example usage, eventhough we may
have standing consensus on something else) and "non-telephony protocol"
information. I would even use the word "de facto standard" in some
cases. However, I am not aware of any non-INVITE dialog usage.

Regards,

Christer



_______________________________________________
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