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

Charles Shen <charles@cs.columbia.edu> Tue, 29 January 2013 15:29 UTC

Return-Path: <charles.newyork@gmail.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 7F30821F892F for <sip-overload@ietfa.amsl.com>; Tue, 29 Jan 2013 07:29:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 P1-3um6bdYK9 for <sip-overload@ietfa.amsl.com>; Tue, 29 Jan 2013 07:29:41 -0800 (PST)
Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by ietfa.amsl.com (Postfix) with ESMTP id C152C21F8923 for <sip-overload@ietf.org>; Tue, 29 Jan 2013 07:29:41 -0800 (PST)
Received: by mail-oa0-f54.google.com with SMTP id n9so554112oag.13 for <sip-overload@ietf.org>; Tue, 29 Jan 2013 07:29:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=dMgg2XDKn2vlrkWXL8VdKjkw7sokMQ4E4nk6ecApgLg=; b=dMWRX6uGCKna8JqqVyBfR9WbZ4deO/U0l9SaT5O4L/Q2DJsZ3oF2vNFLyALx69Wd/9 UoRz2URD5tbAREVqZ175ToHJ9cqF7rH4ydU+ZdJD18+NjRxP1kK/Toceg31VHGepQ7yT prKr+H2Rn6H1DHb6/IBmHf9U9ZIVgthqRJHOgsv3lIri2KFY1h3tIX3ZHK4iIny71kZA 2iCVrPQ2EzOEqc/d1fKuSRC8ptCJ7WwFy4g7kUuf8QfeoryiFlqG2l5Q9NF1US+pkyzU fQCtSYv+2KvHMhgfSW8dHFKHza4SCc41hVlJoqV9m/KnCJOM88V24kKDvghuzm4U/YN+ Z/LA==
X-Received: by 10.60.31.6 with SMTP id w6mr1016303oeh.65.1359473381204; Tue, 29 Jan 2013 07:29:41 -0800 (PST)
MIME-Version: 1.0
Sender: charles.newyork@gmail.com
Received: by 10.182.151.82 with HTTP; Tue, 29 Jan 2013 07:29:21 -0800 (PST)
In-Reply-To: <510682C5.1090800@ericsson.com>
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> <510682C5.1090800@ericsson.com>
From: Charles Shen <charles@cs.columbia.edu>
Date: Tue, 29 Jan 2013 10:29:21 -0500
X-Google-Sender-Auth: YtmWJBqycmQ702mTCA9ZtDwhJDE
Message-ID: <CAPSQ9ZVEu1ArW6z2yhCppqb87gmTkU7CvNhEtN9gaFsVHVwvAw@mail.gmail.com>
To: vkg@bell-labs.com
Content-Type: text/plain; charset=UTF-8
Cc: sip-overload@ietf.org
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: Tue, 29 Jan 2013 15:29:42 -0000

Dear Vijay, I just want to make sure I include the exact texts that
have been finally agreed on.  Could you please post the complete
version of the final texts on this issue again, and I will update the
event package draft right away.

Thanks!

Charles

On Mon, Jan 28, 2013 at 8:53 AM, Salvatore Loreto
<salvatore.loreto@ericsson.com> wrote:
>
> as co-chair I declare formal consensus on the SHOULD option
>
> the authors of the draft event-package and overload-control are invited to
> update their draft
> to reflect the decision
>
> best regards
> Salvatore
>
>
> On 1/21/13 4:21 PM, 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
>>
>>
>
>
> --
> Salvatore Loreto, PhD
> www.sloreto.com
>
> _______________________________________________
> sip-overload mailing list
> sip-overload@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload