ICANN/GNSO GNSO Email List Archives

[registrars]


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

Re: [registrars] Registrar Resolution

  • To: "Nevett, Jonathon" <jnevett@xxxxxxxxxxxxxxxxxxxx>, Registrar Constituency <registrars@xxxxxxxxxxxxxx>
  • Subject: Re: [registrars] Registrar Resolution
  • From: Sam BAVAFA <s.bavafa@xxxxxxxxxxxxxxxxxxx>
  • Date: Wed, 21 Mar 2007 07:39:05 +0100
  • In-reply-to: <80450ED06C26C8478670D1053475157A02B43430@VAMAIL3.CORPIT.NSI.NET>
  • Sender: owner-registrars@xxxxxxxxxxxxxx
  • Thread-index: AcdqUYMt6SjeZ+M7SECXMA70o2k7GgAAAeogAAGxZEAAOOJXcAAR8TnV
  • Thread-topic: [registrars] Registrar Resolution
  • User-agent: Microsoft-Entourage/11.3.3.061214

So do we.


Best Regards
Cordialement

www.Domaine.fr
www.Domaine.info
www.DomaiNews.fr



De : "Nevett, Jonathon" <jnevett@xxxxxxxxxxxxxxxxxxxx>
Date : Tue, 20 Mar 2007 18:11:15 -0400
À : Registrar Constituency <registrars@xxxxxxxxxxxxxx>
Conversation : Registrar Resolution
Objet : [registrars] Registrar Resolution

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.






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