Re: [GROW] [Technical Errata Reported] RFC8326 (5402)

Warren Kumari <warren@kumari.net> Thu, 21 June 2018 21:45 UTC

MIME-Version: 1.0
References: <20180621193621.4FB96B811A4@rfc-editor.org>
In-Reply-To: <20180621193621.4FB96B811A4@rfc-editor.org>
From: Warren Kumari <warren@kumari.net>
Date: Thu, 21 Jun 2018 17:45:15 -0400
Message-ID: <CAHw9_iJbgderrVZEqhdzg_R_KpVN9fJUaMGE51=yu5YybuG4Nw@mail.gmail.com>
To: RFC System <rfc-editor@rfc-editor.org>
Cc: pfrpfr@gmail.com, Bruno Decraene <bruno.decraene@orange.com>, pelsser@unistra.fr, Keyur Patel <keyur@arrcus.com>, cfilsfil@cisco.com, Ignas Bagdonas <ibagdona@gmail.com>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, John Scudder <jgs@juniper.net>, "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d5a715056f2dd6ef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/44AyTkeuJtuL0foueRp42uTIvIg>
Subject: Re: [GROW] [Technical Errata Reported] RFC8326 (5402)
Precedence: list

On Thu, Jun 21, 2018 at 3:36 PM RFC Errata System <rfc-editor@rfc-editor.org>
wrote:

> The following errata report has been submitted for RFC8326,
> "Graceful BGP Session Shutdown".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata/eid5402
>
> --------------------------------------
> Type: Technical
> Reported by: John Scudder <jgs@juniper.net>
>
> Section: C.2.2.
>
> Original Text
> -------------
>       4.  If, for any reason, RR3 processes the withdraw generated in
>           step 3 before processing the update generated in step 2, RR3
>           transiently suffers from unreachability for the affected
>           prefix.
>
> Corrected Text
> --------------
>       4.  If, for any reason, RR2 processes the withdraw generated in
>           step 3 before processing the update generated in step 2, RR2
>           transiently suffers from unreachability for the affected
>           prefix.
>
> Notes
> -----
> The original text names RR3, but it should be RR2. This becomes evident
> when one works through the example using a diagram.
>

I believe that this is right -- does anyone disagree? If not I'll plan on
approving it.
W




>
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC8326 (draft-ietf-grow-bgp-gshut-13)
> --------------------------------------
> Title               : Graceful BGP Session Shutdown
> Publication Date    : March 2018
> Author(s)           : P. Francois, Ed., B. Decraene, Ed., C. Pelsser, K.
> Patel, C. Filsfils
> Category            : PROPOSED STANDARD
> Source              : Global Routing Operations
> Area                : Operations and Management
> Stream              : IETF
> Verifying Party     : IESG
>


-- 
I don't think the execution is relevant when it was obviously a bad idea in
the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair of
pants.
   ---maf

Re: [GROW] [Technical Errata Reported] RFC8326 (5… bruno.decraene
Re: [GROW] [Technical Errata Reported] RFC8326 (5… Warren Kumari
[GROW] [Technical Errata Reported] RFC8326 (5402) RFC Errata System