Re: [Sidrops] AD review of draft-ietf-sidrops-ov-clarify

Randy Bush <randy@psg.com> Tue, 24 July 2018 21:16 UTC

Return-Path: <randy@psg.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE5581311C9; Tue, 24 Jul 2018 14:16:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham 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 k2XofaAXmZ_s; Tue, 24 Jul 2018 14:16:50 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 458A8130E28; Tue, 24 Jul 2018 14:16:49 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1fi4fn-00027t-EZ; Tue, 24 Jul 2018 21:16:47 +0000
Date: Tue, 24 Jul 2018 14:16:46 -0700
Message-ID: <m27elk8hc1.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Warren Kumari <warren@kumari.net>
Cc: draft-ietf-sidrops-ov-clarify@ietf.org, sidrops-chairs@ietf.org, sidrops@ietf.org
In-Reply-To: <CAHw9_iLod9Fr0PYjpDGtyuD_BH+hOsQOJrT5ngqHwjyUWbaFyA@mail.gmail.com>
References: <CAHw9_iLod9Fr0PYjpDGtyuD_BH+hOsQOJrT5ngqHwjyUWbaFyA@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/k7cEz8NwNGN1OKZ0q3QhVxhIEec>
Subject: Re: [Sidrops] AD review of draft-ietf-sidrops-ov-clarify
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2018 21:16:52 -0000

> 1: Why is this Standards Track? It doesn't update a Std Track
> document

well, it does.  6811.  i guess i should figure out how to get that in
the header.

> 2: Section 3.  Mark ALL Prefixes
>    "Significant Clarification: A router MUST mark all routes in BGP
>    coming from any source (eBGP, iBGP, or redistribution from static),
> unless..."
> Presumably the router should also mark routes redistributed from
> protocols other than static as well? Regardless of the wisdom of
> redistributing $favorite_igp, I'd assume they should be consistent.

hmmm.  i guess i should include 'connected'.  can you think of others?

> 3: The Shepherd Writeup seems to be missing some words:

ain't my dawg

> 4: Nit:
> Section 1.  Introduction
> "Deployment of RPKI-based BGP origin validation is hampered by, among
> other things, vendor mis-implementations in two critical areas, which
> routes are validated and whether policy is applied when not specified
> by configuration."
> 
> I think that this would read much cleaner as:
> "vendor mis-implementations in two critical areas: which routes are
> validated" (s/,/:/)
> If editing the draft to address any of the above, this seems like a
> nit worth addressing.

i have other nits i have fixed in the next rev.

randy