Dear all,
Ben brought this point up about the support of the target-independent and/or
target-aware modes in the ALTO protocol, as specified in the ALTO reqs draft.
Here is the definition of the two modes (as a recap):
o In target-aware query mode, an ALTO client performs the ALTO query
when the desired resource and a set of candidate resource
providers are already known, i. e., after DHT lookups, queries to
the resource directory, etc.
o In target-independent query mode, ALTO queries are performed in
advance or periodically, in order to receive comprehensive,
"target-independent" guidance, which will be cached locally and
evaluated later, when a resource is to be accessed.
The requirements say that at least one of the two modes must be supported:
REQ. ARv10-24: An ALTO client protocol MUST support at least one of
these two modes, either the target-aware or the target-independent
query mode.
And that the protocol SHOULD support both.
REQ. ARv10-25: An ALTO client protocol SHOULD support both the
target-aware and the target-independent query mode.
We could also argue for replacing these 2 arguments with this new requirement:
An ALTO client protocol MUST support both the
target-aware and the target-independent query mode.
This will cut away a bit of freedom, but on the other hand ensure that the
protocol itself is always capable of both modes.
Please send your replies to this until July 7th COB.
Martin
[email protected]
NEC Laboratories Europe - Network Research Division NEC Europe Limited |
Registered Office: NEC House, 1 Victoria Road, London W3 6BL | Registered in
England 2832014
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
