Skip to main content

Root Zone Evolution Review Committee (RZERC)

The RZERC reviews proposed architectural changes to the content of the DNS root zone, the systems including both hardware and software components used in executing changes to the DNS root zone, and the mechanisms used for distribution of the DNS root zone. The RZERC was formed as a result of the IANA Stewardship Transition.

About RZERC

Overview

In the ICG proposal, the domain names community required that a standing committee be put into place that will provide recommendations to the ICANN Board regarding the advisability of moving forward with all major architectural changes to the DNS root. ICANN named this committee the Root Zone Evolution Review Committee (RZERC). The RZERC will consider issues raised by any of its members, PTI, or by the CSC.

While the RZERC will not necessarily be the group that considers the details of the issues under consideration, it will be responsible for ensuring that those involved in the decision include all relevant bodies and have access to necessary expertise. As such, the RZERC will coordinate with relevant organizations and communities, and if appropriate, external experts, to confirm that all affected parties are involved in discussions and recommendations regarding architectural changes to the root zone.

Latest Updates

  • 12 Aug 2018

    RZERC has published: Feedback on the Updated Plan for Continuing the Root Key Signing Key (KSK) Rollover 

  • 26 Jul 2018

    Meeting minutes, audio recording and transcript from the RZERC Teleconference Call on 25 June 2018 have been published

  • 25 Jun 2018

    Meeting minutes, audio recording and transcript from the RZERC Teleconference Call on 22 May 2018 have been published

  • 07 Feb 2018

    Meeting minutes, audio recording and transcript of 11 December 2017 RZERC Teleconference call available

  • 11 Dec 2017

    RZERC has suspended monthly Teleconference Calls until proposals are received. The committee will have one public meeting during the year next ICANN General Meeting next fall 2018. 

  • 01 Nov 2017

    Meeting minutes, audio recording and transcript of 1 November 2017 RZERC Teleconference call and Public Meeting available

  • 29 Oct 2017

    Meeting minutes, audio recording and transcript of 29 Ocotber 2017 RZERC Teleconference call and Executive Session are available

  • 25 Oct 2017

    Notice of RZERC Public Meeting

    1 November 2017 – Public Meeting of the Root Zone Evolution Review Committee - at 10:00 UTC (2:00pm in Abu Dhabi).

    https://www.icann.org/en/rzerc/1-november-2017-public-meeting-of-the-icann-root-zone-evolution-review

  • 16 Oct 2017

    Meeting minutes, audio recording and transcript of 25 September 2017 RZERC Teleconference call available

  • 16 Oct 2017

    Meeting minutes, audio recording and transcript of 16 Ocotber 2017 RZERC Teleconference call available

  • 28 Sep 2017

    Meeting minutes, audio recording and transcript of 21 August 2017 RZERC Teleconference call available

  • 06 Sep 2017

    RZERC Operational Procedure document has been approved and published

  • 24 Jul 2017

     Meeting minutes, audio recording and transcript of 17 July 2017 RZERC Teleconference call available

  • 17 Jul 2017

    Minutes, audio recording and transcript of 19 June 2017 RZERC Teleconference call available

  • 23 Jun 2017

    Minutes, audio recording and transcript of 22 May 2017 RZERC Teleconference call available

  • 24 May 2017

    Minutes, audio recording and transcript of the 4 April RZERC Teleconference call available.

  • 24 May 2017

    Upcoming RZERC meeting next 19 June 17:00-18:00 UTC

  • 01 Mar 2017

    Duane Wessels selected as the Chair of RZERC. Duane represents the Root Zone Maintainer. His term starts in March 2017. 

  • 01 Mar 2017

    RZERC Website LIVE! Comments please send to mario.aleman@icann.org.

Meetings & Work Sessions

Document Archive & Links

Related Links

A note about our privacy policies and terms of service:

We have updated our privacy policies and certain website terms of service to provide greater transparency, promote simplification, and align with recent changes in privacy laws applicable to us. Learn more.

This site uses cookies to deliver an efficient user experience and to help us see how the site is used. Learn more.OK

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