Hi all,
We have submitted a new draft entitled ALTO Cost Schedule and proposing
extensions on Cost Value specifications.
The idea is to provide cost values as a set of values each defined on a
given time period, together with appropriate description attributes.
The main motivation is that current ALTO Costs and their modes provide
static values, assuming to report on information that does not change
rapidly. However the ALTO use cases now extend to CDNs, Data centers and
non real time applications that deal with information changing rapidly.
If this information can be predicted, non-real time applications or
management systems using ALTO could take advantage of scheduling their
access to content or resources.
Another motivation of scheduled costs is the need to regulate the
traffic through incentives: if ALTO provides an abstracted or aggregated
form of dynamic information that is centrally managed (and readable), it
can help preserving network stability while keeping network state
information confidential.
This draft has also been advertised on the altoex mailing-list but we would
appreciate your feedback on the use cases (relevance, whether other ones
are applicable), whether it makes sense to extend ALTO to support time-dependent
arrays of cost values.
Thanks,
Sabine
-------- Message original --------
Sujet : New Version Notification for
draft-randriamasy-alto-cost-schedule-00.txt
Date : Tue, 6 Mar 2012 01:53:25 +0100
De : [email protected] <[email protected]>
Pour : RANDRIAMASY, SABINE (SABINE)
<[email protected]>
Copie à : Schwan, Nico (Nico) <[email protected]>
A new version of I-D, draft-randriamasy-alto-cost-schedule-00.txt has been
successfully submitted by Sabine Randriamasy and posted to the IETF repository.
Filename: draft-randriamasy-alto-cost-schedule
Revision: 00
Title: ALTO Cost Schedule
Creation date: 2012-03-05
WG ID: Individual Submission
Number of pages: 13
Abstract:
The goal of Application-Layer Traffic Optimization (ALTO) is to
bridge the gap between network and applications by provisioning
network related information. This allows applications to make
informed decisions, for example when selecting a target host from a
set of candidates. The ALTO problem statement [RFC5693] considers
typical applications as file sharing, real-time communication and
live streaming peer-to-peer networks. Recently other use cases
focused on Content Distribution Networks and Data Centers have
emerged [draft-jenkins-alto-cdn-use-cases-01].
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' to connect. 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. The draft
therefore specifies a new cost mode, called the "schedule" mode. In
this mode the ALTO server offers cost maps that contain link ratings
that are valid for a given timeframe (e.g. hourly) for a period of
time (e.g. a day). Besides the functional time-shift enhancement
providing multi-timeframe cost values the extansion also allows the
saving of a number of ALTO transactions and thus resources on the
ALTO server and clients.
The IETF Secretariat
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
