On Wed, Mar 31, 2010 at 03:28:24AM -0400, Igor Gashinsky wrote:
You are absolutely right -- it's not a DNS problem, it *is* a host behavior problem. The issue is that it takes *years* to fix a host behavior problem, and we need to engineer and deploy a fix much sooner then that (hopefully about a year before the v4 exhaustion date). Given that, is there something other then DNS that can address it better/faster?
I don't understand why DNS is seemingly being tasked here with mopping up the messes of other parts of the network. DNS works because it has a clearly defined purpose. Adding more and more random "features" to DNS, because it is a part of the network which is seemingly not broken, is a great way to ensure DNS fails to achieve its purpose. DNS is not the network janitor. (By the way, I am not claiming DNS is not broken.) -- Andras Salamon [email protected] _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
