Skip to main content

How to catch up on every major policy issue before Nairobi

Whether you intend to participate in the upcoming Nairobi meeting in person or remotely, you’re not alone if you feel under-prepared. The ICANN community has a huge number of important issues working their way through the policy development process (PDP), and it’s tough to track them all. It almost makes you wish you could sit some policy experts down and say, “I haven’t got all day, so give me the executive briefing, short and sweet!”

If you relate to that feeling, you’ll be glad to learn that before each international meeting, staff members on ICANN’s Policy Team assemble a high-level presentation recapping the state of every major issue in policy development. The briefing involves all Supporting Organizations at ICANN, so whether your primary concern is generic domain names, country code domain names, or the oft-overlooked-but-oh-so-necessary numbers and addresses, you can rapidly learn the status of key issues.

The pre-Nairobi Policy Update Webinar happened last week, but if you missed it, don’t worry: we recoreded the entire 90-minute session. You can see and hear the presentation just as if you had participated in it live. And if the presentation raises questions in your mind, the Policy Team always answers inquiries that you email to policy-staff@icann.org.

You might think 90 minutes is not a “short and sweet” briefing. But wait until you see how many issues we recap: everything from GNSO Improvements, to the usual list of alphabet-issues (spelled out in the briefing): IRTP, RAP, PEDNR, RAA, STI, ASNs, Whois, the recently initiated PDP on Vertical Integration, and more.

If you’d love a one-stop resource for quickly getting the lay of the land before meeting your ICANN colleagues in Nairobi, this is a must-see presentation. Simply point your browser here and sit back for your whirlwind tour: http://icann.na3.acrobat.com/p18646275/ .

Comments

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