>The discussion focuses on the problem EMSK is optional or mandatory. I don't think this is a problem - GENERATION of EMSK is compulsoty as spelled out in RFC 3578.
The problem is non-compliance. Some, er, people seem to think "the standard says do A, but since I don't use A at the moment - I won't bother." >RFC3578 defined EMSK is mandatory, And that should be the end of discussion. > but it is not used at all. First - do you know all the applications that use key-generating EAP methods? But really - who cares? >If EMSK must be used, it is mandatory. if no, I think, >it may be better that it is optional. VERY strongly disagree. Mandatory is what is explicitly specified as mandatory, period. Otherwise many would implement just those pieces and features of the standard that his particular product needs today. (I'm proud of my restraint - not even once using a term "B*S*" :-) _______________________________________________ Emu mailing list [email protected] https://www1.ietf.org/mailman/listinfo/emu
