<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</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>
<div>
<div>Hi Jordan,</div>
<div><br>
</div>
<div>That approach should work and I can’t think of anything that would work (significantly) better.</div>
<div>I suggest that the first exercise that some of us as a sub-team do, is categorize the comments. Possible categories: comments on mechanisms, comments on powers, comments on (AoC in) bylaws etc. And that we then assign a category or multiple categories
to subteams to do both the analysis and the initial thinking of a way forward. In this way, not all of us will have to go through all the comments, we can do a lot of work in a relatively short timespan and if the subteams present at the F2F sessions, those
can be quite effective.</div>
<div>How does that sound?</div>
<div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri"><br>
</font></font></div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri">best,</font></font></div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri"><br>
</font></font></div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri">Roelof</font></font></div>
</div>
</div>
</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>Jordan Carter <<a href="mailto:jordan@internetnz.net.nz">jordan@internetnz.net.nz</a>><br>
<span style="font-weight:bold">Date: </span>woensdag 20 mei 2015 22:45<br>
<span style="font-weight:bold">To: </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>[WP1] WP1 - proposed work approach 7-16 June<br>
</div>
<div><br>
</div>
<div>
<div>Dear WP1 members,
<div><br>
</div>
<div>This email sets out how I propose we do our next piece of work. Please read and offer your comments.</div>
<div><br>
</div>
We are getting public comments back from our comment period 6-7 June, and then have a CCWG meeting on 9 June to look at the input and decide where to focus.
<div><br>
</div>
<div>The work approach agreed at the last CCWG call asked Work Parties to take the lead in analysing feedback on the specific parts of the comment report, identifying where there was broad support, where there were questions to be answered, and where there
was disagreement and other alternatives needed to be explored.</div>
<div><br>
</div>
<div>The outcome of this work, by 16 June, is some documentation of the above points along with some ideas about how to keep the conversation going with the ICANN community in Buenos Aires. </div>
<div><br>
</div>
<div>That is, we don't have to come up with proposals to address all the feedback, but we do need to be able to propose to CCWG how to deal with the discussions on the ground at ICANN 53.</div>
<div><br>
</div>
<div>To my mind the most logical way for us to do this work is for rapporteur or volunteers to take the task of preparing initial thinking on those matters, and then discuss them across a few meetings.</div>
<div><br>
</div>
<div>We have identified the weekend of 13/14 June as the time for these meetings to be held, with WP1 and WP2 and ST-WP meetings not clashing.</div>
<div><br>
</div>
<div>I don't know how much feedback we will get but I think it is prudent for us to schedule three WP1 meetings over that Friday-Sunday period 12-14 June, each of 2 hrs.</div>
<div><br>
</div>
<div>Hopefully we will only need two of the meetings. If we get a huge flood of feedback in the second half of the comment period, we might need more.</div>
<div><br>
</div>
<div>I would appreciate your <b>comments</b> on this approach, and I will work with staff to propose three meetings that are at different times of day so that people all have a chance to participate no matter where they live.</div>
<div><br>
</div>
<div><br>
</div>
<div>Look forward to your thoughts!</div>
<div><br>
</div>
<div>best</div>
<div>Jordan</div>
<br>
<br>
-- <br>
Jordan Carter<br>
Chief Executive, InternetNZ
<p>+64-21-442-649 | <a href="mailto:jordan@internetnz.net.nz">jordan@internetnz.net.nz</a></p>
<p>Sent on the run, apologies for brevity<br>
</p>
<p></p>
</div>
</div>
</span>
</body>
</html>