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

Document Type Active Internet-Draft (individual)
Last updated 2020-03-16
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized 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                                                            J. Zhang
Internet-Draft                                         Tongji University
Intended status: Standards Track                                  K. Gao
Expires: 16 September 2020                            Sichuan University
                                                                 J. Wang
                                                                        
                                                                Q. Xiang
                                                               Y.R. Yang
                                                         Yale University
                                                           15 March 2020

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

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.

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 https://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 16 September 2020               [Page 1]
Internet-Draft                  ALTO-FCS                      March 2020

   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 16 September 2020.

Copyright Notice

   Copyright (c) 2020 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 (https://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
     1.1.  Requirement Language  . . . . . . . . . . . . . . . . . .   5
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   5
       1.2.1.  Flow  . . . . . . . . . . . . . . . . . . . . . . . .   5
       1.2.2.  Data Transmission Type  . . . . . . . . . . . . . . .   5
   2.  Overview of Approaches  . . . . . . . . . . . . . . . . . . .   5
     2.1.  Extended Endpoint Address . . . . . . . . . . . . . . . .   6
     2.2.  Flow-based Filter . . . . . . . . . . . . . . . . . . . .   6
     2.3.  Flow-specific Announcement  . . . . . . . . . . . . . . .   6
   3.  Extended Endpoint Address . . . . . . . . . . . . . . . . . .   7
     3.1.  Address Type  . . . . . . . . . . . . . . . . . . . . . .   7
     3.2.  Endpoint Address  . . . . . . . . . . . . . . . . . . . .   8
       3.2.1.  MAC Address . . . . . . . . . . . . . . . . . . . . .   8
       3.2.2.  Internet Domain Name  . . . . . . . . . . . . . . . .   8
       3.2.3.  IPv4 Socket Address . . . . . . . . . . . . . . . . .   8
       3.2.4.  IPv6 Socket Address . . . . . . . . . . . . . . . . .   8
     3.3.  Address Type Compatibility  . . . . . . . . . . . . . . .   9
     3.4.  Examples  . . . . . . . . . . . . . . . . . . . . . . . .   9
   4.  Flow-specific Announcement  . . . . . . . . . . . . . . . . .   9
     4.1.  Flow-specific Announcement Type . . . . . . . . . . . . .   9
Show full document text