RFC 2905: AAA Authorization Application Examples
In plain English — editorial summary, not part of the RFC
This memo describes several examples of applications requiring authorization. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2905
- Published
- August 2000
- Authors
- J. Vollbrecht; P. Calhoun; S. Farrell; L. Gommans; G. Gross; B. de Bruijn; C. de Laat; M. Holdrege; D. Spence
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 53
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2906AAA Authorization RequirementsCurrent
August 2000
- RFC 2904AAA Authorization FrameworkCurrent
August 2000
- RFC 2903Generic AAA ArchitectureCurrent
August 2000
- RFC 3141CDMA2000 Wireless Data Requirements for AAACurrent
June 2001
- RFC 2989Criteria for Evaluating AAA Protocols for Network AccessCurrent
November 2000
- 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
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?