<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></head>
<body>
I haven't checked the Board resolution enacting the restrictions, but the
original GAC advice said "The GAC considers that Safeguards should
apply to broad categories of strings. For clarity, this means any
application for a relevant string in the current or future rounds, <u>in
all languages applied for</u>."<br><br>
Alan<br><br>
At 2020-07-15 10:40 AM, Justine Chew wrote:<br>
<blockquote type="cite" class="cite" cite="">Jeff,<br><br>
I understand what you are saying to be what is in that paragraph I
quoted. What I don't quite understand is how that concern has been
mitigated by the adoption of the category 1 restrictions. Do the category
1 restrictions also apply to exact translations of category 1
strings?<br><br>
Thanks,<br><br>
Justine<br>
---<br><br>
<br>
On Wed, 15 Jul 2020 at 22:31, Jeff Neuman
<<a href="mailto:jeff@jjnsolutions.com">jeff@jjnsolutions.com</a>>
wrote:<br>
<dl><br>
<dd>Justine,<br><br>
<dd> <br><br>
<dd>The short answer is that exact translations are allowed to be applied
for now.<br><br>
<dd> <br><br>
<dd>Longer Answer is that the principal concern initially expressed by
the regulated TLDs was that someone would apply for an exact translation
of an existing regulated string but not apply the restrictions that are
currently in the existing TLD. Before we discussed/recommended the
adoption of the category 1 restrictions, this was a true concern.
Now that we are recommending the adoption of the category 1 restrictions,
that concern (although not totally gone) has been mitigated in the minds
of many. So there was no need to establish a new class of
objections for the existing regulated TLD registry.<br><br>
<dd> <br><br>
<dd>Hope that makes sense.<br><br>
<dd> <br><br>
<dd><img src="cid:.0" width="300" height="3" alt="[]"><br><br>
<dd> <br><br>
<dd><img src="cid:.1" width="219" height="123" alt="[]"><br><br>
<dd>Jeffrey J. Neuman<br><br>
<dd>Founder & CEO<br><br>
<dd>JJN Solutions, LLC<br><br>
<dd>p: +1.202.549.5079<br><br>
<dd>E:
<a href="mailto:jeff@jjnsolutions.com">jeff@jjnsolutions.com</a><br><br>
<dd><a href="http://jjnsolutions.com/" eudora="autourl">
http://jjnsolutions.com</a><br><br>
<dd> <br><br>
<dd> <br><br>
<dd>From:</b> Gnso-newgtld-wg
<<a href="mailto:gnso-newgtld-wg-bounces@icann.org">
gnso-newgtld-wg-bounces@icann.org</a>> On Behalf Of </b>Justine
Chew<br>
<dd>Sent:</b> Tuesday, July 14, 2020 8:30 PM<br>
<dd>To:</b>
<a href="mailto:gnso-newgtld-wg@icann.org">gnso-newgtld-wg@icann.org</a>
<br>
<dd>Subject:</b> Re: [Gnso-newgtld-wg] Reminder: Deadline Wed 15 July -
"Can't Live With" Review of Package 7 and Final Check on
Revised Package 6<br><br>
<dd> <br><br>
<dd>Jeff, Cheryl,<br><br>
<dd>I would like to seek clarification on one paragraph under part c. of
Objections<br>
<dl><br>
<dd>c. New issues raised in deliberations since publication of the
Initial Report, if applicable.<br><br>
<dd>The Working Group discussed a proposal that there should be grounds
for a formal objection if an applied-for string is an exact translation
of an existing TLD string that is in a highly regulated sector, and the
applied-for string would not employ the same safeguards as the existing
TLD, subject to the applicant’s governing law. This proposal would
potentially require creating a new type of objection. The rationale for
this proposal is that end-users may be confused and assume that both
strings have the same safeguards in place. A concern was raised that this
proposal could potentially harm competition and discourage the use of
innovative business models. The Working Group determined that because the
Working Group agreed upon Category 1 restrictions for regulated strings,
there is no need for the objection process</u>. <br><br>
</dl><br>
<dd>My question is what happens if there is an application for a string
which is an exact translation of an existing TLD string that is in a
highly regulated sector, i.e. one marked for Category 1 restrictions for
regulated strings - how is such an applied-for string dealt
with?<br><br>
<dd>Thanks,<br>
<dd>Justine<br>
<dd>---<br><br>
<dd> <br><br>
<dd> <br><br>
<dd>On Tue, 14 Jul 2020 at 01:47, Emily Barabas
<<a href="mailto:emily.barabas@icann.org">emily.barabas@icann.org</a>
> wrote:<br>
<dl><br>
<dd>Dear all,<br><br>
<dd> <br><br>
<dd>As a reminder, the deadline for Can’t Live With comments on package
7 and a final check on package 6 is Wednesday 15 July at 23:59 UTC</b>.
Details below.<br><br>
<dd> <br><br>
<dd>Kind regards,<br><br>
<dd>Emily<br><br>
<dd> <br><br>
<dd>From: </b>Emily Barabas
<<a href="mailto:emily.barabas@icann.org">emily.barabas@icann.org</a>
><br>
<dd>Date: </b>Friday, 10 July 2020 at 19:44<br>
<dd>To:
</b>"<a href="mailto:gnso-newgtld-wg@icann.org">
gnso-newgtld-wg@icann.org</a>"
<<a href="mailto:gnso-newgtld-wg@icann.org">
gnso-newgtld-wg@icann.org</a>><br>
<dd>Subject: </b>Deadline Wed 15 July - "Can't Live With"
Review of Package 7 and Final Check on Revised Package 6<br><br>
<dd> <br><br>
<dd>Dear all,<br><br>
<dd> <br><br>
<dd>The following are now available for your review in the
<a href="https://docs.google.com/document/d/1Hh8Wj3IwXvi91Am1k4Zoooct2zmPOmVe1pLmjQLuQuo/edit?usp=sharing%20%5bdocs.google.com%5d">
production document</a>. The deadline </b>for comments is Wednesday 15
July at 23:59 UTC</b>.
<dd>Package 7</b> sections of the Report are now ready for “Can’t
Live Withâ€</b> review (beginning on
<a href="https://docs.google.com/document/d/1Hh8Wj3IwXvi91Am1k4Zoooct2zmPOmVe1pLmjQLuQuo/edit">
page 148</a>):</b> <br>
<dd>· Please limit
comments to items in the revised sections that you absolutely “cannot
live with.†If there is text that you cannot accept, please fill out
the attached form and send it to the WG by email. Please do not provide
your input in any other format.<br><br>
<dd>· Package 7 includes
two report sections: <br><br>
<dd>· 2.5.4 Applicant
Support</u> (last discussed on
<a href="https://community.icann.org/display/NGSPP/2020-06-11+New+gTLD+Subsequent+Procedures+PDP">
11 June</a>) - For this section, please limit “Can’t Live Withâ€
comments to the new text in the section</b>, which is displayed in black.
The text in grey has already gone through “Can’t Live With†review
as part of an earlier package.<br><br>
<dd>· 2.3.2 Registry
Voluntary Commitments (RVCs) / Public Interest Commitments (PICs)</u>
(last discussed on
<a href="https://community.icann.org/display/NGSPP/2020-06-18+New+gTLD+Subsequent+Procedures+PDP">
18 June</a>)<br><br>
<dd>· Comments will be
tracked <a href="https://community.icann.org/x/JDKJBw">here</a>.<br><br>
<dd>
<dd>Package 6</b> revisions of the report, now ready for a final
check</b> (beginning on
<a href="https://docs.google.com/document/d/1Hh8Wj3IwXvi91Am1k4Zoooct2zmPOmVe1pLmjQLuQuo/edit">
page 118</a>): <br>
<dd>· Please limit
feedback to errors in the edits, for example a revision that you believe
does not accurately reflect the outcome of discussions about a “Can’t
Live With†item.<br><br>
<dd>· Please send this
type of feedback to the mailing list. Typo corrections can be sent
directly to staff.<br><br>
<dd>· For package 6
sections, please do not raise new issues, introduce new “Can’t Live
With†items, or re-open deliberations.</u> <br><br>
<dd>· A high-level
summary of the “Can’t Live With†input received is available
<a href="https://community.icann.org/display/NGSPP/g.+Draft+Final+Report">
here</a>. And a detailed log with the outcomes from the WG’s
consideration of that input is available
<a href="https://docs.google.com/spreadsheets/d/1blgQjzh_vR7WQ1utsqBnHDb8_b2DD7IDQu-bcJVsmTQ/edit?usp=sharing">
here</a>.<br><br>
<dd>Kind regards,<br><br>
<dd>Emily<br><br>
<dd> <br><br>
<dd> <br><br>
<dd>Emily Barabas<br><br>
<dd>Policy Manager, GNSO Policy Development Support<br><br>
<dd>Internet Corporation for Assigned Names and Numbers (ICANN)<br><br>
<dd>Phone: +31 (0)6 84507976<br><br>
<dd><a href="http://www.icann.org/">www.icann.org</a><br><br>
<dd> <br><br>
<dd>_______________________________________________<br>
<dd>Gnso-newgtld-wg mailing list<br>
<dd><a href="mailto:Gnso-newgtld-wg@icann.org">
Gnso-newgtld-wg@icann.org</a><br>
<dd>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg" eudora="autourl">
https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</a><br>
<dd>_______________________________________________<br>
<dd>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
(<a href="https://www.icann.org/privacy/policy">
https://www.icann.org/privacy/policy</a>) and the website Terms of
Service
(<a href="https://www.icann.org/privacy/tos">
https://www.icann.org/privacy/tos</a>). 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.<br><br>
</dl>
</dl>Content-Type: image/png; name="image001.png"<br>
Content-Disposition: inline; filename="image001.png"<br>
Content-ID: <17352e5a4654cff311><br>
X-Attachment-Id: 17352e5a4654cff311<br><br>
Content-Type: image/png; name="image004.png"<br>
Content-Disposition: inline; filename="image004.png"<br>
Content-ID: <17352e5a4657745b42><br>
X-Attachment-Id: 17352e5a4657745b42<br><br>
<br>
_______________________________________________<br>
Gnso-newgtld-wg mailing list<br>
Gnso-newgtld-wg@icann.org<br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg" eudora="autourl">
https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</a><br>
_______________________________________________<br>
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
(<a href="https://www.icann.org/privacy/policy" eudora="autourl">
https://www.icann.org/privacy/policy</a>) and the website Terms of
Service
(<a href="https://www.icann.org/privacy/tos" eudora="autourl">
https://www.icann.org/privacy/tos</a>). 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.</blockquote></body>
</html>