Re: [Idr] [Editorial Errata Reported] RFC4271 (6256)

[anton yushkov <[e-mail]>]

Good afternoon.
How can this errata be confirmed or rejected? Do I need any further action,
or will the community of specialists make a decision and report it?

пт, 14 авг. 2020 г. в 17:38, John Scudder <[e-mail]>:

> Sounds right.
>
> —John
>
> > On Aug 12, 2020, at 2:36 PM, RFC Errata System <
> [e-mail]> wrote:
> >
> > [External Email. Be cautious of content]
> >
> >
> > The following errata report has been submitted for RFC4271,
> > "A Border Gateway Protocol 4 (BGP-4)".
> >
> > --------------------------------------
> > You may review the report below and at:
> >
> https://urldefense.com/v3/__https://www.rfc-editor.org/errata/eid6256__;!!NEt6yMaO-gk!SpELvNfLhQUuQ203AvJuTme321r3LEellWBGShISiC4EiRgcaRihajHiLAC-cQ$
> >
> > --------------------------------------
> > Type: Editorial
> > Reported by: Anton Yushkov <[e-mail]>
> >
> > Section: 5.1.3
> >
> > Original Text
> > -------------
> > 3) When sending a message to an external peer X, and the peer is
> > multiple IP hops away from the speaker (aka "multihop EBGP"):
> > ...
> > - By default, the BGP speaker SHOULD use the IP address of the interface
> that the speaker uses in the NEXT_HOP attribute to establish the BGP
> connection to peer X.
> >
> > Corrected Text
> > --------------
> > 3) When sending a message to an external peer X, and the peer is
> > multiple IP hops away from the speaker (aka "multihop EBGP"):
> > ...
> > - By default, the BGP speaker SHOULD use the IP address of the interface
> that the speaker uses to establish the BGP connection to peer X in the
> NEXT_HOP attribute.
> >
> > Notes
> > -----
> > confusing incorrect word order:
> > reading the original text, the reader might think that the BGP speaker
> is using the NEXT_HOP attribute as part of establishing a connection with
> the peer
> >
> > 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.
> >
> > --------------------------------------
> > RFC4271 (draft-ietf-idr-bgp4-26)
> > --------------------------------------
> > Title               : A Border Gateway Protocol 4 (BGP-4)
> > Publication Date    : January 2006
> > Author(s)           : Y. Rekhter, Ed., T. Li, Ed., S. Hares, Ed.
> > Category            : DRAFT STANDARD
> > Source              : Inter-Domain Routing
> > Area                : Routing
> > Stream              : IETF
> > Verifying Party     : IESG
>
>