Encapsulating MPLS in IPsec
draft-raggarwa-mpls-ipsec-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Rahul Aggarwal | ||
| Last updated | 2004-01-27 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
In various applications of MPLS, label stacks with multiple entries are used. In some cases, it is possible to replace the top label of the stack with an IP-based encapsulation, thereby enabling the application to run over networks which do not have MPLS enabled in their core routers. MPLS-in-IP and MPLS-in-GRE encapsulations have already been specified by the MPLS WG. In some cases, in addition to IP and GRE tunnels, it may be desirable to use IPsec for transporting MPLS packets securely over non-MPLS networks, using standard IPsec authentication and/or encryption functions. This draft describes procedures for encapsulating MPLS packets in IPsec.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)