Subject: [Idr] [Errata Held for Document Update] RFC4271 (6256)

From: RFC Errata System <[email-masked]>
Date: Tue, 18 Aug 2020 11:00:53 -0700 (PDT)

The following errata report has been held for document update 
for RFC4271, "A Border Gateway Protocol 4 (BGP-4)". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6256

--------------------------------------
Status: Held for Document Update
Type: Editorial

Reported by: Anton Yushkov <[email-masked]>
Date Reported: 2020-08-12
Held by: Alvaro Retana (IESG)

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

--------------------------------------
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