RFC Errata
RFC 5059, "Bootstrap Router (BSR) Mechanism for Protocol Independent Multicast (PIM)", January 2008
Note: This RFC has been updated by RFC 8736, RFC 9436
Source of RFC: pim (rtg)See Also: RFC 5059 w/ inline errata
Errata ID: 1321
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-02-14
Verifier Name: Adrian Farrel
Date Verified: 2011-08-18
Section 3.1, 3rd par says:
In a scoped IPv4 BSM, the scope of the message is given by the first group range in the message, which can be any sub-range of 224/4. [...]
It should say:
In a scoped IPv4 BSM, the scope of the message is given by the first | group range in the message, which can be any sub-range of 224.0.0.0/4. [...]
Notes:
Location is 3rd paragraph of Section 3.1, on mid-page 9.
This correction also needs to be applied to "224/4" in the
7th paragraph of Section 3.3, on mid-page 19.
Rationale:
The basic "strategic" document for CIDR notation now is BCP 122,
RFC 4632, and that document clearly states (in section 3.1, at
the bottom of page 5):
vvvvvvv
| [...] In CIDR notation, a prefix is shown as a 4-octet
quantity, just like a traditional IPv4 address or network number,
followed by the "/" (slash) character, followed by a decimal value
between 0 and 32 that describes the number of significant bits.
As a Standards-Track document, RFC 5059 should follow this rule.