From jari.arkko@piuha.net Mon Dec 2 21:50:27 2013 Return-Path: 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 A4AE21AE051; Mon, 2 Dec 2013 21:50:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 FGDdkfgdS1ps; Mon, 2 Dec 2013 21:50:25 -0800 (PST) Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id CCCFE1AE048; Mon, 2 Dec 2013 21:50:24 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 2C57A2CC61; Tue, 3 Dec 2013 07:50:21 +0200 (EET) X-Virus-Scanned: amavisd-new at piuha.net Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jIt7J1T3ICaX; Tue, 3 Dec 2013 07:50:19 +0200 (EET) Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id D51FB2CC48; Tue, 3 Dec 2013 07:50:19 +0200 (EET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Jari Arkko In-Reply-To: <1385372383632.075e6c61@Nodemailer> Date: Tue, 3 Dec 2013 07:50:19 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <12A2D7CB-96AE-424B-B6C9-B89DAC068E90@piuha.net> References: <9904FB1B0159DA42B0B887B7FA8119CA129486F7@AZ-FFEXMB04.global.avaya.com> <1385372383632.075e6c61@Nodemailer> To: charles newyork X-Mailer: Apple Mail (2.1510) Cc: "Dan \(Dan\) Romascanu" , gen-art@ietf.org, sip-overload@ietf.org, draft-ietf-soc-load-control-event-package.all@tools.ietf.org Subject: Re: [sip-overload] [Gen-art] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Dec 2013 05:50:27 -0000 Thank you Dan for the review and Charles for addressing the concerns. I = have placed a no-obj position for this document on this week's IESG = telechat. Jari On Nov 25, 2013, at 11:39 AM, charles newyork = wrote: > That's great, I will keep it as in the current 11 version then. Again = thank you so much for the careful review! >=20 >=20 >=20 > Charles=20 >=20 > =E2=80=94 > Sent from Mailbox for iPhone >=20 > On =E5=91=A8=E4=B8=80, 11=E6=9C=88 25, 2013 at 5:32 =E4=B8=8B=E5=8D=88, = Romascanu, Dan (Dan) > = wrote: > Hi Charles, >=20 >=20 >=20 >=20 > =20 >=20 > No, this is not a strong comment. Actually all my comments were listed = as =E2=80=98minor=E2=80=99 thus non-blocking vs. a document I appreciate = as of good quality. Thank you for the dialog and for considering my = comments. >=20 >=20 >=20 >=20 > =20 >=20 > Regards, >=20 >=20 >=20 >=20 > =20 >=20 > Dan >=20 >=20 >=20 >=20 > =20 >=20 >=20 > =20 >=20 >=20 > =20 >=20 >=20 > =20 >=20 >=20 > =20 >=20 > 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 >=20 >=20 >=20 >=20 > =20 > Hi Dan, >=20 >=20 >=20 > =20 > On Mon, Nov 25, 2013 at 1:09 AM, Romascanu, Dan (Dan) = wrote: >=20 >=20 >=20 >=20 > Also, in the same list of requirements I miss an explicit requirement = on persistency. >=20 >=20 > =20 >=20 > =20 >=20 > This part I am not sure if I understand clearly, could you please = elaborate a bit?=20 >=20 >=20 > =20 >=20 > [[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? >=20 >=20 >=20 > =20 > 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: >=20 >=20 >=20 > =20 > Key to this is the fact that following initial >=20 > subscription, the notifier sends a notification without a body if = no >=20 > load filtering policy is defined (Section 6.7), and that the >=20 > subscription needs to be refreshed periodically to make it >=20 > persistent, as described in Section 4.1 and Section 4.2 of = [RFC6665]. >=20 > =20 >=20 > 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.=20 >=20 >=20 >=20 > =20 > 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. >=20 >=20 >=20 > =20 > 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! >=20 >=20 >=20 > =20 > Charles=20 >=20 >=20 >=20 > =20 >=20 > =20 >=20 > =20 > _______________________________________________ > Gen-art mailing list > Gen-art@ietf.org > https://www.ietf.org/mailman/listinfo/gen-art From internet-drafts@ietf.org Wed Dec 4 08:47:20 2013 Return-Path: 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 E570D1ADFB4; Wed, 4 Dec 2013 08:47:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 XB_nrtC9OGEa; Wed, 4 Dec 2013 08:47:17 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D94F51AE157; Wed, 4 Dec 2013 08:47:17 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131204164717.14271.22598.idtracker@ietfa.amsl.com> Date: Wed, 04 Dec 2013 08:47:17 -0800 Cc: sip-overload@ietf.org Subject: [sip-overload] I-D Action: draft-ietf-soc-load-control-event-package-12.txt X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.15 List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Dec 2013 16:47:21 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the SIP Overload Control Working Group of the= IETF. Title : A Session Initiation Protocol (SIP) Load Control Event P= ackage Author(s) : Charles Shen Henning Schulzrinne Arata Koike Filename : draft-ietf-soc-load-control-event-package-12.txt Pages : 43 Date : 2013-12-04 Abstract: We define a load control event package for the Session Initiation Protocol (SIP). It allows SIP entities to distribute load filtering policies to other SIP entities in the network. The load filtering policies contain rules to throttle calls based on their source or destination domain, telephone number prefix or for a specific user. The mechanism helps to prevent signaling overload and complements feedback-based SIP overload control efforts. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-soc-load-control-event-package There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-soc-load-control-event-package-12 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-soc-load-control-event-packag= e-12 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From volker.hilt@bell-labs.com Thu Dec 5 13:18:31 2013 Return-Path: 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 A91031AE180 for ; Thu, 5 Dec 2013 13:18:31 -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 6pDSN7zD5NNy for ; Thu, 5 Dec 2013 13:18:26 -0800 (PST) Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 52D0C1AE149 for ; Thu, 5 Dec 2013 13:18:26 -0800 (PST) Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id rB5LIH3K020962 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 5 Dec 2013 15:18:18 -0600 (CST) Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id rB5LIGc5020959 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Thu, 5 Dec 2013 22:18:16 +0100 Received: from [135.244.176.82] (135.239.27.38) by FR711WXCHHUB02.zeu.alcatel-lucent.com (135.239.2.112) with Microsoft SMTP Server (TLS) id 14.2.247.3; Thu, 5 Dec 2013 22:18:16 +0100 Message-ID: <52A0ED91.2030804@bell-labs.com> Date: Thu, 5 Dec 2013 22:18:09 +0100 From: Volker Hilt User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: References: <015a01ced161$be570550$3b050ff0$@com> In-Reply-To: <015a01ced161$be570550$3b050ff0$@com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [135.239.27.38] X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35 Subject: Re: [sip-overload] Request for discussion of end2end SIP Overload Control X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 21:18:31 -0000 Jinzhu Wang, the WG is currently finishing up work on the last remaining charter items. Unfortunately, we won't be able to take on new drafts. Thanks, Volker On 25.10.2013 11:08, wangjinzhu wrote: > Dear all > Request for discussion of a proposal to end2end SIP Overload Control (http://datatracker.ietf.org/doc/draft-wang-appsawg-end2end-overload-control). Since I cannot find the SOC session in this IETF meeting, I submitted the draft to the appsawg. The submission cannot be changed as the system is closed. I will re-submit the draft to the Soc wg or Dispatch wg when the system is re-open. > Any comments or suggestions will be greatly appreciated. > > Best Regards > Jinzhu Wang > China Mobile > > > -----Original Mail----- > 发件人: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] > 发送时间: 2013年10月19日 22:10 > 收件人: Yu Qing; Deng Lingli; wangjinzhu; Qing Yu; Jinzhu Wang; Lingli Deng > 主题: New Version Notification for draft-wang-appsawg-end2end-overload-control-00.txt > > > A new version of I-D, draft-wang-appsawg-end2end-overload-control-00.txt > has been successfully submitted by Jinzhu Wang and posted to the IETF repository. > > Filename: draft-wang-appsawg-end2end-overload-control > Revision: 00 > Title: End-to-end Session Initiation Protocol (SIP) overload control > Creation date: 2013-10-18 > Group: Individual Submission > Number of pages: 6 > URL: http://www.ietf.org/internet-drafts/draft-wang-appsawg-end2end-overload-control-00.txt > Status: http://datatracker.ietf.org/doc/draft-wang-appsawg-end2end-overload-control > Htmlized: http://tools.ietf.org/html/draft-wang-appsawg-end2end-overload-control-00 > > > Abstract: > This draft proposes end-to-end Session Initiation Protocol (SIP) > overload control, in which the edge servers of the SIP network > throttle the arriving calls in order to control overload for the SIP > network. Compared to the local and hop-by-hop SIP overload control, > the end-to-end SIP overload control can achieve best performance. > > > > > Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat > > > > > _______________________________________________ > sip-overload mailing list > sip-overload@ietf.org > https://www.ietf.org/mailman/listinfo/sip-overload > From internet-drafts@ietf.org Mon Dec 9 11:43:49 2013 Return-Path: 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 E518E1AE500; Mon, 9 Dec 2013 11:43:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 O9e43G46hAJr; Mon, 9 Dec 2013 11:43:48 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A53E91AE3F3; Mon, 9 Dec 2013 11:43:48 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131209194348.32358.55155.idtracker@ietfa.amsl.com> Date: Mon, 09 Dec 2013 11:43:48 -0800 Cc: sip-overload@ietf.org Subject: [sip-overload] I-D Action: draft-ietf-soc-overload-control-14.txt X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.15 List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Dec 2013 19:43:50 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the SIP Overload Control Working Group of the= IETF. Title : Session Initiation Protocol (SIP) Overload Control Author(s) : Vijay K. Gurbani Volker Hilt Henning Schulzrinne Filename : draft-ietf-soc-overload-control-14.txt Pages : 37 Date : 2013-12-09 Abstract: Overload occurs in Session Initiation Protocol (SIP) networks when SIP servers have insufficient resources to handle all SIP messages they receive. Even though the SIP protocol provides a limited overload control mechanism through its 503 (Service Unavailable) response code, SIP servers are still vulnerable to overload. This document defines the behaviour of SIP servers involved in overload control, and in addition, it specifies a loss-based overload scheme for SIP. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-soc-overload-control There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-soc-overload-control-14 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-soc-overload-control-14 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From vkg@bell-labs.com Mon Dec 9 11:56:26 2013 Return-Path: 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 1BE311AE50B for ; Mon, 9 Dec 2013 11:56:26 -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 7BovVPFKwUjR for ; Mon, 9 Dec 2013 11:56:23 -0800 (PST) Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 8C9761AE4DA for ; Mon, 9 Dec 2013 11:56:23 -0800 (PST) Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id rB9JuIWx005190 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 9 Dec 2013 13:56:18 -0600 (CST) Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id rB9JuH8L003375 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 9 Dec 2013 13:56:18 -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 rB9JuHgX023655 for ; Mon, 9 Dec 2013 13:56:17 -0600 (CST) Message-ID: <52A62070.1090200@bell-labs.com> Date: Mon, 09 Dec 2013 13:56:32 -0600 From: "Vijay K. Gurbani" Organization: Bell Laboratories, Alcatel-Lucent User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: "sip-overload@ietf.org" Content-Type: text/plain; charset=ISO-8859-1; 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.9 Subject: [sip-overload] draft-ietf-soc-overload-control-14 X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Dec 2013 19:56:26 -0000 Folks: I have submitted draft-ietf-soc-overload-control. The changes in this version resulted from the AD review; the thread can be followed from [1,2]. The changes were editorial with a slightly expanded Security Considerations section. The draft is ready to be progressed ahead. Thanks to all WG contributors. [1] http://www.ietf.org/mail-archive/web/sip-overload/current/msg01013.html [2] http://www.ietf.org/mail-archive/web/sip-overload/current/msg01014.html 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 From iesg-secretary@ietf.org Mon Dec 9 12:24:58 2013 Return-Path: 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 EA0AD1AE07A; Mon, 9 Dec 2013 12:24:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 YTL9TT1DFaWo; Mon, 9 Dec 2013 12:24:54 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D0CAA1AE2B4; Mon, 9 Dec 2013 12:24:54 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Sender: Message-ID: <20131209202454.23223.88002.idtracker@ietfa.amsl.com> Date: Mon, 09 Dec 2013 12:24:54 -0800 Cc: sip-overload@ietf.org Subject: [sip-overload] Last Call: (Session Initiation Protocol (SIP) Overload Control) to Internet Standard X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.15 Reply-To: ietf@ietf.org List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Dec 2013 20:24:58 -0000 The IESG has received a request from the SIP Overload Control WG (soc) to consider the following document: - 'Session Initiation Protocol (SIP) Overload Control' as Internet Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2013-12-23. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract Overload occurs in Session Initiation Protocol (SIP) networks when SIP servers have insufficient resources to handle all SIP messages they receive. Even though the SIP protocol provides a limited overload control mechanism through its 503 (Service Unavailable) response code, SIP servers are still vulnerable to overload. This document defines the behaviour of SIP servers involved in overload control, and in addition, it specifies a loss-based overload scheme for SIP. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-soc-overload-control/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-soc-overload-control/ballot/ The following IPR Declarations may be related to this I-D: http://datatracker.ietf.org/ipr/1364/ From volker.hilt@bell-labs.com Mon Dec 9 13:39:37 2013 Return-Path: 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 259D61AE103 for ; Mon, 9 Dec 2013 13:39:37 -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 lJSdirhMW3hj for ; Mon, 9 Dec 2013 13:39:35 -0800 (PST) Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 0AE151AE0B1 for ; Mon, 9 Dec 2013 13:39:34 -0800 (PST) Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id rB9LdQwd004580 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 9 Dec 2013 15:39:28 -0600 (CST) Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id rB9LdQCH004646 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Mon, 9 Dec 2013 22:39:26 +0100 Received: from [135.244.176.63] (135.239.27.39) by FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) with Microsoft SMTP Server (TLS) id 14.2.247.3; Mon, 9 Dec 2013 22:39:26 +0100 Message-ID: <52A6388A.9090801@bell-labs.com> Date: Mon, 9 Dec 2013 22:39:22 +0100 From: Volker Hilt User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: "sip-overload@ietf.org" Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [135.239.27.39] X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37 Subject: [sip-overload] WGLC: draft-ietf-soc-overload-rate-control X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Dec 2013 21:39:37 -0000 All, a new version of draft draft-ietf-soc-overload-rate-control is available that addresses comments received during and after the last WGLC for this document. The new version is at: https://datatracker.ietf.org/doc/draft-ietf-soc-overload-rate-control/ A diff between pre-WGLC and current version is at: http://tools.ietf.org/rfcdiff?url1=draft-ietf-soc-overload-rate-control-04&url2=draft-ietf-soc-overload-rate-control-06.txt We are issuing another WGLC for the updated version of this draft that will end on Dec 20, 2013. Please review the updated draft and send your comments to the mailing list. If you agree with the changes, please comment also. Thanks, Volker From internet-drafts@ietf.org Sat Dec 14 00:25:43 2013 Return-Path: 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 9AF491AE511; Sat, 14 Dec 2013 00:25:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 Uw2aVjSPzOu9; Sat, 14 Dec 2013 00:25:30 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C0BF1AE17C; Sat, 14 Dec 2013 00:25:30 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131214082530.6124.19973.idtracker@ietfa.amsl.com> Date: Sat, 14 Dec 2013 00:25:30 -0800 Cc: sip-overload@ietf.org Subject: [sip-overload] I-D Action: draft-ietf-soc-load-control-event-package-13.txt X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.15 List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Dec 2013 08:25:43 -0000 X-List-Received-Date: Sat, 14 Dec 2013 08:25:43 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the SIP Overload Control Working Group of the= IETF. Title : A Session Initiation Protocol (SIP) Load Control Event P= ackage Author(s) : Charles Shen Henning Schulzrinne Arata Koike Filename : draft-ietf-soc-load-control-event-package-13.txt Pages : 42 Date : 2013-12-14 Abstract: This specification defines a load control event package for the Session Initiation Protocol (SIP). It allows SIP entities to distribute load filtering policies to other SIP entities in the network. The load filtering policies contain rules to throttle calls based on their source or destination domain, telephone number prefix or for a specific user. The mechanism helps to prevent signaling overload and complements feedback-based SIP overload control efforts. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-soc-load-control-event-package There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-soc-load-control-event-package-13 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-soc-load-control-event-packag= e-13 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From vkg@bell-labs.com Tue Dec 17 05:59:30 2013 Return-Path: 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 8241E1AE1F5 for ; Tue, 17 Dec 2013 05:59:30 -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 SLyMKxZq54Yg for ; Tue, 17 Dec 2013 05:59:29 -0800 (PST) Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 115601ADFAB for ; Tue, 17 Dec 2013 05:59:28 -0800 (PST) Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id rBHDxJo1020535 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 17 Dec 2013 07:59:20 -0600 (CST) Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id rBHDxJJT005496 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 17 Dec 2013 07:59:19 -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 rBHDxJqH004171; Tue, 17 Dec 2013 07:59:19 -0600 (CST) Message-ID: <52B058CC.1050508@bell-labs.com> Date: Tue, 17 Dec 2013 07:59:40 -0600 From: "Vijay K. Gurbani" Organization: Bell Laboratories, Alcatel-Lucent User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Charles Shen , "NOEL, ERIC C (ERIC C)" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39 X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12 Cc: "sip-overload@ietf.org" Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Dec 2013 13:59:30 -0000 Charles, Eric: The Gen-ART review of draft-ietf-soc-overload-control triggered me to check the references of your drafts, especially whether the reference to draft-ietf-soc-overload-control is normative or informative in your drafts. It appears that both the drafts list draft-ietf-soc-overload-control as an informative reference. I believe that this should be changed to a normative reference. The distinction between normative and informative reference is captured in http://www.rfc-editor.org/policy.html#policy.refs From this reading, it appears reasonable that someone wanting to implement either rate-control or event-package will need to read overload-control first. You can ask the chairs for guidance as well, and assuming that you do make the change, you can easily do so before IETF last call or during Auth-48. 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/ | Calendar: http://goo.gl/x3Ogq From charles.newyork@gmail.com Tue Dec 17 07:31:39 2013 Return-Path: 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 6A5FD1AE006 for ; Tue, 17 Dec 2013 07:31:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.277 X-Spam-Level: X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no 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 JvieNwHbxDZB for ; Tue, 17 Dec 2013 07:31:37 -0800 (PST) Received: from mail-oa0-x22a.google.com (mail-oa0-x22a.google.com [IPv6:2607:f8b0:4003:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 06AF61AE197 for ; Tue, 17 Dec 2013 07:31:35 -0800 (PST) Received: by mail-oa0-f42.google.com with SMTP id i4so6796741oah.1 for ; Tue, 17 Dec 2013 07:31:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=1z2ZbVJtxdt/0Ap+X2xnT3kOGau6aBd98Tv/S7fqDQs=; b=ZourFKslzgOK6kX+uieESMYVAgBxopUepv04Lqk7ROlNKlwttmazTIPMqEBF2Q85ez nesITblodByFJ7Fe9roi6Ipng3fhr/0t/++vbiJ+y6G7EjHqRi7JQTnikGVF1kGAnUwl 72//hpPx0QsqyLu4lC2H9EpOEGKyit31bptrmQVqGAcE+aySYpGm+vwdBxibax8ZF+6A co2hpjZ/VYFziiyoenp4PaH8R3feHF7pgh0Qr7etIUcNL2rj+hA5wYfDSW2QCV+GHH6g qnYWlIetNdzBEuD5g2ID+1SryiCn75XMkxrXeK5Mzu100xh3EfMIu4n5H2yTaSAeQitV ORWA== X-Received: by 10.182.92.231 with SMTP id cp7mr1816768obb.82.1387294294818; Tue, 17 Dec 2013 07:31:34 -0800 (PST) MIME-Version: 1.0 Sender: charles.newyork@gmail.com Received: by 10.182.27.9 with HTTP; Tue, 17 Dec 2013 07:31:14 -0800 (PST) In-Reply-To: <52B058CC.1050508@bell-labs.com> References: <52B058CC.1050508@bell-labs.com> From: Charles Shen Date: Tue, 17 Dec 2013 23:31:14 +0800 X-Google-Sender-Auth: oNhQhowJmkxFfdy0l7AqEaWz8UQ Message-ID: To: "Vijay K. Gurbani" Content-Type: multipart/alternative; boundary=001a11c302cca4449e04edbc9f4b Cc: "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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Dec 2013 15:31:39 -0000 --001a11c302cca4449e04edbc9f4b Content-Type: text/plain; charset=UTF-8 Hi Vijay, I will update it in the next version. Thanks! Charles On Tue, Dec 17, 2013 at 9:59 PM, Vijay K. Gurbani wrote: > Charles, Eric: The Gen-ART review of draft-ietf-soc-overload-control > triggered me to check the references of your drafts, especially whether > the reference to draft-ietf-soc-overload-control is normative or > informative in your drafts. > > It appears that both the drafts list draft-ietf-soc-overload-control as > an informative reference. > > I believe that this should be changed to a normative reference. > > The distinction between normative and informative reference is > captured in http://www.rfc-editor.org/policy.html#policy.refs > From this reading, it appears reasonable that someone wanting to > implement either rate-control or event-package will need to > read overload-control first. > > You can ask the chairs for guidance as well, and assuming that you > do make the change, you can easily do so before IETF last call or > during Auth-48. > > 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/ | Calendar: http://goo.gl/x3Ogq > --001a11c302cca4449e04edbc9f4b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Vijay, I will update it in the next version. Thanks!
Charles


On Tue, Dec 17, 2013 at 9:59 PM, Vijay K. Gurbani <= vkg@bell-labs.com> wrote:
Charles, Eric: The Gen-ART review of draft-i= etf-soc-overload-control
triggered me to check the references of your drafts, especially whether
the reference to draft-ietf-soc-overload-control is normative or
informative in your drafts.

It appears that both the drafts list draft-ietf-soc-overload-control= as
an informative reference.

I believe that this should be changed to a normative reference.

The distinction between normative and informative reference is
captured in http://www.rfc-editor.org/policy.html#policy.refs
>From this reading, it appears reasonable that someone wanting to
implement either rate-control or event-package will need to
read overload-control first.

You can ask the chairs for guidance as well, and assuming that you
do make the change, you can easily do so before IETF last call or
during Auth-48.

Thanks,

- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.co= m,acm.org} / vijay.gurban= i@alcatel-lucent.com
Web: http:/= /ect.bell-labs.com/who/vkg/ =C2=A0| Calendar: http://goo.gl/x3Ogq

--001a11c302cca4449e04edbc9f4b-- From vkg@bell-labs.com Tue Dec 17 07:39:04 2013 Return-Path: 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 795C41AE014 for ; Tue, 17 Dec 2013 07:39:04 -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 hlopFI6YdSQP for ; Tue, 17 Dec 2013 07:39:01 -0800 (PST) Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 8FE541ADEBA for ; Tue, 17 Dec 2013 07:39:01 -0800 (PST) Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id rBHFcj2I028810 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 17 Dec 2013 09:38:45 -0600 (CST) Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id rBHFcigI019895 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 17 Dec 2013 09:38:44 -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 rBHFchkt021165; Tue, 17 Dec 2013 09:38:44 -0600 (CST) Message-ID: <52B07019.80501@bell-labs.com> Date: Tue, 17 Dec 2013 09:39:05 -0600 From: "Vijay K. Gurbani" Organization: Bell Laboratories, Alcatel-Lucent User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Charles Shen References: <52B058CC.1050508@bell-labs.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33 X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10 Cc: "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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Dec 2013 15:39:04 -0000 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 From charles.newyork@gmail.com Tue Dec 17 07:42:38 2013 Return-Path: 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 D86FF1AE016 for ; Tue, 17 Dec 2013 07:42:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.277 X-Spam-Level: X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no 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 G6RK22kfVjp4 for ; Tue, 17 Dec 2013 07:42:37 -0800 (PST) Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id BC3D31ADEBA for ; Tue, 17 Dec 2013 07:42:24 -0800 (PST) Received: by mail-oa0-f53.google.com with SMTP id m1so6790679oag.40 for ; Tue, 17 Dec 2013 07:42:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=Yd6u7SrA2mzxXrhxK3gjScf1ok7DwJcYgT5V8qzLQp4=; b=quNs00RJBG6pwXqzHuXlKvUuXanrgzW5RQY14FpSwtvSvlyaiU+ihZu9mnvc7ZOEM7 ezKKZew4N9dKw/LznoQrJOpX+EGmYRfbFCHERgXpZS2PX2QUjXioiLQ/jBwf519X/R0w s6KfX2qYFtU1XVYQwKXHqWvhLG+3yTD/aWM3fpFCQvkR0BfBN3X940YB4V7wh43wsARE xP2k/qIzhcAACvGnb0c7iOPBuLw2sUdOU3JGZPni0g+9EvJlzTsUNLZUb2lM1TVkkNTR pWvykLc2fCF2n1Ct+k2GW7fwEbS91hknZIzSWGDYd9R3vixpZHmQBB8s923iFSbsprGB Emjg== X-Received: by 10.60.177.66 with SMTP id co2mr1065708oec.85.1387294943585; Tue, 17 Dec 2013 07:42:23 -0800 (PST) MIME-Version: 1.0 Sender: charles.newyork@gmail.com Received: by 10.182.27.9 with HTTP; Tue, 17 Dec 2013 07:42:03 -0800 (PST) In-Reply-To: <52B07019.80501@bell-labs.com> References: <52B058CC.1050508@bell-labs.com> <52B07019.80501@bell-labs.com> From: Charles Shen Date: Tue, 17 Dec 2013 23:42:03 +0800 X-Google-Sender-Auth: 4IEQ_RnmZcY8b7Qb72IFM8jGI-g Message-ID: To: "Vijay K. Gurbani" Content-Type: multipart/alternative; boundary=047d7bd6b03a4fabbf04edbcc6e3 Cc: "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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Dec 2013 15:42:39 -0000 --047d7bd6b03a4fabbf04edbcc6e3 Content-Type: text/plain; charset=UTF-8 I actually agree :) On Tue, Dec 17, 2013 at 11:39 PM, Vijay K. Gurbani wrote: > 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 > --047d7bd6b03a4fabbf04edbcc6e3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I actually agree :)


=
On Tue, Dec 17, 2013 at 11:39 PM, Vijay K. Gurba= ni <vkg@bell-labs.com> wrote:
On 12/17/2013 09:31 AM, Ch= arles 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.co= m,acm.org} / vijay.gurban= i@alcatel-lucent.com
Web: http:/= /ect.bell-labs.com/who/vkg/ =C2=A0| Calendar: http://goo.gl/x3Ogq

--047d7bd6b03a4fabbf04edbcc6e3-- From keith.drage@alcatel-lucent.com Tue Dec 17 15:55:09 2013 Return-Path: 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 ; 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 ; 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 ; 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)" To: "Gurbani, Vijay K (Vijay)" , "Charles Shen" 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> <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" 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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=20 > -----Original Message----- > From: sip-overload [mailto:sip-overload-bounces@ietf.org] On=20 > 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=20 > drafts and normative references >=20 > On 12/17/2013 09:31 AM, Charles Shen wrote: > > Hi Vijay, I will update it in the next version. Thanks! >=20 > Charles: I was looking at event-package draft and I think=20 > that perhaps it is not necessary for you to upgrade the=20 > reference to normative. >=20 > event-package essentially fleshes out a rfc6665 event=20 > package; as such it does not ask the actors to use overload=20 > control parameters defined in the overload-control draft. >=20 > So it looks like an informative references from your document=20 > suffices. >=20 > The rate-control document will most definitely need to move=20 > the reference to normative since it uses the overload control=20 > parameters defined in the overload-control draft. >=20 > Cheers, >=20 > - vijay > -- > Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960=20 > 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:=20 > http://goo.gl/x3Ogq _______________________________________________ > sip-overload mailing list > sip-overload@ietf.org > https://www.ietf.org/mailman/listinfo/sip-overload > = From charles.newyork@gmail.com Tue Dec 17 16:27:50 2013 Return-Path: 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 C78691ADF30 for ; Tue, 17 Dec 2013 16:27:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.277 X-Spam-Level: X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no 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 Q-APw7fpqKpW for ; Tue, 17 Dec 2013 16:27:48 -0800 (PST) Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id AD8A71ADEC0 for ; Tue, 17 Dec 2013 16:27:48 -0800 (PST) Received: by mail-ob0-f179.google.com with SMTP id wm4so7207604obc.10 for ; Tue, 17 Dec 2013 16:27:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=YZaDZ9qkGuxyb/SXDJ5FyBkJ3HedAIh7dsidnyHjUL8=; b=eQD16cnEyDXQLlKn4Xf1VINGMJ16LBaRSrMLvd3RbSGSLCjxCR4jGdPMazNppIALP7 FatnBtXIhUO4in1m5C4yEu/T5hJs+UFmlB4NAIS/OCltQyGadqQS1vfYN9nRxcZIPt7z K1isUVe7/nkbUzJsDZa+Exad6somCZ9xuw2VjjX1pUgO7w8mihuLS35/TgY1VN6ZiIyQ 0hFEh8rQtNQnLTH7vUaWeUm0oL7TQlXnqBhbnsomWRcPcQ+KuoevVCsakC/99iAC8RK3 OdQgkBMpm0jzC5uHi7qbk2n7Rws1A7dI4iWnnZBeJt4C+3tZ30EwkbXO4k87B7uWG0iV hwvQ== X-Received: by 10.182.255.137 with SMTP id aq9mr502040obd.80.1387326467364; Tue, 17 Dec 2013 16:27:47 -0800 (PST) MIME-Version: 1.0 Sender: charles.newyork@gmail.com Received: by 10.182.27.9 with HTTP; Tue, 17 Dec 2013 16:27:27 -0800 (PST) In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B0FA8D2@FR712WXCHMBA11.zeu.alcatel-lucent.com> References: <52B058CC.1050508@bell-labs.com> <52B07019.80501@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0FA8D2@FR712WXCHMBA11.zeu.alcatel-lucent.com> From: Charles Shen Date: Wed, 18 Dec 2013 08:27:27 +0800 X-Google-Sender-Auth: MqqYTLKwEXI_lvgDCd_TauSdPvw Message-ID: To: "DRAGE, Keith (Keith)" Content-Type: multipart/alternative; boundary=001a1134a71a465ea004edc41d8b Cc: "sip-overload@ietf.org" , "Gurbani, Vijay K \(Vijay\)" 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Dec 2013 00:27:51 -0000 --001a1134a71a465ea004edc41d8b Content-Type: text/plain; charset=UTF-8 Hi Keith, Just want to make sure your +1 is for "leaving it as informative", is that correct or not? I feel the most direct interaction between this draft and the overload-control one is when you specify the numbers in the actions, such as a rate. However, since it does not use the oc-parameter as Vijay mentioned, and the computation of those numbers is also out of scope of this document, It seems ok to leave it as informative. Thanks Charles On Wed, Dec 18, 2013 at 7:54 AM, DRAGE, Keith (Keith) < keith.drage@alcatel-lucent.com> wrote: > 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 > > --001a1134a71a465ea004edc41d8b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Keith, Just want to make sur= e your +1 is for "leaving it as informative", is that correct or = not?

I= feel the most direct interaction between this draft and the overload-contr= ol one is when you specify the numbers in the actions, such as a rate. Howe= ver, since it does not use the oc-parameter as Vijay mentioned, and the com= putation of those numbers is also out of scope of this document, It seems o= k to leave it as informative.=C2=A0

Thanks

Charles=C2= =A0

On Wed, Dec 18, 2013 at 7:54 AM, DRAG= E, Keith (Keith) <keith.drage@alcatel-lucent.com> wrote:
I was about to respond saying pretty much wh= at 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-ove= rload@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-la= bs.com,acm.org} / vijay.gur= bani@alcatel-lucent.com
> Web: h= ttp://ect.bell-labs.com/who/vkg/ =C2=A0| Calendar:
> http://g= oo.gl/x3Ogq _______________________________________________
> sip-overload mailing list
> sip-overloa= d@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload
>

--001a1134a71a465ea004edc41d8b-- From keith.drage@alcatel-lucent.com Tue Dec 17 16:31:05 2013 Return-Path: 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 984E01ADF96 for ; Tue, 17 Dec 2013 16:31:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.899 X-Spam-Level: X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 qZWBpPYdCSTJ for ; Tue, 17 Dec 2013 16:31:03 -0800 (PST) Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id F41B01ADF8A for ; Tue, 17 Dec 2013 16:31:02 -0800 (PST) Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id rBI0Upow023383 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 17 Dec 2013 18:30:53 -0600 (CST) Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id rBI0UpMM008918 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 18 Dec 2013 01:30:51 +0100 Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.203]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Wed, 18 Dec 2013 01:30:51 +0100 From: "DRAGE, Keith (Keith)" To: Charles Shen Thread-Topic: [sip-overload] rate-control and event-package drafts and normative references Thread-Index: AQHO+4f8wPMfF7ykUUyClrxV2WiI4JpZGafw Date: Wed, 18 Dec 2013 00:30:50 +0000 Message-ID: <949EF20990823C4C85C18D59AA11AD8B0FA92A@FR712WXCHMBA11.zeu.alcatel-lucent.com> References: <52B058CC.1050508@bell-labs.com> <52B07019.80501@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0FA8D2@FR712WXCHMBA11.zeu.alcatel-lucent.com> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.239.27.38] Content-Type: multipart/alternative; boundary="_000_949EF20990823C4C85C18D59AA11AD8B0FA92AFR712WXCHMBA11zeu_" MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33 Cc: "sip-overload@ietf.org" , "Gurbani, Vijay K \(Vijay\)" 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Dec 2013 00:31:05 -0000 --_000_949EF20990823C4C85C18D59AA11AD8B0FA92AFR712WXCHMBA11zeu_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Yes, +1 to Vijay and leave as informative. Keith ________________________________ From: charles.newyork@gmail.com [mailto:charles.newyork@gmail.com] On Behal= f Of Charles Shen Sent: 18 December 2013 00:27 To: DRAGE, Keith (Keith) Cc: Gurbani, Vijay K (Vijay); sip-overload@ietf.org Subject: Re: [sip-overload] rate-control and event-package drafts and norma= tive references Hi Keith, Just want to make sure your +1 is for "leaving it as informative"= , is that correct or not? I feel the most direct interaction between this draft and the overload-cont= rol one is when you specify the numbers in the actions, such as a rate. How= ever, since it does not use the oc-parameter as Vijay mentioned, and the co= mputation of those numbers is also out of scope of this document, It seems = ok to leave it as informative. Thanks Charles On Wed, Dec 18, 2013 at 7:54 AM, DRAGE, Keith (Keith) > wrote: 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 > --_000_949EF20990823C4C85C18D59AA11AD8B0FA92AFR712WXCHMBA11zeu_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Yes, +1 to Vijay and leave as= informative.
 
Keith

From: charles.newyork@gmail.com [ma= ilto:charles.newyork@gmail.com] On Behalf Of Charles Shen
Sent: 18 December 2013 00:27
To: DRAGE, Keith (Keith)
Cc: Gurbani, Vijay K (Vijay); sip-overload@ietf.org
Subject: Re: [sip-overload] rate-control and event-package drafts an= d normative references

Hi Keith, Just want to make sure your +1 is = for "leaving it as informative", is that correct or not?

I feel the most direct interaction between this = draft and the overload-control one is when you specify the numbers in the a= ctions, such as a rate. However, since it does not use the oc-parameter as = Vijay mentioned, and the computation of those numbers is also out of scope of this document, It seems ok to lea= ve it as informative. 

Thanks

Charles 

On Wed, Dec 18, 2013 at 7:54 AM, DRAGE, Keith (K= eith) <kei= th.drage@alcatel-lucent.com> wrote:
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-ove= rload@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-la= bs.com,acm.org} / vijay= .gurbani@alcatel-lucent.com
> Web: h= ttp://ect.bell-labs.com/who/vkg/  | Calendar:
> http://goo.gl/x3Ogq<= /a> _______________________________________________
> sip-overload mailing list
> sip-overloa= d@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload
>

--_000_949EF20990823C4C85C18D59AA11AD8B0FA92AFR712WXCHMBA11zeu_-- From charles.newyork@gmail.com Tue Dec 17 19:03:28 2013 Return-Path: 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 9BA761ADF43 for ; Tue, 17 Dec 2013 19:03:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.277 X-Spam-Level: X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no 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 As3ARdJyd2qZ for ; Tue, 17 Dec 2013 19:03:27 -0800 (PST) Received: from mail-oa0-x230.google.com (mail-oa0-x230.google.com [IPv6:2607:f8b0:4003:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 10BD01ADEB4 for ; Tue, 17 Dec 2013 19:03:26 -0800 (PST) Received: by mail-oa0-f48.google.com with SMTP id l6so7548694oag.7 for ; Tue, 17 Dec 2013 19:03:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=QGqjigGqBMU7MFvQGXsVmrSrxFzMJRekXOwYNNiS6E8=; b=VU0OUoRVogR66FJjw+FiSrZtwuyxJQGfAloThRmIYDMuJyPgxu2c9avc+oy5hSZ0CX fStibEXrCzJlGvIrCRRR/+8gz2WtdIzJLVCGCehK63zWQO08rN0dFZA3dWHHUJgh5E3U a8uwNiN2C4gdjMtzYvNUkrNn+MFouBgDLOnz4sv2HTDIPu1FH5Enp3cMHDU2zWmrwnAM zJFPG9EEHVscPYVzesqNUkLdTNLjejRpBZquoMYRM8K9OhkW1QsDHCg5STMZvN4JFsq8 CuZAbACETJGZPhGlwYiHmev0BPTan+BAFSxUEz1vP/54trLqoRivDtbxhPI+S9glxTUi p/uQ== X-Received: by 10.60.165.2 with SMTP id yu2mr274241oeb.78.1387335805595; Tue, 17 Dec 2013 19:03:25 -0800 (PST) MIME-Version: 1.0 Sender: charles.newyork@gmail.com Received: by 10.182.27.9 with HTTP; Tue, 17 Dec 2013 19:03:05 -0800 (PST) In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B0FA92A@FR712WXCHMBA11.zeu.alcatel-lucent.com> References: <52B058CC.1050508@bell-labs.com> <52B07019.80501@bell-labs.com> <949EF20990823C4C85C18D59AA11AD8B0FA8D2@FR712WXCHMBA11.zeu.alcatel-lucent.com> <949EF20990823C4C85C18D59AA11AD8B0FA92A@FR712WXCHMBA11.zeu.alcatel-lucent.com> From: Charles Shen Date: Wed, 18 Dec 2013 11:03:05 +0800 X-Google-Sender-Auth: p2cntlr8P88ytIjxEHMoyT_HzCM Message-ID: To: "DRAGE, Keith (Keith)" Content-Type: multipart/alternative; boundary=047d7b47202ce0a81804edc64990 Cc: "sip-overload@ietf.org" , "Gurbani, Vijay K \(Vijay\)" 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Dec 2013 03:03:28 -0000 --047d7b47202ce0a81804edc64990 Content-Type: text/plain; charset=UTF-8 Great. On Wed, Dec 18, 2013 at 8:30 AM, DRAGE, Keith (Keith) < keith.drage@alcatel-lucent.com> wrote: > Yes, +1 to Vijay and leave as informative. > > Keith > > ------------------------------ > *From:* charles.newyork@gmail.com [mailto:charles.newyork@gmail.com] *On > Behalf Of *Charles Shen > *Sent:* 18 December 2013 00:27 > *To:* DRAGE, Keith (Keith) > *Cc:* Gurbani, Vijay K (Vijay); sip-overload@ietf.org > > *Subject:* Re: [sip-overload] rate-control and event-package drafts and > normative references > > Hi Keith, Just want to make sure your +1 is for "leaving it as > informative", is that correct or not? > > I feel the most direct interaction between this draft and the > overload-control one is when you specify the numbers in the actions, such > as a rate. However, since it does not use the oc-parameter as Vijay > mentioned, and the computation of those numbers is also out of scope of > this document, It seems ok to leave it as informative. > > Thanks > > Charles > > On Wed, Dec 18, 2013 at 7:54 AM, DRAGE, Keith (Keith) < > keith.drage@alcatel-lucent.com> wrote: > >> 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 >> > > > > --047d7b47202ce0a81804edc64990 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Great.


On Wed, Dec 18, 2013 at 8:30 AM, DRAGE, Keith (Keith) <keith.drage@alcatel-lucent.com> wrote:
Yes, +1 to Vijay and leave as informative.
=C2=A0
Keith

Hi Keith, Just want to make sure your +1 is for = "leaving it as informative", is that correct or not?

I feel the most direct interaction between this = draft and the overload-control one is when you specify the numbers in the a= ctions, such as a rate. However, since it does not use the oc-parameter as = Vijay mentioned, and the computation of those numbers is also out of scope of this document, It seems ok to lea= ve it as informative.=C2=A0

Thanks

Charles=C2=A0

On Wed, Dec 18, 2013 at 7:54 AM, DRAGE, Keith (K= eith) <kei= th.drage@alcatel-lucent.com> wrote:
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-ove= rload@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-la= bs.com,acm.org} / vijay= .gurbani@alcatel-lucent.com
> Web: h= ttp://ect.bell-labs.com/who/vkg/ =C2=A0| Calendar:
> http://goo.gl/x3Ogq<= /a> _______________________________________________
> sip-overload mailing list
> sip-overloa= d@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload
>


--047d7b47202ce0a81804edc64990--