One document matched: draft-ietf-roamops-nai-12.txt

Differences from draft-ietf-roamops-nai-11.txt

A new Request for Comments is now available in online RFC libraries.


        RFC 2486:

        Title:	    The Network Access Identifier
	Author(s):  B. Aboba, M. Beadles
	Status:     Proposed Standard
	Date:       January 1999
        Mailbox:    bernarda@microsoft.com, mbeadles@wcom.net
	Pages:      8
        Characters: 14261
        Updates/Obsoletes/See Also: None    
        I-D Tag:    draft-ietf-roamops-nai-12.txt

	
        URL:        ftp://ftp.isi.edu/in-notes/rfc2486.txt


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 document is a product of the Roaming Operations Working Group of
the IETF.

This is now a Proposed Standard Protocol.

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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute