You don't think
"(i) a service provider, as that term is defined in section 512(k)(1) of = title 17, United States Code, or other operator of a domain name system = server shall take reasonable steps that will prevent a domain name from = resolving to that domain name=92s Internet protocol address;"
could be taken as a requirement for providers to intercept attempts to = use off-network DNS resolvers and manage such requests to meet the end = goal above?
Given that many providers already do this (for whatever reason), it's = not much of a stretch to see someone declaring that such behaviour falls = under the umbrella of "reasonable steps".
I'm not suggesting that I think any of this is reasonable or sensible, = but it does seem to imply an operational burden on service providers.
It's funny, isn't it, didn't we just finish convincing the government of the need for DNSSEC, making the DNS system more resistant to some forms of tampering? ... JG -- Joe Greco - sol.net Network Services - Milwaukee, WI - http://www.sol.net "We call it the 'one bite at the apple' rule. Give me one chance [and] then I won't contact you again." - Direct Marketing Ass'n position on e-mail spam(CNN) With 24 million small businesses in the US alone, that's way too many apples.