Application-Layer Traffic Optimization (ALTO) Cost Calendar
draft-ietf-alto-cost-calendar-21

Document Type Active Internet-Draft (alto WG)
Last updated 2020-05-01 (latest revision 2020-03-17)
Replaces draft-randriamasy-alto-cost-calendar
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Jul 2020 - Submit cost property... )
Document shepherd Vijay Gurbani
Shepherd write-up Show (last changed 2020-01-24)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Mirja K├╝hlewind
Send notices to Vijay Gurbani <vijay.gurbani@gmail.com>
IANA IANA review state Version Changed - Review Needed
IANA action state No IANA Actions
RFC Editor RFC Editor state RFC-EDITOR
Details
Network Working Group                                     S. Randriamasy
Internet-Draft                                           Nokia Bell Labs
Intended status: Standards Track                                 R. Yang
Expires: September 18, 2020                              Yale University
                                                                   Q. Wu
                                                                  Huawei
                                                                 L. Deng
                                                            China Mobile
                                                               N. Schwan
                                                      Thales Deutschland
                                                          March 17, 2020

      Application-Layer Traffic Optimization (ALTO) Cost Calendar
                    draft-ietf-alto-cost-calendar-21

Abstract

   This document is an extension to the base Application-Layer Traffic
   Optimization (ALTO) protocol.  It extends the ALTO cost information
   service so that applications decide not only 'where' to connect, but
   also 'when'.  This is useful for applications that need to perform
   bulk data transfer and would like to schedule these transfers during
   an off-peak hour, for example.  This extension introduces ALTO Cost
   Calendar, with which 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 Information Resources Directory and ALTO Server responses.

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
   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 18, 2020.

Randriamasy, et al.    Expires September 18, 2020               [Page 1]
Internet-Draft             ALTO Cost Calendar                 March 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.  Some recent known uses  . . . . . . . . . . . . . . . . .   4
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   5
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   5
   3.  Overview of ALTO Cost Calendars and terminology . . . . . . .   5
     3.1.  ALTO Cost Calendar overview . . . . . . . . . . . . . . .   6
     3.2.  ALTO Cost Calendar information features . . . . . . . . .   6
     3.3.  ALTO Calendar design characteristics  . . . . . . . . . .   7
       3.3.1.  ALTO Cost Calendar for all cost modes . . . . . . . .   9
       3.3.2.  Compatibility with legacy ALTO Clients  . . . . . . .  10
   4.  ALTO Calendar specification: IRD extensions . . . . . . . . .  10
     4.1.  Calendar attributes in the IRD resource capabilities  . .  11
     4.2.  Calendars in a delegate IRD . . . . . . . . . . . . . . .  12
     4.3.  Example IRD with ALTO Cost Calendars  . . . . . . . . . .  13
   5.  ALTO Calendar specification: Service Information Resources  .  17
     5.1.  Calendar extensions for Filtered Cost Maps (FCM)  . . . .  17
       5.1.1.  Calendar extensions in Filtered Cost Map requests . .  17
       5.1.2.  Calendar extensions in Filtered Cost Map responses  .  18
       5.1.3.  Use case and example: FCM with a bandwidth Calendar .  21
     5.2.  Calendar extensions in the Endpoint Cost Service  . . . .  23
       5.2.1.  Calendar specific input in Endpoint Cost requests . .  23
       5.2.2.  Calendar attributes in the Endpoint Cost response . .  24
       5.2.3.  Use case and example: ECS with a routingcost Calendar  25
       5.2.4.  Use case and example: ECS with a multi-cost Calendar
               for routingcost and owdelay . . . . . . . . . . . . .  27
Show full document text