ALTO Extension: Path Vector Cost Mode
draft-yang-alto-path-vector-03
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
---|---|---|---|
Authors | Greg M. Bernstein , Kai Gao , Young Lee , Wendy Roome , Michael Scharf , Y. Richard Yang | ||
Last updated | 2017-01-09 (Latest revision 2016-07-08) | ||
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 | |||
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 support use cases such as capacity regions for applications. This document starts with a non-normative example called multi-flow scheduling (or capacity region) 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
Kai Gao
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.)