The Network Access Identifier
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 16
- 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]
- Publication Date
- 2005-12-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC4282- Link
- https://doi.org/10.17487/RFC4282
- Author(s)
- Dr. Bernard D. AbobaMark A. BeadlesJari ArkkoPasi Eronen
- Keyword(s)
- NAI, Roaming, Tunnel
Latest version of IETF RFC 4282
Document Versions — IETF RFC 4282
-
▶ IETF RFC 4282 (2005-12-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 1035 [Active, Amended*]
- IETF RFC 2119 [Active*]
- IETF RFC 3490 [Superseded*]
- IETF RFC 4013 [Superseded*]
- IETF RFC 4234 [Superseded*]
Bibliographic Reference(s)
- Arkko, J. and B. Aboba, "Network Discovery and Selection Problem", Work in Progress, October 2005. EXTERNAL
- IETF RFC 821 [Superseded*]
- IETF RFC 2194 [Active*]
- IETF RFC 2341 [Active*]
- IETF RFC 2401 [Superseded*]
- IETF RFC 2486 [Superseded*]
- IETF RFC 2637 [Active*]
- IETF RFC 2661 [Active*]
- IETF RFC 2865 [Active*]
- IETF RFC 2866 [Active*]
- IETF RFC 3579 [Active*]
- IETF RFC 3588 [Superseded*]
- IETF RFC 3748 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4282.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4282, The Network Access Identifier. Available at https://doi.org/10.17487/RFC4282
Snippet:
IETF RFC 4282, The Network Access Identifier. Available at https://doi.org/10.17487/RFC4282
HTML (ISO 690 compliant)
Preview:
IETF RFC 4282, The Network Access Identifier. Available at https://doi.org/10.17487/RFC4282
Snippet:
<span class="citation"><cite>IETF RFC 4282</cite>, The Network Access Identifier. Available at <a href="https://doi.org/10.17487/RFC4282" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4282</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4282, The Network Access Identifier
doi: 10.17487/RFC4282
url: https://doi.org/10.17487/RFC4282
doi: 10.17487/RFC4282
url: https://doi.org/10.17487/RFC4282
Snippet:
<li> <cite id="bib-rfc4282">IETF RFC 4282</cite>, The Network Access Identifier <span class="doi">10.17487/RFC4282</span> </li>
Referenced By
- IETF RFC 4186 [Active*]
- IETF RFC 4187 [Active*]
- IETF RFC 4283 [Active*]
- IETF RFC 4284 [Active*]
- IETF RFC 4372 [Active*]
- IETF RFC 4718 [Superseded*]
- IETF RFC 4763 [Active*]
- IETF RFC 4764 [Active*]
- IETF RFC 4851 [Active*]
- IETF RFC 5106 [Active*]
- IETF RFC 5113 [Active*]
- IETF RFC 5176 [Active*]
- IETF RFC 5216 [Active*]
- IETF RFC 5247 [Active*]
- IETF RFC 5281 [Active*]
- IETF RFC 5421 [Active*]
- IETF RFC 5580 [Active*]
- IETF RFC 5687 [Active*]
- IETF RFC 5729 [Active*]
- IETF RFC 5931 [Active*]
- IETF RFC 5996 [Superseded*]
- IETF RFC 5997 [Active*]
- IETF RFC 6124 [Active*]
- IETF RFC 6678 [Active*]
- IETF RFC 6733 [Active*]
- IETF RFC 6973 [Active*]
- IETF RFC 7170 [Superseded*]
- IETF RFC 7296 [Active*]
- IETF RFC 7542 [Active*]
- IETF RFC 9190 [Active*]