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

Document Type Active Internet-Draft (individual)
Last updated 2018-07-02
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: January 3, 2019                             Tsinghua University
                                                                 J. Wang
                                                       Tongji University
                                                                Q. Xiang
                                                  Tongji/Yale University
                                                                 Y. Yang
                                                         Yale University
                                                            July 2, 2018

                 ALTO Extension: Flow-based Cost Query
                       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.

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.

Zhang, et al.            Expires January 3, 2019                [Page 1]
Internet-Draft              Flow Cost Service                  July 2018

   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
   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 January 3, 2019.

Copyright Notice

   Copyright (c) 2018 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 . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Flow  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Data Transmission Type  . . . . . . . . . . . . . . . . .   5
   3.  Overview of Approaches  . . . . . . . . . . . . . . . . . . .   5
     3.1.  Extended Endpoint Address . . . . . . . . . . . . . . . .   5
     3.2.  Flow-based Filter . . . . . . . . . . . . . . . . . . . .   6
     3.3.  Flow-specific Announcement  . . . . . . . . . . . . . . .   6
   4.  Change Logs . . . . . . . . . . . . . . . . . . . . . . . . .   7
   5.  Extended Endpoint Address . . . . . . . . . . . . . . . . . .   8
     5.1.  Address Type  . . . . . . . . . . . . . . . . . . . . . .   8
     5.2.  Endpoint Address  . . . . . . . . . . . . . . . . . . . .   9
       5.2.1.  MAC Address . . . . . . . . . . . . . . . . . . . . .   9
       5.2.2.  Internet Domain Name  . . . . . . . . . . . . . . . .   9
       5.2.3.  IPv4 Socket Address . . . . . . . . . . . . . . . . .   9
       5.2.4.  IPv6 Socket Address . . . . . . . . . . . . . . . . .   9
Show full document text