IETF Logo Mail Archive

[mpls] [Technical Errata Reported] RFC3107 (2319)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 07 July 2010 15:22 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 04A7A3A67E7 for <mpls@core3.amsl.com>; Wed, 7 Jul 2010 08:22:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J3waMjv0TkW5 for <mpls@core3.amsl.com>; Wed, 7 Jul 2010 08:22:10 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 94F2A3A6812 for <mpls@ietf.org>; Wed, 7 Jul 2010 08:22:09 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 490DEE0677; Wed, 7 Jul 2010 08:22:12 -0700 (PDT)
To: yakov@juniper.net, erosen@cisco.com, stbryant@cisco.com, adrian.farrel@huawei.com, swallow@cisco.com, loa@pi.nu
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20100707152212.490DEE0677@rfc-editor.org>
Date: Wed, 07 Jul 2010 08:22:12 -0700
Cc: rfc-editor@rfc-editor.org, mpls@ietf.org
Subject: [mpls] [Technical Errata Reported] RFC3107 (2319)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 07 Jul 2010 15:22:13 -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=2319

--------------------------------------
Type: Technical
Reported by: Bruno Decraene <bruno.decraene@orange-ftgroup.com>

Section: 5

Original Text
-------------
"A BGP speaker should not advertise this capability to another BGP speaker unless there is a Label Switched Path (LSP) between the two speakers."


Corrected Text
--------------
"An eBGP speaker should not advertise this capability to another eBGP speaker unless there is a Label Switched Path (LSP) or layer two interface between the two speakers."

Or just remove completely that sentence.

Notes
-----
1) :s/BGP/eBGP
An iBGP router should be able to set up an internal BGP session for AFI 1 / SAFI 4 toward a Route Reflector even if the Route Reflector is not capabble of forwarding MPLS packets (This case is even described in the section 2 of the RFC)

2) + layer two interface
If both router are connected by a direct (sub)interface, they should be able to exchange MPLS packets even if there is no LSP between them.

3) Remove the sentence
AFAIK, the point is now better addressed by draft-ietf-idr-bgp-bestpath-selection-criteria-01.txt

Instructions:
-------------
This errata 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

v2.23.0 | Report a Bug | By Email