At 3:28 -0400 3/31/10, 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?
On topic of DNSOP: Reversing a fix slipped into the DNS for some other segment's problem will take years to remove. We still have round-robin in the DNS, for example, added to help load balancing for an application (mail?) way way back in time. Today round-robin is a pain for DNSSEC (for example).
This is off-topic for DNSOP: I don't believe it takes "years" to fix host behavior problems. Yes, some hosts will run the same software they have today for years to come. But most won't last that long. If you don't fight the problem in the right place, you won't eradicate the issue.
-- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Edward Lewis NeuStar You can leave a voice message at +1-571-434-5468 New pithy statement under construction... _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
