The Network Access Identifier
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 8
- Abstract
- This document proposes syntax for the Network Access Identifier (NAI), the userID submitted by the client during PPP authentication. [STANDARDS-TRACK]
- Publication Date
- 1999-01-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC2486- Link
- https://doi.org/10.17487/RFC2486
- Author(s)
- Dr. Bernard D. AbobaMark A. Beadles
- Keyword(s)
- NAI, Tunnel, Roaming
Latest version of IETF RFC 2486
Document Versions — IETF RFC 2486
-
▶ IETF RFC 2486 (1999-01-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Bibliographic Reference(s)
- IETF RFC 821 [Superseded*]
- IETF RFC 1035 [Active, Amended*]
- IETF RFC 2052 [Superseded*]
- IETF RFC 2119 [Active*]
- IETF RFC 2138 [Superseded*]
- IETF RFC 2139 [Superseded*]
- IETF RFC 2194 [Active*]
- IETF RFC 2234 [Superseded*]
- IETF RFC 2401 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC2486.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 2486, The Network Access Identifier. Available at https://doi.org/10.17487/RFC2486
Snippet:
IETF RFC 2486, The Network Access Identifier. Available at https://doi.org/10.17487/RFC2486
HTML (ISO 690 compliant)
Preview:
IETF RFC 2486, The Network Access Identifier. Available at https://doi.org/10.17487/RFC2486
Snippet:
<span class="citation"><cite>IETF RFC 2486</cite>, The Network Access Identifier. Available at <a href="https://doi.org/10.17487/RFC2486" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2486</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 2486, The Network Access Identifier
doi: 10.17487/RFC2486
url: https://doi.org/10.17487/RFC2486
doi: 10.17487/RFC2486
url: https://doi.org/10.17487/RFC2486
Snippet:
<li> <cite id="bib-rfc2486">IETF RFC 2486</cite>, The Network Access Identifier <span class="doi">10.17487/RFC2486</span> </li>
Referenced By
- IETF RFC 2607 [Active*]
- IETF RFC 2794 [Active*]
- IETF RFC 2865 [Active*]
- IETF RFC 2881 [Active*]
- IETF RFC 2975 [Active*]
- IETF RFC 2977 [Active*]
- IETF RFC 2989 [Active*]
- IETF RFC 3024 [Active*]
- IETF RFC 3169 [Active*]
- IETF RFC 3539 [Active*]
- IETF RFC 3576 [Superseded*]
- IETF RFC 3579 [Active*]
- IETF RFC 3588 [Superseded*]
- IETF RFC 3748 [Active*]
- IETF RFC 3830 [Active*]
- IETF RFC 3846 [Active*]
- IETF RFC 3957 [Active*]
- IETF RFC 4004 [Active*]
- IETF RFC 4006 [Superseded*]
- IETF RFC 4282 [Superseded*]
- IETF RFC 5113 [Active*]
- IETF RFC 5729 [Active*]