Sebastian et al, Has anyone considered the following ALTO server discovery mechanism? Create a global registry of all public ALTO servers, with a well-known, persistent uri. We would strongly encourage anyone who fields a public ALTO server to register it. Since (presumably!) ISPs and the like want customers to use their ALTO servers, I think it would be easy to get them to register the servers.
So what would the interface be? Why ALTO, of course! Specifically, the global registry would be an ALTO server with an Endpoint Property Service (and the PID Property Service, draft-roome-alto-pid-properties <https://datatracker.ietf.org/doc/draft-roome-alto-pid-properties/> , assuming that extension is adopted) with the property ³Preferred-ALTO-Server², whose value is the URI of ALTO server with the best local knowledge around that endpoint. If this is a PID property, a p2p tracker could download the network map and full set of PID properties, so it would not need to consult the global registry for each request. I think this is the moral equivalent of getting the ALTO server through DNS, except that it doesn¹t require updating DNS tables. And it allows clients like trackers to discover the ALTO server for remote regions. Comments? - Wendy
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
