November 2015 - Idngwg - lists.icann.org

Suggestions for items for discussion
by Sarmad Hussain Nov. 24, 2015

Nov. 24, 2015

Dear All, Here are more items which may be considered for further discussion. As discussed, I am suggesting a liberal list. 1. Transition and Terminology a. Any (residual) issues/items from IDNA2003 to IDNA2008 transition? b. Glossary of terms around LGRs and variants from the IDN TLD project and other work 2. Language table format and managing consistency of end-user experience a. IDN Table format in XML, based on new LGR specifications being developed b. Role of reference second level tables in managing consistency and differences across TLDs for a predictable end-user experience c. Relationship between language tables and script tables? Other categories (some languages but not entire script)? d. Managing consistence across levels; relationship of Root Zone LGR and the second level IDN tables? 3. Variants a. Variant states (number and nomenclature) and state-change mechanisms (e.g. blocked, allocatable, allocated, reserved, etc.) b. Primary vs. secondary variants in Chinese language (other scripts or languages?) c. Policy for activating variants i. Automatic or registrant requested allocation 1. Automatic activation of variant labels at second level for Chinese language domain names ii. Minimum and Maximum number of allocated variants/Ceiling value? iii. Choosing which variants may be activated d. Variants at second level must(?) be allocated to the same registrant? e. Implication of second level variants on TMCH 4. Similarity/Confusability of labels a. Homographic issues within script i. General homographic issues within a script ii. Scope of confusability: upper to lower case mapping b. Cross-script homoglyphs management to prevent phishing possibilities- cox.com, where "cox" can be in Latin or Greek or Cyrillic i. Script mixing within a second level label ii. Script mixing across levels iii. Scope of confusability: upper to lower case mapping iv. Is ASCII a special case for mixing? 5. Registration data a. Registration data for IDNs b. Registration data of variants - information regarding variant sets and variant label disposition(s) Regards, Sarmad

2 1

IDN Implementation Guidelines WG meeting 18 Nov 2015
by Sarmad Hussain Nov. 24, 2015

Nov. 24, 2015

Dear All, Please find attached the minutes of the meeting on 18 Nov. for your review and feedback (in case I missed some point). The same have been posted on our WG wiki (along with the call recording). See: https://community.icann.org/display/IDN/IDN+implementation+Guideline. A list of relevant documents has been started on this WG wiki as well. Please feel free to go and edit/add information on it. The Action Items from the meeting are posted below. For AI3, the suggested time for regular meetings is Wednesdays 11am UTC. S.No. Action Owner 1 Staff (and other members) to develop a list of relevant documents on the WG wiki. Staff to identify areas in these documents where reference to IDNs is made. Staff; All WG members 2 The members to contribute items and issues to the mailing list. All are encouraged to share as many items as possible. All WG members 3 Those not attending the meeting to let staff know if the current time/day does not work. WG members who could not attend the call on 11 Nov. Regards, Sarmad

2 1

FW: A draft for the meeting Wednesday
by Feher, Kal Nov. 18, 2015

Nov. 18, 2015

Forwarding reply. I think the group email got dropped off accidentally. PS It would be great if the mailing list address ‘sent on behalf’ to avoid direct replies going missing From: Edmon Chung <edmon(a)registry.asia<mailto:edmon@registry.asia>> Date: Wednesday, 18 November 2015 at 9:11 PM To: 'Mats Dufberg' <mats.dufberg(a)iis.se<mailto:mats.dufberg@iis.se>>, Kal Feher <kalman.feher(a)neustar.biz<mailto:kalman.feher@neustar.biz>> Subject: RE: [Idngwg] A draft for the meeting Wednesday Agree with using MUST / SHOULD and possibly MAY too. Agree that we should probably revisit specific assignments after we have a good stocktaking of the issues. Edmon From: idngwg-bounces(a)icann.org<mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Mats Dufberg via Idngwg Sent: Wednesday, November 18, 2015 5:10 PM To: Feher, Kal; idngwg(a)icann.org<mailto:idngwg@icann.org> Subject: Re: [Idngwg] A draft for the meeting Wednesday Rather than deferring to another document we can explicitly state for each statement if it is a MUST, SHOULD or a recommendation. I do not think that the Guidelines will be a large document, and by splitting it into two documents we increase confusion and the risk that both documents are not read. Let us postpone the final decision, but you raise an important point that we must consider if it is a MUST, a SHOULD or a recommendation. In my list that I sent some hours ago probably contain all three types. Yours, Mats -- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.iis.se_en&d=CwMFaQ&…> Från: <idngwg-bounces(a)icann.org<mailto:idngwg-bounces@icann.org>> on behalf of idngwg <idngwg(a)icann.org<mailto:idngwg@icann.org>> Svara till: "Feher, Kal" <Kalman.Feher(a)neustar.biz<mailto:Kalman.Feher@neustar.biz>> Datum: Wednesday 18 November 2015 09:06 Till: idngwg <idngwg(a)icann.org<mailto:idngwg@icann.org>> Ämne: Re: [Idngwg] A draft for the meeting Wednesday I think you may have misunderstood my point. The guidelines are part of the RA which makes them enforceable. There’s no likelihood they’ll be removed from the RA, so we have to be mindful of the impact of any inclusion, no matter how trivial. Therefore only items we want to be explicitly enforceable should be present in the guidelines. However we may want to explore alternative expressions for our advice if we consider something important enough to document, but impractical for contractual inclusion. My question during our first meeting regarding the original purpose of the guidelines was with their current use in mind. The answer as I recall, was that there was no specific goal and that they evolved through several iterations with no purpose other than to document good implementation advice. Given that the older revisions were developed ignorant of what would become the current use of the guidelines, we should take this as an opportunity to consider exactly what belongs in a contractually enforceable IDN implementation document. I have to disagree regarding your suggestion that we not defer to other documents. I think we should always defer to other documents. Having any specific advice within the guidelines will result in those items becoming immutable, no matter how impractical they might become. There are forums for providing expert advice on specific IDN topics and we should allow those forums to guide Registry operators rather than overriding them with this document. From: <idngwg-bounces(a)icann.org<mailto:idngwg-bounces@icann.org>> on behalf of "idngwg(a)icann.org<mailto:idngwg@icann.org>" <idngwg(a)icann.org<mailto:idngwg@icann.org>> Reply-To: Edmon Chung <edmon(a)registry.asia<mailto:edmon@registry.asia>> Date: Wednesday, 18 November 2015 at 5:39 PM To: "idngwg(a)icann.org<mailto:idngwg@icann.org>" <idngwg(a)icann.org<mailto:idngwg@icann.org>> Subject: Re: [Idngwg] A draft for the meeting Wednesday Those are all good points. I am not so sure whether enforcement/oversight is within the scope of our discussion though. On that, I think perhaps more appropriate to rely on existing mechanisms (including for gTLDs the new implementation & policy recommendations) On the question of “standards or advisory body”, I view this group as the expert “body” producing the guidelines. Although I am not sure whether it is appropriate to understand us as a “body” per se. More specifically, rather than *defer* to other documents, perhaps we can identify a few sets of documents as our points of references, and *refer* to them in the guidelines: - Current (and past versions of) IDN Guidelines - Policy related documents (from ccNSO and GNSO) concerning IDN - Relevant portions of IDN fast track and AGB - ICANN IDN Variant project documents - IDN related RFCs and ongoing IETF works - (and others maybe) Building on them though, I think we will need to produce recommendations that may not be explicitly included in those documents. Edmon From:idngwg-bounces@icann.org<mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Feher, Kal via Idngwg Sent: Wednesday, November 18, 2015 2:16 PM To: idngwg(a)icann.org<mailto:idngwg@icann.org> Subject: Re: [Idngwg] A draft for the meeting Wednesday My suggested talking points below: Given that this will be an enforceable document, what items belong in the guidelines and what items should be moved out to a non enforceable advisory document? What criteria and oversight will be applied to each item staying within the guidelines? Should items come from authoritative sources and if those sources modify their advice, should the guidelines explicitly allow contracted parties to follow those modifications? Will we include any items which have not been recommended by a domain name standards or advisory body and if so, should those recommendations be enforceable? From: <idngwg-bounces(a)icann.org<mailto:idngwg-bounces@icann.org>> on behalf of "idngwg(a)icann.org<mailto:idngwg@icann.org>" <idngwg(a)icann.org<mailto:idngwg@icann.org>> Reply-To: Edmon Chung <edmon(a)registry.asia<mailto:edmon@registry.asia>> Date: Wednesday, 18 November 2015 at 1:09 PM To: "idngwg(a)icann.org<mailto:idngwg@icann.org>" <idngwg(a)icann.org<mailto:idngwg@icann.org>> Subject: Re: [Idngwg] A draft for the meeting Wednesday Mat’s list is a good set of items for starting discussion. My contribution below on a more abstract/structural level. I think the following components may be useful for the guidelines: - Terminology - IDN Registration Policy Components - IDN policy development checklist/references - IDN policies/tables/repertoires considerations - Technical & linguistic considerations - IDN Registration - 2LD registrations - ccTLD vs gTLD contextual differences - IDN TLDs - IDN Variants - IDN Policy implementation recommendations - additional implementation guidelines based on ccNSO/GNSO documents - IDN registration systems A very rough off the top of my head framework. Edmon From:idngwg-bounces@icann.org<mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Mats Dufberg via Idngwg Sent: Wednesday, November 18, 2015 6:40 AM To: idngwg Subject: [Idngwg] A draft for the meeting Wednesday Friends, Enclosed is my contribution to the meeting tomorrow. Yours, Mats -- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.iis.se_en&d=CwMFaQ&…>

1 0

A draft for the meeting Wednesday
by Mats Dufberg Nov. 18, 2015

Nov. 18, 2015

Friends, Enclosed is my contribution to the meeting tomorrow. Yours, Mats -- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/<http://www.iis.se/en>

3 6

IDN Implementation Guidelines WG meeting
by Sarmad Hussain Nov. 18, 2015

Nov. 18, 2015

Agenda: - Review of reference documents - identify sets of documents to review - what from the documents will be useful for consideration - Stocktaking of issues - approach / cataloguing - discussion of substantive points Link to Adobe Connect: https://icann.adobeconnect.com/idn/ *Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number* (Remember to change the Country Code if needed). After joining the call, as a courtesy to others and the presenters, please MUTE your phone. This can be done by selecting *6 on your keypad. To UNMUTE select *6 again. If you are Unable to log into Adobe Connect and can only join via phone: List of International Dial In Numbers: https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=4054049491&num=1-719-… Participant Passcode: 4054049491

1 0

What is the status of the wiki?
by Mats Dufberg Nov. 17, 2015

Nov. 17, 2015

I still do not have any account on the wiki. Has anyone tried to log in? Yours, Mats -- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/<http://www.iis.se/en>

1 0

tomorrows Meeting
by Wael Nasr Nov. 17, 2015

Nov. 17, 2015

Dear All something urgent came up and I will not be able to attend the con call My sincere apologies. I will listen to the recording after wards and I have already sent an email with some points. My main concern is that for IDN to grow we need to take into account the local regulatory legal and cultural dimension in key markets where IDN is more important like China, India , Arabia and Russia . -- --------------------------- Wael Nasr SVP - TLDVIilla LLC http://icannwiki.com/Wael_Nasr http://www.linkedin.com/in/nasrwael US Office : +1 209 682 5144. Bahrain mobile :+973 393 16891

1 0

Accepted: IDN Implementation Guidelines WG meeting
by rmohan＠afilias.info Nov. 16, 2015

Nov. 16, 2015

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 15.0 MIMEDIR//EN VERSION:2.0 METHOD:REPLY X-MS-OLK-FORCEINSPECTOROPEN:TRUE BEGIN:VTIMEZONE TZID:Pakistan Standard Time BEGIN:STANDARD DTSTART:16010101T000000 TZOFFSETFROM:+0500 TZOFFSETTO:+0500 END:STANDARD END:VTIMEZONE BEGIN:VEVENT ATTENDEE;PARTSTAT=ACCEPTED:mailto:rmohan@afilias.info CLASS:PUBLIC COMMENT:\n CREATED:20151116T022745Z DTEND;TZID="Pakistan Standard Time":20151118T170000 DTSTAMP:20151116T022745Z DTSTART;TZID="Pakistan Standard Time":20151118T160000 LAST-MODIFIED:20151116T022745Z LOCATION:https://icann.adobeconnect.com/idn/ PRIORITY:5 SEQUENCE:0 SUMMARY;LANGUAGE=en-us:Accepted: IDN Implementation Guidelines WG meeting TRANSP:OPAQUE UID:040000008200E00074C5B7101A82E0080000000090850BC6DB1ED101000000000000000 01000000084965B6B919B094780DCF8CB1417E761 X-ALT-DESC;FMTTYPE=text/html:<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//E N">\n<HTML>\n<HEAD>\n<META NAME="Generator" CONTENT="MS Exchange Server ve rsion rmj.rmm.rup.rpr">\n<TITLE></TITLE>\n</HEAD>\n<BODY>\n\n\n<P DIR=LTR><SPAN LANG="en-us"></SPAN></P>\n\n< /BODY>\n</HTML> X-MICROSOFT-CDO-BUSYSTATUS:BUSY X-MICROSOFT-CDO-IMPORTANCE:1 X-MS-OLK-AUTOFILLLOCATION:FALSE X-MS-OLK-CONFTYPE:0 END:VEVENT END:VCALENDAR

1 0

IDN Implementation Guidelines WG meeting
by Sarmad Hussain Nov. 15, 2015

Nov. 15, 2015

Agenda: TBA Link to Adobe Connect: https://icann.adobeconnect.com/idn/ *Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number* (Remember to change the Country Code if needed). After joining the call, as a courtesy to others and the presenters, please MUTE your phone. This can be done by selecting *6 on your keypad. To UNMUTE select *6 again. If you are Unable to log into Adobe Connect and can only join via phone: List of International Dial In Numbers: https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=4054049491&num=1-719-… Participant Passcode: 4054049491

1 0

Community wiki account
by Alireza Saleh Nov. 13, 2015

Nov. 13, 2015

Hi, Those working group members who don't have community wiki username/password, please send an email to engagement(a)icann.org<mailto:engagement@icann.org> with your fullname and your preferred email address. Thanks Alireza

1 0