RFC 2868: RADIUS Attributes for Tunnel Protocol Support
In plain English — editorial summary, not part of the RFC
This document defines a set of RADIUS (Remote Authentication Dial In User Service) attributes designed to support the provision of compulsory tunneling in dial-up networks. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2868
- Published
- June 2000
- Authors
- G. Zorn; D. Leifer; A. Rubens; J. Shriver; M. Holdrege; I. Goyret
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 20
- Also known as
- —
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 2869RADIUS ExtensionsUpdated
June 2000
- RFC 2138Remote Authentication Dial In User Service (RADIUS)Obsoleted
April 1997
- RFC 3579RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP)Updated
September 2003
- RFC 2058Remote Authentication Dial In User Service (RADIUS)Obsoleted
January 1997
- RFC 2607Proxy Chaining and Policy Implementation in RoamingCurrent
June 1999
- RFC 2867RADIUS Accounting Modifications for Tunnel Protocol SupportCurrent
June 2000
- RFC 2889Benchmarking Methodology for LAN Switching DevicesCurrent
August 2000
- RFC 3127Authentication, Authorization, and Accounting: Protocol EvaluationCurrent
June 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?