ALTO Cost Calendar
Network Working Group S. Randriamasy
Internet-Draft Nokia Bell Labs
Intended status: Standards Track R. Yang
Expires: May 17, 2019 Yale University
November 13, 2018
ALTO Cost Calendar
This document is an extension to the base ALTO protocol [RFC7285].
It extends the ALTO cost information service such 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 Calendars, 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.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
When the words appear in lower case, they are to be interpreted with
their natural language meanings.
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
Randriamasy, et al. Expires May 17, 2019 [Page 1]
Internet-Draft ALTO Cost Calendar November 2018
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 May 17, 2019.
Copyright (c) 2018 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
2. Overview of ALTO Cost Calendars . . . . . . . . . . . . . . . 4
2.1. ALTO Cost Calendar information features . . . . . . . . . 5
2.2. ALTO Calendar design characteristics . . . . . . . . . . 5
2.2.1. ALTO Cost Calendar for all cost modes . . . . . . . . 6
2.2.2. Compatibility with legacy ALTO Clients . . . . . . . 7
3. ALTO Calendar specification: IRD extensions . . . . . . . . . 7
3.1. Calendar attributes in the IRD resources capabilities . . 7
3.2. Calendars in a delegate IRD . . . . . . . . . . . . . . . 9
3.3. Example IRD with ALTO Cost Calendars . . . . . . . . . . 9
4. ALTO Calendar specification: Service Information Resources . 13
4.1. Calendar extensions for filtered cost maps . . . . . . . 13
4.1.1. Calendar extensions in Filtered Cost Map requests . . 13
4.1.2. Calendar extensions in Filtered Cost Map responses . 14
4.1.3. Use case and example: FCM with a bandwidth Calendar . 16
4.2. Calendar extensions in the Endpoint Cost Service . . . . 18
4.2.1. Calendar specific input in Endpoint Cost requests . 18
4.2.2. Calendar attributes in the Endpoint Cost response . . 18
4.2.3. Use case and example: ECS with a routingcost Calendar 19
Show full document text