RFC Errata
Found 1 record.
Status: Held for Document Update (1)
RFC 7115, "Origin Validation Operation Based on the Resource Public Key Infrastructure (RPKI)", January 2014
Source of RFC: sidr (rtg)
Errata ID: 4973
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Tassos Chatzithomaoglou
Date Reported: 2017-03-18
Held for Document Update by: Alvaro Retana
Date Held: 2017-03-25
Section 3 & 5 says:
section 3 --------- For example, if, instead of 10.0.0.0/16-24, one issues 10.0.0.0/16 and 10.0.42.0/24, a forged origin attack cannot succeed against 10.0.666.0/24. section 5 --------- Consider having a ROA for AS 42 for prefix 10.0.0.0/16-24. A BGP announcement for 10.0.666.0/24 from AS 666 would be Invalid
It should say:
section 3 --------- For example, if, instead of 10.0.0.0/16-24, one issues 10.0.0.0/16 and 10.0.42.0/24, a forged origin attack cannot succeed against 10.0.66.0/24. section 5 --------- Consider having a ROA for AS 42 for prefix 10.0.0.0/16-24. A BGP announcement for 10.0.66.0/24 from AS 666 would be Invalid
Notes:
666 is not a valid octet for an ipv4 address
===
I am marking this report as "Held for Document Update" [1], which means that the author might consider its merits for a future update. If the use of the "666" octet was intentional, then a short note explaining might be appropriate to avoid further confusion.
- Alvaro.
[1] https://www.ietf.org/iesg/statement/errata-processing.html