<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=iso-8859-1">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;}
@font-face
{font-family:"Comic Sans MS";
panose-1:3 15 7 2 3 3 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Comic Sans MS";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</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;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space'>
<div class=Section1>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#1F497D'>Dear Bill and all,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#1F497D'>I would like to say that in two of these 5 teams NCUC has
already representatives. The PDP and the Working Groups teams fall under the
PPSC groups that ICANN has established to assist the GNSO’s new
improvement implementation plans. I am the NCUS representative in the PPSC as a
whole and I also serve in the WG team. Gabriel Piniero is the other NCUC
representative in the PDP team.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#1F497D'>Thanks<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#1F497D'>Konstantinos<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#2E08D2'>Dr. Konstantinos Komaitis</span><span style='font-size:11.0pt;
font-family:"Comic Sans MS";color:#2E08D2'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#2E08D2'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#2E08D2'>Lecturer in IT&T Law, Panellist,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#2E08D2'>Chair Membership Committee,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#2E08D2'>Global Internet Governance Academic Network,</span><span
style='font-size:11.0pt;font-family:"Comic Sans MS";color:#2E08D2'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#2E08D2'>University of Strathclyde,</span><span style='font-size:11.0pt;
font-family:"Comic Sans MS";color:#2E08D2'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#2E08D2'>The Law School,</span><span style='font-size:11.0pt;font-family:
"Comic Sans MS";color:#2E08D2'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#2E08D2'>141 St James Road, </span><span style='font-size:11.0pt;
font-family:"Comic Sans MS";color:#2E08D2'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#2E08D2'>Glasgow G4 0LT.</span><span style='font-size:11.0pt;font-family:
"Comic Sans MS";color:#2E08D2'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Comic Sans MS";
color:#2E08D2'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#2E08D2'>tel:+44 (0)141 548 4306<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#2E08D2'>fax:+44 (0)141 548 3639<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#2E08D2'>email: k.komaitis@strath.ac.uk<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#2E08D2'>http://www.law.strath.ac.uk/staff/bio_sharepoint.aspx?id=75 <o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> Non-Commercial User Constituency
[mailto:NCUC-DISCUSS@LISTSERV.SYR.EDU] <b>On Behalf Of </b>William Drake<br>
<b>Sent:</b> 10 January 2009 11:32<br>
<b>To:</b> NCUC-DISCUSS@LISTSERV.SYR.EDU<br>
<b>Subject:</b> Help Build The New GNSO<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>Begin forwarded message:<o:p></o:p></p>
</div>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><b><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";
color:black'>From: </span></b><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif"'>Glen
de Saint Géry <<a href="mailto:Glen@icann.org">Glen@icann.org</a>></span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><b><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";
color:black'>Date: </span></b><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif"'>January
10, 2009 12:47:59 AM GMT+01:00</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><b><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";
color:black'>To: </span></b><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif"'>Carlos
Affonso Pereira de Souza <<a href="mailto:caffsouza@gmail.com">caffsouza@gmail.com</a>>,
William Drake <<a href="mailto:william.drake@graduateinstitute.ch">william.drake@graduateinstitute.ch</a>></span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><b><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";
color:black'>Cc: </span></b><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif"'>"<a
href="mailto:MWong@piercelaw.edu">MWong@piercelaw.edu</a>" <<a
href="mailto:MWong@piercelaw.edu">MWong@piercelaw.edu</a>>, Glen de Saint
Géry <<a href="mailto:gnso.secretariat@gnso.icann.org">gnso.secretariat@gnso.icann.org</a>></span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><b><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";
color:black'>Subject: </span></b><b><span style='font-size:13.5pt;font-family:
"Helvetica","sans-serif"'>FW: Help Build The New GNSO</span></b><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>Dear Carlos and Bill,<br>
<br>
This is the message that Rob Hoggarth mentioned in the meeting yesterday,
please distribute widely.<br>
Many thanks,<br>
<br>
Glen<br>
[To: council[at]gnso.icann.org; liaison6c[at]gnso.icann.org]<br>
[To: ga[at]gnso.icann.org; announce[at]gnso.icann.org]<br>
[To: regional-liaisons[at]icann.org]<br>
<br>
<a href="http://www.icann.org/en/announcements/announcement-09jan09-en.htm">http://www.icann.org/en/announcements/announcement-09jan09-en.htm</a><br>
Help Build The New GNSO<br>
<br>
Volunteers Are Now Being Accepted To Join Work Teams That Will Develop GNSO
Improvement Implementation Plans<br>
<br>
9 January 2009<br>
<br>
The GNSO is creating five new Work Teams to be the incubators through which
implementation plans for ICANN Board approved GNSO improvement recommendations
can be developed and proposed by members of the ICANN community. Each Work Team
will be made up of community volunteers who have interest in and expertise in
one of five main focus areas: <br>
<br>
Constituency/Stakeholder Group Operations <br>
GNSO Operations <br>
New Working Group Model. <br>
New GNSO Policy Development Process (PDP) <br>
Community Communications and Coordination <br>
We encourage you to participate in one of the Work Teams. <br>
<br>
If you do have an interest in participating, please send a message to
gnso.secretariat@icann.org indicating which Work Team you want to join. Please
include in the message your name, affiliation (constituency or individual),
company/organization, position/title, email address, time zone, telephone
numbers, and describe your specific interest (professional and/or personal) in
joining the team. All personal information will be kept confidential. <br>
<br>
The Work Teams are open to all interested volunteers. Work Team meeting times
will probably overlap, so please consider joining only one Work Team.<br>
<br>
Background information and the scope of each newly chartered team are
summarized below. <br>
<br>
Background Information <br>
<br>
The ICANN Board announced sweeping recommendations for improving the GNSO last
June at their meeting in Paris. The implementation work of the GNSO
Improvements effort is underway and there are many exciting opportunities
available for ICANN community input and support to help achieve the goals and
objectives adopted by the Board. The effort is progressing on four parallel
tracks: <br>
<br>
The GNSO Council is working to develop the transition to a newly structured
GNSO Council by June 2009. <br>
Existing GNSO constituencies are preparing to submit their re-confirmations to
the ICANN Board. <br>
New Stakeholder Groups are developing petitions and charters for ICANN Board
recognition, and <br>
The GNSO is creating five special Work Teams to develop specific proposals,
processes and mechanisms for implementing the ICANN Board's Recommendations. <br>
All four areas require significant investments of time and brainpower from
members of the ICANN community, but the Work Team efforts, in particular, need
an infusion of enthusiasm, passion, expertise and fresh ideas from the entire
community to move the implementation forward. <br>
<br>
Scope of the Work Teams<br>
<br>
Constituency Operations Team (COT) <br>
<br>
This team will develop guidelines and mechanisms to help GNSO constituencies
and stakeholder groups operate in ways that ensure transparency, accountability
and accessibility, including outreach efforts to encourage broader
participation within the GNSO by explaining the added value of membership in
these groups. <br>
<br>
In its Paris recommendations, the Board directed GNSO constituencies to develop
participation rules and operating procedures that set certain minimum standards
regarding transparency and accountability. The Board emphasized that criteria
for participation in any ICANN constituency should be objective, clearly
stated, and standardized. In addition, the Board directed constituencies to
develop global, targeted outreach programs aimed at increasing participation
and interest in the GNSO policy process, including information on the option to
self-form new constituencies. <br>
<br>
Some of the specific recommendations approved by the Board include: <br>
<br>
Develop a global outreach program to broaden participation in current
constituencies. <br>
Enhance existing constituencies by developing recommendations on the following:
<br>
Develop a set of top-level participation guidelines based on the principles as
defined in the GNSO recommendations, while recognizing differences between
constituencies and that one size may not fit all constituencies; and <br>
<br>
Develop a "tool kit" of basic administrative, operational and technical
services available to all constituencies <br>
<br>
Please refer to the draft COT Charter for more information:
https://st.icann.org/icann-osc/index.cgi?constituency_operations_team. <br>
<br>
Communication and Coordination Team (CCT) <br>
<br>
This team will develop tools for increased communication effectiveness and
efficiency within the GNSO and improve GNSO communication and coordination with
other ICANN structures, including members of the ICANN Board, other Supporting
Organizations (SOs) and Advisory Committees (ACs). <br>
<br>
The Board stated that the Council as well as the GNSO constituencies should
consider additional ways in which the GNSO can further improve communication,
cooperation and coordination with other ICANN structures. The Board added that
there should be more frequent contact and communication between the GNSO
Council, GNSO constituencies and the members the Council elects to the Board,
and among the Chairs of the GNSO, other Supporting Organizations and Advisory
Committees especially in advance of each ICANN Meeting. <br>
<br>
Some of the specific recommendations approved by the Board include: <br>
<br>
Improve the GNSO's: <br>
<br>
Web site <br>
Document management capacity <br>
Ability to solicit meaningful public comments on its work <br>
Coordination with other ICANN structures. <br>
Please refer to the draft CCT Charter for more information:
https://st.icann.org/icann-osc/index.cgi?osc_communications_team. <br>
<br>
GNSO Council Operations Team (GCOT) <br>
<br>
This work team will develop any changes needed to the Council's operational
procedures and role in response to the Board approved GNSO structure including
determining what steps are needed to establish the role of the Council as a
"strategic manager of the policy process" and preparing clear rules
for the establishment of new constituencies within stakeholder groups, while
recognizing that differences exist between stakeholder groups and
constituencies. <br>
<br>
The Board recommended that the Council move away from being a legislative body
concerned primarily with voting towards becoming a strategic entity focused on overseeing
and managing Working Groups, which will be primarily engaged in developing
policy for the GNSO. The Council should adopt term limits and implement a
training and development curriculum for its members. <br>
<br>
The Board endorsed a new bicameral voting structure for the newly reorganized
Council comprised of four broad stakeholder groups. It authorized the
establishment of a "contracted party house" (made up of registry and
registrar stakeholder group representatives) and a second "non-contracted
party house" (made up of commercial and non-commercial stakeholder group
representatives) and set parameters for their respective compositions. The
Board also approved the presence of a voting Nominating Committee Appointee
(NCA) in each house and subsequently authorized a third Council-level
non-voting appointee. The Board also approved a methodology for the GNSO
Council to select a Chair and approved various voting thresholds recommended by
the community. <br>
<br>
Some of the specific recommendations approved by the Board include: <br>
<br>
Determine what steps are needed to establish the role of the Council as a
"strategic manager of the policy process." <br>
Define and develop scope and responsibilities of any other standing
"committees" as recommended by the BGC WG (those suggested to date:
committee to analyze trends; committee to benchmark policy implementation) <br>
Develop "Statement of Interest" and "Declaration of
Interest" forms. <br>
Develop curriculum for training Council members, constituents, facilitators and
others. <br>
Prepare clear rules for the establishment of new constituencies within
stakeholder groups, while recognizing that differences exist between
stakeholder groups and constituencies. <br>
Review and recommend amendments as appropriate regarding methods for
encouraging, promoting and introducing new constituencies, while recognizing
that differences exist between stakeholder groups and constituencies. <br>
Please refer to the draft GCOT Charter for more information:
https://st.icann.org/icann-osc/index.cgi?gnso_operations_team. <br>
<br>
Working Group Model Team (WGMT) <br>
<br>
This team will collaborate to develop a new Working Group model for GNSO policy
development and decision making. <br>
<br>
The ICANN Board recommended that Working Groups become the focal point for GNSO
policy development to enhance the process by making it more inclusive and
representative, and, ultimately, more effective and efficient. The Board noted
that this approach can be a more constructive way of establishing areas of
agreement than task forces, where membership is limited and discussion can
become polarized along constituency lines. Working Groups also enable key
parties to become involved in the beginning and work together to address
complex and/or controversial issues. Appointing skilled chairs and drafters, as
well as proper scoping of the Working Group's objectives, will be integral
parts of a successful model. The Board urged that steps be taken immediately to
move to a Working Group model for future policy development work, developing
appropriate operating principles, rules and procedures that can draw upon
expertise gained from other organization's successful policy development
efforts, as appropriate. <br>
<br>
Please refer to the draft WGMT Charter for more information:
https://st.icann.org/gnso_transition/index.cgi?pdp_team. <br>
<br>
Policy Development Process (PDP) Team (PDPT) <br>
<br>
This team will work to develop a more efficient and effective policy
development process for the GNSO community. <br>
<br>
The Board emphasized that the GNSO Policy Development Process (PDP) needs to be
revised to make it more effective and responsive to ICANN's policy development
needs. It should be brought in-line with the time and effort actually required
to develop policy and made consistent with ICANN's existing contracts
(including, but not limited to, clarifying the appropriate scope of GNSO
"consensus policy" development). <br>
<br>
The Board stated that, while the procedure for developing "consensus
policies" will need to continue to be established by the Bylaws as long as
required by ICANN's contracts, the GNSO Council and Staff should develop and
propose new PDP rules for the Board's consideration and approval that contain
more flexibility. The new rules should emphasize the importance of the
preparation that must be done before launch of a Working Group or other
activity, such as public discussion, fact-finding, and expert research in order
to properly define the scope, objective and schedule for a specific policy
development goal, and the development of metrics for measuring success. <br>
<br>
Please refer to the draft PDPT Charter for more information:
https://st.icann.org/gnso_transition/index.cgi?pdp_team<br>
<br>
For additional information about the GNSO Improvements Implementation process
please consult the GNSO Improvements Information Page at
http://gnso.icann.org/en/improvements/<br>
<br>
Glen de Saint Géry<br>
GNSO Secretariat<br>
gnso.secretariat@gnso.icann.org<br>
http://gnso.icann.org<br>
<br>
<o:p></o:p></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Arial","sans-serif";
color:black'>***********************************************************<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Arial","sans-serif";
color:black'>William J. Drake <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Arial","sans-serif";
color:black'>Senior Associate<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Arial","sans-serif";
color:black'>Centre for International Governance<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Arial","sans-serif";
color:black'>Graduate Institute of International and<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Arial","sans-serif";
color:black'> Development Studies<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Arial","sans-serif";
color:black'>Geneva, Switzerland<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Arial","sans-serif";
color:black'><a href="mailto:william.drake@graduateinstitute.ch">william.drake@graduateinstitute.ch</a><o:p></o:p></span></p>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Arial","sans-serif";
color:black'>New book: <i>Governing Global Electronic Networks,</i><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Arial","sans-serif";
color:black'><a href="http://tinyurl.com/5mh9jj">http://tinyurl.com/5mh9jj</a><o:p></o:p></span></p>
</div>
</div>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Arial","sans-serif";
color:black'>***********************************************************<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</body>
</html>