[Idngwg] Summary of Meeting on 16 Feb. 2017

Satish Babu sbabu at ieee.org
Thu Feb 23 02:24:24 UTC 2017


Thanks Edmon. The wording appears fine to me.







satish


On Thu, Feb 23, 2017 at 7:25 AM, Edmon Chung <edmon at 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 at icann.org [mailto:idngwg-bounces at icann.org] *On
> Behalf Of *Tan Tanaka, Dennis
> *Sent:* Wednesday, 22 February 2017 06:15 AM
> *To:* Sarmad Hussain <sarmad.hussain at icann.org>; idngwg at 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 at icann.org> on behalf of Sarmad Hussain <
> sarmad.hussain at icann.org>
> *Date: *Tuesday, February 21, 2017 at 9:38 AM
> *To: *"idngwg at icann.org" <idngwg at 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 at 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
>
>
>
> _______________________________________________
> Idngwg mailing list
> Idngwg at icann.org
> https://mm.icann.org/mailman/listinfo/idngwg
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/idngwg/attachments/20170223/cfc3d9e2/attachment-0001.html>


More information about the Idngwg mailing list