January 2012 - IDN-WG - lists.icann.org

FW: At-Large IDN Variant Issues Project Draft Integrated Issues Report
by Matt Ashtiani Jan. 24, 2012

Jan. 24, 2012

Apologies, I have now added the IDN WG mailing list. Regards, Matt Ashtiani At-Large Coordination Officer ICANN 4676 Admiralty Way, Suite 330 Marina del Rey, CA 90292 From: Matt Ashtiani <matt.ashtiani(a)icann.org<mailto:matt.ashtiani@icann.org>> Date: Thu, 5 Jan 2012 15:37:00 -0800 To: Edmon <edmon(a)isoc.hk<mailto:edmon@isoc.hk>> Cc: "pavan(a)registry.asia<mailto:pavan@registry.asia>" <pavan(a)registry.asia<mailto:pavan@registry.asia>>, Olivier Crepin-Leblond <ocl(a)gih.com<mailto:ocl@gih.com>>, Rinalia Abdul Rahim <rinalia.abdulrahim(a)gmail.com<mailto:rinalia.abdulrahim@gmail.com>>, Carlton Samuels <carlton.samuels(a)gmail.com<mailto:carlton.samuels@gmail.com>>, "Tijani Ben Jemaa (Confluence)" <no-reply(a)icann.org<mailto:no-reply@icann.org>>, "evan(a)telly.org<mailto:evan@telly.org>" <evan(a)telly.org<mailto:evan@telly.org>>, ICANN At-Large Staff <staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>> Subject: At-Large IDN Variant Issues Project Draft Integrated Issues Report Dear Edmon, In your capacity as, the Executive Committee (CCed on here) has asked that you draft an initial At-Large IDN Variant Issues Project Draft Integrated Issues Report Statement<https://community.icann.org/x/PIvbAQ>. Please confirm as soon as possible if you are able to draft the Statement. Regards, Matt Ashtiani At-Large Coordination Officer ICANN 4676 Admiralty Way, Suite 330 Marina del Rey, CA 90292

6 15

Initial Report on Universal Acceptance of IDN TLDs - request to develop ALAC statement
by ICANN At-Large Staff Jan. 23, 2012

Jan. 23, 2012

Dear Edmon, In your capacity as ALAC IDN Liaison, Olivier Crepin-Leblond, ALAC Chair, has asked that you, in collaboration with the At-Large IDN WG, draft an initial ALAC statement on the Initial Report on Universal Acceptance of IDN TLDs <https://community.icann.org/display/alacpolicydev/At-Large+Initial+Report+o n+Universal+Acceptance+of+IDN+TLDs+Workspace+-+2012> . The public comment period for this issue closes on 7 February 2012. In order to have a 5 day comment period and a 5 day vote, a draft statement would need to be prepared by 20 January. Given the tight time-frame, staff have added this issue to the agenda for tomorrow's IDN WG call under Next Steps. Would you like staff to organize a call of the IDN WG next week to develop this statement? Regards, Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Gisella Gruber, and Nathalie Peregrine ICANN At-Large Staff E-mail: staff(a)atlarge.icann.org

3 3

URGENT [Call for comments on JIG Report on Universal Acceptance of IDNs]
by Salanieta T. Tamanikaiwaimaro Jan. 23, 2012

Jan. 23, 2012

Dear Team, Further to request from Edmon to initiate a first Draft on JIG Report on Universal Acceptance, kindly find the first draft and request for your comments and urgent input. This will then be consolidated and sent to the ALAC for their input and comments. You can find the JIG Report on Universal Acceptance of IDNs in the At Large Workspace in our usual wiki. The link in which ordinarily we could access the link was broken and fixed yesterday. Bart later sent me the link to the report yesterday and after reading the Report and also going through the work done by the At Large IDN Working Group in the past, I have put together this draft for you to comment and add your tracked edits and comments. Kind Regards, -- Salanieta Tamanikaiwaimaro aka Sala Tweeter: @SalanietaT Skype:Salanieta.Tamanikaiwaimaro Cell: +679 998 2851

1 2

Wikispace IDN Policy
by Salanieta T. Tamanikaiwaimaro Jan. 22, 2012

Jan. 22, 2012

Dear All, I have been observing that the information on the wiki space is cluttered and it is difficult to try to locate and read seamlessly. I have asked the At Large Staff to send me a map of the At Large website/wiki. I could not wait for this so I started mapping the information on the IDN Policy Wiki. It is worthwhile for us to start thinking about the type of categories or folders and rename certain documents by date and chronologically store the same. For sustainability, I think there needs to be a pattern established where there is consistency of naming documents and storing them. This will make our life as a Working Group easier so we can swiftly read and analyse material. We can also create hyperlinks to the various other working groups etc. I have started with creating a chronology of the material uploaded into our Policy space. This is still incomplete. I thought I would map it and we can come up with suitable categories and then reorganise the information and file them electronically in a logical fashion. *Name of Document* Date Uploaded Person who uploaded Comments *03 December 2009* Sep 20 2010 ICANN Default Agenda Workspace Tour Table of Contents Sep 8 2010 ICANN Default Create New Page Sep 8 2010 ICANN Default Attachment How do I make a new page? Sep 8 2010 ICANN Default *03 December 2009* Sep 20 2010 ICANN Default Agenda Past Announcements Sep 8 2010 ICANN Default Needs its independent chronology 20100802165715.txt Sep 8 2010 ICANN Default Spam??? Meeting Agendas Sep 8 2010 ICANN Default IDN Liaison Report May 2010 Sep 8 2010 ICANN Default ALAC Statement on Draft Topic Paper for Policy on the Introduction of IDN ccTLD Sep 8 2010 ICANN Default PDF Link is broken Liaison Monthly Report Sep 8 2010 ICANN Default Contains monthly Liaison Reports from May 2007 to October 2008 August 2009 Report Sep 8 2010 ICANN Default IDN Liaison's Report Search.png Sep 8 2010 ICANN Default There are 3 attachments Navbar-Home.png Sep 8 2010 ICANN Default There are 3 attachments View-Page-What's-new.png Sep 8 2010 ICANN Default How do I find my way around? Sep 8 2010 ICANN Default VIew-Page-Revisions.png Sep 8 2010 ICANN Default What if I make a mistake? Sep 8 2010 ICANN Default ALAC Statement IDN Variants and IDN 3 Characters Sep 8 2010 ICANN Default Page was renamed to ALAC Statement IDN Issues ok Sep 8 2010 ICANN Default Spam??? IDN Liaison Report December 2009 Report Sep 8 2010 ICANN Default Past WG Meetings Sep 8 2010 ICANN Default IDN Policy WG Call of * 3 December 2009* idn-setup-v1-4.pdf Sep 8 2010 ICANN Default i18n-dns-chronology-klensin-faltstrom.pdf Sep 8 2010 ICANN Default presentation-ccnso-idn-28mar07.pdf Sep 8 2010 ICANN Default IDN%20-%20MUSENIC.ppt Sep 8 2010 ICANN Default Powerpoint Presentation Lisbon-IDN-status.ppt Sep 8 2010 ICANN Default Powerpoint Presentation karp.idn.pdf Sep 8 2010 ICANN Default Issues_in_Multilingual_Domains.ppt Sep 8 2010 ICANN Default Powerpoint Presentation idn-report-15feb07.pdf Sep 8 2010 ICANN Default idn-test-labels-05.pdf Sep 8 2010 ICANN Default IDNs%20Introduction%20and%20Update%20-%20MENOG-1.ppt Sep 8 2010 ICANN Default Mohan_yale_a2k_idn_apr27-2007.ppt Sep 8 2010 ICANN Default IDN_Update.pdf Sep 8 2010 ICANN Default Effect%20of%20Multilingualism%20on%20the%20Internet.pdf Sep 8 2010 ICANN Default IDN-tutorial-2006.ppt Sep 8 2010 ICANN Default Powerpoint Presentation IDN Reference Shelf Sep 8 2010 ICANN Default People Sep 8 2010 ICANN Default ALAC comment on the 3rd Revision of the Draft Implementation Plan for IDN ccTLDs Sep 8 2010 ICANN Default AL-2007-R-3 Sep 8 2010 ICANN Default At Large Resolution Navbar-Home.png Sep 8 2010 ICANN Default Advanced Getting Around Sep 8 2010 ICANN Default Quick Start Sep 8 2010 ICANN Default Announcements and Links Sep 8 2010 ICANN Default IDN Liaison Report 2010 Sep 8 2010 ICANN Default IDNs IN THE NEWS Sep 8 2010 ICANN Default Documents that people are working on Sep 8 2010 ICANN Default Spam??? Feedback for the IDN Policy Process Sep 8 2010 ICANN Default Discussion on IDN Working Group - Sunday 10th of February 2008, ICANN New Delhi meeting Sep 8 2010 ICANN Default AL-ALAC-ST-1209-1%20ALAC%20Statement%20on%20Draft%20Topic%20Paper%20forPolicy%20on%20the%20Introduction%20of%20IDN%20ccTLD.pdf Sep 8 2010 ICANN Default ALAC Statement on the Draft Topic Paper for Policy on the Introduction of IDN ccTLD Sep 8 2010 ICANN Default Congratulations! You know how to use a workspace Sep 8 2010 ICANN Default HX%20IGF%20IDN%202007.ppt Sep 8 2010 ICANN Default Powerpoint Presentation View-Page-Edit.png Sep 8 2010 ICANN Default Can I change something? Sep 8 2010 ICANN Default IDNs%20IGF%20WS.ppt Sep 8 2010 ICANN Default Powerpoint Presentation cnnic-eai.ppt Sep 8 2010 ICANN Default Powerpoint Presentation DSC01569.JPG Sep 8 2010 ICANN Default Andrzej%202007_11_12_RIO.ppt Sep 8 2010 ICANN Default ALAC Statement on Final Report on Three-Character Requirement and Variant Management Sep 8 2010 ICANN Default -- Salanieta Tamanikaiwaimaro aka Sala Tweeter: @SalanietaT Skype:Salanieta.Tamanikaiwaimaro Cell: +679 998 2851

1 0

The New gTLD Progam in CLASS IN is no more a swindle
by JFC Morfin Jan. 11, 2012

Jan. 11, 2012

The ICANN procedures are cute. They are not that easy to understand, follow and eventually comply with. However, they, from time to time, ultimately permit some transparency in order to show that it was possible not to pay ICANN for something small when you can get "samething" big for free (but without the ICANN legaleses). In the New gTLD Program case, I made an effort to try to save ICANN millions. You will find it at the URL http://forum.icann.org/lists/new-gtld-applicant-support-handbook/msg00013.h…. I hope this demonstrate enough that ICANN and the US Governments are not crooks: - they only did not "underline" the full truth, as every good sales, at it results from the small prints - however, and I am the proof, they made nothing to prevent the truth from being published before the gTLD candidates send their requests and checks. The truth is that: 1. there is no technical difference between gTLDs and IDNgTLDs except non contractual foreign software application (punycode family of alogithms) TLD registrant cannot control. 2. ICANN uses a "de facto" situation to register TLDs that can be "de jure" (RFCs) replicated in 65,535 other DNS top level registries. 3. TLDs may use protected IRNs (International Root Names) by WIPO or ISO. The use of a string as a TLD does not protect it as an IRN. 4. ICANN stays at the IETF Internet end to end layers under the ignorance of the US Government. This is obsolete: IETF RFCs have already transparently made inteligent users to scale to fringe to fringe Internet+. http://iutf.org/wiki/Internet%2B_architectural_Framework. This makes clear that the ICANN Pew gTLD Program brings to its gTLD registrants is a very worked-out screen of paper to sign and an entry in the DNS CLASS "IN" (ICANN/NTIA) every of us can replicate, - in full right: in 255 other CLASSes - at least in test: in 65.375 other ones. If this was plainly stated in the Agreement, this would be perfectly honnest. As it is not, Courts may have to decide. However, in favor of ICANN: 1. my mail was published by ICANN within the Pew gTLD Program dedicated part, on a public forumeveryone could read. 2. RFC are publicly published and TLD would be Managers should know them to correctly operates the service they plan to sell. After several RFCs over the last 29 years of DNS operations, RFC 5395 states anew: "DNS CLASSes have been little used but constitute another dimension of the DNS distributed database. In particular, there is no necessary relationship between the name space or root servers for one data CLASS and those for another data CLASS. The same DNS NAME can have completely different meanings in different CLASSes. The label types are the same, and the null label is usable only as root in every CLASS. As global networking and DNS have evolved, the IN, or Internet, CLASS has dominated DNS use. [] The current CLASS assignments [] are as follows: This simply means that for each ".abcd" top-zone IDNgTLD paid K$ 185++ to ICANN, there can be 65,535 other ".abcd" top-zones in the DNS. Some will be immediatel because the IUTF is going to accept a few CLASSes for family protection, customer documentation, testing of third party applications, etc. jfc

4 6