RFC 2989 on Network Access AAA Evaluation Criteria

[RFC Editor <[e-mail]>]

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


        RFC 2989

        Title:	    Criteria for Evaluating AAA Protocols for Network
                    Access 
        Author(s):  B. Aboba, P. Calhoun, S. Glass, T. Hiller,
                    P. McCann, H. Shiino, G. Zorn, G. Dommety,
                    C. Perkins, B. Patil, D. Mitton, S. Manning,
                    M. Beadles, P. Walsh, X. Chen, 
                    S. Sivalingham, A. Hameed, M. Munson, S. Jacobs,
                    B. Lim, B. Hirschman, R. Hsu, Y. Xu,
                    E. Campbell, S. Baba, E. Jaques 
        Status:     Informational
	Date:       November 2000
        Mailbox:    [e-mail], [e-mail],
                    [e-mail], [e-mail],
                    [e-mail], [e-mail],
                    [e-mail], [e-mail],
                    [e-mail],
                    [e-mail],
                    [e-mail],
                    [e-mail],
                    [e-mail], [e-mail],
                    [e-mail], 
                    [e-mail],
                    [e-mail], [e-mail],
                    [e-mail],
                    [e-mail], [e-mail],
                    [e-mail],
                    [e-mail], [e-mail],
                    [e-mail], [e-mail],
                    [e-mail] 
        Pages:      29
        Characters: 53197
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-aaa-na-reqts-07.txt

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


This document represents a summary of Authentication, Authorization,
Accounting (AAA) protocol requirements for network access.  In
creating this document, inputs were taken from documents produced by
the Network Access Server Requirements Next Generation (NASREQ),
Roaming Operations (ROAMOPS), and MOBILEIP working groups, as well as
from TIA 45.6.  This document summarizes the requirements collected
from those sources, separating requirements for authentication,
authorization and accounting.  Details on the requirements are
available in the original documents. 

This document is a product of the Authentication, Authorization and
Accounting 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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc2989.txt"><ftp://ftp.isi.edu/in-notes/rfc2989.txt>