I would like to see the crypto-binding stuff (not compound binding -- as
others have noted, we don't have consensus on that topic) and
extensibility (how to add new attributes) specified.
That should not take more than 1-2 months to write-up, review and
finalize :). That should also be least disruptive to existing
implementations. I would also like to see TTLS-v0 published very soon.
regards,
Lakshminath
On 8/21/2007 9:38 PM, Alan DeKok wrote:
Sam Hartman wrote:
So, if EMU is going to base its work on something existing, it is
probably important for EMU to take on the entire method.
If consensus is to use EAP-TTLS, then I would suggest publishing the
base EAP-TTLS document pretty much as-is as a standards-track document.
The additional EMU requirements can be addressed in a separate document.
This process lets us get something done quickly. I would prefer to
void spending years talking about a new EAP method, followed by years of
trying to get it widely deployed.
Alan DeKok.
_______________________________________________
Emu mailing list
Emu@ietf.org
https://www1.ietf.org/mailman/listinfo/emu
_______________________________________________
Emu mailing list
Emu@ietf.org
https://www1.ietf.org/mailman/listinfo/emu
