[Idr] [Errata Verified] RFC5065 (3791)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 16 January 2014 16:05 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DF331AE35F; Thu, 16 Jan 2014 08:05:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level:
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 UJOySW6NZ0pQ; Thu, 16 Jan 2014 08:05:57 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id E57631AE13C; Thu, 16 Jan 2014 08:05:56 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id BA9BC7FC39A; Thu, 16 Jan 2014 08:05:44 -0800 (PST)
To: ramakrishnadtv@infosys.com, bgp-confederations@st04.pst.org, danny@arbor.net, jgs@juniper.net
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140116160544.BA9BC7FC39A@rfc-editor.org>
Date: Thu, 16 Jan 2014 08:05:44 -0800
Cc: idr@ietf.org, rfc-editor@rfc-editor.org, iesg@ietf.org
Subject: [Idr] [Errata Verified] RFC5065 (3791)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 16 Jan 2014 16:05:58 -0000

The following errata report has been verified for RFC5065,
"Autonomous System Confederations for BGP". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5065&eid=3791

--------------------------------------
Status: Verified
Type: Editorial

Reported by: Ramakrishna DTV <ramakrishnadtv@infosys.com>
Date Reported: 2013-11-08
Verified by: Stewart Bryant (IESG)

Section: 7

Original Text
-------------
   Additionally, confederations (as well as route reflectors), by
   excluding different reachability information from consideration at
   different locations in a confederation, have been shown [RFC3345] to
   cause permanent oscillation between candidate routes when using the
   tie-breaking rules required by BGP [BGP-4].

Corrected Text
--------------
   Additionally, confederations (as well as route reflectors), by
   excluding different reachability information from consideration at
   different locations in a confederation, have been shown [RFC3345] to
   cause persistent oscillation between candidate routes when using the
   tie-breaking rules required by BGP [BGP-4].

Notes
-----
s/permanent/persistent

RFC 3345 nowhere refers to this oscillation as "permanent". It consistently refers to it as "persistent" only.

"Permanent" is a much stronger word than "persistent", and I believe is not applicable here.

--------------------------------------
RFC5065 (draft-ietf-idr-rfc3065bis-06)
--------------------------------------
Title               : Autonomous System Confederations for BGP
Publication Date    : August 2007
Author(s)           : P. Traina, D. McPherson, J. Scudder
Category            : DRAFT STANDARD
Source              : Inter-Domain Routing
Area                : Routing
Stream              : IETF
Verifying Party     : IESG