Server Discovery was discussed in great details in the beginning of the WG.
The result is this draft: http://tools.ietf.org/html/draft-kiesel-alto-3pdisc-05 Bittorrent can make use of this method http://www.bittorrent.org/beps/bep_0022.html The 'first' server discovery problem exists whether that is the server from which you will get the cost map or the service discovery server. You might think I'm against RESTful but I was the one that proposed service discovery in the first place and worked on it with Alimi in the first versions of the draft. I'm just reminding the list that: In two different IETF meetings the consensus was that the protocol could be very extensible and have many options as long as there was a simple mode of operation that P2P clients could make use to start working almost 'out of the box'. This mode of operation was demonstrated in more than one ISP. Thanks, Reinaldo On 3/22/11 3:52 PM, "Thomson, Martin" <[email protected]> wrote: > On 2011-03-23 at 08:15:28, Reinaldo Penno wrote: >> One of the original arguments against URI discovery (as present in v03 >> of the original draft) was P2P clients that are not interested in >> having a full HTTP client built-in can perform a simple GET request >> and download a file. >> There is no need for the URI discovery phase. > > How does the client know which URI to GET? _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
