| Re: Proposed Resolution to Issue 357: Channel Binding Defintiion | <– Date –> <– Thread –> |
|
From: Yoshihiro Ohba (yohba |
|
| Date: Wed, 21 Jun 2006 16:28:05 -0700 (PDT) | |
On Wed, Jun 21, 2006 at 03:16:14PM -0700, Bernard Aboba wrote: > Yoshi Ohba said: > > How about: > > "It is expected that the parameters are also agreed upon by the peer > and authenticator via the lower layer if the authenticator is the > valid entity that advertised the parameters." > > Question: What does "valid" mean here? Do we mean "securely agreed upon"? > > How about this: > > "A secure mechanism for ensuring that a subset of the parameters transmitted > by the > authenticator (such as authenticator identifiers and properties) are agreed > upon by > the EAP peer and server. It is expected that the parameters are also > securel agreed > upon by the EAP peer and authenticator via the lower layer if the > authenticator > advertised the parameters." The text works for me. (s/securel/securely/) Thank you, Yoshihiro Ohba > > > _________________________________________________________________ > To unsubscribe or modify your subscription options, please visit: > http://lists.frascone.com/mailman/listinfo/eap > > Arhives: http://lists.frascone.com/pipermail/eap >
-
Re: Proposed Resolution to Issue 357: Channel Binding Defintiion Bernard Aboba, June 21 2006
- Re: Proposed Resolution to Issue 357: Channel Binding Defintiion Yoshihiro Ohba, June 21 2006
- Re: Proposed Resolution to Issue 357: Channel Binding Defintiion Jari Arkko, June 24 2006
Results generated by Tiger Technologies using MHonArc.