Skip to main content

Layer Two Tunneling Protocol (L2TP) over Frame Relay

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3070.
Authors Suhail Nanji , Rohit verma , Rene Tio , Vipin Rawat
Last updated 2013-03-02 (Latest revision 2000-11-28)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3070 (Proposed Standard)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3070

        Title:      Layer Two Tunneling Protocol (L2TP) over Frame
        Author(s):  V. Rawat, R. Tio, S. Nanji, R. Verma
        Status:     Standards Track
        Date:       February 2001
        Pages:      7
        Characters: 12940
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-l2tpext-fr-01.txt


Layer Two Tunneling Protocol (L2TP) describes a mechanism to tunnel
Point-to-Point (PPP) sessions.  The protocol has been designed to be
independent of the media it runs over.  The base specification
describes how it should be implemented to run over the User Datagram
Protocol (UDP) and the Internet Protocol (IP).  This document
describes how L2TP is implemented over Frame Relay Permanent Virtual
Circuits (PVCs) and Switched Virtual Circuits (SVCs).

This document is a product of the Layer Two Tunneling Protocol
Extensions Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.