<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Re: [council] Draft Statement of Work for Funnel Review</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3492" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=715351215-26012009><FONT face=Arial
color=#0000ff size=2>A number of us were not privy to the communications to
staff regarding problems with the RSEP. Would either Staff or the RyC please
share the examples provided? Many thanks.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> owner-council@gnso.icann.org
[mailto:owner-council@gnso.icann.org] <B>On Behalf Of </B>Stéphane Van
Gelder<BR><B>Sent:</B> Monday, January 26, 2009 10:08 AM<BR><B>To:</B> Patrick
Jones<BR><B>Cc:</B> council@gnso.icann.org<BR><B>Subject:</B> Re: [council]
Draft Statement of Work for Funnel Review<BR></FONT><BR></DIV>
<DIV></DIV><FONT face="Verdana, Helvetica, Arial"><SPAN
style="FONT-SIZE: 10pt">Dear Patrick,<BR><BR>Although I am not as familiar
with the subject as Chuck undoubtedly is, I do tend to have to agree with his
concerns over seeing yet another review initiated if the process being
reviewed has already been identified as flawed.<BR><BR>I am also worried about
seeing staff decide a review is needed without being so directed by the Board
or by any action from the relevant SO Council, in this case the
GNSO.<BR><BR>Chuck mentions that staff was made aware of problems with RSEP
before and during the Cairo meeting. Could you explain why staff’s reaction to
this was to feel an outside consultant need be hired and a full review process
initiated? Is it not feasible to try and address the problems that have been
brought to staff’s attention first?<BR><BR>Thanks,<BR><BR>Stéphane Van
Gelder<BR><BR><BR>Le 25/01/09 16:29, « Gomes, Chuck » <<A
href="cgomes@verisign.com">cgomes@verisign.com</A>> a
écrit :<BR><BR></SPAN></FONT>
<BLOCKQUOTE><SPAN style="FONT-SIZE: 10pt"><FONT color=#0000ff><FONT
face=Arial>Patrick,<BR></FONT></FONT><FONT
face="Verdana, Helvetica, Arial"><BR></FONT><FONT color=#0000ff><FONT
face=Arial>Please don't take my comments personally because as I stated
publicly in Cairo, I do not attribute my concerns to anything you did in
coordinating the RSEP.<BR></FONT></FONT><FONT
face="Verdana, Helvetica, Arial"><BR></FONT><FONT color=#0000ff><FONT
face=Arial>Regular reviews of policy are a good practice, but in this case
it seems like overkill and a poor use of funds to hire a consultant to
evaluate the policy or the procedures. In my opinion, Staff
implementation of the RSEP has already been identified as a problem and we
do not need a high priced consultant to point that out. As stated in
your SoW, "</FONT></FONT></SPAN><FONT face=Arial><FONT size=4><SPAN
style="FONT-SIZE: 11pt">The RSEP and its implementation were developed in
particular: To support a timely, efficient, and open process for the
evaluation of new registry services</SPAN></FONT><FONT color=#0000ff><SPAN
style="FONT-SIZE: 10pt">". In 2008, we had at least three examples
where implementation of the RSEP was not timely, efficient or open.
All three examples were pointed out to ICANN Staff prior to Cairo and
in Cairo. So again, we do not need a consultant to identify the
problem; it has already happened.<BR></SPAN></FONT></FONT><SPAN
style="FONT-SIZE: 10pt"><FONT
face="Verdana, Helvetica, Arial"><BR></FONT><FONT color=#0000ff><FONT
face=Arial>Those of us in the RyC believe that the RSEP procedures that
ICANN Staff should follow were clear, but obviously they were not clear
enough for ICANN Staff, otherwise we would not have seen the significant
delays that were experienced for three registry service proposals.
Therefore, maybe all we need to do is provide the clarity that ICANN
Staff seems to need. That shouldn't be too difficult. I think it
could be done in fairly short order by a small group of interested GNSO and
ICANN Staff with the opportunity for public comment. It may not even
be necessary to amend the policy as long as the clarified procedures are
consistent with the policy as is, something that I sincerely believe is very
possible.<BR></FONT></FONT><FONT
face="Verdana, Helvetica, Arial"><BR></FONT><FONT color=#0000ff><FONT
face=Arial>Chuck<BR></FONT></FONT><FONT
face="Verdana, Helvetica, Arial"><BR></FONT></SPAN>
<BLOCKQUOTE><SPAN style="FONT-SIZE: 10pt"><FONT
face="Verdana, Helvetica, Arial"><BR> <BR>
<HR align=center width="100%" SIZE=3>
</FONT><FONT face="Tahoma, Verdana, Helvetica, Arial"><B>From:</B> <A
href="owner-council@gnso.icann.org">owner-council@gnso.icann.org</A>
[<A
href="mailto:owner-council@gnso.icann.org">mailto:owner-council@gnso.icann.org</A>]
<B>On Behalf Of </B>Patrick Jones<BR><B>Sent:</B> Saturday, January
24, 2009 8:21 PM<BR><B>To:</B> <A
href="council@gnso.icann.org">council@gnso.icann.org</A><BR><B>Subject:</B>
[council] Draft Statement of Work for Funnel Review<BR></FONT><FONT
face="Verdana, Helvetica, Arial"><BR> <BR></FONT></SPAN><FONT
size=4><FONT face="Calibri, Verdana, Helvetica, Arial"><SPAN
style="FONT-SIZE: 11pt">Dear Council,<BR><BR>At the 20 November 2008 GNSO
Council meeting, ICANN staff alerted Council members that efforts
were underway to initiate a review of the gTLD registry funnel
process – also known as the Registry Services Evaluation Policy
(RSEP) - that was first implemented in July 2006.<BR> <BR>Staff
reminded Council members that the RSEP was developed through the
GNSO’s policy development process, and applies to all gTLD
registries and registry sponsoring organizations under contract with
ICANN.<BR> <BR>The adoption of the RSEP by the ICANN Board did
not call for a periodic review of the process, but ICANN staff is of
the opinion that a review is consistent with ICANN’s continuing
efforts to evaluate and improve policies and
procedures.<BR> <BR>A draft statement of work regarding the
review has now been developed. The document will be used to
identify and retain a reviewer to evaluate the process as it has
worked to date.<BR> <BR>In view of the GNSO Council’s critical
role in developing the original RSEP, staff would like to give
Council members the opportunity to review and comment on the draft
document. A copy of the draft SOW is attached. Please feel
free to send any comments on the document directly to
me.<BR> <BR>An announcement will be made when the SOW is
released and subsequent announcements will be made when the reviewer
is selected and when other milestones in the review process take
place. <BR> <BR>Also, if you are interested in being identified
as a possible contact for the review process itself, please let me
know of your interest. We hope to finalize the SOW in late
February, so any comments should be submitted by 23 February in
order to be incorporated.
<BR><BR>Patrick<BR><BR></SPAN></FONT></FONT></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>