Skip to main content

Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised)
draft-ietf-pim-dm-new-v2-05

Yes

(Alex Zinin)

No Objection

(Allison Mankin)
(Russ Housley)
(Ted Hardie)

Note: This ballot was opened for revision 05 and is now closed.

(Alex Zinin; former steering group member) Yes

Yes ()

                            

(Allison Mankin; former steering group member) No Objection

No Objection ()

                            

(Bert Wijnen; former steering group member) No Objection

No Objection (2004-01-20)
From OPS Directorate (Pekka):

One question/comment:

6.  IANA Considerations
6.1.  PIM Address Family
6.2.  PIM Hello Options

==> this specification defines PIM AF/Hello options which affect all
the PIM protocols (including PIM-SM). Is this the appropriate place to
do so (at least, if it is, I guess it should be explicitly called out
in the section, and noted in the other PIM specs as well..)?  At
least, the PIM-SM revised spec includes about the same text again --
you can't do the allocations twice, at least.. :-)

nits:
 - split refs
 - add ipr etc. sections

(Ned Freed; former steering group member) No Objection

No Objection (2004-01-18)
Nits: No copyright or IPR boilerplate, references need separating

(Russ Housley; former steering group member) (was Discuss) No Objection

No Objection ()

                            

(Steven Bellovin; former steering group member) No Objection

No Objection (2004-01-20)
Since when is set union non-commutativ (section 2.2)?  If it is non-commutative here, it shouldn't be called set union, or the reason for the difference should be explained.

The IPsec section of the security considerations is quite vague; it doesn't really say what has to be supported.  It also doesn't take msec into account.

(Ted Hardie; former steering group member) No Objection

No Objection ()