RFC 3308: Layer Two Tunneling Protocol (L2TP) Differentiated Services Extension
In plain English — editorial summary, not part of the RFC
The Layer Two Tunneling Protocol (L2TP) provides a standard method for tunneling PPP packets. The current specification provides no provisions for supporting Differentiated Services (diffserv) over the L2TP control connection or subsequent data sessions. As a result, no standard mechanism currently exists within L2TP to provide L2TP protocol negotiations for service discrimination.
Document record
- Document ID
- RFC3308
- Published
- November 2002
- Authors
- P. Calhoun; W. Luo; D. McPherson; K. Peirce
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3301Layer Two Tunnelling Protocol (L2TP): ATM access network extensionsCurrent
June 2002
- RFC 3355Layer Two Tunnelling Protocol (L2TP) Over ATM Adaptation Layer 5 (AAL5)Current
September 2002
- RFC 3371Layer Two Tunneling Protocol "L2TP" Management Information BaseCurrent
September 2002
- RFC 3193Securing L2TP using IPsecCurrent
November 2001
- RFC 3931Layer Two Tunneling Protocol - Version 3 (L2TPv3)Updated
March 2005
- RFC 3248A Delay Bound alternative revision of RFC 2598Current
March 2002
- RFC 3140Per Hop Behavior Identification CodesCurrent
June 2001
- RFC 2661Layer Two Tunneling Protocol "L2TP"Updated
August 1999
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?