From shida@ntt-at.com Mon Oct 3 07:44:58 2011 Return-Path: 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 55F4721F8B40 for ; Mon, 3 Oct 2011 07:44:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.265 X-Spam-Level: X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M+1zYd5C5CQF for ; Mon, 3 Oct 2011 07:44:57 -0700 (PDT) Received: from gator465.hostgator.com (gator465.hostgator.com [69.56.174.130]) by ietfa.amsl.com (Postfix) with ESMTP id D0A7121F8B3F for ; Mon, 3 Oct 2011 07:44:57 -0700 (PDT) Received: from [122.133.87.237] (port=56987 helo=[192.168.1.14]) by gator465.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1RAjoE-0005bf-2V for sip-overload@ietf.org; Mon, 03 Oct 2011 09:47:58 -0500 From: Shida Schubert Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Mon, 3 Oct 2011 23:47:56 +0900 Message-Id: <15724199-7C27-4577-ADB3-3CB8A484C030@ntt-at.com> To: sip-overload@ietf.org Mime-Version: 1.0 (Apple Message framework v1244.3) X-Mailer: Apple Mail (2.1244.3) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator465.hostgator.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ntt-at.com X-BWhitelist: no X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: fl1-122-133-87-237.tky.mesh.ad.jp ([192.168.1.14]) [122.133.87.237]:56987 X-Source-Auth: shida@agnada.com X-Email-Count: 5 X-Source-Cap: c3NoaWRhO3NzaGlkYTtnYXRvcjQ2NS5ob3N0Z2F0b3IuY29t Subject: [sip-overload] Comments on draft-ietf-soc-load-control-event-package-01 X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2011 14:44:58 -0000 I recently reviewed the draft and below are some comments. A: Terminology First of all, I find that the document is rather hard to read=20 because; 1. it uses different terminology for what I believe is=20 the same thing. 2. introduce many terminology that=20 is not defined anywhere and 3. the terminology used should=20 probably be aligned with that of the other drafts=20 that define some of these terminologies (RFC6537 etc). Here are some examples; 1. "load control" - should this be "overload control"? 2. What is "user load control information"? 3. "edge server" - edge of what? At the edge of domain?=20 4. load document, load control document and load filter, are they the = same thing? 5. load filtering mechanism and load filter control the same thing? 6. What is a dynamic filter?=20 7. What is a load control policy maker? 8. What is a policy entry point? 9. What is a filter computation decision maker? 10. Is load control policy, load control information and load control = rule the same thing? 11. What is load control filter content definition? Also some terminology can be changed to common terminology used in SIP = related RFCs e.g. SIP entity subscribers > SIP subscribers or subscribers e.g. local format/global format > local number / global number = [RFC3966] B: Requirements The draft does a really nice job evaluating whether the=20 document meets the requirements set forth by RFC 5390 in=20 section section 9. but the draft also has design requirements=20 in section 3. This seems reasonable thing to have but shouldn't=20 these requirements expressed with RFC2119 language? =20 =20 C: Behavior of Notifier and Subscriber is mixed in section 5.6 - I think followings should be described as Subscribers' behavior.=20 "SIP entity subscribers SHOULD try to subscribe to all those SIP entity notifiers with which they have regular signaling exchanges, although not all such SIP notifiers may permit such a subscription" D: Technical questions 1. section 5.7.=20 - "Following the [RFC3265] specification, a notifier MUST send a = NOTIFY with its current load control policy to the subscriber upon successfully accepting or refreshing a subscription. The NOTIFY request MAY include a body. " - So it says MUST send a NOTIFY but it is followed by MAY include a = body. If load control policy is carried in a body, I don't know there is = a MAY following=20 the first paragraph.=20 - If what you want to say is to include the control policy in the body = when=20 there is an active policy to be MUST and otherwise a MAY, this = should be=20 clarified.=20 2. section 5.8. - "Upon receipt of a NOTIFY request with a Subscription-State header field containing the value "terminated", the subscriber MUST remove all previously received load control information and process all calls without applying any restriction" - This should be clarified that this applies only to the relevant = filter and=20 not to all the policy that may be active at the time of receiving = this NOTIFY.=20 Regards Shida=20 =20 =20= From internet-drafts@ietf.org Fri Oct 28 13:41:17 2011 Return-Path: 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 E426B21F8509; Fri, 28 Oct 2011 13:41:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.556 X-Spam-Level: X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tXFPAbo4xhIK; Fri, 28 Oct 2011 13:41:17 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84BC621F84E1; Fri, 28 Oct 2011 13:41:17 -0700 (PDT) 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: 3.62 Message-ID: <20111028204117.31699.15344.idtracker@ietfa.amsl.com> Date: Fri, 28 Oct 2011 13:41:17 -0700 Cc: sip-overload@ietf.org Subject: [sip-overload] I-D Action: draft-ietf-soc-overload-control-04.txt X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2011 20:41:18 -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-04.txt Pages : 32 Date : 2011-10-28 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-soc-overload-control-04.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-soc-overload-control-04.txt From internet-drafts@ietf.org Fri Oct 28 14:29:04 2011 Return-Path: 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 E101521F84CB; Fri, 28 Oct 2011 14:29:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.557 X-Spam-Level: X-Spam-Status: No, score=-102.557 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L8NeeNP-HE93; Fri, 28 Oct 2011 14:29:04 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 763CC21F84C1; Fri, 28 Oct 2011 14:29:04 -0700 (PDT) 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: 3.62 Message-ID: <20111028212904.12976.82383.idtracker@ietfa.amsl.com> Date: Fri, 28 Oct 2011 14:29:04 -0700 Cc: sip-overload@ietf.org Subject: [sip-overload] I-D Action: draft-ietf-soc-overload-control-05.txt X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2011 21:29:05 -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-05.txt Pages : 32 Date : 2011-10-28 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-soc-overload-control-05.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-soc-overload-control-05.txt From vkg@bell-labs.com Fri Oct 28 14:54:03 2011 Return-Path: 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 23B231F0C55 for ; Fri, 28 Oct 2011 14:54:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.562 X-Spam-Level: X-Spam-Status: No, score=-106.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rZ1zozwfiuTa for ; Fri, 28 Oct 2011 14:54:02 -0700 (PDT) Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 31B8A1F0C54 for ; Fri, 28 Oct 2011 14:54:02 -0700 (PDT) Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p9SLrxFG012001 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 28 Oct 2011 16:53:59 -0500 (CDT) Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p9SLrwjb016894 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 28 Oct 2011 16:53:59 -0500 Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id p9SLrwqD027860 for ; Fri, 28 Oct 2011 16:53:58 -0500 (CDT) Message-ID: <4EAB2526.3030307@bell-labs.com> Date: Fri, 28 Oct 2011 16:56:54 -0500 From: "Vijay K. Gurbani" Organization: Bell Laboratories, Alcatel-Lucent User-Agent: Mozilla/5.0 (X11; Linux i686; rv:7.0) Gecko/20110927 Thunderbird/7.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.39 X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10 Subject: [sip-overload] draft-ietf-soc-overload-control-05 released X-BeenThere: sip-overload@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP Overload List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2011 21:54:03 -0000 Folks: I have released a new version of the SIP overload control draft, version -05. (BTW, version -04 did not contain one crucial consensus item that was hashed on the list, so -05 was released shortly after -04 to account for this). This version is a result of discussions since the Quebec City IETF. More specifically, the following changes have occurred between -05 and -03: - Editorial and typo nits. - An expanded Section 5 to encode general behavior. - Addition of S5.1 (Handshake to determine support for overload control). - There was some confusion in Section 4.2 where -03 was ambiguous on whether or not a client should include "oc-algo" parameter. This has been ironed out in the first paragraph of S4.2. - The client orders the overload control algorithms in the "oc-algo" parameter by decreasing order of preference, however, the server is not bound to pick the most preferred algorithm if it does not want to (new text in Section 4.2) [1]. - Clients continue to include all overload control algorithms in the "oc-algo" parameter even after the client and server have converged to mutually agreeable class (next text in Section 4.2) [2]. - Pushed the burden on re-negotiation to server instead of client (diffs in Section 5.8) [2]. - Specified a default (and reference) algorithm for loss-based overload control (Section 6.3). -05 is available in [3], and a diff against -03 is available in [4]. [1] http://www.ietf.org/mail-archive/web/sip-overload/current/msg00666.html [2] http://www.ietf.org/mail-archive/web/sip-overload/current/msg00672.html [3] http://tools.ietf.org/html/draft-ietf-soc-overload-control-05 [4] http://tools.ietf.org/rfcdiff?url1=http://www.ietf.org/id/draft-ietf-soc-overload-control-03.txt&url2=http://www.ietf.org/id/draft-ietf-soc-overload-control-05.txt Please let me know if there are any further issues with the draft. Thanks, - vijay -- Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA) Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com Web: http://ect.bell-labs.com/who/vkg/