One document matched: draft-ietf-roamops-roamreq-10.txt

Differences from draft-ietf-roamops-roamreq-09.txt

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


        RFC 2477:

        Title:      Criteria for Evaluating Roaming Protocols
	Author(s):  B. Aboba, G. Zorn
	Status:     Informational
	Date:       January 1999
        Mailbox:    bernarda@microsoft.com glennz@microsoft.com
	Pages:      12
        Characters: 23530
        Updates/Obsoletes/See Also: None 
        I-D Tag:    draft-ietf-roamops-roamreq-10.txt

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


This document describes requirements for the provisioning of "roaming
capability" for dialup Internet users.  "Roaming capability" is
defined as the ability to use multiple Internet service providers
(ISPs), while maintaining a formal, customer-vendor relationship with
only one.

This document is a product of the Roaming Operations Working Group of
the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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