<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
Thanks for your thoughtful response George. There's a lot to parse here so I'll have to give it more time. I remain unconvinced we should comment but, in the end, I cannot censor what folks want to write in the list. I also believe I've seen a lot of variation
the discussion and folks trying to get a grip on the subject. I've never found the arguments about ISOCs mission to be persuasive. Instead my two years with a competition economist in the CCTRT suggested the caps might be obsolete and an impediment to new
entrants. I also believe that domainers have a special interest in this which is NOT typical of an "ordinary" registrant. They value many of the new obligations and would pay for them. Your mention of capture seemed pretty dismissive of the rather rigorous
discussion which has taken place. I know that capture gets discussed in the abstract quite a bit and, I believe, often inappropriately. The organization is organized to support contracted parties and that shows up a lot. So a missive from registries or registrars
on capture is unlikely to sway me.<br>
<br>
</div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
Finally yes, NetChoice was spun out of the organization, from which I retired a couple years ago, but has been operating independently, often confrontationally for quite some time and I'm no longer at ACT in any case.<br>
<br>
</div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
Hope that helps to explain my bizarre message.<br>
</div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
Jonathan<br>
<br>
</div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
Jonathan Zuck<br>
</div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
Executive Director<br>
</div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
Innovators Network Foundation<br>
</div>
<div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black">
<a href="http://www.Innovatorsnetwork.org">www.Innovatorsnetwork.org</a></div>
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> GTLD-WG <gtld-wg-bounces@atlarge-lists.icann.org> on behalf of George Kirikos <icann@leap.com><br>
<b>Sent:</b> Wednesday, May 1, 2019 12:43:52 PM<br>
<b>To:</b> CPWG<br>
<b>Subject:</b> [GTLD-WG] [CPWG] Discussion of Capture is and always has been a legitimate topic at ICANN (was Re: ICANN Code of Conduct)</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:11pt;">
<div class="PlainText">Jonathan,<br>
<br>
I find your email:<br>
<br>
<a href="https://mm.icann.org/pipermail/cpwg/2019-April/001168.html">https://mm.icann.org/pipermail/cpwg/2019-April/001168.html</a><br>
<br>
which was in response to my email at:<br>
<br>
<a href="https://mm.icann.org/pipermail/cpwg/2019-April/001149.html">https://mm.icann.org/pipermail/cpwg/2019-April/001149.html</a><br>
<br>
which was responding to Greg's email at:<br>
<br>
<a href="https://mm.icann.org/pipermail/cpwg/2019-April/001136.html">https://mm.icann.org/pipermail/cpwg/2019-April/001136.html</a><br>
<br>
to be quite bizarre. Discussion of capture is and always has been a<br>
legitimate topic at ICANN.<br>
<br>
1. Before going into the substance, there appears to be a double<br>
standard here, where you state my comments are "disingenuous" and<br>
refer to some "campaign". Calling someone "disingenuous" isn't nice or<br>
respectful. The "campaign" presumably refers to Greg Shatan's<br>
statement at:<br>
<br>
<a href="https://mm.icann.org/pipermail/cpwg/2019-April/001162.html">https://mm.icann.org/pipermail/cpwg/2019-April/001162.html</a><br>
<br>
where wild accusations of a "well-orchestrated campaign" are made, and<br>
pointing to just one "lobby group", the Internet Commerce Association<br>
as behind it. Again, not nice words (and which I'll discuss further<br>
below), but not a peep when those statements are made (which you<br>
presumably share, given you refer to "the campaign"). Greg Shatan's<br>
entire email disrespects and attempts to delegitimize the thousands of<br>
comments that were made. Again, not a peep of concern about that.<br>
<br>
2. There's a great tool called "Google" that allows one to research<br>
past discussions of "capture" at ICANN, demonstrating that it has<br>
always been a legitimate topic that can be raised. Here are some<br>
examples to show that my statements are not out of line (not in any<br>
order):<br>
<br>
a)<br>
<a href="https://www.icann.org/en/system/files/files/report-comments-atlarge-review-draft-report-10apr17-en.pdf">https://www.icann.org/en/system/files/files/report-comments-atlarge-review-draft-report-10apr17-en.pdf</a><br>
<br>
In a review of the At-Large itself, comments by the Registry<br>
Stakeholder Group (RySG) regarding capture:<br>
<br>
"While we believe the structural changes proposed by ITEMS will help<br>
to improve the quality and representativeness of At-Large advice, we<br>
remain skeptical that representation by a few users is the best way to<br>
fully capture the user voice. Considering the diversity and breadth of<br>
user perspectives and ****pervasive concerns about the motivations of<br>
and potential capture by At-Large leaders*****, a more informative<br>
approach could be to carry out both quantitative and qualitative user<br>
studies about the impact of policies and other proposals and<br>
developments on Internet users." (page 40, emphasis added)<br>
<br>
"Pervasive concerns and motivations of and potential capture by<br>
At-Large leaders" -- that's permitted topic for discussion.<br>
<br>
Later in the same document, also by the RySG:<br>
<br>
"Carrying out quantitative and qualitative user studies1 on the impact<br>
of policies and other proposals and developments on Internet users<br>
would be effective way to deal with the breadth and diversity of user<br>
perspectives and balance ****ongoing concerns about the motivations<br>
of, and potential capture by, At-Large leaders.****"<br>
<br>
Again, "ongoing concerns about the motivations of, and potential<br>
capture by, At-Large leaders" is a legitimate topic for discussion<br>
within ICANN.<br>
<br>
b) The CCWG-Accountability report at:<br>
<br>
<a href="https://www.icann.org/en/system/files/files/ccwg-acct-ws2-draft-recs-improve-soac-accountability-29mar17-en.pdf">https://www.icann.org/en/system/files/files/ccwg-acct-ws2-draft-recs-improve-soac-accountability-29mar17-en.pdf</a><br>
<br>
"The new Bylaws tasked the CCWG-Accountability WS2 to:<br>
“review and develop ... recommendations on SO/AC accountability,<br>
including but not limited to improved processes for accountability,<br>
transparency, and participation that are helpful to prevent capture”"<br>
(page 4)<br>
<br>
<br>
c) By Greg Shatan himself:<br>
<br>
<a href="https://community.icann.org/download/attachments/52892329/Transcript%20Client%20Comm%20Meeting%20%232%2011%20March.doc?version=1&modificationDate=1426162093000&api=v2">https://community.icann.org/download/attachments/52892329/Transcript%20Client%20Comm%20Meeting%20%232%2011%20March.doc?version=1&modificationDate=1426162093000&api=v2</a><br>
<br>
<br>
Greg Shatan: "…It’s one of the - I wouldn’t say it’s a bogeyman<br>
because there are ****legitimate concerns about capture****. But it’s<br>
- it gets thrown around a fair amount and it’s definitely - while it<br>
can’t be ignored it’s also - it’s important to try to dig down and do<br>
exactly what you do, which is to say, “What are you - what concerns<br>
are you actually expressing when you talk about capture?” (page 8, and<br>
elsewhere too; emphasis added)<br>
<br>
<br>
d) <a href="https://www.icann.org/public-comments/soac-accountability-2017-04-14-en">
https://www.icann.org/public-comments/soac-accountability-2017-04-14-en</a><br>
<br>
"(iii) Supporting Organization and Advisory Committee accountability,<br>
including but not limited to improved processes for accountability,<br>
transparency, and participation that are ****helpful to prevent<br>
capture*****;<br>
<br>
This Bylaws mandate for this project specifically mention capture, a<br>
concern raised by NTIA in Stress Tests 32-34, *****regarding internal<br>
capture by a subset of SO/AC members, and concern that incumbent<br>
members might exclude new entrants to an SO/AC.****" (emphasis added)<br>
<br>
e) <a href="https://meetings.icann.org/en/dublin54/schedule/tue-ipc/transcript-ipc-20oct15-en.pdf">
https://meetings.icann.org/en/dublin54/schedule/tue-ipc/transcript-ipc-20oct15-en.pdf</a><br>
<br>
Kiran Malancharuvil (of the IP Constituency): "…So, but that group, it<br>
does make me sad because we - and this maybe a dangerous thing to say<br>
in an open meeting, but whatever. It's a really good example of<br>
capture in the ICANN community I think.<br>
<br>
I think that the privacy interests have captured and refused to<br>
compromise. I think that the Registrars and the self-interested<br>
service providers have captured that group." (pp. 40-41)<br>
<br>
Greg Shatan was even on that call, and wasn't perturbed at the<br>
discussion of capture. Immediately after Kiran spoke, Greg said:<br>
<br>
"Kiran, there are others. Do you have any idea about solutions to this<br>
problem more concretely?"<br>
<br>
Then Kiran even went further:<br>
<br>
"And everybody talks about capture at ICANN as if the business<br>
interests are the ones capturing the groups, and it's absolutely not<br>
the case. And the Privacy interests actually now are starting to the<br>
capture the Public Safety Working Group which is the Law Enforcement<br>
Group." (p. 42)<br>
<br>
Again, a legitimate topic of discussion within ICANN.<br>
<br>
f)<br>
<a href="https://meetings.icann.org/en/dublin54/schedule/mon-ccwg-accountability/transcript-ccwg-accountability-19oct15-en.pdf">https://meetings.icann.org/en/dublin54/schedule/mon-ccwg-accountability/transcript-ccwg-accountability-19oct15-en.pdf</a><br>
<br>
"ANNE AIKMAN-SCALESE: Is this thing on? Can you hear me? Okay. Just<br>
three quick points. I think that ****there's been a lot of concern<br>
expressed about capture and not keeping things open to capture.****<br>
And from my standpoint if one SO or AC can completely dictate the<br>
nuclear option, the use thereof or no use thereof, that would be a<br>
capture situation. So if only one can completely block, that's<br>
capture. That would mean one SO or AC can capture. So I agree with the<br>
way it's formulated now." (page 81, emphasis added)<br>
<br>
g) <a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/transcript-gnso-working-session-2-11mar18-en.pdf">
https://gnso.icann.org/sites/default/files/file/field-file-attach/transcript-gnso-working-session-2-11mar18-en.pdf</a><br>
<br>
Phil Corwin of Verisign:<br>
<br>
"Good morning. Phil Corwin. My group, and we had some participation,<br>
not a great deal of people involved, was on the question of capture.<br>
So I'll of course working group recommendations are subject to<br>
challenge as representing ****captured by a single constituency or a<br>
single interest and that's why capture should be avoided***** because<br>
consensus recommendations of a working group should represent<br>
consensus of a fairly board cross-section of the ICANN community, and<br>
not simply people from this constituency or that stakeholder group, or<br>
this particular economic interest.<br>
<br>
I'm going to speaking to this, I can't help but think in the context<br>
of a working group I'm co-chairing but I'm not going to refer to that<br>
specifically. I think you could have two types of capture. One, you<br>
could have a working group, which is just the only participants for<br>
whatever reason are from a single group, however you define it, and<br>
you can't get other people to participate. And I'm not sure what can<br>
be done at that point other than trying to encourage others to join in<br>
or to disband the group because you know that it's quite likely to<br>
have a single point of view and be subject to challenge, and why go<br>
through the exercise.<br>
<br>
The situation I've been dealing with is different. You have a -- it's<br>
basically ****what I call operational capture where you have a small group<br>
representing a single interest and single point of view who are the<br>
most active members of the working group.****" (pp. 24-25, emphasis<br>
added; discussion is even longer, than this)<br>
<br>
h) <a href="https://archive.icann.org/meetings/singapore2015/en/schedule/tue-csg/transcript-csg-meeting-10feb15-en.pdf">
https://archive.icann.org/meetings/singapore2015/en/schedule/tue-csg/transcript-csg-meeting-10feb15-en.pdf</a><br>
<br>
Elisa Cooper: "Yeah, so, you know, that’s an - if they ask us about<br>
that, that’s an opportunity for us. Our explanation was actually quite<br>
lengthy and I wanted to keep this to one slide. But it’s risks to<br>
coming from marginalized groups. It’s similar to some of these other<br>
ones that are out there.<br>
<br>
****It’s risk of capture****. It’s risk of over representation by<br>
governments. There’s a whole category of items that we think pose<br>
potential risk to the multistakeholder model." (pp. 3-4, emphasis<br>
added)<br>
<br>
i) <a href="https://www.icann.org/news/announcement-2003-01-09-en">https://www.icann.org/news/announcement-2003-01-09-en</a><br>
<br>
"Among the reforms is fresh thinking on how to bring the voices of<br>
individual users and registrants into the decision process. An<br>
At-Large Advisory Committee is being formed to channel the thinking of<br>
users around the world. Last March, the ICANN Board decided that, at<br>
this time, online elections of directors is an expensive process too<br>
fraught with dangers of capture and fraud, and more effective means of<br>
bringing users to the ICANN table needed to be found. "ALAC," added<br>
Lynn, "will help bring this about."<br>
<br>
That was an interesting one. Concerns about capture of online<br>
elections for ICANN directors, which then led to the creation of ALAC!<br>
<br>
j)<br>
<a href="https://gnso.icann.org/sites/default/files/filefield_4878/transcript-09dec08-en.txt">https://gnso.icann.org/sites/default/files/filefield_4878/transcript-09dec08-en.txt</a><br>
<br>
Danny Younger: "…The second, more urgent question that I've got is on<br>
the topic of<br>
capture. ****I'm one of many that views ICANN as having been captured by<br>
the contracted parties.**** I see multiple regional registry/registrar<br>
gatherings funded every year by ICANN with no equivalent for non-<br>
contracted parties whatsoever. Has the committee started thinking<br>
about recommendations to deal with the internal capture issue?" (emphasis added)<br>
<br>
and later:<br>
<br>
Marilyn Cade: "…Today ****I do think we have been captured by the<br>
contracted parties****, but I believe that we can overcome that and I<br>
believe that that is in the best interest of the contract parties as<br>
well." (emphasis added)<br>
<br>
Normally 10 examples would be more than enough, but I couldn't resist an 11th:<br>
<br>
k) <a href="https://www.icann.org/en/system/files/correspondence/badiei-to-chalaby-22may18-en.pdf">
https://www.icann.org/en/system/files/correspondence/badiei-to-chalaby-22may18-en.pdf</a><br>
<br>
>From NCSG:<br>
<br>
"At-Large must develop a robust conflict of interest policy, in<br>
particular for their leadership.<br>
<br>
It is no easy task to represent the interests of the Internet’s over<br>
3 billion end users. However, if At-Large is going to play this<br>
function effectively in the multistakeholder process, it is critical<br>
to consider their role as being distinct from that of other<br>
stakeholder groups at ICANN. ****At-Large should develop a conflict of<br>
interest policy to facilitate this distinction, and to avoid capture<br>
by interests whose goals may not be in line with those of end-users*****<br>
more generally such as, for example, governments and businesses.<br>
Although governments and businesses are, of course, end users in their<br>
own right, they also have dedicated stakeholder groups in which their<br>
interests are represented. Moreover, governments and some business<br>
sectors may have interests which are directly divergent from those of<br>
the vast majority of Internet users. ****In order to protect the integrity<br>
of ALAC, it is important to develop a conflict of interest policy<br>
which prevents membership by persons who are closely tied to these<br>
other groups.*****" (page 4)<br>
<br>
There are obviously many more examples, but I'll stop at 11. It should<br>
be abundantly clear that discussion of capture has been and is an<br>
entirely legitimate topic at ICANN.<br>
<br>
3. If one returns to my actual email:<br>
<br>
<a href="https://mm.icann.org/pipermail/cpwg/2019-April/001149.html">https://mm.icann.org/pipermail/cpwg/2019-April/001149.html</a><br>
<br>
it mentioned capture twice:<br>
<br>
a) "Given the overwhelming opposition already expressed in the public<br>
comments to date, Greg's statement is more indicative of capture of<br>
the At-Large, rather than anything that could reasonably reflect what<br>
users think of these contracts."<br>
<br>
and<br>
<br>
b) "The statement that "many At-Large Structures are also ISOC<br>
Chapters" is consistent with a conflict of interest and capture,<br>
rather than being reflective of ordinary users."<br>
<br>
The 2nd one is a supporting statement for the first, and literally<br>
quotes a statement from Greg Shatan's own draft:<br>
<br>
<a href="https://mm.icann.org/pipermail/cpwg/2019-April/001136.html">https://mm.icann.org/pipermail/cpwg/2019-April/001136.html</a><br>
<br>
"Many At-Large Structures are also ISOC Chapters, further<br>
demonstrating the commonality of interests."<br>
<br>
That's a direct conflict of interest in my view, an entirely<br>
legitimate concern to raise, as per the many citations pointed to<br>
above.<br>
<br>
4. Look at the actual history of this matter. At the last meeting, it<br>
was decided that At-Large would not be making a statement. What "new<br>
information" exists since that decision, to justify change? There is<br>
none, other than the fact that thousands of others have made comments,<br>
and so presumably some of ISOC's friends and/or allies feel the need<br>
to help ISOC. That's not a good justification at all.<br>
<br>
Remember, Jonathan even wrote on Friday:<br>
<br>
<a href="https://mm.icann.org/pipermail/cpwg/2019-April/001099.html">https://mm.icann.org/pipermail/cpwg/2019-April/001099.html</a><br>
<br>
"Let's table this discussion until we can have a more thorough<br>
exploration of the issues. Email is a terrible way in which to have<br>
such a discussion. "<br>
<br>
But then some people ignored that, wanting to relitigate a decided<br>
issue. And, many of those people were present at last week's meeting<br>
too, so they already had their chance. Again, what new information did<br>
they have? None. Did Jonathan rebuke them for not tabling the<br>
discussion? Nope.<br>
<br>
Indeed, look at Greg Shatan's email at:<br>
<br>
<a href="https://mm.icann.org/pipermail/cpwg/2019-April/001094.html">https://mm.icann.org/pipermail/cpwg/2019-April/001094.html</a><br>
<br>
"I believe that PIR was hoping for a comment along the lines of our<br>
first draft (which I believe they saw on our site) or our second<br>
draft."<br>
<br>
That is again entirely consistent with capture.<br>
<br>
5. It's obvious that many folks have some past or present connection<br>
to ISOC or one of its chapters, or perhaps even aspirational future<br>
connections with them. e.g. Greg Shatan's is obvious, via the NYC<br>
chapter of ISOC.<br>
<br>
Maureen Hilyard's SOI:<br>
<br>
<a href="https://community.icann.org/display/atlarge/Maureen+Hilyard+SOI">https://community.icann.org/display/atlarge/Maureen+Hilyard+SOI</a><br>
<br>
mentions the "Pacific Islands Chapter of the Internet Society"<br>
<br>
Marita Moll has a history with the Canadian chapter:<br>
<br>
<a href="http://www.maritamoll.ca/content/about-site">http://www.maritamoll.ca/content/about-site</a><br>
<br>
Cheryl Landon-Orr's SOI:<br>
<br>
<a href="https://community.icann.org/display/atlarge/Cheryl+Langdon-Orr+SOI">https://community.icann.org/display/atlarge/Cheryl+Langdon-Orr+SOI</a><br>
<br>
mentions "Internet Australia (IA) formally known as the Internet<br>
Society of Australia ( ISOC-AU)"<br>
<br>
John Laprise's LinkedIn profile:<br>
<br>
<a href="https://www.linkedin.com/in/jplaprise">https://www.linkedin.com/in/jplaprise</a><br>
<br>
mentions "cofounding Qatar's Internet Society chapter" as well as<br>
"Faculty" of Internet Society in May 2014.<br>
<br>
I think I've made my point.<br>
<br>
6. Let's take a look at Jonathan Zuck himself. Jonathan has 2 SOIs<br>
that I could find at ICANN, one for the At Large and one for the GNSO:<br>
<br>
<a href="https://community.icann.org/display/atlarge/Jonathan+Zuck+SOI">https://community.icann.org/display/atlarge/Jonathan+Zuck+SOI</a><br>
<a href="https://community.icann.org/display/gnsosoi/Jonathan+Zuck+SOI">https://community.icann.org/display/gnsosoi/Jonathan+Zuck+SOI</a><br>
<br>
One thing that you won't find mentioned in those SOIs is the history<br>
of Jonathan's involvement with Netchoice, as documented by their Form<br>
990 statements:<br>
<br>
<a href="http://foundationcenter.org/find-funding/990-finder">http://foundationcenter.org/find-funding/990-finder</a><br>
<a href="http://990finder.foundationcenter.org/990results.aspx?990_type=&fn=netchoice&st=&zp=&ei=&fy=&action=Search">http://990finder.foundationcenter.org/990results.aspx?990_type=&fn=netchoice&st=&zp=&ei=&fy=&action=Search</a><br>
<br>
<a href="http://990s.foundationcenter.org/990_pdf_archive/271/271716101/271716101_201512_990O.pdf">http://990s.foundationcenter.org/990_pdf_archive/271/271716101/271716101_201512_990O.pdf</a><br>
<a href="http://990s.foundationcenter.org/990_pdf_archive/271/271716101/271716101_201612_990O.pdf">http://990s.foundationcenter.org/990_pdf_archive/271/271716101/271716101_201612_990O.pdf</a><br>
<a href="http://990s.foundationcenter.org/990_pdf_archive/271/271716101/271716101_201712_990O.pdf">http://990s.foundationcenter.org/990_pdf_archive/271/271716101/271716101_201712_990O.pdf</a><br>
<br>
Page 7 of each Form 990 lists Jonathan Zuck as a director of<br>
Netchoice, an organization where Verisign is a member.<br>
<br>
<a href="https://netchoice.org/">https://netchoice.org/</a><br>
<br>
And of course Verisign desires fee increases too.<br>
<br>
Indeed, one of the drafters of the Business Constituency's statement<br>
in support of fee increases was Steve DelBianco, of Netchoice:<br>
<br>
<a href="https://mm.icann.org/pipermail/comments-org-renewal-18mar19/2019q2/003085.html">https://mm.icann.org/pipermail/comments-org-renewal-18mar19/2019q2/003085.html</a><br>
<br>
[another drafter of that statement was Andrew Mack, who even has<br>
PIR/ISOC as a client, see:<br>
<br>
<a href="https://www.amglobal.com/clients">https://www.amglobal.com/clients</a> ]<br>
<br>
And one is trying to assert that "capture" is somehow an inappropriate<br>
topic for discussion, given all of the above? I don't agree.<br>
<br>
7. Let's not forget about Greg's email at:<br>
<br>
<a href="https://mm.icann.org/pipermail/cpwg/2019-April/001162.html">https://mm.icann.org/pipermail/cpwg/2019-April/001162.html</a><br>
<br>
where he is either unaware of or ignores relevant facts, such as:<br>
<br>
a) I *personally* raised awareness to many .org/info/biz/asia<br>
registrants via Slashdot (as well as via my blog and Twitter), see:<br>
<br>
<a href="https://tech.slashdot.org/story/19/04/23/2330210/icann-proposes-allowing-unlimited-fee-increases-for-org-domain-names">https://tech.slashdot.org/story/19/04/23/2330210/icann-proposes-allowing-unlimited-fee-increases-for-org-domain-names</a><br>
<br>
Take a look at the date of that -- it's *before* our last meeting,<br>
linking again to a post by Nat Cohen at CircleID *before* our last<br>
meeting. On Slashdot, it generated 82 comments, and I didn't link to<br>
any form (neither did Nat Cohen via CircleID):<br>
<br>
<a href="http://www.circleid.com/posts/20190423_spurious_justifications_for_eliminating_caps_on_legacy_domains/">http://www.circleid.com/posts/20190423_spurious_justifications_for_eliminating_caps_on_legacy_domains/</a><br>
<br>
Take a look at the number of pageviews of the CircleID article --<br>
35,257 (at the time of this email), which is far above any other<br>
recent post:<br>
<br>
<a href="http://www.circleid.com/">http://www.circleid.com/</a><br>
<br>
(most CircleID articles get 1,000 to 2,000 views)<br>
<br>
Back in 2006, a similar Slashdot article also vent viral:<br>
<br>
<a href="https://slashdot.org/story/06/08/25/0611209/icann-oks-tiered-pricing-for-orgbizinfo">https://slashdot.org/story/06/08/25/0611209/icann-oks-tiered-pricing-for-orgbizinfo</a><br>
<br>
linking to my CircleID post that generate 76,707 views:<br>
<br>
<a href="http://www.circleid.com/posts/icann_tiered_pricing_tld_biz_info_org_domain/">http://www.circleid.com/posts/icann_tiered_pricing_tld_biz_info_org_domain/</a><br>
<br>
(and more than a thousand public comments opposing the proposed contracts)<br>
<br>
There was no "campaign". Individuals simply got interested in an<br>
important issue.<br>
<br>
b) NameCheap themselves blogged about it, *and* sent emails to all<br>
their own customers, thus generating many comments, both via the ICA<br>
form (which they linked to), and original creations. They certainly<br>
have a right to raise awareness. And then those clients also went to<br>
social media, to encourage public comment. For example, I don't know<br>
Quincy Larson personally, but take a look at his Twitter feed:<br>
<br>
<a href="https://twitter.com/ossia">https://twitter.com/ossia</a><br>
<br>
He's involved with FreeCodeCamp.org, and has more than 77,000<br>
followers. His tweet at:<br>
<br>
<a href="https://twitter.com/ossia/status/1121778165406265346">https://twitter.com/ossia/status/1121778165406265346</a><br>
<br>
has 322 retweets, and 365 likes, implying it received huge coverage<br>
and clicks, raising awareness. And if you look at the WHOIS for<br>
FreeCodeCamp.org:<br>
<br>
<a href="http://whois.domaintools.com/freecodecamp.org">http://whois.domaintools.com/freecodecamp.org</a><br>
<br>
it's registered at NameCheap, where he presumably learned about the issue.<br>
<br>
<br>
c) While many have been focused on .org, consider the number of public<br>
comments re: .info:<br>
<br>
<a href="https://mm.icann.org/pipermail/comments-info-renewal-18mar19/2019q2/date.html">https://mm.icann.org/pipermail/comments-info-renewal-18mar19/2019q2/date.html</a><br>
<br>
250 at the time of this post. Or for .biz:<br>
<br>
<a href="https://mm.icann.org/pipermail/comments-biz-renewal-03apr19/2019q2/date.html">https://mm.icann.org/pipermail/comments-biz-renewal-03apr19/2019q2/date.html</a><br>
<br>
169 at the time of this post. [The .asia archives appear to be broken,<br>
haven't been updated in a week, and haven't even posted my own<br>
submission yet, so those 6 comments aren't informative]<br>
<br>
Given the relative size of .org vs. .biz and .info, one would easily<br>
have expected more than 1000 comments for .org.<br>
<br>
d) Even the BBC reported about the issue, further raising awareness.<br>
<br>
e) Some very large non-profits and organizations representing<br>
non-profits made substantial comments:<br>
<br>
(i) NPR, YMCA, C-SPAN, National Geographic Society, AARP, The<br>
Conservation Fund, Oceana, and National Trust for Historic<br>
Preservation<br>
<br>
<a href="https://mm.icann.org/pipermail/comments-org-renewal-18mar19/2019q2/003179.html">https://mm.icann.org/pipermail/comments-org-renewal-18mar19/2019q2/003179.html</a><br>
<br>
(ii) National Council of Nonprofits<br>
<a href="https://mm.icann.org/pipermail/comments-org-renewal-18mar19/2019q2/000918.html">https://mm.icann.org/pipermail/comments-org-renewal-18mar19/2019q2/000918.html</a><br>
<br>
(iii) ASAE<br>
<br>
<a href="https://mm.icann.org/pipermail/comments-org-renewal-18mar19/2019q2/002154.html">https://mm.icann.org/pipermail/comments-org-renewal-18mar19/2019q2/002154.html</a><br>
<br>
f) Where are all the public comments from At-Large structures or<br>
individuals of this CPWG? We agreed last week that folks should submit<br>
individual comments, but where are they? I submitted one, of course.<br>
Where are comments from ALSes? Where's any outreach to those ALSes?<br>
All the entities that At Large purports to represent --- where are<br>
their comments? Doesn't At Large do any outreach or education?<br>
<br>
Instead, we have a small number of people pushing for an At Large<br>
statement at this late date (despite last week's call), one that is<br>
rather extreme and illogical, inconsistent with those who've made<br>
comments already. It doesn't represent the views of billions of users,<br>
nor should it pretend to. It's reactionary, reacting to a perceived<br>
desire from PIR/ISOC to have their views (which are self-serving<br>
views) put forth at ICANN. That's the very essence of capture. Go back<br>
to Greg's email:<br>
<br>
<a href="https://mm.icann.org/pipermail/cpwg/2019-April/001094.html">https://mm.icann.org/pipermail/cpwg/2019-April/001094.html</a><br>
<br>
"I believe that PIR was hoping for a comment along the lines of our<br>
first draft (which I believe they saw on our site) or our second<br>
draft."<br>
<br>
8. I feel so strongly about this issue, that if At Large does issue a<br>
statement that demonstrates capture, I will definitely cease my<br>
involvement with At Large and CPWG. Such a statement would undermine<br>
At Large's integrity and reputation. I will not waste my time<br>
providing input and analysis that will be ignored, if At Large<br>
demonstrates it has been captured.<br>
<br>
Sincerely,<br>
<br>
George Kirikos<br>
416-588-0269<br>
<a href="http://www.leap.com/">http://www.leap.com/</a><br>
<br>
On Tue, Apr 30, 2019 at 6:59 PM Jonathan Zuck<br>
<JZuck@innovatorsnetwork.org> wrote:<br>
><br>
> George,<br>
> Your comments about Greg somehow "capturing" the At-large (on whose behalf I wonder) are disingenuous given the campaign. In which you are engaged and insulting to everyone on this list attempting to get a handle on a complex and highly political issue. I
suggest you withdraw them. Thanks.<br>
> Jonathan<br>
><br>
> Jonathan Zuck<br>
> Executive Director<br>
> Innovators Network Foundation<br>
> <a href="http://www.Innovatorsnetwork.org">www.Innovatorsnetwork.org</a><br>
><br>
> ________________________________<br>
> From: GTLD-WG <gtld-wg-bounces@atlarge-lists.icann.org> on behalf of George Kirikos <icann@leap.com><br>
> Sent: Tuesday, April 30, 2019 7:51:47 AM<br>
> To: CPWG<br>
> Subject: Re: [GTLD-WG] [CPWG] Further Revised Draft Statement on .ORG Renewal<br>
><br>
> For the record, I disagree with the statement that Greg prepared, and<br>
> it doesn't reflect my views (which I linked to in an earlier post). It<br>
> doesn't even reflect the views expressed by many non-profits who made<br>
> public comments, including NPR and other high profile ones:<br>
><br>
> <a href="https://mm.icann.org/pipermail/comments-org-renewal-18mar19/2019q2/003179.html">
https://mm.icann.org/pipermail/comments-org-renewal-18mar19/2019q2/003179.html</a><br>
><br>
> or the Non-Commercial Stakeholders:<br>
><br>
> <a href="https://mm.icann.org/pipermail/comments-org-renewal-18mar19/2019q2/003207.html">
https://mm.icann.org/pipermail/comments-org-renewal-18mar19/2019q2/003207.html</a><br>
><br>
> If folks wanted to send a letter, they should have sent it in an<br>
> individual capacity, rather than pretend that this statement is<br>
> reflective of the views of billions of internet users. Given the<br>
> overwhelming opposition already expressed in the public comments to<br>
> date, Greg's statement is more indicative of capture of the At-Large,<br>
> rather than anything that could reasonably reflect what users think of<br>
> these contracts.<br>
><br>
> ISOC/PIR is just one of many non-profits, and its mission is no better<br>
> than any other. Every organization has unlimited wants, but needs to<br>
> work within a reasonable budget. ISOC/PIR doesn't own .org, and<br>
> shouldn't pretend it does via unlimited "rent" or taxes payable to it.<br>
> They'll always be able to spend as much money as they can take in. As<br>
> I noted in my own comments, nothing would stop ISOC/PIR from selling<br>
> out to private equity, who could then take the heat for huge price<br>
> increases, while ISOC/PIR walks away with an enormous multi-billion<br>
> dollar endowment fund.<br>
><br>
> The statement that "many At-Large Structures are also ISOC Chapters"<br>
> is consistent with a conflict of interest and capture, rather than<br>
> being reflective of ordinary users.<br>
><br>
> The base agreement for new gTLDs is different from that of legacy<br>
> gTLDs for good reason, and should not be adopted by legacy gTLDs which<br>
> predate ICANN itself, and whose registrants do not agree with<br>
> unlimited fee increases. That's changing the rules in the middle of<br>
> the game (whereas registrants of new gTLDs knew all along the risks<br>
> they take registering with new gTLDs, where the registry essentially<br>
> "owns" that TLD).<br>
><br>
> The letter quotes Jonathan Zuck's statement about the "desirability"<br>
> of higher prices almost verbatim, but hasn't done the same for others<br>
> in the CPWG. Higher prices are not desirable in any way, except by<br>
> some twisted logic that makes no economic sense (my own personal<br>
> background is in economics and finance). New entrants always knew that<br>
> legacy gTLDs had capped prices, before they entered the space.<br>
> Furthermore, competition generally leads to *lower* prices, not higher<br>
> prices!<br>
><br>
> Attempting to argue that capped fees contribute to confusion, phising,<br>
> fraud and abuse is truly a stretch. The most abused TLDs are the new<br>
> gTLDs, not the legacy ones, e.g. see:<br>
><br>
> <a href="https://www.spamhaus.org/statistics/tlds/">https://www.spamhaus.org/statistics/tlds/</a><br>
><br>
> If one wants to target phishing, fraud and other abuses, one needs to<br>
> actually *target* it using effective tools. Raising prices for<br>
> *everyone* is not an effective tool, as it has more collateral damage<br>
> than actual benefits. If 1%, for example, of domains are engaged in<br>
> abused, it makes no sense to raise costs on 100% of registrants. One<br>
> wants to raise costs only on those engaged in abuse (e.g. through high<br>
> penalties for abuse, like jailtime, fines, etc.). Raising prices for<br>
> *everyone* simply enriches the registry, at the expense of the public.<br>
><br>
> Pretending that an "economic study" will be helpful is absurd, as<br>
> ICANN has in the past commissioned "experts" who simply regurgitated<br>
> whatever ICANN wanted them to say. Recall that these so-called<br>
> "experts" (the Carlton report, etc.) were used to justify the new gTLD<br>
> program in the first place, which has been a failure. Here's a comment<br>
> from K. Claffy, which talked about those reports:<br>
><br>
> <a href="https://forum.icann.org/lists/economic-framework/msg00004.html">https://forum.icann.org/lists/economic-framework/msg00004.html</a><br>
><br>
> which also referenced my scathing comments about them at the time<br>
> (which proved prescient). She concluded her comments with:<br>
><br>
> "Similar to my observations of what's happening in the security and<br>
> stability discussion of root scaling, ICANN's behavior looks like it's<br>
> trying to buy rubberstamps of its current plans from commercial<br>
> consultants, rather than foster what is needed in the long term: a<br>
> coherent field of objective, peer-reviewed technical, policy, and<br>
> economic research on Internet naming and numbering, and incentivized<br>
> data-sharing to support such research."<br>
><br>
> The ICANN contracts do not have any mechanism to "undo" the changes.<br>
> Once the caps are removed, that genie cannot be put back in the<br>
> bottle. One should do an economic study *before* lifting any price<br>
> caps, rather than doing them after the horse has left the barn, and<br>
> after the damage has already been done.<br>
><br>
> What "problem" is this contract actually trying to solve? If it's not<br>
> broken (and legacy gTLDs are successful, obviously), one should stick<br>
> with the status quo. If new gTLDs are the "broken" thing, they can be<br>
> fixed directly (by adding fee caps, just like the successful legacy<br>
> gTLDs, or making other changes).<br>
><br>
> In conclusion, Greg, Jonathan, and others should have simply submitted<br>
> their own personal comments, rather than try to suggest that this<br>
> statement is reflective of billions of users.<br>
><br>
> Sincerely,<br>
><br>
> George Kirikos<br>
> 416-588-0269<br>
> <a href="http://www.leap.com/">http://www.leap.com/</a><br>
><br>
> On Tue, Apr 30, 2019 at 2:14 AM Greg Shatan <greg@isoc-ny.org> wrote:<br>
> ><br>
> > All,<br>
> ><br>
> > I am attaching another, further revised draft public comment on the .ORG renewal, after sifting through the various recent conversations on the list. I will try to circulate a redline in the morning, New York time, but can't right now.<br>
> ><br>
> > I thought about including something on UA, but for .ORG and in the absence of proposed language, I did not see the obvious hook in this statement to bring that concept in.<br>
> ><br>
> > Best regards,<br>
> ><br>
> > Greg<br>
> ><br>
> > Greg Shatan<br>
> > greg@isoc-ny.org<br>
> > President, ISOC-NY<br>
> > "The Internet is for everyone"<br>
> > _______________________________________________<br>
> > CPWG mailing list<br>
> > CPWG@icann.org<br>
> > <a href="https://mm.icann.org/mailman/listinfo/cpwg">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
> _______________________________________________<br>
> CPWG mailing list<br>
> CPWG@icann.org<br>
> <a href="https://mm.icann.org/mailman/listinfo/cpwg">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
> _______________________________________________<br>
> GTLD-WG mailing list<br>
> GTLD-WG@atlarge-lists.icann.org<br>
> <a href="https://atlarge-lists.icann.org/mailman/listinfo/gtld-wg">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">
https://community.icann.org/display/atlarge/New+GTLDs</a><br>
_______________________________________________<br>
CPWG mailing list<br>
CPWG@icann.org<br>
<a href="https://mm.icann.org/mailman/listinfo/cpwg">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
_______________________________________________<br>
GTLD-WG mailing list<br>
GTLD-WG@atlarge-lists.icann.org<br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/gtld-wg">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">
https://community.icann.org/display/atlarge/New+GTLDs</a></div>
</span></font>
</body>
</html>