<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font face="Times New Roman, Times, serif">In the interests
brokering some kind of comprise, I take up Greg's offer to make
a suggestion on beefing up the last sentence of his proposal re:
ICANN monitoring the impact of price increases. <br>
</font></p>
<p><font face="Times New Roman, Times, serif"> I would suggest
retaining </font>the price caps but raising them slightly and
then have a periodic review that could either raise or lower the
caps.<br>
</p>
<p>e.g. price cap raised to 12% (15?) and reviewed after 5 )10?)
years. That would make everybody equally unhappy. Good political
compromise.</p>
<p>My second choice would be Greg's suggestion that ICANN reserve
the right to roll back price increases deemed to be abusive -- but
rolling back price increases would be really controversial if it
ever came to pass.<br>
</p>
<p>In addition, I would limit the statement to .org and add the
comment already put forward by Maureen re: .asia. I have not seen
any strong arguments for retaining price caps on .biz .info. I
think throwing all these thing together in one pot has been
disingenuous. I realize the goal was standardization but the
timing seems to be wrong.<br>
</p>
<p>Marita<br>
</p>
<div class="moz-cite-prefix">On 4/29/2019 7:14 AM, Greg Shatan
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAGQ5VrV-n9PjMFO+g5znW81y07=eddS71BBBZQ8aABudubZBSw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div>
<div>
<div dir="auto">
<div dir="auto">I would be happy, Marita, to beef up the
last line of the comment and make that aspect more
substantial generally! Please send your editorial
suggestions. As for what ICANN should do, one possibility
is that ICANN reserves the right to roll back price
increases, in whole or in part, if the price hikes are
abusive or discriminatory.</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">All, I still hope that there is room for a
comment here. It would be particularly unfortunate if we
fail to comment on the .ORG renewal. Roberto’s email
encapsulates many of the reasons why. I look at ISOC as
almost a sister organization of At-Large. As Roberto points
out, ISOC works to accomplish many goals that it shares with
At-Large. ISOC also supports the IETF and even provides its
corporate “home.” PIR runs on similar principles. PIR is
not a run of the mill commercial registry. In many ways, it
was put into business by ISOC. Yet the essence of the
concerted campaign against .ORG is that PIR can’t be trusted
to abstain from massive price increases, that ISOC could and
possibly would push it to do so, and that ISOC is a
parasitical organization sucking money out of other
non-profits. I feel like we would be throwing ISOC under the
bus if we fail to comment on the .ORG renewal in particular.
[Disclosure: I am the President & Chair of an At Large
Structure that is also an ISOC Chapter, ISOC-NY.]</div>
</div>
<div>
<div>
<div dir="auto"><br>
</div>
<div dir="auto">Originally, my draft dealt only with .org.
We could just go back to that focus. We can leave a
general discussion of price caps to one side if we don’t
expand this to .biz and .info (and .asia doesn’t have
price caps now).</div>
<div dir="auto"><br>
</div>
<div dir="auto">Based on the discussions we had, I aimed to
limit the comment to the concrete issues raised by the
agreement rather than go beyond the agreement to some of
the broader registry issues. But that’s a question of
approach and I’m fine with a broader statement.
Alternatively, we could decide not to comment on .biz and
.info at all, limit the current statement to .org, and put
in a brief UA statement for .asia. But first we would
have to get any drafts, revisions, etc. out on the table
so we can see what we’re dealing with.</div>
</div>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Even asking for an extension is a double-edged
sword, since that keeps the doors open for more of the
cut-and-paste comments that have been filed in opposition to
these renewals.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Best regards,</div>
<div dir="auto"><br>
</div>
<div dir="auto">Greg</div>
<div>
<div>
<div>
<div dir="auto"><br>
</div>
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sat, Apr 27, 2019
at 2:34 AM Marita Moll <<a
href="mailto:mmoll@ca.inter.net" target="_blank"
moz-do-not-send="true">mmoll@ca.inter.net</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p><font face="Times New Roman, Times, serif">I am
reading powerful arguments on both sides of this
issue and then reading Greg's proposed comment
again. In the particular case of .org, and
should we decide to go in the direction that
Greg has mapped, would it be possible to beef up
the last line. It seems like a throw away but it
could be a good bridge between the opposing
points of view. The comment asks that ICANN
"monitor" future price increases and any market
responses to those increases. What should ICANN
do if it decides the increases are unwarranted?</font></p>
<p><font face="Times New Roman, Times, serif">@Christopher
-- eh bien, le poisson est encore vivant !!</font></p>
</div>
<div text="#000000" bgcolor="#FFFFFF">
<p><font face="Times New Roman, Times, serif"><br>
</font></p>
<p><font face="Times New Roman, Times, serif">Marita<br>
</font></p>
<div
class="m_5635567038250828320m_-847023625134173502m_-1825612036884396901m_5693160749745162347moz-cite-prefix">On
4/26/2019 5:41 PM, Greg Shatan wrote:<br>
</div>
<blockquote type="cite">
<div>
<div dir="auto">Justine,</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Thank you for your kind words and
helpful comments.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Unfortunately, the “party” got
rained out. The CPWG decided not to approve
this statement, whether it covers all the
renewals or is limited to .ORG. So nothing is
being sent to the ALAC for their consideration.
I think it’s a good statement, and it would be
made better with your suggestions. I am
considering revising this draft, cutting the
subject back to .ORG and submitting it
individually. Also, circulating it for others
to submit — either individually or with multiple
signatures.</div>
<div dir="auto"><br>
</div>
<div dir="auto">In particular, I am concerned
there are a number of comments being made that
tend to denigrate PIR and ISOC. This is
something I would like to counter. [Full
disclosure: I am the President of ISOC-NY (an
At-Large Structure) and participate here in that
capacity. However, I have not yet asked the
ISOC-NY Board to consider endorsing this
statement, so I am discussing it here in my
individual capacity.]. I honestly think much of
what has been said about PIR and ISOC has been
untrue or exaggerated and fails to to give
credit to ISOC for its mission and unique place
in the internet ecosystem.</div>
<div dir="auto"><br>
</div>
<div dir="auto">I believe that PIR was hoping for
a comment along the lines of our first draft
(which I believe they saw on our site) or our
second draft. I’m not comfortable leaving PIR
and ISOC to be “thrown under the bus” by
ill-informed and prejudicial comments. If ALAC
will not comment (or more precisely, if the CPWG
wont send ALAC a draft comment for their
consideration), then it behooves those who
support this statement to submit it or use it as
a basis for their own comments.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Best regards,</div>
<div dir="auto"><br>
</div>
<div dir="auto">Greg</div>
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Apr
26, 2019 at 6:02 AM Justine Chew <<a
href="mailto:justine.chew@gmail.com"
target="_blank" moz-do-not-send="true">justine.chew@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
<div dir="ltr">
<div class="gmail_default"
style="font-size:small">Thanks to Greg
Shatan for the 24 April draft statement.
<br>
<br>
My comments / suggestion are as
follows:-<br>
<br>
1. I wonder if it might be better to
prepare (and submit) 2 statements
instead of a consolidated one ie. one to
address .BIZ, .ORG and .INFO and another
for .ASIA.. This is because .ASIA had a
"different playing field of no price
caps" to begin with and in this way, any
concerns about price cap removals for
.BIZ, .ORG and .INFO can be addressed
squarely in comparison with .NET and
with reference to the ALAC's 2017
comment. Given that we don't seem to be
offering comments to the inclusion of
some RPMs.<br>
<br>
2. In any case, the draft starts with
"Background" but doesn't indicate where
that backgrounder ends and where the
present comment begins.<br>
<br>
3. Related to the point about
standardizing RAs as being a good
approach, it be useful to draw attention
to the use of Addendums as the
controlled means for handling necessary
variations.<br>
<br>
4. Would it not be incumbent on At-Large
to also support (or least comment on)
regularizing the inclusion of PICs in
these RA renewals (if any)?<br>
<br>
5. As for UA, it's not clear (to me at
least) what we want all ROs to do about
it at this point. Given community
interest on UA has increased further in
recent meetings, actual responsibilities
might be better framed in due course.
So, it may be prudent to tackle the
inclusion of UA into the base Registry
Agreement by amending Specification 6,
or possibly by way of a consensus policy
addition in Specification 1, at a later
date. </div>
<div>
<div dir="ltr"
class="m_5635567038250828320m_-847023625134173502m_-1825612036884396901m_5693160749745162347m_-2259064000804484507gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div><br>
Justine<br>
<div class="gmail_default"
style="font-size:small">(my
apologies for being late to the
"party")</div>
<br>
-----</div>
</div>
</div>
</div>
<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu,
25 Apr 2019 at 04:15, Evin Erdogdu <<a
href="mailto:evin.erdogdu@icann.org"
target="_blank" moz-do-not-send="true">evin.erdogdu@icann.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div
class="m_5635567038250828320m_-847023625134173502m_-1825612036884396901m_5693160749745162347m_-2259064000804484507gmail-m_7765071405837289844WordSection1">
<p class="MsoNormal"><span
style="font-size:10pt;font-family:Arial,sans-serif">Thank
you Greg; this draft ALAC
Statement on the 4 Registry
Agreement Public Comments is
posted to each workspace, for
comment:</span></p>
<p class="MsoNormal"><span
style="font-size:10pt;font-family:Arial,sans-serif"> </span></p>
<p class="MsoNormal"><a
href="https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Proposed+Renewal+of+.biz+Registry+Agreement"
target="_blank"
moz-do-not-send="true"><span>At-Large
Workspace: Proposed Renewal of
.biz Registry Agreement</span></a></p>
<p class="MsoNormal"><a
href="https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Proposed+Renewal+of+.asia+Registry+Agreement"
target="_blank"
moz-do-not-send="true"><span>At-Large
Workspace: Proposed Renewal of
.asia Registry Agreement</span></a></p>
<p class="MsoNormal"><a
href="https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Proposed+Renewal+of+.org+Registry+Agreement"
target="_blank"
moz-do-not-send="true"><span>At-Large
Workspace: Proposed Renewal of
.org Registry Agreement</span></a></p>
<p class="MsoNormal"><a
href="https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Proposed+Renewal+of+.info+Registry+Agreement"
target="_blank"
moz-do-not-send="true"><span>At-Large
Workspace: Proposed Renewal of
.info Registry Agreement</span></a></p>
<p class="MsoNormal"><span
style="font-size:10pt;font-family:Arial,sans-serif"> </span></p>
<p class="MsoNormal"><span
style="font-size:10pt;font-family:Arial,sans-serif">Kind
Regards,</span></p>
<p class="MsoNormal"><span
style="font-size:10pt;font-family:Arial,sans-serif">Evin</span></p>
<p class="MsoNormal"><span
style="font-size:10pt;font-family:Arial,sans-serif"> </span></p>
<div
style="border-right:none;border-bottom:none;border-left:none;border-top:1pt
solid rgb(181,196,223);padding:3pt
0in 0in">
<p class="MsoNormal"><b><span
style="font-size:12pt;color:black">From:
</span></b><span
style="font-size:12pt;color:black">GTLD-WG
<<a
href="mailto:gtld-wg-bounces@atlarge-lists.icann.org"
target="_blank"
moz-do-not-send="true">gtld-wg-bounces@atlarge-lists.icann.org</a>>
on behalf of Greg Shatan <<a
href="mailto:greg@isoc-ny.org" target="_blank" moz-do-not-send="true">greg@isoc-ny.org</a>><br>
<b>Date: </b>Wednesday, April
24, 2019 at 2:44 PM<br>
<b>To: </b>CPWG <<a
href="mailto:cpwg@icann.org"
target="_blank"
moz-do-not-send="true">cpwg@icann.org</a>>,
Evin Erdogdu <<a
href="mailto:evin.erdogdu@icann.org"
target="_blank"
moz-do-not-send="true">evin.erdogdu@icann.org</a>>,
Jonathan Zuck <<a
href="mailto:JZuck@innovatorsnetwork.org"
target="_blank"
moz-do-not-send="true">JZuck@innovatorsnetwork.org</a>><br>
<b>Subject: </b>[GTLD-WG]
[CPWG] Fwd: FW: Draft Comment
on RA Renewals</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><b><span
style="font-family:Arial,sans-serif">Please
see attached.</span></b></p>
</div>
<p class="MsoNormal">-- </p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span>Greg
Shatan</span> </p>
<div>
<p
class="MsoNormal"><a
href="mailto:greg@isoc-ny.org" target="_blank" moz-do-not-send="true"><span>greg@isoc-ny.org</span></a></p>
</div>
<div>
<p
class="MsoNormal"><span>President,
ISOC-NY</span></p>
</div>
<div>
<p
class="MsoNormal"><i><span>"The
Internet is
for everyone"</span></i></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
CPWG mailing list<br>
<a href="mailto:CPWG@icann.org"
target="_blank" moz-do-not-send="true">CPWG@icann.org</a><br>
<a
href="https://mm.icann.org/mailman/listinfo/cpwg"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
</blockquote>
</div>
_______________________________________________<br>
CPWG mailing list<br>
<a href="mailto:CPWG@icann.org"
target="_blank" moz-do-not-send="true">CPWG@icann.org</a><br>
<a
href="https://mm.icann.org/mailman/listinfo/cpwg"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
_______________________________________________<br>
GTLD-WG mailing list<br>
<a
href="mailto:GTLD-WG@atlarge-lists.icann.org"
target="_blank" moz-do-not-send="true">GTLD-WG@atlarge-lists.icann.org</a><br>
<a
href="https://atlarge-lists.icann.org/mailman/listinfo/gtld-wg"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://atlarge-lists.icann.org/mailman/listinfo/gtld-wg</a><br>
<br>
Working Group direct URL: <a
href="https://community.icann.org/display/atlarge/New+GTLDs"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://community.icann.org/display/atlarge/New+GTLDs</a></blockquote>
</div>
</div>
-- <br>
<div dir="ltr"
class="m_5635567038250828320m_-847023625134173502m_-1825612036884396901m_5693160749745162347gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr"><font face="trebuchet
ms, sans-serif">Greg Shatan</font>
<div><a
href="mailto:greg@isoc-ny.org"
target="_blank"
moz-do-not-send="true"><font
face="trebuchet ms,
sans-serif">greg@isoc-ny.org</font></a></div>
<div><font face="trebuchet ms,
sans-serif">President, ISOC-NY</font></div>
<div><font face="trebuchet ms,
sans-serif"><i>"The Internet
is for everyone"</i></font></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset
class="m_5635567038250828320m_-847023625134173502m_-1825612036884396901m_5693160749745162347mimeAttachmentHeader"></fieldset>
<pre class="m_5635567038250828320m_-847023625134173502m_-1825612036884396901m_5693160749745162347moz-quote-pre">_______________________________________________
CPWG mailing list
<a class="m_5635567038250828320m_-847023625134173502m_-1825612036884396901m_5693160749745162347moz-txt-link-abbreviated" href="mailto:CPWG@icann.org" target="_blank" moz-do-not-send="true">CPWG@icann.org</a>
<a class="m_5635567038250828320m_-847023625134173502m_-1825612036884396901m_5693160749745162347moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/cpwg" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/cpwg</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>
CPWG mailing list<br>
<a href="mailto:CPWG@icann.org" target="_blank"
moz-do-not-send="true">CPWG@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cpwg"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
_______________________________________________<br>
GTLD-WG mailing list<br>
<a href="mailto:GTLD-WG@atlarge-lists.icann.org"
target="_blank" moz-do-not-send="true">GTLD-WG@atlarge-lists.icann.org</a><br>
<a
href="https://atlarge-lists.icann.org/mailman/listinfo/gtld-wg"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://atlarge-lists.icann.org/mailman/listinfo/gtld-wg</a><br>
<br>
Working Group direct URL: <a
href="https://community.icann.org/display/atlarge/New+GTLDs"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://community.icann.org/display/atlarge/New+GTLDs</a></blockquote>
</div>
</div>
</div>
</div>
</div>
-- <br>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr"><font face="trebuchet ms, sans-serif">Greg
Shatan</font>
<div><a href="mailto:greg@isoc-ny.org"
target="_blank" moz-do-not-send="true"><font
face="trebuchet ms, sans-serif">greg@isoc-ny.org</font></a></div>
<div><font face="trebuchet ms, sans-serif">President,
ISOC-NY</font></div>
<div><font face="trebuchet ms, sans-serif"><i>"The
Internet is for everyone"</i></font></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</body>
</html>