Skip to main content

RegisterFly update: 24 June 2007

The last update on the RegisterFly situation covered the deal struck between RegisterFly and GoDaddy that saw all the registrar’s domains transferred over to GoDaddy.

That deal has seen the vast majority of domain issues sorted out. However, as far as ICANN is concerned, RegisterFly and Kevin Medina were in breach of their contract and ICANN has continued to prosecute its case against the company.

On 4 June 2007, RegisterFly applied to the court to modify the Permanent Injunction against it.

On 8 June 2007, the Court denied RegisterFly’s application and set a hearing for 12 June 2007 regarding the company’s lack of compliance with the Permanent Injunction. Mr. Medina’s was ordered to appear personally.

On 12 June 2007, ICANN provided the Court with an update on RegisterFly’s compliance, noting the remaining deficiencies. The Court ordered a further hearing for 15 June 2007 and noted that if RegisterFly had not fully complied with the Permanent Injunction by that date he would begin calculating sanctions.

On 13 June 2007, the Court entered the Permanent Injunction and ruled that RegisterFly was in default on the underlying action.

At the hearing on 15 June 2007, ICANN instructed the Court that RegisterFly had finally at least attempted to comply with the Permanent Injunction provisions, but since most of the data had been provided to ICANN the previous afternoon, ICANN reserved the right to seek further relief if the data RegisterFly provided to ICANN was not compliant.

During the hearing, the Court continued to show its dissatisfaction with Mr. Medina’s conduct.

Related point:

ICANN will be holding a public meeting tomorrow that will review, among other things, changes to the registrar system that, it is hoped, will ensure that the RegisterFly situation does not reoccur. The meeting will be held on Monday 25 June at 1pm EST at ICANN’s meeting in Puerto Rico.

Those unable to attend will be able to follow events online and will be able to participate in the discussion through ICANN’s public participation site. A specific meeting webpage for the event will see questions will be taken from the public and from remote users and introduced into the meeting – for more information review the blog post here.


    Domain Name System
    Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as"""" is not an IDN."