Skip to main content

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

Yes

(Allison Mankin)

No Objection

(David Kessens)
(Margaret Cullen)
(Ted Hardie)

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

(Allison Mankin; former steering group member) Yes

Yes ()

                            

(David Kessens; former steering group member) No Objection

No Objection ()

                            

(Harald Alvestrand; former steering group member) No Objection

No Objection (2004-04-01)
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

No Objection ()

                            

(Russ Housley; former steering group member) No Objection

No Objection (2004-03-30)
  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

No Objection (2004-03-30)
References need normative/informative split.

(Steven Bellovin; former steering group member) No Objection

No Objection (2004-03-29)
       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

No Objection ()