RFC Errata
Found 3 records.
Status: Verified (3)
RFC 2622, "Routing Policy Specification Language (RPSL)", June 1999
Note: This RFC has been updated by RFC 4012, RFC 7909
Source of RFC: rps (ops)
Errata ID: 7564
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Jiang Li
Date Reported: 2023-07-13
Verifier Name: Warren Kumari (Ops AD)
Date Verified: 2024-01-15
Section 5.6 says:
In page 26 of RFC2622 In the following example 9.9.9.1 imports 128.9.0.0/16 from 9.9.9.2 and 9.9.9.3. (7) peering-set: prng-bar peering: AS1 at 9.9.9.1 peering-set: prng-foo peering: prng-bar peering: AS2 at 9.9.9.1 aut-num: AS1 import: from prng-foo accept { 128.9.0.0/16 }
It should say:
In the following example 9.9.9.1 imports 128.9.0.0/16 from 9.9.9.2 and 9.9.9.3. (7) peering-set: prng-bar peering: AS3 at 9.9.9.1 peering-set: prng-foo peering: prng-bar peering: AS2 at 9.9.9.1 aut-num: AS1 import: from prng-foo accept { 128.9.0.0/16 }
Notes:
As "Figure 22: Example topology consisting of three ASes, AS1, AS2, and
AS3; two exchange points, EX1 and EX2; and six routers." shows, the router 9.9.9.1 of AS1 connects to the router 9.9.9.3 of AS3 in exchange point 2. It states that "In the following example 9.9.9.1 imports 128.9.0.0/16 from 9.9.9.2 and 9.9.9.3.", so I think the corresponding AS of 9.9.9.3 should be AS3 instead of AS1.
Errata ID: 6588
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Benjamin Kaduk
Date Reported: 2021-05-20
Verifier Name: Robert Wilton
Date Verified: 2024-01-12
Throughout the document, when it says:
authenticaiton
It should say:
authentication
Notes:
The typo appears in section 3 (twice) and section 3.1 (once)
Errata ID: 8243
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Michael Lambert
Date Reported: 2025-01-06
Verifier Name: RFC Editor
Date Verified: 2025-01-07
Section 5.3 says:
5.3 Predefined Set Objects In a context that expects a route set (e.g. members attribute of the route-set class), an AS number ASx defines the set of routes that are originated by ASx; and an as-set AS-X defines the set of routes that are originated by the ASes in AS-X. A route p is said to be originated by ASx if there is a route object for p with ASx as the value of the origin attribute. For example, in Figure 15, the route set rs-special contains 128.9.0.0/16, routes of AS1 and AS2, and routes of the ASes in AS set AS-FOO. route-set: rs-special members: 128.9.0.0/16, AS1, AS2, AS-FOO Figure 15: Use of AS numbers and AS sets in route sets. The set rs-any contains all routes registered in IRR. The set as-any contains all ASes registered in IRR.
It should say:
In a context that expects a route set (e.g. members attribute of the route-set class), an AS number ASx defines the set of routes that are originated by ASx; and an as-set AS-X defines the set of routes that are originated by the ASes in AS-X. A route p is said to be originated by ASx if there is a route object for p with ASx as the value of the origin attribute. For example, in Figure 15, the route set rs-special contains 128.9.0.0/16, routes of AS1 and AS2, and routes of the ASes in AS set AS-FOO. route-set: rs-special members: 128.9.0.0/16, AS1, AS2, AS-FOO Figure 15: Use of AS numbers and AS sets in route sets. 5.3 Predefined Set Objects The set rs-any contains all routes registered in IRR. The set as-any contains all ASes registered in IRR.
Notes:
The section header for 5.3 is misplaced. It breaks 5.2 (definition and examples of route-set) at a place that does not make sense in context. The section break should be after the caption for Figure 15. The last two sentences (beginning with "The set rs-any") are the only text referring to predefined set objects.