Last Call Review of draft-billon-expires-06
review-billon-expires-06-secdir-lc-lonvick-2022-12-05-00
Request | Review of | draft-billon-expires |
---|---|---|
Requested revision | No specific revision (document currently at 09) | |
Type | Last Call Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2022-12-27 | |
Requested | 2022-11-29 | |
Authors | Benjamin BILLON , John R. Levine | |
I-D last updated | 2022-12-05 | |
Completed reviews |
Artart Last Call review of -06
by Barry Leiba
(diff)
Opsdir Last Call review of -06 by Carlos Pignataro (diff) Genart Last Call review of -08 by Robert Sparks (diff) Secdir Last Call review of -06 by Chris M. Lonvick (diff) Secdir Last Call review of -08 by Chris M. Lonvick (diff) Artart Last Call review of -07 by Barry Leiba (diff) Opsdir Last Call review of -08 by Tim Chown (diff) |
|
Assignment | Reviewer | Chris M. Lonvick |
State | Completed | |
Request | Last Call review on draft-billon-expires by Security Area Directorate Assigned | |
Posted at | https://mailarchive.ietf.org/arch/msg/secdir/yP-dGkARqgGYZGWWSt1xlzSwyqk | |
Reviewed revision | 06 (document currently at 09) | |
Result | Ready | |
Completed | 2022-12-05 |
review-billon-expires-06-secdir-lc-lonvick-2022-12-05-00
Hi, 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 Ready. I'd like to suggest that the authors consider recommending that a mechanism to protect the header be utilized if there is a concern that a malicious attacker may surreptitiously attempt to change the value of the Expires header field. The authors will likely know what mechanisms may be used better than me. Best regards, Chris