Skip to main content
Resources

RSSAC Caucus Work Parties

This page provides an overview of work parties in the RSSAC Caucus, including a description of the effort and its current status.

Composition | Work parties consist of a work party leader; members who may contribute to, review, or observe the work; and an RSSAC shepherd. Staff support resources from the ICANN organization are available to assist the work party.

Current Status | There are five stages to a work party.

Initiation

The RSSAC has approved the statement of work and appointed a shepherd. There is an open call for volunteers from the RSSAC Caucus.

Active

The Work Party is conducting its work and preparing its work product.

Inactive

The RSSAC has suspended the work party to evaluate its status.

Review

The work party has concluded its work, and the work product is under review by the RSSAC Caucus and/or the RSSAC.

Closed

The RSSAC has published the work product.

RSS Security Incident Reporting

  • Description: Statement of Work
  • Current Status: Active
  • Work Party Leader: Robert Story
  • RSSAC Shepherd: Ken Renard
  • Staff Support: Andrew McConachie

RSSAC002v5

RSSAC001v2

RSSAC047v2

Tool to Gather a Local Perspective of the Root Server System

Effects and Mitigations of a Rogue Root Server Operator

Expectations of the Root Server System and Related Metrics

Studying Modern Resolver Behaviours

Service Coverage of the Root Server System

  • Description: Statement of Work
  • Current Status: Inactive
  • Work Party Leader: Lars-Johan Liman
  • RSSAC Shepherd: Lars-Johan Liman
  • Staff Support: Steve Sheng

Packet Sizes

  • Description: Statement of Work
  • Current Status: Closed
  • Work Party Leader: George Michaelson
  • RSSAC Shepherd: Duane Wessels
  • Staff Support: Andrew McConachie

Best Practices for the Distribution of Anycast Instances of the Root Name Service

  • Description: Statement of Work
  • Current Status: Closed
  • Work Party Leader: Kaveh Ranjbar
  • RSSAC Shepherd: Kaveh Ranjbar
  • Staff Support: Andrew McConachie

Harmonization of Anonymization Procedures for Data Collecting

  • Description: Statement of Work
  • Current Status: Closed
  • Output: RSSAC040
  • Work Party Leader: Paul Hoffman
  • RSSAC Shepherd: Lars-Johan Liman
  • Staff Support: Andrew McConachie

Technical Analysis of the Naming Scheme Used for Individual Root Servers

  • Description: Statement of Work
  • Current Status: Closed
  • Output: RSSAC028
  • Work Party Leader: Paul Hoffman
  • RSSAC Shepherd: Suzanne Woolf
  • Staff Support: Steve Sheng

For questions and concerns regarding any of the RSSAC Caucus Work Parties, please contact ask-rssac@icann.org.

A note about our terms of service:

We have updated our electronic terms of service to provide greater transparency and align with 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."