Last Call Review of draft-ietf-oauth-iss-auth-resp-02
review-ietf-oauth-iss-auth-resp-02-secdir-lc-nir-2021-11-06-00
Request | Review of | draft-ietf-oauth-iss-auth-resp |
---|---|---|
Requested revision | No specific revision (document currently at 05) | |
Type | Last Call Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2021-11-17 | |
Requested | 2021-10-27 | |
Authors | Karsten Meyer zu Selhausen , Daniel Fett | |
I-D last updated | 2021-11-06 | |
Completed reviews |
Artart Last Call review of -02
by Julian Reschke
(diff)
Secdir Last Call review of -02 by Yoav Nir (diff) |
|
Assignment | Reviewer | Yoav Nir |
State | Completed | |
Request | Last Call review on draft-ietf-oauth-iss-auth-resp by Security Area Directorate Assigned | |
Posted at | https://mailarchive.ietf.org/arch/msg/secdir/PBUPS9ty4S_6iyIJeuTqBn-hyFA | |
Reviewed revision | 02 (document currently at 05) | |
Result | Ready | |
Completed | 2021-11-06 |
review-ietf-oauth-iss-auth-resp-02-secdir-lc-nir-2021-11-06-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 draft is clear and well-written. The Security Considerations section specifically is comprehensive and clear. My one suggestion would be to move the first paragraph in the Security Considerations section to the Introduction. It is about the attack and about the protocol in the document being effective against the attack. It's not really a consideration in the way that the rest of the section is.