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

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 12 August 2020 18:36 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E1E53A0772 for <idr@ietfa.amsl.com>; Wed, 12 Aug 2020 11:36:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kRK9y5yKXobE for <idr@ietfa.amsl.com>; Wed, 12 Aug 2020 11:36:36 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60BBC3A0747 for <idr@ietf.org>; Wed, 12 Aug 2020 11:36:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4079DF40752; Wed, 12 Aug 2020 11:36:30 -0700 (PDT)
To: yakov@juniper.net, tony.li@tony.li, skh@nexthop.com, db3546@att.com, aretana.ietf@gmail.com, martin.vigoureux@nokia.com, jgs@juniper.net, shares@ndzh.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: antonyyushkov@gmail.com, idr@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20200812183630.4079DF40752@rfc-editor.org>
Date: Wed, 12 Aug 2020 11:36:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/i23PiyFC3yAP8SD1xbKvig5WwW8>
X-Mailman-Approved-At: Fri, 14 Aug 2020 07:34:04 -0700
Subject: [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: Wed, 12 Aug 2020 18:36:37 -0000

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://www.rfc-editor.org/errata/eid6256

--------------------------------------
Type: Editorial
Reported by: Anton Yushkov <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