IETF Logo Mail Archive

Re: [sip-overload] Local Policy Re: I-D Action: draft-ietf-soc-load-control-event-package-05.txt

"Vijay K. Gurbani" <vkg@bell-labs.com> Thu, 03 January 2013 16:42 UTC

Return-Path: <vkg@bell-labs.com>
X-Original-To: sip-overload@ietfa.amsl.com
Delivered-To: sip-overload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCEB321F8CD0 for <sip-overload@ietfa.amsl.com>; Thu, 3 Jan 2013 08:42:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.362
X-Spam-Level:
X-Spam-Status: No, score=-109.362 tagged_above=-999 required=5 tests=[AWL=1.237, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 140OqxOU2H4f for <sip-overload@ietfa.amsl.com>; Thu, 3 Jan 2013 08:42:07 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 44BD421F8CA7 for <sip-overload@ietf.org>; Thu, 3 Jan 2013 08:42:02 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id r03GfTUH012274 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 3 Jan 2013 10:41:29 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r03GfTRv009563 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 3 Jan 2013 10:41:29 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r03GfPhC008225; Thu, 3 Jan 2013 10:41:25 -0600 (CST)
Message-ID: <50E5B529.2090105@bell-labs.com>
Date: Thu, 03 Jan 2013 10:43:21 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Charles Shen <charles@cs.columbia.edu>
References: <20121022163217.13864.84970.idtracker@ietfa.amsl.com> <CAPSQ9ZU_52XDJGm0AFs6fe0ZkMSiQCwp7kSoQ5nDvxjnJh5McA@mail.gmail.com> <5EBD159DE88147488A3B1590E090018403530A9E6275@njfpsrvexg2.research.att.com> <OF7CCDE698.10939705-ON85257AD4.0072A173-85257AD4.007308A2@csc.com> <CAPSQ9ZVx7K_2_ApjG_sP2uopRLocaasgpJQNUNeh6NmSVAGiyw@mail.gmail.com> <24674_1355758104_50CF3A18_24674_468_1_88CAD1D4E8773F42858B58CAA28272A00E2A2C@PEXCVZYM12.corporate.adroot.infra.ftgroup> <CAPSQ9ZU-9fZRGksgut-UiRmbVfTi9WR9Orn6cockYqgjVjRF7Q@mail.gmail.com> <OF0E1F39E5.19A27B85-ON85257AE5.005E7CF8-85257AE5.005EF464@csc.com> <EDC0A1AE77C57744B664A310A0B23AE20D7456E216@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <CAPSQ9ZV10ShtsZwzA10RfBmjyzmLy7TpxomJW+GfPr08qh5z2g@mail.gmail.com>
In-Reply-To: <CAPSQ9ZV10ShtsZwzA10RfBmjyzmLy7TpxomJW+GfPr08qh5z2g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: "sip-overload@ietf.org" <sip-overload@ietf.org>, Arata Koike <koike.arata@lab.ntt.co.jp>, "NOEL, ERIC \(ERIC C\)" <ecnoel@att.com>, Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [sip-overload] Local Policy Re: I-D Action: draft-ietf-soc-load-control-event-package-05.txt
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-overload>, <mailto:sip-overload-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-overload>
List-Post: <mailto:sip-overload@ietf.org>
List-Help: <mailto:sip-overload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-overload>, <mailto:sip-overload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 16:42:07 -0000

On 01/03/2013 07:34 AM, Charles Shen wrote:
> Sounds good, I can update the wording in the event package draft, if
> Vijay is OK with the other one.

I just want to make sure we are all agreeing to the same thing.

It seems to me that the question of using SHOULD versus MUST is being
decided slightly in favour of a MUST.  Martin and Bruno prefer a MUST,
Janet is okay with, although her original text used a SHOULD; and Keith
could go either way.

Is the consensus, then, that the text on honoring local policy contains
MUST?  If so, the text to be inserted would be the following:

   A SIP client MUST honor any local policy for prioritizing SIP
   requests such as policies based on message type, e.g., INVITEs vs.
   requests associated with existing sessions.

   A SIP client MUST honor any local policy for prioritizing SIP
   requests based on the content of the Resource-Priority header (RPH,
   RFC4412 [RFC4412]).  Specific (namespace.value) RPH contents may
   indicate high priority requests that should be preserved as much as
   possible during overload.  The RPH contents can also indicate a
   low-priority request that is eligible to be dropped during times of
   overload.

   A SIP client MUST honor any local policy for prioritizing SIP
   requests relating to emergency calls, as identified by the SOS
   URN [RFC5031] indicating an emergency request.

Yes?

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

v2.8.7 | Report a Bug | By Email