[Sip] Need for RPH in SIP Responses
"Sandesara, Niranjan B" <nsandesa@telcordia.com> Tue, 27 November 2007 22:48 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 1Ix9EV-0008NX-L8; Tue, 27 Nov 2007 17:48:47 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Ix9ET-0008Iv-IR for sip-confirm+ok@megatron.ietf.org; Tue, 27 Nov 2007 17:48:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ix9ET-0008I9-88 for sip@ietf.org; Tue, 27 Nov 2007 17:48:45 -0500
Received: from dnsmx2pya.telcordia.com ([128.96.20.32]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ix9EQ-0005ik-BY for sip@ietf.org; Tue, 27 Nov 2007 17:48:45 -0500
Received: from pya-dte-ieg01.cc.telcordia.com (pya-dte-ieg01.cc.telcordia.com [128.96.20.21]) by dnsmx2pya.telcordia.com (8.11.7+Sun/8.9.3) with SMTP id lARMmfP14188 for <sip@ietf.org>; Tue, 27 Nov 2007 17:48:41 -0500 (EST)
Received: from rrc-dte-exbh02.dte.telcordia.com ([128.96.109.16]) by pya-dte-ieg01.cc.telcordia.com (SMSSMTP 4.1.9.35) with SMTP id M2007112717483803660 for <sip@ietf.org>; Tue, 27 Nov 2007 17:48:38 -0500
Received: from rrc-dte-exs01.dte.telcordia.com ([128.96.150.34]) by rrc-dte-exbh02.dte.telcordia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 27 Nov 2007 17:48:38 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 27 Nov 2007 17:48:37 -0500
Message-ID: <A09345776B6C7A4985573569C0F3004318F208AD@rrc-dte-exs01.dte.telcordia.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Need for RPH in SIP Responses
thread-index: AcgxR6Xo+opTKDioRVyYpl8WSOkQTQ==
From: "Sandesara, Niranjan B" <nsandesa@telcordia.com>
To: sip@ietf.org
X-OriginalArrivalTime: 27 Nov 2007 22:48:38.0805 (UTC) FILETIME=[A6A0BC50:01C83147]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0aa019322dfce838bd8604f5a841b57
Cc: "Wainberg, Stanley" <swainber@telcordia.com>
Subject: [Sip] Need for RPH in SIP Responses
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>
Content-Type: multipart/mixed; boundary="===============1686328528=="
Errors-To: sip-bounces@ietf.org
It seems to me that the strongest argument for the inclusion of RPH in SIP responses is illustrated by the following two use cases. Authentication, authorization and assignment of priority for a GETS/WPS call happens in the middle of the network, and preceding nodes (between the caller and the authenticating node) A) are initially aware of the GETS/WPS call but they need to know the priority level assigned to the call after authorization, or B) are initially not aware of the GETS/WPS call and they need to know that the call is authorized as a GETS/WPS call and they also need to know the priority level assigned to the call after authorization. The Internet Draft, "Requirements for SIP Resource Priority Header in SIP Responses" (draft-gunn-sip-req-for-rph-in-responses-00) has described the use case A). The Internet Draft, "Allowing SIP Resource Priority Header in SIP Responses" (draft-polk-sip-rph-in-responses-00) identifies the need for inclusion of RPH in SIP responses for the benefit of stateless servers in some environments. This draft proposes that a UAS can optionally include an RPH in a SIP response. It also proposes that a receiving node may choose to ignore the RPH. In other words, both the inclusion of the RPH in responses and processing of the received RPH in responses are optional capabilities. Nodes and networks can choose not to implement these capabilities. It is critical to get the RPH with the caller's priority level back to the originating network node after the GETS/WPS call authorization since this is needed to reserve access (and possibly other) resources immediately. Radio access resources are very limited, and during emergency, they are typically congested and not available to the few first responders that need to place calls. The operation of GETS/WPS is dependent on the capability of inclusion of RPH in SIP responses. Regards, Niranjan Sandesara
_______________________________________________ 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
- Re: [Sip] Need for RPH in SIP Responses ken carlberg
- [Sip] Need for RPH in SIP Responses Sandesara, Niranjan B
- Re: [Sip] Need for RPH in SIP Responses Jeroen van Bemmel
- RE: [Sip] Need for RPH in SIP Responses DOLLY, MARTIN C, ATTLABS
- Re: [Sip] Need for RPH in SIP Responses Jeroen van Bemmel
- RE: [Sip] Need for RPH in SIP Responses DRAGE, Keith (Keith)
- Re: [Sip] Need for RPH in SIP Responses Joel M. Halpern
- RE: [Sip] Need for RPH in SIP Responses DRAGE, Keith (Keith)
- [Sip] Need for RPH in SIP Responses Sandesara, Niranjan B
- Re: [Sip] Need for RPH in SIP Responses Janet P Gunn
- Re: [Sip] Need for RPH in SIP Responses ken carlberg