| Re: Re: [802.1] Re: 802.1X interface variable | <– Date –> <– Thread –> |
|
From: Bernard Aboba (aboba |
|
| Date: Sat, 3 Jan 2004 08:30:49 -0500 (EST) | |
> draft-ietf-eap-keying-01 already states this: > > EAP key derivation takes place between the EAP peer > and EAP server, and methods supporting key derivation MUST also > support mutual authentication. > > (Perhaps this is one of the keyword statements that should already > have been moved to 2284bis...) This statement is already in Section 7.10. > The reverse requirement (mutual auth => key derivation) seems sensible > to me as well. I do not have a comment on the protected result indiciations > part, I have to think about that some more. I've added both statements in the proposed resolution of Issue 207 (posted previously). Let me know what you think.
- Re: [802.1] Re: 802.1X interface variable, (continued)
-
Re: [802.1] Re: 802.1X interface variable Bernard Aboba, January 2 2004
- Re: [802.1] Re: 802.1X interface variable Yoshihiro Ohba, January 2 2004
- Re: [802.1] Re: 802.1X interface variable Bernard Aboba, January 2 2004
- Re: Re: [802.1] Re: 802.1X interface variable Jari Arkko, January 2 2004
- Re: Re: [802.1] Re: 802.1X interface variable Bernard Aboba, January 3 2004
- Re: Re: [802.1] Re: 802.1X interface variable Jari Arkko, January 4 2004
- Re: Re: [802.1] Re: 802.1X interface variable Bernard Aboba, January 4 2004
-
Re: [802.1] Re: 802.1X interface variable Bernard Aboba, January 2 2004
- Re: Re: [802.1] Re: 802.1X interface variable Yoshihiro Ohba, January 9 2004
Results generated by Tiger Technologies using MHonArc.