Re: [sip-overload] Gen-ART review for draft-ietf-soc-load-control-event-package-10.txt

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Mon, 25 November 2013 09:32 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: sip-overload@ietfa.amsl.com
Delivered-To: sip-overload@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95C981ACCF0; Mon, 25 Nov 2013 01:32:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YpWTqUVEy643; Mon, 25 Nov 2013 01:32:04 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id E14BA1ACCDF; Mon, 25 Nov 2013 01:32:03 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoTAFMYk1LGmAcV/2dsb2JhbABZDoI1IyE4U4J5pDQDBIwkiEwYgQ0WdIIlAQEBAQMSEQpMEAIBCA0BAwQBAQsDGgMCAgIfERQJCAIEDgUIGodNAw8BDKF+ikCIMA2IDReMeIFeFhsGAYJrNYETA5QyBYFxAYMbhTuFb4U4gmk/gio
X-IronPort-AV: E=Sophos; i="4.93,766,1378872000"; d="scan'208,217"; a="38302388"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by co300216-co-outbound.net.avaya.com with ESMTP; 25 Nov 2013 04:32:03 -0500
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 25 Nov 2013 04:25:22 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.03.0146.000; Mon, 25 Nov 2013 10:32:01 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Charles Shen <qs2005@columbia.edu>
Thread-Topic: Gen-ART review for draft-ietf-soc-load-control-event-package-10.txt
Thread-Index: AQHO6b2OuZoEnxGmj0muX2XfgTK4spo1rjqw
Date: Mon, 25 Nov 2013 09:32:01 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA129486F7@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA12941662@AZ-FFEXMB04.global.avaya.com> <CAPSQ9ZXkEBd5JJu-mt08+StkPY5R4KfYwsqcWS35AFSLLxaFXw@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA12947F8F@AZ-FFEXMB04.global.avaya.com> <CAPSQ9ZVmoCc3xr_Ui=Wrua7D8K0yp3XGWMHq1KN1u+-CEWQH1Q@mail.gmail.com>
In-Reply-To: <CAPSQ9ZVmoCc3xr_Ui=Wrua7D8K0yp3XGWMHq1KN1u+-CEWQH1Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.45]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA129486F7AZFFEXMB04globa_"
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 25 Nov 2013 02:44:29 -0800
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>, "draft-ietf-soc-load-control-event-package.all@tools.ietf.org" <draft-ietf-soc-load-control-event-package.all@tools.ietf.org>
Subject: Re: [sip-overload] Gen-ART review for draft-ietf-soc-load-control-event-package-10.txt
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.15
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, 25 Nov 2013 09:32:06 -0000

Hi Charles,

No, this is not a strong comment. Actually all my comments were listed as ‘minor’ thus non-blocking vs. a document I appreciate as of good quality. Thank you for the dialog and for considering my comments.

Regards,

Dan





From: charles.newyork@gmail.com [mailto:charles.newyork@gmail.com] On Behalf Of Charles Shen
Sent: Monday, November 25, 2013 11:06 AM
To: Romascanu, Dan (Dan)
Cc: gen-art@ietf.org; draft-ietf-soc-load-control-event-package.all@tools.ietf.org; sip-overload@ietf.org
Subject: Re: Gen-ART review for draft-ietf-soc-load-control-event-package-10.txt

Hi Dan,

On Mon, Nov 25, 2013 at 1:09 AM, Romascanu, Dan (Dan) <dromasca@avaya.com<mailto:dromasca@avaya.com>> wrote:


Also, in the same list of requirements I miss an explicit requirement on persistency.


This part I am not sure if I understand clearly, could you please elaborate a bit?

 [[DR]] In section 5.3, second paragraph there are a couple of references to the persistency of subscriptions of neighboring SIP entities and periodic refresh. Should not this be mentioned explicitly in the list in Section 4?

I see what you mean. In fact I tend to think of this as one of those micro-aspects that have been covered by existing macro-clauses. Specifically, as Section 5.3 says:


 Key to this is the fact that following initial

   subscription, the notifier sends a notification without a body if no

   load filtering policy is defined (Section 6.7<http://tools.ietf.org/html/draft-ietf-soc-load-control-event-package-11#section-6.7>)7>), and that the

   subscription needs to be refreshed periodically to make it

   persistent, as described in Section 4.1<http://tools.ietf.org/html/draft-ietf-soc-load-control-event-package-11#section-4.1> and Section 4.2 of [RFC6665]<http://tools.ietf.org/html/rfc6665#section-4.2>.2>.

The behavior of notifier sending a notification following initial subscription is mandated in Section 6.7 of this document. And the behavior of periodic refresh is specified in Section 4.1 and Section 4.2 of RFC 6665.

Both this document and RFC 6665 have already been explicitly listed in Section 4 of this document. So they seem to have covered the persistency issue.

That said, I am open to add another explicit clause for this aspect if you really feel strongly about it. Please let me know. Thanks again!

Charles