Welcome:
Login
|
Sign Up
|
About CircleID
Follow:
|
|
|
DotCo, which is the ccTLD for Colombia, is opening up to general public registration today. According to official sources from both Neustar and CoInternet the registry has handled over 90 thousand registrations in the first 15 minutes! ... While the initial registration phase of any new domain extension can attract a lot of media interest and a flood of registrations you need to look at the "big picture".
DNSSEC adoption has been slow, but is now picking up speed, thanks to organizations leading the way. ... While some registries have already signed, some have announced plans to sign and others are still trying to figure out their plan. Either way, DNSSEC is here. How can we make DNSSEC adoption quicker and easier not only for the registry but for individual name owners?
The Coalition for Internet Transparency (CFIT) filed an anti-trust suit against VeriSign for their monopoly control of the .COM registry and the expiring market of .COM domains. The claims were many including excessive financial pressure lobbying and lawsuits to force ICANN into renewing the VeriSign .COM agreement under very self-serving terms. ICANN inevitably was paid millions of dollars to settle the suit. However, the saga continues once again. ... In the light of continuous and relentless discussions and proposals by the Vertical Integration working group, one question is in the back of everyone's mind. Could the decision on Vertical Integration backfire on ICANN and invite similar suits in the domain name space?
With the launch of new generic Top-Level Domains (gTLDs) expected to occur early next year, many are closely examining the opportunities and risks associated with ICANN's Program. Although still in draft format and subject to change, keep these gotchas in mind as you think through your strategy.
As the implementation of DNSSEC continues to gather momentum and with a number of ccTLDs, and the '.org' gTLD having deployed it into their production systems, I think it is worth pausing to take a look at the entire DNSSEC situation. Whilst it is absolutely clear that DNSSEC is a significant step forward in terms of securing the DNS, it is but one link in the security chain and is therefore not, in itself, a comprehensive solution to fully securing the DNS system.
For a brief moment earlier this week, I thought my days spent dreaming of hover-boards, flying cars and Biff's elusive Sports Almanac were finally over. From reports circulating online, we had finally reached "Back to the Future Day". Those movie buffs out there will know exactly what I'm referring to... But it got me thinking. What would the Domain Name world look like if that crazy cat Doc Brown swung past in his DeLorean, with a fully-charged flux capacitor and a return ticket to October 21st 2015?
Last week ICANN took another very significant step forward in the expansion of the internet by approving the delegation of a number of Chinese script IDN ccTLDs. Although we have all heard statements that portray the introduction of IDN ccTLDs as being perhaps the single most important factor in the achievement of ICANN's "One World, One Internet" vision, we should take a moment to appreciate the true significance of this latest round of IDN ccTLD approvals.
ICANN's Generic Names Supporting Organisation (GNSO) has formed a working group to consider changes to the domain transfer process to enhance security and reduce hijacking. The working group consists of registrars, aftermarket players, domainers and other members of the ICANN Community. The group published its preliminary recommendations at the ICANN meeting in Brussels two weeks ago and the 20-day comment period has just begun.
We have just returned from the Brussels, Belgium ICANN meeting where we released our Registrar audit, the Internet "Doomsday Book." There are many topics covered in the report, but we wanted to follow up specifically on the issue of WHOIS access and add data to our previous column Who Is Blocking WHOIS? which covered Registrar denial of their contracted obligation to support Port 43 WHOIS access.
At Friday's meeting of the ICANN board in Brussels, they voted, probably for the last time, to approve the 2004 application for the .XXX domain. Purely on the merits, there is of course no need for a top level domain for porn. This isn't about the merits, this is about whether ICANN follows its own rules. Despite overheated press reports, .XXX will not make porn any more available online than it already is (how could it?), there is no chance of all porn being forced into .XXX (that's a non-starter under US law), and .XXX will have no effect on the net other than perhaps being a place to put legal but socially marginal porn far away from any accidental visitors.
A World-Renowned Source for Internet Developments. Serving Since 2002.