<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Having watched Chuck in action on a couple of the working groups he
has mentioned, I fully endorse his candidature. He does an
excellent job as a neutral chair. I would suggest that, supported
by co-chairs from the various stakeholder groups, we would have a
fair and balanced leadership team for this initiative.<br>
Stephanie Perrin<br>
<br>
<div class="moz-cite-prefix">On 2016-01-28 18:12, Gomes, Chuck
wrote:<br>
</div>
<blockquote
cite="mid:6DCFB66DEEF3CF4D98FA55BCC43F152E4A1D1C23@BRN1WNEXMBX01.vcorp.ad.vrsn.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
<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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I
strongly encourage newcomers to review the information in
the two links Lisa provided. For the most part I think they
are self-explanatory but am quite sure that they will
generate questions. I think I can speak for the more
experience members on the WG, that any of us will be happy
to respond to questions that you may have. No question is
dumb and answers will likely benefit multiple people and
will facilitate more effective participation in our work.<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"">
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a>
[<a class="moz-txt-link-freetext" href="mailto:gnso-rds-pdp-wg-bounces@icann.org">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Lisa Phifer<br>
<b>Sent:</b> Wednesday, January 27, 2016 4:32 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" 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<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Those new to ICANN may also find this
summary web page useful:<br>
<a moz-do-not-send="true"
href="https://www.icann.org/resources/pages/groups-2012-02-06-en">https://www.icann.org/resources/pages/groups-2012-02-06-en<br>
<br>
</a>It expands all of these acronyms and provides links to web
pages for each group.<br>
<br>
For offline reference, you may also find this beginner's guide
useful:<br>
<a moz-do-not-send="true"
href="https://www.icann.org/en/system/files/files/participating-08nov13-en.pdf">https://www.icann.org/en/system/files/files/participating-08nov13-en.pdf</a>
<br>
<br>
Among other things, this guide summarizes each groups' role
and provides points of contact for those who may be interested
in joining a stakeholder group, constituency, supporting
organization, or advisory committee.<br>
<br>
Best Regards,<br>
Lisa<br>
<br>
<br>
At 07:49 AM 1/27/2016, Marika Konings wrote:<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Dear Karnika,<br>
<br>
Thank you for your feedback – it may be helpful to
re-emphasize that participation in this Working Group happens
on an equal footing for all participants, regardless of
whether or not you are affiliated with a GNSO Stakeholder
Group (SG) or Constituency (C) or another ICANN Supporting
Organisation (SO) or Advisory Committee (AC), or no
affiliation at all. What has been discussed by the WG is
whether it would be beneficial to have representation from
GNSO Stakeholder Groups in the WG leadership team as
eventually the WG recommendations will need to be considered
by the GNSO Council which is composed of representatives of
those Stakeholder Groups and as such it may ensure that
particular sensitivities or concerns are dealt with
appropriately by the WG before the recommendations are
finalised for submission. <br>
<br>
In their applications, WG members were asked to indicate their
affiliation (i.e. if you are a member of a GNSO SG/C or
SO/AC). For those not affiliated or not wanting to be
affiliated, those have been identified as individuals. There
is no such category as ‘independent experts’ although the WG
at some point may identify a need to identify, approach and
consult independent experts if it is determined that the
needed expertise is not available within the WG membership.<br>
<br>
I hope this is helpful.<br>
<br>
Best regards,<br>
<br>
Marika <br>
<br>
From: <<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg-bounces@icann.org">
gnso-rds-pdp-wg-bounces@icann.org</a>> on behalf of
karnika <<a moz-do-not-send="true"
href="mailto:karnika@sethassociates.com">
karnika@sethassociates.com</a>><br>
Date: Wednesday 27 January 2016 at 08:13<br>
To: "<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org">
gnso-rds-pdp-wg@icann.org</a>" <<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org">
gnso-rds-pdp-wg@icann.org</a>><br>
Subject: Re: [gnso-rds-pdp-wg] RDS PDP WG Leadership<br>
<br>
Dear Members,<br>
<br>
While I do agree that GNSO has important role here, I
emphasise that leaders from other stakeholder groups must be
equally involved. In order to develop a fair policy practical
experience of each working group member will have a
significant role .Therefore independent cyber law experts or
cyber security experts may be consulted as group member by
segregating the domain /stakeholder group .If I have correctly
understood independent experts will belong to non commercial
category.Please correct me if It is otherwise.
<br>
<br>
I do agree with Mr. Chuck suggestions on creating different
leaders for different teams that will work on the project.<br>
<br>
<br>
With Regards,<br>
<br>
<b>Karnika Seth<br>
</b><i>Cyberlaw expert. & Founding Partner<br>
</i> <br>
<br>
<b>SETH ASSOCIATES<br>
</b>ADVOCATES AND LEGAL CONSULTANTS<br>
<br>
<i>,<br>
</i><img moz-do-not-send="true" id="_x0000_i1025"
src="cid:image001.jpg@01D1593B.040F7740" alt="[]" border="0"
width="226" height="89"><br>
<br>
<b>Website</b>: <a moz-do-not-send="true"
href="http://www.sethassociates.com">www.sethassociates.com</a>
,<a moz-do-not-send="true" href="http://www.lexcyberia.com">
www.lexcyberia.com</a><br>
<b>E-mail</b>: <a moz-do-not-send="true"
href="mailto:mail@sethassociates.com">mail@sethassociates.com</a>,
<a moz-do-not-send="true" href="mailto:mail@lexcyberia.com">mail@lexcyberia.com</a><br>
<br>
<br>
<a moz-do-not-send="true"
href="http://in.linkedin.com/pub/karnika-seth/3/87/110"><span
style="text-decoration:none"><img moz-do-not-send="true"
id="_x0000_i1026"
src="cid:image002.gif@01D1593B.040F7740" alt="[]"
border="0" width="21" height="21"></span></a> <a
moz-do-not-send="true"
href="http://www.linkedin.com/pub/karnika-seth/3/87/110">
LinkedIn</a> <a moz-do-not-send="true"
href="https://www.facebook.com/karnika.seth.1"><span
style="text-decoration:none"><img moz-do-not-send="true"
id="_x0000_i1027"
src="cid:image003.gif@01D1593B.040F7740" alt="[]"
border="0" width="21" height="21"></span></a><a
moz-do-not-send="true"
href="https://www.facebook.com/karnika.seth.1">Facebook</a>
<a moz-do-not-send="true"
href="https://twitter.com/karnikaseth"><span
style="text-decoration:none"><img moz-do-not-send="true"
id="_x0000_i1028"
src="cid:image004.gif@01D1593B.040F7740" alt="[]"
border="0" width="21" height="21"></span></a><a
moz-do-not-send="true"
href="https://twitter.com/karnikaseth">Twitter</a><br>
<br>
<br>
<br>
<br>
<br>
<b>From:</b> <a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a>
[<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg-bounces@icann.org">
mailto:gnso-rds-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Holly Raiche<br>
<b>Sent:</b> 26 January 2016 22:06<br>
<b>To:</b> Alan Greenberg <<a moz-do-not-send="true"
href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>
><br>
<b>Cc:</b> <a moz-do-not-send="true"
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<br>
<br>
I agree with Alan on this - why is this restricted GNSO?<br>
<br>
But I do agree in the need for more than one chair<br>
<br>
Holly<br>
On 27 Jan 2016, at 12:20 am, Alan Greenberg <<a
moz-do-not-send="true"
href="mailto:alan.greenberg@mcgill.ca"><a class="moz-txt-link-abbreviated" href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a></a>
> wrote:<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">I
often support Chuck in his suggestions on how to structure
things, but sadly I cannot in this case.<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">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.<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">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.<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">Alan<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">At
25/01/2016 03:56 PM, Gomes, Chuck wrote:<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">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:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">· Have a
leadership team consisting of 4 WG members plus the ICANN
staff support personnel.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">· Have one
leader from each of the four GNSO Stakeholder Groups (SGs):<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">1.
Non-Commercial SG (NCSG)<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">2.
Commercial SG (CSG)<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">3.
Registrars SG (RrSG)<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">4.
Registries SG (RySG).<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">· The four
leaders could serve in one of two ways:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">o 2 co-chairs
& 2 co-vice-chairs<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">o 1 chair &
3 co-vice chairs.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">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:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">· The GNSO
Council has a chair plus two vice chairs.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">· The
Policy & Implementation WG had two co-chairs and two
vice-chairs.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">· The CWG
Stewardship has two co-chairs.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">· The CCWG
Accountability has three co-chairs.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">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.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">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.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">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.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">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).<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">I would be happy
to respond to any questions anyone has.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Chuck Gomes<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">P.S. – For those
that do not know me, my Statement of Interest (SOI) can be
found here:
<a moz-do-not-send="true"
href="https://community.icann.org/display/gnsosoi/Chuck+Gomes+SOI">https://community.icann.org/display/gnsosoi/Chuck+Gomes+SOI</a><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">_______________________________________________<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">gnso-rds-pdp-wg
mailing list<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><a
moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"><a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a></a><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in"><a
moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"><a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></a><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">_______________________________________________<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">gnso-rds-pdp-wg
mailing list<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><a
moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"><a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a></a><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in"><a
moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"><a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></a><o:p></o:p></p>
<p class="MsoNormal"> <br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<a moz-do-not-send="true"
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>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gnso-rds-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
<br>
</body>
</html>