[Sipping] draft-hilt-sipping-overload and RPH
Janet P Gunn <jgunn6@csc.com> Thu, 30 August 2007 21:16 UTC
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQrNF-0008Ce-JZ; Thu, 30 Aug 2007 17:16:21 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43) id 1IQrNE-00089G-7p for sipping-confirm+ok@megatron.ietf.org; Thu, 30 Aug 2007 17:16:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQrND-000898-UP for sipping@ietf.org; Thu, 30 Aug 2007 17:16:19 -0400
Received: from mail86.messagelabs.com ([216.82.244.115]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IQrNC-0007Rz-MM for sipping@ietf.org; Thu, 30 Aug 2007 17:16:19 -0400
X-VirusChecked: Checked
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-2.tower-86.messagelabs.com!1188508546!26284439!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [20.137.52.151]
Received: (qmail 12491 invoked from network); 30 Aug 2007 21:15:47 -0000
Received: from amer-mta07.csc.com (HELO amer-mta07.csc.com) (20.137.52.151) by server-2.tower-86.messagelabs.com with AES256-SHA encrypted SMTP; 30 Aug 2007 21:15:47 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta07.csc.com (Switch-3.1.6/Switch-3.1.7) with ESMTP id l7ULEYfP018356 for <sipping@ietf.org>; Thu, 30 Aug 2007 17:16:04 -0400 (EDT)
To: sipping@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes 652HF83 November 04, 2004
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OFCFBCBB2C.9D8066FF-ON85257347.00746623-85257347.0074A87C@csc.com>
Date: Thu, 30 Aug 2007 17:14:13 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 7.0.2FP1 HF180|March 29, 2007) at 08/30/2007 05:14:22 PM, Serialize complete at 08/30/2007 05:14:22 PM
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd
Subject: [Sipping] draft-hilt-sipping-overload and RPH
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1228125398=="
Errors-To: sipping-bounces@ietf.org
Section 4.3 of Session Initiation Protocol (SIP) Overload Control (draft-hilt-sipping-overload-02) provides priority treatment for Emergency requests, in accordance with “ [8] Rosen, B., "Framework for Emergency Calling in Internet Multimedia", draft-ietf-ecrit-framework-01 (work in progress), March 2007.” “4.3. Emergency Services Requests It is generally recommended that SIP servers, which need to reject requests due to overload, SHOULD treat emergency services request [8] with highest priority and preserve them if possible. When a SIP server receives an emergency services request, it should not be treated by alleviation methods and should be processed immediately. In some cases, a SIP server may receive more emergency services requests than it is allowed to forward. This may happen, for example, to a SIP server that is serving an emergency service center. In these cases and after rejecting/redirecting all non-emergency service requests, a SIP server should also include emergency service requests in the alleviation treatment to avoid that the downstream server becomes overloaded.” However this document also references. “[6] Rosenberg, J., "Requirements for Management of Overload in the Session Initiation Protocol", draft-rosenberg-sipping-overload-reqs-02 (work in progress), October 2006.” In the requirements document, Requirement 13 says: “ REQ 13: The mechanism must not dictate a specific algorithm for prioritizing the processing of work within a proxy during times of overload. It must permit a proxy to prioritize requests based on any local policy, so that certain ones (such as a call for emergency services or a call with a specific value of of the Resource-Priority header field [3]) are processed ahead of others.” draft-hilt-sipping-overload-02 prioritizes treatment for “an emergency services request”, but does not provide prioritized treatment for “a call with a specific value of the Resource-Priority header field”. I would like to see draft-hilt-sipping-overload-02 modified to provide prioritized treatment for BOTH “emergency services” and “specific value of RPH” Thanks Janet -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
_______________________________________________ Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@cs.columbia.edu for questions on current sip Use sip@ietf.org for new developments of core SIP
- [Sipping] draft-hilt-sipping-overload and RPH Janet P Gunn
- Re: [Sipping] draft-hilt-sipping-overload and RPH Volker Hilt