Welcome:
Login
|
Sign Up
|
About CircleID
Follow:
|
|
|
Censorship practices by governments and other private actors are becoming more increasingly more sophisticated, and their effects are increasingly being felt globally. A case in point, the YouTube incident in Pakistan was a recent example affecting both users and the DNS at a national and global level. Likely other incidents will occur in the near future. As such, I believe censorship should be considered as a threat to the stability and security of the DNS. In the context of Internet governance discussions, I believe the issue should be raised both at ICANN and the Internet Governance forum. Do others agree? more
ICANN's GNSO council had WHOIS on its agenda for today. The options on the table: (1) Accepting the outcome of years of policy development processes; (2) rejecting that outcome (again?), but calling for some kind of fact-gathering to feed into future policy work, in order to keep the space occupied; (3) acknowledging that there is broad dissent in the Internet community, and calling for a sunset on the WHOIS clauses in current agreements, as these clauses are not backed by community consensus any more. Not very surprisingly, motions (1) and (3) failed; (2) was accepted; all that after lengthy discussion, with lots of procedural bells and whistles. more
ICANN staff has published a draft report on dispute resolution procedures for IGO (inter-governmental organization) domain names. This proposal has deep flaws and should be rejected by the community, as it does not have the balance and protection of registrant rights present in the existing UDRP. Initially, the proposed policy would apply to new Top-Level Domains (TLDs), but via a Policy Development Process (PDP) it could be extended to existing TLDs. more
ICANN has been wrangling about WHOIS privacy for years. Last week, yet another WHOIS working group ended without making any progress. What's the problem? Actually, there are two: one is that WHOIS privacy is not necessarily all it's cracked up to be, and the other is that so far, nothing in the debate has given any of the parties any incentive to come to agreement. The current ICANN rules for WHOIS say, approximately, that each time you register a domain in a gTLD (the domains that ICANN manages), you are supposed to provide contact information... WHOIS data is public, and despite unenforceable rules to the contrary, it is routinely scraped... more
The report of the Whois Working Group was published today. The Working Group could not achieve agreement on how to reconcile privacy and data protection rights with the interests of intellectual property holders and law enforcement agencies. So the Working Group Chair redefined the meaning of "agreement." See the full story at the Internet Governance Project site. more
ICANN has embarked on the IDN boat at the same time it wants to introduce DNSSEC and new gTLDs. This promises lots of fun. Or grey hair, depending how you look at it. First is the issue of country code IDNs. The ISO-3166 table, based on two letter codes, is a western convention. Some cultures do not use abbreviations or acronyms. Some do not use a character-based alphabet, but a syllabic one. Hence, the next logical step would be to represent the full country name in local script, rather than a transliteration of the ISO string... Imagine the case of India, where there are 1.652 languages, of which 24 are spoken by more than one million people... more
ICANN seems to be out to re-prove Hirschman's theories of exit, voice, and loyalty by driving all of its good people to exit rather than giving them meaningful voices. Thomas Roessler, a long-time advocate of individual users' interests on the interim ALAC now suggests it's Time to Reconsider the structure of ICANN's At-Large, as he feels compelled to promise himself not to get involved with ICANN again... more
The ICANN Board voted today 9-5, with Paul Twomey abstaining, to reject a proposal to open .xxx. This is my statement in connection with that vote. I found the resolution adopted by the Board (rejecting xxx) both weak and unprincipled... I am troubled by the path the Board has followed on this issue since I joined the Board in December of 2005. I would like to make two points. First, ICANN only creates problems for itself when it acts in an ad hoc fashion in response to political pressures. Second, ICANN should take itself seriously as a private governance institution with a limited mandate and should resist efforts by governments to veto what it does. more
As an alternative to the creation of the .XXX TLD, ICANN/IANA can assign special port numbers that can be used to label adult content. IANA assigns port numbers as part of its duties. For example, port 80 is reserved for the HTTP protocol (i.e. the World Wide Web). Port 443 is reserved for the HTTPS protocol (SSL-secure version of HTTP). Port 23 is for Telnet, port 25 is for SMTP, and so on. One can see the full list at here... In a real sense, the IANA port assignments are just suggestions to the world as to what to expect on certain ports, whether it be a mail server, WHOIS, FTP, POP email or any other service/protocol. more
According to this article in IHT , those who want deployment of IDNs now are "political gambits". Cerf said that the technical side is not yet ready and thus the deployment of IDNs should be done very carefully. I agree to the technical aspects. However, the next question is of course: "when will it be ready for deployment?"... more
Excavation is fun. You get to rumble around on heavy equipment bashing up this and tearing up that. Each scoop uncovers original earth. As your big machine chews up the hill, an occasional sparkle suggests a raw gem or two. ...ICANN business is still predominately conducted on Email lists/forums. Email lists and forums are good at excavating... more
I am often asked how to get a ccTLD by folks just coming in to the domain industry. There is RFC1591 as a start for reading material on the subject matter, and then there is ICP-1. I defer them to IANA, who defers to ICANN, who in turn defers to ISO and the ISO3166-1 list being the definitive list, and then you have to factor in some of the "reserved code elements" from their decoding table to normalize 3166 against the list of IANA Country Codes for ccTLD delegations like .EU. How does one get their ccTLD into the ISO list? The ISO in turn (likely due to the masses that contact them hoping to list their country) defer the criteria for what it is to be a 'country' for being on the 3166-1 list, and partially defer to the United Nations. more
I had the pleasure of eating breakfast with Vint Cerf, chairman of ICANN's board and Chief Internet Evangelist at Google, prior to his keynote address this morning. It was great to discuss some of the issues domainers are facing with regards to registrar practices, expiring domains, etc. directly with Cerf. Cerf's keynote kept the crowd engaged. I've summarized the topics he covered... Some people have misunderstood Cerf's position with regards to adding new domains. He said he is not opposed to adding new TLDs. What he advocates, however, is having a solid rationale for adding new TLDs. Cerf believes the processes and outcomes of the first two rounds of TLD adds were not satisfactory... more
I've finally recovered from another ICANN meeting, frustrated as ever. 700 or so people flew halfway around the world to hear canned presentations, dueling-monologue public form sessions, and resolutions that left major issues unresolved, and to gripe in the hallways about how little was being done. more
Well, at least one part of it. As ICANN has announced, the Board approved the VeriSign Settlement Agreement. Now, there will be many questions, many pros and contras, but for me the main question is that finally this discussion is over. Here's what I think about my vote and the agreement itself. more
A World-Renowned Source for Internet Developments. Serving Since 2002.