<div dir="auto">Jonathan:<div dir="auto">I agree there is no model that guarantees equality. I'm just plumbing for equality of opportunity to influence outcomes. It's always the results that matter.</div><div dir="auto"><br></div><div dir="auto">And as it is now, end user interests are sorely disadvantaged, even with the confluence of these fluid alliances it appears you and I value and support.</div><div dir="auto"><br></div><div dir="auto">I have seen several times where the end user interest is coincident, even assist the conjugation of the BC and IPC interests. And I believe we should hug those and work them thru the fire.</div><div dir="auto"><br></div><div dir="auto">But all in, we're  working against  a stacked deck in current framework.</div><div dir="auto"><br></div><div dir="auto">-Carlton<br><div dir="auto"><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 1 Mar 2019, 5:39 pm Jonathan Zuck, <<a href="mailto:JZuck@innovatorsnetwork.org">JZuck@innovatorsnetwork.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">




<div>
<div dir="auto" style="direction:ltr;margin:0;padding:0;font-family:sans-serif;font-size:11pt;color:black">
Having been on both sides of this, though representing small business, it's a good convo to have. I've always tried to think of it using the principles of non violence. Even governments are dominated by big interests so it's up to us to build fluid alliances
 and look for points of leverage. There's NO model where we're equal.<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" target="_blank" rel="noreferrer">www.Innovatorsnetwork.org</a></div>
<br>
</div>
<hr style="display:inline-block;width:98%">
<div id="m_1773997524176256398divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> ALAC <<a href="mailto:alac-bounces@atlarge-lists.icann.org" target="_blank" rel="noreferrer">alac-bounces@atlarge-lists.icann.org</a>> on behalf of John Laprise <<a href="mailto:jlaprise@gmail.com" target="_blank" rel="noreferrer">jlaprise@gmail.com</a>><br>
<b>Sent:</b> Friday, March 1, 2019 4:13:22 PM<br>
<b>To:</b> León Felipe Sánchez Ambía<br>
<b>Cc:</b> ALAC Working List; Alan Greenberg<br>
<b>Subject:</b> Re: [ALAC] Bad Actor Admission</font>
<div> </div>
</div>
<div>
<div dir="auto">The more the merrier!<br>
<br>
<div>Sent from my Pixel 3XL<br>
<br>
John Laprise, Ph.D.</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Mar 1, 2019, 12:55 PM León Felipe Sánchez Ambía <<a href="mailto:leonfelipe@sanchez.mx" target="_blank" rel="noreferrer">leonfelipe@sanchez.mx</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;line-break:after-white-space">Happy to join you in that conversation if you don’t mind. I’ll buy you guys a beer!
<div><br>
<div>
<div>Best regards,</div>
<div><br>
</div>
<div><br>
</div>
<div>León</div>
</div>
<div><br>
<blockquote type="cite">
<div>El 1 mar 2019, a las 12:14, Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca" rel="noreferrer noreferrer" target="_blank">alan.greenberg@mcgill.ca</a>> escribió:</div>
<br class="m_1773997524176256398m_211765731506359645Apple-interchange-newline">
<div><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline!important">If
 there is a concern among staff, it must be raised through the CEO to the Board. If he/she can convince the Board, the Board has the power to act. If not, then it does not warrant action (in the minds of those who ARE legally held responsible for the ICANN).</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline!important">Should
 someone have seen GDPR coming and acted? And when it did become obvious, act faster, you bet.<span class="m_1773997524176256398m_211765731506359645Apple-converted-space"> </span></span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline!important">Lots
 of people saw GDPR coming and said so. Why we didn't act is an interesting discussion. Ask me in Kobe.</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline!important">Alan</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline!important">At
 01/03/2019 12:55 PM, John Laprise wrote:</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<blockquote type="cite" class="m_1773997524176256398m_211765731506359645cite" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
So one of the complaints I saw online is that ICANN org legal which presumably saw the GDPR train coming down the track had limited options beyond waving a flag despite it's material impact. ICANN org spends a lot of resources to stay abreast of international
 law but can only do something at the last minute. (Epdp)<span class="m_1773997524176256398m_211765731506359645Apple-converted-space"> </span><br>
<br>
The more I think about it, the more giving ICANN org (pres?) the right to ask the community to initiate a PDP has a kind of symmetry with the powers of the enhanced community. Essentially, if the community and the board fail to address an operational, material
 threat, ICANN org can hold the board and the community to account.<br>
<br>
Sent from my Pixel 3XL<br>
<br>
John Laprise, Ph.D.<br>
<br>
On Fri, Mar 1, 2019, 11:45 AM John Laprise <<a href="mailto:jlaprise@gmail.com" rel="noreferrer noreferrer" target="_blank">jlaprise@gmail.com</a>> wrote:<br>
<dl><dd>Not just staff...I was thinking ICANN org leadership...needs authority<br>
<br>
</dd><dd>Sent from my Pixel 3XL<br>
<br>
</dd><dd>John Laprise, Ph.D.<br>
<br>
</dd><dd>On Fri, Mar 1, 2019, 9:02 AM Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca" rel="noreferrer noreferrer" target="_blank">alan.greenberg@mcgill.ca</a><span class="m_1773997524176256398m_211765731506359645Apple-converted-space"> </span>> wrote:<br>
<dl><dd>John, do you really mean "ICANN org", ie staff, to make that decision?<br>
<br>
</dd><dd>Alan<br>
</dd><dd>--<span class="m_1773997524176256398m_211765731506359645Apple-converted-space"> </span><br>
</dd><dd>Sent from my mobile. Please excuse brevity and typos.<br>
<br>
</dd><dd>On March 1, 2019 9:00:50 AM EST, John Laprise <<a href="mailto:jlaprise@gmail.com" rel="noreferrer noreferrer" target="_blank">jlaprise@gmail.com</a>> wrote:<span class="m_1773997524176256398m_211765731506359645Apple-converted-space"> </span><br>
<dl><dd>Hi and thanks Olivier,<span class="m_1773997524176256398m_211765731506359645Apple-converted-space"> </span><br>
<br>
</dd><dd>My apologies for not being clear. I was suggesting a possible bylaws change where in ICANN org can ask the community to initiate policy development when it sees an urgent/important need that the community has not noticed.<br>
<br>
</dd><dd>Sent from my Pixel 3XL<br>
<br>
</dd><dd>John Laprise, Ph.D.<br>
<br>
</dd><dd>On Fri, Mar 1, 2019, 7:07 AM Olivier MJ Crépin-Leblond <<a href="mailto:ocl@gih.com" rel="noreferrer noreferrer" target="_blank">ocl@gih.com</a>> wrote:<br>
<dl><dd>Dear John,<br>
<br>
</dd><dd>please be so kind to find my response below:<br>
<br>
</dd><dd>On 01/03/2019 13:31, John Laprise wrote:<br>
<blockquote type="cite" class="m_1773997524176256398m_211765731506359645cite"><dd>Well said Evan and I share your concerns. If memory serves, so does the Board as MSM threats is a strategic planning issue. Musing upon waking I was wondering whether it would help if we could implement
 a mechanism whereby ICANN org could ask the empowered community to implement a pdp? This might've avoided the current epdp issue.</dd></blockquote>
<br>
</dd><dd>The ICANN Board and the Empowered Community cannot implement or launch PDPs relating to gTLDs. The "PDP" as such is a defined term for "Policy Development Process" and in the context of the Generic Names, only the GNSO can launch a PDP. In the context of
 Country Codes Names, when it relates to global policy, the ccNSO can launch a PDP.<br>
</dd><dd>The Board can ask the GNSO to launch a PDP on a gTLD related issue, but the GNSO can refuse.<br>
<br>
</dd><dd>The Board can also ask the ICANN communities, SOs/ACs to launch a Cross Community Working Group (CCWG). However, there are doubts expressed in the GNSO that CCWGs should *not* be the basis for policy making for gTLDs as all policy making for gTLDs should
 go through a PDP.<br>
<br>
</dd><dd>It's a power game and the bottom line is who has the control of policy processes on gTLDs.<br>
</dd><dd>Kindest regards,<br>
<br>
</dd><dd>Olivier<br>
</dd></dl>
</dd></dl>
</dd></dl>
</dd></dl>
</blockquote>
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline!important">_______________________________________________</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline!important">ALAC
 mailing list</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline!important"><a href="mailto:ALAC@atlarge-lists.icann.org" rel="noreferrer noreferrer" target="_blank">ALAC@atlarge-lists.icann.org</a></span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline!important"><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" rel="noreferrer noreferrer" target="_blank">https://atlarge-lists.icann.org/mailman/listinfo/alac</a></span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline!important">At-Large
 Online: <a href="http://www.atlarge.icann.org" rel="noreferrer noreferrer" target="_blank">
http://www.atlarge.icann.org</a></span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline!important">ALAC
 Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" rel="noreferrer noreferrer" target="_blank">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a></span></div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
</div>
</div>

_______________________________________________<br>
ALAC mailing list<br>
<a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank" rel="noreferrer">ALAC@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" rel="noreferrer noreferrer" target="_blank">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br>
<br>
At-Large Online: <a href="http://www.atlarge.icann.org" rel="noreferrer noreferrer" target="_blank">http://www.atlarge.icann.org</a><br>
ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" rel="noreferrer noreferrer" target="_blank">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a></blockquote></div>