Re: [Idngwg] Summary of Meeting on 16 Feb. 2017
Dear All, My comments and proposed edits are enclosed. Thanks, Dennis From: <idngwg-bounces@icann.org> on behalf of Sarmad Hussain <sarmad.hussain@icann.org> Date: Tuesday, February 21, 2017 at 9:38 AM To: "idngwg@icann.org" <idngwg@icann.org> Subject: [EXTERNAL] Re: [Idngwg] Summary of Meeting on 16 Feb. 2017 Dear All, A gentle reminder on Action Item 2 below. You are all requested to please review the report attached, based on the most recent call. I have done an initial pass and identified some items to discuss. I have also tried to add some definitions from various sources and added some terms (but have not deleted any yet). I have also marked the use of "will" to discuss how we want to address these instances. Please let us know your feedback. We aim to finalize this report (with some more changes noted in AIs below) in the next call to circulate to the community for discussion during ICANN 58. regards, Sarmad ________________________________ From: Sarmad Hussain Sent: Friday, February 17, 2017 1:14 AM To: idngwg@icann.org Subject: Summary of Meeting on 16 Feb. 2017 Dear All, Please find attached the summary of the meeting of the WG on 16 Feb. Please let me know if there are any changes or suggestions. The meeting has the following AIs: S. No. Action Items Owner 1 Update recommendation on automatic activation of labels in Section 2.6.based on the discussion in the call. EC 2 Review the entire document by next call for any suggestions and feedback on the text All WG members 3 Update the glossary and fill in the definitions MD (and SH) The next meeting is scheduled for Thursday 23 Feb. 2017 11am UTC. We will continue following a weekly meeting schedule. The attached notes of the meeting and the recording of the meeting are available at the IDNGWG wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_display_IDN_IDN-26-2343-3BImplementation-26-2343-3BGuidelines&d=DgMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=iHyLVWg5XYYYMyRqhLrWLRT-0Iuh0o5-T_cl8G4x7nY&s=_HPo9va0P1o27gRKBycMzrAZTgn8xXAy86zJg9CEjjI&e=>. Regards, Sarmad
Hi Everyone, Please find below a rough draft on the IDN Variant Labels activation section. It is a bit worded, but hopefully captures the many considerations that should be taken into consideration. Due to travel shuffling, I may only be able to join the first half of today's meeting (will try to stay on as long as possible). Edmon =================== 2.6 IDN Variant Labels ... 13. Only IDN Variant Labels with a disposition of "allocatable" may be included in the DNS. IDN Variant Labels must only be delegated into the DNS ("activated") as requested by the registrant (or corresponding registrar), except in rare cases where a registry-side approach is explicitly expressed in the IDN policies for a particular language/script. In such cases, the registry must carefully take into consideration the security and stability impacts: 1. as advised in the relevant documents from SSAC (https://www.icann.org/groups/ssac/documents); 2. different user experience perspectives as explained in the document "Examining the User Experience Implications of Active Variant TLDs" (https://www.icann.org/en/system/files/files/active-ux-21mar13-en.pdf); 3. the IDN Variant Issues Project: Final Integrated Issues Report (https://www.icann.org/en/topics/idn/idn-vip-integrated-issues-final-clean-20...); 4. the IDN policies and LGRs adopted by the relevant respective language communities; as well as 5. the evidenced operational experiences from such communities, before implementing any IDN policy that includes registry-side activation of IDN Variant Labels. For example, the Chinese Domain Name Consortium (http://www.cdnc.org/), the related informational RFC on preferred variants relevant to the Han script (RFC3743: https://www.ietf.org/rfc/rfc3743.txt) and the Report on Chinese Variants in Internationalized Top-Level Domains (https://archive.icann.org/en/topics/new-gtlds/chinese-vip-issues-report-03oc...). From: idngwg-bounces@icann.org [mailto:idngwg-bounces@icann.org] On Behalf Of Tan Tanaka, Dennis Sent: Wednesday, 22 February 2017 06:15 AM To: Sarmad Hussain <sarmad.hussain@icann.org>; idngwg@icann.org Subject: Re: [Idngwg] Summary of Meeting on 16 Feb. 2017 Dear All, My comments and proposed edits are enclosed. Thanks, Dennis From: <idngwg-bounces@icann.org <mailto:idngwg-bounces@icann.org> > on behalf of Sarmad Hussain <sarmad.hussain@icann.org <mailto:sarmad.hussain@icann.org> > Date: Tuesday, February 21, 2017 at 9:38 AM To: "idngwg@icann.org <mailto:idngwg@icann.org> " <idngwg@icann.org <mailto:idngwg@icann.org> > Subject: [EXTERNAL] Re: [Idngwg] Summary of Meeting on 16 Feb. 2017 Dear All, A gentle reminder on Action Item 2 below. You are all requested to please review the report attached, based on the most recent call. I have done an initial pass and identified some items to discuss. I have also tried to add some definitions from various sources and added some terms (but have not deleted any yet). I have also marked the use of "will" to discuss how we want to address these instances. Please let us know your feedback. We aim to finalize this report (with some more changes noted in AIs below) in the next call to circulate to the community for discussion during ICANN 58. regards, Sarmad _____ From: Sarmad Hussain Sent: Friday, February 17, 2017 1:14 AM To: idngwg@icann.org <mailto:idngwg@icann.org> Subject: Summary of Meeting on 16 Feb. 2017 Dear All, Please find attached the summary of the meeting of the WG on 16 Feb. Please let me know if there are any changes or suggestions. The meeting has the following AIs: S. No. Action Items Owner 1 Update recommendation on automatic activation of labels in Section 2.6.based on the discussion in the call. EC 2 Review the entire document by next call for any suggestions and feedback on the text All WG members 3 Update the glossary and fill in the definitions MD (and SH) The next meeting is scheduled for Thursday 23 Feb. 2017 11am UTC. We will continue following a weekly meeting schedule. The attached notes of the meeting and the recording of the meeting are available at the IDNGWG wiki page at <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_dis...> https://community.icann.org/display/IDN/IDN+Implementation+Guidelines[community.icann.org]. Regards, Sarmad
Thanks Edmon. The wording appears fine to me. satish On Thu, Feb 23, 2017 at 7:25 AM, Edmon Chung <edmon@registry.asia> wrote:
Hi Everyone,
Please find below a rough draft on the IDN Variant Labels activation section.
It is a bit worded, but hopefully captures the many considerations that should be taken into consideration.
Due to travel shuffling, I may only be able to join the first half of today's meeting (will try to stay on as long as possible).
Edmon
===================
2.6 IDN Variant Labels
...
13.
Only IDN Variant Labels with a disposition of "allocatable" may be included in the DNS. IDN Variant Labels must only be delegated into the DNS ("activated") as requested by the registrant (or corresponding registrar), except in rare cases where a registry-side approach is explicitly expressed in the IDN policies for a particular language/script.
In such cases, the registry must carefully take into consideration the security and stability impacts: 1. as advised in the relevant documents from SSAC (https://www.icann.org/groups/ssac/documents); 2. different user experience perspectives as explained in the document "Examining the User Experience Implications of Active Variant TLDs" ( https://www.icann.org/en/system/files/files/active-ux-21mar13-en.pdf); 3. the IDN Variant Issues Project: Final Integrated Issues Report ( https://www.icann.org/en/topics/idn/idn-vip-integrated- issues-final-clean-20feb12-en.pdf); 4. the IDN policies and LGRs adopted by the relevant respective language communities; as well as 5. the evidenced operational experiences from such communities, before implementing any IDN policy that includes registry-side activation of IDN Variant Labels.
For example, the Chinese Domain Name Consortium (http://www.cdnc.org/), the related informational RFC on preferred variants relevant to the Han script (RFC3743: https://www.ietf.org/rfc/rfc3743.txt) and the Report on Chinese Variants in Internationalized Top-Level Domains ( https://archive.icann.org/en/topics/new-gtlds/chinese-vip- issues-report-03oct11-en.pdf).
*From:* idngwg-bounces@icann.org [mailto:idngwg-bounces@icann.org] *On Behalf Of *Tan Tanaka, Dennis *Sent:* Wednesday, 22 February 2017 06:15 AM *To:* Sarmad Hussain <sarmad.hussain@icann.org>; idngwg@icann.org *Subject:* Re: [Idngwg] Summary of Meeting on 16 Feb. 2017
Dear All,
My comments and proposed edits are enclosed.
Thanks,
Dennis
*From: *<idngwg-bounces@icann.org> on behalf of Sarmad Hussain < sarmad.hussain@icann.org> *Date: *Tuesday, February 21, 2017 at 9:38 AM *To: *"idngwg@icann.org" <idngwg@icann.org> *Subject: *[EXTERNAL] Re: [Idngwg] Summary of Meeting on 16 Feb. 2017
Dear All,
A gentle reminder on Action Item 2 below. You are all requested to please review the report attached, based on the most recent call. I have done an initial pass and identified some items to discuss. I have also tried to add some definitions from various sources and added some terms (but have not deleted any yet). I have also marked the use of "will" to discuss how we want to address these instances.
Please let us know your feedback. We aim to finalize this report (with some more changes noted in AIs below) in the next call to circulate to the community for discussion during ICANN 58.
regards, Sarmad
------------------------------
*From:* Sarmad Hussain *Sent:* Friday, February 17, 2017 1:14 AM *To:* idngwg@icann.org *Subject:* Summary of Meeting on 16 Feb. 2017
Dear All,
Please find attached the summary of the meeting of the WG on 16 Feb. Please let me know if there are any changes or suggestions.
The meeting has the following AIs:
*S. No.*
*Action Items *
*Owner*
1
*Update recommendation on automatic activation of labels in Section 2.6.based on the discussion in the call.*
EC
2
*Review the entire document by next call for any suggestions and feedback on the text*
All WG members
3
*Update the glossary and fill in the definitions*
MD (and SH)
The next meeting is scheduled for Thursday 23 Feb. 2017 11am UTC. We will continue following a weekly meeting schedule.
The attached notes of the meeting and the recording of the meeting are available at the IDNGWG wiki page at https://community.icann. org/display/IDN/IDN+Implementation+Guidelines[community.icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_dis...> .
Regards, Sarmad
_______________________________________________ Idngwg mailing list Idngwg@icann.org https://mm.icann.org/mailman/listinfo/idngwg
Thanks Edmon, Dennis and Satish for your feedback. Please find attached an updated draft incorporating this feedback. We will use this version for the discussion during the call today. regards, Sarmad ________________________________ From: idngwg-bounces@icann.org <idngwg-bounces@icann.org> on behalf of Edmon Chung <edmon@registry.asia> Sent: Thursday, February 23, 2017 6:55 AM To: idngwg@icann.org Subject: Re: [Idngwg] Summary of Meeting on 16 Feb. 2017 Hi Everyone, Please find below a rough draft on the IDN Variant Labels activation section. It is a bit worded, but hopefully captures the many considerations that should be taken into consideration. Due to travel shuffling, I may only be able to join the first half of today's meeting (will try to stay on as long as possible). Edmon =================== 2.6 IDN Variant Labels ... 13. Only IDN Variant Labels with a disposition of "allocatable" may be included in the DNS. IDN Variant Labels must only be delegated into the DNS ("activated") as requested by the registrant (or corresponding registrar), except in rare cases where a registry-side approach is explicitly expressed in the IDN policies for a particular language/script. In such cases, the registry must carefully take into consideration the security and stability impacts: 1. as advised in the relevant documents from SSAC (https://www.icann.org/groups/ssac/documents[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_groups_ssac_documents&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=zE9YtM7BD8QUqnMUAfSZHPfhc5PfeVcB66j2qSqiXhM&s=mlj9xXqu8i95T1vHzEtrO9gvMnPCjQWn3A9ltyq7gjM&e=>); 2. different user experience perspectives as explained in the document "Examining the User Experience Implications of Active Variant TLDs" (https://www.icann.org/en/system/files/files/active-ux-21mar13-en.pdf[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system_files_files_active-2Dux-2D21mar13-2Den.pdf&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=zE9YtM7BD8QUqnMUAfSZHPfhc5PfeVcB66j2qSqiXhM&s=Z_Z1Jm-nWcnLI0mnMeE8MKKsYuD4DAAvlM4arj7v2Kc&e=>); 3. the IDN Variant Issues Project: Final Integrated Issues Report (https://www.icann.org/en/topics/idn/idn-vip-integrated-issues-final-clean-20feb12-en.pdf[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_topics_idn_idn-2Dvip-2Dintegrated-2Dissues-2Dfinal-2Dclean-2D20feb12-2Den.pdf&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=zE9YtM7BD8QUqnMUAfSZHPfhc5PfeVcB66j2qSqiXhM&s=EcgyWZ7Mqnzir_iy-Q5pbtcrI9HUD19m4s0DoKD_PK8&e=>); 4. the IDN policies and LGRs adopted by the relevant respective language communities; as well as 5. the evidenced operational experiences from such communities, before implementing any IDN policy that includes registry-side activation of IDN Variant Labels. For example, the Chinese Domain Name Consortium (http://www.cdnc.org/[cdnc.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.cdnc.org_&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=zE9YtM7BD8QUqnMUAfSZHPfhc5PfeVcB66j2qSqiXhM&s=xpZeUHdMcD_24eQFLAItbhltBwNIPjm3ZW0J3XSXk34&e=>), the related informational RFC on preferred variants relevant to the Han script (RFC3743: https://www.ietf.org/rfc/rfc3743.txt[ietf.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_rfc_rfc3743.txt&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=zE9YtM7BD8QUqnMUAfSZHPfhc5PfeVcB66j2qSqiXhM&s=HNoooPVkq2g3_OY2Y9Hy8Qdn-rhEiVTEixeHeEtVQcc&e=>) and the Report on Chinese Variants in Internationalized Top-Level Domains (https://archive.icann.org/en/topics/new-gtlds/chinese-vip-issues-report-03oct11-en.pdf[archive.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__archive.icann.org_en_topics_new-2Dgtlds_chinese-2Dvip-2Dissues-2Dreport-2D03oct11-2Den.pdf&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=zE9YtM7BD8QUqnMUAfSZHPfhc5PfeVcB66j2qSqiXhM&s=Zq6mIQNa00yoMDVsBkpqmvIyNkmR0v3DVJ9FSqa1X6o&e=>). From: idngwg-bounces@icann.org [mailto:idngwg-bounces@icann.org] On Behalf Of Tan Tanaka, Dennis Sent: Wednesday, 22 February 2017 06:15 AM To: Sarmad Hussain <sarmad.hussain@icann.org>; idngwg@icann.org Subject: Re: [Idngwg] Summary of Meeting on 16 Feb. 2017 Dear All, My comments and proposed edits are enclosed. Thanks, Dennis From: <idngwg-bounces@icann.org<mailto:idngwg-bounces@icann.org>> on behalf of Sarmad Hussain <sarmad.hussain@icann.org<mailto:sarmad.hussain@icann.org>> Date: Tuesday, February 21, 2017 at 9:38 AM To: "idngwg@icann.org<mailto:idngwg@icann.org>" <idngwg@icann.org<mailto:idngwg@icann.org>> Subject: [EXTERNAL] Re: [Idngwg] Summary of Meeting on 16 Feb. 2017 Dear All, A gentle reminder on Action Item 2 below. You are all requested to please review the report attached, based on the most recent call. I have done an initial pass and identified some items to discuss. I have also tried to add some definitions from various sources and added some terms (but have not deleted any yet). I have also marked the use of "will" to discuss how we want to address these instances. Please let us know your feedback. We aim to finalize this report (with some more changes noted in AIs below) in the next call to circulate to the community for discussion during ICANN 58. regards, Sarmad ________________________________ From: Sarmad Hussain Sent: Friday, February 17, 2017 1:14 AM To: idngwg@icann.org<mailto:idngwg@icann.org> Subject: Summary of Meeting on 16 Feb. 2017 Dear All, Please find attached the summary of the meeting of the WG on 16 Feb. Please let me know if there are any changes or suggestions. The meeting has the following AIs: S. No. Action Items Owner 1 Update recommendation on automatic activation of labels in Section 2.6.based on the discussion in the call. EC 2 Review the entire document by next call for any suggestions and feedback on the text All WG members 3 Update the glossary and fill in the definitions MD (and SH) The next meeting is scheduled for Thursday 23 Feb. 2017 11am UTC. We will continue following a weekly meeting schedule. The attached notes of the meeting and the recording of the meeting are available at the IDNGWG wiki page at https://community.icann.org/display/IDN/IDN+Implementation+Guidelines[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_display_IDN_IDN-26-2343-3BImplementation-26-2343-3BGuidelines&d=DgMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=iHyLVWg5XYYYMyRqhLrWLRT-0Iuh0o5-T_cl8G4x7nY&s=_HPo9va0P1o27gRKBycMzrAZTgn8xXAy86zJg9CEjjI&e=>. Regards, Sarmad
participants (4)
-
Edmon Chung -
Sarmad Hussain -
Satish Babu -
Tan Tanaka, Dennis