<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mv="http://macVmlSchemaUri" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Title content=""><meta name=Keywords content=""><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Arial;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"Lucida Grande";
panose-1:2 11 6 0 4 5 2 2 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Calibri;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:Calibri;}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:Calibri;}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:Calibri;}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:Calibri;}
span.EmailStyle18
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt'>James, I’ve added the proposed changes / comments in relation to specific whereas and resolved clauses on the wiki page (see <a href="https://community.icann.org/x/HgObAw)">https://community.icann.org/x/HgObAw)</a>. Following your confirmation on which changes should be made as the maker of the motion, we can update the motion accordingly. I hope this is helpful. If you prefer that this is captured in a different format, please let me know.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Marika<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><div><p class=MsoNormal style='text-autospace:none'><b><span style='font-size:10.0pt'>Marika Konings</span></b><span style='font-size:10.0pt;font-family:Cambria'><o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt'>Senior Policy Director & Team Leader for the GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) </span><span style='font-size:10.0pt;font-family:Cambria'><o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt'>Email: <a href="mailto:marika.konings@icann.org"><span style='color:#0563C1'>marika.konings@icann.org</span></a> </span><span style='font-size:10.0pt;font-family:Cambria'><o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><i><span style='font-size:10.0pt'> </span></i><span style='font-size:10.0pt;font-family:Cambria'><o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><i><span style='font-size:10.0pt'>Follow the GNSO via Twitter @ICANN_GNSO<o:p></o:p></span></i></p><p class=MsoNormal style='text-autospace:none'><i><span style='font-size:10.0pt'>Find out more about the GNSO by taking our <a href="http://learn.icann.org/courses/gnso"><span style='color:#0563C1'>interactive courses</span></a> and visiting the <a href="http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers"><span style='color:#0563C1'>GNSO Newcomer pages</span></a>.</span></i><span style='font-size:10.0pt;font-family:Cambria'><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='color:black'>From: </span></b><span style='color:black'><owner-council@gnso.icann.org> on behalf of "James M. Bladel" <jbladel@godaddy.com><br><b>Date: </b>Monday 19 September 2016 at 23:29<br><b>To: </b>"egmorris1@toast.net" <egmorris1@toast.net>, GNSO Council List <council@gnso.icann.org>, Phil Corwin <psc@vlaw-dc.com><br><b>Subject: </b>Re: [council] RE: Draft Motion - GNSO Validation of CCWG-Accountability Budget Request<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Times New Roman"'><o:p> </o:p></span></p></div><div><p class=MsoNormal>As always, thanks Phil & Ed for contributing to this motion.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Marika/Mary - Are we tracking changes to the language in a centralized place or doc? I expect we’ll be working this one on the table during our next call.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks—<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>J.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:11.0pt;color:black'>From: </span></b><span style='font-size:11.0pt;color:black'>Edward Morris <<a href="mailto:egmorris1@toast.net">egmorris1@toast.net</a>><br><b>Reply-To: </b>Edward Morris <<a href="mailto:egmorris1@toast.net">egmorris1@toast.net</a>><br><b>Date: </b>Tuesday, September 20, 2016 at 1:57 <br><b>To: </b>James Bladel <<a href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a>>, GNSO Council List <<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>>, Phil Corwin <<a href="mailto:psc@vlaw-dc.com">psc@vlaw-dc.com</a>><br><b>Subject: </b>re: [council] RE: Draft Motion - GNSO Validation of CCWG-Accountability Budget Request<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Times New Roman"'><o:p> </o:p></span></p></div><div><div><div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Lucida Grande"'>James, Phil, all:</span><span style='font-size:9.0pt;font-family:Arial'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Arial'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Lucida Grande"'> I share Phil's concerns with the Draft Motion and support his modification proposal.</span><span style='font-size:9.0pt;font-family:Arial'><o:p></o:p></span></p></div><div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Arial'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Lucida Grande"'>? As rapporteur for the CEP subgroup and a participant in three other CCWG WS2 subgroups I'm encountering situations concerning staff support and expenses that border on the ridiculous. For example, in the Ombudsman subgroup staff refused to set up a doodle poll at the request of the rapporteur that had in turn requested by a Board member. Staff is not allowed to do doodles, budgetary concerns, we were told. Staff papers have been weeks late, and in some cases have been of low quality and of little use. Volunteers have been deserting some groups in droves and momentum from the successful completion of work stream one has been lost. I'm very concerned about the direction of WS2 and the low level of funding is increasingly a focus of that concern.</span><span style='font-size:9.0pt;font-family:Arial'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Arial'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Lucida Grande"'>? As a rapporteur for one of the subgroups:</span><span style='font-size:9.0pt;font-family:Arial'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Arial'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Lucida Grande"'> 1. I certainly would not want to have to tell my group that we could not go in a direction we felt was necessary because the budget would allow us to make only certain choices,</span><span style='font-size:9.0pt;font-family:Arial'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Arial'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Lucida Grande"'> 2. I would not want to be precluded from requesting that the CCWG reexamine it's budget assumptions short of extraordinary circumstances if additional funds were needed to adequately complete this project.</span><span style='font-size:9.0pt;font-family:Arial'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Arial'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Lucida Grande"'> With regards to budgeting I can relay a conversation I had with Xavier during a recent webinar kicking off the FY18 budget consultation. There is documentation suggesting that, for example, the $1.4 million budgeted for WS2 legal expenses is an amount that is the total approved for the entire WS2 project, even if it were to extend into FY18. Xavier now claims that is not true, that the budget amounts are coming from the reserve fund and are expressly targeted for use in FY17. FY18 requests would have to be made separately. Again, this rather confused state would also auger against including the language that requests "for additional funding will only be requested in extraordinary circumstances". Merely going into a new fiscal year would likely not be considered an exceptional circumstance.</span><span style='font-size:9.0pt;font-family:Arial'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Arial'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Lucida Grande"'>In summary:</span><span style='font-size:9.0pt;font-family:Arial'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Arial'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Lucida Grande"'>1. I would delete or otherwise modify Whereas clause 4 to temper the suggestion that exploration of jurisdiction or any other subtopic should be restricted by budgetary concerns. I should note we have a WS2 subgroup entitled "jurisdiction" for a reason: the community in WS1 did feel an examination of jurisdiction was an essential part of our accountability discussions. Jurisdiction has many aspects. Whether the location of ICANN headquarters is an appropriate topic of consideration, something that would cause a number of difficulties budgetary and otherwise, is something the subgroup is currently discussing. Other aspects of jurisdiction, for example the site of arbitration of contractual disputes, are also matters being looked at by this subgroup and would not raise many of the same budgetary concerns. A blanket statement concerning the budgetary aspect of "revisiting the topic of the jurisdiction of ICANN's organisation" would not be appropriate. </span><span style='font-size:9.0pt;font-family:Arial'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Arial'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Lucida Grande"'>2. I would delete or change Resolved clause three to recognise that additional funding may be needed due to : 1. inadequate preliminary budgeting or 2. unforeseen circumstances that are less than extraordinary (i.e. seepage of WS2 into FY 18).</span><span style='font-size:9.0pt;font-family:Arial'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Arial'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Lucida Grande"'>?3. I share Phil's concerns regarding the amount budgeted for independent legal counsel. As a member of the legal committee I'll do my best to constrain costs but certainly if additional funds are needed I would like to feel requests for additional funding would be considered short of "extraordinary circumstances" (again, another reason to modify or eliminate Resolved clause 3). </span><span style='font-size:9.0pt;font-family:Arial'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Arial'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Lucida Grande"'>Thanks for considering,</span><span style='font-size:9.0pt;font-family:Arial'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Arial'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Lucida Grande"'>Ed Morris</span><span style='font-size:9.0pt;font-family:Arial'><o:p></o:p></span></p></div></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Arial'> <o:p></o:p></span></p></div></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Arial'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Arial'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Arial'> <o:p></o:p></span></p></div><div class=MsoNormal align=center style='text-align:center'><span style='font-size:9.0pt;font-family:Arial'><hr size=2 width="100%" align=center></span></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:Tahoma'>From</span></b><span style='font-size:10.0pt;font-family:Tahoma'>: "Phil Corwin" <<a href="mailto:psc@vlaw-dc.com">psc@vlaw-dc.com</a>><br><b>Sent</b>: Monday, September 19, 2016 11:41 PM<br><b>To</b>: "James M. Bladel" <<a href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a>>, "GNSO Council List" <<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>><br><b>Subject</b>: [council] RE: Draft Motion - GNSO Validation of CCWG-Accountability Budget Request</span><span style='font-size:9.0pt;font-family:Arial'> <o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:Arial'> <o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>James:</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>The following remarks are my personal views, and I will share them with the BC Executive Committee and BC members prior to our September 29<sup>th</sup> meeting to assure that any statement I make/position I take at that meeting is consistent with the consensus within the BC.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>That said, I have some significant concerns about the wording of the draft Resolution, and shall now set them forth.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><u><span style='font-size:11.0pt;color:#1F497D'>Use of Budget Constraints to limit range of discussion within WGs</span></u><span style='font-size:11.0pt;color:#1F497D'>_-</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Your cover note states, “I would like to draw your attention to WHEREAS #4 and RESOLVED #4, in which I attempted to capture the concerns raised by Phil and Paul and others regarding revisiting the subject of ICANN Jurisdiction in WS2”. My comments on this draft resolution are solely my own and I will let Paul chime in, or not, as he sees fit.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Whereas #4 states -- “The GNSO Council notes that many members of the GNSO community have expressed the view that the projected budget does not support revisiting the topic of the jurisdiction of ICANN”s organization.”</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Resolved #4 states – “It is the position of the GNSO Council that revisiting the jurisdiction or organization of the ICANN legal entity, as established by CCWG-Accountability Work Stream 1, is not supported by this projected budget.”</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>My very public personal position on ICANN’s organizational jurisdiction is that it was a mistake not to resolve this matter during WS1 (and the failure to do so is now being cited by Congressional critics of the IANA Transition), and that ICANN’s U.S. incorporation should be enshrined in a Fundamental Bylaw as an expedited outcome of WS2.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Notwithstanding that clear personal view, I have concerns about the proposed language cited above. For one thing, it is presently ambiguous – it is not clear whether the import of the language is that:</span><o:p></o:p></p><p class=MsoListParagraphCxSpFirst style='text-indent:-18.0pt'><span style='font-size:11.0pt;color:#1F497D'>·</span><span style='font-size:7.0pt;font-family:"Times New Roman";color:#1F497D'> </span><span style='font-size:11.0pt;color:#1F497D'>The projected budget should be increased so that “the topic of the jurisdiction of ICANN”s organization” can be revisited or addressed (the word “revisited” is also problematic, as it implies that some conclusive decision was made on this matter during WS2, whereas the record is to the contrary), or</span><o:p></o:p></p><p class=MsoListParagraphCxSpLast style='text-indent:-18.0pt'><span style='font-size:11.0pt;color:#1F497D'>·</span><span style='font-size:7.0pt;font-family:"Times New Roman";color:#1F497D'> </span><span style='font-size:11.0pt;color:#1F497D'>The topic of organizational jurisdiction should be off-limits in WS2 due to budget constraints</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Again, my personal view is that this topic of ICANN’s organizational jurisdiction should be further addressed in WS2 – and should be definitively resolved through the adoption of a Fundamental Bylaw enshrining US incorporation.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:11.0pt;color:#1F497D'>Notwithstanding that personal view, I am opposed to any Resolution which takes the position that budget considerations should limit the scope of inquiry and discussion of any WS2 subgroup. The budget, and especially that for impartial outside legal expertise on accountability matters on which ICANN Legal may have an inherent bias (such as transparency or staff accountability) should be adequate to support the necessary work, rather than suggesting that the work should be constrained to fit within the scope of the budget.</span></b><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:11.0pt;color:#1F497D'> </span></b><o:p></o:p></p><p class=MsoNormal><u><span style='font-size:11.0pt;color:#1F497D'>Adequacy of the budget for outside legal expertise</span></u><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:11.0pt;color:#1F497D'>The other problem I have with the draft Resolution is that it does not speak at all to the general concerns I and others have expressed about the adequacy of the budget for outside legal expertise for WS2 activities, as well as the proposed process for obtaining authorization of additional funding. </span></b><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:11.0pt;color:#1F497D'> </span></b><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>My recollection is that the WS2 legal budget is just one-tenth of the amounts expended for WS1 -- $1.4M compared to $14M. I would certainly anticipate that WS2 outside legal expenses will be substantially less than in WS1 because major revisions and drafting of Bylaws and Articles of Incorporation will not be required. Yet there is still reason to believe that a 90% reduction is excessively severe and likely to fall short of requirements for a quality and fully considered work product.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>It is also my recollection that under the proposed budget and accompanying procedures, even if the Legal Committee agrees that additional funding is required at some point in the process, the Board has unbridled discretion and decisional authority to accept, reject, or modify such a request for additional funds. This is very troubling given that WS2 addresses such matters as organizational transparency, and Board and staff accountability. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><u><span style='font-size:11.0pt;color:#1F497D'>Therefore, at this time I cannot personally support the proposed language in Resolved clause #3</span></u><span style='font-size:11.0pt;color:#1F497D'> – “The GNSO Council expects the CCWG-Accountability and staff to work within the constraints of this approved budget, and that excess costs or request for additional funding <b>will be considered only in extraordinary circumstances</b>.” (Emphasis added)</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>An “extraordinary circumstances” standard for authorizing additional funds is, in my opinion, far too high given that the budget for WS2 was set by a small group and only put out for public reaction after the fact. Further, it is absolutely unacceptance as a standard for consideration of additional funding requests – every such request should be considered without bias on its own separate merits, and not face a high hurdle simply because it exceeds a legal assistance budget that some Council and community members already fear may be inadequate to support the necessary work delegated to WS2. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><b><u><span style='font-size:11.0pt;color:#1F497D'>Summing up, my personal view is that this Resolution should be modified to:</span></u></b><o:p></o:p></p><p class=MsoListParagraphCxSpFirst style='text-indent:-18.0pt'><b><span style='font-size:11.0pt;color:#1F497D'>1.</span></b><span style='font-size:7.0pt;font-family:"Times New Roman";color:#1F497D'> </span><b><span style='font-size:11.0pt;color:#1F497D'>Eliminate any suggestion that discussion of ICANN’s organizational locus of incorporation is off-limits for the Jurisdiction subgroup based upon budget considerations</span></b><o:p></o:p></p><p class=MsoListParagraphCxSpLast style='text-indent:-18.0pt'><b><span style='font-size:11.0pt;color:#1F497D'>2.</span></b><span style='font-size:7.0pt;font-family:"Times New Roman";color:#1F497D'> </span><b><span style='font-size:11.0pt;color:#1F497D'>Express general concern about the adequacy of the funds budgeted for outside legal assistance, as well as the proposed process for deciding whether additional funds should be allocated at a future point of time.</span></b><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>I thank you and my fellow Councilors for considering these views, and look forward to further discussion of this matter.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Regards, Philip</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:Tahoma;color:navy'>Philip S. Corwin, Founding Principal</span></b><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:Tahoma;color:navy'>Virtualaw LLC</span></b><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:Tahoma;color:navy'>1155 F Street, NW</span></b><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:Tahoma;color:navy'>Suite 1050</span></b><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:Tahoma;color:navy'>Washington, DC 20004</span></b><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:Tahoma;color:navy'>202-559-8597/Direct</span></b><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:Tahoma;color:navy'>202-559-8750/Fax</span></b><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:Tahoma;color:navy'>202-255-6172/Cell</span></b><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:Tahoma;color:navy'> </span></b><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:Tahoma;color:navy'>Twitter: @VlawDC</span></b><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:Tahoma;color:black'> </span><o:p></o:p></p><p class=MsoNormal><b><i><span style='font-size:10.0pt;font-family:Tahoma;color:navy'>"Luck is the residue of design" -- Branch Rickey</span></i></b><o:p></o:p></p></div><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:Tahoma'>From:</span></b><span style='font-size:10.0pt;font-family:Tahoma'> <a href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a> [<a href="mailto:owner-council@gnso.icann.org">mailto:owner-council@gnso.icann.org</a>] <b>On Behalf Of </b>James M. Bladel<br><b>Sent:</b> Monday, September 19, 2016 4:02 PM<br><b>To:</b> GNSO Council List<br><b>Subject:</b> [council] Draft Motion - GNSO Validation of CCWG-Accountability Budget Request</span><o:p></o:p></p></div></div><p class=MsoNormal> <o:p></o:p></p><div><p class=MsoNormal><span style='color:black'>Council Colleagues - </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'>Attached and copied below, please find a draft motion for consideration during our next GNSO Council call (29 SEP), that examines the subject of the proposed budget & cost control mechanisms for CCWG-ACCT and Work Stream 2. </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'>In particular, I would like to draw your attention to WHEREAS #4 and RESOLVED #4, in which I attempted to capture the concerns raised by Phil and Paul and others regarding revisiting the subject of ICANN Jurisdiction in WS2. Please review these provisions closely, and make sure that they accurately reflect these points.</span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'>Thank you,</span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'>J.</span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal><b><span style='color:black'>Draft Motion - GNSO Validation of CCWG-Accountability Budget Request</span></b><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'>WHEREAS, </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoListParagraph style='margin-left:18.0pt;mso-add-space:auto;text-indent:-18.0pt;text-autospace:none'><span style='color:black'>1.</span><span style='font-size:7.0pt;font-family:"Times New Roman";color:black'> </span><span style='color:black'>Per its Charter, the Project Cost Support Team (PCST) has supported the CCWG-Accountability in developing a draft budget and cost-control processes for the CCWG-Accountability activities for FY17, and has also developed a historical analysis of all the transition costs to date (see <a href="https://gnso.icann.org/mailing-lists/archives/council/pdfpklU5q6Ojg.pdf">https://gnso.icann.org/mailing-lists/archives/council/pdfpklU5q6Ojg.pdf</a>).</span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoListParagraph style='margin-left:18.0pt;mso-add-space:auto;text-indent:-18.0pt;text-autospace:none'><span style='color:black'>2.</span><span style='font-size:7.0pt;font-family:"Times New Roman";color:black'> </span><span style='color:black'>The CCWG-Accountability FY17 budget was presented at its plenary meeting of June 21st and approved for transmission to the Chartering Organizations for validation as per the process agreed with the PCST. This request for validation was received on 23 June.</span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoListParagraph style='margin-left:18.0pt;mso-add-space:auto;text-indent:-18.0pt;text-autospace:none'><span style='color:black'>3.</span><span style='font-size:7.0pt;font-family:"Times New Roman";color:black'> </span><span style='color:black'>Following review and discussion during ICANN56, the GNSO Council <a href="https://gnso.icann.org/en/correspondence/bladel-to-bfc-ccwg-accountability-chairs-10jul16-en.pdf">requested</a> a webinar on this topic which was held on 23 August (see transcript at <a href="https://gnso.icann.org/en/meetings/transcript-ccwg-accountability-webinar-23aug16-en.pdf">https://gnso.icann.org/en/meetings/transcript-ccwg-accountability-webinar-23aug16-en.pdf</a>, recording at <a href="http://audio.icann.org/gnso/gnso-ccwg-accountability-webinar-23aug16-en.mp3">http://audio.icann.org/gnso/gnso-ccwg-accountability-webinar-23aug16-en.mp3</a> and AC recording at <a href="https://icann.adobeconnect.com/p8fu99qpt7d/">https://icann.adobeconnect.com/p8fu99qpt7d/</a>). </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoListParagraph style='margin-left:18.0pt;mso-add-space:auto;text-indent:-18.0pt;text-autospace:none'><span style='color:black'>4.</span><span style='font-size:7.0pt;font-family:"Times New Roman";color:black'> </span><span style='color:black'>The GNSO Council notes that many members of the GNSO community have expressed the view that the projected budget does not support revisiting the topic of the jurisdiction of ICANN”s organization.</span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoListParagraph style='margin-left:18.0pt;mso-add-space:auto;text-indent:-18.0pt;text-autospace:none'><span style='color:black'>5.</span><span style='font-size:7.0pt;font-family:"Times New Roman";color:black'> </span><span style='color:black'>The GNSO Council has discussed and reviewed all the relevant materials. </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'>RESOLVED,</span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoListParagraph style='margin-left:18.0pt;mso-add-space:auto;text-indent:-18.0pt;text-autospace:none'><span style='color:black'>1.</span><span style='font-size:7.0pt;font-family:"Times New Roman";color:black'> </span><span style='color:black'>The GNSO Council hereby accepts the proposed CCWG-Accountability FY17 budget, as well as the cost-control processes presented in conjunction with the CCWG budget (see <a href="https://gnso.icann.org/mailing-lists/archives/council/pdfpklU5q6Ojg.pdf)">https://gnso.icann.org/mailing-lists/archives/council/pdfpklU5q6Ojg.pdf)</a>. </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoListParagraph style='margin-left:18.0pt;mso-add-space:auto;text-indent:-18.0pt;text-autospace:none'><span style='color:black'>2.</span><span style='font-size:7.0pt;font-family:"Times New Roman";color:black'> </span><span style='color:black'>The GNSO Council expects to receive regular updates on actual expenditures as tracked against this adopted budget, and reserves the right to provide further input on the budget allocation in relation to the CCWG-Accountability related activities.</span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoListParagraph style='margin-left:18.0pt;mso-add-space:auto;text-indent:-18.0pt;text-autospace:none'><span style='color:black'>3.</span><span style='font-size:7.0pt;font-family:"Times New Roman";color:black'> </span><span style='color:black'>The GNSO Council expects the CCWG-Accountability and staff to work within the constraints of this approved budget, and that excess costs or request for additional funding will be considered only in extraordinary circumstances. </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoListParagraph style='margin-left:18.0pt;mso-add-space:auto;text-indent:-18.0pt;text-autospace:none'><span style='color:black'>4.</span><span style='font-size:7.0pt;font-family:"Times New Roman";color:black'> </span><span style='color:black'>It is the position of the GNSO Council that revisiting the jurisdiction or organization of the ICANN legal entity, as established by CCWG-Accountability Work Stream 1, is not supported by this projected budget.</span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoListParagraph style='margin-left:18.0pt;mso-add-space:auto;text-indent:-18.0pt;text-autospace:none'><span style='color:black'>5.</span><span style='font-size:7.0pt;font-family:"Times New Roman";color:black'> </span><span style='color:black'>The GNSO Council requests the GNSO Secretariat to communicate this resolution to the CCWG-Accountability Chairs, and to the office of the ICANN CFO. </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p></div><div class=MsoNormal align=center style='text-align:center'><hr size=1 width="100%" noshade style='color:#A0A0A0' align=center></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.5pt;color:black'>No virus found in this message.<br>Checked by AVG - <a href="http://www.avg.com">www.avg.com</a><br>Version: 2016.0.7797 / Virus Database: 4656/13026 - Release Date: 09/16/16</span><o:p></o:p></p></div></div></div></div></body></html>