General comment: EAP configuration and implementation is certainly one issue,
but the whole certificate stuff is terrible from a user's point of view. We
could try to solve it in this draft, but it certainly touches a lot of topics.
The goal of the draft is to leverage the web root, in order to bootstrap
trust in EAP. The only real thing that the user needs to do is to enter:
Name: [email protected]
Password: superSecret
Provided there's some network connection available, everything else can be
automatic.
ah yes. I guess it might make sense to make that clear towards the
beginning of the document :-) I only got a later ....
I finished the document now and really like it. I just think the
normative part comes quite late in the document. Maybe it should also be
referenced in earlier sections. To make it stronger, you could even use
SHOULD instead of RECOMMENDED (in section 8.2), I guess
best regards
Carolin
_______________________________________________
Emu mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/emu
