RFC Errata
RFC 5384, "The Protocol Independent Multicast (PIM) Join Attribute Format", November 2008
Note: This RFC has been updated by RFC 7887
Source of RFC: pim (rtg)
Errata ID: 1599
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-11-17
Held for Document Update by: Adrian Farrel
Section 3.2,1st para says:
To ensure that a type 1 Encoded-Source Address is not sent to a PIM neighbor that does not understand this encoding, a new PIM Hello option, the "Join Attribute" option, is defined. This option MUST be included in the PIM Hellos of any PIM router that is willing to | receive type 1 Encoded-Source Address. A PIM router MUST NOT send a ^ type 1 Encoded-Source Address out any interface on which there is a PIM neighbor that has not included this option in its Hellos. (Even | a router that is not the upstream neighbor must be able parse the ^ packet in order to do Join suppression or overriding.)
It should say:
To ensure that a type 1 Encoded-Source Address is not sent to a PIM neighbor that does not understand this encoding, a new PIM Hello option, the "Join Attribute" option, is defined. This option MUST be included in the PIM Hellos of any PIM router that is willing to | receive type 1 Encoded-Source Addresses. A PIM router MUST NOT send ^^^ a type 1 Encoded-Source Address out any interface on which there is a PIM neighbor that has not included this option in its Hellos. (Even | a router that is not the upstream neighbor must be able to parse the ^^^^ packet in order to do Join suppression or overriding.)
Notes:
Rationale: Grammar flawed.