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

<bruno.decraene@orange.com> Fri, 22 June 2018 07:00 UTC

From: bruno.decraene@orange.com
To: "jgs@juniper.net" <jgs@juniper.net>, "warren@kumari.net" <warren@kumari.net>
CC: "grow@ietf.org" <grow@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>, "pfrpfr@gmail.com" <pfrpfr@gmail.com>, "pelsser@unistra.fr" <pelsser@unistra.fr>, "keyur@arrcus.com" <keyur@arrcus.com>, "cfilsfil@cisco.com" <cfilsfil@cisco.com>, "ibagdona@gmail.com" <ibagdona@gmail.com>, "christopher.morrow@gmail.com" <christopher.morrow@gmail.com>, "job@ntt.net" <job@ntt.net>
Thread-Topic: [Technical Errata Reported] RFC8326 (5402)
Thread-Index: AQHUCZcl04vIiv8siUW8v1Nhh4rapqRr2Jdg
Date: Fri, 22 Jun 2018 07:00:40 +0000
Message-ID: <31151_1529650842_5B2C9E99_31151_204_15_53C29892C857584299CBF5D05346208A47AAB5A6@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <20180621193621.4FB96B811A4@rfc-editor.org>
In-Reply-To: <20180621193621.4FB96B811A4@rfc-editor.org>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/Mu5eui_-HjIciIvQiMBI_aSUIZw>
Subject: Re: [GROW] [Technical Errata Reported] RFC8326 (5402)
Precedence: list

> From: RFC Errata System [mailto:rfc-editor@rfc-editor.org]
> 
 > 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.

Agreed.

Thank you John.

--Bruno

 
 > 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

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

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