Skip to main content
Resources

Document Publication Operational Policy

Open: 8 September 09
Closed: 8 October 09

Explanation: In an effort to build on existing best practices, and to encourage the early sharing of documentation that is primarily intended for public review and discussion, a document publication operational policy [PDF, 146 KB] has been developed for use across ICANN at the organization’s international public meetings.

The intent of the operational policy is to provide a clear framework and guidelines for the consistent publication of work across the organization and so enable wide dialogue throughout the community. It will be reviewed in the light of each meeting in an effort to continuously improve ICANN operations.

That operational policy includes: a single 15-working-day deadline for all documents (including meetings agendas) ; best practice guidelines on the production of meeting agendas, cover sheets and executive summaries ; an emphasis on the use of plain language and minimised use of jargon; and sections considering the issues of translation, earlier provision of presentations, and reporting on the efficacy of the operational policy.

You are invited to discuss and comment any part of the policy online with suggestions for changes. You will need to register to add comments online. The results of the discussion will result in changes to the policy before it is put to the Board for review and approval.

The policy is split into clear sections to encourage focussed responses but at the same time, a number of broader questions are also asked below:
  • Is the community (and staff) prepared for the early provision of documents?
  • Are you sufficiently persuaded of the need for a document deadline to change established approaches and cultures?
  • How do we effectively tackle the issue of language/jargon?
Staff member responsible: Kieren McCarthy

Announcement | Discussion space | Summary/analysis of comments

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