<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=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Tahoma","sans-serif";
color:#1F497D;
font-weight:normal;
font-style:normal;}
.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;}
--></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-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#1F497D'>HI Chuck,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#1F497D'> I strongly agree your statement. we will include our points. Then we will review it and will analysis with the group. <o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#002060'>Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#002060'>G.Kannan<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#002060'>Information security consultant <o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> gnso-rds-pdp-wg-bounces@icann.org [mailto:gnso-rds-pdp-wg-bounces@icann.org] <b>On Behalf Of </b>Gomes, Chuck<br><b>Sent:</b> Tuesday, January 26, 2016 7:29 PM<br><b>To:</b> Alan Greenberg; gnso-rds-pdp-wg@icann.org<br><b>Subject:</b> Re: [gnso-rds-pdp-wg] RDS PDP WG Leadership<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Alan,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I see no problem with leaders being associated with strong views as long as they do not let their strong views impact their ability to lead neutrally. In fact, I strongly believe that it is a positive to have a leadership team made up of those who have strong views on both sides of the two extremes in the Whois debate; provided the leaders are willing to collaborate to facilitate consensus in the whole WG in spite of their strong views, it will force the leadership team to grapple with their competing views just like the whole WG will need to do.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>In the mid 1990’s when generic domain name registrations just started to escalate rapidly, I was managing a customer service team with a group of managers who all had strong views and more often than not disagreed with one another at the outset. But we worked through our differences and found solutions that were ultimately best for the entire team and our customers. The fact that we had strong differences forced us to grapple with our differences constructively and allowed us to more effectively deal with the differences on the entire team of several hundred people.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Chuck<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Alan Greenberg [mailto:alan.greenberg@mcgill.ca] <br><b>Sent:</b> Tuesday, January 26, 2016 8:20 AM<br><b>To:</b> Gomes, Chuck; gnso-rds-pdp-wg@icann.org<br><b>Subject:</b> Re: [gnso-rds-pdp-wg] RDS PDP WG Leadership<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>I often support Chuck in his suggestions on how to structure things, but sadly I cannot in this case.<br><br>As with many others, I agree to the multi-person leadership group, and will not push much for one option over another. And I agree with Liz that those on the team should not be associated with strong views on the outcomes if at all possible.<br><br>But Don is right! Restricting the leadership to GNSO people may be counter productive and will definitely send exactly the wrong message to the overall community. Multi-stakeholderism is not limited to the GNSO, and in the past, we have had PDP WG leaders who were not part of the GNSO (myself included). We may not end up with qualified volunteers from other parts of ICANN, since the workload will be heavy. But a priori excluding them excluding them is ill-conceived on multiple levels.<br><br>Alan<br><br>At 25/01/2016 03:56 PM, Gomes, Chuck wrote:<br><br><o:p></o:p></p><p class=MsoNormal>In my personal capacity as a volunteer for the RDS PDP WG I would like to propose the following approach to the WG leadership that I think would be very helpful in facilitating our productivity:<br>· Have a leadership team consisting of 4 WG members plus the ICANN staff support personnel.<br>· Have one leader from each of the four GNSO Stakeholder Groups (SGs):<br>1. Non-Commercial SG (NCSG)<br>2. Commercial SG (CSG)<br>3. Registrars SG (RrSG)<br>4. Registries SG (RySG).<br>· The four leaders could serve in one of two ways:<br>o 2 co-chairs & 2 co-vice-chairs<br>o 1 chair & 3 co-vice chairs.<br> <br>In recent years in the GNSO, a team leadership approach for WGs and even for the GNSO Council itself has proved to be quite effective. It not only spreads the workload around but more importantly it allows for a small team of experienced people to collaborate together in leading the group’s efforts. Here are a few examples where a collaborative leadership team have been used:<br>· The GNSO Council has a chair plus two vice chairs.<br>· The Policy & Implementation WG had two co-chairs and two vice-chairs.<br>· The CWG Stewardship has two co-chairs.<br>· The CCWG Accountability has three co-chairs.<br> <br>By adding a condition that each of the leadership team members come from different SGs, it ensures that the chairs and vice chairs collectively have expertise about all four of the GNSO stakeholder groups and creates a situation where the leaders are well versed in the varying viewpoints that exist across all four groups as well as differences within their respective groups. I believe that this is especially important for an area such as Registration Data Services (Whois) that has been very controversial over the entirety of ICANN’s history.<br> <br>For those that are new to GNSO policy development processes, any recommendations made by a WG have to eventually be approved by the GNSO Council, which primarily consists of the four SGs. So Having all SGs involved in the leadership of the WG from the beginning should facilitate approval in the end.<br> <br>It is important to remember that the role of the leadership team is to facilitate bottom-up multi-stakeholder policy development in a neutral and effective manner using a consensus based approach. This of course means managing meetings and online work to ensure that the WG charter requirements are satisfied. Hopefully, in most cases this will mean guiding the full group in developing recommendations that most if not all of the WG members can support. But, after diligent efforts to reach consensus, there is still significant divergence about certain proposed recommendations, it will be the leaders responsibility to decide whether there is sufficient support in the WG to submit such recommendations to the GNSO Council. Understanding this, it is important that each SG endorse the person on the leadership team from its group.<br> <br>I hope that we can confirm whether or not there is support for this approach in our WG call tomorrow. If there is, then it will guide our efforts in finding qualified members to serve on the leadership team as well as how to structure the team (2 co-chairs + 2 co-vice-chairs or 1 chair + 3 co-vice-chairs).<br> <br>I would be happy to respond to any questions anyone has.<br> <br>Chuck Gomes<br> <br>P.S. – For those that do not know me, my Statement of Interest (SOI) can be found here: <a href="https://community.icann.org/display/gnsosoi/Chuck+Gomes+SOI">https://community.icann.org/display/gnsosoi/Chuck+Gomes+SOI</a> <br> <br> <br>_______________________________________________<br>gnso-rds-pdp-wg mailing list<br><a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></p></div></body></html>