Skip to main content

DNSO Transfers and Whois Task Forces Post Reports; Comments Invited

The DNSO Names Council Transfers and Whois Task Forces have issued reports and invited public comment on them:

Transfers Task Force

The DNSO Names Council's Transfers Task Force has issued its "Final Report & Recommendations – Policies and Processes for Gaining and Losing Registrars". This report submits twenty-eight policy recommendations to the Names Council for consideration as consensus policies. These recommendations are the subject of item 3 on the agenda for the Names Council's 14 December 2002 meeting:

3. Transfers Task Force final report and recommendations (40mins)
Transfers Task Force final report:
<http://www.dnso.org/dnso/notes/20021130.NCTransferTF-gaining-and-losing-registrars.html>

  • for decision (deadline for report 30 Nov 2002)
  • confirm and approve consensus policy recommendations

The Names Council is soliciting additional public comment on this report until 8 December 2002. Comments should be sent by e-mail to <comments-transfer@dnso.org>. Comments will be archived here.

Whois Task Force

The DNSO Names Council's Whois Task Force has issued its Policy Report on Whois Accuracy and Bulk Access. The report contains consensus policy recommendations as well as advice and comment from the Task Force. These recommendations are the subject of item 4 on the agenda for the Names Council's 14 December 2002 meeting:

4. Whois Task Force final report and recommendations (40 mins)
Whois TF Policy Report on Accuracy and Bulk Access:
<http://www.dnso.org/dnso/notes/20021130.NCWhois-TF-accuracy-and-bulkaccess.html>

  • for decision (deadline for report 30 Nov 2002)
  • confirm and approve consensus policy recommendations

The Names Council is soliciting additional public comment on this report until 8 December 2002. Comments should be sent by e-mail to <comments-whois@dnso.org>. Comments will be archived here.


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""icann.org"" is not an IDN."