Re: [Idr] Barry Leiba's No Objection on draft-ietf-idr-rfc5575bis-22: (with COMMENT)

Susan Hares <shares@ndzh.com> Wed, 22 April 2020 12:49 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7D723A0B7B; Wed, 22 Apr 2020 05:49:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.948
X-Spam-Level:
X-Spam-Status: No, score=0.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 o6MCEmh7d9Gn; Wed, 22 Apr 2020 05:49:37 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-100-static.hfc.comcastbusiness.net [50.245.122.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B0FB3A0B77; Wed, 22 Apr 2020 05:49:35 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=166.170.25.188;
From: "Susan Hares" <shares@ndzh.com>
To: "'Barry Leiba'" <barryleiba@computer.org>, "'The IESG'" <iesg@ietf.org>
Cc: <draft-ietf-idr-rfc5575bis@ietf.org>, <idr-chairs@ietf.org>, <idr@ietf.org>, "'Jie Dong'" <jie.dong@huawei.com>, <aretana.ietf@gmail.com>
References: <158753687275.21086.14037095023027210670@ietfa.amsl.com>
In-Reply-To: <158753687275.21086.14037095023027210670@ietfa.amsl.com>
Date: Wed, 22 Apr 2020 08:49:14 -0400
Message-ID: <005901d618a4$6e2e2770$4a8a7650$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQEEvI26MCYpNXOTByy5KNUXOciUtaonz3kQ
Content-Language: en-us
X-Antivirus: AVG (VPS 200421-2, 04/21/2020), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/nLIVDe9I6SMwlxEiMmk57DclU9A>
Subject: Re: [Idr] Barry Leiba's No Objection on draft-ietf-idr-rfc5575bis-22: (with COMMENT)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2020 12:49:40 -0000

Barry: 

Thank you for the editorial comments on this draft. 

 I'm sorry I missed the "i.e." in the edits.  Of course it should be "e.g." 

We'll address the remainder in the next draft. 

Sue 

-----Original Message-----
From: Barry Leiba via Datatracker [mailto:noreply@ietf.org] 
Sent: Wednesday, April 22, 2020 2:28 AM
To: The IESG
Cc: draft-ietf-idr-rfc5575bis@ietf.org; idr-chairs@ietf.org; idr@ietf.org; Jie Dong; aretana.ietf@gmail.com; jie.dong@huawei.com
Subject: Barry Leiba's No Objection on draft-ietf-idr-rfc5575bis-22: (with COMMENT)

Barry Leiba has entered the following ballot position for
draft-ietf-idr-rfc5575bis-22: No Objection

When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-idr-rfc5575bis/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

All of this is editorial:

— Abstract —

   Other applications (ie. centralized control of traffic in a SDN or
   NFV context) are also possible.

I don’t think you mean “i.e.” here, but “e.g.”  I would avoid the Latin (for exactly this reason: many people don’t understand it and misuse it) and say, “Other applications, such as centralized control of traffic in an SDN or NFV context, are also possible.”

— Section 1 —

   Modern IP routers contain both the capability to forward traffic
   according to IP prefixes as well as to classify, shape, rate limit,
   filter, or redirect packets based on administratively defined

The two things that come after “both” have to be parallel, and they’re not. 
This will read better without the word “both”, like this:

NEW
   Modern IP routers have the capabilities to forward traffic
   according to IP prefixes and to classify, shape, rate limit,
   filter, or redirect packets based on administratively defined END

   Section 4 of this document defines a general procedure to encode Flow
   Specification for aggregated traffic flows so that they can be
   distributed as a BGP [RFC4271] NLRI.

I think this has to say “Flow Specifications”, plural, yes?  That matches “they”.

   automated systems are used, care should be taken to ensure their
   correctness as well as the limitations of the systems that receive
   and process the advertised Flow Specifications

How does “as well as the limitations...” fit into the sentence?  There seems to be something missing here.

— Section 3 —

   prefix as well as community matching and manipulation, must apply to
   the Flow Specification defined NLRI-type

I can’t tell whether “Flow Specification defined” is meant to be a compound modifier for “NLRI-type” (in which case the former needs hyphens and the latter does not), or this is meant to describe a defined NLRI tyoe called “Flow Specification”.  I think you mean the latter.  Can you re-word this or re-punctuate it to make it clear?

— Section 5 —

   In order to achieve this goal, this document specifies two
   application specific NLRI identifiers that provide traffic filters,
   and a set of actions encoding in BGP Extended Communities.  The two
   application specific NLRI identifiers are:

Both instances of “application-specific” should be hyphenated.

— Section 6 —

   By default a Flow Specification NLRI MUST be validated such that it
   is considered feasible if and only if all of the below is true:

Make it “are true”.

      c) There are no more specific unicast routes

Hyphenate “more-specific” to distinguish it from “there are no more (specific unicast routes)”.

   By originator of a BGP route, we mean either the address of the

But nothing else says “originator of a BGP route”.  (b) does say “originator of the best-match unicast route”... is that what you mean here?  Can you make this match up so it’s clearer?

On thinking more about this text, I think maybe putting quotation marks around “originator” in the quoted sentence is all that’s needed.

   Specification information that conveys a more or equally specific
   destination prefix.

This needs awkward hyphenation ti be correct.  I suggest avoiding that by saying, “Specification information that conveys a destination prefix that is more or equally specific.”

   Thus, as long as there are no more specific
   unicast routes, received from a different neighboring AS, which would
   be affected by that Flow Specification.

As above, hyphenate “more-specific”.  And then fix the sentence, as it doesn’t appear to be a complete sentence.

— Section 7 —

   treated as interfering Traffic filtering actions (see below).

Please capitalize “Filtering Actions”, to be consistent.

   Some Traffic Filtering Actions may interfere with each other even
   contradict.

Make it “may interfere with or even contradict each other.”

— Section 7.7 —

   behaviour (ie. match - replace - delete communities on administrative
   boundaries).

I can’t understand what’s in the parentheses, nor even whether “i.e.” is correct or it should be “e.g.”.

— Section 9 —

   statistics facilities.  While this is an implementation specific

Hyphenate “implementation-specific”.

— Section 12 —

   This may stress the receiving systems, exceed their
   maximum capacity or may lead to unwanted Traffic Filtering Actions
   being applied to flows.

Change “capacity or may lead” to “capacity, or lead” — the “may” is already there at the start of the sentence, and the Oxford comma helps readability here.