RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

RFC 5252, "OSPF-Based Layer 1 VPN Auto-Discovery", July 2008

Source of RFC: l1vpn (rtg)

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

Reported By: Alfred Hoenes
Date Reported: 2008-08-15
Verifier Name: Adrian Farrel
Date Verified: 2010-08-20

Section 3.1,1st para says:

{at the end of the first paragraph, line 2 on page 8}

    ... advertised by a specific TE.
                                 ^

It should say:

    ... advertised by a specific PE.
                                 ^

Notes:

distorting typo: TE = Traffic Engineering,
PE = Provider Edge {Router}

Status: Held for Document Update (1)

RFC 5252, "OSPF-Based Layer 1 VPN Auto-Discovery", July 2008

Source of RFC: l1vpn (rtg)

Errata ID: 3310
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT

Reported By: Kris Michielsen
Date Reported: 2012-08-07
Held for Document Update by: Adrian Farrel

Section 2.1 says:

   L1VPN Info TLV
      A single TLV, as defined in Section 3.2, MUST be present.  If more
      than one L1VPN Info TLV is present, only the first TLV is
      processed and the others MUST be ignored on receipt.


It should say:

   L1VPN Info TLV
      A single TLV, as defined in Section 2.2, MUST be present.  If more
      than one L1VPN Info TLV is present, only the first TLV is
      processed and the others MUST be ignored on receipt.


Report New Errata



Advanced Search