[mpls] Opinion sort: [Technical Errata Reported] RFC3107 (2319)

Adrian Farrel <Adrian.Farrel@huawei.com> Thu, 19 August 2010 12:23 UTC

Return-Path: <Adrian.Farrel@huawei.com>
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 54B073A68E1 for <mpls@core3.amsl.com>; Thu, 19 Aug 2010 05:23:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.36
X-Spam-Level:
X-Spam-Status: No, score=-102.36 tagged_above=-999 required=5 tests=[AWL=0.238, BAYES_00=-2.599, STOX_REPLY_TYPE=0.001, USER_IN_WHITELIST=-100]
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 lCHb+lWQHrAA for <mpls@core3.amsl.com>; Thu, 19 Aug 2010 05:23:13 -0700 (PDT)
Received: from usaga03-in.huawei.com (usaga03-in.huawei.com [206.16.17.220]) by core3.amsl.com (Postfix) with ESMTP id 570563A68B0 for <mpls@ietf.org>; Thu, 19 Aug 2010 05:23:13 -0700 (PDT)
Received: from huawei.com (usaga03-in [172.18.4.17]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L7E00BE1FRNJW@usaga03-in.huawei.com> for mpls@ietf.org; Thu, 19 Aug 2010 07:23:48 -0500 (CDT)
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L7E00KOEFRL93@usaga03-in.huawei.com> for mpls@ietf.org; Thu, 19 Aug 2010 07:23:47 -0500 (CDT)
Date: Thu, 19 Aug 2010 13:23:40 +0100
From: Adrian Farrel <Adrian.Farrel@huawei.com>
To: Yakov Rekhter <yakov@juniper.net>, Eric Rosen <erosen@cisco.com>
Message-id: <563FC961F0064F8BAB96729A972786DE@your029b8cecfe>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
References: <20100707152212.490DEE0677@rfc-editor.org>
Cc: mpls@ietf.org
Subject: [mpls] Opinion sort: [Technical Errata Reported] RFC3107 (2319)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <Adrian.Farrel@huawei.com>
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: Thu, 19 Aug 2010 12:23:14 -0000

Hi,

Can I have the authors'  and WG's opinion on Bruno's comments, please.

Point 1 seems reasonable to me.
Point 2 feels like a bit of  semantic issue. If MPLS packets can be
exchanged, is there not an LSP by definition?
Removing the sentence (as in Point 3) would require adding the reference,
etc. and that is a mess better handled by the new draft "updating" the RFC.

Thoughts?

Thanks,
Adrian
----- Original Message ----- 
From: "RFC Errata System" <rfc-editor@rfc-editor.org>
To: <yakov@juniper.net>; <erosen@cisco.com>; <stbryant@cisco.com>;
<adrian.farrel@huawei.com>; <swallow@cisco.com>; <loa@pi.nu>
Cc: <rfc-editor@rfc-editor.org>; <mpls@ietf.org>
Sent: Wednesday, July 07, 2010 4:22 PM
Subject: [mpls] [Technical Errata Reported] RFC3107 (2319)


>
> 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
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>