ICANN/GNSO GNSO Email List Archives

[dow1tf]


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

[dow1tf] white-list Qs

  • To: "'dow1tf@xxxxxxxxxxxxxx'" <dow1tf@xxxxxxxxxxxxxx>
  • Subject: [dow1tf] white-list Qs
  • From: Paul Stahura <stahura@xxxxxxxx>
  • Date: Tue, 6 Apr 2004 09:56:43 -0700
  • Cc: "'Jeff.Neuman@xxxxxxxxxx'" <Jeff.Neuman@xxxxxxxxxx>
  • Sender: owner-dow1tf@xxxxxxxxxxxxxx

Some off-the-top-of-my-head questions around a centralized white-list:

                                                          

*	Who is the central authority that determines the entities that are
on or off the list?
*	Does this same authority maintain the centralized white-list
database/system?
*	What are the criteria that this authority uses to determine the
list?
*	Is it envisioned that the list be large, say over 300 entities? Or
small, say less than 50?
*	Would registrars be on the list? (they may need to be in order to
perform transfers).  If they are, would the information they have access to
be different than the information other white-list members get?
*	Would registries be on the list?  If yes, do they get only the
information for their names, or all the other TLDs, too?
*	What happens if a rouge white-listed entity mines the data or uses
it for a purpose other than what they specified?
*	Would there still be limits to the queries, or is it once they are
on the list, its all you can eat?  
*	How does it change bulk access, if at all?  If all-you-can-eat, then
there is no need for "bulk" access. Do bulk requestors need to be on the
white-list?  Do bulk requestors get sensitive information? 
*	For entities on the list, can they give/proxy the information to
off-list entities?
*	Can they store the information for long periods of time?
*	Who pays for the implementation of the system?  Would there be a
contribution by the members of the white-list?
*	If white-list members must give the reason for the query, how does
(or can) that information get to the registrants?

 

 

 

 

 

 



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