<<<
Chronological Index
>>> <<<
Thread Index
>>>
[council] Registry services - consensus policy- dot net
- To: <council@xxxxxxxxxxxxxx>
- Subject: [council] Registry services - consensus policy- dot net
- From: "Philip Sheppard" <philip.sheppard@xxxxxx>
- Date: Wed, 27 Jul 2005 16:04:06 +0200
- Cc: "'John Jeffrey'" <jeffrey@xxxxxxxxx>
- In-reply-to: <BAY104-DAV17A3A30A8667BE77323C95D3CC0@phx.gbl>
- Sender: owner-council@xxxxxxxxxxxxxx
- Thread-index: AcWSW2aLCrr7TSv4TVeVIPpk0iwaHwAIAa/wAAdpMcAABl2dYA==
Further to Maria's invitation to post specific questions for ICANN's GC let
me add one further question to the three (repeated 1,2,3 below) already
asked by Marilyn Cade.
Questions
1. What is the situation in terms of the impact of the negotiated terms in
the .net agreement on other contracts, including .com?
2. What is the role of Consensus Policy related to the .net agreement in the
two areas where it appears that there is variance: definition of security
and stability, and Consensus Policy on new registry services: e.g., is there
a time lapse when consensus policy, whatever it is, again is in force?
3. Are other registries actually disadvantaged by being subject to
Consensus Policy in a way that is "disparate" as suggested in Mr. Neuman's
email?
-------
4. The GNSO Council wants to fulfil its duty under the by-laws to develop
Consensus Policy in good faith. How do you advise the GNSO Council to
proceed, if there will indeed be a potential competitive variance between
the treatment of the .net registry and others, with respect to the GNSO
Council's current PDP on Registry Services?
Philip
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|