eap Mailing List: RE: Re: Rewrite of Section 2 of the EAP Key Management Framework

[Bernard Aboba (Bernard_Aboba]

>Perhaps we could move forward on the AMSK/EMSK issue
>by looking at the constraints we are under:

I presume that you're talking about a future document, not the current key
framework document, right? 

As I see it, we really only need to do a few things in the key framework
document:

a. Define the interactions between the EAP method layer, EAP
authenticator/peer layer, EAP layer, and lower layer (including AAA).

b. Define the EAP security model (e.g. the cryptographic assumptions). 

c. Derive the security requirements for the lower layer based on a) and b).

d. Describe how current implementations behave (including lower layers). 

If we've do these things, then we can always build on that in future
documents.   However, it has turned out to be difficult enough to accomplish
just these goals that taking on even more probably will make it even more
difficult to finish.