RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

RFC 6512, "Using Multipoint LDP When the Backbone Has No Route to the Root", February 2012

Source of RFC: mpls (rtg)

Errata ID: 6313
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: Alexander Vainshtein
Date Reported: 2020-10-20
Verifier Name: Deborah Brungard
Date Verified: 2021-02-26

Section 3.2.1 says:

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

It should say:

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.

Status: Reported (1)

RFC 6512, "Using Multipoint LDP When the Backbone Has No Route to the Root", February 2012

Source of RFC: mpls (rtg)

Errata ID: 6754
Status: Reported
Type: Technical
Publication Format(s) : TEXT

Reported By: Bert Van Ael
Date Reported: 2021-11-25

Section 3.2.1 says:

PE1 also has this Inter-AS I-PMSI A-D route.

It should say:

PE1 also has this Intra-AS I-PMSI A-D route.

Notes:

"PE1 also has this route" refers to "Although ASBR1 does not have a route to PE2, it does have a BGP Intra-AS Inclusive PMSI (I-PMSI) auto-discovery (A-D) route". Intra-AS mechanisms are used for auto-discovery/binding for Non-Segmented Inter-AS Tunnels.

Report New Errata



Advanced Search