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

Document Type Active Internet-Draft (individual)
Last updated 2017-06-26
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                                                           K. Gao
Internet-Draft                                       Tsinghua University
Intended status: Standards Track                                J. Zhang
Expires: December 27, 2017                                       J. Wang
                                                       Tongji University
                                                                Q. Xiang
                                                  Tongji/Yale University
                                                                 Y. Yang
                                                         Yale University
                                                           June 25, 2017

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

Abstract

   The emergence of new networking datapath capabilities has
   substantially increased the flexibility of networking.  For example,
   OpenFlow has emerged as a major southbound protocol for Software-
   Defined Networking, and OpenFlow allows flexible routing beyond
   simple destination-based routing.  In this document, we define a new
   extention to ALTO, namely the Flow Cost Service, for ALTO clients in
   an OpenFlow-enabled network to query ALTO network information.

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
   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 December 27, 2017.

Gao, et al.             Expires December 27, 2017               [Page 1]
Internet-Draft              Flow Cost Service                  June 2017

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.  Changes Since Version -01 . . . . . . . . . . . . . . . . . .   4
   3.  ALTO Flow Cost Specification: Basic Flow-based Query  . . . .   4
     3.1.  Flow-based Filtered Cost Map  . . . . . . . . . . . . . .   4
       3.1.1.  Capabilities  . . . . . . . . . . . . . . . . . . . .   4
       3.1.2.  Accept Input Parameters . . . . . . . . . . . . . . .   5
       3.1.3.  Response  . . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  Extend Endpoint Encoding  . . . . . . . . . . . . . . . .   6
       3.2.1.  Protocol  . . . . . . . . . . . . . . . . . . . . . .   6
       3.2.2.  EndpointName  . . . . . . . . . . . . . . . . . . . .   6
       3.2.3.  Port  . . . . . . . . . . . . . . . . . . . . . . . .   7
       3.2.4.  EndpointURI Example . . . . . . . . . . . . . . . . .   7
     3.3.  Flow-based Endpoint Cost Service  . . . . . . . . . . . .   7
       3.3.1.  Capabilities  . . . . . . . . . . . . . . . . . . . .   7
       3.3.2.  Accept Input Parameters . . . . . . . . . . . . . . .   8
       3.3.3.  Response  . . . . . . . . . . . . . . . . . . . . . .   8
     3.4.  Example . . . . . . . . . . . . . . . . . . . . . . . . .   8
       3.4.1.  IRD Example . . . . . . . . . . . . . . . . . . . . .   9
       3.4.2.  Flow-based Filtered Cost Map Service Example  . . . .  10
       3.4.3.  Flow-based Endpoint Cost Service Example  . . . . . .  11
   4.  ALTO Flow Cost Specification: Advanced Flow-based Query . . .  12
     4.1.  Basic Data Types  . . . . . . . . . . . . . . . . . . . .  12
Show full document text