<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
Thank you, Berry, for explaining the situation and our improvements over time to address better the way we can manage WG rosters.
<div>
<div><br>
</div>
<div>Regards. David <br>
<br>
<div id="AppleMailSignature" dir="ltr">Sent from my iPhone
<div><br>
</div>
<div><span style="background-color: rgba(255, 255, 255, 0);">David A. Olive<br>
Senior Vice President</span></div>
<div><span style="background-color: rgba(255, 255, 255, 0); font-size: 13pt;">Policy Development Support</span></div>
<div><span style="background-color: rgba(255, 255, 255, 0);">Internet Corporation for Assigned Names and Numbers (ICANN)<br>
<br>
<br>
</span></div>
</div>
<div dir="ltr"><br>
On Apr 4, 2019, at 2:48 PM, "<a href="mailto:mail@berrycobb.com">mail@berrycobb.com</a>" <<a href="mailto:mail@berrycobb.com">mail@berrycobb.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:124129526;
mso-list-template-ids:-1518684142;}
@list l1
{mso-list-id:811675523;
mso-list-type:hybrid;
mso-list-template-ids:735219604 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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]-->
<div class="WordSection1">
<p class="MsoNormal">Hi All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I won’t opine on whether the observer list should be published or not, but I wish to offer a bit of information about this issue.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Our current process for documenting WG rosters exists on a decentralized solution of the Wiki, which is considered the authoritative list. The mailman lists created for WGs of course is managed via the mailman interface and while it’s
not considered authoritative it has no easy way to reconcile it back to the roster on the Wiki. Also, a “third list” is maintained for Members/Participants so that attendance can be taken against the roster via an Excel sheet. Suffice it to say, it is a
challenge to maintain accuracy given the quantity of changes in the life of a given WG across the three different tools and with 8 or so “live” groups.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The good news is that this will change with a centralized WG Enrollment tool on a CRM. In the future, community members will be able to manage their WG status (participant vs. observer) and their SOIs via the WGE portal. While the go-live
date for this application is several months away, staff is starting to migrate in-flight WGs into the backend of the CRM for which it will become the authoritative source for managing WG rosters and attendance tracking. At some interval, staff will export
roster and attendance data for publication on the wiki until an automated publication solution is developed. But this should/will go a long way to help maintain higher levels of accuracy.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">When the next generation roster is posted on the wiki, it will be categorized by Members/Participant, Observers, and ICANN staff. Should the Council decide not to publish the Observer list, we can easily filter them out from the roster
reports. In the next few months, we’ll be scheduling time for a demonstration of the new enrollment management tool.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">EPDP-Phase 2 is already setup in the CRM and ready to go once the final membership roster has been determined. We’re working on importing the 200 Observers as well which will include a reconciliation between that list and what is loaded
on the Mailman interface. Once a meeting schedule is determined, staff will start to create events for which attendance can be tracked and published back to the Wiki.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I hope you find this useful.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">B<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">GNSO Policy Consultant<o:p></o:p></p>
<p class="MsoNormal">@berrycobbb<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> council <<a href="mailto:council-bounces@gnso.icann.org">council-bounces@gnso.icann.org</a>>
<b>On Behalf Of </b>Drazek, Keith via council<br>
<b>Sent:</b> Thursday, April 4, 2019 14:49<br>
<b>To:</b> <a href="mailto:icann@ferdeline.com">icann@ferdeline.com</a>; <a href="mailto:michele@blacknight.com">
michele@blacknight.com</a><br>
<b>Cc:</b> <a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a><br>
<b>Subject:</b> Re: [council] EPDP list of Observers is incomplete<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">My quick and preliminary reaction here is:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo3">We should decide whether we believe observer lists are needed, or not. I don’t have a strong opinion here. Noting that anyone can technically ‘observe’ PDP WG email discussions via
the public email archives, perhaps maintaining a list of subscribed observers is mostly meaningless and really just an extra burden on staff to maintain.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo3">However, IF we decide we want a list of subscribed observers, I agree with Ayden it should be complete, up-to-date and accurate, to include all observes whether they are staff or otherwise.
Otherwise, what’s the point? Naturally recognizing that all GNSO Policy staff subscribe to all PDP mailing lists, we could identify them by group rather than name.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level1 lfo3">The issue of ICANN Staff attempting to influence a community member during policy development work is an entirely different discussion, and one that might warrant escalation to the
staffer’s manager. Ayden and I will take that off-list and figure out the most appropriate path forward.<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Keith<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>From:</b> council <<a href="mailto:council-bounces@gnso.icann.org">council-bounces@gnso.icann.org</a>>
<b>On Behalf Of </b>Ayden Férdeline<br>
<b>Sent:</b> Thursday, April 04, 2019 2:29 PM<br>
<b>To:</b> Michele Neylon - Blacknight <<a href="mailto:michele@blacknight.com">michele@blacknight.com</a>><br>
<b>Cc:</b> GNSO Council List <<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>><br>
<b>Subject:</b> [EXTERNAL] Re: [council] EPDP list of Observers is incomplete<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">No. This _is_ a conversation for the Council to have. We are not discussing the comments that we made to me. We are discussing the Observer list and whether or not it should be complete. And it should be, in my view. Why should there be
one standard for community transparency, and another, lower one, for staff?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regards, Ayden<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="protonmail_mobile_signature_block">
<p class="MsoNormal">Sent from ProtonMail Mobile<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">On Thu, Apr 4, 2019 at 20:22, Michele Neylon - Blacknight <<a href="mailto:michele@blacknight.com">michele@blacknight.com</a>> wrote:<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Ayden <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I’ll keep this brief<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">1 - I don’t think listing staff members who are subscribed to various lists is necessary and I can also see that creating more problems than it solves<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">2 - as this is a rather serious allegation I’ll leave it to Keith or Marika to address. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">However I don’t understand why you thought it appropriate to raise on this list without first speaking to the interim chair. As Council we shouldn’t be getting into this sort of issue unless other avenues have been exhausted <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regards <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Michele <o:p></o:p></p>
<div id="AppleMailSignature">
<p class="MsoNormal">Mr Michele Neylon <o:p></o:p></p>
<div>
<p class="MsoNormal">Blacknight Hosting & Domains<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.blacknight.host_&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=h7ObVMPGpAcLv72avqZ3syNYxeg9Akd-D4l9_q4cPOQ&m=tRU9IBULsKSSCSRnQUUz7li1itGgauZqgfmPZZDWwY4&s=6lDhmfa11l_GW8ZqfShTf3KWkLiK1D1Q9mqwJXctdeA&e=">http://www.blacknight.host/
[blacknight.host]</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.mneylon.social&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=h7ObVMPGpAcLv72avqZ3syNYxeg9Akd-D4l9_q4cPOQ&m=tRU9IBULsKSSCSRnQUUz7li1itGgauZqgfmPZZDWwY4&s=vC6acGEcoNJSpRlx-UUHe62fhLp_6x2FdJ1zNFSxHFc&e=">http://www.mneylon.social
[mneylon.social]</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Sent from mobile so typos and brevity are normal <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On 4 Apr 2019, at 18:20, Ayden Férdeline <<a href="mailto:icann@ferdeline.com">icann@ferdeline.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">Hi Michele,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks for your questions.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Yes, I believe all ICANN staff members who are subscribed to the mailing list should be named on the wiki page. We can separate them between staff observers and support staff. But if we name community observers, I do not understand why
we would not name staff observers, and especially so if they are reading the list in their professional capacity and then attempting to influence discussions with participants.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">And yes, it was an ICANN staff member (not support staff, but from GSE), who attempted to influence me and sought to use me to advance an objective of the ICANN organisation. I can only speak to my experience here. But when their message
reached my inbox I was surprised, as I did not even realise their department was monitoring the EPDP discussions.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal">Ayden <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">On Thursday, April 4, 2019 6:43 PM, Michele Neylon - Blacknight <<a href="mailto:michele@blacknight.com">michele@blacknight.com</a>> wrote:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p><span lang="EN-GB">Ayden</span><o:p></o:p></p>
<p><span lang="EN-GB"> </span><o:p></o:p></p>
<p><span lang="EN-GB">There are a few things here that are confusing me a little and maybe you can clarify them</span><o:p></o:p></p>
<p><span lang="EN-GB"> </span><o:p></o:p></p>
<p><span lang="EN-GB">Are you asking that ALL ICANN Staff who are on the mailing list should be listed on wiki page?</span><o:p></o:p></p>
<p><span lang="EN-GB"> </span><o:p></o:p></p>
<p><span lang="EN-GB">Are you also accusing ICANN staffers of trying to influence you?</span><o:p></o:p></p>
<p><span lang="EN-GB"> </span><o:p></o:p></p>
<p><span lang="EN-GB">Or are you saying there are people on the list who are not ICANN staff and that some of them tried to influence you?</span><o:p></o:p></p>
<p><span lang="EN-GB"> </span><o:p></o:p></p>
<p><span lang="EN-GB">Sorry, but I’m just not 100% clear on what you’re saying.</span><o:p></o:p></p>
<p><span lang="EN-GB"> </span><o:p></o:p></p>
<p><span lang="EN-GB">Regards</span><o:p></o:p></p>
<p><span lang="EN-GB"> </span><o:p></o:p></p>
<p><span lang="EN-GB">Michele</span><o:p></o:p></p>
<p><span lang="EN-GB"> </span><o:p></o:p></p>
<p><span lang="EN-GB"> </span><o:p></o:p></p>
<div>
<p><span style="color:black">--</span><o:p></o:p></p>
<p><span style="color:black">Mr Michele Neylon</span><o:p></o:p></p>
<p><span style="color:black">Blacknight Solutions</span><o:p></o:p></p>
<p><span style="color:black">Hosting, Colocation & Domains</span><o:p></o:p></p>
<p><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.blacknight.com_&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=h7ObVMPGpAcLv72avqZ3syNYxeg9Akd-D4l9_q4cPOQ&m=tRU9IBULsKSSCSRnQUUz7li1itGgauZqgfmPZZDWwY4&s=amqQvgUVWmixY2p_mpCHo6XEjA8FpMr2uoOe655_zXw&e=">https://www.blacknight.com/
[blacknight.com]</a><o:p></o:p></p>
<p><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__blacknight.blog_&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=h7ObVMPGpAcLv72avqZ3syNYxeg9Akd-D4l9_q4cPOQ&m=tRU9IBULsKSSCSRnQUUz7li1itGgauZqgfmPZZDWwY4&s=_xZGRwAEABn4tjAf0KybSfWHxWctmeoiQ1qVEW7yHD4&e=">https://blacknight.blog/
[blacknight.blog]</a><o:p></o:p></p>
<p><span style="color:black">Intl. +353 (0) 59 9183072</span><o:p></o:p></p>
<p><span style="color:black">Direct Dial: +353 (0)59 9183090</span><o:p></o:p></p>
<p><span style="color:black">Personal blog: </span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__michele.blog_&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=h7ObVMPGpAcLv72avqZ3syNYxeg9Akd-D4l9_q4cPOQ&m=tRU9IBULsKSSCSRnQUUz7li1itGgauZqgfmPZZDWwY4&s=H8leTVcm40ibzrxge2V7xuZacpUJvhzLCz3ob5aT55k&e=">https://michele.blog/
[michele.blog]</a><o:p></o:p></p>
<p><span style="color:black">Some thoughts: </span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__ceo.hosting_&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=h7ObVMPGpAcLv72avqZ3syNYxeg9Akd-D4l9_q4cPOQ&m=tRU9IBULsKSSCSRnQUUz7li1itGgauZqgfmPZZDWwY4&s=AJ2n68y_HHkbR2SosEvNsPsMa7jk8EjPFALerYlg-3I&e=">https://ceo.hosting/
[ceo.hosting]</a><o:p></o:p></p>
<p><span style="color:black">-------------------------------</span><o:p></o:p></p>
<p><span style="color:black">Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty</span><o:p></o:p></p>
</div>
<p><span style="color:black">Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845</span><o:p></o:p></p>
<p><span lang="EN-GB"> </span><o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">council <</span><a href="mailto:council-bounces@gnso.icann.org"><span style="font-size:12.0pt">council-bounces@gnso.icann.org</span></a><span style="font-size:12.0pt;color:black">>
on behalf of Ayden Férdeline <</span><a href="mailto:icann@ferdeline.com"><span style="font-size:12.0pt">icann@ferdeline.com</span></a><span style="font-size:12.0pt;color:black">><br>
<b>Reply-To: </b>Ayden Férdeline <</span><a href="mailto:icann@ferdeline.com"><span style="font-size:12.0pt">icann@ferdeline.com</span></a><span style="font-size:12.0pt;color:black">><br>
<b>Date: </b>Thursday 4 April 2019 at 11:37<br>
<b>To: </b>GNSO Council List <</span><a href="mailto:council@gnso.icann.org"><span style="font-size:12.0pt">council@gnso.icann.org</span></a><span style="font-size:12.0pt;color:black">><br>
<b>Subject: </b>[council] EPDP list of Observers is incomplete</span><o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>Dear all,<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>At the moment, the list of Observers for the EPDP's mailing list is incomplete.<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>When I have sent messages to the EPDP list, I have received replies from some individuals, seeking to influence me, whose names are not listed on the Observer page as Observers.<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>It is possible that we do not even need to record the names of Observers. Certainly in the case of the pre-IRT, I have suggested that listing their names might be unnecessary - I'm not sure what it really adds. However this is another discussion altogether.<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>If our existing practice in GNSO-chartered working groups is to record the names of Observers, and I believe it is, then I believe this list should be kept complete and up to date.<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>I have asked that the EPDP Observer list be updated and ICANN staff have declined to update the list. The missing names are of ICANN staff members who work in GSE. It apparently would require the support of the GNSO Council to add their names to the page.<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>As these staff are not supporting the EPDP, or at least are not supporting it to my knowledge, but have been reading the emails and seeking to influence EPDP members, then I believe their names should be made public along with the rest of the EPDP Observers,
official staff support, members, and alternates. I do not understand why their names would not be published and I think it is inconsistent with the principles of accountability and transparency that ICANN claims to value.<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>When I have pushed back and asked why these names cannot be added, I was told that it is to keep the wiki page short. However it already has over 200 names so it isn't short at the moment. I prefer to prioritise having a complete list, rather than a concise
one, as in the case of the wiki, there are really no technical restrictions to adding the missing names to the page.<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>We trust, or at least I trust, that when I visit something on the ICANN website, that it will be complete and accurate. If it isn't, I expect there to be a disclaimer or note explaining what it included, so I can make that decision myself as to its accuracy.
The EPDP list of Observers does not state that some people observing the list will not have their names included. If that is the case, there should be a defined policy around who is/is not named, but I see no reason not to include the names of ICANN staff
who are observing the mailing list and seeking to influence discussions behind the scenes.<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>I am sending this message to the Council list because I have been advised by ICANN staff that the Observer list will only be updated if it is the expressed wish of either the GNSO Council or of the EPDP chair. I would like to ask the Council to support this
request please.<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>Thank you.<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>Ayden Férdeline<o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</blockquote>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div dir="ltr"><span>_______________________________________________</span><br>
<span>council mailing list</span><br>
<span><a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a></span><br>
<span><a href="https://mm.icann.org/mailman/listinfo/council">https://mm.icann.org/mailman/listinfo/council</a></span><br>
</div>
</blockquote>
</div>
</div>
</body>
</html>