Skip to main content

ICANN Announces the Formation of Two Committees Required for IANA Stewardship Transition

ICANN today announced the formation of the Customer Standing Committee (CSC) and the Root Zone Evolution Review Committee (RZERC). Both newly formed committees are requirements for the completion of the IANA Stewardship Transition by the CWG-Stewardship.

The CSC will perform the operational oversight of the performance of the IANA naming function, a role currently performed by NTIA. In its oversight role, the CSC will monitor the performance of the IANA naming function against agreed service level expectations. The CSC may also initiate reviews and make recommendations for post-transition changes to service level expectations. For more information, please see the CSC Charter [PDF, 139 KB] or the CSC Scope and Responsibilities [PDF, 83 KB]. Per the CSC Charter, the Country Code Names Supporting Organization (ccNSO) and the Generic Names Supporting Organization (GNSO) Councils have approved the full slate of the membership.

The RZERC will review proposed architectural changes to the content of the root zone, the systems (including both hardware and software components) used in executing changes to the root zone and the mechanisms used for distribution of the root zone. It will also make recommendations related to those changes for consideration by the ICANN Board. The ICANN Board's approval of recommendations developed through the RZERC will replace NTIA's current role in approval of architectural changes to the root zone. The ICANN Board adopted the RZERC Charter [PDF, 50 KB], finalized through public comment, on 10 August 2016. See the full committee here.

These committees will not become operational unless and until the expiration of the IANA Functions Contract.

Additional details on ICANN's implementation planning efforts can be found at https://www.icann.org/stewardship-implementation.


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