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

John Scudder <jgs@juniper.net> Tue, 18 August 2020 17:10 UTC

From: John Scudder <jgs@juniper.net>
To: anton yushkov <antonyyushkov@gmail.com>
CC: "idr@ietf. org" <idr@ietf.org>, "tony.li@tony.li" <tony.li@tony.li>, "BRUNGARD, DEBORAH A" <db3546@att.com>, Alvaro Retana <aretana.ietf@gmail.com>, "Vigoureux, Martin (Nokia - FR/Paris-Saclay)" <martin.vigoureux@nokia.com>, Hares Susan <shares@ndzh.com>
Thread-Topic: [Editorial Errata Reported] RFC4271 (6256)
Thread-Index: AQHWcNeFeZzbazTbmkKM/se8wJIvx6k3r4GAgAZyXICAAAF5Ww==
Date: Tue, 18 Aug 2020 17:10:45 +0000
Message-ID: <96178AD2-9AC7-405F-82BB-CAB8404D4284@juniper.net>
References: <20200812183630.4079DF40752@rfc-editor.org> <053CBA33-3347-4074-92E2-9FE9DA8FD92B@juniper.net>, <CAAQzaWPRe-D7ZdrC2WCjbVJMFPrxcB7L8_1RQMxQ_Di4wfhM5Q@mail.gmail.com>
In-Reply-To: <CAAQzaWPRe-D7ZdrC2WCjbVJMFPrxcB7L8_1RQMxQ_Di4wfhM5Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_96178AD29AC7405F82BBCAB8404D4284junipernet_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b49eecd8-cc70-4f25-807f-08d84399a5a7
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Aug 2020 17:10:45.9871 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: co9ADxeJfxydMM7TbD+d8Cf6whrbBxADFsFUEz8nFjoJzJaKlY3XxMWTYmGNqwwy
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR05MB4945
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-08-18_11:2020-08-18, 2020-08-18 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 mlxscore=0 bulkscore=0 malwarescore=0 phishscore=0 suspectscore=0 impostorscore=0 adultscore=0 lowpriorityscore=0 clxscore=1015 priorityscore=1501 spamscore=0 mlxlogscore=999 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2006250000 definitions=main-2008180120
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Mk_CK8O3M8qW2e7W4YOJQSpAkBY>
Subject: Re: [Idr] [Editorial Errata Reported] RFC4271 (6256)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Aug 2020 17:10:56 -0000

In due course of time, the Area Director responsible for IDR (Alvaro) will accept or reject it. I anticipate he’ll accept it, but it’s up to him.

—John

On Aug 18, 2020, at 1:05 PM, anton yushkov <antonyyushkov@gmail.com> wrote:



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 <jgs@juniper.net<mailto:jgs@juniper.net>>:
Sounds right.

—John

> On Aug 12, 2020, at 2:36 PM, RFC Errata System <rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>> 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 <antonyyushkov@gmail.com<mailto:antonyyushkov@gmail.com>>
>
> 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

[Idr] [Editorial Errata Reported] RFC4271 (6256) RFC Errata System
Re: [Idr] [Editorial Errata Reported] RFC4271 (62… John Scudder
Re: [Idr] [Editorial Errata Reported] RFC4271 (62… John Scudder
Re: [Idr] [Editorial Errata Reported] RFC4271 (62… anton yushkov
Re: [Idr] [Editorial Errata Reported] RFC4271 (62… Alvaro Retana