RFC 2903: Generic AAA Architecture
In plain English — editorial summary, not part of the RFC
This memo proposes an Authentication, Authorization, Accounting (AAA) architecture that would incorporate a generic AAA server along with an application interface to a set of Application Specific Modules that could perform application specific AAA functions. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC2903
- Published
- August 2000
- Authors
- C. de Laat; G. Gross; L. Gommans; J. Vollbrecht; D. Spence
- Status
- EXPERIMENTAL
- Stream
- Legacy
- Area
- —
- Pages
- 26
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3169Criteria for Evaluating Network Access Server ProtocolsCurrent
September 2001
- RFC 3539Authentication, Authorization and Accounting (AAA) Transport ProfileCurrent
June 2003
- RFC 4441The IEEE 802/IETF RelationshipObsoleted
March 2006
- RFC 7155Diameter Network Access Server ApplicationCurrent
April 2014
- RFC 7241The IEEE 802/IETF RelationshipUpdated
July 2014
- RFC 7423Diameter Applications Design GuidelinesCurrent
November 2014
- RFC 9950A YANG Data Model for Terminal Access Controller Access-Control System Plus (TACACS+)Current
March 2026
- RFC 2904AAA Authorization FrameworkCurrent
August 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?