20 Jun
2011
20 Jun
'11
12:57 a.m.
And your technical solution to ensure "http://apple/" always resolves to "apple." and doesn't break people using "http://apple/" to reach "http://apple.example.net/" is?
Whatever people have been doing for the past decade to deal with http://dk/ and http://bi/. As I think I said in fairly easy to understand language, this is not a new problem. I am not thrilled about lots of new TLDs, but it is silly to claim that they present any new technical problems. Regards, John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. http://jl.ly