[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [eap] RE: [Isms] RADIUS is not a trusted third party

To: "Glen Zorn (gwz)" <gwz@cisco.com>
Subject: RE: [eap] RE: [Isms] RADIUS is not a trusted third party
From: Bernard Aboba <aboba@internaut.com>
Date: Tue, 26 Apr 2005 22:43:05 -0700 (PDT)
Cc: "'Blumenthal, Uri'" <uri.blumenthal@intel.com>, radiusext@ops.ietf.org, eap@frascone.com, isms@ietf.org
In-reply-to: <200504270343.j3R3h0b4009558@sj-core-3.cisco.com>
References: <200504270343.j3R3h0b4009558@sj-core-3.cisco.com>

> "EAP server" is what "eap peer" and "aaa" share.

An EAP server can exist on the authenticator when there is  no AAA
server present.  It is a distinct entity from the EAP peer.  It is not
"shared" between the EAP peer and AAA server.

> Oh and we _are_ talking EAPv2, right?

The only version of EAP that I'm familiar with is defined in RFC 3748.

Maybe this entire discussion has been about some *other* version of EAP?




--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

Follow-Ups:
- RE: [eap] RE: [Isms] RADIUS is not a trusted third party
  - From: "Glen Zorn \(gwz\)" <gwz@cisco.com>

References:
- RE: [eap] RE: [Isms] RADIUS is not a trusted third party
  - From: "Glen Zorn \(gwz\)" <gwz@cisco.com>

Prev by Date: RE: [eap] RE: [Isms] RADIUS is not a trusted third party
Next by Date: RE: [eap] RE: [Isms] RADIUS is not a trusted third party
Previous by thread: RE: [eap] RE: [Isms] RADIUS is not a trusted third party
Next by thread: RE: [eap] RE: [Isms] RADIUS is not a trusted third party
Index(es):
- Date
- Thread