Hi Wendy, this idea sounds like draft-kiesel-alto-alto4alto-00 ...
The question is: what is less cumbersome and unlikely to happen - update the DNS reverse tree and re-use the root name servers as a rendezvous point, or create and maintain your own global registry and root-alto-server infrastructure? My personal opinion is that both options will be a pain to implement, but the first one a little less... What do you think? Thanks, Sebastian On Mon, Jul 14, 2014 at 12:18:14PM -0400, Wendy Roome wrote: > 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
