May 2016 - Idngwg - lists.icann.org

meeting notes and updated document 19 May 2016
by Sarmad Hussain May 20, 2016

May 20, 2016

Dear All, Please find attached the meeting notes from 19 May and the updated draft Guidelines document. Please let me know if you have any feedback or suggestions. The action item from the meeting is: S. No. Action Items Owner 1 Staff to update the draft Guidelines document based on the discussion and circulate SH Kindly note that the meeting recording and the attached notes are also available at the IDNGWG wiki page: https://community.icann.org/display/IDN/IDN+Implementation+Guidelines. Regards, Sarmad From: idngwg-bounces(a)icann.org [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Thursday, May 19, 2016 9:09 AM To: idngwg(a)icann.org Subject: Re: [Idngwg] Draft document initial version Thanks Edmon, Dennis and Chris for the suggestions in the text. Dear All, The suggested revisions have been incorporated in the attached document, for further discussion during our call today. Regards, Sarmad From: Edmon Chung [mailto:edmon@registry.asia] Sent: Thursday, May 19, 2016 4:53 AM To: Sarmad Hussain <sarmad.hussain(a)icann.org <mailto:sarmad.hussain@icann.org> >; 'Tan Tanaka, Dennis' <dtantanaka(a)verisign.com <mailto:dtantanaka@verisign.com> > Cc: idngwg(a)icann.org <mailto:idngwg@icann.org> Subject: RE: [Idngwg] Draft document initial version Simple suggestion for 2.1 as discussed in last call: //current recommendation 1: Top-level domain ("TLD") registries supporting Internationalized Domain Names ("IDNs") will do so in strict compliance with the requirements of the IETF protocol for Internationalized Domain Names in Applications. The initial version of this protocol was defined in RFCs 3454, 3490, 3491, and 3492. A revised version is defined in RFCs 5890, 5891, 5892, 5893, and 5894. Both will be in parallel use in applications for an indeterminate transitional period but registries will conform fully with IDNA2008 in the shortest practicable order. Recommendation: Remove reference to obsoleted RFCs (3,xxx series) and just refer to current ones (5,xxx series): Top-level domain ("TLD") registries supporting Internationalized Domain Names ("IDNs") will do so in strict compliance with the requirements of the IETF protocol for Internationalized Domain Names in Applications, as defined in RFCs 5890, 5891, 5892, 5893, and 5894. ================================== Also, due to travel schedules adjustments, I may not be able to join the call later today. I am supposed to arrive into Tokyo about 45 minutes before the call. If there is no delay, I should be able to join. In case of delay, my apologies. Edmon From: idngwg-bounces(a)icann.org <mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Wednesday, 18 May 2016 17:02 PM To: Tan Tanaka, Dennis <dtantanaka(a)verisign.com <mailto:dtantanaka@verisign.com> > Cc: idngwg(a)icann.org <mailto:idngwg@icann.org> Subject: Re: [Idngwg] Draft document initial version Thank you Dennis. From: Tan Tanaka, Dennis [mailto:dtantanaka@verisign.com] Sent: Wednesday, May 18, 2016 1:21 PM To: Sarmad Hussain <sarmad.hussain(a)icann.org <mailto:sarmad.hussain@icann.org> >; idngwg(a)icann.org <mailto:idngwg@icann.org> Subject: Re: [Idngwg] Draft document initial version Sarmad, et al Please find enclosed a revised Introduction section for version 4 with commentary. In doing this I reviewed previous versions of the guidelines and tried to come up with a short and sweet version that keeps it generic (i.e. not 2013 RA specific). I will be a few minutes late due to a schedule conflict. Talk to you soon. Dennis From: <idngwg-bounces(a)icann.org <mailto:idngwg-bounces@icann.org> > on behalf of Sarmad Hussain <sarmad.hussain(a)icann.org <mailto:sarmad.hussain@icann.org> > Date: Wednesday, May 4, 2016 at 2:00 PM To: "idngwg(a)icann.org <mailto:idngwg@icann.org> " <idngwg(a)icann.org <mailto:idngwg@icann.org> > Subject: [Idngwg] Draft document initial version Dear IDNGWG members, Please find attached the an initial version of the document derived from the issues list and follow our discussion in the previous conf. call (see action items in the email below). I have divided “Terminology and Transition” to two sections and added a place holder for EPP, as raised by the community, totaling to eight items – for the WG to finalize. I have also gone through the earlier version 3.0 of these guidelines and added the recommendations from it in the relevant sections (all nine have been mapped) – shown in italics – as a reference starting point. Finally, I have added the terminology we are identifying in the appendix of this document. This list will grow over time, and we will also need to finalize the definitions for each term. The recommendation section against issue is left blank for the WG to discuss and advise. Please feel free to share your feedback to develop the document further. Looking forward to your call tomorrow (Thursday). Regards, Sarmad From: idngwg-bounces(a)icann.org <mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Friday, April 22, 2016 3:54 PM To: idngwg(a)icann.org <mailto:idngwg@icann.org> Subject: Re: [Idngwg] Agenda for meeting on 20160421 Dear All, Please find attached a summary of the discussion during our meeting on 21 April, with the following action items. S. No. Action Owner 1 WG members should note that it is being suggested to include indication of recommendations or relevant questions in the scope of initial WG report, in addition to the list of issues. WG members to share their feedback on the proposed scope. WG Members not on the call on 20160421 2 Staff to start the initial report for the WG SH Please feel free to suggest any edits to the summary. Call recording and summary is available at IDNGWG wiki page: https://community.icann.org/display/IDN/IDN+Implementation+Guidelines. Regards, Sarmad From: idngwg-bounces(a)icann.org <mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Thursday, April 21, 2016 3:49 PM To: idngwg(a)icann.org <mailto:idngwg@icann.org> Subject: [Idngwg] Agenda for meeting on 20160421 Dear All, Here is a tentative agenda for the meeting today: 1. review feedback from community from Marrakech meeting 2. consider next steps and scope of initial/interim report 3. timeframe for 2. Regards, Sarmad

1 0

Non-IDN-labels with hyphen in position 3 and 4
by Mats Dufberg May 19, 2016

May 19, 2016

On the meeting today we had a discussion on the following text in the upcoming Guidlines: <quote> //current recommendation 8: No label containing hyphens in the third and fourth positions will be registered unless it is a valid A-label, with reservation for transitional action in accordance with the preceding Guideline. Hyphens in these positions are explicitly reserved to indicate encoding schemes, of which IDNA is only one instantiation. These guidelines are not intended to assist with any other instantiations. </quote> The questions was if the IDNA standards included any restriction against non-A-labels with hyphen in position 3 and 4, e.g. xx--mytest. In RFC 5890, section 2.3 it says <quote> Some strings that are prefixed with "xn--" to form labels may not be the output of the Punycode algorithm, may fail the other tests outlined below, or may violate other IDNA restrictions and thus are also not valid IDNA labels. (...) Labels within the class of R-LDH labels that are not prefixed with "xn--" are also not valid IDNA labels. (...) (...) For IDNA-aware systems, the valid label types are: A-labels, U-labels, and NR-LDH labels. </quote> Yours, Mats -- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/<http://www.iis.se/en>

1 0

Re: [Idngwg] Draft document initial version
by Tan Tanaka, Dennis May 19, 2016

May 19, 2016

Sarmad, et al Please find enclosed a revised Introduction section for version 4 with commentary. In doing this I reviewed previous versions of the guidelines and tried to come up with a short and sweet version that keeps it generic (i.e. not 2013 RA specific). I will be a few minutes late due to a schedule conflict. Talk to you soon. Dennis From: <idngwg-bounces(a)icann.org> on behalf of Sarmad Hussain <sarmad.hussain(a)icann.org> Date: Wednesday, May 4, 2016 at 2:00 PM To: "idngwg(a)icann.org" <idngwg(a)icann.org> Subject: [Idngwg] Draft document initial version Dear IDNGWG members, Please find attached the an initial version of the document derived from the issues list and follow our discussion in the previous conf. call (see action items in the email below). I have divided “Terminology and Transition” to two sections and added a place holder for EPP, as raised by the community, totaling to eight items – for the WG to finalize. I have also gone through the earlier version 3.0 of these guidelines and added the recommendations from it in the relevant sections (all nine have been mapped) – shown in italics – as a reference starting point. Finally, I have added the terminology we are identifying in the appendix of this document. This list will grow over time, and we will also need to finalize the definitions for each term. The recommendation section against issue is left blank for the WG to discuss and advise. Please feel free to share your feedback to develop the document further. Looking forward to your call tomorrow (Thursday). Regards, Sarmad From: idngwg-bounces(a)icann.org [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Friday, April 22, 2016 3:54 PM To: idngwg(a)icann.org Subject: Re: [Idngwg] Agenda for meeting on 20160421 Dear All, Please find attached a summary of the discussion during our meeting on 21 April, with the following action items. S. No. Action Owner 1 WG members should note that it is being suggested to include indication of recommendations or relevant questions in the scope of initial WG report, in addition to the list of issues. WG members to share their feedback on the proposed scope. WG Members not on the call on 20160421 2 Staff to start the initial report for the WG SH Please feel free to suggest any edits to the summary. Call recording and summary is available at IDNGWG wiki page: https://community.icann.org/display/IDN/IDN+Implementation+Guidelines. Regards, Sarmad From: idngwg-bounces(a)icann.org<mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Thursday, April 21, 2016 3:49 PM To: idngwg(a)icann.org<mailto:idngwg@icann.org> Subject: [Idngwg] Agenda for meeting on 20160421 Dear All, Here is a tentative agenda for the meeting today: 1. review feedback from community from Marrakech meeting 2. consider next steps and scope of initial/interim report 3. timeframe for 2. Regards, Sarmad

4 4

IDN Implementation Guidelines WG meeting - alternate Thursdays 11am UTC
by Sarmad Hussain May 19, 2016

May 19, 2016

Adobe Connect - IDN Meeting room: How to connect: 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: https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=1064158692&num=1-719-… Participant Passcode: 1064158692

1 0

notes from the meeting on 20160505
by Sarmad Hussain May 6, 2016

May 6, 2016

Dear All, Kindly find attached the notes from the IDNGWG meeting held on 5 May 2016. Please suggest any edits or additions. It was noted in the meeting that we should reach out to the WG members not attending the calls to address any challenges they may have in the participation. Please feel free to share any feedback in this context with me or on the list. The WG members started the discussion on the document which was shared earlier. Here are the action items. S. No. Action Items Owner 1 Introduction: Suggest changes to first introductory legacy text for further discussion DT 2 Introduction: Second sentence to be made more accurate, saying that IDN Guidelines are applicable more generally across gTLDs SH 3 2.1 Transition: Suggest changes in current recommendation 1 for further discussion EC 4 2.1 Transition: Suggest changes in current recommendation 2 for further discussion CD The notes and the recording of the session are also available at IDNGWG wiki page: https://community.icann.org/display/IDN/IDN+Implementation+Guidelines. Regards, Sarmad From: Edmon Chung [mailto:edmon@registry.asia] Sent: Thursday, May 05, 2016 3:11 PM To: Sarmad Hussain <sarmad.hussain(a)icann.org>; idngwg(a)icann.org Subject: RE: [Idngwg] Draft document initial version much thanks for pulling this together. This looks like a good starting point for our discussions for today. Talk to everyone soon. Edmon From: idngwg-bounces(a)icann.org <mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Thursday, 5 May 2016 02:00 AM To: idngwg(a)icann.org <mailto:idngwg@icann.org> Subject: [Idngwg] Draft document initial version Dear IDNGWG members, Please find attached the an initial version of the document derived from the issues list and follow our discussion in the previous conf. call (see action items in the email below). I have divided "Terminology and Transition" to two sections and added a place holder for EPP, as raised by the community, totaling to eight items - for the WG to finalize. I have also gone through the earlier version 3.0 of these guidelines and added the recommendations from it in the relevant sections (all nine have been mapped) - shown in italics - as a reference starting point. Finally, I have added the terminology we are identifying in the appendix of this document. This list will grow over time, and we will also need to finalize the definitions for each term. The recommendation section against issue is left blank for the WG to discuss and advise. Please feel free to share your feedback to develop the document further. Looking forward to your call tomorrow (Thursday). Regards, Sarmad From: idngwg-bounces(a)icann.org <mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Friday, April 22, 2016 3:54 PM To: idngwg(a)icann.org <mailto:idngwg@icann.org> Subject: Re: [Idngwg] Agenda for meeting on 20160421 Dear All, Please find attached a summary of the discussion during our meeting on 21 April, with the following action items. S. No. Action Owner 1 WG members should note that it is being suggested to include indication of recommendations or relevant questions in the scope of initial WG report, in addition to the list of issues. WG members to share their feedback on the proposed scope. WG Members not on the call on 20160421 2 Staff to start the initial report for the WG SH Please feel free to suggest any edits to the summary. Call recording and summary is available at IDNGWG wiki page: https://community.icann.org/display/IDN/IDN+Implementation+Guidelines. Regards, Sarmad From: idngwg-bounces(a)icann.org <mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Thursday, April 21, 2016 3:49 PM To: idngwg(a)icann.org <mailto:idngwg@icann.org> Subject: [Idngwg] Agenda for meeting on 20160421 Dear All, Here is a tentative agenda for the meeting today: 1. review feedback from community from Marrakech meeting 2. consider next steps and scope of initial/interim report 3. timeframe for 2. Regards, Sarmad

1 0

//current recommendation 2
by Dillon, Chris May 6, 2016

May 6, 2016

Dear colleagues, Here's a draft of what I was saying during yesterday's meeting, as promised. The first paragraph is the existing text; the second a suggested addition. //current recommendation 2: No code point permitted in IDNA2003 but disallowed in IDNA2008 will be accepted for registration regardless of the extent to which such code points appear in names registered prior to the protocol revision. The registrant of a domain that is no longer supported by IDNA2008 should be notified that there may be unanticipated consequences for a user attempting to reach it, and such names should be replaced, held, or deleted at registry initiative. In the case of code points permitted in IDNA2008 but disallowed in IDNA2003, those allowed for use in the Root Zone, typically for scripts added in Unicode versions since 2003, should be allowed in labels at other levels. Code points, however, added to IDNA2008 for other reasons should generally be disallowed in the interests of a good user experience and respecting the Longevity Principle in the Procedure. == The word "respecting" is meant to cause discussion. We may want to consider "in the spirit of" or a weaker form of words. This touches on an interesting issue - the Procedure is binding at the Top Level, but what is its relationship to the other levels? I've attached the v.3 of the document, so you can see this in context. Regards, Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon<http://www.ucl.ac.uk/dis/people/chrisdillon> From: idngwg-bounces(a)icann.org [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: 04 May 2016 19:00 To: idngwg(a)icann.org Subject: [Idngwg] Draft document initial version Dear IDNGWG members, Please find attached the an initial version of the document derived from the issues list and follow our discussion in the previous conf. call (see action items in the email below). I have divided "Terminology and Transition" to two sections and added a place holder for EPP, as raised by the community, totaling to eight items - for the WG to finalize. I have also gone through the earlier version 3.0 of these guidelines and added the recommendations from it in the relevant sections (all nine have been mapped) - shown in italics - as a reference starting point. Finally, I have added the terminology we are identifying in the appendix of this document. This list will grow over time, and we will also need to finalize the definitions for each term. The recommendation section against issue is left blank for the WG to discuss and advise. Please feel free to share your feedback to develop the document further. Looking forward to your call tomorrow (Thursday). Regards, Sarmad

1 0

Draft document initial version
by Sarmad Hussain May 5, 2016

May 5, 2016

Dear IDNGWG members, Please find attached the an initial version of the document derived from the issues list and follow our discussion in the previous conf. call (see action items in the email below). I have divided "Terminology and Transition" to two sections and added a place holder for EPP, as raised by the community, totaling to eight items - for the WG to finalize. I have also gone through the earlier version 3.0 of these guidelines and added the recommendations from it in the relevant sections (all nine have been mapped) - shown in italics - as a reference starting point. Finally, I have added the terminology we are identifying in the appendix of this document. This list will grow over time, and we will also need to finalize the definitions for each term. The recommendation section against issue is left blank for the WG to discuss and advise. Please feel free to share your feedback to develop the document further. Looking forward to your call tomorrow (Thursday). Regards, Sarmad From: idngwg-bounces(a)icann.org [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Friday, April 22, 2016 3:54 PM To: idngwg(a)icann.org Subject: Re: [Idngwg] Agenda for meeting on 20160421 Dear All, Please find attached a summary of the discussion during our meeting on 21 April, with the following action items. S. No. Action Owner 1 WG members should note that it is being suggested to include indication of recommendations or relevant questions in the scope of initial WG report, in addition to the list of issues. WG members to share their feedback on the proposed scope. WG Members not on the call on 20160421 2 Staff to start the initial report for the WG SH Please feel free to suggest any edits to the summary. Call recording and summary is available at IDNGWG wiki page: https://community.icann.org/display/IDN/IDN+Implementation+Guidelines. Regards, Sarmad From: idngwg-bounces(a)icann.org <mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Thursday, April 21, 2016 3:49 PM To: idngwg(a)icann.org <mailto:idngwg@icann.org> Subject: [Idngwg] Agenda for meeting on 20160421 Dear All, Here is a tentative agenda for the meeting today: 1. review feedback from community from Marrakech meeting 2. consider next steps and scope of initial/interim report 3. timeframe for 2. Regards, Sarmad

2 1

IDN Implementation Guidelines WG meeting - alternate Thursdays 11am UTC
by Sarmad Hussain May 5, 2016

May 5, 2016

Adobe Connect - IDN Meeting room: How to connect: 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: https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=1064158692&num=1-719-… Participant Passcode: 1064158692

1 0

Accepted: IDN Implementation Guidelines WG meeting - alternate Thursdays 11am UTC
by Ram Mohan May 2, 2016

May 2, 2016

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:VTIMEZONE TZID:Eastern Standard Time BEGIN:STANDARD DTSTART:16011104T020000 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZOFFSETFROM:-0400 TZOFFSETTO:-0500 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010311T020000 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZOFFSETFROM:-0500 TZOFFSETTO:-0400 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT ATTENDEE;PARTSTAT=ACCEPTED:mailto:rmohan@afilias.info CLASS:PUBLIC COMMENT:\n CREATED:20160502T175741Z DTEND;TZID="Eastern Standard Time":20160421T170000 DTSTAMP:20160502T175740Z DTSTART;TZID="Eastern Standard Time":20160421T160000 LAST-MODIFIED:20160502T175740Z LOCATION:https://icann.adobeconnect.com/idn/ PRIORITY:5 RRULE:FREQ=WEEKLY;COUNT=9;BYDAY=TH SEQUENCE:0 SUMMARY;LANGUAGE=en-us:Accepted: IDN Implementation Guidelines WG meeting - alternate Thursdays 11am UTC TRANSP:OPAQUE UID:040000008200E00074C5B7101A82E0080000000070EA750B5097D101000000000000000 0100000002016B9B938E75B43B502A5AEC7BDE95E 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 BEGIN:VEVENT DTEND:20160421T120000Z DTSTART:20160421T110000Z LOCATION:https://icann.adobeconnect.com/idn/ RECURRENCE-ID:20160421T110000Z SUMMARY:IDN Implementation Guidelines WG meeting - alternate Thursdays 11am UTC TRANSP:OPAQUE UID:040000008200E00074C5B7101A82E0080000000070EA750B5097D101000000000000000 0100000002016B9B938E75B43B502A5AEC7BDE95E X-MICROSOFT-CDO-BUSYSTATUS:BUSY END:VEVENT BEGIN:VEVENT DTEND:20160428T120000Z DTSTART:20160428T110000Z LOCATION:https://icann.adobeconnect.com/idn/ RECURRENCE-ID:20160428T110000Z SUMMARY:IDN Implementation Guidelines WG meeting - alternate Thursdays 11am UTC TRANSP:OPAQUE UID:040000008200E00074C5B7101A82E0080000000070EA750B5097D101000000000000000 0100000002016B9B938E75B43B502A5AEC7BDE95E X-MICROSOFT-CDO-BUSYSTATUS:BUSY BEGIN:VALARM TRIGGER:-PT15M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR

1 0