LDP based VPN Traffic classification
draft-vijay-mpls-ldp-vpn-class-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | C Vijayanand | ||
| Last updated | 2003-08-29 | ||
| 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
This document describes the use of LDP in establishing VPNs for transporting traffic that needs to be classified based on application flows. This document proposes extensions to existing LDP for establishing end-to-end VPN LSPs for transporting traffic meant for specific destination addresses and applications from specific applications. This document proposes to use a Flow FEC element, which contains the Layer 3 and transport information which is used for identifying the flow. The flow is mapped onto the appropriate VPN LSP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)