IETF Logo Mail Archive

Re: [mpls] [Technical Errata Reported] RFC3107 (4500)

Alexander Okonnikov <alexander.okonnikov@gmail.com> Fri, 16 October 2015 20:44 UTC

Return-Path: <alexander.okonnikov@gmail.com>
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 3B6661A1A75 for <mpls@ietfa.amsl.com>; Fri, 16 Oct 2015 13:44:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 pmPA8owSkhpJ for <mpls@ietfa.amsl.com>; Fri, 16 Oct 2015 13:44:52 -0700 (PDT)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40D8C1A1A6F for <mpls@ietf.org>; Fri, 16 Oct 2015 13:44:52 -0700 (PDT)
Received: by lbbpp2 with SMTP id pp2so80093459lbb.0 for <mpls@ietf.org>; Fri, 16 Oct 2015 13:44:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=BqL1StJag2Q9GWBjvHvbigX2ysG1bbJrC41hFPIIFKs=; b=b2XaqhLQIZPC5vpODFa/hozre4nQVuGPAqk+zyliNNaCS5EGvMGwxf2Wxewrf1UgnU A+2kNUGL3Mvjgwad6D3cPM+2Nc4RprJ793veZ3viUxDuaJVCeSsveHx0Vz0aiiOxjhTy jXdM6GWofMi061BI+p/1a0xWNxD0ZhZq8qFxx4+ZEV2qPR99umJQAxkk4sMJCvA0b6un FyAzw1vEofZ75JkTk6NNGnhodopZOWp9UZ0gJ9sAZ4FrXdljOfH0AoLypyaJk8ew0tCB tQI6mf75c9Fx8J7HqFbI1tm/WtPRthlzCSezbnN5Df3fIVAAciKoQgvfJiK0Gx/sZsMy rVRQ==
X-Received: by 10.112.133.42 with SMTP id oz10mr9303475lbb.62.1445028290370; Fri, 16 Oct 2015 13:44:50 -0700 (PDT)
Received: from [10.0.1.5] (85-114-21-254.obit.ru. [85.114.21.254]) by smtp.googlemail.com with ESMTPSA id h196sm3161446lfg.21.2015.10.16.13.44.49 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 Oct 2015 13:44:49 -0700 (PDT)
Message-ID: <562161C0.4080603@gmail.com>
Date: Fri, 16 Oct 2015 23:44:48 +0300
From: Alexander Okonnikov <alexander.okonnikov@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.8.0
MIME-Version: 1.0
To: Eric C Rosen <erosen@juniper.net>, RFC Errata System <rfc-editor@rfc-editor.org>, akatlas@gmail.com, db3546@att.com, aretana@cisco.com, loa@pi.nu, swallow@cisco.com, rcallon@juniper.net
References: <20151013221920.C2B7C180206@rfc-editor.org> <56215B73.9020600@juniper.net>
In-Reply-To: <56215B73.9020600@juniper.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/SUt2xvxVIPzFcMHUDEbfaEmX5KA>
Cc: mpls@ietf.org
Subject: Re: [mpls] [Technical Errata Reported] RFC3107 (4500)
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: Fri, 16 Oct 2015 20:44:54 -0000

Understand.

Thank you.

On 10/16/2015 11:17 PM, Eric C Rosen wrote:
> I suspect that this capability code has never actually been used, in 
> which case it might be best to avoid doing anything that might be 
> interpreted as encouraging its use.
>
> On 10/13/2015 6:19 PM, 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=4500
>>
>> --------------------------------------
>> Type: Technical
>> Reported by: Alexander Okonnikov <alexander.okonnikov@gmail.com>
>>
>> Section: 5
>>
>> Original Text
>> -------------
>>     A BGP speaker that is capable of handling multiple routes to a
>>     destination (as described above) should use the Capabilities 
>> Optional
>>     Parameter, as defined in [BGP-CAP], to inform its peers about this
>>     capability.  The value of this capability is 4.
>>
>> Corrected Text
>> --------------
>>     A BGP speaker that is capable of handling multiple routes to a
>>     destination (as described above) should use the Capabilities 
>> Optional
>>     Parameter, as defined in [BGP-CAP], to inform its peers about this
>>     capability.  This capability is advertised using the Capability Code
>>     4 and Capability Length 0.
>>
>> Notes
>> -----
>> To remove confusion what word value means - Capability Value or value 
>> of Capability Code.
>> Also, format of multiple routes capability is not described, so 
>> length = 0 is assumed.
>>
>> 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 mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>

v2.23.0 | Report a Bug | By Email