Dear ALTO WG folks,
this new version of the ALTO requirements draft addresses one concern we
heard several times during last call, which is about the two query modes
("sorting oracle" vs. "map") and how to ensure interoperability between
implementations. We consider this a clarification which does not change
what has been WG consensus several years ago.
OLD (draft-ietf-alto-reqs-12.txt and before):
>
> REQ. ARv12-21: An ALTO client protocol MUST support at least one
> query mode, either the target-aware or the target-independent query
> mode.
>
> REQ. ARv12-22: An ALTO client protocol SHOULD support both the
> target-aware and the target-independent query mode.
NEW (draft-ietf-alto-reqs-13.txt):
>
> REQ. ARv13-21: An ALTO client protocol specification MUST specify at
> least one query mode, either the target-aware or the target-
> independent query mode.
>
> REQ. ARv13-22: An ALTO client protocol specification SHOULD specify
> both the target-aware and the target-independent query mode. If an
> ALTO client protocol specification specifies more than one query
> mode, it MUST define at least one of these modes as REQUIRED to
> implement by ALTO Clients and ALTO Servers. Furthermore, it MUST
> specify an appropriate protocol mechanism for negotiating between
> ALTO Client and ALTO Server, which query mode to use.
Thanks,
Sebastian
----- Forwarded message from [email protected] -----
Date: Mon, 16 Jan 2012 07:31:03 -0800
From: [email protected]
To: [email protected]
Cc: [email protected]
Subject: [alto] I-D Action: draft-ietf-alto-reqs-13.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Application-Layer Traffic Optimization Working
Group of the IETF.
Title : Application-Layer Traffic Optimization (ALTO)
Requirements
Author(s) : Sebastian Kiesel
Stefano Previdi
Martin Stiemerling
Richard Woundy
Yang Richard Yang
Filename : draft-ietf-alto-reqs-13.txt
Pages : 22
Date : 2012-01-16
Many Internet applications are used to access resources, such as
pieces of information or server processes, which are available in
several equivalent replicas on different hosts. This includes, but
is not limited to, peer-to-peer file sharing applications. The goal
of Application-Layer Traffic Optimization (ALTO) is to provide
guidance to applications, which have to select one or several hosts
from a set of candidates capable of providing a desired resource.
This guidance shall be based on parameters that affect performance
and efficiency of the data transmission between the hosts, e.g., the
topological distance. The ultimate goal is to improve performance
(or Quality of Experience) in the application while reducing resource
consumption in the underlying network infrastructure.
This document enumerates requirements for specifying, assessing, or
comparing protocols and implementations.
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-alto-reqs-13.txt
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-alto-reqs-13.txt
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
----- End forwarded message -----
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
