[mpls] [Errata Verified] RFC3107 (4498)
RFC Errata System <rfc-editor@rfc-editor.org> Thu, 11 February 2016 23:29 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 C1FD61B3C54; Thu, 11 Feb 2016 15:29:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.903
X-Spam-Level:
X-Spam-Status: No, score=-101.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 WxvW1SR8qW7v; Thu, 11 Feb 2016 15:29:14 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04CEF1B3C52; Thu, 11 Feb 2016 15:29:14 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 5C72118046B; Thu, 11 Feb 2016 15:28:35 -0800 (PST)
To: alexander.okonnikov@gmail.com, yakov@juniper.net, erosen@cisco.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20160211232835.5C72118046B@rfc-editor.org>
Date: Thu, 11 Feb 2016 15:28:35 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/EtJncLm_9X8Z135z1FLPYqgRjfw>
Cc: mpls@ietf.org, iesg@ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] [Errata Verified] RFC3107 (4498)
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: Thu, 11 Feb 2016 23:29:17 -0000
The following errata report has been verified 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=4498 -------------------------------------- Status: Verified Type: Technical Reported by: Alexander Okonnikov <alexander.okonnikov@gmail.com> Date Reported: 2015-10-13 Verified by: Deborah Brungard (IESG) Section: 3 Original Text ------------- The label(s) specified for a particular route (and associated with its address prefix) must be assigned by the LSR which is identified by the value of the Next Hop attribute of the route. When a BGP speaker redistributes a route, the label(s) assigned to that route must not be changed (except by omission), unless the speaker changes the value of the Next Hop attribute of the route. Corrected Text -------------- The label(s) specified for a particular route (and associated with its address prefix) must be assigned by the LSR which is identified by the value of the Network Address of Next Hop field of MP_REACH_NLRI attribute of the route. When a BGP speaker redistributes a route, the label(s) assigned to that route must not be changed (except by omission), unless the speaker changes the value of the Network Address of Next Hop field of MP_REACH_NLRI attribute of the route. Notes ----- Next Hop address for labeled routes is conveyed within MP_REACH_NLRI attribute. -------------------------------------- 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 Verified] RFC3107 (4498) RFC Errata System
- [mpls] [Technical Errata Reported] RFC3107 (4498) RFC Errata System