Skip to main content

Blog

  • Executive Team Announcement

    I want to extend my warmest wishes to Akram Atallah, President, Global Domains Division, who has decided to leave ICANN org for another opportunity after eight years, effective immediately. Akram made many, significant contributions to ICANN in a variety of roles,...
  • Executive Team Update

    I am pleased to announce that Sally Newell Cohen has joined ICANN org in the role of Senior Vice President, Global Communications, responsible for the communications and language services functions, based in Los Angeles. Sally's first day is today. Most recently Sally...
  • Blog: Celebrating ICANN@20 through your recollections

    ICANN will soon be celebrating its birthday in Barcelona, specifically at ICANN63, 20-25 October 2018. This will be an historic meeting for a number of reasons, a primary one being that it will mark the 20th anniversary of ICANN's formation. It's no secret that ICANN's...
  • ICANN GDPR and Data Protection/Privacy Update

    Hero1 data privacy protection update 3121x1560 24sep18 en
    As part of our ongoing work together on the General Data Protection Regulation (GDPR) and seeking clarity for any access mechanism for non-public registration data, I promised to provide regular updates. These updates and any clarity received are input into the...
  • Possible Unified Access Model Published for Community Input

    Hero1 gdpr unified access model 1563x782 20aug18 en
    The ICANN org has been working to further develop its proposal for a possible unified access model, in order to engage in discussions with the community and relevant data protection authorities. Following the June publication of the Framework Elements for a Unified Access...
  • Welcome to ICANN62!

    Hero1 marby 750x425 en
    I'm excited to welcome you to Panama City, Panama, for ICANN62. This is the second time an ICANN meeting has been held in Central America, and the first time we've come to Panama. ICANN meetings represent an important opportunity for our diverse stakeholders to meet...
  • Final Proposed FY19 Operating Plan and Budget

    Today, we published the final proposed FY19 Operating Plan and Budget and submitted it to the ICANN Board for consideration at the meeting on 30 May 2018. This is an important step in the process to ensure transparency so that you – and the rest of the ICANN community –...
  • ICANN org's Open Data Strategy

    The ICANN organization is a community-based organization and one of our defining principles is that we are an "open" organization. Our strategy for the data we hold must reflect this, and our default position must be that all of our data is open data unless there are good...
  • Improving our Planning and Preparation

    Over the last year, we all have worked hard to understand the European Commission’s General Data Protection Regulation (GDPR) legislation. One question that has been asked many times is: why didn’t we start the process earlier? I guess there are many answers to that...
  • Data Protection/Privacy Issues: ICANN61 Wrap-up and Next Steps

    Hero1 icann61 wrap up next steps gdpr 1568x890 21mar18 en
    I want to thank everyone from across the community who participated in discussions around the ICANN61 meeting on the European Union's General Data Protection Regulation (GDPR) and its impact on registration directory services, as well as ICANN's contracts. Your...
  • Budget Discussions at ICANN61

    During ICANN61, a major topic of conversation was the FY19 draft Budget and Operating Plan. As you’ve heard from me, 80-85 percent of our budget is already committed to certain projects that are in our Bylaws, our contracts, our operations, and other fixed costs. This...
  • Update on ICANN61 Adobe Connect Issues

    I wanted to provide you with a brief update on the issue with our Adobe Connect services. The issue is one that could possibly lead to the disclosure of the information shared in an ICANN Adobe Connect room. We are still investigating the root cause of the issue. We have...
  • Issues with Adobe Connect at ICANN61

    I want to share a note I sent to the community earlier today regarding a security issue related to our use of Adobe Connect. Please see below for information regarding this issue. "Yesterday we were notified by a member of the Security and Stability Advisory Committee of...
  • Why I Love the International Office Strategy

    I am proud of many things the ICANN organization has put in place since I've been at ICANN for nearly two years now. One that I am very excited about is our international office strategy. The international office strategy recognizes that stakeholders in different parts of...
  • Welcome to ICANN61!

    Hero1 welcome to icann61 marby 750x425 11mar18 en
    It is my absolute pleasure to welcome you to ICANN61 in San Juan, Puerto Rico. This is the first ICANN Public Meeting held on the island since 2007, and it could not have come at a more important time. Having this meeting in San Juan is a testament to the strength and...
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."