<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" 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)">
<!--[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:"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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
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:#00B050;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
..MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='color:#1F497D'>The BC will exercise its right
to push any vote on this issue to the next meeting in Jaunuary, as we have not
begun to discuss the issue and therefore have not come to a consensus
position. The issue certainly does not warrant emergency consideration in the
next 7 days, particularly given all of the other issues we are considering
these days.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Also, the PDP-WT should not be
making requests of Council, especially requests that do not have consensus even
of the WT. The PPSC should be evaluating this request now, and should make any
recommendation to Council, if any. This was the process that was agrees when
we formed the PPSC and the WTs, and there is no justification to ignore it now,
simply because a WT Chair, some of its members, and a few ICANN Staff apparently
think this is an emergency to schedule a F2F meeting.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>If Council is going to act on
this request, it must be in the context of our overall prioritization work, and
not on an ‘emergency’ basis as appears to be requested.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span style='color:#1F497D'>Mike Rodenbaugh<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>RODENBAUGH LAW<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>548 Market Street<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>San Francisco, CA 94104<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><a
href="http://service.ringcentral.com/ringme/callback.asp?mbid=57178438,0,&referer=http://rodenbaugh.com/contact"><span
style='color:blue'>(415) 738-8087</span></a><o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt;line-height:13.5pt'><span
style='color:#1F497D'><a href="http://rodenbaugh.com/"><span style='color:blue'>http://rodenbaugh.com</span></a><o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt;line-height:13.5pt'><span
style='color:#1F497D'><o:p> </o:p></span></p>
</div>
<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"'>
owner-council@gnso.icann.org [mailto:owner-council@gnso.icann.org] <b>On Behalf
Of </b>Gomes, Chuck<br>
<b>Sent:</b> Friday, December 11, 2009 6:02 AM<br>
<b>To:</b> council@gnso.icann.org<br>
<b>Cc:</b> Neuman, Jeff; gnso-ppsc-pdp@icann.org<br>
<b>Subject:</b> [council] FW: Support for a PDP Work Team Face to Face Meeting<br>
<b>Importance:</b> High<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Here is a request from Jeff Neuman, chair of the PDP WT and chair
of the PPSC, for a face-to-face (F2F) WT meeting including ICANN travel
funding support. Please ignore a previous version of Jeff's message
distributed on the Council list because it was sent to the Council list
prematurely.</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></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><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Please note that a detailed request is provided in the attached file.
In preparation for our Council meeting on 17 December, please review Jeff's
message below and the attached file for discussion and possible action by the
Council in that meeting. And please forward this message with the
attachment to your respective groups immediately so that they can do the same
and provide Councilors input before 17 December and thereby provide you any
direction they have on this issue.</span><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'><o:p></o:p></span></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><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Note that this request was received after the required deadline in
the Council Operation Procedures so we will have to decide whether to make an
exception to the Procedures before taking any action. The reason for
considering this exception is because the request is for a F2F meeting in
January and to delay a decision until our 7 January meeting would be too late
to allow adequate time for travel plans and other arrangements. Also note
that there are no provisions in any of the documents that govern Council
operation that provide procedures for Council action on issues like this; we
quite possibly will need to consider that topic sometime in the future.
At present though, I believe it is important for the Council to be involved in
this decision because already budgeted GNSO Improvement funds used for this
request would not be available for funding of other such requests in the future
or for other GNSO improvement implementation actions in this fiscal year.
Staff will provide more details on funds available.</span><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></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><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Jeff Neuman has been invited to participate in the 17 December
Council meeting so he can be available to answer questions.</span><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></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><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>In the meantime, I encourage discussion on the Council list.</span><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></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><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Chuck</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><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"'> Neuman, Jeff
[mailto:Jeff.Neuman@neustar.us] <br>
<b>Sent:</b> Thursday, December 10, 2009 9:47 PM<br>
<b>To:</b> Gomes, Chuck<br>
<b>Cc:</b> Glen de Saint Géry; gnso-ppsc-pdp@icann.org; gnso-ppsc@icann.org<br>
<b>Subject:</b> Support for a PDP Work Team Face to Face Meeting</span><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal>Chuck,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Please find enclosed a request by the PDP Work Team for a
face to face meeting in January 2010 which sets forth the rationale for needing
such a working session. This draft was discussed by the PDP Work
Team on e-mail and during two conference calls. Although there was not a
consensus on the request for such a face to face meeting within the PDP WT,
there was strong support from the RySG, the IP Constituency, the ISP
Constituency, ALAC and one of the two Business Constituency representatives
for the reasons stated within the attached document. The Registrar
representatives and 1 of the business constituency representatives were not in
favor of the request. The NCSG generally believes that there could be a
positive benefit from a face to face meeting with the caveats expressed
below. The PDP WT offers no opinion in this document on the general role
of face to face meetings, the Council’s role in approving or supporting
those face to face meetings, etc., but rather focuses on our specific request.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>The request was sent to the full Policy Process Steering
Committee on December 5, 2009, and although no comments were actually received
from any person on the PPSC that was not already a member of the PDP WT, there
were a number of e-mails on various mailing lists on this topic. The
discussions are primarily archived on two lists: (i) the PPSC list (<a
href="http://forum.icann.org/lists/gnso-ppsc/"><span style='color:windowtext'>http://forum.icann.org/lists/gnso-ppsc/</span></a>)
and (ii) the PDP-WT list (the PDP WT list - <a
href="http://forum.icann.org/lists/gnso-ppsc-pdp/"><span style='color:windowtext'>http://forum.icann.org/lists/gnso-ppsc-pdp/</span></a>).
It should be noted that the PPSC as a whole has been inactive since the
formation of the Work Teams early this year. In fact some members of the
PPSC listed at <a
href="https://st.icann.org/icann-ppsc/index.cgi?policy_process_steering_committee_ppsc"><span
style='color:windowtext'>https://st.icann.org/icann-ppsc/index.cgi?policy_process_steering_committee_ppsc</span></a>,
may not be members of the Council or even active in the community. That
is a separate issue that I plan on addressing in the next few weeks. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>The NCSG arguments can be found in full at <a
href="http://forum.icann.org/lists/gnso-ppsc-pdp/msg00241.html">http://forum.icann.org/lists/gnso-ppsc-pdp/msg00241.html</a>.
To summarize, the NCSG has argued that there is not a consensus of the group in
support of (i) the rationale for the Face to Face meeting, (ii) the
appropriateness of holding such a meeting in the United States, and (iii) the
resolution of how many people from each SG or constituency should be funded by
ICANN to attend. The NCSG believes that there should be parity of
representatives funded to attend face to face meetings by Stakeholder Group (as
opposed to by Constituency). Finally, there was a question raised as to
who makes the decisions on holding and funding these types of meetings (the
Work Team, the Steering Committee, the GNSO Council, ICANN Policy Staff, etc.).<o:p></o:p></p>
<p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal>Whether or not we have a face to face meeting, each member
of the PDP WT with the exception of one business constituency representative
believes that the work of the PDP-WT is essential and should be of the highest
priority of the GNSO Council and community. The work being performed in
the WT was work directed to be done ultimately by the Board Governance
Committee as part of the GNSO Improvements Process. The finalization of
the Policy Development Process will guide how all future policy is made under
the new structure and as such should be resolved as quickly as possible.
The review of the PDP is incredibly broad and complex. There are a number
of difficult issues that we have been, and continue to be, tackling in order to
come up with a process acceptable to the global Internet community. The
core group of participants (including ICANN policy staff) are diverse,
knowledgeable, passionate and highly respected members of the community and are
fully committed to seeing this process through to the end regardless of having
this face to face meeting. I have the utmost respect for each member of
the team.<o:p></o:p></p>
<p class=MsoNormal><span style='color:#00B050'><o:p> </o:p></span></p>
<p class=MsoNormal>Please let me know if you have any questions. I would
be happy to make myself available for the Council meeting to address any
questions.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thank you for your consideration of our request.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-top:6.0pt;mso-margin-bottom-alt:auto'><b><span
style='font-size:9.0pt;font-family:"Arial","sans-serif"'>Jeffrey J. Neuman<span
style='color:#3366FF'> , PDP Work Team Chair<br>
</span><span style='color:#068658'>Neustar, Inc. / Vice President, Law &
Policy</span></span></b><span style='font-size:8.5pt;font-family:"Arial","sans-serif";
color:#7D7D7D'><br>
46000 Center Oak Plaza Sterling, VA 20166</span><span style='font-size:8.5pt;
font-family:"Arial","sans-serif";color:gray'><br>
</span><b><span style='font-size:8.5pt;font-family:"Arial","sans-serif";
color:#068658'>Office:</span></b><b><span style='font-size:8.5pt;font-family:
"Arial","sans-serif";color:#333333'> </span></b><span style='font-size:8.5pt;
font-family:"Arial","sans-serif";color:#7D7D7D'>+1.571.434.5772</span><span
style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#000066'> </span><b><span
style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658'>Mobile: </span></b><span
style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D'>+1.202.549.5079</span><span
style='font-size:8.5pt;font-family:"Arial","sans-serif";color:gray'> </span><span
style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#000066'> </span><b><span
style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658'>Fax: </span></b><span
style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D'>+1.703.738.7965</span><span
style='font-size:8.5pt;font-family:"Arial","sans-serif";color:gray'> </span><b><span
style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658'>/</span></b><span
style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#3366FF'> </span><span
style='font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658'><a
href="mailto:jeff.neuman@neustar.biz"><span style='color:#068658'>jeff.neuman@neustar.biz</span></a>
</span><span style='font-size:8.5pt;font-family:"Arial","sans-serif";
color:gray'> </span><b><span style='font-size:8.5pt;font-family:"Arial","sans-serif";
color:#068658'>/</span></b><span style='font-size:8.5pt;font-family:"Arial","sans-serif";
color:#3366FF'> </span><span style='font-size:8.5pt;font-family:"Arial","sans-serif";
color:#068658'><a href="http://www.neustar.biz/"><span style='color:#068658'>www.neustar.biz</span></a></span><span
style='font-size:8.5pt;font-family:"Arial","sans-serif";color:gray'>
<o:p></o:p></span></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div class=MsoNormal><span style='font-size:8.0pt;color:gray'>
<hr size=1 width="100%" noshade style='color:#969696' align=left>
</span></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:6.5pt;font-family:"Arial","sans-serif";color:gray'>The
information contained in this e-mail message is intended only for the use of
the recipient(s) named above and may contain confidential and/or privileged
information. If you are not the intended recipient you have received this
e-mail message in error and any review, dissemination, distribution, or copying
of this message is strictly prohibited. If you have received this communication
in error, please notify us immediately and delete the original message.</span><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>