metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 4282: The Network Access Identifier

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7542.

Current document in this lineage: RFC 7542 — The Network Access Identifier

In plain English — editorial summary, not part of the RFC

In order to provide roaming services, it is necessary to have a standardized method for identifying users. This document defines the syntax for the Network Access Identifier (NAI), the user identity submitted by the client during network authentication. "Roaming" may be loosely defined as the ability to use any one of multiple Internet Service Providers (ISPs), while maintaining a formal, \%customer-vendor relationship with only one. Examples of where roaming capabilities might be required include ISP "confederations" and \%ISP-provided corporate network access support. This document is a revised version of RFC 2486, which originally defined NAIs. Enhancements include international character set and privacy support, as well as a number of corrections to the original RFC. [STANDARDS-TRACK]

Document record

Document ID
RFC4282
Published
December 2005
Authors
B. Aboba; M. Beadles; J. Arkko; P. Eronen
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
16
Also known as
—
Obsoletes:
RFC 2486
Obsoleted by:
RFC 7542

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 2486 (1999)
  2. RFC 4282 (2005)
  3. RFC 7542 (2015) ✓

Read the full history of The Network Access Identifier →

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/4282-the-network-access-identifier