RFC 2809: Implementation of L2TP Compulsory Tunneling via RADIUS
In plain English — editorial summary, not part of the RFC
This document discusses implementation issues arising in the provisioning of compulsory tunneling in dial-up networks using the L2TP (Layer Two Tunneling Protocol) protocol. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2809
- Published
- April 2000
- Authors
- B. Aboba; G. Zorn
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2866RADIUS AccountingUpdated
June 2000
- RFC 2548Microsoft Vendor-specific RADIUS AttributesCurrent
March 1999
- RFC 2059RADIUS AccountingObsoleted
January 1997
- RFC 2882Network Access Servers Requirements: Extended RADIUS PracticesCurrent
July 2000
- RFC 2621RADIUS Accounting Server MIBObsoleted
June 1999
- RFC 2620RADIUS Accounting Client MIBObsoleted
June 1999
- RFC 2619RADIUS Authentication Server MIBObsoleted
June 1999
- RFC 2139RADIUS AccountingObsoleted
April 1997
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?