Layer Two Tunneling Protocol 'L2TP' Multi-Protocol Label Switching Extension
draft-ietf-l2tpext-mpls-00
Document | Type |
Expired Internet-Draft
(l2tpext WG)
Expired & archived
|
|
---|---|---|---|
Authors | Ken Peirce , Pat R. Calhoun | ||
Last updated | 2000-03-03 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The L2TP document [1] defines the base protocol which describes the method of tunneling PPP data. The L2TP base protocol does not address any MPLS extensions. The goal of MPLS is to speed forwarding of packets by reducing the lookup required in routing. This draft proposes a method to allow L2TP Data Sessions to be assigned an MPLS Label Switched Path Id (LSPID)[3] for an explicit route (ER). Assignment of such an ER is necessary for traffic engineering.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)