Negative-Acknowledgment (NACK)-Oriented Reliable Multicast (NORM) Building Blocks
RFC 3941
Yes
No Objection
Note: This ballot was opened for revision 09 and is now closed.
(Allison Mankin; former steering group member) Yes
(David Kessens; former steering group member) No Objection
(Harald Alvestrand; former steering group member) No Objection
Reviewed by Brian Carpenter, Gen-ART. Nits need checking. MUST used and not defined. No Table of Contents. No copyright boilerplate. No IANA Considerations. pi-norm defines a 4-bit field and assigns some values to it. Shouldn't all these be IANA maintained?
(Margaret Cullen; former steering group member) No Objection
(Russ Housley; former steering group member) No Objection
Both documents contain some lines that are too long. Please change "IPSEC" to "IPsec" throughout draft-ietf-rmt-bb-norm-08.
(Scott Hollenbeck; former steering group member) No Objection
References need normative/informative split.
(Steven Bellovin; former steering group member) No Objection
60 pages and no ToC
Security: NORM sequence id can only be used to detect replay if
cryptographically protected
(Ted Hardie; former steering group member) No Objection