[mpls] [Technical Errata Reported] RFC3107 (4499)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 13 October 2015 22:05 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D43BB1A1A43 for <mpls@ietfa.amsl.com>; Tue, 13 Oct 2015 15:05:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 oC8GuAcVemG0 for <mpls@ietfa.amsl.com>; Tue, 13 Oct 2015 15:05:39 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0699A1A1A32 for <mpls@ietf.org>; Tue, 13 Oct 2015 15:05:39 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 01C13188CF0; Tue, 13 Oct 2015 15:05:29 -0700 (PDT)
To: yakov@juniper.net, erosen@cisco.com, akatlas@gmail.com, db3546@att.com, aretana@cisco.com, loa@pi.nu, swallow@cisco.com, rcallon@juniper.net
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20151013220529.01C13188CF0@rfc-editor.org>
Date: Tue, 13 Oct 2015 15:05:29 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/PhLRG7HA42qHZUBTw374mQ3zvzI>
Cc: alexander.okonnikov@gmail.com, mpls@ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] [Technical Errata Reported] RFC3107 (4499)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Oct 2015 22:05:41 -0000
The following errata report has been submitted for RFC3107, "Carrying Label Information in BGP-4". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=3107&eid=4499 -------------------------------------- Type: Technical Reported by: Alexander Okonnikov <alexander.okonnikov@gmail.com> Section: 3 Original Text ------------- A BGP speaker can withdraw a previously advertised route (as well as the binding between this route and a label) by either (a) advertising a new route (and a label) with the same NLRI as the previously advertised route, or (b) listing the NLRI of the previously advertised route in the Withdrawn Routes field of an Update message. The label information carried (as part of NLRI) in the Withdrawn Routes field should be set to 0x800000. (Of course, terminating the BGP session also withdraws all the previously advertised routes.) Corrected Text -------------- A BGP speaker can withdraw a previously advertised route (as well as the binding between this route and a label) by either (a) advertising a new route (and a label) with the same NLRI as the previously advertised route, or (b) listing the NLRI of the previously advertised route in the Withdrawn Routes field of an MR_UNREACH_NLRI attribute of an Update message. The label information carried (as part of NLRI) in the Withdrawn Routes field should be set to 0x000001. (Of course, terminating the BGP session also withdraws all the previously advertised routes.) Notes ----- 1. Labeled routes are withdrawn by virtue of MR_UNREACH_NLRI attribute. 2. Label value should be set to 0x00000 with BoS=1. Value 0x800000 was carried from draft, where BoS was high-order bit. 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 (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC3107 (draft-ietf-mpls-bgp4-mpls-04) -------------------------------------- Title : Carrying Label Information in BGP-4 Publication Date : May 2001 Author(s) : Y. Rekhter, E. Rosen Category : PROPOSED STANDARD Source : Multiprotocol Label Switching Area : Routing Stream : IETF Verifying Party : IESG
- [mpls] [Errata Rejected] RFC3107 (4499) RFC Errata System
- [mpls] [Technical Errata Reported] RFC3107 (4499) RFC Errata System
- Re: [mpls] [Technical Errata Reported] RFC3107 (4… Eric C Rosen
- Re: [mpls] [Technical Errata Reported] RFC3107 (4… Alexander Okonnikov
- Re: [mpls] [Technical Errata Reported] RFC3107 (4… Eric C Rosen