RFC 5384, "The Protocol Independent Multicast (PIM) Join Attribute Format", November 2008

Note: This RFC has been updated by RFC 7887

Errata ID: 1597
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-11-17
Verifier Name: Adrian Farrel
Date Verified: 2012-05-08

Section 4, last para says:

   - The encoding type 1 has been allocated, defined as "native encoding
|    for the address family, but with zero or more PIM Join Attributes
     present", and this document is the reference.

It should say:

   - The encoding type 1 has been allocated, defined as "native encoding
|    for the address family, but with one or more PIM Join Attributes
     present", and this document is the reference.

Notes:

Rationale:

Section 3.1 of this RFC says (3rd para):
A type 1 Encoded-Source Address MUST contain at least one Join
Attribute. The way to specify that there are no Join Attributes for
a particular tree is to use the type 0 Encoded-Source Address.

Hence, having *zero* attributes in encoding type 1 is explicitely
forbidden.

Please alse have the IANA registry entry be corrected.

Report New Errata