Skip to main content
Resources

Root Server System Advisory Committee

The Root Server System Advisory Committee (RSSAC) advises the ICANN Board and community on matters relating to the operation, administration, security, and integrity of the Root Server System, as outlined in the ICANN Bylaws.

The RSSAC consists of representatives from the organizations responsible for operating global root service.

Root Server Operator Representative Alternate Term Expires
Cogent Paul Vixie Brad Belanger 31 December 2020
Defense Information Systems Agency Kevin Wright Ryan Stephenson 31 December 2019
ICANN Matt Larson Terry Manderson 31 December 2021
Internet Systems Consortium Fred Baker (Co-Chair) Jeff Osborn 31 December 2021
National Aeronautics and Space Administration (NASA) – Ames Research Center Keith Bluestein Tom Miglin 31 December 2019
Netnod Lars-Johan Liman Patrik Fältström 31 December 2021
Réseaux IP Européens (RIPE) Network Coordination Centre Kaveh Ranjbar Anand Buddhdev 31 December 2020
University of Maryland Karl Reuss Gerry Sneeringer 31 December 2019
University of Southern California – Information Sciences Institute Wes Hardaker Suzanne Woolf 31 December 2020
United States Army Research Laboratory Howard Kash Kenneth Renard 31 December 2019
Verisign, Inc. Brad Verd (Co-Chair) Matt Weinberg 31 December 2021
Widely Integrated Distributed Environment (WIDE) Project Jun Murai Hiro Hotta 31 December 2020

On 18 July 2013, the ICANN Board approved the initial membership and leadership of the RSSAC, with new representatives also appointed on 26 June 2014.

Liaisons

The RSSAC also consists of representatives from the organizations responsible for the management of the Root Zone and other partners in the Internet community.

Liaison from the Internet Assigned Numbers Authority (IANA) Naela Sarras
Liaison Root Zone Maintainer (Verisign, Inc.) Duane Wessels
Liaison from the Internet Architecture Board (IAB) Daniel Migault
Liaison from the ICANN Security and Stability Advisory Committee (SSAC) Russ Mundy

The RSSAC appoints liaisons to other groups to report on matters that need to be coordinated or communicated between them per the RSSAC Operational Procedures.

Liaison to the ICANN Board of Directors Kaveh Ranjbar
Liaison to the Customer Standing Committee (CSC) Lars-Johan Liman
Liaison to the Root Zone Evolution Review Committee (RZERC) Brad Verd
Liaison to ICANN Nominating Committee Amir Qayyum

Other Appointments

Upon request, the RSSAC also appoints representatives to specific review teams and other ICANN community groups or efforts.

Representative to the Second Security, Stability, and Resiliency Review Team (SSR2) Eric Osterweil
Representative to the Third Accountability and Transparency Review Team (ATRT3) Ramet Khalili Nasr
Representative to the ICANN Fellowship Selection Committee Amir Qayyum
Representative to the ICANN Fellowship Mentoring Committee Rao Naveed Bin Rais
Representative to the IANA Naming Function Review Team (IFRT) Suzanne Woolf

Meetings

The RSSAC holds periodic teleconferences and meets at ICANN and IETF meetings. Minutes from meetings and teleconferences (where available) can be viewed here.

Caucus

The RSSAC Caucus is comprised of DNS experts who have an interest in the Root Server System, broadening the base of diverse, technical expertise available for RSSAC work. The primary role of the RSSAC Caucus is to perform research and produce publications on topics relevant to the mission of the RSSAC. More information about the Caucus can be viewed here.

Publications

The RSSAC may publish advisories, correspondence, reports, and statements within its mandate as well as documents related to its own administration and work. More information about RSSAC publications can be viewed here.

Frequently Asked Questions

The RSSAC maintains a list of Frequently Asked Questions that can be found here.

Workplan

The RSSAC maintains an annual workplan that can be found here.

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