(fwd) Re: [wg-c] STRAW POLL VOTE

[Paul Garrin <pg@name-space.com>]

------- Forwarded Message

From: Paul Garrin <pg@name-space.com>
To: Jonathan Weinberg <weinberg@mail.msen.com>
Bcc: 
Subject: Re: [wg-c] STRAW POLL 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <22883.951473081.1@mail.lokmail.net>
Date: Fri, 25 Feb 2000 05:04:41 -0500


> QUESTION ONE

  (write-in category)
  5.  Some gTLDs may have charters while others not, as determined by
  the registry offering services for the gTLD.  A gTLD should not be
  required to have a charter that limits the universe of registrants
  who may register in the gTLD.

> QUESTION TWO

  (write-in category)
  5. There may be both chartered and non chartered gTLDs in the initial
  rollout considering that gTLDs are not required to have charters.
  Registries may elect to support chartered and non-chartered gTLDs.

> QUESTION THREE

> 6. Other (please explain).
  Existing new gTLD registry operators establish a testbed for a shared
  registry system for new gTLDs along with a plan for deployment of a large
  number of gTLDs supported by such system.  ICANN may review the registries
  for technical and business compliance in the way that it presently accredits
  legacy domain ("com." "org." "net.") registrars.  Selection of the gTLDs
  should be based on market demand and the best practice technical
  implementations that assure stability in the scaling of the DNS.


- --Paul Garrin


- ---------------------------------------------------------------------------

> WG-C STRAW POLL
> 
> Please respond before midnight UTC following February 21, 2000.
> 
> 
> QUESTION ONE
> 	Please select from the following possibilities, *as applied to the
> deployment of new gTLDs in the name space over the medium to long term*:
> 
> 1. All new gTLDs must have charters that meaningfully limit the universe of
> people who can register in those gTLDs.
> 
> 2. The name space should not include any new chartered gTLDs.
> (Alternatively, if new gTLDs have charters, those charters may not place
> meaningful limits on the universe of people who can register in the gTLD.)
> 
> 3. ICANN, in selecting new gTLDs, should approve some chartered gTLDs and
> some unchartered ones.  (Alternatively, ICANN should require that all gTLDs
> have charters, but it should approve some gTLDs with charters that
> meaningfully limit the universe of people who can register in the gTLD, and
> some gTLDs with charters that do not impose any such limits.)
> 
> 4. ICANN should simply select new registries and leave issues of names and
> charters (including whether to limit the universe of people who can
> register in the domain, and if so how) to the new registries.
>

  5.  Some gTLDs may have charters while others not, as determined by
  the registry offering services for the gTLD.  A gTLD should not be
  required to have a charter that limits the universe of registrants
  who may register in the gTLD.

 
> 
> QUESTION TWO
> 	The working group has reached and reaffirmed a recommendation that the
> initial expansion of the name space should consist of six to ten new gTLDs,
> followed by an evaluation period.  Please select from the following
> possibilities, *as applied to that initial rollout*.
> 
> 1. All of the gTLDs in the initial rollout must have charters that
> meaningfully limit the universe of people who can register in those gTLDs.
> 
> 2. The initial rollout should not include any new chartered gTLDs.
> (Alternatively, any charters for new gTLDs may not place meaningful limits
> on the universe of people who can register in the gTLD.)
> 
> 3. ICANN, in selecting new gTLDs in the initial rollout, should approve
> some chartered gTLDs and some unchartered ones.  (Alternatively, ICANN
> should require that all gTLDs have charters, but it should approve some
> gTLDs with charters that meaningfully limit the universe of people who can
> register in the gTLD, and some gTLDs with charters that do not impose any
> such limits.)
> 
> 4. ICANN should simply select new registries and leave issues of names and
> charters (including whether to limit the universe of people who can
> register in the domain, and if so how) to the new registries.
>

  5. There may be both chartered and non chartered gTLDs in the initial
  rollout considering that gTLDs are not required to have charters.
  Registries may elect to support chartered and non-chartered gTLDs.

 
> 
> QUESTION THREE
> 	The issue of chartered gTLDs is tied up with the larger issue of how ICANN
> should select new gTLDs -- in particular, whether (a) ICANN itself should
> be the final arbiter of new gTLDs' names and charters, or (b) ICANN should
> simply select new registries and leave the choice of names and charters to
> them.  I think that at this point we can't avoid confronting the larger
> question of how ICANN should pick new TLDs in the initial rollout.
> (Actually, we're returning to the question; part of last summer's straw
> poll spoke to the same issue.  The results then were inconclusive.)  Please
> select from among these possibilities:
> 
> 1. ICANN picks a set of registries according to objective criteria.
> (Alternatively, ICANN narrows the set of applicants using objective
> criteria, and chooses among the remaining applicants, if necessary, via
> lotteries or auctions).  Once chosen, registries pick their own gTLD names
> and associated charters (if any), subject to a process under which ICANN
> can resolve conflicts and can deem certain gTLD strings out of bounds.
> 
> 2. ICANN, through a working group or otherwise, identifies a set of gTLDs
> to be introduced in the initial rollout, and establishes names and charters
> for those new TLDs.  It solicits applications from would-be registries to
> run those TLDs, and picks the ones it deems best-suited or best- qualified.
> 
> 3. ICANN, through a working group or otherwise, identifies a set of gTLDs
> to be introduced in the initial rollout, and establishes names and charters
> for those new TLDs.  It solicits applications from would-be registries to
> run those TLDs, and picks those registries through a lottery or auction
> process.
> 
> 4. Each would-be registry proposing a new gTLD applies to the Names Council
> (or to ICANN directly) for approval; if the gTLD is to be bounded by a
> charter, the applicant must supply one.  If the application is approved,
> the applicant becomes the new registry, subject to its proposed charter.
> 
> 5. Each person proposing a new gTLD applies to the Names Council for the
> formation of a working group devoted to that gTLD (or to several gTLDs).
> The working group identifies a registry/sponsor, and generates a charter,
> for its proposed new TLD.  If the gTLD is approved, then the entity
> identified by the working group becomes the registry/sponsor.  The identity
> of the registry operator may be set for competitive bid (and periodic rebid).
> 
> 6. Other (please explain).
  Existing new gTLD registry operators establish a testbed for a shared
  registry system for new gTLDs along with a plan for deployment of a large
  number of gTLDs supported by such system.  ICANN may review the registries
  for technical and business compliance in the way that it presently accredits
  legacy domain ("com." "org." "net.") registrars.  Selection of the gTLDs
  should be based on market demand and the best practice technical
  implementations that assure stability in the scaling of the DNS.




------- End of Forwarded Message