Re: [Idr] Barry Leiba's No Objection on draft-ietf-idr-bgpls-segment-routing-epe-18: (with COMMENT)

Barry Leiba <barryleiba@computer.org> Thu, 16 May 2019 13:51 UTC

Return-Path: <barryleiba@gmail.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 90B10120105; Thu, 16 May 2019 06:51:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level:
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-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 KZuWeQLhpr03; Thu, 16 May 2019 06:51:10 -0700 (PDT)
Received: from mail-it1-f177.google.com (mail-it1-f177.google.com [209.85.166.177]) (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 A2A5B1200F8; Thu, 16 May 2019 06:51:10 -0700 (PDT)
Received: by mail-it1-f177.google.com with SMTP id m3so2443948itl.1; Thu, 16 May 2019 06:51:10 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=1bhpQ27gzCuKAErJRwadazao6BS3xVjruGu2LV5rny8=; b=BeqEUY4Gx0iOaYlRXvjtQJnEaO+qcSo2FsdL7dT9kQvB62VGBEfv+XOl+VovCZIeDj 57NWABTWuXyGPztyy17GOx4aCFuEaHX5uDvv2E/w/+7NrG5wcprNoiXSIc6SuMj3JZtd g0/Yhs0mk22LyHCv9egJ+VDzvRvoKufWRqRNfQWWbrzNc6roBHkgAE0WM9IkH0T9QvAx g4E2iW/Oy73GkKQH6v46tCIVmhmg7OaiGIaF9bj/SFupPx6DmETC9+uhYMsFc1WwAbYE 7wM+1fMSrS0YiDr3JKAPv7SWF6ndc4LGQfuOiA7M9G9Jbbvzx2RZZmtfNvqAnzrEwggw 26eA==
X-Gm-Message-State: APjAAAUFI/FHMo7KfOn0ATH75aOggOQO6VYAADDswonm3bNAjKYm+utv lRN5qBxPz824Tb5xhZ0dICoBK7CcI3WiLqLaInI=
X-Google-Smtp-Source: APXvYqw+UefmjzbKfcBzC+6jXmm/AzTbGTOzpsZKSx33WiXNq3SXnNdeC6tHth6CNBeB86Q75r65TtSEIbI632VdglU=
X-Received: by 2002:a05:6638:214:: with SMTP id e20mr33308845jaq.59.1558014669598; Thu, 16 May 2019 06:51:09 -0700 (PDT)
MIME-Version: 1.0
References: <155781273933.23637.4432726142963289545.idtracker@ietfa.amsl.com> <SN6PR11MB28455288C334953431EF7E30C10A0@SN6PR11MB2845.namprd11.prod.outlook.com>
In-Reply-To: <SN6PR11MB28455288C334953431EF7E30C10A0@SN6PR11MB2845.namprd11.prod.outlook.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 16 May 2019 09:50:58 -0400
Message-ID: <CALaySJLWmRv=2EkqNMm9hfdeGh5AcCpGe1N-r2OndYvB=gxZMg@mail.gmail.com>
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
Cc: The IESG <iesg@ietf.org>, "draft-ietf-idr-bgpls-segment-routing-epe@ietf.org" <draft-ietf-idr-bgpls-segment-routing-epe@ietf.org>, Susan Hares <shares@ndzh.com>, "aretana.ietf@gmail.com" <aretana.ietf@gmail.com>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "idr@ietf.org" <idr@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/hx9BXG-Ln8QOuljNwgmuRVvelks>
Subject: Re: [Idr] Barry Leiba's No Objection on draft-ietf-idr-bgpls-segment-routing-epe-18: (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: Thu, 16 May 2019 13:51:13 -0000

Thanks, Ketan!

Barry

On Thu, May 16, 2019 at 5:08 AM Ketan Talaulikar (ketant)
<ketant@cisco.com> wrote:
>
> Hi Barry,
>
> Thanks for your review. I've accepted and updated the draft for all your editorial comments below.
>
> A v19 of the draft has just been posted which includes these changes along with others that I had pending in my buffer from Alvaro's AD review and other IESG last call reviews.
>
> https://tools.ietf.org/html/draft-ietf-idr-bgpls-segment-routing-epe-19
>
> Thanks,
> Ketan
>
> -----Original Message-----
> From: Barry Leiba via Datatracker <noreply@ietf.org>
> Sent: 14 May 2019 11:16
> To: The IESG <iesg@ietf.org>
> Cc: draft-ietf-idr-bgpls-segment-routing-epe@ietf.org; Susan Hares <shares@ndzh.com>; aretana.ietf@gmail.com; idr-chairs@ietf.org; idr@ietf.org
> Subject: Barry Leiba's No Objection on draft-ietf-idr-bgpls-segment-routing-epe-18: (with COMMENT)
>
> Barry Leiba has entered the following ballot position for
> draft-ietf-idr-bgpls-segment-routing-epe-18: 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-bgpls-segment-routing-epe/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Just editorial stuff...
>
> Throughout: “i.e.” needs a comma after it.  So does “e.g.”.
>
> — Section 1 —
>
>    SR can be directly applied to either an MPLS dataplane (SR/MPLS) with
>    no change on the forwarding plane or to a modified IPv6 forwarding
>
> Make it “either to” so it’s parallel with the “or to” that comes later.
>
>    centralized controller based BGP Egress Peer Engineering solution
>    involving SR path computation using the BGP Peering Segments.  This
>    use-case comprises of a centralized controller that learns the BGP
>
> “Centralized-controller-based” is a compound adjective that needs to be hyphenated.  “Use case” is a noun, and should not be hyphenated.  And “comprises” should not have “of” after it (“consists of” would, though).
>
>