Re: [Sidrops] RtgDir review: draft-ietf-sidrops-ov-clarify-03
Randy Bush <randy@psg.com> Fri, 10 August 2018 18:26 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 80DB5130E47; Fri, 10 Aug 2018 11:26:13 -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 F_J_nZlpcCiw; Fri, 10 Aug 2018 11:26:12 -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 DAB57130DF9; Fri, 10 Aug 2018 11:26:11 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1foC6y-00048w-4t; Fri, 10 Aug 2018 18:26:08 +0000
Date: Fri, 10 Aug 2018 11:26:07 -0700
Message-ID: <m2mutuhydc.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
Cc: rtg-ads@ietf.org, rtg-dir@ietf.org, draft-ietf-sidrops-ov-clarify.all@ietf.org, sidrops@ietf.org, Dhruv Dhody <dhruv.dhody@huawei.com>
In-Reply-To: <CAB75xn4eFqfykXdhQZjn3=r5t1DsK=gZQ6C=xd6Pwf376oiNPw@mail.gmail.com>
References: <72ee1d70-d135-a445-75df-65df06fda61a@gmail.com> <m2sh3mi1cr.wl-randy@psg.com> <CAB75xn4eFqfykXdhQZjn3=r5t1DsK=gZQ6C=xd6Pwf376oiNPw@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="ISO-8859-7"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/e5UHjSVqEqczBaKbGB3M6WuLHoA>
Subject: Re: [Sidrops] RtgDir review: draft-ietf-sidrops-ov-clarify-03
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: Fri, 10 Aug 2018 18:26:14 -0000
>>> - Since RFC4271 and RFC6480 are stated as mandatory reading to >>> understand >>> this I-D in section 2, shouldn’t they be normative references? >> >> i will be interested in others' feedback on this one. i take normative >> as needed to implement, not as needed to have clue :) > > I usually go by this IESG statement - > https://www.ietf.org/blog/iesg-statement-normative-and-informative-references/; > which says - "Normative references specify documents that must be read to > understand or implement the technology in the new RFC, or whose technology > must be present for the technology in the new RFC to work." Just FYI yes. i guess so. my broken mind-set. >> i have pushed -04. i hope the diff does not cause heartburn to anyone. > > I saw these nits in the diff - > > OLD: > When a route is distributed into BGP, the origin validation state of > the is set to as NotFound, Valid, or Invalid per [RFC6811]. > NEW: > When a route is distributed into BGP, the origin validation state of > the prefix is set to as NotFound, Valid, or Invalid as per [RFC6811]. sigh. thanks will hold -5 for a few more reviews randy