Slashdot Mirror

ICANN has responded to a request for it to reduce the $25,000 annual fee it charges gTLD registries. The answer is no. From a report: That wholly unsurprising reply came in a letter from registry services director Russ Weinstein to John McCabe, CEO of failing new gTLD operator Who's Who Registry. McCabe, in November, had asked ICANN to reduce its fees for TLDs, such as its own .whoswho, that have zero levels of abuse. ICANN fees are the "single biggest item" in the company's budget, he said. His request coincided with ICANN commencing compliance proceedings against the company for failure to pay these fees.

Weinstein wrote, in a letter [PDF] published today: "We sympathize with the financial challenges that some new gTLD registry operators may be facing in the early periods of these new businesses. New gTLD operators face a challenging task of building consumer awareness and this can and may take significant time and effort." But he goes on to point out that the $25,000-a-year fee was known to all applicants before they applied, and had been subject to numerous rounds of public comment before the Applicant Guidebook was finalized.

coondoggie shares a report: In a few months, the internet will be a more secure place. That's because the Internet Corporation for Assigned Names and Numbers (ICANN) has voted to go ahead with the first-ever changing of the cryptographic key that helps protect the internet's address book -- the Domain Name System (DNS). The ICANN Board at its meeting in Belgium this week, decided to proceed with its plans to change or "roll" the key for the DNS root on Oct. 11, 2018. It will mark the first time the key has been changed since it was first put in place in 2010. During its meeting ICANN spelled out the driving forces behind the need for improved DNS security that the rollover will bring. For example, the continued evolution of Internet technologies and facilities, and deployment of IoT devices and increased capacity of networks all over the world, coupled with the unfortunate lack of sufficient security in those devices and networks, attackers have increasing power to cripple Internet infrastructure, ICANN stated.

"Specifically, the growth in attack capacity risks outstripping the ability of the root server operator community to expand defensive capacity. While it remains necessary to continue to expand defensive capacity in the near-term, the long-term outlook for the traditional approach appears bleak," ICANN stated. The KSK rollover means generating a new cryptographic public and private key pair and distributing the new public component to parties who operate validating resolvers, according to ICANN. Such resolvers run software that converts typical addresses like networkworld.com into IP network addresses. Resolvers include: internet service providers, enterprise network administrators and other DNS resolver operators, DNS resolver software developers; system integrators, and hardware and software distributors who install or ship the root's "trust anchor," ICANN said.

Slashdot reader monkeyzoo shares the Register's report on a disturbing letter sent to ICANN: Europe's data protection authorities have effectively killed off the current service, noting that it breaks the law and so will be illegal come 25 May, when GDPR comes into force... ICANN now has a little over a month to come up with a replacement to the decades-old service that covers millions of domain names and lists the personal contact details of domain registrants, including their name, email and telephone number. ICANN has already acknowledged it has no chance of doing so... The company warns that without being granted a special temporary exemption from the law, the system will fracture. ["Registries and registrars would likely implement varying levels of access to data depending on their interpretations of the law," ICANN warns.]
"ICANN had made the concept of a moratorium the central pillar of its effort to become compliant with the law," writes the Register. "But its entire strategy was built on a fantasy."

Thursday the EU's data protection advisory group told the site that there's no provision in the GDPR for an "enforcement moratorium", and the Register adds that the EU's data protection advisory group "is clearly baffled by ICANN's repeated requests for something that doesn't exist."

Slashdot reader monkeyzoo shares the Register's report on a disturbing letter sent to ICANN: Europe's data protection authorities have effectively killed off the current service, noting that it breaks the law and so will be illegal come 25 May, when GDPR comes into force... ICANN now has a little over a month to come up with a replacement to the decades-old service that covers millions of domain names and lists the personal contact details of domain registrants, including their name, email and telephone number. ICANN has already acknowledged it has no chance of doing so... The company warns that without being granted a special temporary exemption from the law, the system will fracture. ["Registries and registrars would likely implement varying levels of access to data depending on their interpretations of the law," ICANN warns.]
"ICANN had made the concept of a moratorium the central pillar of its effort to become compliant with the law," writes the Register. "But its entire strategy was built on a fantasy."

Thursday the EU's data protection advisory group told the site that there's no provision in the GDPR for an "enforcement moratorium", and the Register adds that the EU's data protection advisory group "is clearly baffled by ICANN's repeated requests for something that doesn't exist."

ICANN had planned to change the master key used to sign secure Domain Name System records next week for the first time in history. But now an anonymous reader writes:Inattentive ISPs and technical faults have led the Internet Corporation for Assigned Names and Numbers (ICANN) to delay the KSK Rollover for next year. ICANN was supposed to remove the root encryption KSK key from core DNS servers on October 11 and allow a new one to take effect. The key is used for the DNSSEC protocol.

According to ICANN, between 6% to 8% of ISPs did not install the new KSK key to replace the one issued in 2010. The organization says that if it had gone forward with the original KSK Rollover plan, over 60 million Internet users would have been unable to make DNS requests. For the vast majority, ICANN blames lazy ISPs, which failed to update their existing keys. ICANN also believes that many ISPs may not be aware they had not installed the latest KSK. ICANN also distributed software to automatically pull down and install the new KSK. Some ISPs opted to use this software, which apparently had some bugs and failed to download and install the new KSK, in some situations.

Because of this, ICANN announced this week it would delay the KSK Rollover final step — of removing and revoking the original KSK key -- to the first quarter of 2018. ICANN has not decided yet on a precise date.

angry tapir writes: Privacy advocates are sounding the alarm over a potential policy change (PDF) that would prevent some people from registering website addresses without revealing their personal information. ICANN, the regulatory body that oversees domain names, has asked for public comment on whether it should prohibit the private registration of domains which are "associated with commercial activities and which are used for online financial transactions."

angry tapir writes: Privacy advocates are sounding the alarm over a potential policy change (PDF) that would prevent some people from registering website addresses without revealing their personal information. ICANN, the regulatory body that oversees domain names, has asked for public comment on whether it should prohibit the private registration of domains which are "associated with commercial activities and which are used for online financial transactions."

DW100 writes: "ICANN, the body in charge of overseeing the management and rollout of new top level domains, has asked the FTC to investigate whether the registry running .sucks is acting illegally . ICANN's in-house legal team raised concerns that the registry was selling the domains to brand owners in a 'predatory' manner. "The issues relate to concerns brands wishing to buy the .sucks domain, which went on sale on 30 March for a three-month ‘clearing house' period, will have to pay $2,500 to register it for their brand. This is far in excess of the price that will be offered to the general public and the price of other top-level domains."

Trailrunner7 writes with this news from ThreatPost: Unknown hackers were able to compromise vital systems belonging to ICANN, the organization that manages the global top-level domain system, and had access to the system that manages the files with data on resolving specific domain names. The attack apparently took place in November and ICANN officials discovered it earlier this month. The intrusion started with a spear phishing campaign that targeted ICANN staffers and the email credentials of several staff members were compromised. The attackers then were able to gain access to the Centralized Zone Data System, the system that allows people to manage zone files. The zone files contain quite bit of valuable information, including domain names, the name server names associated with those domains and the IP addresses for the name servers. ICANN officials said they are notifying any users whose zone data might have been compromised." (Here's ICANN's public note on the compromise.)

onproton writes: Amazon outbid Google at the ICANN auction this week for the top-level domain .buy , to which it now has exclusive rights, paying around $4.6 million for the privilege. Google was also reportedly outbid for the .tech domain, which went for around $6.7 million. No word yet on Amazon's plans for the new domain suffix, but it's probably safe to say amazonsucks.buy will be added to Amazon's collection of reserved anti-Amazon URLs.

An anonymous reader writes The debate over Internet governance for much of the past decade has often come down to a battle between ICANN and the United Nations. The reality has always been far more complicated. The U.S. still maintains contractual control over ICANN, while all governments exert considerable power within the ICANN model through the Governmental Advisory Committee (GAC). Now governments are looking for even more power, seeking a near-complete veto power of ICANN decisions.

New submitter gwstuff writes "Last year, Google filed applications for about 100 top level domains. These included .app, .cloud and .lol, but perhaps most prominently .search, which they had requested to operate as a 'dotless' domain. [Friday], ICANN gave their verdict on the idea that would make this URL valid : NO. Here is the formal announcement, and a related Slashdot story from last year. So that's that. But it may still be granted the rights for the remaining 100. Is prime dot-com real estate going to become a thing of the past?"

hypnosec writes "ICANN (Internet Corporation for Assigned Names and Numbers) has approved the first set of global Top Level Domains (gTLDs) and surprisingly all four are non-English words including . ("Web" in Arabic); . ("Game" in Chinese); . ("Online" in Russian); and . ("Web site" in Russian). Approval of four non-English words can be considered as a milestone and this approval marks "the first time that people will be able to access and type in a website address for generic Top-Level Domains in their native language.""

hypnosec writes "ICANN, as a step towards expanding global top level domain names, has approved a new Domain Name Registrar Accreditation Agreement that is expected to bring about waves of continued improvements in the domain name ecosystem (PDF). The new agreement is a result of efforts of over a year of negotiations that took place between ICANN and Registrar Stakeholders Group. The new agreement brings quite a few improvements, including making it mandatory for registrars to appoint a point-of contact for reporting abuse, and to establish registrar responsibilities for reseller compliance, enhancement of compliance tools, audit rights, and certification requirements, among others."

itwbennett writes "If you want to protect your brand before ICANN rolls out the new gTLDs (generic top-level domains), here's your chance. The clearinghouse will allow trademark owners to register their marks for an annual fee of between $95 and $150. The clearinghouse 'doesn't necessarily prevent trademark infringement or cybersquatting, but it does help trademark owners and brand owners somewhat in mitigating the damage that might occur,' said Keith Kupferschmid, general counsel and vice president of IP policy and enforcement for the Software and Information Industry Association (SIIA). 'We've been telling brand owners it's not that expensive to protect themselves and they ought to do it.'" All of the new TLD registrars will be required to check the trademark clearinghouse before issuing domains, preemptively squashing trademark disputes.

hypnosec writes "The Internet Corporation for Assigned Names and Numbers has approved and released a list of domain names as per its new global Top Level Domain plans. A total of 27 domain names have been cleared for use by ICANN, and all of them are non-English domain names. Consisting of Chinese and Arabic names, the list of domain names seems to be mostly for regional companies, prominent among which are the .Qatartelecom and .Mozaic domains."

ICANN.org says, "The DotOrg Foundation [update: Note that the organization is now known as the Public Interest Registry], along with its operating partners, is committed to stable, efficient and affordable management of the .org registry." Most of us don't spend a lot of time thinking about the Internet's basic "plumbing," and few spend much time thinking about .org and the group that is responsible for maintaining it. That group did, however, have a booth at SXSW. That's where Timothy Lord interviewed .org spokesperson Thuy LeDinh, who was happy to explain what the .org people do and why they do it.

ICANN.org says, "The DotOrg Foundation [update: Note that the organization is now known as the Public Interest Registry], along with its operating partners, is committed to stable, efficient and affordable management of the .org registry." Most of us don't spend a lot of time thinking about the Internet's basic "plumbing," and few spend much time thinking about .org and the group that is responsible for maintaining it. That group did, however, have a booth at SXSW. That's where Timothy Lord interviewed .org spokesperson Thuy LeDinh, who was happy to explain what the .org people do and why they do it.

judgecorp writes "ICANN has held a raffle to determine in what order it will examine new domain name applications. This doesn't guarantee applicants will win the generic top-level domain (gTLD) they have set their hearts on, as the applications still have to be considered. There may be competition, or objections such as the South American governments' objection to Amazon's .amazon bid. None of the first batch is an English language domain, and the first one likely to make it through all the hurdles is an application by the Vatican, for a domain spelling 'catholic' in Chinese."

hypnosec writes "ICANN is receiving more and more requests for new generic top level domains, and governments around the world are busy registering their complaints and objections with the proposed names. To date, more than 200 objections have been raised against proposed gTLDs, with Australia leading the pack with over 120 objections. Some of the other countries which are at the forefront of registering their objections include France, Germany and India. US and UK are near the bottom of the list. ICANN's "early warnings" about national objections to gTLDs serves as formal objections but it doesn't mean that these domains will never be signed off. There is always room for discussions and mediation that would allow prospective registrants to keep on pursuing their claims. Australia has objected to names such as '.baby,' '.app,' and '.beauty' among other. It has also objected to names such as '.sucks' and '.wtf,' stating that these names have 'an overtly negative or critical connotation.'"

First time accepted submitter benyacrick writes "WHOIS was invented as an address book for sysadmins. These days, it's more likely to be used by Law Enforcement to identify a perpetrator or victim of an online crime. With ICANN's own study showing that 29% of WHOIS data is junk, it's no surprise that Law Enforcement have been lobbying ICANN hard to improve WHOIS accuracy. The EU's privacy watchdog, the Article 29 Data Protection Working Party, has stepped into the fray with a letter claiming that two of Law Enforcement's twelve asks are "unlawful" (PDF). The problem proposals are data retention — where registrant details will be kept for up to two years after a domain has expired — and re-verification, where a registrant's phone number and e-mail will be checked annually and published in the WHOIS database. The community consultation takes place at ICANN 45 in Toronto on October 15th."

First time accepted submitter benyacrick writes "WHOIS was invented as an address book for sysadmins. These days, it's more likely to be used by Law Enforcement to identify a perpetrator or victim of an online crime. With ICANN's own study showing that 29% of WHOIS data is junk, it's no surprise that Law Enforcement have been lobbying ICANN hard to improve WHOIS accuracy. The EU's privacy watchdog, the Article 29 Data Protection Working Party, has stepped into the fray with a letter claiming that two of Law Enforcement's twelve asks are "unlawful" (PDF). The problem proposals are data retention — where registrant details will be kept for up to two years after a domain has expired — and re-verification, where a registrant's phone number and e-mail will be checked annually and published in the WHOIS database. The community consultation takes place at ICANN 45 in Toronto on October 15th."

First time accepted submitter benyacrick writes "WHOIS was invented as an address book for sysadmins. These days, it's more likely to be used by Law Enforcement to identify a perpetrator or victim of an online crime. With ICANN's own study showing that 29% of WHOIS data is junk, it's no surprise that Law Enforcement have been lobbying ICANN hard to improve WHOIS accuracy. The EU's privacy watchdog, the Article 29 Data Protection Working Party, has stepped into the fray with a letter claiming that two of Law Enforcement's twelve asks are "unlawful" (PDF). The problem proposals are data retention — where registrant details will be kept for up to two years after a domain has expired — and re-verification, where a registrant's phone number and e-mail will be checked annually and published in the WHOIS database. The community consultation takes place at ICANN 45 in Toronto on October 15th."

Qedward writes "The Kingdom of Saudi Arabia has objected to a variety of new generic top-level domains (gTLDs) ranging from .porn and .sexy to .wine and .bar and .bible, according to records of the Internet Corporation for Assigned Names and Numbers (ICANN). The organisation said in June it had received 1930 applications for gTLD 'strings,' of which 911 came from North America and 675 from Europe. Saudi Arabia's Communication and Information Technology Commission, the IT and communications regulator, has objected to the .gay string and asked ICANN to refuse the application for the new gTLD. 'Many societies and cultures consider homosexuality to be contrary to their culture, morality or religion,' CITC said. 'The creation of a gTLD string which promotes homosexuality will be offensive to these societies and cultures,' it added."

Eighteen months after first announcing expansion of the TLD space, ICANN has published the list of new gTLDs that have been applied for. A cursory glance reveals that.app was pretty popular, with 13 applications. Now begins the seven month objection period (but you have to be a large organization to lodge any). angry tapir writes in with info on how duplicate applications will be resolved. From the article: "The Internet Corporation for Assigned Names and Numbers has released statistics about the applications for new top-level domains — so-called 'dot word' domains along the lines of .web and .bank ... Two hundred and thirty of the domains proposed by applicants will become the subject of ICANN's dispute resolution process — which involves an attempt among applicants for the same domain to come to a joint arrangement, followed by an auction if that's unsuccessful. There were 751 conflicting applications for domains in total, which in many cases are likely to involve generic suffixes like .secure."

Eighteen months after first announcing expansion of the TLD space, ICANN has published the list of new gTLDs that have been applied for. A cursory glance reveals that.app was pretty popular, with 13 applications. Now begins the seven month objection period (but you have to be a large organization to lodge any). angry tapir writes in with info on how duplicate applications will be resolved. From the article: "The Internet Corporation for Assigned Names and Numbers has released statistics about the applications for new top-level domains — so-called 'dot word' domains along the lines of .web and .bank ... Two hundred and thirty of the domains proposed by applicants will become the subject of ICANN's dispute resolution process — which involves an attempt among applicants for the same domain to come to a joint arrangement, followed by an auction if that's unsuccessful. There were 751 conflicting applications for domains in total, which in many cases are likely to involve generic suffixes like .secure."

angry tapir writes "ICANN has been subjected to more criticism over the process of creating new 'dot.word' generic top-level domains. Registry services companies have criticised ICANN for processing the 1900 or so applications for new gTLDs in batches, which means that it will take significantly longer for some new domains to go live than others. The real kicker is the process for choosing who goes in which batch: 'Digital archery' — essentially an applicant nominates a particular time then tries to click a button in a browser as close to that time as possible. I should have taken advantage of all those 'punch the monkey' ads in the good ol' days."

As co-designer of TCP/IP (along with Robert E. Kahn), and former chairman of ICANN, it is no exaggeration to say that Vint Cerf is certainly one of the fathers of the internet, and is often referred to as simply the father. His lifetime of network engineering accomplishments — meriting, among many other laurels, the Turing Award — leaves little doubt as to why he's now a full-time internet visionary for Google (and formerly with WorldCom) as well as a Google VP. Now, Cerf has graciously agreed to answer Slashdot readers' inquiries about the past and future of this little thing called the Internet, and his role in it thus far. This short call for questions is inadequate to sum up his contributions to engineering the data flows that entangle and enlighten us in 2011, but read through a few of these capsule descriptions to get a sense of them. In accord with the interview guidelines, please try not to lump together unrelated questions. (You may find that your questions are moderated downward if they aren't concise; if you have several distinct questions, simply submit separately as many as you'd like.)

GeorgeK writes "To update Wednesday's Slashdot article, VeriSign, the .com/net domain name registry, has withdrawn their controversial proposal which would have allowed them to suspend domains without a court order and without due process. VeriSign did not give a reason for the withdrawal. Slashdot 1, VeriSign 0."

GeorgeK writes "VeriSign, the monopoly registry operator for .com/.net domain names, has submitted a proposal to ICANN (PDF) describing an 'Anti-Abuse' policy. If allowed to proceed with such a policy, they would become judge, jury and executioner, with the ability to suspend or even cancel alleged 'abusive' domain names without due process for registrants. The proposal even recognizes that legitimate domain names may be taken down improperly, and offers a 'protest' procedure. However, VeriSign does not appear to offer any ability to protest an accusation of abuse before the suspension or cancellation. They intend to 'shoot first and ask questions later.'"

An anonymous reader writes "The May 10th deadline for comments on the .net registry agreement renewal has arrived with new domain name dispute changes that aid corporations. Instead of UDRP, the new agreement proposes adding the Uniform Rapid Suspension (URS) process to the .net TLD. The URS is a quick $200 process for a trademark holder to disable and take ownership of a domain. URS also reduces the panel size from 1-3 people to a single person. You can still comment on the proposal by sending an email to ICANN (net-agreement-renewal@)."

An anonymous reader writes "The May 10th deadline for comments on the .net registry agreement renewal has arrived with new domain name dispute changes that aid corporations. Instead of UDRP, the new agreement proposes adding the Uniform Rapid Suspension (URS) process to the .net TLD. The URS is a quick $200 process for a trademark holder to disable and take ownership of a domain. URS also reduces the panel size from 1-3 people to a single person. You can still comment on the proposal by sending an email to ICANN (net-agreement-renewal@)."

lothos writes "Pornography will have its own top-level domain, dot-XXX, the board of the Internet Corporation for Assigned Names and Numbers decided today." Ars Technica has a short but thoroughly-linked article tracing some of the long history (in Internet time) behind the push for .xxx. See also ICANN's announcement of the approval, and — for all the juicy details — the rationale behind the decision (PDF).

lothos writes "Pornography will have its own top-level domain, dot-XXX, the board of the Internet Corporation for Assigned Names and Numbers decided today." Ars Technica has a short but thoroughly-linked article tracing some of the long history (in Internet time) behind the push for .xxx. See also ICANN's announcement of the approval, and — for all the juicy details — the rationale behind the decision (PDF).

revealingheart writes "On Thursday, 3 February 2011, at 9:30 AM Eastern Standard Time (EST) [14:30 UTC/GMT], the Number Resource Organization (NRO), along with the Internet Corporation for Assigned Names and Numbers, the Internet Society (ISOC) and the Internet Architecture Board (IAB) will be holding a ceremony and press conference to make a significant announcement and to discuss the global transition to the next generation of Internet addresses. We invite all interested community members to view the webcast of this event."

think_nix writes "A letter to ICANN (PDF) from Victoria Sheckler, Deputy General Counsel for the RIAA, demands modifications to the future implementation of the .music gTLD, threatening to 'escalate the issue' if certain concerns about 'wide scale copyright and trademark infringement' are not addressed by ICANN in compliance with the RIAA. 'Under the current proposed standard, we fear that we will have no realistic ability to object if a pirate chooses to hijack a music themed gTLD to enable wide scale copyright infringement of our works,' Sheckler said."

penciling_in writes "CircleID reports that the Internet Corporation for Assigned Names and Numbers (ICANN) has announced its approval of non-Latin string evaluation of 'Iran.' This approval will allow the availability of Iran's top-level domain in its own native language, Persian, also known as Farsi (that is, the domain name .IRAN, in non-Latin characters). According to ICANN, there are currently 33 requests for Internationalized Domain Names (IDN) country code Top-Level Domains (ccTLDs), representing 22 languages, out of which 18 countries/territories have so far been approved."

mysidia writes "A total of 16,777,216 IP address numbers were just allocated to the Asian Pacific Network Information Centre IP address registry for assignment to users. Some venerable IP addresses such as 1.1.1.1 and 1.2.3.4 have been officially assigned to the registry itself temporarily, for testing as part of the DEBOGON project. The major address blocks 1.0.0.0/8 and 27.0.0.0/8, are chosen accordance with a decision by ICANN to assign the least-desirable remaining IP address ranges to the largest regional registries first, reserving most more desirable blocks of addresses for the African and Latin American internet users, instead of North America, Europe, or Asia. In other words: of the 256 major networks in IPv4, only 24 network blocks remain unallocated in the global free pool, and many of the remaining networks have been tainted or made less desirable by unofficial users who attempted an end-run around the registration process, and treated 'RESERVED' IP addresses as 'freely available' for their own internal use. This allocation is right on target with projected IPv4 consumption and was predicted by the IPv4 report, which has continuously and reliably estimated global pool IP address exhaustion for late 2011 and regional registry exhaustion by late 2012. So, does your enterprise intranet use any unofficial address ranges for private networks?" Reader dude_nl sends in a summary of the issues with allocating from 1.0.0.0/8 from the BGPmon.net blog. "As Alain Durand mentioned on Nanog: 'Who said the water at the bottom of the barrel of IPv4 addresses will be very pure? We ARE running out and the global pain is increasing.'"

Several readers including alphadogg tipped the news that ICANN has approved non-Latin ccTLDs at its meeting in Seoul. "Starting in mid-November, countries and territories will be able to apply to show domain names in their native language, a major technical tweak to the Internet designed to increase language accessibility. On Friday, the Internet's addressing authority approved a Fast-Track Process for applying for an IDN (Internationalized Domain Name) and will begin accepting applications on Nov. 16. The move comes after years of technical testing and policy development... Currently, domain names can only be displayed using the Latin alphabet letters A-Z, the digits 0-9 and the hyphen, but in future countries will be able to display country-code Top Level Domains (cc TLDs) in their native language. ... 'The usability of IDNs may be limited, as not all application software is capable of working with IDNs,' ICANN said in a 59-page proposal (PDF) dated Sept. 30 that describes the [application] process." Reader dhermann adds, "Great, now even less chance I can identify NSFW links before they are blocked by my work's big brother app and my boss is notified... again."

stry_cat writes "Over a year ago ICANN moved to clean up misbehaving registrars like GoDaddy. They released this scary sounding advisory. However, over a year later, problems remain. One company is now publicly complaining. Some of the biggest registrars are slammed for their actions. 'Register.com is one frustrating company. The ICANN policy clearly prohibits blocking a transfer of a domain name that has expired but not yet been deleted. Despite that, a customer trying to transfer a three-day-expired Register.com domain name told us last week that they refused to give him the necessary code to allow him to transfer — unless he pays them to renew it first. ... GoDaddy (and their reseller arm, Wild West Domains) have a different problem: They still block transfers for 60 days after a registrant's contact update, even after the ICANN update specifically prohibited doing so. They freely admit it, too. ... We see a similar problem with many transfers from Network Solutions.'"

stry_cat writes "Over a year ago ICANN moved to clean up misbehaving registrars like GoDaddy. They released this scary sounding advisory. However, over a year later, problems remain. One company is now publicly complaining. Some of the biggest registrars are slammed for their actions. 'Register.com is one frustrating company. The ICANN policy clearly prohibits blocking a transfer of a domain name that has expired but not yet been deleted. Despite that, a customer trying to transfer a three-day-expired Register.com domain name told us last week that they refused to give him the necessary code to allow him to transfer — unless he pays them to renew it first. ... GoDaddy (and their reseller arm, Wild West Domains) have a different problem: They still block transfers for 60 days after a registrant's contact update, even after the ICANN update specifically prohibited doing so. They freely admit it, too. ... We see a similar problem with many transfers from Network Solutions.'"

An anonymous reader writes "Comcast has finally launched its DNS Redirector service in trial markets (Arizona, Colorado, New Mexico, Oregon, Texas, Utah, and Washington state), and has submitted a working draft of the technology to the IETF for review. Comcast customers can opt-out from the service by providing their account username and cable modem MAC address. Customers in trial areas using 'old' Comcast DNS servers, or non-Comcast DNS servers, should not be affected by this. This deployment comes after many previous ISPs, like DSLExtreme, were forced to pull the plug on such efforts as a result of customer disapproval/retaliation. Some may remember when VeriSign tried this back in 2003, where it also failed."

jhutkd writes "On June 3rd, 2009, ICANN and NIST announced formal plans to use DNSSEC to sign the DNS root zone by the end of 2009. This is a huge step forward for the deployment of DNSSEC."

An anonymous reader writes "After coverage here on Slashdot and elsewhere, Cheryl Preston has responded. She says that 'some netizens have missed the mark by turning the rather hum-drum constituency formation issue into a rash of (admittedly sometimes quite humorous) charges, allegations, and ad hominem attacks. I can only wish that I had control of some global Mormon conspiracy network, that this were a money-making proposition, and that my powers of persuasion could possibly move ICANN to adopt a content regulatory system...in reality, the CyberSafety constituency is interested in many current GNSO issues, such as Fast Flux Hosting (FFH); the development of a Registrants' Rights Charter; the gathering of identity information on WHOIS; and public order issues with the granting of new Top Level Domain names, to name a few.'"

An anonymous reader writes "After coverage here on Slashdot and elsewhere, Cheryl Preston has responded. She says that 'some netizens have missed the mark by turning the rather hum-drum constituency formation issue into a rash of (admittedly sometimes quite humorous) charges, allegations, and ad hominem attacks. I can only wish that I had control of some global Mormon conspiracy network, that this were a money-making proposition, and that my powers of persuasion could possibly move ICANN to adopt a content regulatory system...in reality, the CyberSafety constituency is interested in many current GNSO issues, such as Fast Flux Hosting (FFH); the development of a Registrants' Rights Charter; the gathering of identity information on WHOIS; and public order issues with the granting of new Top Level Domain names, to name a few.'"

An anonymous reader writes "After coverage here on Slashdot and elsewhere, Cheryl Preston has responded. She says that 'some netizens have missed the mark by turning the rather hum-drum constituency formation issue into a rash of (admittedly sometimes quite humorous) charges, allegations, and ad hominem attacks. I can only wish that I had control of some global Mormon conspiracy network, that this were a money-making proposition, and that my powers of persuasion could possibly move ICANN to adopt a content regulatory system...in reality, the CyberSafety constituency is interested in many current GNSO issues, such as Fast Flux Hosting (FFH); the development of a Registrants' Rights Charter; the gathering of identity information on WHOIS; and public order issues with the granting of new Top Level Domain names, to name a few.'"

An anonymous reader writes "After coverage here on Slashdot and elsewhere, Cheryl Preston has responded. She says that 'some netizens have missed the mark by turning the rather hum-drum constituency formation issue into a rash of (admittedly sometimes quite humorous) charges, allegations, and ad hominem attacks. I can only wish that I had control of some global Mormon conspiracy network, that this were a money-making proposition, and that my powers of persuasion could possibly move ICANN to adopt a content regulatory system...in reality, the CyberSafety constituency is interested in many current GNSO issues, such as Fast Flux Hosting (FFH); the development of a Registrants' Rights Charter; the gathering of identity information on WHOIS; and public order issues with the granting of new Top Level Domain names, to name a few.'"

angry tapir writes "ICANN has delayed its plans to sell new generic top-level domains while responding to public comments about the controversial proposal. The organization has released a 154-page document detailing and analyzing the hundreds of comments (PDF) it has received about its gTLD plan. In response to several concerns brought up by the public and companies in the Internet industry, ICANN has moved out the projected timeline for taking applications for new gTLDs from September to December."

ICANN posted its proposal for expanding gTLDs late in October, and now the US government has issued its scathing response (PDF, 11 pp., linked from there), from the departments of Commerce and Justice. The initial criticism is that John Levine sent a note to a policy mailing list and summarized the concerns raised as ranging from "...insufficient attention to monopoly and consumer protection, to lack of capacity to enforce compliance, to overreach into non-technical areas such as adjudication of morality, to what they'll do with all the extra money since they are a non-profit. Their first concern is that in 2006 the ICANN board said they would commission a study on economic issues in TLD registrations such as whether different TLDs are different markets, substitutability between TLDs, and registry market power, issues which are fairly important in any new TLD process. Here it is two years later, they're rushing to set up the new TLD process, but there's no study. 'ICANN needs to complete this economic study and the results should be considered by the community before new gTLDs are introduced.'"

narramissic writes "Late last week, ICANN put up for comment a new top-level domain (TLD) proposal that would open up the market for generic TLDs on the Internet, basically allowing anyone with $185,000 to buy a new TLD. ICANN has based the cost of a generic TLD on what it believes will be the cost to evaluate applications and protect the organization against risk, said Paul Levins, ICANN's executive officer and vice president for corporate affairs. Any excess money would be redistributed based on the wishes of the Internet community, he said. As of late Tuesday, there were only a couple of comments on the proposal."