Support for RSVP-TE in L3VPNs
draft-kumaki-murai-ccamp-rsvp-te-l3vpn-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Kenji Kumaki , Tomoki Murai , Tomohiro Yamagata , Chikara Sasaki | ||
| Last updated | 2010-07-12 | ||
| 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
IP Virtual Private Networks (VPNs) provide connectivity between sites across an IP backbone. These VPNs can be supported using BGP/MPLS and the connections can be created by using MPLS Traffic Engineered (TE) Label Switched Paths (LSPs). New RSVP-TE extensions are required to support multiple MPLS-TE based BGP/MPLS IP-VPNs that are interconnected via the same Provider Edge (PE) routers. These extensions are necessary so that RSVP control messages from the Customer Edge (CE) equipment, such as Path messages and Resv messages, are appropriately handled by the PE routers. This document defines the procedure and objects that enable a PE router to distinguish between BGP/MPLS IP-VPNs.
Authors
Kenji Kumaki
Tomoki Murai
Tomohiro Yamagata
Chikara Sasaki
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)