Following up on a Contractual Compliance & Consumer Safeguards Conversation
On 25 September, ICANN hosted a webinar discussion on Contractual Compliance and Consumer Safeguards. Nearly 100 community members attended the webinar. A recording of the webinar can be found here.
The webinar raised topics concerning the Consumer Safeguards position, ICANN's existing safeguards and contractual compliance tools, DNS abuse, and voluntary efforts to address abuse in the Internet's unique identifier system. A short slide deck, and a previously published summary of ICANN's existing safeguards, helped guide the conversation. The slide deck, in particular, raised several questions, such as:
- What should ICANN's role be in addressing DNS abuse?
- Are there gaps between DNS abuse and ICANN's authority to address that abuse?
- What additional tools or data would be helpful in assessing DNS abuse?
- Are there areas where voluntary measures could be helpful?
- How should ICANN collaborate with other stakeholders addressing abuse?
- Is there a threat of governmental intervention if the ICANN community cannot satisfactorily address DNS abuse?
We look forward to supporting future discussions concerning ICANN's consumer safeguards and working to enhance consumer trust within the DNS. In the meantime, we welcome any thoughts or questions concerning ICANN safeguards, which may be directed to Bryan Schilling, Consumer Safeguards Director at email@example.com
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."