Draft: draft-ietf-msec-gkmarch-08.txt
Reviewer: Lucy Lynch
Date: 9 July 2004

NO objection as informational

Proving, once again, that multicast is easy ;-)

"MSEC key management protocols may be used to facilitate secure one-to-
 many, many-to-many, or one-to-one communication."

I take one-to-one is covered in the interest of completeness?

NITS

- I found no iana considerations section
- idnits 1.31 (30 May 2004) draft-ietf-msec-gkmarch-08.txt:

  * The document claims conformance with section 10 of RFC 2026, but uses
    some RFC 3667/3668 boilerplate.  As RFC 3667/3668 replaces section 10
    of RFC 2026, you should not claim conformance with it if you have
    changed to using RFC 3667/3668 boilerplate.

  Checking conformance with RFC 2026 boilerplate...
  The document seems to lack an 2026 Section 10.4(C) Copyright Notice
  -- however, there's a paragraph with a matching beginning. Boilerplate
  error?
  The document seems to lack an RFC 2026 Section 10.4(C) Permission Grants
  Notice The document seems to lack an RFC 2026 Section 10.4(C) Disclaimer
  -- however, there's a paragraph with a matching beginning. Boilerplate
     error?
  There are 788 instances of too long lines in the document,
  -- the longest one being 5 characters in excess of 72.

  Warnings:
    There are 19 instances of lines with hyphenated line breaks in the
    document.

    Line 112 has weird spacing: '...t Draft    Gro...'
    Line 168 has weird spacing: '...t Draft    Gro...'
    Line 224 has weird spacing: '...t Draft    Gro...'
    Line 280 has weird spacing: '...t Draft    Gro...'
    Line 336 has weird spacing: '...t Draft    Gro...'