RFC 2906 on AAA Authorization Requirements

RFC Editor <rfc-ed@ISI.EDU> Fri, 01 September 2000 01:32 UTC

Message-Id: <200008312333.QAA21799@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2906 on AAA Authorization Requirements
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 31 Aug 2000 16:33:38 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2906

        Title:	    AAA Authorization Requirements
        Author(s):  S. Farrell, J. Vollbrecht, P. Calhoun, L. Gommans,
                    G. Gross, B. de Bruijn, C. de Laat, M. Holdrege,
                    D. Spence 
        Status:     Informational
	Date:       August 2000
        Mailbox:    stephen.farrell@baltimore.ie,
                    jrv@interlinknetworks.com,
                    pcalhoun@eng.sun.com, gommans@cabletron.com,
                    gmgross@lucent.com, betty@euronet.nl,
                    delaat@phys.uu.nl, matt@ipverse.com,
                    dspence@interlinknetworks.com
        Pages:      23
        Characters: 48618
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-irtf-aaaarch-authorization-reqs-01.txt

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


This document specifies the requirements that Authentication
Authorization Accounting (AAA) protocols must meet in order to support
authorization services in the Internet. The requirements have been
elicited from a study of a range of applications including mobile-IP,
roamops and others.

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

RFC 2906 on AAA Authorization Requirements RFC Editor