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

Volker Hilt <volker.hilt@bell-labs.com> Mon, 21 January 2013 14:23 UTC

Return-Path: <volker.hilt@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 BE65421F881D for <sip-overload@ietfa.amsl.com>; Mon, 21 Jan 2013 06:23:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level:
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
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 XqzrlulCRPgW for <sip-overload@ietfa.amsl.com>; Mon, 21 Jan 2013 06:23:42 -0800 (PST)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id 145FF21F8815 for <sip-overload@ietf.org>; Mon, 21 Jan 2013 06:23:41 -0800 (PST)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r0LDx4xa031475 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <sip-overload@ietf.org>; Mon, 21 Jan 2013 15:23:34 +0100
Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (135.5.2.36) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (135.120.45.63) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 21 Jan 2013 15:22:42 +0100
Received: from [149.204.61.163] (135.5.27.16) by US70TWXCHHUB04.zam.alcatel-lucent.com (135.5.2.36) with Microsoft SMTP Server (TLS) id 14.2.247.3; Mon, 21 Jan 2013 09:22:36 -0500
Message-ID: <50FD4F2A.7000609@bell-labs.com>
Date: Mon, 21 Jan 2013 15:22:34 +0100
From: Volker Hilt <volker.hilt@bell-labs.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: <sip-overload@ietf.org>
References: <20121022163217.13864.84970.idtracker@ietfa.amsl.com> <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> <50E5B529.2090105@bell-labs.com> <50F01C82.9010406@bell-labs.com> <50F4146E.1080308@bell-labs.com> <50F422E4.8010809@bell-labs.com> <OF5077D3D0.BC87BCA4-ON85257AF3.00582679-85257AF3.00584E45@csc.com> <50F42D9F.1080002@bell-labs.com> <CAPSQ9ZWfu6J+BZZ9BgTTk+f5-dH1BHhkUxEk8ZLcRohvFxMZUA@mail.gmail.com> <OF36DB58E7.14AA60B0-ON85257AF3.005BDC42-85257AF3.005C7511@csc.com> <CAPSQ9ZW3+SX9xitSbgZt+N1=tCoMCqO8jdO4CknHTEZ=7HzGUA@mail.gmail.com> <EDC0A1AE77C57744B664A310A0B23AE20D745EF327@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <50F44BC2.2080703@bell-labs.com> <50FD4EF1.7090702@ericsson.com>
In-Reply-To: <50FD4EF1.7090702@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [135.5.27.16]
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
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: Mon, 21 Jan 2013 14:23:42 -0000

Fine with me.

Volker

On 21.01.2013 15:21, Salvatore Loreto wrote:
> we have been discussing this issue (i.e. SHOULD vs MUST) over the last
> couple of weeks or even more.
> THE result is that an explanatory text is the key thing to have either way
> because of the different views on what a policy can and cannot be.
>
> having said that,
> my reading is that there is a large preference to use  SHOULD
> with the explanatory text proposed by Vijay below
>
> Salvatore
>
> On 1/14/13 8:17 PM, Vijay K. Gurbani wrote:
>
> [snip]
>>
>>    It is expected that a SIP client will follow local policy as long as
>>    the results in reduction of traffic is consistent with the SIP
>>    overload algorithm in effect at that node.  Accordingly, the
>>    normative behaviour in the next three paragraphs should be
>>    interpreted with the understanding that the SIP client will aim to
>>    preserve local policy to the fullest extent possible.
>>
>> And then we go down the three SHOULD paragraphs.
>>
>> I believe that suggesting specific text will help close this gap more
>> expeditiously.
>>
>> Is the above something that we can go with?
>>
>> Thanks,
>>
>> - vijay
>
>
> _______________________________________________
> sip-overload mailing list
> sip-overload@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload