>>>>> "Leif" == Leif Johansson <[email protected]> writes:
>> It seems to me like the EAP applicability update would be a great
>> place to cover these issues.
Leif> Didn't we have the discussion on general vs specific eap
Leif> applicability stmt for abfab already and decided we couldn't
Leif> figure out a way to make sure a general applicability stmt
Leif> would get enough review? Isn't this re-opening this issue?
Yes, we had that discussion.
I actually think all the issues I'm bringing up would be kind of tricky
to cover in a general applicability statement.
It's precisely because they are scoped to using EAP for application
authentication--which is ABFAB's scope--that I think we can address
them.
Remember ABFAB's scope is not GSS-EAP; we're scoped to using EAP
authentication and AAA for application federation.
GSS-EAP is the only method currently on our charter to do that.
However, the applicability statement needs to be broad enough to cover
the ABFAB scope, and I'm fairly sure ABFAB-specific is where we got in
the EAP applicability scoping discussion.
Am I misremembering that discussion?
_______________________________________________
abfab mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/abfab
