RFC 2869: RADIUS Extensions
In plain English — editorial summary, not part of the RFC
This document describes additional attributes for carrying authentication, authorization and accounting information between a Network Access Server (NAS) and a shared Accounting Server using the Remote Authentication Dial In User Service (RADIUS) protocol described in RFC 2865 and RFC 2866. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2869
- Published
- June 2000
- Authors
- C. Rigney; W. Willats; P. Calhoun
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 47
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2868RADIUS Attributes for Tunnel Protocol SupportUpdated
June 2000
- RFC 2138Remote Authentication Dial In User Service (RADIUS)Obsoleted
April 1997
- RFC 2058Remote Authentication Dial In User Service (RADIUS)Obsoleted
January 1997
- RFC 2607Proxy Chaining and Policy Implementation in RoamingCurrent
June 1999
- RFC 3575IANA Considerations for RADIUS (Remote Authentication Dial In User Service)Updated
July 2003
- RFC 2867RADIUS Accounting Modifications for Tunnel Protocol SupportCurrent
June 2000
- RFC 2865Remote Authentication Dial In User Service (RADIUS)Updated
June 2000
- RFC 2889Benchmarking Methodology for LAN Switching DevicesCurrent
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?