ALTO Cost Calendar
draft-randriamasy-alto-cost-calendar-03

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-03-09
Replaced by draft-ietf-alto-cost-calendar
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
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)
Network Working Group                                S. Randriamasy, Ed.
Internet-Draft                                  Alcatel-Lucent Bell Labs
Intended status: Standards Track                                 R. Yang
Expires: September 10, 2015                              Yale University
                                                                   Q. Wu
                                                                  Huawei
                                                                 L. Deng
                                                            China Mobile
                                                               N. Schwan
                                                      Thales Deutschland
                                                           March 9, 2015

                           ALTO Cost Calendar
                draft-randriamasy-alto-cost-calendar-03

Abstract

   The goal of Application-Layer Traffic Optimization (ALTO) is to
   bridge the gap between network and applications by provisioning
   network related information in order to allow applications to make
   informed decisions.  The present draft proposes to extend the cost
   information provided by the ALTO protocol.  The purpose is to broaden
   the decision possibilities of applications to not only decide 'where'
   to connect to, but also 'when'.  This is useful to applications that
   have a degree of freedom on when to schedule data transfers, such as
   non- instantaneous data replication between data centers or service
   provisioning to end systems with irregular connectivity.  ALTO
   guidance to schedule application traffic can also efficiently help
   for load balancing and resources efficiency.

   The draft proposes a new cost Mode called "Calendar" Mode, that is
   applicable to time-sensitive ALTO metrics and allows Applications to
   carefully schedule their connections or data transfers.  In the
   Calendar Mode, an ALTO Server exposes ALTO Cost Values in JSON arrays
   where each value corresponds to a given time interval.  The time
   intervals as well as other Calendar attributes are specified in the
   IRD.  Besides the functional time-shift enhancement the ALTO Cost
   Calendar also allows to schedule the ALTO requests themselves and
   thus save a number of ALTO transactions.

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].

Randriamasy, et al.    Expires September 10, 2015               [Page 1]
Internet-Draft             ALTO Cost Calendar                 March 2015

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 September 10, 2015.

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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Motivating Use cases for ALTO Cost Schedule . . . . . . . . .   5
     2.1.  Bulk Data Transfer scheduling . . . . . . . . . . . . . .   5
     2.2.  Endsystems with limited connectivity or access to
           datacenters . . . . . . . . . . . . . . . . . . . . . . .   6
     2.3.  SDN Controller guided access to application endpoints . .   7
     2.4.  Large flow scheduling on extended ALTO topologies . . . .   8
     2.5.  Time-sensitve TE metrics Calendaring  . . . . . . . . . .  10
   3.  Design considerations for an ALTO calendar  . . . . . . . . .  11
     3.1.  Purpose of an ALTO calendar . . . . . . . . . . . . . . .  11
     3.2.  Design requirements for an ALTO calendar  . . . . . . . .  12
   4.  ALTO extensions for a Cost Calendar . . . . . . . . . . . . .  13
Show full document text