Re: [sip-overload] NaN? RE: WGLC: draft-ietf-soc-overload-rate-control - Christer's comments
"NOEL, ERIC C (ERIC C)" <ecnoel@research.att.com> Mon, 08 July 2013 23:34 UTC
Return-Path: <ecnoel@research.att.com>
X-Original-To: sip-overload@ietfa.amsl.com
Delivered-To: sip-overload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BB7021F9130; Mon, 8 Jul 2013 16:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 kGqRd+kH2osi; Mon, 8 Jul 2013 16:34:32 -0700 (PDT)
Received: from mail-pink.research.att.com (mail-pink.research.att.com [192.20.225.111]) by ietfa.amsl.com (Postfix) with ESMTP id 9E59711E80E3; Mon, 8 Jul 2013 16:34:31 -0700 (PDT)
Received: from mail-blue.research.att.com (unknown [135.207.178.11]) by mail-pink.research.att.com (Postfix) with ESMTP id 5CC8C120445; Mon, 8 Jul 2013 19:34:27 -0400 (EDT)
Received: from njfpsrvexg2.research.att.com (njfpsrvexg2.research.att.com [135.207.177.29]) by mail-blue.research.att.com (Postfix) with ESMTP id ECD89F035E; Mon, 8 Jul 2013 19:34:27 -0400 (EDT)
Received: from njfpsrvexg2.research.att.com ([fe80::a158:97ea:81b0:43d9]) by njfpsrvexg2.research.att.com ([fe80::a158:97ea:81b0:43d9%14]) with mapi; Mon, 8 Jul 2013 19:34:27 -0400
From: "NOEL, ERIC C (ERIC C)" <ecnoel@research.att.com>
To: 'Janet P Gunn' <jgunn6@csc.com>, Christer Holmberg <christer.holmberg@ericsson.com>
Date: Mon, 08 Jul 2013 19:34:26 -0400
Thread-Topic: [sip-overload] NaN? RE: WGLC: draft-ietf-soc-overload-rate-control - Christer's comments
Thread-Index: Ac50EnS/YoXUUMYZQza9CySEFn2SGgIHs60g
Message-ID: <5EBD159DE88147488A3B1590E09001840353BDA4CABE@njfpsrvexg2.research.att.com>
References: <7594FB04B1934943A5C02806D1A2204B1C3BD16D@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1C3BD239@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1C3BD25A@ESESSMB209.ericsson.se> <OF97A56D05.62DA95E0-ON85257B98.005376F9-85257B98.0053E029@csc.com>
In-Reply-To: <OF97A56D05.62DA95E0-ON85257B98.005376F9-85257B98.0053E029@csc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_5EBD159DE88147488A3B1590E09001840353BDA4CABEnjfpsrvexg2_"
MIME-Version: 1.0
Cc: "sip-overload-bounces@ietf.org" <sip-overload-bounces@ietf.org>, "draft-ietf-soc-overload-rate-control.all@tools.ietf.org" <draft-ietf-soc-overload-rate-control.all@tools.ietf.org>, "sip-overload@ietf.org" <sip-overload@ietf.org>
Subject: Re: [sip-overload] NaN? RE: WGLC: draft-ietf-soc-overload-rate-control - Christer's comments
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-overload>, <mailto:sip-overload-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-overload>
List-Post: <mailto:sip-overload@ietf.org>
List-Help: <mailto:sip-overload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-overload>, <mailto:sip-overload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jul 2013 23:34:37 -0000
Janet, Christer, Thank you for your comments and discussion. Actually we did not define any operation for oc = "NaN". In section 5.0, I propose the following change (what is used in draft-ietf-soc-overload-control-12): Replace oc-value = "NaN" / oc-num by oc = "oc" [EQUAL oc-num] Please confirm this change would address the issue. Thanks, Eric Noel AT&T Labs, Inc. Rethink Possible Network Design and Performance Analysis 200 South Laurel Avenue, D5-3D19 Middletown, NJ 07748 P: 732.420.4174 ecnoel@att.com<mailto:jsmith@att.com> From: sip-overload-bounces@ietf.org [mailto:sip-overload-bounces@ietf.org] On Behalf Of Janet P Gunn Sent: Friday, June 28, 2013 11:16 AM To: Christer Holmberg Cc: sip-overload-bounces@ietf.org; draft-ietf-soc-overload-rate-control.all@tools.ietf.org; sip-overload@ietf.org Subject: [sip-overload] NaN? RE: WGLC: draft-ietf-soc-overload-rate-control - Christer's comments Thanks Christer, Syntax is definitely NOT my area of expertise, so I will let the authors follow up. Eric and Philip, What is supposed to happen when oc = "NaN"? I do not see any reference to it in the rest of the document. Is it even needed? Janet This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. From: Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>> To: Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>>, Janet P Gunn/USA/CSC@CSC Cc: "sip-overload-bounces@ietf.org<mailto:sip-overload-bounces@ietf.org>" <sip-overload-bounces@ietf.org<mailto:sip-overload-bounces@ietf.org>>, "draft-ietf-soc-overload-rate-control.all@tools.ietf.org<mailto:draft-ietf-soc-overload-rate-control.all@tools.ietf.org>" <draft-ietf-soc-overload-rate-control.all@tools.ietf.org<mailto:draft-ietf-soc-overload-rate-control.all@tools.ietf.org>>, "sip-overload@ietf.org<mailto:sip-overload@ietf.org>" <sip-overload@ietf.org<mailto:sip-overload@ietf.org>> Date: 06/28/2013 03:25 AM Subject: RE: [sip-overload] WGLC: draft-ietf-soc-overload-rate-control - Christer's comments ________________________________ The following is obviously not needed in draft-ietf-soc-overload-control: "EQUAL" is defined in RFC 3261. "DIGIT" is defined in RFC 5234. From: sip-overload-bounces@ietf.org<mailto:sip-overload-bounces@ietf.org> [mailto:sip-overload-bounces@ietf.org] On Behalf Of Christer Holmberg Sent: 28. kesäkuuta 2013 9:27 To: Janet P Gunn Cc: sip-overload-bounces@ietf.org<mailto:sip-overload-bounces@ietf.org>; draft-ietf-soc-overload-rate-control.all@tools.ietf.org<mailto:draft-ietf-soc-overload-rate-control.all@tools.ietf.org>; sip-overload@ietf.org<mailto:sip-overload@ietf.org> Subject: Re: [sip-overload] WGLC: draft-ietf-soc-overload-rate-control - Christer's comments Hi, So, with the third alternative, Section 5 would look something like: 5. Syntax This specification extends the existing definition of the Via header field parameters of [RFC3261] as follows: via-params =/ oc-nan oc-nan = "NaN" BTW, I think the syntax in draft-ietf-soc-overload-control should look like: via-params =/ oc / oc-validity / oc-seq / oc-algo oc = "oc" [EQUAL oc-num] oc-num = 1*DIGIT oc-validity = "oc-validity" [EQUAL delta-ms] oc-seq = "oc-seq" EQUAL 1*12DIGIT "." 1*5DIGIT oc-algo = "oc-algo" EQUAL DQUOTE algo-list *(COMMA algo-list) DQUOTE algo-list = "loss" / *(other-algo) other-algo = %x41-5A / %x61-7A / %x30-39 delta-ms = 1*DIGIT In both drafts, I would also suggest to rewrite the Syntax sections in the following way: 5. Grammar 5.1. General This section extends the ABNF definition of via-params from [RFC3261] by adding a new Via header field parameter, "oc-nan". The ABNF defined in this specification is conformant to RFC 5234 [RFC5234]. "EQUAL" is defined in RFC 3261. "DIGIT" is defined in RFC 5234. 5.2. ABNF via-params =/ oc-nan oc-nan = "NaN" Regards, Christer From: Christer Holmberg Sent: 28. kesäkuuta 2013 8:40 To: Christer Holmberg; Janet P Gunn Cc: sip-overload-bounces@ietf.org<mailto:sip-overload-bounces@ietf.org>; draft-ietf-soc-overload-rate-control.all@tools.ietf.org<mailto:draft-ietf-soc-overload-rate-control.all@tools.ietf.org>; sip-overload@ietf.org<mailto:sip-overload@ietf.org> Subject: VS: [sip-overload] WGLC: draft-ietf-soc-overload-rate-control - Christer's comments Hi, A third alternative (probably the easiest one, at least from a syntax perspective) would be to simply define a new “oc-nan” Via header field parameter. oc-nan = "nan" …or something like that. It would not require any changes to draft-ietf-soc-overload-control . (Then, in the procedure sections you need to describe how/whether the oc and oc-nan parameters can be used at the same time etc, but that is not a syntax question.) Regards, Christer Lähettäjä: sip-overload-bounces@ietf.org<mailto:sip-overload-bounces@ietf.org> [mailto:sip-overload-bounces@ietf.org] Puolesta Christer Holmberg Lähetetty: 27. kesäkuuta 2013 22:42 Vastaanottaja: Janet P Gunn Kopio: sip-overload-bounces@ietf.org<mailto:sip-overload-bounces@ietf.org>; draft-ietf-soc-overload-rate-control.all@tools.ietf.org<mailto:draft-ietf-soc-overload-rate-control.all@tools.ietf.org>; sip-overload@ietf.org<mailto:sip-overload@ietf.org> Aihe: Re: [sip-overload] WGLC: draft-ietf-soc-overload-rate-control - Christer's comments Hi, When taking a closer look, I actually think there is something technically wrong with the syntax in Section 5 of draft-ietf-soc-overload-rate-control. draft-ietf-soc-overload-control defines the oc parameter as: oc = "oc" [EQUAL oc-num] Now, it seems like draft-ietf-soc-overload-rate-control actually re-defines the same parameter. In addition, it’s done in a backward compatible manner, e.g. because the parameter can now contain a non-numeric value (see the bullet list below what can go wrong): oc = "oc" EQUAL oc-value The following can happen: 1. If an entity that supports draft-ietf-soc-overload-control receives “oc=NaN” it will reject it, as it expects a numeric value. 2. If an entity that supports draft-ietf-soc-overload-rate-control receives “oc” it will reject it, as it expects an oc-value. But, in draft-ietf-soc-overload-control the usage of oc-value is optional. One way to fix this could be to define oc-value as a separate Via header field parameter (similar to oc-validity, oc-seq etc), instead of a value of the oc parameter. But, then you would have oc-num Another way is to change the syntax in draft-ietf-soc-overload-control , in order to allow what you want to do in draft-ietf-soc-overload-rate-control. Regards, Christer Lähettäjä: Janet P Gunn [mailto:jgunn6@csc.com] Lähetetty: 27. kesäkuuta 2013 22:04 Vastaanottaja: Christer Holmberg Kopio: draft-ietf-soc-overload-rate-control.all@tools.ietf.org<mailto:draft-ietf-soc-overload-rate-control.all@tools.ietf.org>; sip-overload@ietf.org<mailto:sip-overload@ietf.org>; sip-overload-bounces@ietf.org<mailto:sip-overload-bounces@ietf.org> Aihe: Re: VS: [sip-overload] WGLC: draft-ietf-soc-overload-rate-control - Christer's comments Christer draft-ietf-soc-overload-control says " 8. Syntax This specification extends the existing definition of the Via header field parameters of [RFC3261] as follows: via-params = via-ttl / via-maddr / via-received / via-branch / oc / oc-validity / oc-seq / oc-algo / via-extension oc = "oc" [EQUAL oc-num] oc-num = 1*DIGIT oc-validity = "oc-validity" [EQUAL delta-ms] oc-seq = "oc-seq" EQUAL 1*12DIGIT "." 1*5DIGIT oc-algo = "oc-algo" EQUAL DQUOTE algo-list *(COMMA algo-list) DQUOTE algo-list = "loss" / *(other-algo) other-algo = %x41-5A / %x61-7A / %x30-39 delta-ms = 1*DIGIT" and "11. IANA Considerations This specification defines four new Via header parameters as detailed below in the "Header Field Parameter and Parameter Values" sub- registry as per the registry created by [RFC3968]. The required information is: Header Field Parameter Name Predefined Values Reference __________________________________________________________ Via oc Yes RFCXXXX Via oc-validity Yes RFCXXXX Via oc-seq Yes RFCXXXX Via oc-algo Yes RFCXXXX RFC XXXX [NOTE TO RFC-EDITOR: Please replace with final RFC number of this specification.]" The text of draft-ietf-soc-overload-control refers to both "loss" and "rate" as values for oc-algo. The text of draft-ietf-soc-overload-control section 5.3 refers to the use of oc for either rate or loss "As an example, a value of "oc=10" when the loss-based algorithm is used implies that 10% of the total number of SIP requests (dialog forming as well as in-dialogue) are subject to reduction at the client. Analogously, a value of "oc=10" when the rate-based algorithm [I-D.ietf-soc-overload-rate-control] is used indicates that the client should send SIP requests at a rate of 10 SIP requests or fewer per second." What are you suggesting would go in the "IANA Considerations" section of draft-ietf-soc-overload-rate-control ? Does it just need a reference to the IANA Considerations in draft-ietf-soc-overload-control? Janet This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. From: Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>> To: Janet P Gunn/USA/CSC@CSC Cc: "draft-ietf-soc-overload-rate-control.all@tools.ietf.org<mailto:draft-ietf-soc-overload-rate-control.all@tools.ietf.org>" <draft-ietf-soc-overload-rate-control.all@tools.ietf.org<mailto:draft-ietf-soc-overload-rate-control.all@tools.ietf.org>>, "sip-overload@ietf.org<mailto:sip-overload@ietf.org>" <sip-overload@ietf.org<mailto:sip-overload@ietf.org>>, "sip-overload-bounces@ietf.org<mailto:sip-overload-bounces@ietf.org>" <sip-overload-bounces@ietf.org<mailto:sip-overload-bounces@ietf.org>> Date: 06/27/2013 12:54 PM Subject: VS: [sip-overload] WGLC: draft-ietf-soc-overload-rate-control - Christer's comments ________________________________ Hi, >The IANA considerations section of draft-ietf-soc-overload-control registers the new Via header field parameters. > >Is it needed here as well? The draft (Section 5) does extend the oc parameter, doesn’t it? I would assume that needs to go to IANA. Regards, Christer sip-overload-bounces@ietf.org<mailto:sip-overload-bounces@ietf.org> wrote on 06/27/2013 06:05:41 AM: > From: Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>> > To: "sip-overload@ietf.org<mailto:sip-overload@ietf.org>" <sip-overload@ietf.org<mailto:sip-overload@ietf.org>> > Cc: "draft-ietf-soc-overload-rate-control.all@tools.ietf.org<mailto:draft-ietf-soc-overload-rate-control.all@tools.ietf.org>" > <draft-ietf-soc-overload-rate-control.all@tools.ietf.org<mailto:draft-ietf-soc-overload-rate-control.all@tools.ietf.org>> > Date: 06/27/2013 06:05 AM > Subject: [sip-overload] WGLC: draft-ietf-soc-overload-rate-control - > Christer's comments > Sent by: sip-overload-bounces@ietf.org<mailto:sip-overload-bounces@ietf.org> > > Hi, > > I have read draft-ietf-soc-overload-rate-control-04.txt as part of the WGLC. > ... > Q7: In Section 7 you say that there are no IANA considerations. But, > don’t you need to request IANA to register the new Via header field > parameters? > > Regards, > > Christer > > > > > _______________________________________________ > sip-overload mailing list > sip-overload@ietf.org<mailto:sip-overload@ietf.org> > https://www.ietf.org/mailman/listinfo/sip-overload
- [sip-overload] WGLC: draft-ietf-soc-overload-rate… Christer Holmberg
- Re: [sip-overload] WGLC: draft-ietf-soc-overload-… Janet P Gunn
- Re: [sip-overload] WGLC: draft-ietf-soc-overload-… Christer Holmberg
- Re: [sip-overload] WGLC: draft-ietf-soc-overload-… Janet P Gunn
- Re: [sip-overload] WGLC: draft-ietf-soc-overload-… Christer Holmberg
- Re: [sip-overload] WGLC: draft-ietf-soc-overload-… Christer Holmberg
- Re: [sip-overload] WGLC: draft-ietf-soc-overload-… Christer Holmberg
- Re: [sip-overload] WGLC: draft-ietf-soc-overload-… Christer Holmberg
- Re: [sip-overload] WGLC: draft-ietf-soc-overload-… Paul Kyzivat
- [sip-overload] NaN? RE: WGLC: draft-ietf-soc-over… Janet P Gunn
- Re: [sip-overload] WGLC: draft-ietf-soc-overload-… DRAGE, Keith (Keith)
- Re: [sip-overload] WGLC: draft-ietf-soc-overload-… Paul Kyzivat
- Re: [sip-overload] WGLC: draft-ietf-soc-overload-… Janet P Gunn
- Re: [sip-overload] NaN? RE: WGLC: draft-ietf-soc-… NOEL, ERIC C (ERIC C)
- Re: [sip-overload] WGLC: draft-ietf-soc-overload-… NOEL, ERIC C (ERIC C)
- Re: [sip-overload] WGLC: draft-ietf-soc-overload-… NOEL, ERIC C (ERIC C)
- Re: [sip-overload] WGLC: draft-ietf-soc-overload-… NOEL, ERIC C (ERIC C)
- Re: [sip-overload] WGLC: draft-ietf-soc-overload-… DRAGE, Keith (Keith)