Needed: Non-crappy e-mail address verification and a Google bomb.

Chris Ambler discusses TLD strings and is concerned that ICANN could worry too much about the problems new TLDs have had in the past, with code that would claim that anything with a TLD segment of more than two or three characters was an invalid d…

Chris Ambler discusses TLD strings and is concerned that ICANN could worry too much about the problems new TLDs have had in the past, with code that would claim that anything with a TLD segment of more than two or three characters was an invalid domain name.I sincerely hope that Chris is wrong about that — for two reasons: One, fools are inventive enough to not just assume 2 and 3 letter TLDs (Google hit #1 for address validation javascript), but to also check for the now-existing gTLDs, while essentially sticking to the same broken design — or, worse, not even being flexible with three-letter TLDs. Two, what I’ve heared on this topic in Rome sounded extremely reasonable. While John Klensin’s RFC 3696 on the topic wasn’t mentioned there — at least in the public forum –, others have recognized that the easiest cure is probably to implement (or just find) free sample code for domain name and e-mail address verification, and to Google-bomb that code.In other words: Let’s help the market take care of that.

%d bloggers like this: