Subject: [eap] FW: I-D ACTION:draft-arkko-eap-service-identity-auth-03.txt

From: Jari Arkko <[email-masked]>
Date: Thu, 21 Jul 2005 10:17:54 +0300

FYI. This version attempts to take into account the
discussion that happened on the EAP list about
channel bindings, including selection of the checking
entity and AAA vs. EAP based transport discussion.
Comments appreciated.

--Jari

>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>
>	Title		: Authenticated Service Information for the Extensible Authentication Protocol (EAP)
>	Author(s)	: J. Arkko, P. Eronen
>	Filename	: draft-arkko-eap-service-identity-auth-03.txt
>	Pages		: 25
>	Date		: 2005-7-20
>	
>EAP is typically used in an arrangement where the actual service
>   (such as a wireless LAN access point) is separated from the
>   authentication server.  However, EAP itself does not have a concept
>   of a service identity or its parameters, and thus the client usually
>   does not authenticate any information about the service itself, even
>   when a mutually authenticating EAP method is used.  This document
>   specifies a backward compatible extension to popular EAP methods for
>   authenticating service related information, such as the identity and
>   type of the offered service.  A common parameter name space is
>   created in order to ensure that the same kinds of identifiers can be
>   authenticated independent of the choice of the EAP authentication
>   method, retaining the EAP media independence principle.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-arkko-eap-service-identity-auth-03.txt
>  
>

_______________________________________________
eap mailing list
[email-masked]
http://mail.frascone.com/mailman/listinfo/eap