Hi Robert,
I think Vittorio is off-site/out-of-office this week so he's unlikely to be able to reply anytime soon. In the meantime, however, I wanted to note that he did add some more explanatory/clarifying text around levels and caching to the document in -11 following Roman's AD review and subsequent discussions (doc history for that revision has 'Updates in the Protocol Overview section clarifying the nature of "authentication levels" and caching strategies, addressing AD review comments). It's subjective, of course, but we do believe the document sufficiently discusses the concepts for the expected/intended audience.
I think Vittorio is off-site/out-of-office this week so he's unlikely to be able to reply anytime soon. In the meantime, however, I wanted to note that he did add some more explanatory/clarifying text around levels and caching to the document in -11 following Roman's AD review and subsequent discussions (doc history for that revision has 'Updates in the Protocol Overview section clarifying the nature of "authentication levels" and caching strategies, addressing AD review comments). It's subjective, of course, but we do believe the document sufficiently discusses the concepts for the expected/intended audience.
On Mon, Mar 20, 2023 at 1:26 PM Robert Sparks via Datatracker <noreply@xxxxxxxx> wrote:
Reviewer: Robert Sparks
Review result: Ready with Issues
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.
CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you.
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
