<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-radext-rfc2486bis" target="https://datatracker.ietf.org/doc/html/draft-ietf-radext-rfc2486bis-06">
   <front>
      <title>The Network Access Identifier</title>
      <author initials="M. A." surname="Beadles" fullname="Mark A. Beadles">
         <organization>ENDFORCE</organization>
      </author>
      <author initials="J." surname="Arkko" fullname="Jari Arkko">
         <organization>Ericsson</organization>
      </author>
      <author initials="B." surname="Aboba" fullname="Dr. Bernard D. Aboba">
         <organization>Microsoft</organization>
      </author>
      <author initials="P." surname="Eronen" fullname="Pasi Eronen">
         <organization>Nokia</organization>
      </author>
      <date month="July" day="20" year="2005" />
      <abstract>
	 <t>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. &quot;Roaming&quot; 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 &quot;confederations&quot; 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]
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-radext-rfc2486bis-06" />
   
</reference>
