Thank you Kal and Edmon.
Based on the discussions so far and the inputs, the updated version of the document is attached for further discussion.
Regards,
Sarmad
From: idngwg-bounces@icann.org [mailto:idngwg-bounces@icann.org]
On Behalf Of Edmon Chung
Sent: Thursday, August 10, 2017 7:44 AM
To: idngwg@icann.org
Subject: Re: [Idngwg] Summary of IDNGWG meeting on 3 August 2017
Hi Everyone,
Suggested rewording of 11 (now 10 it seems) to avoid using "must/should/may" in the second sentence:
=====================================
Any information fundamental to the understanding of a registry's IDN policies that is not published by IANA must be made directly available online by the
registry. Including references to the linguistic and orthographic sources used in establishing IDN policies and tables is useful for implementers to understand the context of such policies. The registry should also encourage its registrars to call attention
to these policies for all IDN registrants. If material is provided both via the IANA Repository of IDN Practices and other channels, the registry must ensure that its substance is concordant across all platforms.
=====================================
Also apologies, am at APIGA (Asia Pacific Internet Governance Academy) this week and most likely will not be able to join the meeting later today.
Edmon
From:
idngwg-bounces@icann.org [mailto:idngwg-bounces@icann.org]
On Behalf Of Feher, Kal via Idngwg
Sent: Thursday, 10 August 2017 09:05 AM
To: idngwg@icann.org
Subject: Re: [Idngwg] Summary of IDNGWG meeting on 3 August 2017
Please see revised section 2.1.5. It is much shorter and hopefully clearer. The only clear obligation is to publish updated registration policies. I'm not aware of any objections to
that particular requirement.
Note that the auto numbering in the doc has experienced a critical failure and the updated section now has "1." in front of it.
I've also left a comment for what was section 2.1.5.e (now auto-numbered: 'b'). Since this section refers to IDNA2008 transition specifically, I think it should be added to 2.1.3.
Kal Feher
Neustar Inc. / Enterprise
Architect
Level 8, 10 Queens Road, Melbourne, Australia VIC 3004
Office +61
3 9866 3710 / kal.feher@neustar.biz / www.neustar.biz[neustar.biz]
Follow Neustar:
Facebook[facebook.com]
LinkedIn[linkedin.com]
Twitter[twitter.com]
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@icann.org>
on behalf of Sarmad Hussain <sarmad.hussain@icann.org>
Date: Thursday, 10 August 2017 at 06:30
To: "idngwg@icann.org" <idngwg@icann.org>
Subject: [EXTERNAL] [Idngwg] Summary of IDNGWG meeting on 3 August 2017
Dear IDNGWG members,
Please find attached the summary of the meeting of the IDNGWG held on 3 August 2017.
Please let me know if you would like to suggest any edits or additions.
Action Items
|
S. No. |
Action Items |
Owner |
|
1 |
Shrink Recommendation 5 without changing the contents |
KF |
|
2 |
Revise the text for Recommendation 7 with a placeholder of number of months for transition, applicable to part (a) |
SH |
|
3 |
Redraft the sentence on references in Recommendation 11 as discussed |
EC |
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