ALTO Extension: Flow-based Cost Query
draft-gao-alto-fcs-06

Document Type Expired Internet-Draft (individual)
Last updated 2019-01-03 (latest revision 2018-07-02)
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 Expired
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-gao-alto-fcs-06.txt

Abstract

ALTO cost maps and endpoint cost services map a source-destination pair into a cost value. However, current filter specifications, which define the set of source-destination pairs in an ALTO query, have two limitations: 1) Only very limited address types are supported (IPv4 and IPv6), which is not sufficient to uniquely identify a flow in networks with fine-grained routing, such as the emerging Software Defined Networks; 2) The base ALTO protocol only defines filters enumerating all sources and all destinations, leading to redundant information in the response; 3) Cannot distinguish transmission types of flows in the query, which makes the server hard to respond the accurate resource consumption. To address these three issues, this document extends the base ALTO protocol with a more fine-grained filter type which allows ALTO clients to select only the concerned source-destination pairs and announce the flow-specific information like data transmission type, and a more expressive address space which allows ALTO clients to make queries beyond the limited IP addresses.

Authors

J. Zhang (jingxuan.n.zhang@gmail.com)
Kai Gao (gaok12@mails.tsinghua.edu.cn)
Junzhuo Wang (wangjunzhuo200@gmail.com)
Qiao Xiang (qiao.xiang@cs.yale.edu)
Yang Yang (yry@cs.yale.edu)

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