ICANN Update on RegisterFly ...
March 3rd, 2007 by Domain Tools Team
" ICANN has posted a public update on the RegisterFly situation we reported about earlier and it doesn’t look good. On February 21st, 2007, ICANN issued a letter to RegisterFly [PDF, 101K] indicating a Notice of Breach of its Registrar Accreditation Agreement (RAA) and demanding that RegisterFly act within 15 working days to cure the breaches outlined in the letter. Also on February 21st, ICANN sent a Notice of Audit [PDF, 60K] that required RegisterFly to allow ICANN to inspect and copy its records. In addition they were given notice to submit data to ICANN or a reputable escrow agent regarding registration applications and Registered name holders. Five days later on February 27th, 2007, ICANN sent two employees to RegisterFly’s offices in New Jersey to audit them and obtain the registrant information. RegisterFly did not compile and refused to give ICANN the Information. Two days later on March 1st, 2007 RegisterFly’s lawyers forwarded a letter [PDF, 12K] to ICANN advising that refusal to comply with ICANN’s request “should not be construed as my client’s unwillingness to cooperate with ICANN but as evidence of their continuing efforts to service their customers.” In response ICANN has issued a second letter [PDF, 288K] dated March 2nd, 2007 setting out additional breaches of the Registrar Agreement and in that letter ICANN describes RegisterFly’s refusal to comply which was based on their “continuing efforts to service their customers” as “preposterous“.
It seems that RegisterFly is continuing to breach the RAA is seen as very serious and ICANN is in hot pursued. It is very clear that RegisterFly is about to crash and burn. ICANN’s primary concern is to do what it can to protect registrant and related data. ICANN has provided notice that it will file a suit against RegisterFly in the United States District Court for the Central District of California seeking a temporary restraining order (TRO) requiring RegisterFly to turn over the data requested and to compel an emergency audit of its books and records. In addition to this legal action, ICANN today convened a telephone conference among those needed to implement a plan that will help cease unintended deletions. The participants were registries holding RegisterFly names: Afilias (.info), Neustar (.biz), VeriSign (.com, .net), RegisterFly backend services provider Tucows and eNom (for which RegisterFly was a reseller) as well as representatives of RegisterFly. The Registries involved have agreed to move any RegisterFly names in Redemption Grace Period status into Server-Delete-Prohibited status. This will prevent them from being deleted from the registry and becoming available for re-registration by others. ICANN commends and encourages this example of cooperation to protect registrant data. "
- http://blog.domaintools.com/2007/03/icann-update-on-registerfly/
" ICANN has posted a public update on the RegisterFly situation we reported about earlier and it doesn’t look good. On February 21st, 2007, ICANN issued a letter to RegisterFly [PDF, 101K] indicating a Notice of Breach of its Registrar Accreditation Agreement (RAA) and demanding that RegisterFly act within 15 working days to cure the breaches outlined in the letter. Also on February 21st, ICANN sent a Notice of Audit [PDF, 60K] that required RegisterFly to allow ICANN to inspect and copy its records. In addition they were given notice to submit data to ICANN or a reputable escrow agent regarding registration applications and Registered name holders. Five days later on February 27th, 2007, ICANN sent two employees to RegisterFly’s offices in New Jersey to audit them and obtain the registrant information. RegisterFly did not compile and refused to give ICANN the Information. Two days later on March 1st, 2007 RegisterFly’s lawyers forwarded a letter [PDF, 12K] to ICANN advising that refusal to comply with ICANN’s request “should not be construed as my client’s unwillingness to cooperate with ICANN but as evidence of their continuing efforts to service their customers.” In response ICANN has issued a second letter [PDF, 288K] dated March 2nd, 2007 setting out additional breaches of the Registrar Agreement and in that letter ICANN describes RegisterFly’s refusal to comply which was based on their “continuing efforts to service their customers” as “preposterous“.
It seems that RegisterFly is continuing to breach the RAA is seen as very serious and ICANN is in hot pursued. It is very clear that RegisterFly is about to crash and burn. ICANN’s primary concern is to do what it can to protect registrant and related data. ICANN has provided notice that it will file a suit against RegisterFly in the United States District Court for the Central District of California seeking a temporary restraining order (TRO) requiring RegisterFly to turn over the data requested and to compel an emergency audit of its books and records. In addition to this legal action, ICANN today convened a telephone conference among those needed to implement a plan that will help cease unintended deletions. The participants were registries holding RegisterFly names: Afilias (.info), Neustar (.biz), VeriSign (.com, .net), RegisterFly backend services provider Tucows and eNom (for which RegisterFly was a reseller) as well as representatives of RegisterFly. The Registries involved have agreed to move any RegisterFly names in Redemption Grace Period status into Server-Delete-Prohibited status. This will prevent them from being deleted from the registry and becoming available for re-registration by others. ICANN commends and encourages this example of cooperation to protect registrant data. "
- http://blog.domaintools.com/2007/03/icann-update-on-registerfly/
posted by JamesB at 10:22 AM
0 Comments:
Post a Comment
<< Home