<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="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:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">As ever, thanks to leadership for their unflagging work!<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">I admit to being a little confused as to why we need this (especially given the multiple discussions about lack of Council time and resource constraints)
and where it came from, but from the perspective of the BC: having an active Council liaison to the GAC is a practical, sensible idea which we support. Not only is communication always a good thing, as is relationship-building, that also helps to surface concerns
early on so hopefully we can avoid later bumps in the road. I appreciate the updates on the GAC perspective from someone who can translate them into GNSO-relevant concerns, and I think we should, as part of any request to the GAC about the liaison role, also
ask if they appreciate the same in the other direction! <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">I do admit that I am a little concerned about GAC policy staff briefing the GAC on GNSO issues without any sort of input from either GNSO policy
staff or the GNSO itself. I’m not for a second suggesting that GAC staff should publicise all drafts or the like, but if GAC staff is issuing briefings about any other SO/AC, there are clear possibilities for misunderstandings. Again on a practical level,
it would make sense to me that we were at least consulted on what’s being said just in case nuances are missed and later misunderstood.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">As for the role of the liaison towards Council, forgive my naivety but I thought that was self-explanatory: reporting back to us on the GAC’s main
issues, especially where they concern the GNSO’s issues, and of course interacting with the GAC itself. Looking back at the request for candidates we issued last year, it looks straightforward to me:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">The Liaison will be primarily responsible for providing timely updates to the GAC on GNSO policy development activities
in order to complement the existing notification processes as well as answering questions in relation to these (GNSO) activities that GAC members may have. Furthermore,
<span style="background:yellow;mso-highlight:yellow">the Liaison will be responsible for providing the GNSO Council with regular updates on progress, including on GAC activities, specifically in so far as these relate to issues of interest to the GNSO.</span>
The objective of the liaison mechanism, in combination with other mechanisms and early engagement tools, is to facilitate effective early engagement of the GAC as well as generally assist with flow of information between the GAC and the GNSO. In addition to
these engagement tools, regular co-ordination calls are to be scheduled between the GNSO Liaison to the GAC and the GAC Leadership/GAC Support Staff to ascertain that all the relevant information has been received by the GAC and progress is being made, following
which a regular status update is provided by the Liaison to the GNSO Council.<o:p></o:p></span></i></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Apologies for my confusion/naivety!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Best to all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Marie<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> council <council-bounces@gnso.icann.org>
<b>On Behalf Of </b>philippe.fouquart--- via council<br>
<b>Sent:</b> Friday, 2 July 2021 17:50<br>
<b>To:</b> Tomslin Samme-Nlar <mesumbeslin@gmail.com><br>
<b>Cc:</b> gnso-secs@icann.org; GNSO Council List <council@gnso.icann.org><br>
<b>Subject:</b> Re: [council] Review of the GNSO Liaison to the GAC Role<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US">Thanks Tomslin. Good point, 1) (consultation+revision of the role) and 2) (expected role within council) are largely independent, so they’re
meant to run in parallel. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US">Clearly, we don’t want this to be open-ended, and I’m hopeful that by late September, leadership will have something to offer.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US">Philippe<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="FR" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="FR" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Tomslin Samme-Nlar [<a href="mailto:mesumbeslin@gmail.com">mailto:mesumbeslin@gmail.com</a>]
<br>
<b>Sent:</b> Friday, July 2, 2021 1:54 PM<br>
<b>To:</b> FOUQUART Philippe INNOV/NET <<a href="mailto:philippe.fouquart@orange.com">philippe.fouquart@orange.com</a>><br>
<b>Cc:</b> GNSO Council List <<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>>;
<a href="mailto:gnso-secs@icann.org">gnso-secs@icann.org</a><br>
<b>Subject:</b> Re: [council] Review of the GNSO Liaison to the GAC Role<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="FR"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="FR">Hi Philippe,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="FR"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="FR">I want to thank the council leadership for this well thought out proposal.
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="FR">Is it possible to have a rough estimate as to how long tasks 1 & 2 would take? Will they happen in parallel or sequentially?<o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="FR"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="FR">Regards,<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="FR">Tomslin<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="FR" style="font-size:9.5pt;color:black">@LinkedIn:
<a href="https://www.linkedin.com/in/tomslin/" target="_blank">https://www.linkedin.com/in/tomslin/</a></span><span lang="FR"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="FR"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="FR"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="FR">On Fri, 2 Jul 2021 at 04:00, philippe.fouquart--- via council <<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>> wrote:<o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Hi again,</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">During wrap-up we initiated a review of the GNSO Liaison to the GAC Role, and agreed for leadership to come up with
a proposal for the next steps, which you will find attached for your review and comments (reproduced below). Please note that we consider accommodating the timelines of this review and the appointment of the liaison.
</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:18.0pt">
<span lang="EN-US" style="font-size:10.0pt">1.</span><span lang="EN-US" style="font-size:7.0pt">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif">The GNSO Chair to reach out to the GAC Chair to seek input from the GAC side on the role and function of
the Liaison. In this context, further consideration needs to be given whether a formal review and/or update to the role description is necessary and helpful, and if so, how this could be achieved (for example, both leadership teams with input from the Liaison
as well as the GAC point of contact, could take on this task). As part of this conversation, the GNSO Chair would also share the recommended improvements that have been recently put forward by the Liaison with the Council for consideration (see
<u><a href="https://community.icann.org/download/attachments/162890199/v2%20GNSO%20GAC%20Relations.pdf?version=1&modificationDate=1623940556000&api=v2" target="_blank">slides</a></u>), noting that at this point these are recommendations from the Liaison that
have not been fully considered nor endorsed by the Council. </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:18.0pt">
<span lang="EN-US" style="font-size:10.0pt">2.</span><span lang="EN-US" style="font-size:7.0pt">
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif">Council leadership to develop proposed guidelines in relation to the Liaison’s participation and expected role when engaging with the Council and/or related activities. As this
aspect of the Liaison role is solely focused on the engagement of the Liaison with the Council, this is not expected to be part of a possible review as referenced in 1).
</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:18.0pt">
<span lang="EN-US" style="font-size:10.0pt">3.</span><span lang="EN-US" style="font-size:7.0pt">
</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif">Council to consider whether to postpone reconfirmation of the Liaison role while 1. and 2. are ongoing. The current Liaison would remain in his post until 1 and 2 are complete
so that both the Council and the Liaison can make an informed decision, based on an updated role description, about possible reappointment or whether it will be necessary to launch a new call for volunteers.
</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Thanks,</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Philippe</span><span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="FR"> <o:p></o:p></span></p>
</div>
<pre><span lang="FR">_________________________________________________________________________________________________________________________<o:p></o:p></span></pre>
<pre><span lang="FR"><o:p> </o:p></span></pre>
<pre><span lang="FR">Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc<o:p></o:p></span></pre>
<pre><span lang="FR">pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler<o:p></o:p></span></pre>
<pre><span lang="FR">a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,<o:p></o:p></span></pre>
<pre><span lang="FR">Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre>
<pre><span lang="FR"><o:p> </o:p></span></pre>
<pre><span lang="FR">This message and its attachments may contain confidential or privileged information that may be protected by law;<o:p></o:p></span></pre>
<pre><span lang="FR">they should not be distributed, used or copied without authorisation.<o:p></o:p></span></pre>
<pre><span lang="FR">If you have received this email in error, please notify the sender and delete this message and its attachments.<o:p></o:p></span></pre>
<pre><span lang="FR">As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.<o:p></o:p></span></pre>
<pre><span lang="FR">Thank you.<o:p></o:p></span></pre>
</div>
<p class="MsoNormal"><span lang="FR">_______________________________________________<br>
council mailing list<br>
<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/council" target="_blank">https://mm.icann.org/mailman/listinfo/council</a><br>
<br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" target="_blank">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style
delivery or disabling delivery altogether (e.g., for a vacation), and so on.<o:p></o:p></span></p>
</blockquote>
</div>
<pre><span lang="FR">_________________________________________________________________________________________________________________________<o:p></o:p></span></pre>
<pre><span lang="FR"><o:p> </o:p></span></pre>
<pre><span lang="FR">Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc<o:p></o:p></span></pre>
<pre><span lang="FR">pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler<o:p></o:p></span></pre>
<pre><span lang="FR">a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,<o:p></o:p></span></pre>
<pre><span lang="FR">Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre>
<pre><span lang="FR"><o:p> </o:p></span></pre>
<pre><span lang="FR">This message and its attachments may contain confidential or privileged information that may be protected by law;<o:p></o:p></span></pre>
<pre><span lang="FR">they should not be distributed, used or copied without authorisation.<o:p></o:p></span></pre>
<pre><span lang="FR">If you have received this email in error, please notify the sender and delete this message and its attachments.<o:p></o:p></span></pre>
<pre><span lang="FR">As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.<o:p></o:p></span></pre>
<pre><span lang="FR">Thank you.<o:p></o:p></span></pre>
</div>
</body>
</html>