RFC 4282:The Network Access Identifier
RFC-Ref

network


Click on the red underlined text to get to the source

... Considerable interest exists for a set of features that fit within the general category of "roaming capability" for network access, including dialup Internet users, Virtual Private Network ...
... network access, including dialup Internet users, Virtual Private Network (VPN) usage, wireless LAN authentication ...
... necessary to have a standardized method for identifying users. This document defines syntax for the Network Access Identifier (NAI). Examples of implementations that use the NAI ...
... This document frequently uses the following terms: Network Access Identifier The Network Access Identifier ...
... Network Access Identifier The Network Access Identifier (NAI) is the user identity submitted ...
... user identity submitted by the client during network access authentication. In roaming, the purpose of the NAI ...
... authentication. Network Access Server The Network Access Server ...
... Network Access Server The Network Access Server (NAS) is the device that clients connect ...
... NAS) is the device that clients connect to in order to get access to the network. In PPTP terminology, this is referred to as the PPTP Access Concentrator ...
... include ISP "confederations" and ISP-provided corporate network access support. Tunneling Service ...
... A tunneling service is any network service enabled by tunneling protocols such as PPTP ...
... secure access to corporate intranets via a Virtual Private Network (VPN). ...
... As described in [RFC2194], there are a number of providers offering network access services, and the number of Internet Service Providers ...
... authentication server. For use in roaming, this function is accomplished via the Network Access Identifier (NAI) submitted by the user to the NAS ...
... by the user to the NAS in the initial network authentication. It is also expected that NASes will use the NAI ...


... bidirectional character processing MUST be performed by end systems that take international text as input. In a network access setting, such systems are typically the client and the Authentication, Authorization, and Accounting ...
... nodes that just pass NAIs around or receive them from the network. End systems MUST also perform checking for prohibited output and unassigned code points ...
... The responsibility for the conversion of internationalized domain names to ASCII is left for the end systems, such as network access clients and AAA servers ...
... As proposed in this document, the Network Access Identifier is of the form user@realm. Please note that while the user portion of the NAI ...
... Examples of valid Network Access Identifiers include the following: bob ...
... ASCII representation. Examples of invalid Network Access Identifiers include the following: fred@example ...


... Aboba, B. and M. Beadles, "The Network Access Identifier", RFC 2486(-> 4282prop), January 1999. ...
... Arkko, J. and B. Aboba, "Network Discovery and Selection Problem", Work in Progress, October 2005. ...


... nodes. o The mediating network syntax and its implications have been fully described and not given only as an example. Note that this syntax is not intended to be a full solution to network ...
... mediating network syntax and its implications have been fully described and not given only as an example. Note that this syntax is not intended to be a full solution to network discovery and selection needs as defined in [netsel-problem]. Rather, it is ...


... discussions of this problem space, and to Farid Adrangi for suggesting the representation of mediating networks in NAIs. Jonathan Rosenberg reported the BNF ...



Google
Web
RFC-Ref