<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div>Ayden,<div class=""><br class=""></div><div class="">The alternative to redraft is not sending any comment whatsoever, including parts that are in scope for the Council. </div><div class="">My suggestion is for us to ask for an extension to the comment deadline, while the SCBO reworks the comment. </div><div class=""><br class=""></div><div class="">On what is in scope, I would go a bit beyond just PDPs and also address policy implementation, something also in the Council's mission. </div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Rubens</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Em 6 de fev de 2019, à(s) 14:14:000, Ayden Férdeline <<a href="mailto:icann@ferdeline.com" class="">icann@ferdeline.com</a>> escreveu:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi Paul, <br class=""></div><div class=""><br class=""></div><div class="">Unfortunately it will not be possible for the SCBO to re-draft this comment now. There are 48 hours until the submission deadline, and we have developed this comment over five calls and numerous conversations on our mailing list, which has had participation from all stakeholder groups on this topic since December. This comment has not changed substantially in the two weeks that a draft has been shared on the Council's mailing list. I cannot ask SCBO members to re-draft something now as I am aware some are offline or traveling today and/or tomorrow.<br class=""></div><div class=""><br class=""></div><div class="">I was certainly under the impression that members of the SCBO had taken the comment back to their respective stakeholder group and/or constituency for feedback already, and certainly, feedback had been received and the comment re-drafted already. This might be something that individual stakeholder groups and/or constituencies want to address with their members and/or subject matter experts on the SCBO.<br class=""></div><div class=""><br class=""></div><div class="">That said, the comment will not be submitted if there is an objection raised by a member of the Council, and I do note that Michele has objected already. <br class=""></div><div class=""><br class=""></div><div class="">In terms of how we move forward, if the Council had small edits, I would feel comfortable resolving these over email with the SCBO, but what we are talking about here is a re-write and removal of bullet points that the SCBO has discussed, and I think that can't happen without a fuller contingency of SCBO members.<br class=""></div><div class=""><br class=""></div><div class="">But the Council could either prepare a fresh comment that reflects the views now being expressed, or remove the language about this comment being prepared by the SCBO and trim down the existing comment to a level where the Council is comfortable with it.<br class=""></div><div class=""><br class=""></div><div class="">Ayden <br class=""></div><div class="protonmail_signature_block"><div class="protonmail_signature_block-proton protonmail_signature_block-empty"><br class=""></div></div><div class=""><br class=""></div><div class="">‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br class=""></div><div class=""> On Wednesday, February 6, 2019 10:53 AM, McGrady, Paul D. <<a href="mailto:PMcGrady@winston.com" class="">PMcGrady@winston.com</a>> wrote:<br class=""></div><div class=""> <br class=""></div><blockquote type="cite" class="protonmail_quote"><div class=""><p class=""><span style="" class=""><span style="font-size:12pt" class="">Ayden,</span></span><br class=""></p><p class=""><span style="" class=""><span style="font-size:12pt" class=""> </span></span><br class=""></p><p class=""><span style="" class=""><span style="font-size:12pt" class="">I have the draft into the IPC for review and comment, but my initial take (and this is a personal view, not necessarily the view if the IPC), but this document goes way beyond what
I thought the purpose of this Standing Committee would be. I was under the impression that this group would address those things within the purview of the GNSO Council (PDP development. Full stop.) and leave other issues to the C/SG’s. This document goes
much further than that – for example, it jumps to the conclusion that the ALAC is over resourced and under representative. I’m not sure that is a Council position. In fact, I’m pretty sure that has never been in front of any of us at the table as a matter
of voting. Michele’s point about Staff and Board funding is another example.</span></span><br class=""></p><p class=""><span style="" class=""><span style="font-size:12pt" class=""> </span></span><br class=""></p><p class=""><span style="" class=""><span style="font-size:12pt" class="">While I respect the idea behind this Standing Committee, I don’t think it can be used as a blunt instrument for us to try to excise anything that the committee members don’t particularly
like about ICANN (the reference to “secret contracts” for example). </span></span><br class=""></p><p class=""><span style="" class=""><span style="font-size:12pt" class=""> </span></span><br class=""></p><p class=""><span style="" class=""><span style="font-size:12pt" class="">Again, the IPC may tell me something different after they have read it, but my impression is that this document needs to go back to the team for a quick redraft focusing on PDP issues.</span></span><br class=""></p><p class=""><span style="" class=""><span style="font-size:12pt" class=""> </span></span><br class=""></p><p class=""><span style="" class=""><span style="font-size:12pt" class="">Best,<br class=""> Paul</span></span></p><p class=""><span style="" class=""><span style="font-size:12pt" class=""> </span></span><br class=""></p><p class=""><span style="" class=""><span style="font-size:12pt" class=""> </span></span><br class=""></p><p class=""><span style="" class=""><span style="font-size:12pt" class=""> </span></span><br class=""></p><div class=""><div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in" class=""><div class=""><br class="webkit-block-placeholder"></div><div class=""><b class="">From:</b> council <<a href="mailto:council-bounces@gnso.icann.org" class="">council-bounces@gnso.icann.org</a>> <b class="">On Behalf Of </b>Michele Neylon - Blacknight<br class=""></div><div class=""> <b class="">Sent:</b> Wednesday, February 6, 2019 9:05 AM<br class=""></div><div class=""> <b class="">To:</b> Ayden Férdeline <<a href="mailto:icann@ferdeline.com" class="">icann@ferdeline.com</a>>; GNSO Council List <<a href="mailto:council@gnso.icann.org" class="">council@gnso.icann.org</a>><br class=""></div><div class=""> <b class="">Subject:</b> Re: [council] [new draft] Proposed GNSO Council Comment on FY20 ICANN Budget<br class=""></div><div class=""><br class="webkit-block-placeholder"></div></div></div><p class=""> <br class=""></p><p class=""><span lang="EN-IE" class="">Ayden</span><br class=""></p><p class=""><span lang="EN-IE" class=""> </span><br class=""></p><p class=""><span lang="EN-IE" class="">I object to the comment in its current form. <br class=""> I do not think that singling out either Board or Staff expenditure as currently proposed is appropriate for a Council comment.</span></p><p class=""><span lang="EN-IE" class=""> </span><br class=""></p><p class=""><span lang="EN-IE" class="">Regards</span><br class=""></p><p class=""><span lang="EN-IE" class=""><br class="">Michele</span></p><p class=""><span lang="EN-IE" class=""> </span><br class=""></p><p class=""><span lang="EN-IE" class=""> </span><br class=""></p><div class=""><p class=""><span style="" class=""><span style="font-family:-webkit-standard" class="">--</span></span><br class=""></p><p class=""><span style="" class=""><span style="font-family:-webkit-standard" class="">Mr Michele Neylon</span></span><br class=""></p><p class=""><span style="" class=""><span style="font-family:-webkit-standard" class="">Blacknight Solutions</span></span><br class=""></p><p class=""><span style="" class=""><span style="font-family:-webkit-standard" class="">Hosting, Colocation & Domains</span></span><br class=""></p><p class=""><span style="" class=""><span style="font-family:-webkit-standard" class=""><a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blacknight.com%2F&data=02%7C01%7Cpmcgrady%40winston.com%7C85d80643ffde4115afdc08d68c44765a%7C12a8aae45e2f4ad8adab9375a84aa3e5%7C0%7C0%7C636850623019463585&sdata=RQgLSLKW1yUoSSewiszby2j1sZU7SSa%2BzVp66NTnV2c%3D&reserved=0" class="">https://www.blacknight.com/</a></span></span><br class=""></p><p class=""><span style="" class=""><span style="font-family:-webkit-standard" class=""><a href="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fblacknight.blog%2F&data=02%7C01%7Cpmcgrady%40winston.com%7C85d80643ffde4115afdc08d68c44765a%7C12a8aae45e2f4ad8adab9375a84aa3e5%7C0%7C0%7C636850623019463585&sdata=Lbq5SVc9aB1j4%2F33QC0BUcLeGpV2L8su3Uk4XWYxr2o%3D&reserved=0" class="">http://blacknight.blog/</a></span></span><br class=""></p><p class=""><span style="" class=""><span style="font-family:-webkit-standard" class="">Intl. +353 (0) 59 9183072</span></span><br class=""></p><p class=""><span style="" class=""><span style="font-family:-webkit-standard" class="">Direct Dial: +353 (0)59 9183090</span></span><br class=""></p><p class=""><span style="" class=""><span style="font-family:-webkit-standard" class="">Personal blog: <a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmichele.blog%2F&data=02%7C01%7Cpmcgrady%40winston.com%7C85d80643ffde4115afdc08d68c44765a%7C12a8aae45e2f4ad8adab9375a84aa3e5%7C0%7C0%7C636850623019473593&sdata=Vxnt0oJWTTjxEIy3V2D1dPpl3%2Fdl0nQ4gjWRnyq9i7U%3D&reserved=0" class="">https://michele.blog/</a></span></span><br class=""></p><p class=""><span style="" class=""><span style="font-family:-webkit-standard" class="">Some thoughts: <a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fceo.hosting%2F&data=02%7C01%7Cpmcgrady%40winston.com%7C85d80643ffde4115afdc08d68c44765a%7C12a8aae45e2f4ad8adab9375a84aa3e5%7C0%7C0%7C636850623019473593&sdata=UpJDcP6kr13afqiUQh6v%2BEqkAENYyfg%2FHCNHllwQnoE%3D&reserved=0" class="">https://ceo.hosting/</a></span></span><br class=""></p><p class=""><span style="" class=""><span style="font-family:-webkit-standard" class="">-------------------------------</span></span><br class=""></p><p class=""><span style="" class=""><span style="font-family:-webkit-standard" class="">Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty</span></span><br class=""></p><p class=""><span style="" class=""><span style="font-family:-webkit-standard" class="">Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845</span></span><br class=""></p></div><p class=""><span lang="EN-IE" class=""> </span><br class=""></p><p class=""><span lang="EN-IE" class=""> </span><br class=""></p><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in" class=""><p class=""><b class=""><span style="" class=""><span style="font-size:12pt" class="">From: </span></span></b><span style="" class=""><span style="font-size:12pt" class="">council <<a href="mailto:council-bounces@gnso.icann.org" class="">council-bounces@gnso.icann.org</a>> on behalf of Ayden Férdeline <<a href="mailto:icann@ferdeline.com" class="">icann@ferdeline.com</a>><br class=""> <b class="">Reply-To: </b>Ayden Férdeline <<a href="mailto:icann@ferdeline.com" class="">icann@ferdeline.com</a>><br class=""> <b class="">Date: </b>Sunday 3 February 2019 at 17:31<br class=""> <b class="">To: </b>GNSO Council List <<a href="mailto:council@gnso.icann.org" class="">council@gnso.icann.org</a>><br class=""> <b class="">Subject: </b>[council] [new draft] Proposed GNSO Council Comment on FY20 ICANN Budget</span></span></p></div><div class=""><p class=""><span lang="EN-IE" class=""> </span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class="">Dear all,</span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class=""> </span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class="">The Standing Committee on Budget and Operations has prepared a new draft of a proposed GNSO Council comment on the FY20 Budget and Operating Plan. Please find attached, both clean and redlined versions.</span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class=""> </span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class="">There are two key changes from the previous version. First, we have worked with Councilors who raised concerns around the bullet point about the fellowship program, and in this draft this language has been refined. Second,
we have inserted a new bullet point calling for an upgrade to the GNSO's website to be prioritized, following the resourcing discussion at the Strategic Planning Session.</span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class=""> </span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class="">Absent any objections from a member of the Council we are seeking to submit this comment on behalf of the GNSO Council on 8 February 2019. If possible, please raise any concerns by 13:00 UTC on Wednesday, 6 February 2019
so that we have sufficient time to address them.</span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class=""> </span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class="">Thank you.</span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class=""> </span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class="">Best wishes,</span><br class=""></p></div><div class=""><div class=""><div class=""><p class=""><span lang="EN-IE" class="">Ayden Férdeline</span><br class=""></p></div></div><div class=""><p class=""><span lang="EN-IE" class=""> </span><br class=""></p></div></div><div class=""><p class=""><span lang="EN-IE" class=""> </span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class="">‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐</span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class="">On Thursday, January 24, 2019 6:58 PM, Ayden Férdeline <<a href="mailto:icann@ferdeline.com" class="">icann@ferdeline.com</a>> wrote:</span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class=""> </span><br class=""></p></div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt" class=""><div class=""><p class=""><span lang="EN-IE" class="">Dear all,</span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class=""> </span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class="">On behalf of the GNSO Council's Standing Committee on ICANN Budget and Operations, please find attached our draft comment on the proposed FY20 Budget and Operating Plan for your review and consideration. Absent any objections
from a member of the Council we are seeking to submit this comment on behalf of the GNSO Council on 8 February 2019.</span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class=""> </span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class="">We have our next call on Monday, 28 January at 14:00 UTC. If you have any questions, concerns, or suggested edits which you can share before this call, we will gladly table them for discussion on this call. Alternatively
we can address any concerns or questions that are raised after 28 January via email.</span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class=""> </span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class="">If possible,<b class=""> please raise any concerns by 1 February 2019 at 14:00 UTC</b> so that the SCBO is able to address these concerns and to share a revised draft with the Council with sufficient time for you to review the
final version. Thank you!</span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class=""> </span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class="">Finally, there is one paragraph in the proposed comment that is highlighted in yellow. This is in reference to the Document Drafting and Development pilot program. At this time the SCBO does not have a firm view on whether
or not this text should remain. We would appreciate input from the Council on whether or not this paragraph should remain, be edited, or deleted.</span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class=""> </span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class="">Best wishes,</span><br class=""></p></div><div class=""><p class=""><span lang="EN-IE" class="">Ayden Férdeline</span><br class=""></p></div></blockquote><div class=""><p class=""><span lang="EN-IE" class=""> </span><br class=""></p></div></div><span style="font-family:Arial" class=""><span style="font-size:10px" class=""><div class=""><br class=""></div><p class=""><br class=""></p><div class=""><hr class="">The contents of this message may be privileged and confidential. If this message has been received in error, please delete it without reading it. Your receipt of this message is not intended to waive any applicable privilege. Please do not disseminate this
message without the permission of the author. Any tax advice contained in this email was not intended to be used, and cannot be used, by you (or any other taxpayer) to avoid penalties under applicable tax laws and regulations.<br class=""></div><p class=""><br class=""></p></span></span></blockquote><div class=""><br class=""></div>_______________________________________________<br class="">council mailing list<br class=""><a href="mailto:council@gnso.icann.org" class="">council@gnso.icann.org</a><br class="">https://mm.icann.org/mailman/listinfo/council<br class=""></div></blockquote></div><br class=""></div></body></html>