Found 2 records.

Status: Verified (2)

RFC 6368, "Internal BGP as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)", September 2011

Note: This RFC has been updated by RFC 7606, RFC 9494

Errata ID: 4309
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Guillaume Gaulon
Date Reported: 2015-03-20
Verifier Name: Alia Atlas
Date Verified: 2015-04-09

Section 7 says:

   In the traditional model, where External BGP sessions are used
   between the BGP/MPLS VPN PE and CE, the PE router identifies itself
   as belonging to the customer network autonomous system.

It should say:

   In the traditional model, where External BGP sessions are used
   between the BGP/MPLS VPN PE and CE, the PE router identifies itself
   as belonging to the provider network autonomous system.

Errata ID: 7834
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Hugues Le Bastard
Date Reported: 2024-03-01
Verifier Name: John Scudder
Date Verified: 2024-03-07

Section 5 says:

Using this mechanism isolates the customer network from the
attributes used in the customer network and vice versa.  Attributes
such as the route reflection cluster list attribute are segregated
such that customer network cluster identifiers won't be considered by
the customer network route reflectors and vice versa.

It should say:

Using this mechanism isolates the customer network from the
attributes used in the provider network and vice versa.  Attributes
such as the route reflection cluster list attribute are segregated
such that customer network cluster identifiers won't be considered by
the provider network route reflectors and vice versa.

Notes:

"customer network" is used twice instead of "provider network"

Report New Errata