Last Call Review of draft-ietf-i2rs-traceability-08
review-ietf-i2rs-traceability-08-secdir-lc-ladd-2016-05-05-00
Request | Review of | draft-ietf-i2rs-traceability |
---|---|---|
Requested revision | No specific revision (document currently at 11) | |
Type | Last Call Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2016-04-29 | |
Requested | 2016-04-21 | |
Authors | Joe Clarke , Gonzalo Salgueiro , Carlos Pignataro | |
I-D last updated | 2016-05-05 | |
Completed reviews |
Genart Last Call review of -09
by Elwyn B. Davies
(diff)
Genart Last Call review of -08 by Elwyn B. Davies (diff) Secdir Last Call review of -08 by Watson Ladd (diff) Opsdir Last Call review of -08 by Menachem Dodge (diff) Rtgdir Early review of -06 by Mach Chen (diff) Rtgdir Early review of -06 by Les Ginsberg (diff) |
|
Assignment | Reviewer | Watson Ladd |
State | Completed | |
Request | Last Call review on draft-ietf-i2rs-traceability by Security Area Directorate Assigned | |
Reviewed revision | 08 (document currently at 11) | |
Result | Ready | |
Completed | 2016-05-05 |
review-ietf-i2rs-traceability-08-secdir-lc-ladd-2016-05-05-00
Dear all, I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the security area directors. Document editors and WG chairs should treat these comments just like any other last call comments. In my opinion the document is ready. It describes what data should be logged. While the security considerations section mentions the privacy impact of the data in the logs, it doesn't mention the value of the information in the logs for event reconstruction, which is mentioned in the text. I don't see a lot of space for problems here, but maybe I didn't see them. Sincerely, Watson Ladd