I have reviewed this document as part of the security directorate's

ongoing effort to review all IETF documents being processed by the

IESG.  Document editors and WG chairs should treat these comments just

like any other last call comments.

This short draft provides instructions for an IANA  registry for Protocol Independent Multicast (PIM) message types.  There is currently no such registry, and there

are already several RFCs specifying PIM message types that should be included.  The document gives the initial content of the

registry based on these RFCs, as well as a new type which is reserved for the extension of type space.

The authors not that other than the possible security benefits of having one place where the various PIM message types can

be found, there are no security considerations.  I agree with them, and so don't have anything further to add.

 




Catherine Meadows

Naval Research Laboratory

Code 5543

4555 Overlook Ave., S.W.

Washington DC, 20375

phone: 202-767-3490

fax: 202-404-7942

email: 

catherine.meadows at nrl.navy.mil