Telechat Review of draft-ietf-oauth-step-up-authn-challenge-13
review-ietf-oauth-step-up-authn-challenge-13-artart-telechat-sparks-2023-03-20-00

Request Review of draft-ietf-oauth-step-up-authn-challenge
Requested revision No specific revision (document currently at 17)
Type Telechat Review
Team ART Area Review Team (artart)
Deadline 2023-04-11
Requested 2023-03-15
Authors Vittorio Bertocci , Brian Campbell
I-D last updated 2023-09-08 (Latest revision 2023-06-26)
Completed reviews Secdir IETF Last Call review of -12 by Valery Smyslov (diff)
Artart IETF Last Call review of -12 by Robert Sparks (diff)
Genart IETF Last Call review of -11 by Christer Holmberg (diff)
Artart Telechat review of -13 by Robert Sparks (diff)
Httpdir Telechat review of -13 by Mark Nottingham (diff)
Assignment Reviewer Robert Sparks
State Completed
Request Telechat review on draft-ietf-oauth-step-up-authn-challenge by ART Area Review Team Assigned
Posted at https://mailarchive.ietf.org/arch/msg/art/ZuSlwngmH_kQFHhzoPAWUJb4PYc
Reviewed revision 13 (document currently at 17)
Result Ready w/issues
Completed 2023-03-20
review-ietf-oauth-step-up-authn-challenge-13-artart-telechat-sparks-2023-03-20-00
Summary: essentially ready but with issues to consider before being published
as a proposed standard RFC.

Thanks for addressing the nit from my previous review.

I am not convinced that the document doesn't need more discussion around the
points I raised as issues in my previous review. See
https://mailarchive.ietf.org/arch/msg/last-call/Ragwzpjm_58ydcr5VHqOyrmfw5I/.

I fully understand that you can't completely specify behavior, but your
explanations in your response to Roman, and the refinement in the response to
me really belong in the draft.