Re: [mpls] [Technical Errata Reported] RFC6426 (4012)

Eric Gray <eric.gray@ericsson.com> Tue, 10 June 2014 17:51 UTC

From: Eric Gray <eric.gray@ericsson.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>, "nitinb@juniper.net" <nitinb@juniper.net>, "sboutros@cisco.com" <sboutros@cisco.com>, "raggarwa_1@yahoo.com" <raggarwa_1@yahoo.com>, "akatlas@gmail.com" <akatlas@gmail.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "loa@pi.nu" <loa@pi.nu>, "swallow@cisco.com" <swallow@cisco.com>, "rcallon@juniper.net" <rcallon@juniper.net>
Thread-Topic: [Technical Errata Reported] RFC6426 (4012)
Thread-Index: AQHPhNCXWTgc9xmmQk24z+HQvjPXnZtqnuLA
Date: Tue, 10 Jun 2014 17:51:17 +0000
Message-ID: <48E1A67CB9CA044EADFEAB87D814BFF632ADB421@eusaamb107.ericsson.se>
References: <20140610172150.4F1BB1801C0@rfc-editor.org>
In-Reply-To: <20140610172150.4F1BB1801C0@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mpls/VT2ZfVJyWWnO7SPekA-CsHhRL1s
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] [Technical Errata Reported] RFC6426 (4012)
Precedence: list

As a co-author of RFC 6426, I agree that this is an issue that should be fixed, in order to 
avoid a name-space collision.  Already there is a draft that attempts to use the same 
bit for a separate and distinct purpose.

--
Eric

-----Original Message-----
From: RFC Errata System [mailto:rfc-editor@rfc-editor.org] 
Sent: Tuesday, June 10, 2014 1:22 PM
To: Eric Gray; nitinb@juniper.net; sboutros@cisco.com; raggarwa_1@yahoo.com; akatlas@gmail.com; adrian@olddog.co.uk; loa@pi.nu; swallow@cisco.com; rcallon@juniper.net
Cc: Gregory Mirsky; mpls@ietf.org; rfc-editor@rfc-editor.org
Subject: [Technical Errata Reported] RFC6426 (4012)
Importance: High

The following errata report has been submitted for RFC6426, "MPLS On-Demand Connectivity Verification and Route Tracing".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6426&eid=4012

--------------------------------------
Type: Technical
Reported by: Gregory Mirsky <gregory.mirsky@ericsson.com>

Section: 7

Original Text
-------------


Corrected Text
--------------
7.6 New Global Flags Bit

RFC 6425 defines a registry for Global Flags under Multi-Protocol Label Switching (MPLS) Label Switched Path (LSP)  Ping Parameters.

This document defines a new Global Flag, "Validate Reverse Path (R)"
that needs to be added to that registry, as follows:

   Bit number  |  Name                      | Reference
   ------------+----------------------------+--------------
      13       |  Validate Reverse Path     | [RFC 6426]



Notes
-----
"Global Flags" registry was created per request of RFC 6425, not RFC 4379 and did not yet existed when RFC 6426 was published. This "race condition" has to be fixed to avoid possible name-space collision between RFC 6426 and new extensions to LSP ping.

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. 

--------------------------------------
RFC6426 (draft-ietf-mpls-tp-on-demand-cv-07)
--------------------------------------
Title               : MPLS On-Demand Connectivity Verification and Route Tracing
Publication Date    : November 2011
Author(s)           : E. Gray, N. Bahadur, S. Boutros, R. Aggarwal
Category            : PROPOSED STANDARD
Source              : Multiprotocol Label Switching
Area                : Routing
Stream              : IETF
Verifying Party     : IESG

[mpls] [Technical Errata Reported] RFC6426 (4012) RFC Errata System
Re: [mpls] [Technical Errata Reported] RFC6426 (4… Eric Gray
[mpls] [Errata Verified] RFC6426 (4012) RFC Errata System