Song Haibin <[email protected]> wrote: > > Here is the link for the merged document. More comments are appreciated! > > http://tools.ietf.org/id/draft-song-alto-server-discovery-01.txt
One quick comment: ] ] 5.1.2.1. Using DHCP option for access domain name ] ] There are DHCP options (OPTION_V4_ACCESS_DOMAIN and ] OPTION_V6_ACCESS_DOMAIN) proposed in [I-D.ietf-geopriv-lis-discovery] ] to discover the local access domain names. The retrieved access ] domain name can be used to form a SRV name by prefixing the ALTO ] service label to the access domain name. If it failed with the SRV ] lookup with this service name, then it will remove one tag from the ] left hand of the access domain name and prefix the ALTO service label ] to form a new SRV name. It will iterate the process until it ] succeeds in getting an ATLO server information or failed. This iterative process can lead to problems, both in that it will search towards Top-Level-Domains that have no relation to the network to which the host is actually attached, and in that (if ALTO usage grows) it could generate excessive (and pointless) DNS queries at or near the Top-Level-Domain servers. In particular, note that many of the .us locality servers have limited bandwidth; and I'm sure there are other Country-Code servers whose bandwidth is even more limited. I recommend caution in applying this strip-the-leftmost tactic even once, and strongly recommend against applying it iteratively without limit. If used at all, there is a need for a standardized signal to say "Search no further". -- John Leslie <[email protected]> _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
