RE: [registrars] Registrar Resolution

["Margie Milam" <Margie.Milam@xxxxxxxxxxxxxxx>]

MarkMonitor supports this resolution.

 

Margie

 

  _____  

From: owner-registrars@xxxxxxxxxxxxxx
[mailto:owner-registrars@xxxxxxxxxxxxxx] On Behalf Of Clint Page
Sent: Wednesday, March 21, 2007 10:08 AM
To: registrars
Subject: RE: [registrars] Registrar Resolution

 

Dotster supports this resolution.

 

  _____  

From: Bruce Tonkin [mailto:Bruce.Tonkin@xxxxxxxxxxxxxxxxxx] 
Sent: Tuesday, March 20, 2007 9:20 PM
To: Registrars Constituency
Subject: RE: [registrars] Registrar Resolution

 

Melbourne IT supports this resolution.

	 

	
  _____  


	From: owner-registrars@xxxxxxxxxxxxxx
[mailto:owner-registrars@xxxxxxxxxxxxxx] On Behalf Of Nevett, Jonathon
	Sent: Wednesday, 21 March 2007 9:11 AM
	To: Registrar Constituency
	Subject: [registrars] Registrar Resolution
	Importance: High

	Registrars:

	 

	A number of folks have collaborated in drafting the following
resolution in response to the recent events related to the
de-accreditation of RegisterFly.

	 

	Please indicate if you support the resolution and I will read it
in Lisbon along with a copy of those registrars in support.

	 

	Thanks.

	 

	Jon

	 

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

	Whereas, registrars only succeed if they provide valuable
services to their customers;

	 

	Whereas, registrants must be protected against the potential bad
acts of "fly-by-night" registries and registrars;

	 

	Whereas, it is incumbent on ICANN to protect registrants against
the potential bad acts of "fly-by-night" gTLD registries and registrars;

	 

	Whereas, ICANN Staff has recently formulated a new Compliance
Program for gTLD Registries and Registrars; 

	 

	Whereas, ICANN Staff has recently announced its success in
furthering a data escrow requirement for gTLD registries
http://www.icann.org/announcements/announcement-05mar07.htm;

	 

	Whereas, ICANN Staff has not yet specified a schedule, terms, or
a format of a data escrow requirement for gTLD registrars; 

	 

	Whereas, many registrars currently secure registrant and domain
name data through various back-up methods, but that this practice is by
no means uniform or compulsory across all accredited registrars;

	 

	Whereas, the various back-up methods used by registrars may not
be sufficient in all cases to assist ICANN Staff in recovering such data
in the event of registrar business failure; and

	 

	Whereas, recent events have highlighted the need for a registrar
data escrow program and enhanced compliance efforts with regard to
requirements in the Registrar Accreditation Agreement.

	 

	Be it resolved that the undersigned registrars call for ICANN
Staff to work with the ICANN Registrar Constituency to finalize the
terms of a gTLD registrar data escrow program; and 

	 

	Be it further resolved that the undersigned registrars call for
ICANN Staff to work with the ICANN Registrar Constituency to improve the
effectiveness of the ICANN Compliance Program for gTLD Registrars.