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

Document Type Active Internet-Draft (individual)
Last updated 2017-12-12
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
ALTO WG                                                         J. Zhang
Internet-Draft                                         Tongji University
Intended status: Standards Track                                  K. Gao
Expires: June 16, 2018                               Tsinghua University
                                                                 J. Wang
                                                       Tongji University
                                                                Q. Xiang
                                                  Tongji/Yale University
                                                                 Y. Yang
                                                         Yale University
                                                       December 13, 2017

                 ALTO Extension: Flow-based Cost Query
                       draft-gao-alto-fcs-04.txt

Abstract

   The ALTO cost query service maps a source-destination pair into a
   cost value, which provides a network view abstract based on a subset
   of the 2-dimension address space.  Given that the emergence of new
   networking optimization requirements, such a query space is not
   sufficient to uniquely identify a flow.  To address the limitations
   of the network information query space provided by the legacy ALTO
   protocol, this document introduces two extensions: extending the
   existing ALTO cost query services with fine-grained semantics, and
   enabling a new flow-based query service named Flow Cost Service.
   These extensions move ALTO to a more flexible and expressive network
   information query space.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any

Zhang, et al.             Expires June 16, 2018                 [Page 1]
Internet-Draft              Flow Cost Service              December 2017

   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on June 16, 2018.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Overview of Approaches  . . . . . . . . . . . . . . . . . . .   5
     3.1.  Flexible Flow-based Filter  . . . . . . . . . . . . . . .   5
     3.2.  Extended Endpoint Address . . . . . . . . . . . . . . . .   5
     3.3.  Mapping Flow Attributes to Cost . . . . . . . . . . . . .   5
   4.  Changes Since Version -01 . . . . . . . . . . . . . . . . . .   6
   5.  ALTO Flow Cost Specification: Basic Flow-based Query  . . . .   6
     5.1.  Flow-based Filtered Cost Map  . . . . . . . . . . . . . .   7
       5.1.1.  Capabilities  . . . . . . . . . . . . . . . . . . . .   7
       5.1.2.  Accept Input Parameters . . . . . . . . . . . . . . .   7
       5.1.3.  Response  . . . . . . . . . . . . . . . . . . . . . .   8
     5.2.  Extended Endpoint Address Encoding  . . . . . . . . . . .   8
       5.2.1.  Address Type  . . . . . . . . . . . . . . . . . . . .   8
       5.2.2.  Address Type Conflict . . . . . . . . . . . . . . . .   9
       5.2.3.  Endpoint Address  . . . . . . . . . . . . . . . . . .   9
       5.2.4.  Extended Endpoint Address Examples  . . . . . . . . .  10
     5.3.  Flow-based Endpoint Cost Service  . . . . . . . . . . . .  10
       5.3.1.  Capabilities  . . . . . . . . . . . . . . . . . . . .  10
       5.3.2.  Accept Input Parameters . . . . . . . . . . . . . . .  11
       5.3.3.  Response  . . . . . . . . . . . . . . . . . . . . . .  11
Show full document text