June 2009 - IDN-WG - lists.icann.org

Draft Implementation Plan for IDN Fast Track Proces
by Sivasubramanian Muthusamy July 16, 2009

July 16, 2009

Hello The third revision of the Draft Implementation Plan is at page http://icann.org/en/topics/idn/fast-track/draft-implementation-plan-cctld-c… is also attached as a PDF here. As per schedule ICANN public consultation closes on 15th July. ALAC consultation on this topic would open on 30th June and closes on 7th July, based on which a final draft is to be preapred and posted for voting on 9th. Voting would close on 14th on the ALAC submission. Please go through the attached PDF with specific consideration to the following: 1. Page 25 - 29 Process Overview and the detailed flowcharts- are there any comments about the process as outlined? 2. 3.4 Technical String Criteria : Should Alac recommend relaxation on the number of characters required? Is this a technical issue or a socio-political issue? What would be alac's position on this? 3. 5.5 contentin issues 4. 5.6 Processing of a Fast Track issue 5. 6.3 US Government Authorization: is this within the purview of alac to comment in the context of IDNs. 6. Are there specific IDN points from the various constituency sessions of other constituencies that alac is in agreement with, that may be featured as points agreed, in the alac draft comment? I also wish to submit to alac and the IDN Working Group to consider the fact that the fast track process has taken a long time, during which there have been positive developmens on the technical and process readiness on the part of ICANN to implement IDN's, so is there a need to imply a delayed implementation of the gTLD process? Would alac like to consider being equally concerned about ccTLDs and gTLDs? And is there anything that requires caution on the path towards implentation of IDNs? There was some opinion that DNS stability takes precedence over the fast track process. Is there any such contrary opinion and are these opinions have any validity? To truly fast track the IDN process, I wish to propose to alac to propose to ICANN that an "IDN Day" be organized, either for one full day preceeding the ICANN meeting to bring together the constituencies concerned to focussed sessions on security, legal and commericial issues, all related to IDN's. If an additional day is not possible, a relatively light day such as a Thrusday could be dedicated for discussions on IDNs for ICANN to come to a conclusive position on IDNs and truly fast track the implementation process. Sivasubramanian Muthusamy Blog: http://isocmadras.blogspot.com facebook: http://is.gd/x8Sh LinkedIn: http://is.gd/x8U6 Twitter: http://is.gd/x8Vz

5 15

Fwd: Draft Comments on the Draft Implementation Plan for IDN ccTLDs 3rd Revision.
by Sivasubramanian Muthusamy June 29, 2009

June 29, 2009

Hello, A draft comment on the 3rd revision of the "Draft Implementation plan for IDN ccTLDs" is forwarded to this working group for additions and comments. Please comment. Thank you Sivasubramanian Muthusamy IDN liaision. ---------- Forwarded message ---------- From: Sivasubramanian Muthusamy <isolatedn(a)gmail.com> Date: Sat, Jun 27, 2009 at 5:10 AM Subject: Draft Comments on the Draft Implementation Plan for IDN ccTLDs 3rd Revision. To: ALAC Internal List <alac-internal(a)atlarge-lists.icann.org> Cc: At-Large Staff <staff(a)alac.icann.org> ALAC Comments on Draft Implementation Plan for IDN ccTLD Fast Track Process Revision 3 Posted as an initial draft to start the comment process. The red line (actually it is in blue color) version of the 3rd revision of the draft implementation plan is attached to show changes During the ICANN meeting at Mexico, the ICANN Board encouraged the community to continue its work so that the implementation plan can be finalized and considered by the Board no later than at its annual meeting in 2009. ICANN has released the third revision of the Draft Implementation Plan for IDN ccTLDs. A public comment on this plan and the related papers is due on 15th July. Comments received will be used to revise the plan in preparation of a Final Implementation Plan which is expected to be provided for Board consideration no later than at the ICANN meeting in Seoul, 25-30 October 2009 1. In this revision detailed explanations of the entire evaluation process have been included together with flowcharts which points for clarity of expression and further progress towards implementation. ALAC notes these details in the Implementation plan as a sign that IDN TLDs are moving closer to implementation. 2. ALAC in agreement in principle that “the request for an IDN ccTLD cannot proceed through the Fast Track Process if the Panel or review team identifies that a requested string raises significant security and stability issues” ( 4.1) 3. In line with the IDNC WG Final Report, the external and independent DNS Stability Panel should be appointed to conduct technical due diligence and report to the ICANN Board. And in agreement with the IDNC WG report, the 3rd revision excludes the reference to the Registry Services Evaluation Process and the hint of DNSSEC but instead adds that “ICANN will secure the services of a competent technical panel (DNS Stability Panel) to make stability evaluations” And the report adds that “ICANN is finalizing the coordination of the DNS Stability panel and further details will be made available”. ALAC awaits further details. 4. The 3rd revision further enhances the role of Governments in the IDN ccTLD application process with its emphasis on “evidence of support” and the deletion of [evidenced of] “non-objection” as documentation requirements in the Preparation Stage. As in previous drafts, the 3 rd revision retains its position that such evidence of support needs to be from “the Minister with the portfolio responsible for domain name administration, ICT, foreign affairs or Office of the Prime Minister or President; or a senior representative of the agency or department responsible for domain name administration, ICT, Foreign Affairs or the Office of the Prime Minister.” While this stipulation reflects the positive involvement of Governments in the IDN TLD process and their concerns, and is in tune with ICANN's ccTLD delegation policies, ALAC notes with apprehension that International Domain Names as ccTLDs, together with ascii ccTLDs could enable governments to control access and curtail civil liberties. ALAC expresses concern about the emphatic reference to Governments which in effect makes the Governments as the requesters, either directly or indirectly. The description of the Preparation Stage process ( 5.1.1) specifies 1) 1. Support from the relevant government or public authority 2) Support ... by the relevant government, ALAC expresses concerns on this continued and emphatic references to Governments as total deviation from the gTLD processes and principles. 5. ALAC is committed to multi-stakeholder approach and notes postively the inclusion of the passage “The application should demonstrate there has been community dialogue regarding which string is the appropriate representation of the country in the selected string(s) and/or language(s)/script(s), and that appropriate stakeholders have been involved in the decision making process.” and feels that this passage alone could address the concerns of Governments and all stakeholders. 6. Alac welcomes the proposed submission system for the string evaluation stage (Stage 2) as a web-based form that identifies the information necessary. ALAC feels that web based processes would be of help in enabling swift submission of the required information and would lead to transparency even in the level of applications as submitted. 7. ALAC notes that the 3rd revision excludes portions of Module 7 of the 2nd revision purportedly "to only contain discussions of outstanding issues". Topics deleted from the previous versions of the plan are “considered solved” though included elsewhere in the plan “as deemed necessary”. Module 7: Discussion of Additional Topics has been entirely deleted in the third revision with the observation that “most of the topics remaining in this module relate directly to the overarching requirements to Preserve the security and stability of the DNS and Ensure compliance with the IDNA protocol and IDN Guidelines.The remaining topics included have all been addressed in supporting papers to this plan. (But the hypertext links to the documents are not included in the draft implementation Plan document.) Alac wishes to comment that the topics could have been listed under a separate section of the report as topics considered solved to retain the extent and depth of topics related to the IDN TLD process. 8. ALAC feels that the topic of “Financial Contribution” or cost recovery, for instance could not be considered as a topic that can be “considered solved”. ALAC feels that more discussions are needed on the details of the proposed cost recovery model. Sivasubramanian Muthusamy ALAC IDN liaison.

1 1

Re: [IDN-WG] Fwd: [At-Large] Can anyone surf to peking university?
by Sivasubramanian Muthusamy June 16, 2009

June 16, 2009

Hello On Tue, Jun 16, 2009 at 8:11 PM, Eduardo A. Suárez < esuarez(a)fcaglp.fcaglp.unlp.edu.ar> wrote: > Hi, > > I can reach > > http://北京大学.cn/ > The URL looks strange, it doesn't work. > > and > > http://www.pku.edu.cn/ > > The correct Punycode is xn--1lq90ic7fzpc.cn so the URL will be > http://xn--1lq90ic7fzpc.cn/ These URL's work. The issue is not whether Peking University's website is accessible, the issue is that of China maintaining its own national root, and its cabability to shut down access of the domain names under its control for the rest of the world. Whether or not this issue concerning the URL of the Peking University is accurately reported or not, the underlying issue is valid. (As an update of the message in the at-Large list, now cross posted at the Internet Governace Caucus mailing list, Joe Baptista actually has made some anti-ICANN statements, and makes a bizarre suggestion that each nation should maintain its own root away from ICANN. He says that it is also his comment to NTIA.. He is receiving fitting responses that are interesting) IDN policy development, in this context, may have to pay attention to the importance of preserving the root server infrastructure as globally accessible and not give any room for any possibility of alternate root or restricted or restrictable DNS infrastructure that could make it possible for a whole script or region being shut down for the rest of the world. Sivasubramanian M. > > > Cheers, > Eduardo.- > > > Quoting Sivasubramanian Muthusamy <isolatedn(a)gmail.com>: > > Hello, >> >> Posting this here as this is pertinent to IDN policy and needs to be >> followed. >> >> Sivasubramanian Muthusamy >> ALAC IDN Liaison. >> >> >> ---------- Forwarded message ---------- >> From: Joe Baptista <baptista(a)publicroot.org> >> Date: Mon, Jun 15, 2009 at 9:23 PM >> Subject: [At-Large] Can anyone surf to peking university? >> To: governance(a)lists.cpsr.org, At-Large Worldwide < >> at-large(a)atlarge-lists.icann.org> >> >> >> This is the official URL for Peking University - it's in IDN >> >> http://xn--1lq90ic7fzpc.xn--fiqs8s/ >> >> how many people here can surf to that URL? I can see it. but any one on >> the ICANN root can't. Chinese domains can only be seen in china or to >> those >> outside china who see the chinese root system. >> >> cheers >> joe baptista >> >> p.s. where is icann in this equation? >> >> -- >> Joe Baptista >> >> www.publicroot.org >> PublicRoot Consortium >> ---------------------------------------------------------------- >> The future of the Internet is Open, Transparent, Inclusive, Representative >> & >> Accountable to the Internet community @large. >> ---------------------------------------------------------------- >> Office: +1 (360) 526-6077 (extension 052) >> Fax: +1 (509) 479-0084 >> >> Personal: www.joebaptista.wordpress.com >> _______________________________________________ >> At-Large mailing list >> At-Large(a)atlarge-lists.icann.org >> >> http://atlarge-lists.icann.org/mailman/listinfo/at-large_atlarge-lists.ican… >> >> At-Large Official Site: http://atlarge.icann.org >> _______________________________________________ >> IDN-WG mailing list >> IDN-WG(a)atlarge-lists.icann.org >> >> http://atlarge-lists.icann.org/mailman/listinfo/idn-wg_atlarge-lists.icann.… >> >> IDN WG Wiki: >> https://st.icann.org/idn-policy/index.cgi?at_large_idn_policy >> >> > > > -- > Eduardo A. Suarez > Facultad de Ciencias Astronomicas y Geofisicas > Universidad Nacional de La Plata > Tel: (0221)-4236593 int. 158(35)/Cel: (0221)-15-4557542/Casa: > (0221)-4526589 > > ------------------------------------------------------------------------------ > "In a world where data is the coin of the realm, and transmissions are > guarded > by no better sentinels than man-made codes and corruptible devices, there > is > no such thing as a secret." - This Alien Shore > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > >

1 0

Fwd: [At-Large] Can anyone surf to peking university?
by Sivasubramanian Muthusamy June 16, 2009

June 16, 2009

Hello, Posting this here as this is pertinent to IDN policy and needs to be followed. Sivasubramanian Muthusamy ALAC IDN Liaison. ---------- Forwarded message ---------- From: Joe Baptista <baptista(a)publicroot.org> Date: Mon, Jun 15, 2009 at 9:23 PM Subject: [At-Large] Can anyone surf to peking university? To: governance(a)lists.cpsr.org, At-Large Worldwide < at-large(a)atlarge-lists.icann.org> This is the official URL for Peking University - it's in IDN http://xn--1lq90ic7fzpc.xn--fiqs8s/ how many people here can surf to that URL? I can see it. but any one on the ICANN root can't. Chinese domains can only be seen in china or to those outside china who see the chinese root system. cheers joe baptista p.s. where is icann in this equation? -- Joe Baptista www.publicroot.org PublicRoot Consortium ---------------------------------------------------------------- The future of the Internet is Open, Transparent, Inclusive, Representative & Accountable to the Internet community @large. ---------------------------------------------------------------- Office: +1 (360) 526-6077 (extension 052) Fax: +1 (509) 479-0084 Personal: www.joebaptista.wordpress.com _______________________________________________ At-Large mailing list At-Large(a)atlarge-lists.icann.org http://atlarge-lists.icann.org/mailman/listinfo/at-large_atlarge-lists.ican… At-Large Official Site: http://atlarge.icann.org

1 0

discussion on the latest revision of the Draft Implementation Plan for the IDN ccTLD Fast Track Process
by Sivasubramanian Muthusamy June 5, 2009

June 5, 2009

Hello ICANN has released the (3rd) revised Draft Implementation Plan for the IDN ccTLD Fast Track Process Public comment forum on this is open until 15 July 2009. Consultation papers have also been made available on the three remaining topics: Documentation of Responsibility, Fee and Cost Considerations, and the IDN Tables and Variant Management. The papers describe: 1. Draft Implementation Plan for the IDN ccTLD Fast Track Process (rev 3.0) (redlined)<http://icann.org/en/topics/idn/fast-track/draft-implementation-plan-cctld-r…>[PDF, 528K] 2. Draft Implementation Plan for the IDN ccTLD Fast Track Process (rev 3.0) (clean)<http://icann.org/en/topics/idn/fast-track/draft-implementation-plan-cctld-c…>[PDF, 287K] 3. Revised Proposed Implementation Details Regarding Documentation of Responsibility<http://icann.org/en/topics/idn/fast-track/proposed-implementation-details-d…>[PDF,145K] 4. Revised Proposed Implementation Details Regarding IDN Tables Development and Usage (redlined)<http://icann.org/en/topics/idn/fast-track/proposed-implementation-details-i…>[PDF, 146K] 5. Revised Proposed Implementation Details Regarding IDN Tables Development and Usage (clean)<http://icann.org/en/topics/idn/fast-track/proposed-implementation-details-i…>[PDF, 157K] 6. Proposed Implementation Details Regarding Financial Contributions to Support the Development and Deployment of IDN ccTLDs<http://icann.org/en/topics/idn/fast-track/proposed-implementation-details-f…>[PDF, 84K] 7. Cost Analysis of IDN ccTLDs: Focus on Program Development and Processing Costs<http://icann.org/en/topics/idn/fast-track/analysis-idn-cctld-development-pr…>[PDF, 148K] * Related links: * Public comment period for Fast Track: http://www.icann.org/en/public-comment/public-comment-200907.html#fast-track<http://icann.org/en/public-comment/public-comment-200907.html#fast-track> Staff considerations on received comments: (coming) Working Group Final Report (with public comments): http://www.icann.org/en/topics/idn/fast-track/staff-considerations-idnc-wg-…<http://icann.org/en/topics/idn/fast-track/staff-considerations-idnc-wg-fina…>[PDF, 269K] Fast Track webpage: http://www.icann.org/en/topics/idn/fast-track/<http://icann.org/en/topics/idn/fast-track/> Posted in this list for discussion, please. Sivasubramanian Muthusamy ALAC IDN Liaison

1 0