Registration of IDN Language Tables

1
Registration ofIDN Language Tables

• John L. Crain ltcrain_at_icann.orggt
• APT-ITU Joint workshop on ENUM and IDN
• Bandar Seri Begawan, Brunei Darussalam
• May 22nd 2004

2
Guidelines

• ICANN issued a set of guidelines for the
  Implementation of Internationalized Domain Names
  in June of 2003
• Developed collaboratively by ICANN and leading
  Internationalized Domain Names (IDN) registries

http//www.icann.org/general/idn-guidelines-20jun0
3.htm
3
Section 3.

• 3. In implementing the IDN standards, top-level
  domain registries will (a) associate each
  registered internationalized domain name with one
  language or set of languages, (b) employ
  language-specific registration and administration
  rules that are documented and publicly available,
  such as the reservation of all domain names with
  equivalent character variants in the languages
  associated with the registered domain name, and,
  (c) where the registry finds that the
  registration and administration rules for a given
  language would benefit from a character variants
  table, allow registrations in that language only
  when an appropriate table is available.

4
Registration of Language Tables

• The IANA Registry for IDN Language Tables has
  been created to support the development of the
  IDN technology
• In addition to making the Language Tables
  publicly available on TLD registry websites, the
  TLD registries (TLD Sponsors, gTLD and ccTLD
  Registry Operators) may register Language
  Tables with the IANA, which in turn will display
  them online for public access

5
The inevitable disclaimer

• The IANA Registry for Language Tables will not
  maintain the content of the Language Tables and
  is hence not responsible for their accuracy.

6
Purpose?

• Gives one centralized location for people to find
  language tables as they are used by registries.
• This data can be useful for others implementing
  IDN

7
What is registered

• A Language Table must contain the following
  elements
• TLD Registry (for example, name of Registry
  Operator or the TLD)
• Language Tag (as defined in BCP 47)
• http//www.rfc-editor.org/rfc/rfc3066.txt
• Revision Control (table version number) supplied
  by the Registry
• Effective Date (DD Month YYYY)
• Registry Contact Details (For example, contact
  name, email address, and/or phone number)
• .

8
Submission Format

• Language Tables are encouraged to be submitted in
  a standards based format. There are no other
  format requirements. For convenience, the IANA
  has provided a template that registries can use
  to prepare their submission.
• http//www.iana.org/assignments/idn/registry-langu
  age-template.txt

9
Current Submissions

• .jp Japanese Language
• .kr Korean Language
• .pl Polish Language
• .pl Arabic Language
• .pl Hebrew Language
• .pl Greek Language

10

• .info German Language
• .museum Danish Language
• .museum Icelandic Language
• .museum Norwegian Language
• .museum Swedish Language
• http//www.iana.org/assignments/idn/registered.htm

11
Conclusion Plug

• Registry is now there.
• Take up is slow but we expect to see more
  registries taking up IDN and publishing
• http//www.iana.org/assignments/idn/
• Next ICANN Meeting will be in Kuala Lumpur,
  Malaysia, 19-23 July 2004
• http//www.icann.org/meetings/kualalumpur/