Negative-acknowledgment (NACK)-Oriented Reliable Multicast (NORM) Protocol
RFC 3940

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

(Allison Mankin) Yes

(Harald Alvestrand) No Objection

Comment (2004-04-01 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
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?

(Steven Bellovin) No Objection

Comment (2004-03-29 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
       60 pages and no ToC
        Security: NORM sequence id can only be used to detect replay if
                cryptographically protected

(Margaret Cullen) No Objection

(Ted Hardie) No Objection

(Scott Hollenbeck) No Objection

Comment (2004-03-30 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
References need normative/informative split.

(Russ Housley) No Objection

Comment (2004-03-30 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
  Both documents contain some lines that are too long.

  Please change "IPSEC" to "IPsec" throughout draft-ietf-rmt-bb-norm-08.

(David Kessens) No Objection