Re: [Ecrit] draft-ietf-ecrit-local-emergency-rph-namespace
Janet P Gunn <jgunn6@csc.com> Mon, 18 April 2011 19:22 UTC
Return-Path: <jgunn6@csc.com>
X-Original-To: ecrit@ietfc.amsl.com
Delivered-To: ecrit@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 60611E0714 for <ecrit@ietfc.amsl.com>; Mon, 18 Apr 2011 12:22:28 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V2wknSKWLwLh for <ecrit@ietfc.amsl.com>; Mon, 18 Apr 2011 12:22:25 -0700 (PDT)
Received: from mail164.messagelabs.com (mail164.messagelabs.com [216.82.253.131]) by ietfc.amsl.com (Postfix) with ESMTP id 55D74E0694 for <ecrit@ietf.org>; Mon, 18 Apr 2011 12:22:23 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-4.tower-164.messagelabs.com!1303154541!42851692!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [20.137.2.88]
Received: (qmail 1082 invoked from network); 18 Apr 2011 19:22:22 -0000
Received: from amer-mta102.csc.com (HELO amer-mta102.csc.com) (20.137.2.88) by server-4.tower-164.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Apr 2011 19:22:22 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta102.csc.com (Switch-3.4.3/Switch-3.3.3mp) with ESMTP id p3IJMJss019801 for <ecrit@ietf.org>; Mon, 18 Apr 2011 15:22:21 -0400
In-Reply-To: <A88F12A7-9A91-43A8-971D-69E1AB842606@nostrum.com>
References: <C87DE073.27647%mlinsner@cisco.com> <OF9A370283.14EE1E7E-ON85257776.003DDA78-85257776.003DFFBF@csc.com> <A88F12A7-9A91-43A8-971D-69E1AB842606@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>, ecrit@ietf.org
MIME-Version: 1.0
X-KeepSent: 968BAE2F:50D07487-85257876:0069D185; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.0.2FP1 CCH2 April 23, 2009
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF968BAE2F.50D07487-ON85257876.0069D185-85257876.006A4187@csc.com>
Date: Mon, 18 Apr 2011 15:20:32 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP1 HF29|January 09, 2011) at 04/18/2011 03:21:12 PM, Serialize complete at 04/18/2011 03:21:12 PM
Content-Type: multipart/alternative; boundary="=_alternative 006A303A85257876_="
Subject: Re: [Ecrit] draft-ietf-ecrit-local-emergency-rph-namespace
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Apr 2011 19:22:28 -0000
Here are my comments on -local-emergency-rph-namespace (from last August), which apparently did not get incorporated. Mostly nits, but a couple of comments on content. -- First comment on content At the end of section 2 it says “ To be clear, specifically for the use of an edge proxy in any network, because the "esnet" namespace is allowed to be modified or deleted at the edge proxy of the ESInet does not allow any edge proxy to modify or delete any other Resource-Priority namespace.” First of all, this is a long and awkward sentence, and a little bit awkward to understand. But you SEEM to be saying that an “edge proxy on any network” is not allowed to modify or delete any OTHER R-P namespace. If that is NOT what you are trying to say, then you need to reword it to make it clear that you are only referring to modifying or deleting the esinet header. If that IS what you are trying to say, then I take strong objection to the ESINET Namespace ID (and later RFC) proscribing what other network’s edge proxies can do with/to other namespace headers, and even what the ESInet proxies can do with/to other namespace headers. Perhaps what you mean is “ To be clear, even though an edge proxy of the ESInet may modify or delete an R-P Header with the ESINET namespace, this has no bearing on whether or not a given proxy (on ESInet or elsewhere) is allowed to modify an R-P Header with a different namespace.” Remember that 4412 says that ANY proxy can remove or modify ANY R-P Header (amdr in table 2) -- The second comment on content is about the “intended algorithm”. RFC4412 says that “Both algorithms can sometimes be combined in the same element, although none of the namespaces described in this document do this.” (e.g., both “preemption” and “queue”).” But the IANA registration requires you to chose one or the other – you chose “queue”. It seems that you want to permit “both algorithms combined in the same element”, but the actual text switches back and forth in a very confusing way. First you say “There is the possibility that within emergency services networks - provided local policy supports enabling this function - a Multilevel Precedence and Preemption (MLPP)-like behavior can be achieved (likely without the 'preemption' part, which will always be a matter of local policy, and defined here) “ -Mentioning MLPP/Preemption before mentioning Queuing implies that MLPP is the dominant algorithm -“MLPP-like behavior without the preemption part” is pretty ineffective for anything. But a combination of MLPP and queuing (as in 3GPP eMLPP) can be effective. -What does “and defined here” refer to? MLPP without preemption? “local policy”? In either case I don’t find it “defined here”. Then on the next page you say “The "esnet" namespace has 5 priority-values, in a specified relative priority order, and is a queue-based treatment namespace [RFC4412]. Individual jurisdictions MAY configure their SIP entities for preemption treatment. This is OPTIONAL, subject to local policy decisions.” -it would be a lot clearer if you replaced the earlier reference to MLPP without preemption with something like- “Within an Emergency Services Network, it is possible that local policy will involve a combination of “preemption” and “queuing” algorithms, as permitted by RFC4412, though queuing is expected to be the dominant algorithm, and is selected in the IANA registration. This combination can ensure that more important calls are established or retained. The "esnet" namespace is given 5 priority-levels, analogous to other Prememption based and Queue based namespaces. The MLPP-like SIP signaling needed for the preemption side of a combined algorithm is not defined in this document for 911/112/999 style emergency calling, but it is not prevented either.” And then the second becomes- “The "esnet" namespace has 5 priority-values, in a specified relative priority order, and is a registered as a queue-based treatment namespace [RFC4412]. However, as permitted in RFC4412, individual jurisdictions MAY configure their SIP entities for a combination of queuing and preemption treatment, or even a preemption only treatment. This selection of the treatment algorithm is OPTIONAL, subject to local policy decisions.” Now to the nits. In the introduction, you say : “This new namespace is to be used within public safety answering point (PSAP) networks.” But this appears to be an over-simplification, as elsewhere you say that (dependant, of course, on the proper business and policy agreements): “Adjacent ASPs to the ESInet MAY have a trust relationship that includes allowing this/these neighboring ASP(s) to use the "esnet" namespace to differentiate SIP requests and dialogs within the ASP's network.” (more on other concerns with this sentence later). Perhaps reword the sentence in the Intro to say : “This new namespace is to be used within, or in conjunction with, public safety answering point (PSAP) networks.” Later on in the Intro, you say: “This indication is used solely to differentiate SIP requests, transactions or dialogs, from other requests, transactions or dialogs that do not have the need for priority treatment.” The way it is worded sounds as if you are distinguishing “SIP requests”, from “non-SIP requests”, but I do not think that is what you mean. I think you mean: “This indication is used solely to differentiate PSAP-related SIP requests, transactions or dialogs, from other, non PSAP-related, SIP requests, transactions or dialogs, that do not have the need for priority treatment.” Next sentence says: “If there are differing, yet still valid Resource-Priority header values between SIP requests in a network, then this indication can be used by local policy to determine which SIP request, transaction or dialog receives which treatment (likely better or worse than another).” Going back to the wording of 4412, the point is whether or not the namespaces are “understood”, not just whether the values are valid. But I don’t understand why you say “between” in this context. Suggest: “As described in section 8 of RFC4412, other namespaces, not understood by the SIP actor are ignored. If multiple RPH namespaces are understood by the SIP actor, it must create a local total ordering across all resource values from the namespaces it understands. This will determine the relative priority with which each message, request, transaction or dialog is treated.” In section 2, you say: “Every use of this namespace will be in times of an emergency, where at least one end of the signaling is within a local emergency organization.” This, of course, begs the question -what is the definition of a “time of emergency”? Does some authority have to formally declare a “time of emergency”? It would seem that, by definition, every 911/112/999 call represents a “time of emergency”, at least for the caller. And what do you mean by “one end of signaling? Is a B2BUA an “end”? What is the definition of “a local emergency organization”? If a PSAP is directly connected to the (public) Service Provider network, without a separate “ESI network”, is it allowed to use this namespace? I am confused by the relationship between the terminology in Figure 1 and the terminology in the text. The text refers to “Application Service Providers (ASP) directly attached to an ESInet” (which may have a trust relationship with the ESInet, and thus may use the esinet namespace). But the figure does not show an ASP, it shows something called a “Service Network”. Is the “Service Network” supposed to be the “ASP”? This sentence in sec 3.2 is rather awkward: “The rules originated in RFC 4412 remain with regard to an RP actor, who understands more than one namespace, MUST maintain its locally significant relative priority order.” Perhaps “The rules originated in RFC 4412 , that an RP actor, who understands more than one namespace, MUST maintain its locally significant relative priority order, remain in effect.” In section 6, this sentence is ambiguous: “ The implications of using this namespace within the Resource-Priority header field incorrectly can cause a large impact on a network - given that this indication is to give preferential treatment of marked traffic great preference within the network than other traffic.” First, “marked” could mean many different things. Second, given that you have 5 different priority levels, it is unlikely that they ALL “give preferential treatment of marked traffic great preference” (which is also redundant). Suggest: “Incorrectly using this namespace within the Resource-Priority header field can cause a large impact on a network. For some priority values, this namespace can give great preference within the network to marked traffic over other traffic.” Thanks 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: Robert Sparks <rjsparks@nostrum.com> To: Janet P Gunn/USA/CSC@CSC Date: 04/07/2011 01:42 PM Subject: Re: [Ecrit] draft-ietf-ecrit-local-emergency-rph-namespace Hi Janet - I'm picking this back up (it fell between some cracks). Did you get a chance to review it last year? RjS On Aug 5, 2010, at 6:17 AM, Janet P Gunn wrote: I plan to review it, but not until the second half of August. 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: Marc Linsner <mlinsner@cisco.com> To: "'ecrit'" <ecrit@ietf.org> Date: 08/03/2010 03:04 PM Subject: [Ecrit] draft-ietf-ecrit-local-emergency-rph-namespace All, As you all know, RPH namespace is an ECRIT draft without a milestone. At the meeting last week Robert Sparks announced he is willing to AD sponsor this draft. Robert asks everyone to read the draft and comment on it to this list. Thanks, -Marc- _______________________________________________ Ecrit mailing list Ecrit@ietf.org https://www.ietf.org/mailman/listinfo/ecrit _______________________________________________ Ecrit mailing list Ecrit@ietf.org https://www.ietf.org/mailman/listinfo/ecrit
- [Ecrit] draft-ietf-ecrit-local-emergency-rph-name… Marc Linsner
- Re: [Ecrit] draft-ietf-ecrit-local-emergency-rph-… Janet P Gunn
- Re: [Ecrit] draft-ietf-ecrit-local-emergency-rph-… Janet P Gunn
- [Ecrit] draft-ietf-ecrit-local-emergency-rph-name… Janet P Gunn
- Re: [Ecrit] draft-ietf-ecrit-local-emergency-rph-… James M. Polk
- [Ecrit] draft-polk-local-emergency-rph-namespace-… Janet P Gunn
- Re: [Ecrit] draft-polk-local-emergency-rph-namesp… DOLLY, MARTIN C (ATTSI)
- Re: [Ecrit] draft-polk-local-emergency-rph-namesp… James M. Polk