Skip to main content

Welcome to the new! Learn more, and send us your feedback. Dismiss

Advisory Concerning .org Transition

On 1 January 2003, Public Interest Registry (PIR) officially assumed responsibility as the registry operator for the .org top-level domain.

PIR is a not-for-profit corporation created by the Internet Society (ISOC) to manage the .org registry. PIR was selected by ICANN from among eleven competing proposals through an open request-for-proposals process. Proposals were judged on criteria including the need to preserve a stable, well-functioning .org registry, enhancement of competition for registration services; responsiveness to the noncommercial Internet user community; and the type, quality, and cost of the registry services proposed.

The overall purpose of changing operators of the .org registry is to enhance the diversity of providers in the provision of registry services. This purpose is being accomplished in a way that preserves the security and stability of the domain-name system.

Operationally, 1 January was only one of several milestones that must be passed to complete the transition of the .org registry. As of 1 January, all registrars wishing to continue to sponsor their customers' registrations in .org were required to enter into Registry-Registrar Agreements (RRAs) with PIR. (The .org RRAs with VeriSign expired on 31 December 2002.) All but a few very small registrars have completed this step; we expect the remaining RRAs to be completed quickly.

During the first 25 days of January, VeriSign Global Registry Services (VeriSign) will continue to operate the registry system, as a subcontractor to PIR. On Saturday, 25 January, the operation of the .org registry will be shifted to Afilias, the subcontractor selected by PIR. To allow time for the processes required to separate the .org registry from the .com and .net registries, there will be a period of approximately seven hours on that day when changes cannot be made in any of the three registries. (This outage coincides with a software upgrade at VeriSign registry, which among other things will introduce support for the Redemption Grace Period feature.)

After the registries come back up after this outage, registrars must send requests for changes to .org names to Afilias, while still sending changes for .com and .net registrations to VeriSign. The protocol (other than the registry IP address) will remain unchanged. Although many registrar systems will need to be revised to properly handle the split, significant problems are not expected. (All registrars' systems will be required to complete testing and qualification beforehand.)

As described in the PIR (ISOC) proposal, once the split of registries is completed PIR/Afilias will begin a migration from the current "thin" registry to a "thick" registry. (This is very similar to the registry system Afilias currently operates for .info.) This migration will be done on a registrar-by-registrar basis.

VeriSign will continue providing nameservice for the .org top-level domain (using zone files prepared by Afilias) for approximately six months. Nameservice for the .org domain will then be transitioned to UltraDNS, which provides nameservice under contract with Afilias.

For additional information concerning the .org transition, please refer to the following sources:

More Announcements
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."