[rfc-dist] RFC 4817 on Encapsulation of MPLS over Layer 2 Tunneling Protocol Version 3
rfc-editor at rfc-editor.org
Thu Mar 29 17:57:28 PDT 2007
A new Request for Comments is now available in online RFC libraries.
Title: Encapsulation of MPLS over Layer
2 Tunneling Protocol Version 3
Author: M. Townsley, C. Pignataro,
S. Wainner, T. Seely,
Status: Standards Track
Date: March 2007
Mailbox: mark at townsley.net,
cpignata at cisco.com,
swainner at cisco.com, tseely at sprint.net,
young at jsyoung.net
I-D Tag: draft-ietf-mpls-over-l2tpv3-03.txt
The Layer 2 Tunneling Protocol, Version 3 (L2TPv3) defines a
protocol for tunneling a variety of payload types over IP networks.
This document defines how to carry an MPLS label stack and its
payload over the L2TPv3 data encapsulation. This enables an
application that traditionally requires an MPLS-enabled core network,
to utilize an L2TPv3 encapsulation over an IP network instead.
This document is a product of the Multiprotocol Label Switching
Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: 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
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 at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
More information about the rfc-dist