QoS considerations for L3 PPVPNs
draft-declercq-ppvpn-l3vpn-qos-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jeremy De Clercq | ||
| Last updated | 2003-02-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
Although QoS is identified as a very important requirement for L3 PPVPNs (see for example [PPVPN-REQ]), the proposed L3 PPVPN solutions ([2547bis], [VR], [CE-based]) have paid very little attention to describing how the proposed approach fulfills the QoS requirements. This document explores different points of view, describes dependencies and orthogonalities, and details a number of solutions and guidelines.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)