Browse Prior Art Database

Layer Two Tunneling Protocol - Version 3 (L2TPv3) (RFC3931)

IP.com Disclosure Number: IPCOM000088361D
Original Publication Date: 2005-Mar-01
Included in the Prior Art Database: 2005-Mar-04

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Lau: AUTHOR [+6]

Abstract

This document describes "version 3" of the Layer Two Tunneling Protocol (L2TPv3). L2TPv3 defines the base control protocol and encapsulation for tunneling multiple Layer 2 connections between two IP nodes. Additional documents detail the specifics for each data link type being emulated.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 1% of the total text.

Network Working Group                                        J. Lau, Ed.

Request for Comments: 3931                              M. Townsley, Ed.

Category: Standards Track                                  Cisco Systems

                                                          I. Goyret, Ed.

                                                     Lucent Technologies

                                                              March 2005

           Layer Two Tunneling Protocol - Version 3 (L2TPv3)

Status of this Memo

   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.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   This document describes "version 3" of the Layer Two Tunneling

   Protocol (L2TPv3).  L2TPv3 defines the base control protocol and

   encapsulation for tunneling multiple Layer 2 connections between two

   IP nodes.  Additional documents detail the specifics for each data

   link type being emulated.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3

       1.1.  Changes from RFC 2661. . . . . . . . . . . . . . . . . .  4

       1.2.  Specification of Requirements. . . . . . . . . . . . . .  4

       1.3.  Terminology. . . . . . . . . . . . . . . . . . . . . . .  5

   2.  Topology . . . . . . . . . . . . . . . . . . . . . . . . . . .  8

   3.  Protocol Overview. . . . . . . . . . . . . . . . . . . . . . .  9

       3.1.  Control Message Types. . . . . . . . . . . . . . . . . . 10

       3.2.  L2TP Header Formats. . . . . . . . . . . . . . . . . . . 11

             3.2.1.  L2TP Control Message Header. . . . . . . . . . . 11

             3.2.2.  L2TP Data Message. . . . . . . . . . . . . . . . 12

       3.3.  Control Connection Management. . . . . . . . . . . . . . 13

             3.3.1.  Control Connection Establishment . . . . . . . . 14

             3.3.2.  Control Connection Teardown. . . . . . . . . . . 14

       3.4.  Session Management . . . . . . . . . . . . . . . . . . . 15

             3.4.1.  Session Establishment for an Incoming Call . . . 15

             3.4.2.  Session Establishment for an Outgoing Call . . . 15

Lau, et al.                 Standards Track                     [Page 1]

RFC...