eap Mailing List: FW: RFC 4284 on Identity Selection Hints for the Extensible Authentication Protocol (EAP)

[Jari Arkko (jari.arkko]

rfc-editor [at] rfc-editor.org wrote:

> A new Request for Comments is now available in online RFC libraries.
>
>
>        RFC 4284
>
>        Title:      Identity Selection Hints for the 
>                    Extensible Authentication Protocol EAP 
>        Author:     F. Adrangi,  V. Lortz, 
>                    F. Bari,  P. Eronen
>        Status:     Informational
>        Date:       January 2006
>        Mailbox:    farid.adrangi [at] intel.com, 
>                    victor.lortz [at] intel.com, 
>                    farooq.bari [at] cingular.com, pasi.eronen [at] nokia.com
>        Pages:      14
>        Characters: 30322
>        Updates/Obsoletes/SeeAlso:   None
>
>        I-D Tag:    draft-adrangi-eap-network-discovery-14.txt
>
>        URL:        http://www.rfc-editor.org/rfc/rfc4284.txt
>
> The Extensible Authentication Protocol (EAP) is defined in RFC 3748.
> This document defines a mechanism that allows an access network to
> provide identity selection hints to an EAP peer -- the end of the
> link that responds to the authenticator.  The purpose is to assist
> the EAP peer in selecting an appropriate Network Access Identifier
> (NAI).  This is useful in situations where the peer does not receive
> a lower-layer indication of what network it is connecting to, or when
> there is no direct roaming relationship between the access network
> and the peer\'s home network.  In the latter case, authentication is
> typically accomplished via a mediating network such as a roaming
> consortium or broker.
>
> The mechanism defined in this document is limited in its scalability.
> It is intended for access networks that have a small to moderate
> number of direct roaming partners.  This memo provides information for the Internet community.
>