<html>
<body>
Jon and all,<br><br>
Thanks for drafting this resolution.<br>
Please add DomainIt as a signee.<br><br>
~Paul<br><br>
At 11:00 AM 3/21/2007, Nevett, Jonathon wrote:<br>
<blockquote type=cite class=cite cite="">
<font face="Arial, Helvetica" size=2 color="#000080">Below is an updated
version of the resolution based on the comments to date. So far, I
have the following registrars signing on. Thanks. Jon<br>
<br>
Active 24<br>
Blue Razor Domains<br>
CORE<br>
domaine.fr<br>
EPAG<br>
Go Australia Domains<br>
Go Canada Domains<br>
Go China Domains<br>
Go Daddy<br>
Go France Domains<br>
Go Italy Domains<br>
Melbourne IT<br>
Misk.com<br>
NameKing.com<br>
NameSecure<br>
Network Solutions<br>
Nominalia<br>
OwnRegistrar.com<br>
Register.com<br>
Schlund<br>
SRSplus<br>
Tucows<br>
Wild West Domains<br>
<br>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>
</font><font face="Arial, Helvetica" size=2>Whereas, registrars only
succeed if they provide valuable services to their customers;<br>
<br>
Whereas, registrants must be protected against the potential bad acts of
</font><font face="Arial, Helvetica" size=2 color="#000080">
disreputable</font><font face="Arial, Helvetica" size=2> registries and
registrars;<br>
<br>
Whereas,
</font><font face="Arial, Helvetica" size=2 color="#000080">within the
scope of ICANN’s mission and mandate,
</font><font face="Arial, Helvetica" size=2>it is incumbent on
</font><font face="Arial, Helvetica" size=2 color="#000080">it
</font><font face="Arial, Helvetica" size=2>to protect registrants
against the potential bad acts of
</font><font face="Arial, Helvetica" size=2 color="#000080">
disreputable</font><font face="Arial, Helvetica" size=2> gTLD registries
and registrars;<br>
<br>
Whereas, ICANN Staff has recently formulated a new Compliance Program for
gTLD Registries and Registrars; <br>
<br>
Whereas, ICANN Staff has recently announced its success in furthering a
data escrow requirement for gTLD registries
<a href="http://www.icann.org/announcements/announcement-05mar07.htm">
http://www.icann.org/announcements/announcement-05mar07.htm</a>;<br>
<br>
Whereas, ICANN Staff has not yet specified a schedule, terms, or a format
of a data escrow requirement for gTLD registrars; <br>
<br>
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;<br>
<br>
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<br>
<br>
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.<br>
<br>
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 <br>
<br>
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. <br>
</font><br>
</blockquote></body>
</html>