Multicast Security (MSEC) Group Key Management Architecture
draft-ietf-msec-gkmarch-08
Yes
(Russ Housley)
No Objection
(Alex Zinin)
(Bert Wijnen)
(Margaret Cullen)
(Steven Bellovin)
(Ted Hardie)
No Record
(David Kessens)
Note: This ballot was opened for revision 08 and is now closed.
Russ Housley Former IESG member
Yes
Yes
()
Unknown
Alex Zinin Former IESG member
No Objection
No Objection
()
Unknown
Allison Mankin Former IESG member
(was Discuss)
No Objection
No Objection
(2004-11-12)
Unknown
Cleared based on Russ's RFC Editor note
Bert Wijnen Former IESG member
No Objection
No Objection
()
Unknown
Margaret Cullen Former IESG member
No Objection
No Objection
()
Unknown
Scott Hollenbeck Former IESG member
No Objection
No Objection
(2004-06-25)
Unknown
The "Comments on this document should be sent to msec@securemulticast.org" text at the end of the abstract should be removed. Section 5.5 The "If all or even many members contact the GCKS at about the same time, the GCKS cannot handle all those messages" text sounds too absolute to me because there are ways to provide reliable service with load balancing, fast processors, etc. It might be better phrased as "If all or even many members contact the GCKS at about the same time, there is a risk that the GCKS will be unable to process all of the messages". This could also be addressed in section 7. References should be split normative/informative.
Steven Bellovin Former IESG member
No Objection
No Objection
()
Unknown
Ted Hardie Former IESG member
No Objection
No Objection
()
Unknown
David Kessens Former IESG member
(was No Objection)
No Record
No Record
()
Unknown