RFC 2888: Secure Remote Access with L2TP
In plain English — editorial summary, not part of the RFC
The objective of this document is to extend security characteristics of IPsec to remote access users, as they dial-in through the Internet. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2888
- Published
- August 2000
- Authors
- P. Srisuresh
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2442The Batch SMTP Media TypeCurrent
November 1998
- RFC 2341Cisco Layer Two Forwarding (Protocol) "L2F"Current
May 1998
- RFC 2884Performance Evaluation of Explicit Congestion Notification (ECN) in IP NetworksCurrent
July 2000
- RFC 2897Proposal for an MGCP Advanced Audio PackageCurrent
August 2000
- RFC 2963A Rate Adaptive Shaper for Differentiated ServicesCurrent
October 2000
- RFC 2798Definition of the inetOrgPerson LDAP Object ClassUpdated
April 2000
- RFC 2985PKCS #9: Selected Object Classes and Attribute Types Version 2.0Current
November 2000
- RFC 2774An HTTP Extension FrameworkCurrent
February 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?