Browse Prior Art Database

The Network Access Identifier (RFC2486)

IP.com Disclosure Number: IPCOM000003066D
Original Publication Date: 1999-Jan-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 6 page(s) / 13K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Aboba: AUTHOR [+2]

Abstract

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.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 21% of the total text.

Network Working Group B. Aboba

Request for Comments: 2486 Microsoft

Category: Standards Track M. 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 (C) The Internet Society (1999). All Rights Reserved.

1. Abstract

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.

2. Introduction

Considerable interest has arisen recently in a set of features that

fit within the general category of "roaming capability" for dialup

Internet users. Interested parties have included:

Regional Internet Service Providers (ISPs) operating within a

particular state or province, looking to combine their efforts

with those of other regional providers to offer dialup service

over a wider area.

National ISPs wishing to combine their operations with those of

one or more ISPs in another nation to offer more comprehensive

dialup service in a group of countries or on a continent.

Businesses desiring to offer their employees a comprehensive

package of dialup services on a global basis. Those services

may include Internet access as well as secure access to

corporate intranets via a Virtual Private Network (VPN), enabled

by tunneling protocols such as PPTP, L2F, L2TP, and IPSEC tunnel

mode.

In order to enhance the interoperability of roaming and tunneling...