ALTO Extension: Abstract Path Vector as a Cost Mode
draft-yang-alto-path-vector-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Greg M. Bernstein , Young Lee , Wendy Roome , Michael Scharf , Y. Richard Yang | ||
| Last updated | 2016-01-07 (Latest revision 2015-07-06) | ||
| Replaced by | draft-ietf-alto-path-vector, draft-ietf-alto-path-vector, draft-ietf-alto-path-vector, draft-ietf-alto-path-vector, RFC 9275 | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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
The Application-Layer Traffic Optimization (ALTO) Service has defined network and cost maps to provide basic network information, where the cost maps allow only scalar (numerical or ordinal) cost mode values. This document introduces a new cost mode called path-vector to allow ALTO clients to better distinguish cost information. This document starts with a non-normative use case called multi-flow scheduling to illustrate that ALTO cost maps without path vectors cannot provide sufficient information. This document then defines path-vector as a new cost mode.
Authors
Greg M. Bernstein
Young Lee
Wendy Roome
Michael Scharf
Y. Richard Yang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)