<<<
Chronological Index
>>> <<<
Thread Index
>>>
[council] GNSO Council Restructuring - a wrinkle in the two houses approach
- To: "'Council GNSO'" <council@xxxxxxxxxxxxxx>
- Subject: [council] GNSO Council Restructuring - a wrinkle in the two houses approach
- From: "Philip Sheppard" <philip.sheppard@xxxxxx>
- Date: Mon, 8 Dec 2008 15:38:39 +0100
- In-reply-to: <C7EF85CA4CE9417680AF5B62042BDC19@PSEVO>
- List-id: council@xxxxxxxxxxxxxx
- References: <046F43A8D79C794FA4733814869CDF07027CC366@dul1wnexmb01.vcorp.ad.vrsn.com> <C56199F6.49D2%robert.hoggarth@icann.org> <C7EF85CA4CE9417680AF5B62042BDC19@PSEVO>
- Sender: owner-council@xxxxxxxxxxxxxx
- Thread-index: AclWk5BsnF/k/i7bEEGW3gSB/yew2gALx/OAAHmZBNkAGfQPcAAL+oOw
For discussion
Some recent activity with new organisations seeking involvement inside the GNSO
has opened
up the thought that maybe the delineation of the two house we have currently
proposed is too
narrow. It was based on old thinking.
The two houses are:
a) users
b) ICANN contracted parties
On reflection this division into two does NOT reflect the totality of potential
stakeholders.
A division between:
a) users
b) domain name suppliers
may be a better fit.
The parties with no home in the proposed structure are:
a) applicant registries in the new TLD process (not yet a contract with ICANN)
b) resellers of domain names (with no contract with ICANN)
c) sellers of registry services based on sub-domains (with no contract with
ICANN)
These three categories have little communality with true user interests (a safe
place to
communicate or do business)
and much more with the contracted parties ( eg want to be a registry / shared
customer base
/ focus on registry pricing).
Should we not extend the scope of the contracted parties house to fit these
sort of
organisations inside if the desire is there ?
Philip
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|