On Mar 31, 2010, at 12:28 AM, 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?
Except that, since it IS a host problem, why not focus on improved detection and debugging.... EG, yahoo is one of the big pushes behind it. THey could easily add auto-debugging to their homepgae would would detect this condition and NOTIFY the users that this will be a problem, same for google. This to me seems like a "cure" worse than the disease. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
