Reviewer: Bob Halley
Review result: Ready
I am an assigned INT directorate reviewer for draft-ietf-emu-tls-eap-types.
These comments were written primarily for the benefit of the Internet Area
Directors. Document editors and shepherd(s) should treat these comments just
like they would treat commen
On Feb 2, 2023, at 10:15 AM, Bob Halley via Datatracker
wrote:
> While I am not an EAP or TLS expert, I found the document to be very clearly
> written, in particular in its explanations of why various choices were made.
> I
> did not see anything worrisome in the document.
Thanks.
> The fo
On Feb 2, 2023, at 2:22 AM, Eliot Lear wrote:
> I am wondering if we should close this issue. At the end of the day, if the
> client knows it's doing something like 2FA that requires an EAP method, it
> can initiate.
I'm not clear how that would happen. Nothing in the doc discusses how a
c
On Thu, 2 Feb 2023, at 18:31, Alan DeKok wrote:
> On Feb 2, 2023, at 2:22 AM, Eliot Lear wrote:
>> I am wondering if we should close this issue. At the end of the day, if the
>> client knows it's doing something like 2FA that requires an EAP method, it
>> can initiate.
>
> I'm not clear how t
On Feb 2, 2023, at 1:52 PM, Alexander Clouter wrote:
>> I'm not clear how that would happen. Nothing in the doc discusses
>> how a client may choose authentication methods.
>
> The documentation does not but I did see Appendix C.9 lets the client state
> what it wants to do:
>
> https://data
