Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Obsoletes:

RFC 2486

Obsoleted by:

RFC 7542

Authors:

B. Aboba
M. Beadles
J. Arkko
P. Eronen

Stream:

IETF

Source:

radext (sec)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC4282

Discuss this RFC: Send questions or comments to the mailing listradext@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 4282

Abstract

In order to provide roaming services, it is necessary to have astandardized method for identifying users. This document defines thesyntax for the Network Access Identifier (NAI), the user identitysubmitted by the client during network authentication. "Roaming" maybe loosely defined as the ability to use any one of multiple InternetService Providers (ISPs), while maintaining a formal, \%customer-vendorrelationship with only one. Examples of where roaming capabilitiesmight be required include ISP "confederations" and \%ISP-providedcorporate network access support. This document is a revised versionof RFC 2486, which originally defined NAIs. Enhancements includeinternational character set and privacy support, as well as a numberof corrections to the original RFC. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.