<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Stephanie, All,</div><div dir="ltr"><br></div><div dir="ltr">Apologies for responding to this so late, but I wanted to respond to Stephanie's Point 1 before the face to face, and<span style="font-family:verdana,sans-serif"> correct some misconceptions about how the EPDP WG Charter treats GNSO Stakeholder Groups and Constituencies. Specifically, the IPC, BC and ISPCP are each separately represented in the EPDP WG. The Charter recognizes that the IPC, BC and ISPCP Members represent their respective constituencies (page 12):</span><div><div class="gmail_default"><div dir="auto"><div><font face="verdana, sans-serif"><br></font></div></div></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div class="gmail_default">Each Non-Contracted Party House SG, namely the Commercial Stakeholder Group and the Non-Commercial Stakeholder Group, may appoint 6 Members + 3 Alternates (for the Commercial Stakeholder Group this is further broken down to 2 Members + 1 Alternate per Constituency). </div></blockquote><div class="gmail_default"><div dir="auto"><br></div><div><font face="verdana, sans-serif">The fact that the IPC, BC and ISPCP are participating at the "C" (Constituency) level, while others in the GNSO are participating at the "SG" (Stakeholder Group) level is also reflected in the Charter's discussion of consensus (also page 12):</font></div><div><br></div></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div class="gmail_default">For the purpose of assessing level of consensus, Members are required to represent the formal position of their <b>SG/C</b> or SO/AC, not individual views or positions. [emphasis added]</div></blockquote><div class="gmail_default"><div><br></div><div><span style="font-family:verdana,sans-serif">This reflects reality, which is that the IPC, BC and ISPCP each develop "formal positions" at the Constituency level.</span> <font face="verdana, sans-serif"><br></font></div><div><font face="verdana, sans-serif"><br></font></div><div><font face="verdana, sans-serif">Constituency-based representation is also reflected in the membership chart on pages 12-13 of the Charter, where the IPC, BC and ISPCP representation is set out separately, at the C level, but the RySG, RrSG and NCSG representation is set out at the SG level. This is consistent with other GNSO WGs and the GNSO Council, where the IPC, BC and ISPCP participate as members of their Constituency. </font></div><div><font face="verdana, sans-serif"><br></font></div><div><font face="verdana, sans-serif">To clearly correct prior statements on this list: <b>IPC, BC and ISPCP representation (in the GNSO Council and in the ePDP Working Group) is based on constituencies, not on the SG. Consensus calls in the ePDP WG are also based on the IPC, BC and ISPCP constituencies.</b></font></div><div><font face="verdana, sans-serif"><b><br></b></font></div><div><font face="verdana, sans-serif">Regards and safe travels. </font></div><div><font face="verdana, sans-serif"><br></font></div><div><font face="verdana, sans-serif">Alex (on behalf of the IPC)</font></div><div><font face="verdana, sans-serif"><b><br></b></font></div></div><div><div dir="ltr" class="gmail_signature"><div dir="ltr">___________<div><b>Alex Deacon</b></div><div>Cole Valley Consulting</div><div><a href="mailto:alex@colevalleyconsulting.com" target="_blank">alex@colevalleyconsulting.com</a></div><div>+1.415.488.6009</div><div><br></div></div></div></div><br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Jan 7, 2019 at 7:43 PM Stephanie Perrin <<a href="mailto:stephanie.perrin@mail.utoronto.ca">stephanie.perrin@mail.utoronto.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div>
<p><font size="+1"><font face="Lucida Grande">Hi, we have discussed the matter in NCSG and generally agree with Kristina's alternative proposal. Here are a few of the reasons why:</font></font></p>
<p><font size="+1"><font face="Lucida Grande">1. While your latest two small group proposal avoids the representation issue which we raised, we still think that it is important for SGs to reach consensus on the recommendations/questions, and the small group
approach does nothing to help with that issue. Representation here is by SG/AC not by constituency.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">2. As Kristina has pointed out, the subject matter is inextricably linked...ir it were not, we would have made better progress by now. Atomizing the issues is tempting, but will do nothing to get us out of the
challenge of considering questions organically, linked as they are. <br>
</font></font></p>
<p><font size="+1"><font face="Lucida Grande">3. The schedule is heroic if not naive, and we have wasted much time. Trying to take shortcuts at this point, in our opinion, will not help</font></font><font size="+1"><font face="Lucida Grande">. I am sure
that <font face="Lucida Grande">Kristina is right when she says </font>that people have not read the comments. A group SG approach will help avoid further delays when we debate the outputs of a potential small group process in plenary. I am truly sorry
to think that staff went to all this work on the materials over the Christmas holidays....I did no ICANN work over that period myself. After counting my potential Christmases on first one hand then more optimistically two, I decided to take an ICANN holiday
over the holidays. Doubtless others smarter than I reached the same conclusion without having to do a risk assessment.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">4. We need to think seriously about which questions we are not going to have answered in a consensus fashion by the deadline, and develop recommendations for next steps for the GNSO Council, in my personal view.
In the meantime, let's try Kristina' approach.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">Stephanie Perrin</font></font><br>
</p>
<div class="gmail-m_1801025029055081529moz-cite-prefix">On 2019-01-07 18:32, Kurt Pritz wrote:<br>
</div>
<blockquote type="cite">
Hi Kristina:
<div><br>
</div>
<div>Thanks for your thoughts and proposal. </div>
<div><br>
</div>
<div>First, I would appreciate it if any other groups on the list came in with their opinions. Obviously, time is of the essence.</div>
<div><br>
</div>
<div>Without yet changing the currently published agenda and dual meeting plan (they are still in place), I have some thoughts and also questions about your proposal. </div>
<div><br>
</div>
<div>I. </div>
<div><br>
</div>
<div>This approach undoubtably places an additional burden on the team members. Your statement of it reflects much of the thinking that the Support Team experienced Friday and through the weekend as we discussed the amount of work to accomplish. The
balance is between these additional burdens and creating some opportunity to finish our work in a timely manner. </div>
<div><br>
</div>
<div>Therefore, we put this proposal out to see if the different groups were willing to endorse it. We have had some good successes with small teams in the past but also had some attempts not work out because the small team conclusions were re-litigated
at the plenary level. In those efforts, we recognized that each group must be represented in the small teams and that an opportunity for coordination must be provided for the small team member to communicate with their group.</div>
<div><br>
</div>
<div>In addition, the memo outlining the approach calls for the requirement to give the small team conclusions a significant amount of deference and also provided for an inter-meeting consultation on issues if necessary. We must sign up to these conditions
if the effort is to work. Certainly, no small team member would be forced to endorsing a conclusion if s/he desired to consult with her/his team.</div>
<div><br>
</div>
<div>I agree with your assessment of additional difficulty and that is the balancing that must occur as we decide whether to commit to this approach. I.e., in order for this effort to succeed, the various groups must commit to approach this with a
determination to shoulder the burden and also to make sound judgments when additional coordination is needed (and when it is not). For me, given the time available to us, I thought it was imperative to suggest or to try something to expand our capacity. I
came to the conclusion that trebling our capacity provided a chance of appropriately considering public comment within a time period in line with our objectives. </div>
<div><br>
</div>
<div>II.</div>
<div><br>
</div>
<div>Your assessment that the Team has not yet read the comment is disappointing (given the staff holiday work that went into it), however, I understand it. In partial mitigation of that, the agenda calls for a review of the rationale to introduce
each subject and give the Team a few minutes to read through the summary prior to the discussion. </div>
<div><br>
</div>
<div>The agenda seeks to march through the first few topics on each team’s list. The Support Team has prepared new summaries to help those who have not fully formed their thoughts as of yet.</div>
<div><br>
</div>
<div>III. </div>
<div><br>
</div>
<div>With regard to your proposal, I have questions so that I fully understand it. </div>
<div><br>
</div>
<div>Where you say: </div>
<div><br>
</div>
<div>"If, after reviewing the public comments, a group would like to change their position, they need to provide a rationale as to why. If the group's position is unchanged, they should identify why they haven't changed their position.” I wish to
be careful how we manage that.</div>
<div><br>
</div>
<div>Does that mean, a group would like to change their position as stated in the Initial Report or does it mean change their position as stated in the public comment?</div>
<div>
<ul class="gmail-m_1801025029055081529MailOutline">
<li>If the former, that is appropriate, a group can change its position on an agreed upon conclusion in the Initial report based on arguments made in the public comment.
</li><li>If the latter, I think that is inappropriate. The comments are the comments and should be taken as written, i.e., stand on their own. There are commenters that are not seated at our table and do not have the ability to change, elaborate on, or
explain their comment. </li></ul>
</div>
<div><br>
</div>
<div>Also, there are two parts to your proposal I don’t believe I can endorse (i.e., where I think it inappropriate to further burden the team): </div>
<div><br>
</div>
<div>1) "Each group should provide their position and rationale for each purpose/recommendation in writing, in advance of the meeting where it is going to be discussed, so that Staff can present it to the whole group in a review-friendly format”</div>
<div><br>
</div>
<div>I do not see each group providing a separate writing on 20-some-odd recommendations plus several open questions for each meeting in time for the other groups to read and consider it. Given that the comments, as collected and summarized by staff,
have not been read yet. I can’t burden the different groups with so many additional readings and writings and expect that to be successful.</div>
<div><br>
</div>
<div>There will likely be some issues where a written analysis is required but I believe we should take those as they arise and not create a blanket requirement for a writing on each issue. </div>
<div><br>
</div>
<div>2) "In between meetings, the list should be utilised to continue discussion, one topic at a time. List discussion should be highly focused and structured, for example providing a response to specific questions.”</div>
<div><br>
</div>
<div>I agree with having an email discussion on issues but I would not base the success of our plan on it. That is, I think it is a good idea but I would not delay any other effort in reliance that we will be able to work difficult issues out via email.
We have not yet been able to have a focused discussion on email. I lay this at the feet of the meeting cadence. With meetings twice a week there is not time for team members to formulate questions and have a thoughtful discussion. </div>
<div><br>
</div>
<div>IV</div>
<div>
<div><br>
</div>
<div>So, if you have gotten this far, I’d be happy to discuss this further but have left the agenda in place for now. If you think it would be helpful, I’d be happy to have a conversation. Unfortunately, most of the rest of the world is no longer at
their desks today but we could chat in an Adobe Connect room and anyone wanting to could listen in. </div>
</div>
<div><br>
</div>
<div>Thanks for reading this,</div>
<div><br>
</div>
<div>Kurt</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
<div><br>
<blockquote type="cite">
<div>On Jan 7, 2019, at 12:24 PM, Rosette, Kristina via Gnso-epdp-team <<a href="mailto:gnso-epdp-team@icann.org" target="_blank">gnso-epdp-team@icann.org</a>> wrote:</div>
<br class="gmail-m_1801025029055081529Apple-interchange-newline">
<div>
<div class="gmail-m_1801025029055081529WordSection1" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
All,<u></u><u></u></div>
<div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u> <u></u></div>
<div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
On behalf of the CPH members and alternates, attached and copied below is a CPH-proposed alternative to the small team approach. The CPH does not support the small team approach, and discussed it at a meeting earlier today. <u></u><u></u></div>
<div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u> <u></u></div>
<div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
-*-<u></u><u></u></div>
<div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u> <u></u></div>
<div style="margin:0in 0in 0.0001pt;font-size:10pt;font-family:Calibri,sans-serif">
<span style="font-size:11pt">Whilst we appreciate the challenge of finding an approach that is both effective and works for all members, the CPH does not support the 3 small team proposal as the best way to review public comments.<a name="m_1801025029055081529__ftnref1" title="" style="color:rgb(149,79,114);text-decoration:underline"><span class="gmail-m_1801025029055081529MsoFootnoteReference" style="vertical-align:super"><span class="gmail-m_1801025029055081529MsoFootnoteReference" style="vertical-align:super"><span style="font-size:11pt;font-family:Calibri,sans-serif">[1]</span></span></span></a><span class="gmail-m_1801025029055081529Apple-converted-space"> </span>[FN1:<span class="gmail-m_1801025029055081529Apple-converted-space"> </span></span><span style="font-size:11pt">Although
CPH representatives discussed at their meeting this morning the 3-team proposal that had been put forward over the weekend, the rationale applies also to the more recent 2-team proposal. ]</span><span style="font-size:11pt"><br>
<br>
Dividing the EPDP Team into 3 Small teams creates huge coordination challenges for each group and puts a significant burden on the individuals who have to represent their group. EPDP topics are so interrelated that it’s difficult to discuss in the vacuum of
small teams and given the necessary need to ensure all differing interests are represented in each team, there is likely to be same lack of consensus that exists in the team as a whole. Furthermore, dividing up group members will necessitate an increase in
the amount of time that will have to be spent discussing progress and concerns within each group. Being on the EPDP Team is already a huge time commitment for its members, and presumably few can afford to commit even more time to be able to keep up to date
on 3 teams, instead of 1.<span class="gmail-m_1801025029055081529Apple-converted-space"> </span><br>
<br>
Therefore the CPH would like to propose the following alternate approach:<br>
<br>
1) Staff confirm the order in which each purpose/recommendation is going to be reviewed<br>
<br>
2) Instead of meeting as a team (or small teams) allow this Tuesday’s (8 January 2019) call time to be used by each group to go through the public comments themselves. We appreciate that members have already been asked to review all public comments, but in
practise, it is unlikely that most have had the time to do so.<br>
<br>
3) Each group should review the public comments for each purpose and recommendation (in the order specified by staff as per 1) and agree on their position. If, after reviewing the public comments, a group would like to change their position, they need to provide
a rationale as to why. If the group's position is unchanged, they should identify why they haven't changed their position.<br>
<br>
4) Each group should provide their position and rationale for each purpose/recommendation in writing, in advance of the meeting where it is going to be discussed, so that Staff can present it to the whole group in a review-friendly format<br>
<br>
5) The EPDP Team continues to meet as a whole team on Tuesdays and Thursdays, but instead of discussing the individual public comments, it discusses the position of each group on the public comments of each recommendation/purpose, where there is no consensus.<br>
<br>
6) In between meetings, the list should be utilised to continue discussion, one topic at a time. List discussion should be highly focused and structured, for example providing a response to specific questions.<br>
<br>
</span><span style="font-size:11pt;font-family:"Times New Roman",serif">-*-<u></u><u></u></span></div>
<div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u> <u></u></div>
<div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u> <u></u></div>
<div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
Kristina<u></u><u></u></div>
<div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u> <u></u></div>
<div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u> <u></u></div>
<div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
Kristina Rosette<u></u><u></u></div>
<div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
Senior Corporate Counsel, IP – Domains<u></u><u></u></div>
<div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<a href="mailto:rosettek@amazon.com" style="color:rgb(149,79,114);text-decoration:underline" target="_blank">rosettek@amazon.com</a><span class="gmail-m_1801025029055081529Apple-converted-space"> </span>| 703.407.1354<u></u><u></u></div>
<div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u> <u></u></div>
</div>
<div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<br clear="all">
<hr width="33%" size="1" align="left">
<div id="gmail-m_1801025029055081529ftn1">
<div style="margin:0in 0in 0.0001pt;font-size:10pt;font-family:Calibri,sans-serif">
<a name="m_1801025029055081529__ftn1" title="" style="color:rgb(149,79,114);text-decoration:underline"><span class="gmail-m_1801025029055081529MsoFootnoteReference" style="vertical-align:super"><span class="gmail-m_1801025029055081529MsoFootnoteReference" style="vertical-align:super"><span style="font-size:10pt;font-family:Calibri,sans-serif">[1]</span></span></span></a><span class="gmail-m_1801025029055081529Apple-converted-space"> </span>Although
CPH representatives discussed at their meeting this morning the 3-team proposal that had been put forward over the weekend, the rationale applies also to the more recent 2-team proposal.<u></u><u></u></div>
</div>
</div>
<span id="gmail-m_1801025029055081529cid:BB5D8BCE-F99D-4D4E-B91D-26165CB34D8D@fios-router.home"><CPH Proposal for EPDP public comment review approach.docx></span><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">_______________________________________________</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">Gnso-epdp-team
mailing list</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<a href="mailto:Gnso-epdp-team@icann.org" style="color:rgb(149,79,114);text-decoration:underline;font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">Gnso-epdp-team@icann.org</a><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" style="color:rgb(149,79,114);text-decoration:underline;font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a></div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="gmail-m_1801025029055081529mimeAttachmentHeader"></fieldset>
<pre class="gmail-m_1801025029055081529moz-quote-pre">_______________________________________________
Gnso-epdp-team mailing list
<a class="gmail-m_1801025029055081529moz-txt-link-abbreviated" href="mailto:Gnso-epdp-team@icann.org" target="_blank">Gnso-epdp-team@icann.org</a>
<a class="gmail-m_1801025029055081529moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a></pre>
</blockquote>
</div>
_______________________________________________<br>
Gnso-epdp-team mailing list<br>
<a href="mailto:Gnso-epdp-team@icann.org" target="_blank">Gnso-epdp-team@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a></blockquote></div></div>