RFC 3575: IANA Considerations for RADIUS (Remote Authentication Dial In User Service)
In plain English — editorial summary, not part of the RFC
This document describes the IANA considerations for the Remote Authentication Dial In User Service (RADIUS). [STANDARDS-TRACK]
Document record
- Document ID
- RFC3575
- Published
- July 2003
- Authors
- B. Aboba
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 8
- Also known as
- —
- Updated by:
- RFC 6929
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3579RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP)Updated
September 2003
- RFC 2869RADIUS ExtensionsUpdated
June 2000
- RFC 2867RADIUS Accounting Modifications for Tunnel Protocol SupportCurrent
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 3692Assigning Experimental and Testing Numbers Considered UsefulCurrent
January 2004
- RFC 3737IANA Guidelines for the Registry of Remote Monitoring (RMON) MIB modulesCurrent
April 2004
- RFC 3169Criteria for Evaluating Network Access Server ProtocolsCurrent
September 2001
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?