I totally agree. Please see section 5.1 in draft-song-alto-server-discovery for the DNS discovery method for ALTO. And check section 5.1.2.1 for reusing the DHCP option for domain name. And check section 5.1.2.3 for the limitations of the reverse DNS lookup.
BR, Haibin Martin Thomson wrote: >draft-ietf-geopriv-lis-discovery probably provides most of what you will need for your application. You could possibly even use the DHCP option defined there. >The security problems arising from the delegation scenario is described briefly in draft-barnes-hard-problem. You might have fewer problems with this with ALTO. draft-thomson-geopriv-res-gw-discovery includes the more controversial portion - the use of the reverse tree. We did originally follow the PTR, but that had even more problems. For instance, two IPs in different networks - and different servers - can refer to the same domain. Feedback on the draft that uses the reverse tree has been nothing less than harsh. It would take me more time than I have right now to go through all the issues. I'm happy to expand on this in person. I would strongly recommend that you look at draft-ietf-geopriv-lis-discovery as defining the scope of what is achievable in the short term ...and what you should look at addressing now. >--Martin _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
