RFC 3193: Securing L2TP using IPsec
In plain English — editorial summary, not part of the RFC
This document discusses how L2TP (Layer Two Tunneling Protocol) may utilize IPsec to provide for tunnel authentication, privacy protection, integrity checking and replay protection. Both the voluntary and compulsory tunneling cases are discussed. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3193
- Published
- November 2001
- Authors
- B. Patel; B. Aboba; W. Dixon; G. Zorn; S. Booth
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 28
- 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 3308Layer Two Tunneling Protocol (L2TP) Differentiated Services ExtensionCurrent
November 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 3931Layer Two Tunneling Protocol - Version 3 (L2TPv3)Updated
March 2005
- RFC 2661Layer Two Tunneling Protocol "L2TP"Updated
August 1999
- RFC 4301Security Architecture for the Internet ProtocolUpdated
December 2005
- RFC 4302IP Authentication HeaderCurrent
December 2005
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?