Traffic classification in end-system IP VPNs.
draft-marques-sdnp-flow-spec-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Pedro Marques , Luyuan Fang , Ping Pan , Amit Shukla , Maria Napierala | ||
| Last updated | 2012-10-12 (Latest revision 2012-04-10) | ||
| 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
When IP VPNs are used to interconnect end-systems [I-D.marques-l3vpn- end-system] it may be desirable to introduce traffic control rules at a finer level of granularity than an IP destination address. This document extends the end-system IP VPN specification with support for fine grain traffic classification, filtering and redirection rules. It applies the existing BGP IP VPN flow specification dissemination mechanism [RFC5575] to end-system IP VPNs in order to provide the ability to control IP packets that match a specific pattern, which may include fields other than the IP destination address.
Authors
Pedro Marques
Luyuan Fang
Ping Pan
Amit Shukla
Maria Napierala
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)