<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Dear Mike,<br>
<br>
the discussion was a brief one, on the ISOC policy mailing list. A
question asked was "should PIR comment", and the response was that a
Registry usually does not comment on another Registry's Registry
agreement. Andrew Sullivan directed the discussion to go to the
ICANN Public Comment.<br>
Kindest regards,<br>
<br>
Olivier<br>
<br>
<div class="moz-cite-prefix">On 20/04/2023 20:56, mike palage.com
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CY4PR13MB1029D02FC3C077445826D16DA1639@CY4PR13MB1029.namprd13.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}span.EmailStyle21
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}div.WordSection1
{page:WordSection1;}</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hello Olivier,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Can you provide a public reference to the
thread or email list? I am a sucker for subscribing to a good
mailing list.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">That being said I would agree with John’s
statement. As someone who has consulted with many registry
operators over the last two decades, the language in the .COM
and the now proposed .NET registry agreement is not
inconsistent with standards provisions across the industry.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Sadly, ICANN only requires Verisign to post
its Registry/Registrar agreements. However, I was able to
quickly find this legal provision from EURid in connection
with .EU registrations, see
<a
href="https://eurid.eu/d/7556497/Terms_and_Conditions_EN.pdf"
moz-do-not-send="true" class="moz-txt-link-freetext">https://eurid.eu/d/7556497/Terms_and_Conditions_EN.pdf</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Section 6.4 - <span
style="background:yellow;mso-highlight:yellow">
The Registry shall be entitled to immediately suspend or
cancel the Domain<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="background:yellow;mso-highlight:yellow">Name when the
Registrant is in breach of the Rules.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Section 3. OBLIGATIONS OF THE REGISTRANT<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Throughout the Term, the Registrant has the
following obligations:<o:p></o:p></p>
<p class="MsoNormal">1. As referred to in the Registration
Policy, to keep its contact information accurate, complete,
and up-to-date, both (i) with the Registrar with whom the
Registrant has entered into an Agreement and (ii) with the
Registry (via the Registrar). Moreover, the Registrant
represents and warrants that any email address communicated to
the Registry shall be a functioning e-mail<o:p></o:p></p>
<p class="MsoNormal">address;<o:p></o:p></p>
<p class="MsoNormal">2. To use the Domain Name in such a way
that does not violate any third-party rights, applicable laws,
or regulations, including discrimination on the basis of race,
language, sex, religion, or political view;<o:p></o:p></p>
<p class="MsoNormal">3. Not to use the Domain Name (i) in bad
faith or (ii) for <span
style="background:yellow;mso-highlight:yellow">
any unlawful purpose</span>.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Section 4. REPRESENTATIONS AND WARRANTIES
OF THE REGISTRANT<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The Registrant represents and warrants
that:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">1. it meets the Eligibility Criteria, and
it shall inform the Registry when it ceases to meet such
conditions via its Registrar;<o:p></o:p></p>
<p class="MsoNormal">2. all information provided to the Registry
during the Domain Name registration process is true, complete,
and accurate;<o:p></o:p></p>
<p class="MsoNormal">3. the Domain Name registration is made in
good faith, <span
style="background:yellow;mso-highlight:yellow">
for a lawful purpose</span>, and does not infringe the
rights of any third party;<o:p></o:p></p>
<p class="MsoNormal">4. the Domain Name is not contrary to
public policy or morality (e.g. is not obscene or offensive),
and is not unlawful;<o:p></o:p></p>
<p class="MsoNormal">5. throughout the Term, it shall abide by
these Terms and Conditions and any and all applicable Rules.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Therefore while the Verisign lawyers were a
bit verbose our friends at EURid were much more succinct.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Net Net – I personally am not losing any
sleep over the proposed mark-up to the RRA. That being said
there are A LOT of other provisions in the existing/proposed
.NET agreement that are giving me angst, so please tune in
next Wednesday when Bill and I share our initial assessment
and concerns. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Michael<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> CPWG
<a class="moz-txt-link-rfc2396E" href="mailto:cpwg-bounces@icann.org"><cpwg-bounces@icann.org></a> <b>On Behalf Of </b>
Olivier MJ Crépin-Leblond via CPWG<br>
<b>Sent:</b> Thursday, April 20, 2023 3:28 PM<br>
<b>To:</b> Evan Leibovitch <a class="moz-txt-link-rfc2396E" href="mailto:evan@telly.org"><evan@telly.org></a>; CPWG
<a class="moz-txt-link-rfc2396E" href="mailto:cpwg@icann.org"><cpwg@icann.org></a><br>
<b>Subject:</b> Re: [CPWG] Something of actual importance
to end-users<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Forgot the
reference:<br>
<a
href="https://itp.cdn.icann.org/en/files/registry-agreements/com/com-amend-3-pdf-27mar20-en.pdf"
moz-do-not-send="true" class="moz-txt-link-freetext">https://itp.cdn.icann.org/en/files/registry-agreements/com/com-amend-3-pdf-27mar20-en.pdf</a><br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal">On 20/04/2023 20:26, Olivier MJ
Crépin-Leblond wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-bottom:12.0pt">Worth
noting: John Levine points out on another mailing list that
the changes are the same as those already integrated in the
.COM Registry Agreement 3 years ago and that did not cause
as many ripples back then.<br>
<br>
He also mentions that governments seize gTLD domains all the
time when they get a suitable
<br>
court order. But of course I guess this is all in the
details.<br>
<br>
Kindest regards,<br>
<br>
Olivier<br>
<br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal">On 20/04/2023 17:12, Evan Leibovitch
via CPWG wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span
style="font-family:"Tahoma",sans-serif;color:#0B5394"><a
href="https://freespeech.com/2023/04/19/red-alert-icann-and-verisign-proposal-would-allow-any-government-in-the-world-to-seize-domain-names/"
moz-do-not-send="true"
class="moz-txt-link-freetext">https://freespeech.com/2023/04/19/red-alert-icann-and-verisign-proposal-would-allow-any-government-in-the-world-to-seize-domain-names/</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Tahoma",sans-serif;color:#0B5394"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Tahoma",sans-serif;color:#0B5394">Let's
briefly put aside the boasting about ALAC's
incremental involvement in the trivial agendas set
by ICANN's vested interests. Here's a real example
of an issue that can negatively affect end-users.
The aims of the proposed modification may be
laudable, but there's too much room for
arbitrariness and too much potential to curb
political speech unwanted by a government.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Tahoma",sans-serif;color:#0B5394"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Tahoma",sans-serif;color:#0B5394">BTW
... Why was this not already flagged by ALAC as
cause for concern? Why did I have to find out about
this in the media rather than from the inside. Was
ALAC intending to ignore it?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Tahoma",sans-serif;color:#0B5394"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Tahoma",sans-serif;color:#0B5394">This
is EXACTLY what I'm talking about. ALAC is obsessed
with the trivial and the self-absorbed, but asleep
during the issues that actually affect the
constituency we're supposed to serve.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Tahoma",sans-serif;color:#0B5394"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Tahoma",sans-serif;color:#0B5394">Does
ALAC have what it takes to fight for the public
interest on something that actually matters?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Tahoma",sans-serif;color:#0B5394">Is
it capable of balancing the various intertwining
issues? If the CPWG meets on this issue I'll be
there.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Tahoma",sans-serif;color:#0B5394"><br
clear="all">
<o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Evan Leibovitch, <span
style="font-size:9.5pt">Toronto Canada</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:9.5pt">@evanleibovitch /
@el56</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>CPWG mailing list<o:p></o:p></pre>
<pre><a href="mailto:CPWG@icann.org" moz-do-not-send="true" class="moz-txt-link-freetext">CPWG@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/cpwg" moz-do-not-send="true" class="moz-txt-link-freetext">https://mm.icann.org/mailman/listinfo/cpwg</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>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" moz-do-not-send="true" class="moz-txt-link-freetext">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" moz-do-not-send="true" class="moz-txt-link-freetext">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.<o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>