The Network Access Identifier
RFC 4282, “The Network Access Identifier”, is a Proposed Standard document published in December 2005 by B. Aboba, M. Beadles, J. Arkko, P. Eronen. It obsoletes RFC 2486. It has been obsoleted by RFC 7542 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 4282 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4281 The Codecs Parameter for "Bucket" Media Types
- RFC 4283 Mobile Node Identifier Option for Mobile IPv6
- RFC 4280 Dynamic Host Configuration Protocol Options for Broadcast and Multicast Control Servers
- RFC 4279 Pre-Shared Key Ciphersuites for Transport Layer Security
- RFC 4286 Multicast Router Discovery
- RFC 4287 The Atom Syndication Format
- RFC 4288 Media Type Specifications and Registration Procedures
- RFC 4289 Multipurpose Internet Mail Extensions Part Four: Registration Procedures