What is the difference between defining a new method vs. a new version
of the existing EAP method that is not backward compatible? I don't see
how the implementation issue will go away. Some one still needs to
implement it and customers need to deploy it. Might be more confusing to
define another
Sorry it took me a few days to respond to this thread.
I agree with Bernard that there's no benefit in creating
Yet Another Password-Based EAP Method (YAPBEM). There's
no point in reinventing the wheel for a fourth time and
it's not the IETF way. We're not researchers. We're practical
engineers
I am not surprised to hear that EAP method authors agree that no further
EAP methods should be developed.
Part of the problem with EAP methods is that people should have started
to standardize them within the IETF several years ago. Unfortunately,
there was no interest by some of the EAP method
