Re: [mpls] [Editorial Errata Reported] RFC6669 (3392)

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 24 October 2012 15:20 UTC

From: Adrian Farrel <adrian@olddog.co.uk>
To: mpls@ietf.org
References: <20121024102523.2FC9D72E038@rfc-editor.org>
In-Reply-To: <20121024102523.2FC9D72E038@rfc-editor.org>
Date: Wed, 24 Oct 2012 16:20:05 +0100
Message-ID: <12a001cdb1fb$0c287ca0$247975e0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AQHT+D4Xc1gYExVkgAT3QfEbqc6qxJe8BTSw
Content-Language: en-gb
Subject: Re: [mpls] [Editorial Errata Reported] RFC6669 (3392)
Precedence: list
Reply-To: adrian@olddog.co.uk

Hi,

Nurit reported to me that she had made a mistake in entering the correct details
in the Errata system.
I have fixed the report which you can see at
http://www.rfc-editor.org/errata_search.php?rfc=6669&eid=3392

I believe the report is correct and plan to approve it.

Comments welcome.

Adrian

> -----Original Message-----
> From: RFC Errata System [mailto:rfc-editor@rfc-editor.org]
> Sent: 24 October 2012 11:25
> To: nurit.sprecher@nsn.com; lufang@cisco.com; stbryant@cisco.com;
> adrian@olddog.co.uk; loa@pi.nu; swallow@cisco.com; rcallon@juniper.net
> Cc: nurit.sprecher@nsn.com; mpls@ietf.org; rfc-editor@rfc-editor.org
> Subject: [Editorial Errata Reported] RFC6669 (3392)
> 
> 
> The following errata report has been submitted for RFC6669,
> "An Overview of the Operations, Administration, and Maintenance (OAM)
> Toolset for MPLS-Based Transport Networks".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=6669&eid=3392
> 
> --------------------------------------
> Type: Editorial
> Reported by: Nurit Sprecher <nurit.sprecher@nsn.com>
> 
> Section: 4
> 
> Original Text
> -------------
>   +------------------------+---------------------------------+---------+
>   | Lock Instruct (LI)     | (1) G-ACh-based Loopback,       |[RFC6426]|
>   |                        | (2) Lock Instruct (LI)          |         |
>   +------------------------+---------------------------------+---------+
>   | Lock Report (LKR)      | Flag in AIS message             |[RFC6426]|
> 
> 
> Corrected Text
> --------------
>    +------------------------+---------------------------------+--------+
>    | Diagnostic: Loopback   | (1) G-ACh based Loopback and    | [RFC   |
>    | and Lock Instruct      | Lock Instruct, (2) LSP Ping     | 6435]  |
>    +------------------------+---------------------------------+--------+
>    | Lock Instruct(LI)      | Flag in MPLS Fault Management   | [RFC   |
>    |                        | message                         | 6427]  |
> 
> 
> Notes
> -----
> The RFC numbers were correct in version latest draft version (9), and
obviously it
> is an editing mistake.
> 
> 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.
> 
> --------------------------------------
> RFC6669 (draft-ietf-mpls-tp-oam-analysis-09)
> --------------------------------------
> Title               : An Overview of the Operations, Administration, and
Maintenance
> (OAM) Toolset for MPLS-Based Transport Networks
> Publication Date    : July 2012
> Author(s)           : N. Sprecher, L. Fang
> Category            : INFORMATIONAL
> Source              : Multiprotocol Label Switching
> Area                : Routing
> Stream              : IETF
> Verifying Party     : IESG

[mpls] [Editorial Errata Reported] RFC6669 (3392) RFC Errata System
Re: [mpls] [Editorial Errata Reported] RFC6669 (3… Sprecher, Nurit (NSN - IL/Hod HaSharon)
Re: [mpls] [Editorial Errata Reported] RFC6669 (3… Adrian Farrel