<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE>Re: [registrars] FW: Registrar Failover Working Group Invitation</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>I'll participate as well. Thanks. Jon<BR>
<BR>
-----Original Message-----<BR>
From: Ross Rader [<A HREF="mailto:ross@tucows.com">mailto:ross@tucows.com</A>]<BR>
Sent: Sat Mar 18 09:23:43 2006<BR>
To: Bhavin Turakhia<BR>
Cc: registrars@gnso.icann.org<BR>
Subject: Re: [registrars] FW: Registrar Failover Working Group Invitation<BR>
<BR>
Before we commit to sending representatives, we should inquire regarding<BR>
who else will be on this "working group". This is purely a registrar<BR>
matter and not a policy development exercise. Participation in the<BR>
exercise should be limited as closely as possible to ICANN technical and<BR>
operational staff and members of the registrar community.<BR>
<BR>
In parallel, we should also discuss, prior to meeting with this working<BR>
group, the appropriateness and scope of these provisions. In reading<BR>
them again, I'm struck by how exceptionally vague and one-sided they<BR>
are. I would not agree to these terms in a normal commercial agreement.<BR>
<BR>
I would also like to participate in this effort.<BR>
<BR>
Bhavin Turakhia wrote:<BR>
> Hi all,<BR>
><BR>
> Have recvd the below email from ICANN. This is an important item since it<BR>
> results in a compliance cost for registrars, and at the same time the<BR>
> provision ensures stability. Any volunteers from the constituency for this<BR>
> task force?<BR>
><BR>
> bhavin<BR>
><BR>
> -----Original Message-----<BR>
> From: Mike Zupke [<A HREF="mailto:mike.zupke@icann.org">mailto:mike.zupke@icann.org</A>]<BR>
> Sent: Wednesday, March 15, 2006 8:24 PM<BR>
> To: 'Bhavin Turakhia'<BR>
> Cc: 'Tim Cole'<BR>
> Subject: Registrar Failover Working Group Invitation<BR>
><BR>
> Dear Bhavin,<BR>
><BR>
> In furtherance of our mission to promote stability in the domain name space,<BR>
> ICANN is beginning preparations to launch a registrar failover program. We<BR>
> hope to involve the Registrars' Constituency in these early stages so that<BR>
> the program will best take into account the needs the registrar community.<BR>
><BR>
> As you are probably aware, paragraph 3.6 of the Registrar Accreditation<BR>
> Agreement calls for all accredited registrars to escrow certain domain name<BR>
> registration data with ICANN or an ICANN-approved escrow services provider<BR>
> on a schedule established by ICANN. Until now, ICANN has never invoked this<BR>
> provision of the RAA. Some time ago, a working group drafted specifications<BR>
> and proposed procedures for a data escrow program, but the project has not<BR>
> advanced beyond the planning stages due to budget constraints. <BR>
><BR>
> We now wish to revisit and update the original working group's<BR>
> recommendations as we look to implement data escrow and a broader registrar<BR>
> failover plan. To do this, we would like to request participation from<BR>
> members of the registrar community in a working group that will meet<BR>
> initially at the ICANN meeting in Wellington, New Zealand, and thereafter by<BR>
> telephone and email.<BR>
><BR>
> Would you kindly solicit the membership of your constituency for interest in<BR>
> participation in this working group and forward to me a list of volunteers?<BR>
><BR>
> Thank you for your help with this. <BR>
><BR>
> Best regards,<BR>
><BR>
> Mike Zupke<BR>
> Registrar Liaison Manager<BR>
> Internet Corporation for Assigned Names and Numbers<BR>
> 4676 Admiralty Way; Suite 330<BR>
> Marina del Rey, California 90292, USA<BR>
> <BR>
> <BR>
><BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>