Patricio,
Thank you for your notes below.
Given that I have had no further comment I have sent the draft
out to members with a couple of minor grammatical changes and the removal of
the paragraph in 9 which mentioned stacking of membership.
I have also amended the response to 4. The use of the word ‘research’
was unfortunate. I have changed it to ‘experience’ and was
intending the comment to refer to the experience of the ccNSOs Participation WG
and generally.
I’m not sure if you were intending there to be amendments
flowing from your other comments. Let men know if you are suggesting any
specific changes.
I think it would be most useful for the council to discuss your
thoughts below re PDP and terms at our next council workshop.
Cheers,
Chris Disspain | Chief Executive Officer
.au Domain Administration Ltd
T: 1300 732 929 | F:
03 8341 4112
E: ceo@auda.org.au | W:www.auda.org.au
auDA - The Australian Domain Name Administrator
Important Notice - This
email may contain information which is confidential and/or subject to legal
privilege, and is intended for the use of the named addressee only. If you are
not the intended recipient, you must not use, disclose or copy any part of this
email. If you have received this email by mistake, please notify the sender and
delete this message immediately. Please consider the environment before
printing this email.
From: owner-ccnso-council@icann.org
[mailto:owner-ccnso-council@icann.org] On Behalf Of Patricio Poblete
Sent: Friday, 27 August 2010 02:39
To: ccNSO Council
Cc: Bart Boswinkel
Subject: Re: [ccnso-council] Response ITEMS Final Report (ccNSO Review)
Dear all,
I have a few comments about the proposed response.
First of all, I believe the note should begin "The
ccNSO Council welcomes..." instead of "The ccNSO welcomes...".
About Recommendation 1: The recommendation does not
distinguish between two things that are very different: (1) more streamlined
policy developing mechanisms, and (2) formal mechanisms to generate non-binding
comments and positions. About (2), I think it might be a good idea to make such
mechanisms explicit. Today we do this by a variety of means, ranging from an
improvised answer to a question from the board during breakfast to a formal
resolution of the council. About (1), Chris is right that this is a delicate
issue, and we should not tinker with it unnecessarily, but on the other hand I
cannot help feeling that something is not right if a PDP for the simplest thing
takes years and years. This means that, in practice, if something really
important and urgent needs to be done, it has to bypass the PDP mechanism in
some other ad-hoc way, like the Fast Track. I would not be against
*considering* if the PDP mechanism can be optimized.
About Recommendation 4: "Lastly, the ccNSO’s own
research shows that there is a very high opportunity cost associated
with attempting to significantly increase membership." Is there a
link to this research?
About Recommendation 9: As a long-time council member from a
region with a reasonably large number of ccNSO members, I think we could at
least have recommended term limits. It is easy to just keep asking the same
person to be the representative, but if there is a motivation to look for a
different one, usually suitable candidates appear. Personally, I will probably
provide such an incentive to my colleagues when my current term ends.
Patricio
__________ Information from ESET Smart Security, version of virus signature
database 5400 (20100826) __________
The message was checked by ESET Smart Security.
http://www.eset.com
__________ Information from ESET Smart Security, version of virus signature
database 5394 (20100824) __________
The message was checked by ESET Smart Security.
http://www.eset.com
__________ Information from ESET Smart Security, version of virus signature
database 5400 (20100826) __________
The message was checked by ESET Smart Security.
http://www.eset.com
__________ Information from ESET Smart Security, version of virus signature
database 5401 (20100827) __________
The message was checked by ESET Smart Security.
http://www.eset.com