<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Some of these are implementation details and should not be considered gating issues for moving forward, but I wanted to identify a couple of questions that come to mind in reading Izumi’s paper:</div>
<div><br>
</div>
<ol>
<li>Given the waiting period, is it the intention that any Bylaws change approved by the Board will have an effective date of 15/30 days past approval (whatever the period identified) passes, so that there’s time for the community process to follow?</li><li>Are there any requirements that the issues raised as the reason for community rejection of the Bylaws be raised within the earlier public comment over the proposed Bylaws changes?</li><li>There is reference in here to changes to mission, commitments and core values – aren’t those to be included in the fundamental Bylaws and therefore subject to a different process? Or is this about changes that might result in parts of the Bylaws not being
consistent with the mission/commitments/core values?</li></ol>
<div>Thanks, </div>
<div><br>
</div>
<div>Sam</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span><<a href="mailto:wp1-bounces@icann.org">wp1-bounces@icann.org</a>> on behalf of Jordan Carter <<a href="mailto:jordan@internetnz.net.nz">jordan@internetnz.net.nz</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, July 22, 2015 at 11:34 AM<br>
<span style="font-weight:bold">To: </span>Izumi Okutani <<a href="mailto:izumi@nic.ad.jp">izumi@nic.ad.jp</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:wp1@icann.org">wp1@icann.org</a>" <<a href="mailto:wp1@icann.org">wp1@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [WP1] Agenda for Meeting #20 - 22 July @ 19h UTC<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">Hi all
<div><br>
</div>
<div>Attached is a PDF copy of Izumi's paper, and the original Word version again if you need it.</div>
<div><br>
</div>
<div>cheers</div>
<div>Jordan</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 22 July 2015 at 23:46, Izumi Okutani <span dir="ltr">
<<a href="mailto:izumi@nic.ad.jp" target="_blank">izumi@nic.ad.jp</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
<br>
If you look at the "reference" there three points we want to consider, in addressing public comments.<br>
Please find the attached changes from ver.2, which attempts to address these points.<br>
<br>
<br>
Changes from ver.2:<br>
* Clarify Review period is not the only opportunity for the community to provide feedback<br>
i. e. there will be a public comment for the community before excercising this power<br>
<br>
--> Review whether this influences the need to extend the review period<br>
--> Review whether this addresses concerns on possible delays in changes needed<br>
<br>
* Additional explanation on how this power is not likely to destabilize ICANN<br>
--> Added the rationale provided by budget/strategic/operational plan section<br>
<br>
<br>
Changes needed but not reflected:<br>
* Explanation on how we described this how Member status can be created and maintained without undue costs, complexity, or liability<br>
--> Preferable to provide common explanation to be given under the section single membership model<br>
--> How we trigger the mechanism to bring ICANN to court in relation to this power<br>
<br>
Discussion points:<br>
* Does additional explanation on comment period give sufficient justification for short review period,<br>
or does we see the need to extend the review period to more than two weeks as requested?<br>
* Does additional explanation give sufficient confidence on this power being a blocking factor to the changes needed?<br>
* Does additional explanation give sufficient confidence this power still maintains stability to ICANN?<br>
* How do we address "Changes needed but not reflected" issues?<br>
<br>
<br>
<br>
------------------------------------------------------------------------------------------<br>
Reference: Points raised on the public comment<br>
------------------------------------------------------------------------------------------<br>
<br>
* The community review period<br>
- CCWG needs to agree on the alternative<br>
- Alternative options expressed from the public comment:<br>
a) 30 days<br>
b) 60 days<br>
c) 15-30 calendar days<br>
d) The end of the next ICANN meeting that begins no sooner than one month after the Board posts notice of adoption<br>
Prior to such changes becoming effective<br>
<br>
* Explain member structure<br>
- Requested to explain how Member status can be created and maintained without undue costs, complexity, or liability (325)<br>
- Needs an explanation once the mechanism is fixed<br>
<br>
* Consider mechanisms for limiting procedural impasse and possible delays<br>
<br>
* Consider a cap on the number of times this power can be utilized.<br>
-->No consensus to reflect<br>
<br>
* Increase compostions other than ccNSO and GAC (341)<br>
-->No consensus to reflect<br>
<br>
------------------------------------------------------------------------------------------<br>
<span class=""><br>
<br>
On 2015/07/22 20:12, Jordan Carter wrote:<br>
> Hi all<br>
><br>
> I am building off Grace's email below to build the agenda for the meeting<br>
> in eight hours or so - forgive the formatting.<br>
><br>
</span>> On 22 July 2015 at 20:36, Grace Abuhamad <<a href="mailto:grace.abuhamad@icann.org">grace.abuhamad@icann.org</a>> wrote:<br>
>><br>
>><br>
>> *22 July - meeting #20*<br>
<span class="">>><br>
>> 1. Community Model<br>
>> - overall description of CMSM model (first WP1 review of text, follows<br>
</span>>> CCWG discussion on 21 July) [*Grace* and *Jordan* first draft] ��� sent to<br>
>> WP1 list<br>
>> - voting weights (update following Paris, *finalise* if poss) [*Alan*] ���<br>
<span class="">>> sent to WP1 list in Jordan's email around 11.04am UTC<br>
>> - Community Forum (first WP1 review of text, replacement for ICANN<br>
</span>>> Community Council) [*Alan* and *Jordan*]��� sent to WP1 list in Jordan's<br>
<span class="">>> email around 11.04am UTC<br>
>><br>
>> 2. Fundamental Bylaws (review if anything outstanding from CCWG discussion<br>
</span>>> on 21 July, finalise) [*Jordan*] ��� same text as previously circulated.<br>
>><br>
>> 3. Standard Bylaws (review if any other changes, *finalise* if poss) [<br>
>> *Izumi*] ��� sent to WP1 list by Izumi around the same time as this email<br>
>><br>
>> 4. AOC Reviews into the ICANN Bylaws (*finalise* if poss) [*Steve*] ���<br>
<span class="">>> sent to WP1 list, needs staff revision before call<br>
>><br>
>><br>
> Then items 5 and 6 are a bit different to those previously identified, and<br>
> there's a new #7:<br>
><br>
</span>> 5. Removal of Individual Directors (review, choose option, *agree for CCWG<br>
> on 23 July*) ��� sent to WP1 by Jordan just before 11am UTC, building on<br>
> Alan's draft<br>
><br>
> 6. Recall of the entire ICANN Board (review material from lawyers, *agree<br>
> for CCWG on 23 July*) ��� sent to WP1 list by Jordan around 19h20 on 21 July<br>
<span class="">><br>
> 7. ICANN Budget (review Jonathan's updated paper) ��� sent to WP1 list by<br>
> Jonathan Zuck a few hours ago.<br>
><br>
> Then 7 below becomes 8.<br>
><br>
>> 7. Identification of any other bits of work we need to do to wrap this up [<br>
</span>>> *EVERYONE*]<br>
<span class="">>><br>
>><br>
> 9. Agree Agenda outline for meeting #21.<br>
><br>
><br>
> Thanks all, speak with you in ~8 hours.<br>
><br>
><br>
> Jordan<br>
><br>
><br>
><br>
</span>> _______________________________________________<br>
> WP1 mailing list<br>
> <a href="mailto:WP1@icann.org">WP1@icann.org</a><br>
> <a href="https://mm.icann.org/mailman/listinfo/wp1" rel="noreferrer" target="_blank">
https://mm.icann.org/mailman/listinfo/wp1</a><br>
><br>
<br>
<br>
_______________________________________________<br>
WP1 mailing list<br>
<a href="mailto:WP1@icann.org">WP1@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/wp1" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/wp1</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">Jordan Carter<br>
<br>
Chief Executive <br>
<b>InternetNZ</b><br>
<br>
04 495 2118 (office) | +64 21 442 649 (mob)<br>
<a href="mailto:jordan@internetnz.net.nz" target="_blank">jordan@internetnz.net.nz</a><br>
Skype: jordancarter<br>
<br>
<i>A better world through a better Internet </i><br>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>