Skip to main content

Additional Coordination Through New Transition Facilitation Calls

One of the words most often heard during the IANA Stewardship Transition and Enhancing ICANN Accountability processes has been coordination – coordination amongst communities, coordination amongst members and participants of working groups, coordination amongst community and staff members.

As many who follow these processes know, they can at times be complex, and are interrelated. One group can rely on another for various needs, such as the formal dependency between CWG-Stewardship and CCWG-Accountability, or the necessary inputs groups contribute into each other's processes by way of Public Comment periods.

At an informal breakfast meeting during ICANN53 in Buenos Aires with many of the transition working group chairs and SO/AC leaders, we shared a working draft transition timeline, and discussed how we could better ensure clearer alignment amongst all the agendas, timelines and expectations.

As a result of the discussion that followed, the group decided it would hold monthly facilitation calls with each other, ICANN leadership and NTIA, to discuss where each group stands at that given point in time. The group also decided that these meetings would not to be used to discuss substance.

The group agreed to share publicly the working draft transition timeline [PDF, 1.01 MB], as well as an audio file [MP3, 8.32 MB] of the first call with the community held last Thursday. As we move steadily towards completion of the first phase of the IANA Stewardship Transition process, it is vital that we all stay aligned, and these monthly calls will help facilitate that.

To listen to the audio of the first call, please see here: http://audio.icann.org/iana-stewardship-draft-transition-timeline-16jul15-en.mp3 [MP3, 8.32 MB]

- TS

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