Skip to main content

Evolving the Governance of the Root Server System

Today, ICANN org is launching a Public Comment proceeding on evolving the governance of the Root Server System (RSS). We invite the ICANN community to participate in this important work.

Following the IANA stewardship transition, the Root Server System Advisory Committee (RSSAC) developed an initial framework to evolve the governance of the RSS. Supporting the evolution of RSS governance contributes to ICANN's commitment to strengthen the security, stability, and resiliency of the Domain Name System (DNS). It also enables direct interaction between the ICANN community and Root Server Operators (RSOs). Furthermore, it ensures that global root service remains accountable and sustainable into the future.

After three years of extensive RSSAC work, the RSSAC published "RSSAC037: A Proposed Governance Model for the DNS Root Server System" (RSSAC037) in June 2018. The RSSAC concurrently published "RSSAC038: RSSAC Advisory on a Proposed Governance Model for the Root Server System" (RSSAC038), making three recommendations for next steps to the ICANN Board.

As part of the ICANN Board's consideration of RSSAC037 and RSSAC038, ICANN org prepared a "Concept Paper on a Community-Driven Process to Develop a Final Model Based on RSSAC037". The Concept Paper proposes a governance model based on RSSAC037 as well as a community-driven process to develop a final governance model for the RSS in response to a recommendation from RSSAC038.

RSSAC037 and RSSAC038 address outstanding and unanswered questions around DNS root service accountability, financial stability, and sustainability. The ICANN Board and ICANN org appreciate the significant work of the RSSAC and the important role and continued commitment of the RSOs.

We recognize that not every community group is familiar with the RSS, RSOs, and global root service. The Public Comment proceeding provides additional RSSAC publications as resources for context and background.

The RSSAC, ICANN Board, and ICANN org look forward to your input.


    Rama  20:25 UTC on 25 May 2019

    Current information has become a very important commodity. Furthermore, many parties think that the present era is an age of information or known as an information based society. See karina-d-p-fisip11(dot)web(dot)unair(dot)ac(dot)id/artikel_detail-79279-Tugas%20-Keamanan%20Sistem%20Informasi(dot)html for a complete explanation of information systems

    software hris indonesia  22:23 UTC on 30 May 2019

    are this compatible with windows xp?

    Fred Baker  09:03 UTC on 03 June 2019

    Yes, Windows XP uses the Domain Name System, of which this is part. For example, in this post, when your computer asks for the address associated with www(dot)icann(dot)org, the DNS Root would tell it (or the resolver it uses) the information related to (dot)org, and the resolver would in turn return resource records for icann(dot)org and www(dot)icann(dot)org.

    brett carr  03:46 UTC on 05 August 2019

    As an operator of Auth TLD Infrastructure that has a reliance on the root server system Nominet have a high interest in the transparency and ongoing operation of the root server system. Nominet welcome the extra transparency that evolving the root server system in the manner detailed in this proposal. The DNS is a critical resource relied on by millions of people worldwide and as such it's important that it is operated in a clear and transparent manner from top to bottom. We think it is very important that the organisations running root servers maintain their independence while also being accountable for the way they operate from a technical/process/business point of view. This proposal puts the right level of controls in place and so we support its implementation.

    Carlos Reyes  05:14 UTC on 07 August 2019

    Hello, Brett. You may want to consider providing this input via Public Comment (navigate to the "Public Comment" tab at the top of this page and then find the proceeding on "Evolving the Governance of the Root Server System," which closes on Friday.

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