ICANN/GNSO GNSO Email List Archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

[council] GNSO Review

  • To: <council@xxxxxxxxxxxxxx>
  • Subject: [council] GNSO Review
  • From: "Philip Sheppard" <philip.sheppard@xxxxxx>
  • Date: Thu, 4 Aug 2005 09:22:17 +0200
  • In-reply-to: <BAY104-DAV9AEBEA7852CD4F9FF5272D3C50@phx.gbl>
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Thread-index: AcWXqZRghuCR/uTbTDaMaOPgUQI2CgADAtMgACa5FSAAHPQEoA==

Before we all get carried away on great and good ideas on this review, can
we agree on the scope of the review?

We have already done an ICANN evolution and reform process (ERP) - no one I
HOPE - wants to repeat that in the context of the GNSO ?
We have already done a GNSO Council review and agreed actions as a result -
no one I HOPE - wants to duplicate that ?

Therefore the scope question is surely:
Given the purpose of the GNSO,
Given the current structures / networks / methodology,
How effective are these structures / networks and methods? 

Anything more - such as comparison to other models - I suggest is out of
scope.
That may be relevant if we conclude structures / networks / methods are
broken or useless, but that should inform a second tier of work ONCE the
ineffective bits are identified.

If there is a proposal to repeat the evolution and reform process work for
the GNSO, I plan a long holiday.

Philip



<<< Chronological Index >>>    <<< Thread Index >>>