Updating the requirements draft
Enrico Marocco <enrico.marocco <at> telecomitalia.it>
2009-07-01 07:58:13 GMT
the recent WGLC discussion has brought to surface a couple of not
exactly new issues I think it would be worth keeping track of, possibly
in the alto-reqs draft we decided to keep alive to reflect ongoing
A first consideration has to do with the information an ALTO server may
want to pass to its clients. Even though, to preserve users' privacy, a
server should take care of disclosing sensible information only to the
clients that information is about (e.g. it's OK to tell a user its own
provisioned bandwidth, less its peers'), there is no way to control the
redistribution of any bit of information. This means that, if an ALTO
service provider is willing to tell something to someone, it must be
aware that that information may reach anyone and everyone. I think that
having it clearly stated somewhere -- maybe as informative text in
section 3.3 -- could help avoid annoying misconceptions.
Another thing that's been mentioned a few times, but not really
discussed, is related to how the information is provided to the clients.
Since the amount of such information may be fairly large, it could be
desirable to have a mechanism for delta exchanges; this would be
particularly useful when the client, e.g. located in a tracker, queries
ALTO servers on behalf of several peers. Some proposals already have
such a mechanism, while others could be easily extended, so I think it
would be worth adding this to the requirements, maybe as a SHOULD.
Do people think that tracking such and similar issues is worth the
effort? Any further elaboration on the above considerations?