RFC 3127 on AAA Protocol Evaluation Process

RFC Editor <rfc-ed@ISI.EDU> Fri, 29 June 2001 23:36 UTC

Message-Id: <200106292309.f5TN9gG29181@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3127 on AAA Protocol Evaluation Process
Cc: rfc-ed@ISI.EDU, aaa-wg@merit.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 29 Jun 2001 16:09:42 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 3127

        Title:	    Authentication, Authorization, and Accounting:
                    Protocol Evaluation
        Author(s):  D. Mitton, M. St.Johns, S. Barkley, D. Nelson,
                    B. Patil, M. Stevens, B. Wolff
        Status:     Informational
	Date:       June 2001
        Mailbox:    dmitton@nortelnetworks.com,
                    stjohns@rainmakertechnologies.com,
                    stuartb@uu.net, dnelson@enterasys.com,
                    Basavaraj.Patil@nokia.com, mstevens@ellacoya.com,
                    barney@databus.com 
        Pages:      86
        Characters: 170579
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-aaa-proto-eval-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3127.txt


This memo represents the process and findings of the Authentication,
Authorization, and Accounting Working Group (AAA WG) panel evaluating
protocols proposed against the AAA Network Access Requirements, RFC
2989.  Due to time constraints of this report, this document is not as
fully polished as it might have been desired.  But it remains mostly
in this state to document the results as presented.

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 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 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/rfc3127.txt"><ftp://ftp.isi.edu/in-notes/rfc3127.txt>

RFC 3127 on AAA Protocol Evaluation Process RFC Editor