<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;}
/* 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:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";
color:black;}
.MsoChpDefault
{mso-style-type:export-only;}
@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=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>OK, so my last post on the subject wasn’t my final one. <span style='font-family:"Segoe UI Emoji",sans-serif'>😊</span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I agree with Steph. The problem is that listed affiliation has nothing to do with a person’s experience with ICANN and its processes.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>To make the point, especially for folks who don’t know my ICANN background and some familiar names from other endeavors:</p><p class=MsoNormal>I listed myself as an individual using Steph’s criteria, not employed and not a consultant for a GNSO related group. For my own reasons, I have chosen not to join the SG that does not require commercial relationships as part of their interests (not a criticism. Just covering all the possibilities). On the other hand, I currently or have been</p><p class=MsoNormal>Chair (co-chair when I had to step back) of the Proxy/Privacy Accreditation Services Issues PDP WG</p><p class=MsoNormal>Chair of the Privacy subgroup of the Thick Whois PDP WG</p><p class=MsoNormal>Member of a number of other ICANN WGs</p><p class=MsoNormal>Initially involved in domain name registration system issues in 1998 when with the US FTC</p><p class=MsoNormal>Member of the ICANN Security and Stability Committee</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I can spot other names with significant ICANN experience in the Individuals list, including at least one whose leadership credentials arguably are stronger than mine.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Judging from interest expressed so far, the WP leadership will be from GNSO groups and I see nothing wrong with that. I do have a problem with what to me are arbitrary restrictions on who can serve.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Don</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><br><b>From: </b><a href="mailto:stephanie.perrin@mail.utoronto.ca">Stephanie Perrin</a><br><b>Sent: </b>Wednesday, January 27, 2016 11:40 AM<br><b>To: </b><a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br><b>Subject: </b>Re: [gnso-rds-pdp-wg] RDS PDP WG Leadership</p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>AS someone who is a relative newcomer to ICANN (February 2013) who has participated in quite a few working groups and the EWG, I would like to add that it takes quite a while to understand the community, the processes, and the history at ICANN. I arrived as an "independent expert" with quite a bit of experience in chairing various multi-stakeholder activities, but I would in all humility suggest that chairing or co-chairing an initiative such as this requires a set of skills best gained through experience with ICANN and its processes. Yes we need particular expertise, and that is why the call for participation has been so broad.</span><span style='font-size:12.0pt'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Times New Roman",serif;color:black'><o:p> </o:p></span></p></div></body></html>