RFC 4284: Identity Selection Hints for the Extensible Authentication Protocol (EAP)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC4284
- Published
- January 2006
- Authors
- F. Adrangi; V. Lortz; F. Bari; P. Eronen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4282The Network Access IdentifierObsoleted
December 2005
- RFC 5729Clarifications on the Routing of Diameter Requests Based on the Username and the RealmCurrent
December 2009
- RFC 2794Mobile IP Network Access Identifier Extension for IPv4Current
March 2000
- RFC 3846Mobile IPv4 Extension for Carrying Network Access IdentifiersCurrent
June 2004
- RFC 2486The Network Access IdentifierObsoleted
January 1999
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?