Network Working GroupB. Aboba
Request for Comments: 2486Microsoft Corporation
Category: Standards TrackM. Beadles
 WorldCom Advanced Networks
 January 1999

The Network Access Identifier

Status of this Memo

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 © The Internet Society (1999). All Rights Reserved.


In order to enhance the interoperability of roaming and tunneling services, it is desirable to have a standardized method for identifying users. This document proposes syntax for the Network Access Identifier (NAI), the userID submitted by the client during PPP authentication. It is expected that this will be of interest for support of roaming as well as tunneling. "Roaming capability" 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.

1.  not available

2. References

[RFC2194] Aboba, B., Lu, J., Alsop, J., Ding, J., and W. Wang, “Review of Roaming Implementations,” RFC 2194, September 1997 (TXT).
[RFC2138] Rigney, C., Rigney, C., Rubens, A., Simpson, W., and S. Willens, “Remote Authentication Dial In User Service (RADIUS),” RFC 2138, April 1997 (TXT, HTML, XML).
[RFC2139] Rigney, C. and C. Rigney, “RADIUS Accounting,” RFC 2139, April 1997 (TXT, HTML, XML).
[RFC1035] Mockapetris, P., “Domain names - implementation and specification,” STD 13, RFC 1035, November 1987 (TXT).
[RFC0821] Postel, J., “Simple Mail Transfer Protocol,” STD 10, RFC 821, August 1982 (TXT).
[RFC2052] Gulbrandsen, A. and P. Vixie, “A DNS RR for specifying the location of services (DNS SRV),” RFC 2052, October 1996 (TXT).
[RFC2234] Crocker, D., Ed. and P. Overell, “Augmented BNF for Syntax Specifications: ABNF,” RFC 2234, November 1997 (TXT, HTML, XML).
[RFC2401] Kent, S. and R. Atkinson, “Security Architecture for the Internet Protocol,” RFC 2401, November 1998 (TXT, HTML, XML).
[RFC2119] Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” BCP 14, RFC 2119, March 1997 (TXT, HTML, XML).

Authors' Addresses

  Bernard Aboba
  Microsoft Corporation
  One Microsoft Way
  Redmond, WA 98052
Phone:  +1 425 936 6605
Email:  bernarda@microsoft.com
  Mark A. Beadles
  WorldCom Advanced Networks
  5000 Britton Rd.
  Hilliard, OH 43026
Phone:  +1 614 723 1941
Email:  mbeadles@wcom.net

Full Copyright Statement

Intellectual Property