ICANN 50: IDN Root Zone LGR Generation Panels Workshop
2 likes1,614 views
This document outlines a workshop at ICANN50 discussing the work of prospective generation panels for Chinese, Japanese, Korean, and other scripts. The agenda includes updates from each panel on developing label generation rules for their script and coordinating rules across scripts. The goal is to finalize code points, variants, whole label rules, and LGR documents for each script by ICANN51 to submit to ICANN for the IDN root zone.
![2. The Review of MSR-1 (3)
• [Question] How was the list of Han charact
ers in MSR-1 created?
Ⅱ. The result of KLGP Meeting (jut once)](https://image.slidesharecdn.com/compiledlgrworkshop-icannppt-140708181429-phpapp02/85/ICANN-50-IDN-Root-Zone-LGR-Generation-Panels-Workshop-37-320.jpg)
![Ⅳ. Issues
2. Multi-script IDN TLD ?
• Multi-script IDN TLD allowed?
– E.g., “.한國”, “.韓국”, etc (Hangul + Hanja)
• [Ques] Can KLGR limit the Hangul TLD ?
– Allowed chars in Hangul TLD must be the same a
s those in the second level domain (2LD) under “.
kr”/”.한국” ?
– 2LD under “.kr”/”.한국”: composed of complete Ha
ngul syllables (11,172), English letters (a~z), digit
s (0~9), and hyphen (-).
– No other chars allowed in TLD having Hangul ?](https://image.slidesharecdn.com/compiledlgrworkshop-icannppt-140708181429-phpapp02/85/ICANN-50-IDN-Root-Zone-LGR-Generation-Panels-Workshop-44-320.jpg)
![Current
Work
and
Next
Steps
• XML
Manual
[June
30,
2014]
• Finalize
the
discussions
on
Code
Points
[August
28,
2014]
• Finalize
the
discussions
on
Variants
[September
30,
2014]
• Whole
Label
Rules
–
Aug
–
Oct
14
– Document
principles
for
whole
label
variants
– Define
whole
label
variants
– Release
for
Public
Comments
• Finaliza-on
–
Nov
–Dec
14
– Finalize
LGR
for
Arabic
script
– Submit
to
ICANN/IP
– Release
for
Public
Comments
9
Task
Force
on
Arabic
Script
IDNs](https://image.slidesharecdn.com/compiledlgrworkshop-icannppt-140708181429-phpapp02/85/ICANN-50-IDN-Root-Zone-LGR-Generation-Panels-Workshop-92-320.jpg)
ICANN 50: IDN Root Zone LGR Generation Panels Workshop
- 1. Text #ICANN50 IDN Root Zone LGR Generation Panels Workshop 25 June 2014
- 3. TextText #ICANN50 Agenda • Welcome – 5 min • Community updates: o Chinese Prospective Generation Panel - 15 min o Japanese Prospective Generation Panel - 15 min o Korean Prospective Generation Panel - 15 min o CJK Coordination Report – 15 min o Neo-Brahmi Prospective Generation Panel - 15 min o Arabic Generation Panel – 15 min • LGR project mailing lists – 5 min • Discussions and Q&A- 20 min
- 5. Updates on Chinese Generation Panel Wang Wei ICANN 50th, London 25th June 2014
- 6. Evolution of Chinese Character Totally 100,000 Chinese Characters 200 AD1600 ~ 1100 BC 221BC
- 7. Countries with Significant User Communities for Chinese Script Chinese script is the logogram used in the writing of Chinese and some other Asian languages • hanzi in Chinese • Traditional Chinese • Taiwan • Macau • Hong Kong • Simplified Chinese • Mainland China • Singapore • TC & SC • Malaysia • kanji in Japanese • hanja in Korean
- 8. Target Script and Scope (1/3) Target Script: Hani ISO 15924 code: Hani ISO 15924 no.: 500 English Name: Han (Hanzi, Kanji, Hanja) 4 Hani (Hans &Hant) Jpan Kore Kanji Hanja Hiragana + Katakana+ +Hangul
- 9. Target Script and Scope (2/3) 5 CJK and Han Unification: CJK Unified Ideographs: 4E00–9FFF CJK Unified Ideographs Extension A: 3400–4DBF CJK Unified Ideographs Extension B: 20000-2A6DF CJK Unified Ideographs Extension C: 2A700-2B73F CJK Unified Ideographs Extension D: 2B740–2B81F Ø MSR-1 includes CJK, CJK-A and a minor part of CJK-B. Ø The complete character set for the Chinese script in the IANA IDN tables from .CN, .TW, and.JP all fall in the ranges of CJK and CJK-A.
- 10. Target Script and Scope (3/3) Best Practice: CDNC Character Set and Guide Rules • In 2004, according to RFC 3743 and RFC 4713, CDNC submitted to IANA a unified Chinese Character Set (19320 characters). • CDNC put forwards its guild rule for SLD registration, applied on CN, TW and etc. • The IDL and its Variant Labels SHOULD belong to the same registrant. • The Simplified Chinese form and Traditional Chinese form of the applied-for IDL SHOULD be resolvable simultaneously or non-resolvable at all. • In 2013, among 76 Chinese new gTLD applications, 32 applications are announced to abide by CDNC Character Set and Guide Rules. Owing to the above factors, CGP would like to propose that CDNC Character Set be treated as the initial character set of CGP. 6
- 11. Initial Composition of the Panel ß The CGP gathers 13 experts from a variety of backgrounds (bringing varied linguistic and technical perspectives) from 7 different countries/ regions, including: Þ national and regional policy makers. Þ members from technical community directly working with the DNS (e.g. registries and registrars), security, academia (technical and linguistic). Þ members of community based organizations. Þ members with experience of local language studying. 7
- 12. Name Designation Organization Country/Region Language Expertise Chris DILLON Mr University College London UK Chinese/Japanese/ Korean Chao QI Mr CNNIC China Chinese Di MA Dr ZDNS China Chinese Guoying LI Dr B e i j i n g N o r m a l University China Chinese Jiagui XIE Mr. CONAC China Chinese Joe ZHANG Dr. Beijing UniHan Digital Technology Co., Ltd. China Chinese Japanese Korean Jonathan SHEA Mr HKIRC Hong Kong Chinese Joseph YEE Mr Afilias Canada Chinese, (Familiar with Japanese) Kenny HUANG Dr TWNIC Taiwan Chinese Linlin ZHOU Ms CNNIC China Chinese Nai-Wen HSU Dr. TWNIC Taiwan Chinese Ryan TAN Mr. SGNIC Singapore Chinese Wei WANG Dr. CNIC China Chinese Xiaodong LEE Dr. CNNIC China Chinese Zheng WANG Dr. CONAC China Chinese Zhiwei YAN Dr. CNNIC China Chinese (Familiar with Japanese)
- 13. Relationship with Past Work ß From JET to CDNC to VIP to CGP Þ JET : April, 2004, produced RFC 3743 Ý It includes various concepts for variant handling, such as bundling, atomic IDL Package, and reserved variants. Ý It also defines a standard table as well as an algorithm to generate the preferred variant and reserved variants. Þ CDNC: TC-SC Equivalence Þ VIP: Chinese Case Study Report Þ CGP: variants and label rules for Root Zone 9
- 14. Work Plan ß Four stages (< ICANN51 L.A. in October 2014): Þ 1. Finalization of Code Points Þ 2. Finalization of Variants Þ 3. Finalization of Whole Label Rules Þ 4. Finalization of LGR Documents for Chinese Script and Submission to ICANN Þ 14th Mar, 1st joint meeting of CGP and CDNC Þ 2nd Apr, proposal submitted to ICANN (comments feedbacked on 3rd May) Þ 13th May, principle of character set submitted to ICANN Þ 29th May, 2nd joint meeting of CGP and CDNC 10
- 15. Challenges ß Character Reduction and Extension ß Coordination between C J K Þ Character, variant, rule
- 16. Reduction & Extension ß preliminary question: Þ Will The requirement of generation rules for root zone be different from rules applied in 2nd layers (e.g., RFC3743 for CJK registration)? Þ Will future character extension be allowed after LGR finished the current work?
- 17. Some Suggestions ß The obsolete Korean Lidu be removed from the CGP repertoire. ß Remove the Han Radicals /Strokes that are not regarded as independent Hanzi. ß Remove some Kanji only used in J script context. ß Include more local Hongkong character into CGP repertoire.
- 18. Coordination
- 19. Coordination
- 20. Coordination ß Different language panels (C, J and K) have different views about the Chinese characters and variants: Þ Chinese: Equivalent mapping between SC and TC and generic variants. (reflected in the CDNC character table) Þ Japanese: It is appropriate to distinguish new and old forms (of Kanji) as different and independent characters instead of handling them as variants. Þ Korean: Its IDN policy does not allow Hanja as reflected by the language table it submitted to IANA (Hanja are no longer widely used in ROK) 16 * Then a coordination scheme between different panels is needed (especially between CGP and JGP).
- 21. Root Zone IDNA Label LGR Development and Maintenance Appendix F
- 22. Coordination ß In the last CDNC meeting in Shanghai, a coordination scheme was proposed by the ICANN expert : Þ Each CJK panel creates an LGR and each LGR includes a repertoire and variants. Þ If an LGR includes Han characters, the variant mappings must agree for all three panels. Þ The variant types may be different (blocked or allocatable), the variant types do not have to agree across LGRs ß C and J (and K) need to work closely on the above principle. 18
- 24. About CDNC Ø Evaluates all Chinese domain name compliance with international criterion. Ø Establish the standards for Chinese domain name and corresponding regulation on Chinese domain name registration. Ø Coordinates the operations and management of Chinese domains in various countries or regions, Ø Collaborates with all corresponding international organizations on Chinese domain names
- 25. More 10 years Experience On Variant Issues 2000 2004 2005 2006 2010 2011 2012 2013 CNNIC began its testing process for CDN registration IANA publishes the Chinese Character Table Delegation of Synchronized IDN ccTLDs 中国/中 國, .台湾/台灣 CDNC reaches agreement on synthesis character table format for the root Approval of RFC 3743 Approval of RFC 4713 Publish IDN Variant issue - Chinese Case Study Report New gTLDs launches .CN/.TW CDN Second Level Domain open for registration 2002
- 27. Copyright © 2014 Japan Registry Services Co., Ltd. 1 JGP Schedule (draft) ５月 ６月 ７月 ８月 ９月 １０月 １１月 １２月 Milestone Japanese Generation Panel Japanese Community CJK Joint Panel ICANN Contact to candidates ▲ICANN50 ▲ICANN51 ▲formation Confirm Japanese Rule, Consensus, Prepare for Public comments Confirm each CJK Rules, Discussion, Consensus Public comments Explain draft Japanese▲ Rule, call for comments Propose Japanese Rule▲ ▲Approval of JGP Generation of CJK Unified Rule Explain at ICANN ▲ Discussion among CJK Mtg▲ Pre-Mtg▲ Mtg▲ Mtg▲ Mtg▲ Mtg▲ Monthly meeting
- 29. The Status of KLGP (Korean Label Generation P anel) Jun. 25, 2014. ICANN #50, London, UK gimgs@pnu.kr, PNU choimh@kisa.or.kr, KISA
- 30. Contents CJK Meeting In Shanghai Ⅱ Ⅲ The result of KLGP Meeting Ⅰ The status of KLGP IssuesⅣ Future PlanⅤ
- 31. Ⅰ The Status of KLGP
- 32. Ⅰ. The Status of KLGP l Members of Korean Label Gen. Panel Classification Name Chair (Linguistic Expert) Kyongsok Kim Policy Expert Youngeum Lee Policy Expert Dongman Lee Linguistic Expert Kyungran Kang Language Expert Yongju Hwang New Member Community Eunghwi Jeon New Member Community Yangwoo Ko Community YJ Park Registry MinJung Park Registry Myunghee Choi Still recruiting members who have expertise in culture.
- 33. Ⅱ The Result of KLGP Meeting
- 34. Ⅱ. The result of KLGP Meeting (jut once) 1. The Scope of KLGR ? • Hangul Syllables – seems to be No Variant issues – Range : AC00-D7A3 (11,172 syllables) • Hanja (Hanzi, CJK Ideographs) ? – probably need to have a pub. hearing
- 35. 2. The Review of MSR-1 (1) • Hangul: Hangul syllables(11,172) Ⅱ. The result of KLGP Meeting (jut once)
- 36. 2. The Review of MSR-1 (2) • Han Script (CJK Unified Ideographs, CJKU main, CJKU ExtA, and CJKU ExtB; IICORE) Ⅱ. The result of KLGP Meeting (jut once)
- 37. 2. The Review of MSR-1 (3) • [Question] How was the list of Han charact ers in MSR-1 created? Ⅱ. The result of KLGP Meeting (jut once)
- 38. Ⅲ CJK Meeting in Shanghai
- 39. III. CJK Meeting In Shanghai 1. The Overview of CJK LGP Meeting • Meeting : CGP (Chinese Generation Panel) • Date : 2014. 5. 29. • Place: Shanghai Branch of Chinese Academy of Science Building No.1, 2nd Floor Meeting Room • Participants : about 20 people (Prof. Kyongsok K im from Rep. of Korea attended the meeting) - Japan and USA by teleconferencing
- 40. III. CJK Meeting In Shanghai 2. The detail of CJK Meeting • MSR-1 Review • The Status of Hanja Domain in Korea – In Korea, we don’t use Chinese (Han scr ipt) under ‘.한국(.xn--3e0b707e, Korean Top-level IDN)’: – e.g., “漢字.한국” not allowed currently. • KLGP will continuously participate in the C JK LGP meeting.
- 41. III. CJK Meeting In Shanghai 3. Idu (89/91 chars) • Some Idu chars are included in IICORE. • For most Idu chars, K (South Korea), KP (Nor th Korea), and G (China) columns are filled in . For some chars, T (19) and H (14), J (5), an d V (2) columns are also filled in. • Need to keep IICORE chars • Suggest NOT to exclude Idu from MSR-1 • Note. The term “Idu” does not show up in ISO /IEC 10646, 3ed:2012 anymore.
- 42. Ⅳ Issues
- 43. Ⅳ. Issues 1. KLGR Scope ? • Need more time to consider the KLGR sco pe. – KLGR: Hangul only? & participate in CJK LGP – KLGR: (Hangul + Hanja)? & participate in CJK LGP
- 44. Ⅳ. Issues 2. Multi-script IDN TLD ? • Multi-script IDN TLD allowed? – E.g., “.한國”, “.韓국”, etc (Hangul + Hanja) • [Ques] Can KLGR limit the Hangul TLD ? – Allowed chars in Hangul TLD must be the same a s those in the second level domain (2LD) under “. kr”/”.한국” ? – 2LD under “.kr”/”.한국”: composed of complete Ha ngul syllables (11,172), English letters (a~z), digit s (0~9), and hyphen (-). – No other chars allowed in TLD having Hangul ?
- 45. Ⅳ. Issues 3. Members of KLGP – How to make North Koreans involved in KLGP? – Making North Korean refugees in South Korea involved in KLGP?
- 46. Ⅳ Future Plan
- 47. Ⅴ. Future Plan • To hold KLGP meetings • To hold a public hearing • To draft KLGR
- 48. Thanks.
- 50. CJK Rules For The Root Zone Kenny Huang, Ph.D. 黃勝雄博士 Member, CDNC / CGP Co-author, RFC3743 IETF Member, Executive Council, APNIC Member, Board of Directors, TWNIC huangksh@gmail.com 2014.Jun
- 51. Problem : CJK Is Complicated 2 PuttingCJKlabels in the root zone is evenmore complicated
- 52. Institutionalized Problem Solving : Structure 3
- 53. Constraints for CJK LGR 4 Independent Tasks Each CJK Panel creates an LGR Each LGR includes a repertoire and variants Define labels permission Define variants labels Assign dispositions •Allocatable •Block Coordination Tasks If an LGR includes Han characters: The variant *mappings* must agree for all the panels The variant *types* may be different The repertoires may be different *Presented by Lee Han Chuan & IP, Shanghai 2014 May 29
- 54. Overlap Case Illustration 5 壹 U58F9 弌 U5F0C 壱 U58F1 一 U4E00 allocate block block Variant Unicode Disposition 一 U4E00 Variant Unicode Disposition Chinese LGR Japanese LGR 1 2 3 Integrate ? Integrated Root Zone Label Generation Rules Rejected Generation Panel F T
- 55. High Level Conflict Strategies 6 ID Strategy Pros Cons Rank 1 Adopt X Abandon Rcjk Permit X No label rule 2 Adopt X Intersection ∩ (Rcjk) Permit X Permit ∩(variants/disp) Rules changed 3 Adopt X Union ∪(Rcjk) Permit X Permit ∪(variants/disp) Rules changed 4 Abandon X and Rcjk No conflict Label not available 5 Adopt rules based on frequency of use Fair & scientific approach Rules changed; fairness doesn’t mean appropriate CJK overlap C: rule Rc J : rule Rj K: rule Rk
- 56. Unified CJK LGR Illustration 7 壹 U58F9 弌 U5F0C 壱 U58F1 一 U4E00 allocate block block Variant Unicode Disposition Chinese LGR 1 2 3 一 U4E00 Variant Unicode Disposition Japanese LGR 壹 U58F9 弌 U5F0C 壱 U58F1 一 U4E00 allocate block block Variant Unicode Disposition Integrated LGR 1 2 3 一 U4E00 Variant Unicode Disposition Integrated LGR Union Intersection
- 57. CJK Integration Methodology Divide & Conquer (D&C) Unified CJK Rules Variant Dispositions Minimal Viable Solution CJK Rules Root Zone Admin Strategic Direction Plan and Define CJK Overlap Resources JK Overlap CJ Usage Pattern CJ Overlap CK Usage Pattern CK Overlap Services LGR Constrains Evaluation Method Diversified CJK DemandsRequires C Demands J Demands 8 Requires Split Merge
- 58. Splitting Non-overlapping Code Points From Repertories 9 C/J Overlap: 6181 C-Han : 19520 (CNNIC/TWNIC) J-Han : 6356 (JPRS) K-Han : 0 (KRNIC) Develop Conflict Strategy No conflict Rc Rk Rj 13339 175 1 unified code points 13339 175 13514 + CJK Han-overlap in IANA IDN Repository Problem Domain (Unsolved Overlap) : 6181 Rc Rj Rk Chinese LGR Japanese LGR Korean LGR
- 59. Engineering Design 10 2 TC : Apple News SC : Sina News JP : Mainichi News Computation for Word Usage and Frequency C/J overlap code points Matching usage frequency of use Split unused code points Split code points of low frequency of use Sample size is statistical significant
- 60. Splitting Unused Code Points from The Overlap 11 J only : 203 C only : 1927Rc Rj total unused : 2739 3 C / J Overlap Data Set : 6181 unified code points 2739 203 1927 4869 + C / J usage overlap : 1312 total used : 3442 Problem Domain (Unsolved Overlap) : 1312
- 61. Computing Frequency of Use of Code Points 12 4 Initial Data Set : 1312
- 62. Top 10 Most Popular Words 13 的, 2774 人, 1005 在, 975 一, 964 是, 960 不, 951 中, 896 有, 883 大, 776 台, 718 TC 日, 20942 月, 20315 人, 4430 国, 3754 中, 3521 被, 2791 称, 2340 地, 2226 南, 2152 生, 2027 SC 日, 822 年, 496 国, 393 会, 345 月, 325 人, 325 大, 319 市, 253 本, 251 中, 250 JP
- 63. 14 4.063 4.1884 1.7338 0.6 0.6094 0.886 0.55820.59440.5518 0.468 0.7042 0.4304 0.6026 0.4488 0.36 0.35620.4026 0.385 0.7508 0.325 0 0.5 1 1.5 2 2.5 3 3.5 4 4.5 C-Freq J-Freq Top 20 : Chinese Frequency of Use > Japanese Frequency of Use Generated Data Set : 939 FrequencyofUse%
- 64. 15 0.1988 0.2788 0.5512 0.1956 0.3834 0.1644 0.2366 0.1056 0.1212 0.1088 0.1688 0.1422 0.1344 0.1622 0.0856 0.2812 0.1588 0.0912 0.1134 0.1288 0 0.1 0.2 0.3 0.4 0.5 0.6 C-Freq J-Freq Top 20 : Chinese Frequency of Use < Japanese Frequency of Use Generated Data Set : 363 FrequencyofUse%
- 65. 16 0.0222 0.0144 0.0112 0.0056 0.0056 0.0022 0.0012 0.0012 0.0012 0.0012 0 0.005 0.01 0.015 0.02 0.025 8FCE 7D20 675F 541B 846C 79E9 82BD 96C0 5857 5353 C-Freq J-Freq FrequencyofUse% Chinese Frequency of Use = Japanese Frequency of Use Generated Data Set : 10
- 66. Frequency of Use Reassembly 17 unified code points 363 939 1302 + Problem Domain (Unsolved Overlap) : 10 C / J Usage Overlap Data Set : 1312 Freq C > J : 939 Freq J > C : 363 J = C 10 Rc Rj
- 67. Data Processing & Computation Recap 18 >20K Han Code Points 6181 CJK Overlap 1312 Usage Overlap Splitting Non-overlapping Frequency of Use Computation Filtering Process Filtering Process LOGICDesign Splitting Unused Methodology Review CJK Coordination Re-Sampling & Computation Statistical Justification 10 Code Points Problem domain was effectively reduced
- 68. Future Work 19 1578152323 3433 69 122 289 501 80 26 1455321 0 100 200 300 400 500 600 % numberofXwithinthesamerange Chinese Frequency of Use Minus Japanese Frequency of Use Overlap range redefine Expand (?) Std Dev. Require intensive CKJ coordination & deliberation RcRj Mean= 0.034465 S.D.=0.158477
- 69. Re-consider Language Tag 20 K tag J tag TLD registries IANA/Verisign provisioning root server operators publication Internet query Policy C tag Language tag support •RFC 2860 : The name space of language tags is administered by IANA •ISO Standard 639 : •when a language has both an IANA-registered tag and a tag derived from an ISO registered code, one MUST use the ISO tag. •Maintenance Agency : International Information Centre for Terminology (Austria) Sources of Language Tag distribution masters root servers DNS resolvers
- 70. 21 PerfectionSyndrome “Engineering isn't about perfect solutions; it's about doing the best you can with limited resources.” Randy Pausch
- 73. What is Brahmi? • An ancient script • Most of the modern scripts in Indian subcontinent have been derived from Brahmi • Geographically the scripts being used in Central• Geographically the scripts being used in Central Asia, South Asia and South-East Asia • These scripts are used by multiple language families: Largely by Indo-Aryan and Dravidian
- 74. Why Brahmi? • All the scripts derived from Brahmi are Abugida, also known as alphasyllabary. • The lineage, example of “Letter Ka”
- 75. Why Brahmi? • Despite their variations in the visual forms, the basic philosophy in their usage is common • They all are “akshar” driven, and follow a specific syntax – Analogical reference can be made to Indian National– Analogical reference can be made to Indian National standard, IS 13194:1991 – Section 8 • This syntax being the implicit foundation in representation of these scripts in the digital medium, adherence to the structure acts as a obligatory security consideration even in the case of Internationalized Domain Names. • Here we are dealing with “root”
- 76. Why Neo-Brahmi? • Of all the scripts derived from “Brahmi”, not all are in modern usage • Approach is in consonance with the conservatism principle of the LGR procedureprinciple of the LGR procedure
- 77. Past Experience • Experience of working for IDN ccTLDs for 22 Official Indian Languages • Each language is having its own • Code point set• Code point set • Variant • Complex Whole label Evaluation Rules
- 78. Current Members List • Currently the group is of 10 members • Mixed bag expertise like linguistic, Unicode • Need more members to cover the diversity within the group 7 Udaya Narayana Singh Raiomond Doctor Mahesh D. Kulkarni Anupam Agrawal Akshat S. Joshi Abhijit Dutta N. Deiva Sundaram Neha Gupta Nishit Jain Prabhakar Pandey
- 80. Get Involved • The group is currently working on gaining more participation within and outside India. • For participation, please refer “Call for participation - Neo Brahmi Generation Panel” 9 • Published at ICANN communtiy page https://community.icann.org/display/croscomlgrprocedure/Root+Zone+LGR+Project • Interested individuals can send their expression of interest to neobrahmiGP@icann.org and idntlds@icann.org
- 81. Progress so far… • Reviewed and commented on Maximal Starting Repertoire for the Root • A workshop is planned in AprIGF on “Bringing diverse linguistic communities together for a unified IDN ruleset” for reaching out to the community for the wider participation in the panel 10 out to the community for the wider participation in the panel • Working on the Neo-Brahmi Generation panel proposal – May submit to ICANN by end of August/early September
- 84. Task Force on Arabic Script IDNs: Overview and Progress @ ICANN London Mee-ng (June ‘14) Task Force on Arabic Script IDNs (TF-‐AIDN) Middle East Strategy Working Group (MESWG) I-‐aidn@meswg.org
- 85. Community Driven Way forward: Task Force on Arabic Script IDNs • Crea-on and oversight by community based Middle East Strategy Working Group (MESWG; hRps://community.icann.org/display/MES/MESWG+Members ) • TF-‐AIDN Objec-ves: a holis-c approach – Arabic Script Label Genera-on Ruleset (LGR) for the Root Zone – Second level LGRs for the Arabic script – Arabic script Interna-onalized Registra-on Data – Universal acceptability of Arabic script IDNs – Technical challenges around registra-on of Arabic script IDNs – Opera-onal so[ware for registry and registrar opera-ons – DNS security maRers specifically related to Arabic script IDNs – Technical training material around Arabic script IDNs 2 Task Force on Arabic Script IDNs
- 86. Membership • Currently 26 members – applica-ons s-ll being received • From 15 countries – Australia, Egypt, England, Ethiopia, Germany, Iran, Jordan, Lebanon, Malaysia, Morocco, Pakistan, Pales-ne, Saudi Arabia, Sudan, and UAE • Speaking than nine languages – Arabic, Malay, Saraiki, Sindhi, Pashto, Persian, Punjabi, Torwali, Urdu, with experFse in use of Arabic script from East Asia, South Asia, Middle East, North Africa and Africa • Coming from diverse disciplines – academia (linguis-cs and technical), registries, registrars, na-onal and regional policy bodies, community based organiza-ons, technical community 3 Task Force on Arabic Script IDNs
- 87. Task Force on Arabic Script IDNs • Membership open, community based • Details and interests of members posted by MESWG • Discussions publicly archived • Details at hRp://lists.meswg.org/mailman/lis-nfo/I-‐aidn • Background and Introduc-on to TF-‐AIDN – hRps://community.icann.org/display/MES/Task+Force+on+Arabic+Script +IDNs • Workspace, news and document archive – hRps://community.icann.org/display/MES/TF-‐AIDN+Work+Space • Email Archive – hRp://lists.meswg.org/pipermail/I-‐aidn/ 4 Task Force on Arabic Script IDNs
- 88. Arabic Script TLDs Assigned or Delegated اﳉﺰاﺋﺮ .1 ﻋﻤﺎن .2 ا+ﺮان .3 اﻣﺎرات .4 ﺑﺎزار .5 ﭘﺎﮐﺴﺘﺎن .6 اﻻردن .7 بھارت .8 اﳌﻐﺮب .9 01. اﻟﺴﻌﻮدﻳﺔ Task Force on Arabic Script IDNs 5 11. ﺳﻮدان 21. ﻣﻠﻴﺴﻴﺎ 31. ﺷﺒﻜﺔ ﺳﻮرﻳﺔ .14 51. ﺗﻮﻧﺲ 61. ﻣﺼﺮ 71. ﻗﻄﺮ ﲔ81. ﻓﻠﺴﻄ ﻊﻣﻮﻗ .19
- 89. SUMMARY OF THE CODE POINTS Color Descrip-on No. Of codes DISALLOWED by MSR 48 ALLOWED by MSR 227 Not Allowed by IDN2008 64 Total 339 SubmiHed to MSR 172 Discussion on codes to be handed over to LGR Work is under process
- 90. IDN Variants Needs and Challenges Security and Stability Needs ﭘﺎکﭘﺎ ﺳﺘﺎنك ﺳﺘﺎن U+0643 U+06A9 xn-‐-‐mgbai9a5eva00b xn-‐-‐mgbai9azgqp6j • 120+ cases of visually same or similar Arabic script characters iden-fied by case study team – Variants must not be allocated independently – Variants may need ac-va-on to allow user access (w/ different KB) • 16 IDN ccTLD applica-ons with 4 applica-ons with variants Security and Stability Challenges • Consistency and innumerability – Consistent across and within TLDs – Minimal ac-va-on for manageability • Management tools – Registra-on – Configura-on and Maintenance – Security and Monitoring • Usability in applica-ons – Browsing, emailing, etc. – Searching, privacy, etc. 7 Task Force on Arabic Script IDNs
- 91. Progress Work Accomplished – Arabic Script Genera-on Panel – Principles for Inclusion, Exclusion, and Deferral of Arabic Script Variants – MSR Analysis and Feedback – Principles on Variants – Code Points for LGR Outreach to the Community – Launch at the Arab IGF Mee-ng in Algiers – Presenta-on during the IGF in Bali – Outreach during the ME DNS Forum – Presenta-on to the community at ICANN Singapore – Presenta-on to the community at the APTLD Mee-ng Task Force on Arabic Script IDNs 8
- 92. Current Work and Next Steps • XML Manual [June 30, 2014] • Finalize the discussions on Code Points [August 28, 2014] • Finalize the discussions on Variants [September 30, 2014] • Whole Label Rules – Aug – Oct 14 – Document principles for whole label variants – Define whole label variants – Release for Public Comments • Finaliza-on – Nov –Dec 14 – Finalize LGR for Arabic script – Submit to ICANN/IP – Release for Public Comments 9 Task Force on Arabic Script IDNs
- 93. ﻪ ﮐﺎﺳﻴﺎﺗﺮﳝ ًاﺷﻜﺮ ہﺷﮑﺮی س ﺳﭙﺎﺎﺑ ﺮﺗﺸﻜ Thank You 10 Task Force on Arabic Script IDNs
- 94. TextText #ICANN50 LGR project mailing lists o LGR@icann.org: Communicate with LGR community members and the Integration Panel on matters related to LGR work o IntegrationPanel@icann.org: Contact directly the Integration Panel members on all matters related to LGR work o ArabicGP@icann.org, ChineseGP@icann.org, CyrillicGP@icann.org, KoreanGP@icann.org, NeoBrahmiGP@icann.org : script community dedicated mailing lists o idntlds@icann.org: Contact ICANN to submit Generation Panel proposals, individual statement of interests, work reports, updates, etc. o Discuss issues related to the IDN Variant TLDs Program by subscribing to vip@icann.org here: https://mm.icann.org/mailman/listinfo/vip
- 95. TextText #ICANN50 ICANN IDN Team: Thank You USEFUL LINKS: • The LGR Procedure: http://www.icann.org/en/resources/idn/variant-tlds/lgr-procedure-20mar13-en.pdf • MSR-1 Public Comment: https://www.icann.org/public-comments/msr-2014-03-03-en • MSR-1 released: https://www.icann.org/news/announcement-2-2014-06-20-en • V07 Internet Draft for LGR Rules Toolset Project Published: http://tools.ietf.org/html/draft-davies-idntables-07 • Call for Generation Panels to Develop Root Zone Label Generation Rules: http://www.icann.org/en/news/announcements/announcement-11jul13-en.htm • Setting up and running a Generation Panel: https://community.icann.org/display/croscomlgrprocedure/Generation+Panels • Community Wiki LGR Project website: https://community.icann.org/display/croscomlgrprocedure/Root+Zone+LGR+Project • For more info on the IDN Variant related pages, please visit: https://www.icann.org/resources/pages/variant-tlds-2012-05-08-en • To submit expressions of interest, or if you have additional questions, please contact ICANN at: idntlds@icann.org