[Idr] [Errata Rejected] RFC4456 (3898)
RFC Errata System <rfc-editor@rfc-editor.org> Sun, 02 March 2014 10:34 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 9FBB11A0C41; Sun, 2 Mar 2014 02:34:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, 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 NHPJY5DxzuX3; Sun, 2 Mar 2014 02:34:49 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 5A2551A0C97; Sun, 2 Mar 2014 02:34:49 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id C43E87FC3A5; Sun, 2 Mar 2014 02:34:46 -0800 (PST)
To: guban@microsoft.com, tbates@cisco.com, enkechen@cisco.com, rchandra@sonoasystems.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140302103446.C43E87FC3A5@rfc-editor.org>
Date: Sun, 02 Mar 2014 02:34:46 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/idr/AfRMdN5-NM53Z5F2w2BOk-kD5MQ
Cc: idr@ietf.org, rfc-editor@rfc-editor.org, iesg@ietf.org
Subject: [Idr] [Errata Rejected] RFC4456 (3898)
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: Sun, 02 Mar 2014 10:34:51 -0000
The following errata report has been rejected for RFC4456, "BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=4456&eid=3898 -------------------------------------- Status: Rejected Type: Technical Reported by: Gunjan Bansal <guban@microsoft.com> Date Reported: 2014-02-23 Rejected by: Stewart Bryant (IESG) Section: 8 Original Text ------------- ORIGINATOR_ID ORIGINATOR_ID is a new optional, non-transitive BGP attribute of Type code 9. This attribute is 4 bytes long and it will be created by an RR in reflecting a route. This attribute will carry the BGP Identifier of the originator of the route in the local AS. A BGP speaker SHOULD NOT create an ORIGINATOR_ID attribute if one already exists. A router that recognizes the ORIGINATOR_ID attribute SHOULD ignore a route received with its BGP Identifier as the ORIGINATOR_ID. CLUSTER_LIST CLUSTER_LIST is a new, optional, non-transitive BGP attribute of Type code 10. It is a sequence of CLUSTER_ID values representing the reflection path that the route has passed. When an RR reflects a route, it MUST prepend the local CLUSTER_ID to the CLUSTER_LIST. If the CLUSTER_LIST is empty, it MUST create a new one. Using this attribute an RR can identify if the routing information has looped back to the same cluster due to misconfiguration. If the local CLUSTER_ID is found in the CLUSTER_LIST, the advertisement received SHOULD be ignored. Corrected Text -------------- Notes ----- Although the guideline exists for the "egress" reflected routes (RR should create ORIGINATOR_ID if none exists, prepend its own ClusterId in CLUSTER_LIST), there is no guideline on how the routes received from iBGP peers be treated if "only one" attribute (ORIGINATOR_ID or CLUSTER_LIST) is present. Should such routes be dropped (Considering them as a malformed routes ?) --VERIFIER NOTES-- This is a question that should be addressed to the IDR WG. Any new guideline that results should be considered for publication in an RFC. Technical changes of the type requested are outside the scope of the Errata process. -------------------------------------- RFC4456 (draft-ietf-idr-rfc2796bis-02) -------------------------------------- Title : BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP) Publication Date : April 2006 Author(s) : T. Bates, E. Chen, R. Chandra Category : DRAFT STANDARD Source : Inter-Domain Routing Area : Routing Stream : IETF Verifying Party : IESG
- [Idr] [Technical Errata Reported] RFC4456 (3898) RFC Errata System
- [Idr] [Errata Rejected] RFC4456 (3898) RFC Errata System