<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;color:#0b5394">Hi Roberto and Alan,</div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:#0b5394"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:#0b5394">Thanks for the explanations. I understand and withdraw my objection. I'll even overlook the weird math in Alan's description of ccNSO growth :-).<br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:#0b5394"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:#0b5394">- Evan<br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;color:#0b5394"> <br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 25 Jul 2019 at 13:22, Roberto Gaetano <<a href="mailto:roberto_gaetano@hotmail.com">roberto_gaetano@hotmail.com</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 style="overflow-wrap: break-word;">
Evan,
<div>I have some sympathy for your argumentation, but am nevertheless in favour of the proposed formulation for a few reasons that I will try to detail below.</div>
<div>I think that ICANN has won the ccNSO battle. If we go back a few years, there was a substantial objection to join the ccNSO, even by major ccTLDs, with the argument that they did not need ICANN, substantiated by the fact that their existence and
relationship with IANA predates ICANN, and things were working properly even before. Now more and more ccTLDs are joining the ccNSO and I would argue that there is no longer an organised objection to the ccNSO itself.</div>
<div>About the change from the current formulation to the proposed one, I observe that we move from the obligation to have a non-ccNSO participant to the recommendation not to exclude them in the choice of the three representatives. This, IMHO, will
bring to a situation in which most of the times the representatives will be ccNSO members, because they are the ones that are more aware of what is going on and more willing to devote time and resources to a volunteer job, but leaves the door open to the possibility
that, in case we have some interested folks among the non-ccNSO ccTLD managers, one of them could get the position. I am sure that the ccNSO itself will make sure that the majority of the representatives are ccNSO members.</div>
<div><br>
</div>
<div>This said, we still have not solved the other issue: if it is recognised that a service is provided to the ccTLD community, why is the financial participation left to voluntary contributions? But I am not saying this loud because I know that it
will (re-)open a big can of worms.</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Roberto<br>
<div><br>
<blockquote type="cite">
<div>On 25.07.2019, at 07:35, Evan Leibovitch <<a href="mailto:evan@telly.org" target="_blank">evan@telly.org</a>> wrote:</div>
<br class="gmail-m_-6545053532315091339Apple-interchange-newline">
<div>
<div dir="ltr">
<div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(11,83,148)">I understand the problem to be solved but don't like the wording of the replacement.<br>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(11,83,148)"><br>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(11,83,148)">Why should non-ccNSO-member ccTLD managers even be eligible?</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(11,83,148)"><br>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(11,83,148)">There is precious little incentive for ccTLD registries to have anything to do with ICANN. Eligibility for selection here ought to be part of such incentive.</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(11,83,148)"><br>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(11,83,148)">They should just change "Two" to "Three" in
<span class="gmail-m_-6545053532315091339gmail-cloak gmail-m_-6545053532315091339gmail-conf-macro gmail-m_-6545053532315091339gmail-output-block" id="gmail-m_-6545053532315091339gmail-content_1">
18.7(a)</span><span class="gmail-m_-6545053532315091339gmail-cloak gmail-m_-6545053532315091339gmail-conf-macro gmail-m_-6545053532315091339gmail-output-block" id="gmail-m_-6545053532315091339gmail-content_1"> and drop 18.7(b) entirely. No other rewording is needed.<br>
</span></div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(11,83,148)"><br>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(11,83,148)">- Evan</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;color:rgb(11,83,148)"><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, 24 Jul 2019 at 18:18, Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">alan.greenberg@mcgill.ca</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">
I was asked to draft the comment for the ALAC's response to the <br>
Public Comment on the Fundamental Bylaw Change <br>
(<a href="https://community.icann.org/pages/viewpage.action?pageId=111384218" rel="noreferrer" target="_blank">https://community.icann.org/pages/viewpage.action?pageId=111384218</a>).<br>
<br>
The Public Comment closes this Friday at 23:59 UTC. (about 50 hours from now)<br>
<br>
===================================<br>
<br>
The ALAC supported the current version of the ICANN Bylaws Section <br>
18.7(a) and 18.7(b), but understands that it has now proven to be <br>
difficult to implement.<br>
<br>
The ALAC agrees that the proposed change preserves the intent of the <br>
original Fundamental Bylaw and supports the change.<br>
<br>
Subject to any new information being brought to the ALAC's attention, <br>
the current intention is that the ALAC will support this Fundamental <br>
Bylaw change when it is present to the Empowered Community.<br>
<br>
_______________________________________________<br>
CPWG mailing list<br>
<a href="mailto:CPWG@icann.org" target="_blank">CPWG@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cpwg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
<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" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">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>
GTLD-WG mailing list<br>
<a href="mailto:GTLD-WG@atlarge-lists.icann.org" target="_blank">GTLD-WG@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/gtld-wg" rel="noreferrer" target="_blank">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">
https://community.icann.org/display/atlarge/New+GTLDs</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" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">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>
</blockquote>
</div>
<br clear="all">
<br>
-- <br>
<div dir="ltr" class="gmail-m_-6545053532315091339gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div dir="ltr">
<div style="text-align:center">
<div style="text-align:left">Evan Leibovitch, <span style="font-size:12.8px">Toronto Canada</span></div>
<div style="text-align:left"><span style="font-size:12.8px">@evanleibovitch or </span><span style="font-size:12.8px">@el56</span></div>
</div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
CPWG mailing list<br>
<a href="mailto:CPWG@icann.org" target="_blank">CPWG@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cpwg" target="_blank">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
<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" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank">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>
registration-issues-wg mailing list<br>
<a href="mailto:registration-issues-wg@atlarge-lists.icann.org" target="_blank">registration-issues-wg@atlarge-lists.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/registration-issues-wg" target="_blank">https://mm.icann.org/mailman/listinfo/registration-issues-wg</a><br>
<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" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank">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.</div>
</blockquote>
</div>
<br>
</div>
</div>
_______________________________________________<br>
CPWG mailing list<br>
<a href="mailto:CPWG@icann.org" target="_blank">CPWG@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cpwg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
<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" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">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>
GTLD-WG mailing list<br>
<a href="mailto:GTLD-WG@atlarge-lists.icann.org" target="_blank">GTLD-WG@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/gtld-wg" rel="noreferrer" target="_blank">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">https://community.icann.org/display/atlarge/New+GTLDs</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" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">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></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div style="text-align:center"><div style="text-align:left">Evan Leibovitch, <span style="font-size:12.8px">Toronto Canada</span></div><div style="text-align:left"><span style="font-size:12.8px">@evanleibovitch or </span><span style="font-size:12.8px">@el56</span></div></div></div></div></div></div></div>