ALTO Extension: Endpoint Cost Service for Flows
draft-wang-alto-ecs-flows-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-10-19
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 Working Group                                         Junzhuo. Wang
Internet-Draft                                         Tongji University
Intended status: Standards Track                             Qiao. Xiang
Expires: April 21, 2016                           Tongji/Yale University
                                                        October 19, 2015

            ALTO Extension: Endpoint Cost Service for Flows
                      draft-wang-alto-ecs-flows-00

Abstract

   The Endpoint Cost Service (ECS) has limitations to illustrate the
   network condition and to work with the OpenFlow protocol.  This
   document extends ECS to improve the Application-Layer Traffic
   Optimization (ALTO) protocol by defining more types of endpoint
   address such as port number, protocol type, domain and etc.

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 April 21, 2016.

Copyright Notice

   Copyright (c) 2015 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

Wang & Xiang             Expires April 21, 2016                 [Page 1]
Internet-Draft                  ECS Flow                    October 2015

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Motivations . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Overview Of Approach  . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Multi-Field Typed Endpoint Address Format . . . . . . . .   5
     3.2.  Compatibility With Legacy Clients . . . . . . . . . . . .   6
     3.3.  Endpoint Cost Resources . . . . . . . . . . . . . . . . .   6
   4.  Protocol Extension for Flow-Extended ECS  . . . . . . . . . .   7
     4.1.  Endpoints Extensions  . . . . . . . . . . . . . . . . . .   7
       4.1.1.  Multi-Field Typed Endpoint Addresses  . . . . . . . .   7
       4.1.2.  Address Type  . . . . . . . . . . . . . . . . . . . .   8
       4.1.3.  Endpoint Address  . . . . . . . . . . . . . . . . . .   8
       4.1.4.  Field Name  . . . . . . . . . . . . . . . . . . . . .   8
       4.1.5.  Field Value . . . . . . . . . . . . . . . . . . . . .   8
     4.2.  Endpoint Cost Service Extensions  . . . . . . . . . . . .   8
       4.2.1.  Accept Input Parameters . . . . . . . . . . . . . . .   9
       4.2.2.  Capabilities  . . . . . . . . . . . . . . . . . . . .   9
       4.2.3.  Response  . . . . . . . . . . . . . . . . . . . . . .  10
     4.3.  ALTO Address Type Registry Extensions . . . . . . . . . .  11
   5.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  11
     5.1.  Information Resource Directory  . . . . . . . . . . . . .  11
     5.2.  Endpoint Cost Service . . . . . . . . . . . . . . . . . .  13
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   7.  Privacy And Security Considerations . . . . . . . . . . . . .  14
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   ECS is a basic service of the ALTO services defined in [RFC7285].
   Based on the simple host model when defining endpoints, ECS defined
   in [RFC7285] may not work well in an emerging settings such as
   Software Defined Networking (SDN) based settings, where network
   routing decisions can be flow based.  In this document, we present an
   extended ECS for such new settings.

1.1.  Terminology
Show full document text