Last Call Review of draft-ietf-httpbis-expect-ct-07
review-ietf-httpbis-expect-ct-07-secdir-lc-montville-2018-08-10-00
Request | Review of | draft-ietf-httpbis-expect-ct |
---|---|---|
Requested revision | No specific revision (document currently at 08) | |
Type | Last Call Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2018-08-14 | |
Requested | 2018-07-31 | |
Authors | estark@google.com | |
I-D last updated | 2018-08-10 | |
Completed reviews |
Opsdir Last Call review of -07
by Qin Wu
(diff)
Genart Last Call review of -07 by Vijay K. Gurbani (diff) Secdir Last Call review of -07 by Adam W. Montville (diff) |
|
Assignment | Reviewer | Adam W. Montville |
State | Completed | |
Request | Last Call review on draft-ietf-httpbis-expect-ct by Security Area Directorate Assigned | |
Reviewed revision | 07 (document currently at 08) | |
Result | Ready | |
Completed | 2018-08-10 |
review-ietf-httpbis-expect-ct-07-secdir-lc-montville-2018-08-10-00
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. The summary of the review is that this document is ready. Nits/comments from GENART and/or OPS reviews not repeated - I really didn't notice any nits beyond those. I felt that the document read rather well, and that the security and privacy considerations covered what needed to be covered. That said, the first paragraph of Section 4 (Security Considerations) could have a subsection of its own "Hostile Header Attacks", which would give the draft three, clear security considerations - Hostile Header Attacks, Maximum max-age, and Avoiding amplification attacks.