RFC 2882: Network Access Servers Requirements: Extended RADIUS Practices
In plain English — editorial summary, not part of the RFC
This document describes current practices implemented in NAS products that go beyond the scope of the RADIUS (Remote Authentication Dial In User Service) RFCs 2138, 2139. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2882
- Published
- July 2000
- Authors
- D. Mitton
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2881Network Access Server Requirements Next Generation (NASREQNG) NAS ModelCurrent
July 2000
- RFC 2809Implementation of L2TP Compulsory Tunneling via RADIUSCurrent
April 2000
- RFC 2866RADIUS AccountingUpdated
June 2000
- RFC 3169Criteria for Evaluating Network Access Server ProtocolsCurrent
September 2001
- RFC 2548Microsoft Vendor-specific RADIUS AttributesCurrent
March 1999
- RFC 2059RADIUS AccountingObsoleted
January 1997
- RFC 2869RADIUS ExtensionsUpdated
June 2000
- RFC 2868RADIUS Attributes for Tunnel Protocol SupportUpdated
June 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?