[mpls] Re-sending -Re: [Technical Errata Reported] RFC3107 (4497)
Loa Andersson <loa@pi.nu> Wed, 14 October 2015 09:30 UTC
Return-Path: <loa@pi.nu>
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 4EB1D1B2CC1 for <mpls@ietfa.amsl.com>; Wed, 14 Oct 2015 02:30:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable
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 1GTOhLiXYmVC for <mpls@ietfa.amsl.com>; Wed, 14 Oct 2015 02:30:49 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B598F1B2D3B for <mpls@ietf.org>; Wed, 14 Oct 2015 02:20:28 -0700 (PDT)
Received: from [192.168.1.10] (unknown [112.205.73.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 4149618013BE; Wed, 14 Oct 2015 11:20:22 +0200 (CEST)
To: RFC Errata System <rfc-editor@rfc-editor.org>, Eric C Rosen <erosen@juniper.net>, akatlas@gmail.com, db3546@att.com, aretana@cisco.com, swallow@cisco.com, rcallon@juniper.net
References: <20151013210728.27DF9187E28@rfc-editor.org> <561E1CC9.7080600@pi.nu>
From: Loa Andersson <loa@pi.nu>
Message-ID: <561E1E4E.4070208@pi.nu>
Date: Wed, 14 Oct 2015 17:20:14 +0800
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <561E1CC9.7080600@pi.nu>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/MRwjNyC1U5-yKtPkPu55jbg3Y7o>
Cc: alexander.okonnikov@gmail.com, mpls@ietf.org
Subject: [mpls] Re-sending -Re: [Technical Errata Reported] RFC3107 (4497)
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: Wed, 14 Oct 2015 09:30:55 -0000
Folks, I'm re-sending this because Eric's mail address was wrong. SOory for those of you that got duplicates, but better duplicates than none at all. /Loa On 2015-10-14 17:13, Loa Andersson wrote: > Folks, (I removed Yacov, since hie mail address is no longer working), > > I think this errata is > - first of minor importance and could be held for a future update > of RFC 3107 > - second the errata is at the core correct > - third I'm not happy with the proposed new text > > I think it should be: > > NEW - first alternative > ----------------------- > Label distribution can be piggybacked in the BGP Update message by > using the BGP-4 Multiprotocol Extensions attribute defined in > RFC 2858 [BGP-MP]. > > Note: > RFC 2858 obsoletes RFC 2283, so the text above reflects the situation > as it was when 3107 were written. This correctly captured in the > RFC archives and will be found even we only have the original text. > But it would have been no harm doing this updates, if the documentation > had not changed. RFC 2858 has later been obsoleted by RFC 4760, which in > turn has been updated by RFC 7606. > > So I'm a bit undecided what to do about this, given that an update will > take place in the time it is done, I believe that the corrected text > should be: > > NEW - preferred alternative > --------------------------- > Label distribution can be piggybacked in the BGP Update message by > using the BGP-4 Multiprotocol Extensions attribute defined in > RFC 4760 [BGP-MP]. > > Caveat: This requires an update to the [BGP-MP] in the reference > section at the same time. > > Any opinions? > > /Loa > > On 2015-10-14 05:07, RFC Errata System wrote: >> 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=4497 >> >> -------------------------------------- >> Type: Technical >> Reported by: Alexander Okonnikov <alexander.okonnikov@gmail.com> >> >> Section: 2 >> >> Original Text >> ------------- >> Label distribution can be piggybacked in the BGP Update message by >> using the BGP-4 Multiprotocol Extensions attribute [RFC 2283]. >> >> Corrected Text >> -------------- >> Label distribution can be piggybacked in the BGP Update message by >> using the BGP-4 Multiprotocol Extensions attribute [BGP-MP]. >> >> Notes >> ----- >> No such reference [RFC 2283] in References section. Also document >> refers to newer version of BGP-MP (RFC 2858). >> >> 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] [Technical Errata Reported] RFC3107 (4497) RFC Errata System
- Re: [mpls] [Technical Errata Reported] RFC3107 (4… Loa Andersson
- [mpls] Re-sending -Re: [Technical Errata Reported… Loa Andersson
- Re: [mpls] [Technical Errata Reported] RFC3107 (4… Andrew G. Malis
- Re: [mpls] [Technical Errata Reported] RFC3107 (4… Andrew G. Malis
- Re: [mpls] [Technical Errata Reported] RFC3107 (4… Loa Andersson
- Re: [mpls] [Technical Errata Reported] RFC3107 (4… Stewart Bryant
- Re: [mpls] [Technical Errata Reported] RFC3107 (4… Alexander Okonnikov
- Re: [mpls] [Technical Errata Reported] RFC3107 (4… Martin Vigoureux
- Re: [mpls] [Technical Errata Reported] RFC3107 (4… Loa Andersson
- 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… Loa Andersson
- Re: [mpls] [Technical Errata Reported] RFC3107 (4… Eric C Rosen
- Re: [mpls] [Technical Errata Reported] RFC3107 (4… Ross Callon
- Re: [mpls] [Technical Errata Reported] RFC3107 (4… Loa Andersson
- Re: [mpls] [Technical Errata Reported] RFC3107 (4… l.wood
- Re: [mpls] [Technical Errata Reported] RFC3107 (4… Loa Andersson
- Re: [mpls] [Technical Errata Reported] RFC3107 (4… l.wood
- [mpls] [Errata Verified] RFC3107 (4497) RFC Errata System