Dear Bill, Thanks for your comment. For purposes of our *presen*t review of the AGB draft text, we are not getting into the theory of the RZ-LGR. In this respect, applicants will be guided by the RZ-LGR as the RZ-LGR has been designated as the authoritative source to determine what is allocatable and what is blocked. Instead, we are merely pointing out to the ICANN org SubPro IRT Team that where they make reference to *variants being applied-for*, it should indicated that it is "allocatable variants" and not just "variants". I should note that the latter approach appears consistently elsewhere in the draft text that I have viewed, just not here in Topic 4 TLD Types Sections 1.2.2.6 and 1.2.2.7. Kind regards, Justine On Tue, 21 Jan 2025 at 02:18, Bill Jouris <b_jouris@yahoo.com> wrote:
Hi Justine,
I'm not sure if this constitutes a suggestion, or merely a comment. Regarding the first point (on 1.2.2.6 and 1.2.2.7).
Allocatable variants are those which are used interchangeably (to at least some extent, and in some languages using the script). For the Latin script, there are no more than 2. The reason for that being that the Latin Generation Panel had speakers of maybe a half dozen of the hundreds of languages which use that script. Meaning that it was impossible to know what characters were used interchangeably in one or another of those languages. So there are, potentially, a very large number of cases (and for certain several known ones) which should be allocatable variants, but are not so identified.
I'm not sure how, or whether, the next round proposes to address this shortcoming. And the Applicant Guidebook may not be the right place to do something about it. But I persist in noting the elephant in the room.
Bill Jouris
On Friday, January 17, 2025 at 04:36:53 PM PST, Justine Chew via CPWG < cpwg@icann.org> wrote:
All,
At the last CPWG Call on 15 Jan <https://community.icann.org/x/CYABH>, the review team for the Third Proceeding for Proposed Language for Draft Sections of Next Round AGB <https://www.icann.org/en/public-comment/proceeding/third-proceeding-for-prop...> had very briefly presented 5 points which could form an ALAC Comment for this public comment proceeding.
It is our recommendation that the 5 points (found in summary on slide #3 <https://community.icann.org/download/attachments/469860361/20250115v2%20-%20...>) be developed further into a first draft ALAC Comment and presented subsequently for CPWG comment.
In order to take the recommended step, and given that we did not have time to do the same during the 15 Jan call, we are now seeking input for support and/or additional suggestions to our 5 recommended points - which touch on 3 topics of (1) TLD Types, (2) Security and Stability and (3) Community Input and Dispute Resolution.
Please let us have your input *by Monday, 20 Jan at 23:59 UTC*, to allow the review team (who have also agreed to be penholders for the comment) to prepare the first draft of an ALAC Comment in time for consideration at the next CPWG Call on 22 Jan.
*For avoidance of doubt*, the review team shall take no forthcoming input or non-significant objection as a sign of support for us to proceed with drafting an ALAC Comment as mentioned. We would be happy to take questions regarding our recommendations as well, in reply to this thread.
Kind regards,
Avri Doria, Nthabiseng Pule and Justine Chew
_______________________________________________ CPWG mailing list -- cpwg@icann.org To unsubscribe send an email to cpwg-leave@icann.org
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_camp...> Virus-free.www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_camp...> <#m_-8488157803812879355_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>