QuicksearcheasyDNS Main LinksCategoriesSyndicate This BlogStaff WeblogseasyDNS Member Blogs» SelfEmployment.ca
» Jim Carroll » Efficient Market Canada » CEO Blog - Time Leadership by Jim Estill » Caught In Between by Lawrence Greene Archives |
Tuesday, February 28. 2006China Top Level Domain news
There has been a remarkable lack of chatter today around domain policy circles, given the rather stunning announcement out of china that starting tomorrow, China will be launching its own Top Level Domain roots for the .COM, .NET TLDs so that "[Chinese] Internet users don't have to surf the Web via the servers under the management of the Internet Corporation for Assigned Names and Numbers (ICANN) of the United States."
Up until now, the underlying premise was that no matter what happened to naming policies, nothing would ever be done to change the tenet that (aside from deliberate design decisions like esoteric routing, geo-targetting, anycasting, etc) any two people typing "example.com" into their application could always expect the same results, forever. Not so after tomorrow, when according to the one single article at the root of all this, China will be introducing .COM and .NET of their own. CIRA Board member and internet governence commentator Michael Geist comments on the development here, and another domain insider I'll leave nameless (since it came in a private mail) said Although innocuous you should mark and remember this day as the day the root I'm still trying to verify for myself that this is happening in the way it's been interpreted. As I write this, it's approximately 2:45am March 1st in China and I'm not seeing any alternative root glue for .com or .net in the .cn root nameservers, which I was expecting to see. (It also begs the question: how will they backport a new root hints file into every single DNS resolver in the country?) When I started this post, the soa on cn was and since I've been writing it has been changed to And also, since I've started this post, under the new SOA serial there are now these: and So I'm withholding reaction on this as I begin to suspect a poorly translated article was in reality announcing .com.cn and .net.cn subdomains which are non-events by comparison. Update: It has become clearer after trading a couple emails around that the news is indeed that China has added com.cn and net.cn as well as their own alternate character set implementations for com and net. Basically, this comes down to similar efforts over the years to launch competing or expanded root domains. What does make this interesting is that, while typically these enterprises are carried out by net.kooks, this is being done by a government. My guess is they will get some more traction than earlier efforts but what will eventually happen is ICANN (or whoever) will come to the table at some point and a way will be negotiated to maintain visibility and continuity in the root. But for now, there is no fragmentation and no collision crisis to speak of. Update #2 (7:30pm EST): Michael Geist just forwarded me this, the salient bit being:
This is tough to assess because I'm still unsure if this applies to the alternate character set com and net TLDs or if we're really talking about alternative com's and net's in China, which is pretty radical. This article re-iterates that the .com and .net TLDs are in the alternative chinese character set. <speculation> The excerpt above about the "domestic analysis server" makes me curious. Do they intend to somehow reroute requests inside China for the legacy .com and .net TLDs into the chinese charset ones? That would be extreme. </speculation> Another source whom I know likes to stay anonymous just emailed me:
Still digging...(jeez, no pun intended) Monday, February 6. 2006Yahoo and AOL's paid email delivery system
An interesting turn of events surfaced over the weekend with AOL and Yahoo's announced plans to charge a fraction of a cent for "preferred delivery" of email.
Both companies will still accept unpaid email, but by paying the charges, senders will be able to bypass inbound spam filters and have their mail delivered directly to the user's inbox. The predictable backlash will come from this, but in terms of what we think about it here at easyDNS, we're ambivalent. We should go on record to our users now to state that we will not pay AOL or Yahoo on a per-email basis to get forwarded mail through. Mail passing through our forwarders will still be accepted by Yahoo and AOL, but if they add additional restrictions to it based on the fact that we haven't paid for preferred delivery, I foresee a mass exodus of email accounts from both services. We are currently whitelisted by AOL, and I would even consider paying a monthly or annual license fee for that status based on our mail volumes, it would help us further differentiate as a premium domain manager and provide incentive to ramp up our spam filtering here (we're working on that as we speak). But the per-email delivery charge doesn't fit the model for mail forwarders and I see few, if any eager to assume those fees. As mail forwarders, we're largely indifferent to where we forward our members' email to and our entire value proposition is based on the concept of giving our users the ability to route their email around network outages, localized ISP failures, and procedural and commercial roadblocks such as this.
(Page 1 of 1, totaling 2 entries)
|