September 2017 - Idngwg - lists.icann.org

Summary of IDNGWG meeting on 14 September 2017
by Pitinan Kooarmornpatana Sept. 20, 2017

Sept. 20, 2017

Dear IDNGWG members, Please find attached the summary of the meeting of the IDNGWG held on 14 September 2017. Please let us know if you would like to suggest any edits or additions. Action Items S. No. Action Items Owner 1 Rephrase the 13(a) and (b) as discussed by the WG DT 2 Create the Implementation Notes Section in the document and move the text as discussed by WG PK The recording and this summary are also posted at the IDNGWG wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines Regards, Pitinan

1 1

Re: [Idngwg] document for discussion during our call today
by Mats Dufberg Sept. 14, 2017

Sept. 14, 2017

Sarmad, No problem. Pitanen helped us through the meeting. Unfortunately we were quite few today. Yours, Mats --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/ From: <idngwg-bounces(a)icann.org> on behalf of Sarmad Hussain <sarmad.hussain(a)icann.org> Date: Thursday 14 September 2017 at 12:31 To: idngwg <idngwg(a)icann.org> Subject: Re: [Idngwg] document for discussion during our call today Dear All, Pitinan will host the call today, open the adobe room and make the document circulated available for your discussion. Due to a presentation at APTLD at the same time, I will not be able to join the call today. I will join after my session is over – if the IDNGWG call is still going on. Sorry to have missed today’s meeting. Regards, Sarmad From: idngwg-bounces(a)icann.org [mailto:idngwg-bounces@icann.org] On Behalf Of Sarmad Hussain Sent: Thursday, September 14, 2017 2:48 PM To: idngwg(a)icann.org Subject: [Idngwg] document for discussion during our call today Dear All, Please find attached the document for our discussion today. The WG had reviewed till recommendation 13 and needs to continue beyond that to finalize the first pass. Regards, Sarmad

1 0

apologies for tonight's meeting 2017-09-14
by Feher, Kal Sept. 14, 2017

Sept. 14, 2017

Unfortunately I have work commitments which will prevent me from joining tonight. Kal Feher Neustar Inc. Level 8, 10 Queens Road, Melbourne, Australia VIC 3004 Office +61 3 9866 3710 / kal.feher(a)team.neustar / www.neustar.biz<http://www.neustar.biz/> Follow Neustar: [http://neunet.neustar.biz/sites/default/files/295/New%20Picture.png] Facebook<http://www.facebook.com/neustarinc> [http://neunet.neustar.biz/sites/default/files/295/New%20Picture%20(1)(1).png] LinkedIn<http://www.linkedin.com/company/5349> [http://neunet.neustar.biz/sites/default/files/295/New%20Picture%20(2).png] Twitter<http://www.twitter.com/neustarinc> ________________________________ The information contained in this e-mail message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this e-mail message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message.

1 0

document for discussion during our call today
by Sarmad Hussain Sept. 14, 2017

Sept. 14, 2017

Dear All, Please find attached the document for our discussion today. The WG had reviewed till recommendation 13 and needs to continue beyond that to finalize the first pass. Regards, Sarmad

1 1

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

Sept. 12, 2017

A gentle reminder for the call on Thursday 14 Sept UTC 11am. Regards, Sarmad (extending IDNGWG meetings till ICANN 60) 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

Re: [Idngwg] Public Comment Response by IDNGWG - last call
by Tan Tanaka, Dennis Sept. 11, 2017

Sept. 11, 2017

I’m good with the redlines. Thank you, Dennis From: <idngwg-bounces(a)icann.org> on behalf of Sarmad Hussain <sarmad.hussain(a)icann.org> Date: Friday, September 8, 2017 at 9:55 AM To: "idngwg(a)icann.org" <idngwg(a)icann.org> Subject: [EXTERNAL] [Idngwg] Public Comment Response by IDNGWG - last call Dear All, Please find attached the updated response to the public comments, as per the discussions of the WG. I am attaching the redline version, which shows the history of the changes. However, please make any changes in the clean version so that these are more clearly visible. I have asked the Public Comment team if the report is Ok to publish in the format attached. I will let you all know their response once I hear back from them. In case the prescribed format is required, I will move the comments in blue to the next section, else this is the final draft version. We will be submit the report for posting on Monday morning pacific time (11 Sept.) after incorporating any final feedback. Thank you for the great effort you are all putting in. Looking forward to any final input on this report. Regards, Sarmad From: Mats Dufberg [mailto:mats.dufberg@iis.se] Sent: Friday, September 08, 2017 1:59 PM To: Sarmad Hussain <sarmad.hussain(a)icann.org>; idngwg <idngwg(a)icann.org>; Feher, Kal <Kalman.Feher(a)team.neustar> Subject: [Ext] Re: Proposed new CL1 and CL2 Analysis My updated proposal is that we give the same reply to both comments, and that we use Kal's text with slight modification and an addition: CL1: A clarification is suggested regarding the use of IDN labels inside a TLD zone for records that are not-authoritative, e.g. the NS and glue records. So a TLD can restrict a Unicode point for registration purposes, but it could exist inside the TLD zone. So “labels inside a zone” should be clarified to mean “labels of authoritative names inside a zone”.    CL2: Add a new guideline: "a TLD can't restrict the codepoints of names inside its zone for which it's not authoritative (such as delegations to sibling zones or glue records names), but should check such labels are syntactically valid U-labels (in RFC7940 sense)".   CL1 and CL2 Analysis: This is a useful observation and the WG agrees that the IDN label the guidelines are currently referring to names being registered under the TLD in question. We plan to clarify the scope of the document to indicate that only the owner-name of the DNS records which are added to the zone file by the registration system are in-scope. Excluded from scope are any glue records and right-hand or target names. We have, however, asked SSAC for advice, and if they have a different opinion we will consider adjusting the Guidelines accordingly. --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/ From: Sarmad Hussain <sarmad.hussain(a)icann.org<mailto:sarmad.hussain@icann.org>> Date: Thursday 7 September 2017 at 21:30 To: Mats Dufberg <mats.dufberg(a)iis.se<mailto:mats.dufberg@iis.se>>, idngwg <idngwg(a)icann.org<mailto:idngwg@icann.org>> Subject: RE: Proposed new CL1 and CL2 Analysis Dear Mats, all, >> CL2 Analysis: The WG has come to the conclusion that that is out of scope of the Guidelines. We have written to SSAC and we may be expecting a response from them in the context, as we discussed briefly today. In case we do get some language from SSAC as requested, and WG does consider to include it, this response may not accommodate that scenario. Regards, Sarmad From: idngwg-bounces(a)icann.org<mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Mats Dufberg Sent: Thursday, September 07, 2017 6:38 PM To: idngwg <idngwg(a)icann.org<mailto:idngwg@icann.org>> Subject: [Idngwg] Proposed new CL1 and CL2 Analysis Current: CL1 Analysis: This is a useful observation and the WG agrees that the IDN label the guidelines are currently referring to are those which are authoritative in the zone. We will clarify this is meant by default and call out any specific reference to non-authoritative data in the guidelines explicitly to ensure there is no ambiguity. Proposed: CL1 Analysis: This is a useful observation and the WG agrees that the IDN label the guidelines are currently referring to names being registered under the TLD in question. We will clarify that this the scope of the document, and that DNS records as such are only in-scope when there is direct connection to the registered name. Current: CL2 Analysis: The WG is currently considering if the guidelines should cover data which is not authoritative for the relevant zone. If the WG considers it relevant after discussions, appropriate text will be added, either as part of the discussion on scope or else as a guideline specific for such data. Proposed: CL2 Analysis: The WG has come to the conclusion that that is out of scope of the Guidelines. --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/[iis.se]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.iis.se_en_&d=DwMGa…>

2 1

Public Comment Response by IDNGWG - last call
by Sarmad Hussain Sept. 8, 2017

Sept. 8, 2017

Dear All, Please find attached the updated response to the public comments, as per the discussions of the WG. I am attaching the redline version, which shows the history of the changes. However, please make any changes in the clean version so that these are more clearly visible. I have asked the Public Comment team if the report is Ok to publish in the format attached. I will let you all know their response once I hear back from them. In case the prescribed format is required, I will move the comments in blue to the next section, else this is the final draft version. We will be submit the report for posting on Monday morning pacific time (11 Sept.) after incorporating any final feedback. Thank you for the great effort you are all putting in. Looking forward to any final input on this report. Regards, Sarmad From: Mats Dufberg [mailto:mats.dufberg@iis.se] Sent: Friday, September 08, 2017 1:59 PM To: Sarmad Hussain <sarmad.hussain(a)icann.org>; idngwg <idngwg(a)icann.org>; Feher, Kal <Kalman.Feher(a)team.neustar> Subject: [Ext] Re: Proposed new CL1 and CL2 Analysis My updated proposal is that we give the same reply to both comments, and that we use Kal's text with slight modification and an addition: CL1: A clarification is suggested regarding the use of IDN labels inside a TLD zone for records that are not-authoritative, e.g. the NS and glue records. So a TLD can restrict a Unicode point for registration purposes, but it could exist inside the TLD zone. So “labels inside a zone” should be clarified to mean “labels of authoritative names inside a zone”.    CL2: Add a new guideline: "a TLD can't restrict the codepoints of names inside its zone for which it's not authoritative (such as delegations to sibling zones or glue records names), but should check such labels are syntactically valid U-labels (in RFC7940 sense)".   CL1 and CL2 Analysis: This is a useful observation and the WG agrees that the IDN label the guidelines are currently referring to names being registered under the TLD in question. We plan to clarify the scope of the document to indicate that only the owner-name of the DNS records which are added to the zone file by the registration system are in-scope. Excluded from scope are any glue records and right-hand or target names. We have, however, asked SSAC for advice, and if they have a different opinion we will consider adjusting the Guidelines accordingly. --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/ From: Sarmad Hussain <sarmad.hussain(a)icann.org<mailto:sarmad.hussain@icann.org>> Date: Thursday 7 September 2017 at 21:30 To: Mats Dufberg <mats.dufberg(a)iis.se<mailto:mats.dufberg@iis.se>>, idngwg <idngwg(a)icann.org<mailto:idngwg@icann.org>> Subject: RE: Proposed new CL1 and CL2 Analysis Dear Mats, all, >> CL2 Analysis: The WG has come to the conclusion that that is out of scope of the Guidelines. We have written to SSAC and we may be expecting a response from them in the context, as we discussed briefly today. In case we do get some language from SSAC as requested, and WG does consider to include it, this response may not accommodate that scenario. Regards, Sarmad From: idngwg-bounces(a)icann.org<mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Mats Dufberg Sent: Thursday, September 07, 2017 6:38 PM To: idngwg <idngwg(a)icann.org<mailto:idngwg@icann.org>> Subject: [Idngwg] Proposed new CL1 and CL2 Analysis Current: CL1 Analysis: This is a useful observation and the WG agrees that the IDN label the guidelines are currently referring to are those which are authoritative in the zone. We will clarify this is meant by default and call out any specific reference to non-authoritative data in the guidelines explicitly to ensure there is no ambiguity. Proposed: CL1 Analysis: This is a useful observation and the WG agrees that the IDN label the guidelines are currently referring to names being registered under the TLD in question. We will clarify that this the scope of the document, and that DNS records as such are only in-scope when there is direct connection to the registered name. Current: CL2 Analysis: The WG is currently considering if the guidelines should cover data which is not authoritative for the relevant zone. If the WG considers it relevant after discussions, appropriate text will be added, either as part of the discussion on scope or else as a guideline specific for such data. Proposed: CL2 Analysis: The WG has come to the conclusion that that is out of scope of the Guidelines. --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/[iis.se]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.iis.se_en_&d=DwMGa…>

1 1

Re: [Idngwg] Public Comment Response by IDNGWG - last call
by Mats Dufberg Sept. 8, 2017

Sept. 8, 2017

For me the final document looks fine. Thank you, Sarmad, for your work! Yours, Mats --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/ From: <idngwg-bounces(a)icann.org> on behalf of Sarmad Hussain <sarmad.hussain(a)icann.org> Date: Friday 8 September 2017 at 15:55 To: idngwg <idngwg(a)icann.org> Subject: [Idngwg] Public Comment Response by IDNGWG - last call Dear All, Please find attached the updated response to the public comments, as per the discussions of the WG. I am attaching the redline version, which shows the history of the changes. However, please make any changes in the clean version so that these are more clearly visible. I have asked the Public Comment team if the report is Ok to publish in the format attached. I will let you all know their response once I hear back from them. In case the prescribed format is required, I will move the comments in blue to the next section, else this is the final draft version. We will be submit the report for posting on Monday morning pacific time (11 Sept.) after incorporating any final feedback. Thank you for the great effort you are all putting in. Looking forward to any final input on this report. Regards, Sarmad From: Mats Dufberg [mailto:mats.dufberg@iis.se] Sent: Friday, September 08, 2017 1:59 PM To: Sarmad Hussain <sarmad.hussain(a)icann.org>; idngwg <idngwg(a)icann.org>; Feher, Kal <Kalman.Feher(a)team.neustar> Subject: [Ext] Re: Proposed new CL1 and CL2 Analysis My updated proposal is that we give the same reply to both comments, and that we use Kal's text with slight modification and an addition: CL1: A clarification is suggested regarding the use of IDN labels inside a TLD zone for records that are not-authoritative, e.g. the NS and glue records. So a TLD can restrict a Unicode point for registration purposes, but it could exist inside the TLD zone. So “labels inside a zone” should be clarified to mean “labels of authoritative names inside a zone”.    CL2: Add a new guideline: "a TLD can't restrict the codepoints of names inside its zone for which it's not authoritative (such as delegations to sibling zones or glue records names), but should check such labels are syntactically valid U-labels (in RFC7940 sense)".   CL1 and CL2 Analysis: This is a useful observation and the WG agrees that the IDN label the guidelines are currently referring to names being registered under the TLD in question. We plan to clarify the scope of the document to indicate that only the owner-name of the DNS records which are added to the zone file by the registration system are in-scope. Excluded from scope are any glue records and right-hand or target names. We have, however, asked SSAC for advice, and if they have a different opinion we will consider adjusting the Guidelines accordingly. --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/ From: Sarmad Hussain <sarmad.hussain(a)icann.org<mailto:sarmad.hussain@icann.org>> Date: Thursday 7 September 2017 at 21:30 To: Mats Dufberg <mats.dufberg(a)iis.se<mailto:mats.dufberg@iis.se>>, idngwg <idngwg(a)icann.org<mailto:idngwg@icann.org>> Subject: RE: Proposed new CL1 and CL2 Analysis Dear Mats, all, >> CL2 Analysis: The WG has come to the conclusion that that is out of scope of the Guidelines. We have written to SSAC and we may be expecting a response from them in the context, as we discussed briefly today. In case we do get some language from SSAC as requested, and WG does consider to include it, this response may not accommodate that scenario. Regards, Sarmad From: idngwg-bounces(a)icann.org<mailto:idngwg-bounces@icann.org> [mailto:idngwg-bounces@icann.org] On Behalf Of Mats Dufberg Sent: Thursday, September 07, 2017 6:38 PM To: idngwg <idngwg(a)icann.org<mailto:idngwg@icann.org>> Subject: [Idngwg] Proposed new CL1 and CL2 Analysis Current: CL1 Analysis: This is a useful observation and the WG agrees that the IDN label the guidelines are currently referring to are those which are authoritative in the zone. We will clarify this is meant by default and call out any specific reference to non-authoritative data in the guidelines explicitly to ensure there is no ambiguity. Proposed: CL1 Analysis: This is a useful observation and the WG agrees that the IDN label the guidelines are currently referring to names being registered under the TLD in question. We will clarify that this the scope of the document, and that DNS records as such are only in-scope when there is direct connection to the registered name. Current: CL2 Analysis: The WG is currently considering if the guidelines should cover data which is not authoritative for the relevant zone. If the WG considers it relevant after discussions, appropriate text will be added, either as part of the discussion on scope or else as a guideline specific for such data. Proposed: CL2 Analysis: The WG has come to the conclusion that that is out of scope of the Guidelines. --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/[iis.se]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.iis.se_en_&d=DwMGa…>

1 0

Proposed new CL1 and CL2 Analysis
by Mats Dufberg Sept. 8, 2017

Sept. 8, 2017

Current: CL1 Analysis: This is a useful observation and the WG agrees that the IDN label the guidelines are currently referring to are those which are authoritative in the zone. We will clarify this is meant by default and call out any specific reference to non-authoritative data in the guidelines explicitly to ensure there is no ambiguity. Proposed: CL1 Analysis: This is a useful observation and the WG agrees that the IDN label the guidelines are currently referring to names being registered under the TLD in question. We will clarify that this the scope of the document, and that DNS records as such are only in-scope when there is direct connection to the registered name. Current: CL2 Analysis: The WG is currently considering if the guidelines should cover data which is not authoritative for the relevant zone. If the WG considers it relevant after discussions, appropriate text will be added, either as part of the discussion on scope or else as a guideline specific for such data. Proposed: CL2 Analysis: The WG has come to the conclusion that that is out of scope of the Guidelines. --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/

2 2

Re: [Idngwg] [EXTERNAL] Proposed new CL1 and CL2 Analysis
by Feher, Kal Sept. 8, 2017

Sept. 8, 2017

I've made a slight change to the text for CL1. CL1 Analysis: This is a useful observation and the WG agrees that the IDN label the guidelines are currently referring to names being registered under the TLD in question. We will clarify the scope of the document to indicate that only the owner-name of the DNS records which are added to the zone file by the registration system are in-scope. Excluded from scope are any glue records and right-hand or target names. Kal Feher Neustar Inc. Level 8, 10 Queens Road, Melbourne, Australia VIC 3004 Office +61 3 9866 3710 / kal.feher(a)team.neustar / www.neustar.biz<http://www.neustar.biz/> Follow Neustar: [http://neunet.neustar.biz/sites/default/files/295/New%20Picture.png] Facebook<http://www.facebook.com/neustarinc> [http://neunet.neustar.biz/sites/default/files/295/New%20Picture%20(1)(1).png] LinkedIn<http://www.linkedin.com/company/5349> [http://neunet.neustar.biz/sites/default/files/295/New%20Picture%20(2).png] Twitter<http://www.twitter.com/neustarinc> ________________________________ The information contained in this e-mail message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this e-mail message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message. From: <idngwg-bounces(a)icann.org<mailto:idngwg-bounces@icann.org>> on behalf of Mats Dufberg <mats.dufberg(a)iis.se<mailto:mats.dufberg@iis.se>> Date: Thursday, 7 September 2017 at 23:38 To: "idngwg(a)icann.org<mailto:idngwg@icann.org>" <idngwg(a)icann.org<mailto:idngwg@icann.org>> Subject: [EXTERNAL] [Idngwg] Proposed new CL1 and CL2 Analysis Current: CL1 Analysis: This is a useful observation and the WG agrees that the IDN label the guidelines are currently referring to are those which are authoritative in the zone. We will clarify this is meant by default and call out any specific reference to non-authoritative data in the guidelines explicitly to ensure there is no ambiguity. Proposed: CL1 Analysis: This is a useful observation and the WG agrees that the IDN label the guidelines are currently referring to names being registered under the TLD in question. We will clarify that this the scope of the document, and that DNS records as such are only in-scope when there is direct connection to the registered name. Current: CL2 Analysis: The WG is currently considering if the guidelines should cover data which is not authoritative for the relevant zone. If the WG considers it relevant after discussions, appropriate text will be added, either as part of the discussion on scope or else as a guideline specific for such data. Proposed: CL2 Analysis: The WG has come to the conclusion that that is out of scope of the Guidelines. --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.iis.se_en_&d=DwQGa…>

3 2