ICANN/GNSO GNSO Email List Archives

[council]


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

RE: [council] Fast Flux Charter

  • To: <council@xxxxxxxxxxxxxx>
  • Subject: RE: [council] Fast Flux Charter
  • From: "Mike Rodenbaugh" <icann@xxxxxxxxxxxxxx>
  • Date: Wed, 28 May 2008 22:07:10 -0700
  • In-reply-to: <046F43A8D79C794FA4733814869CDF0702452B6C@dul1wnexmb01.vcorp.ad.vrsn.com>
  • List-id: council@xxxxxxxxxxxxxx
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Thread-index: AcjBNg6LPob5H5DHShOmTnPlDfPydAAE6VNg

I am fine with these suggestions, except would delete "at the edge" from the
last addition.

 

Thx,

Mike

 

  _____  

From: owner-council@xxxxxxxxxxxxxx [mailto:owner-council@xxxxxxxxxxxxxx] On
Behalf Of Gomes, Chuck
Sent: Wednesday, May 28, 2008 7:45 PM
To: council@xxxxxxxxxxxxxx
Subject: [council] Fast Flux Charter
Importance: High

 

I would like to suggest the following changes to the Fast Flux charter.

 

Regarding the questions that are part of the Charter:

 

From: How are registry operators involved in fast flux hosting activities? 

To:  Are registry operators involved in fast flux hosting activities?  If
so, how?

 

From: How are registrars involved in fast flux hosting activities?

To:  Are registrars involved in fast flux hosting activities? If so, how?

 

After:  What would be the impact (positive or negative) of establishing
limitations, guidelines, or restrictions on registrants, registrars and/or
registries with respect to practices that enable or facilitate fast flux
hosting?

Add:  What would be the impact of these limitations, guidelines, or
restrictions to product and service innovation at the edge?

Chuck Gomes



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