RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

RFC 5123, "Considerations in Validating the Path in BGP", February 2008

Source of RFC: INDEPENDENT
See Also: RFC 5123w/ inline errata

Errata ID: 1366
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Alfred Hoenes
Date Reported: 2008-03-13
Verifier Name: Nevil Brownlee
Date Verified: 2012-11-05

Section 1.,last para says:

   Assume a BGP speaker in AS65002 has received an advertisement for
|  10.1.1.0/24 from a BGP speaker in AS65001, with an AS Path of {65000,
|  65001}.

It should say:

   Assume a BGP speaker in AS65002 has received an advertisement for
|  10.1.1.0/24 from a BGP speaker in AS65001, with an AS Path of {65001,
|  65000}.

Notes:

Rationale:
AS Path presentation should consistently follow the common
practice for BGP-4.
RFC 5123 mixes standard and reversed AS Path notation.
To avoid confusion, all reversed AS Path notations should
be corrected.

For clarity, further instances of this issue in Sections 1.2,
1.4, and 2.2 are addressed in separate Errata Notes.

Report New Errata