Subject: [mpls] [Editorial Errata Reported] RFC6512 (6313)

From: RFC Errata System <[email-masked]>
Date: Tue, 20 Oct 2020 02:49:45 -0700 (PDT)

The following errata report has been submitted for RFC6512,
"Using Multipoint LDP When the Backbone Has No Route to the Root".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6313

--------------------------------------
Type: Editorial
Reported by: Alexander Vainshtein <[email-masked]>

Section: 3.2.1

Original Text
-------------
Since P1 has no root to PE2, PE1 needs to originate an mLDP message with a FEC element that identifies ASBR1 as the root.

Corrected Text
--------------
Since P1 has no route to PE2, PE1 needs to originate an mLDP message with a FEC element that identifies ASBR1 as the root.

Notes
-----
"no root to PE2" does not parse and looks as a typo. 
And it is quite clear from the context that "no route to PE2" is intended.

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  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6512 (draft-ietf-mpls-mldp-recurs-fec-04)
--------------------------------------
Title               : Using Multipoint LDP When the Backbone Has No Route to the Root
Publication Date    : February 2012
Author(s)           : IJ. Wijnands, E. Rosen, M. Napierala, N. Leymann
Category            : PROPOSED STANDARD
Source              : Multiprotocol Label Switching
Area                : Routing
Stream              : IETF
Verifying Party     : IESG