Re: [sip-overload] rate-control and event-package drafts and normative references

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Tue, 17 December 2013 23:55 UTC

Return-Path: <keith.drage@alcatel-lucent.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 B60881ADF43 for <sip-overload@ietfa.amsl.com>; Tue, 17 Dec 2013 15:55:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] 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 X-fw8BDz_RNc for <sip-overload@ietfa.amsl.com>; Tue, 17 Dec 2013 15:55:08 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id DD5B51AD9AC for <sip-overload@ietf.org>; Tue, 17 Dec 2013 15:55:07 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id rBHNsv3v004168 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 17 Dec 2013 17:54:58 -0600 (CST)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id rBHNsvxe015986 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 18 Dec 2013 00:54:57 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.203]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Wed, 18 Dec 2013 00:54:57 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "Gurbani, Vijay K (Vijay)" <vijay.gurbani@alcatel-lucent.com>, "Charles Shen" <charles@cs.columbia.edu>
Thread-Topic: [sip-overload] rate-control and event-package drafts and normative references
Thread-Index: AQHO+z2kz3JP4Go7oES3zimxmxyCF5pYdP2AgACaLVA=
Date: Tue, 17 Dec 2013 23:54:56 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B0FA8D2@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <52B058CC.1050508@bell-labs.com> <CAPSQ9ZXeR59u=GEoQBiVW1habRb7xVchDwd8obNxjedJHvsTXQ@mail.gmail.com> <52B07019.80501@bell-labs.com>
In-Reply-To: <52B07019.80501@bell-labs.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: "sip-overload@ietf.org" <sip-overload@ietf.org>
Subject: Re: [sip-overload] rate-control and event-package drafts and normative references
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: Tue, 17 Dec 2013 23:55:10 -0000

I was about to respond saying pretty much what you have said below.

So treat this as a +1.

Keith 

> -----Original Message-----
> From: sip-overload [mailto:sip-overload-bounces@ietf.org] On 
> Behalf Of Vijay K. Gurbani
> Sent: 17 December 2013 15:39
> To: Charles Shen
> Cc: sip-overload@ietf.org
> Subject: Re: [sip-overload] rate-control and event-package 
> drafts and normative references
> 
> On 12/17/2013 09:31 AM, Charles Shen wrote:
> > Hi Vijay, I will update it in the next version. Thanks!
> 
> Charles: I was looking at event-package draft and I think 
> that perhaps it is not necessary for you to upgrade the 
> reference to normative.
> 
> event-package essentially fleshes out a rfc6665 event 
> package; as such it does not ask the actors to use overload 
> control parameters defined in the overload-control draft.
> 
> So it looks like an informative references from your document 
> suffices.
> 
> The rate-control document will most definitely need to move 
> the reference to normative since it uses the overload control 
> parameters defined in the overload-control draft.
> 
> Cheers,
> 
> - 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/  | Calendar: 
> http://goo.gl/x3Ogq _______________________________________________
> sip-overload mailing list
> sip-overload@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload
>