Last Call Review of draft-ietf-mile-implementreport-06
review-ietf-mile-implementreport-06-opsdir-lc-brownlee-2016-06-29-00

Request Review of draft-ietf-mile-implementreport
Requested rev. no specific revision (document currently at 10)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2016-06-28
Requested 2016-06-13
Draft last updated 2016-06-29
Completed reviews Genart Last Call review of -09 by Christer Holmberg (diff)
Genart Telechat review of -09 by Christer Holmberg (diff)
Secdir Last Call review of -09 by Brian Weis (diff)
Opsdir Last Call review of -06 by Nevil Brownlee (diff)
Assignment Reviewer Nevil Brownlee
State Completed
Review review-ietf-mile-implementreport-06-opsdir-lc-brownlee-2016-06-29
Reviewed rev. 06 (document currently at 10)
Review result Has Issues
Review completed: 2016-06-29

Review
review-ietf-mile-implementreport-06-opsdir-lc-brownlee-2016-06-29

Hi all:

I have performed an Operations Directorate review of
   draft-ietf-mile-implementreport-09

  "This document is a collection of implementation reports from vendors,
   consortiums, and researchers who have implemented one or more of the
   standards published from the IETF INCident Handling (INCH) and
   Management Incident Lightweight Exchange (MILE) working groups."

This draft is a collection of information about Security Incident
reporting protocols, and the implementation of systems that use them
to share such information.  It is simply a collection of information,
it makes no attempt to compare the various standards or implementations.
As such, it will be of interest to Network Operators who wish to collect
and share such data.

Operationally, Operators would need to decide which incident data
collection group they want to be part of, that choice will strongly
influence their choice of reporting protocol and applications to
gather and distribute the data.

The draft seems (to me) to need quite a bit of copy-editing, I list
a few changes and suggestions below ...

S1  RFC5070-bis.  Is there an Internet Draft about this, or some other
      document you could reference?  It's mentioned again in section
      3.1, but there's nothing about it in the References section.

S2.1  s/provides a solutions/provides solutions/
S2.3  s/IODEF formatted-message to/IODEF formatted-messages to/
      s/by REN-ISAC are designed/by REN-ISAC is designed/

S3.2  "IODEF-SCI is the IETF draft"  there's no reference to such a
      draft, there should be.
      "It also equips the interface ..."  Exactly what does this mean?

S4.2.2 s/prevents from accidentally/prevents accidentally/
       s/ensure it is a well formed format/
         ensure it is well formed/

S5.1  "General availability of Threat Central will
       be in 2014."
      It's now well into 2016 - this needs updating!

Overall, I think the material in this draft is interesting, but it
needs quite a bit of tidying/updating to get it ready for publishing.

Cheers, Nevil

--
---------------------------------------------------------------------
 Nevil Brownlee                          Computer Science Department
 Phone: +64 9 373 7599 x88941             The University of Auckland
 FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand