RFC - 4282
The Network Access Identifier
| Original: | ftp://ftp.isi.edu/in-notes/rfc4282.txt |
|---|---|
| Authors: | B. Aboba [Microsoft], M. Beadles [ENDFORCE], J. Arkko [Ericsson], P. Eronen [Nokia] |
| Date: | December 2005 |
| Category: | Proposed Standard |
| Obsoletes: | |
|---|---|
| RFC-2486 | The Network Access Identifier (Obsoleted by RFC-4282prop) |
| Referred by: | 10 RFC |
| Refers to: | 18 RFC |
Status
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2005).
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.
-
prepared by Miloslav Nic
- the founder of Zvon.org and Law-Ref.org
- the head of B.Sc. program Informatics and chemistry [in Czech]
- the founder of Lidem.org - Volby 2006 - parliamentary elections in the Czech Republic [in Czech]
- the chief consultant of the publishing house ICT Press
- and Pavel Srb, a student of B.Sc. program Informatics and chemistry
