RE: [gnso-dt-wg] Re: [council] Motions re Domain Tasting

["Gomes, Chuck" <cgomes@xxxxxxxxxxxx>]

Let me add to Mike's response to Adrian's questions by providing a
little GNSO history.  One of the consistent concerns that has been
expressed in several different GNSO review exercises over the past few
years has been that when we implement policies, we do not adequately
review their effectiveness over time.  In one specific example, the
IRTP, we specifically tried to deal with this concern by including in
the policy recommendation periodic reviews by the GNSO.  In the case of
the New gTLD Committee, several times we discussed the fact that we
would not get it perfect the first time around but that we could learn
from initial implementations and make improvements in future rounds.

Also, I think it is important to recognize that the intent was never
that the Board be the policy making body; that task is given to the
GNSO, albeit that policies can only become policy if the Board approves
them as such.  In the same way, I believe that it should be the GNSO's
responsibility, not the Board's to review policies after they are
implemented to evaluate their effectiveness and decide whether
improvements could be made, etc.

So I personally think that it helpful to build in provisions to ensure
future review of actions we take.

Chuck

-----Original Message-----
From: owner-gnso-dt-wg@xxxxxxxxx [mailto:owner-gnso-dt-wg@xxxxxxxxx] On
Behalf Of Mike Rodenbaugh
Sent: Monday, March 03, 2008 8:19 AM
To: Adrian Kinderis; owner-council@xxxxxxxxxxxxxx; gnso-dt-wg@xxxxxxxxx;
GNSO Council
Cc: Registrars Constituency
Subject: [gnso-dt-wg] Re: [council] Motions re Domain Tasting


Hi Adrian.

The team was me, Kristina, Tim, Alan and recently Jeff Neuman.  Text was
unanimously agreed although i made some minor edits at last turn that
some may not have seen.

There is precedent for Council to monitor implementation of its
policies, and seemed like a good idea for this.

Thanks,
Mike

-----Original Message-----
From: "Adrian Kinderis" <adrian@xxxxxxxxxxxxxxxxxx>

Date: Mon, 3 Mar 2008 14:57:11 
To:"Mike Rodenbaugh" <mxrodenbaugh@xxxxxxxxx>, <gnso-dt-wg@xxxxxxxxx>,
"Council GNSO" <council@xxxxxxxxxxxxxx>
Cc:"Registrars Constituency" <registrars@xxxxxxxxxxxxxx>
Subject: RE: [council] Motions re Domain Tasting



Mike,

I have a few issues with what you have suggested but will wait for the
Registrar Constituency's response prior to proposing them.

That said, I am not sure I understand Part 3 of your motion and would
like some clarification.

I am of the opinion that once the Board decides on supporting a request
or a policy, that it becomes a "Board policy". Why are we instructing
staff to report back to the GNSO council? Surely the Board would want to
grapple with the effectiveness and implications arising out of the
policy "they" implemented. It is up to them, I would think, to set the
parameters of measurement.

I could be wrong, but I thought that we, as the GNSO Council were to
suggest policy and provide background to enable the ICANN Board to make
informed decisions. It is the ICANN Board that makes policy and reviews
the effectiveness of those decisions.

Is it our job to get ICANN staff to report to us on matters of the
Board? 

Also, can you please provide some clarity around "the Design Team"
(perhaps just to remind me again). Who were the members exactly and how
did you arrive at the motion? How was consensus for the actual wording
reached?

Thanks for this and sorry if I am backtracking unnecessarily.

Regards,

Adrian Kinderis
Chief Executive Officer
AusRegistry International Pty Ltd
Level 8, 10 Queens Road
Melbourne. Victoria Australia. 3004
Ph: +61 3 9866 3710
Fax: +61 3 9866 1970
Email: adrian@xxxxxxxxxxxxxxx
Web: www.ausregistryinternational.com

The information contained in this communication is intended for the
named recipients only. It is subject to copyright and may contain
legally privileged and confidential information and if you are not an
intended recipient you must not use, copy, distribute or take any action
in reliance on it. If you have received this communication in error,
please delete all copies from your system and notify us immediately.


-----Original Message-----
From: owner-council@xxxxxxxxxxxxxx [mailto:owner-council@xxxxxxxxxxxxxx]
On Behalf Of Mike Rodenbaugh
Sent: Monday, 3 March 2008 1:33 PM
To: gnso-dt-wg@xxxxxxxxx; 'Council GNSO'
Subject: [council] Motions re Domain Tasting

The Domain Tasting team has devised the following motion, which
effectively would put the attached substantive motion out for public
comments for 21 days and set a timeline for final vote in our April 17
Council meeting.
 
Whereas, the GNSO Council has discussed the Issues Report on Domain
Tasting and the Final Outcomes Report of the ad hoc group on Domain
Tasting;
 
Whereas, the GNSO Council resolved on 31 October 2007 to launch a PDP on
Domain Tasting and to request Constituency Impact Statements with
respect to issues set forth in the Issues Report and in the Final
Outcomes Report;
 
Whereas, the GNSO Council authorized on 17 January 2008 the formation of
a small design team to develop a plan for the deliberations on the
Domain Tasting PDP (the "Design Team"), the principal volunteers to
which had been members of the Ad Hoc Group on Domain Tasting and were
well-informed of both the Final Outcomes Report of the Ad Hoc Group on
Domain Tasting and the GNSO Initial Report on Domain Tasting
(collectively with the Issues Report, the "Reports on Domain Tasting");
 
Whereas, the Design Team has met and agreed on a Draft Motion [attached]
to be set out for public comment and for Constituency Impact review;
 
The GNSO Council RESOLVES:
 
1.    The Draft Motion shall be posted for 21-day public comment on
March 7,
2008.  Each Constituency shall have 21 days from March 7, 2008 to update
its Constituency Impact Statement with respect to this motion, if it so
chooses.
The deadline for amended Statements shall be March 28, 2008.
 
2.    ICANN Staff please shall provide a summary of any public comments
and/or amended Constituency Impact Statements to the Council, via
submission of a Final Report with respect to this PDP, by April 4, 2008.
 
3.    The Design Team shall then meet and confer with respect to the
Final
Report, in order to consider any public comments and/or amended
Constituency Impact Statements and to consider any suggested amendments
to the Draft Motion, and shall recommend a Final Motion to be considered
by Council for vote in its scheduled meeting April 17, 2008.
 
4.    It is the intention of the GNSO for the Staff to produce a Board
Report on this PDP for consideration by the ICANN Board, in the hope
that the Board may vote on any recommendations of the GNSO with respect
to this PDP, at the scheduled ICANN meeting in Paris in June, 2008
 
 
 
Mike Rodenbaugh