<html 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="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoPlainText"><span style="font-size:12.0pt">Hi, Phil/All.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt">I agree we need to clarify our decision-making processes. I think that process needs to include email in a structured, agreed upon way. Previously, given the difficulty of some members attending some conference
calls, we used the email list to enable members not on the call to weigh-in before decisions are locked down. Given the geographic distribution and busy schedules of our volunteers, I think incorporating email in our decision-making processes, and getting
staff/consultant support in running the protocol, is necessary to support Team member participation. For example, only 9 Team members were on the last conference call.
<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt">Regarding a Barcelona meeting, as I recall the Team agreed on the last conference call that, after DC, we have our next F2F meeting
<u>around</u> the ICANN meeting in October in Barcelona. I specifically suggested that we ask staff to investigate our ability to meet before, after, or during the Barcelona meeting and that we then quickly come to agreement on the exact dates and nature of
our meeting on e-mail over the following few days. <o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt">While Phil noted his understanding that staff prefers to have the Team meet before the Barcelona meeting starts, I don’t think that should be construed as a “Team decision.” Unfortunately, I now see this
was recorded by staff as the Team’s decision. Please clarify if I’m remembering things incorrectly.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt">Personally, I would like to make sure the times and dates for Team meetings are driven by maximizing Team participation rather than staff convenience.
<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt">Thanks.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-size:12.0pt">Denise<o:p></o:p></span></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Denise Michel<o:p></o:p></p>
<p class="MsoPlainText">Domain Name System Strategy & Management<o:p></o:p></p>
<p class="MsoPlainText">Facebook, Inc.<o:p></o:p></p>
<p class="MsoPlainText">denisemichel@fb.com <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">On 7/29/18, 1:27 PM, "Ssr2-review on behalf of Phil Khoury" <ssr2-review-bounces@icann.org on behalf of phil@crkhoury.com> wrote:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> Hello all,<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> I understand people's concerns over scheduling - but could I please make a request?<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> As a matter of process, if the team makes a decision in plenary and you now want to revisit that decision, how about we put that on the agenda for the next team meeting rather than random email exchanges. Without a process for resolution,
these just add to the general sense of confusion and chaotic decision-making.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> Staff, can we please add to agenda for next meeting?<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> Cheers<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> Phil<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> Phil Khoury<o:p></o:p></p>
<p class="MsoPlainText"> Facilitator – ICANN SSR2<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> phil@crkhoury.com <mailto:phil@cameronralph.com.au> <o:p>
</o:p></p>
<p class="MsoPlainText"> tel +61 3 9421 3111 <o:p></o:p></p>
<p class="MsoPlainText"> mob +61 431 500 999 (also WhatsApp)<o:p></o:p></p>
<p class="MsoPlainText"> skype phil.khoury<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> cameron. ralph. khoury<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> Cameron Ralph Pty Ltd | PO Box 307 East Melbourne VIC 8002 | Australia<o:p></o:p></p>
<p class="MsoPlainText"> This email may contain confidential information. If received in error, please let us know us by reply email or phone and delete this email.
<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> On 28/7/18, 6:39 pm, "Ssr2-review on behalf of Boban Krsic" <ssr2-review-bounces@icann.org on behalf of krsic@denic.de> wrote:<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> Oops, we are talking about Thursday / Friday before the official ICANN Meeting. But nevertheless, unfortunately, I am not able to participate in<o:p></o:p></p>
<p class="MsoPlainText"> person due to personal commitments. I am arriving on Sunday in Barcelona and planning to stay until Thursday.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> Best regards,<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> - Boban.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> > On 28. Jul 2018, at 08:25, Boban Krsic <krsic@denic.de> wrote:<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > Hi all,<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> >> On 28. Jul 2018, at 00:13, Geoff Huston <gih@apnic.net> wrote:<o:p></o:p></p>
<p class="MsoPlainText"> >><o:p></o:p></p>
<p class="MsoPlainText"> >> I am in favour of Eric’s suggestions to use some time during the week.<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > Same here. I have already booked my flight back to Germany for Thursday due to private commitments on Friday.<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > Best regards,<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > - Boban.<o:p></o:p></p>
<p class="MsoPlainText"> ><o:p></o:p></p>
<p class="MsoPlainText"> > _______________________________________________<o:p></o:p></p>
<p class="MsoPlainText"> > Ssr2-review mailing list<o:p></o:p></p>
<p class="MsoPlainText"> > Ssr2-review@icann.org<o:p></o:p></p>
<p class="MsoPlainText"> > https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_ssr2-2Dreview&d=DwIGaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=MWVuq3jZIw5gwhGdDf-HWNL4CEWIsdUnt9gOgplCArM&m=gp7LZkBW6Q-6Sn0Jgu08X81C3nqr3fuRJTKiTeX6hMk&s=GTNen8Iiz1kBMStFYnI8Ek8hzaSX-vNvaE7S2CNAxm4&e=<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> _______________________________________________<o:p></o:p></p>
<p class="MsoPlainText"> Ssr2-review mailing list<o:p></o:p></p>
<p class="MsoPlainText"> Ssr2-review@icann.org<o:p></o:p></p>
<p class="MsoPlainText"> https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_ssr2-2Dreview&d=DwIGaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=MWVuq3jZIw5gwhGdDf-HWNL4CEWIsdUnt9gOgplCArM&m=gp7LZkBW6Q-6Sn0Jgu08X81C3nqr3fuRJTKiTeX6hMk&s=GTNen8Iiz1kBMStFYnI8Ek8hzaSX-vNvaE7S2CNAxm4&e=<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> _______________________________________________<o:p></o:p></p>
<p class="MsoPlainText"> Ssr2-review mailing list<o:p></o:p></p>
<p class="MsoPlainText"> Ssr2-review@icann.org<o:p></o:p></p>
<p class="MsoPlainText"> https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_ssr2-2Dreview&d=DwIGaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=MWVuq3jZIw5gwhGdDf-HWNL4CEWIsdUnt9gOgplCArM&m=gp7LZkBW6Q-6Sn0Jgu08X81C3nqr3fuRJTKiTeX6hMk&s=GTNen8Iiz1kBMStFYnI8Ek8hzaSX-vNvaE7S2CNAxm4&e=<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
</div>
</body>
</html>