July 2017 - Idngwg - lists.icann.org

IDN Guidelines WG meeting - weekly on Thursdays 11am UTC -18 May onwards till the Guidelines are finalized
by Sarmad Hussain Aug. 1, 2017

Aug. 1, 2017

Hi All, A gentle reminder. We have not been able to hold a call on last two weeks as we do not get sufficient members on the call. Kindly confirm your attendance for this week. Regards, Sarmad IDN Meeting room: How to connect: Link to Adobe Connect: https://participate.icann.org/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

3 2

Request for discussion with SSAC on public comment feedback on IDN Guidelines
by Sarmad Hussain July 27, 2017

July 27, 2017

Dear Patrik, Hope you are doing well. Please find below a query from IDN Guidelines Working Group, for consideration by the SSAC. Regards, Sarmad ========= Dear SSAC colleagues, You may know that a revised draft of IDN Implementation Guidelines recently underwent a Public Comment<https://www.icann.org/public-comments/idn-guidelines-2017-03-03-en>. In a comment<http://mm.icann.org/pipermail/comments-idn-guidelines-03mar17/2017-March/00…> submitted by Hugo Salgado from NIC Chile (.CL), it has been suggested to clarify the difference between "the use of IDN labels inside a TLD zone for records that are not-authoritative, like NS names and glue records." It further suggests that "a TLD can pose rules and restrictions for labels in the second (or third) level, but not downside and 'sibling-side'. So my TLD can restrict a certain unicode point for registration purposes, but it could exist inside the TLD zone as an NS name in a level below the TLD as a glue record, and can exist at another TLD as a delegation, over which we don't have any jurisdiction." "As an example, if I'm the registry of .example TLD and we don't allow U+00E1 LATIN SMALL LETTER A WITH ACUTE, we can't prohibit a record like: allowed.example. IN NS á.allowed.example á.allowed.example. IN A 192.0.2.1 and certainly we can't prohibit a delegation to other TLD: allowed.example. IN NS á.cl" The IDN Guidelines Working Group (IDNGWG) has found the comment significant. IDNGWG would like to get SSAC's opinion on whether records which are "not-authoritative" should also be constrained to comply with IDNA2008 by the IDN Guidelines. If SSAC considers this relevant, IDNGWG would request for assistance from SSAC to suggest appropriate language for such a guideline. We would like to invite relevant SSAC members for a discussion with IDNGWG during one of its weekly calls, held on Thursdays at 11am UTC. IDNGWG can organize a call on a different day/time if suggested schedule is not suitable for SSAC. We look forward to your confirmation. Regards, IDN Guidelines WG ========

1 0

IDN Guidelines WG meeting - weekly on Thursdays 11am UTC -18 May onwards till the Guidelines are finalized
by Sarmad Hussain July 27, 2017

July 27, 2017

A gentle reminder for the meeting today (Thursday 27 July). Regards, Sarmad IDN Meeting room: How to connect: Link to Adobe Connect: https://participate.icann.org/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

2 1

Request for discussion on public comment feedback on IDN Guidelines
by Sarmad Hussain July 27, 2017

July 27, 2017

Hi Steve, As discussed, please forward the following message to SSAC on behalf of IDN Guidelines Working Group (IDNGWG), which is working on revising the IDN Guidelines. Regards, Sarmad ========= Dear SSAC colleagues, You may know that a revised draft of IDN Implementation Guidelines recently underwent a Public Comment<https://www.icann.org/public-comments/idn-guidelines-2017-03-03-en>. In a comment<http://mm.icann.org/pipermail/comments-idn-guidelines-03mar17/2017-March/00…> submitted by Hugo Salgado from NIC Chile (.CL), it has been suggested to clarify the difference between "the use of IDN labels inside a TLD zone for records that are not-authoritative, like NS names and glue records." It further suggests that "a TLD can pose rules and restrictions for labels in the second (or third) level, but not downside and 'sibling-side'. So my TLD can restrict a certain unicode point for registration purposes, but it could exist inside the TLD zone as an NS name in a level below the TLD as a glue record, and can exist at another TLD as a delegation, over which we don't have any jurisdiction." "As an example, if I'm the registry of .example TLD and we don't allow U+00E1 LATIN SMALL LETTER A WITH ACUTE, we can't prohibit a record like: allowed.example. IN NS á.allowed.example á.allowed.example. IN A 192.0.2.1 and certainly we can't prohibit a delegation to other TLD: allowed.example. IN NS á.cl" The IDN Guidelines Working Group (IDNGWG) has found the comment significant. IDNGWG would like to get SSAC's opinion on whether records which are "not-authoritative" should also be constrained to comply with IDNA2008 by the IDN Guidelines. If SSAC considers this relevant, IDNGWG would request for assistance from SSAC to suggest appropriate language for such a guideline. We would like to invite relevant SSAC members for a discussion with IDNGWG during one of its weekly calls, held on Thursdays at 11am UTC. IDNGWG can organize a call on a different day/time if suggested schedule is not suitable for SSAC. We look forward to your confirmation. Regards, IDN Guidelines WG ========

1 0

Re: [Idngwg] Text for email to SSAC
by Tan Tanaka, Dennis July 27, 2017

July 27, 2017

I’m fine with the proposed text. Thanks, Sarmad. -Dennis From: <idngwg-bounces(a)icann.org> on behalf of Sarmad Hussain <sarmad.hussain(a)icann.org> Date: Monday, July 24, 2017 at 2:49 PM To: "idngwg(a)icann.org" <idngwg(a)icann.org> Subject: [EXTERNAL] [Idngwg] Text for email to SSAC Dear IDNGWG members, Following our discussion, here is a draft email to be sent to invite SSAC members to a discussion on “non-authoritative” records in a TLD zone. Please feel free to make any edits. =============== Dear SSAC colleagues, You may know that a revised draft of IDN Implementation Guidelines recently underwent a Public Comment<https://www.icann.org/public-comments/idn-guidelines-2017-03-03-en>. In a comment<http://mm.icann.org/pipermail/comments-idn-guidelines-03mar17/2017-March/00…> submitted by Hugo Salgado from NIC Chile (.CL), it has been suggested to clarify the difference between “the use of IDN labels inside a TLD zone [from] records that are not-authoritative, like NS names and glue records." It further suggests that “a TLD can pose rules and restrictions for labels in the second (or third) level, but not downside and ‘sibling-side’. So my TLD can restrict a certain unicode point for registration purposes, but it could exist inside the TLD zone as an NS name in a level below the TLD as a glue record, and can exist at another TLD as a delegation, over which we don't have any jurisdiction.” “As an example, if I'm the registry of .example TLD and we don't allow U+00E1 LATIN SMALL LETTER A WITH ACUTE, we can't prohibit a record like: allowed.example. IN NS á.allowed.example á.allowed.example. IN A 192.0.2.1 and certainly we can't prohibit a delegation to other TLD: allowed.example. IN NS á.cl” The IDN Guidelines Working Group (IDNGWG) has found the comment significant. IDNGWG would like to get SSAC’s opinion on whether records which are “not-authoritative” should also be constrained to comply with IDNA2008 by the IDN Guidelines. If SSAC considers this relevant, IDNGWG would request for assistance from SSAC to suggest appropriate language for such a guideline. We would like to invite relevant SSAC member to join IDNGWG during one of its weekly call, held on Thursdays at 11am UTC. IDNGWG can organize a call on a different day/time if suggested schedule is not suitable for SSAC. We look forward our to your confirmation. Regards, IDN Guidelines WG members ======== Regards, Sarmad

2 1

Text for email to SSAC
by Sarmad Hussain July 24, 2017

July 24, 2017

Dear IDNGWG members, Following our discussion, here is a draft email to be sent to invite SSAC members to a discussion on "non-authoritative" records in a TLD zone. Please feel free to make any edits. =============== Dear SSAC colleagues, You may know that a revised draft of IDN Implementation Guidelines recently underwent a Public Comment<https://www.icann.org/public-comments/idn-guidelines-2017-03-03-en>. In a comment<http://mm.icann.org/pipermail/comments-idn-guidelines-03mar17/2017-March/00…> submitted by Hugo Salgado from NIC Chile (.CL), it has been suggested to clarify the difference between "the use of IDN labels inside a TLD zone [from] records that are not-authoritative, like NS names and glue records." It further suggests that "a TLD can pose rules and restrictions for labels in the second (or third) level, but not downside and 'sibling-side'. So my TLD can restrict a certain unicode point for registration purposes, but it could exist inside the TLD zone as an NS name in a level below the TLD as a glue record, and can exist at another TLD as a delegation, over which we don't have any jurisdiction." "As an example, if I'm the registry of .example TLD and we don't allow U+00E1 LATIN SMALL LETTER A WITH ACUTE, we can't prohibit a record like: allowed.example. IN NS á.allowed.example á.allowed.example. IN A 192.0.2.1 and certainly we can't prohibit a delegation to other TLD: allowed.example. IN NS á.cl" The IDN Guidelines Working Group (IDNGWG) has found the comment significant. IDNGWG would like to get SSAC's opinion on whether records which are "not-authoritative" should also be constrained to comply with IDNA2008 by the IDN Guidelines. If SSAC considers this relevant, IDNGWG would request for assistance from SSAC to suggest appropriate language for such a guideline. We would like to invite relevant SSAC member to join IDNGWG during one of its weekly call, held on Thursdays at 11am UTC. IDNGWG can organize a call on a different day/time if suggested schedule is not suitable for SSAC. We look forward our to your confirmation. Regards, IDN Guidelines WG members ======== Regards, Sarmad

1 0

IDN Guidelines WG meeting - weekly on Thursdays 11am UTC -18 May onwards till the Guidelines are finalized
by Sarmad Hussain July 24, 2017

July 24, 2017

IDN Meeting room: How to connect: Link to Adobe Connect: https://participate.icann.org/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

Summary of IDNGWG meeting on 13 July 2017 and annotated document
by Sarmad Hussain July 20, 2017

July 20, 2017

Dear IDNGWG members, Please find attached the summary of the meeting of the IDNGWG held on 13 July 2017. Updated version of the guidelines document is also attached, based on the discussion last week. Please let me know if you would like to suggest any edits or additions. Action Items S. No. Action Items Owner 1 Set up a meeting with SSAC on whether scope of IDN Guidelines should include other data beyond the registered domain names SH 2 In Recommendation 4, suggest alternate to "both" to make clearer MD The recording and this summary are also posted at the IDNGWG wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines. Regards, Sarmad

1 0

Excuse for today
by Mats Dufberg July 20, 2017

July 20, 2017

Friends, I'm sorry, I am travelling and won't be able to make it to today's meeting. Mats --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899<tel:+46%2073%20065%203899> https://www.iis.se/en/<http://www.iis.se/en>

1 0

IDN Guidelines WG meeting - weekly on Thursdays 11am UTC -18 May onwards till the Guidelines are finalized
by Sarmad Hussain July 20, 2017

July 20, 2017

A gentle reminder for today's meeting. Regards, Sarmad IDN Meeting room: How to connect: Link to Adobe Connect: https://participate.icann.org/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

2 1