ALTO Extension: Path Vector Cost Mode
draft-yang-alto-path-vector-04

Document Type Replaced Internet-Draft (individual)
Last updated 2017-03-13
Replaced by draft-ietf-alto-path-vector
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-alto-path-vector
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-yang-alto-path-vector-04.txt

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 Bernstein (gregb@grotto-networking.com)
Shiwei Chen (dawn_chen_f@hotmail.com)
Kai Gao (gaok12@mails.tsinghua.edu.cn)
Young Lee (leeyoung@huawei.com)
Wendy Roome (wendy.roome@nokia.com)
Michael Scharf (michael.scharf@nokia.com)
Yang Yang (yry@cs.yale.edu)
J. Zhang (jingxuan.n.zhang@gmail.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)