Dynamic Path Selection use-cases
draft-arumuganainar-rtgwg-dps-use-cases-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Arun Arumuganainar | ||
| Last updated | 2015-04-07 (Latest revision 2014-10-04) | ||
| 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
Dynamic Path Selection is framework for offloading certain applications traffic that are considered not-so-critical by the network administrator on to a secondary paths ( The paths that are not considered best by routing protocols ). The frame work for implementing such a offloading mechanism is clearly defined in the draft draft-arumuganainar-rtgwg-DPS-requirements-01. This draft describes the use cases for DPS in brief.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)