eap Mailing List: Re: hopefully final changes for draft-ietf-eap-keying

[Jari Arkko (jari.arkko]

FYI -- With the publication of -22 and some discussion with Bernard,
the remaining edits appear to be:

In Section 1.5, change

OLD:
If the authenticator
uses a key derivation function to derive additional keying material,
the authenticator is trusted to distribute the derived keying
material only to the appropriate party that is known to the peer, and
no other party. When this approach is used, care must be taken to
ensure that the resulting key management system meets all of the
principles in [RFC4962], confirming that keys used to protect data
are to be known only by the peer and authenticator.
NEW:
If the authenticator or backend authentication server uses a key
derivation function to derive additional keying material, it is
trusted to distribute the derived keying material
only to the appropriate party that is known to the peer, and no
other party. When this approach is used, care must be taken to
ensure that the resulting key management system meets all of the
principles in RFC this document, confirming that keys used to protect
data are to be known only by the peer and authenticator.