RFC 3539: Authentication, Authorization and Accounting (AAA) Transport Profile
In plain English — editorial summary, not part of the RFC
This document discusses transport issues that arise within protocols for Authentication, Authorization and Accounting (AAA). It also provides recommendations on the use of transport by AAA protocols. This includes usage of standards-track RFCs as well as experimental proposals. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3539
- Published
- June 2003
- Authors
- B. Aboba; J. Wood
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 41
- 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 7155Diameter Network Access Server ApplicationCurrent
April 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 2989Criteria for Evaluating AAA Protocols for Network AccessCurrent
November 2000
- RFC 2903Generic AAA ArchitectureCurrent
August 2000
- RFC 4441The IEEE 802/IETF RelationshipObsoleted
March 2006
- RFC 5779Diameter Proxy Mobile IPv6: Mobile Access Gateway and Local Mobility Anchor Interaction with Diameter ServerCurrent
February 2010
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?