<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>[registrars] Registrar Restore command reports issue</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText42907 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>What a great question. If
anyone does have such a workaround I would like to know it too. As a congenital
worrier, when I can't find anything else, I can dream nightmare scenarios of the
misuse of the password and the RAT. I have asked on several occasions that the
VeriSign Registry create a more limited tool than the RAT, actually a series of
special use tools. That has not happened.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>We try to protect from abuse by limiting
access to 3 very senior people (which is highly inefficient and a poor use of
their time), very frequent changes (also highly inefficient) and monitoring use
daily by 2 people not in the chain of command of the 3 who have access.
Obviously that system has real holes in it, but it is the best we have come up
with and is cumbersome, leads to misuse of senior assets and is generally
inconvenient for all concerned at the best of times and sometimes creates its
own set of problems. </FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>By the way, I am not one of the 3 senior
people I trust with access. I hope smarter people than me have derived a better
system and will share it. Best to all, Champ</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> owner-registrars@gnso.icann.org on behalf
of Bhavin Turakhia<BR><B>Sent:</B> Tue 12/13/2005 3:59 AM<BR><B>To:</B>
registrars@gnso.icann.org<BR><B>Subject:</B> [registrars] Registrar Restore
command reports issue<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>Hi all<BR><BR>I am wondering if anyone else faces this issue -
especially the bigger<BR>registrars<BR><BR>Right now for running a restore
command a manual report needs to be<BR>submitted using the registrar admin tool.
For a registrar like ourselves, or<BR>say one of the larger ones, there may be
several restores being processed<BR>each week. This requires us to provide the
passwd to the Registrar admin<BR>tool, to someone from our support staff who
handle this task of feeding in<BR>restore reports. That seems like a risky
proposition to me since the RAT<BR>allows complete control over all domain names
and I would not ideally wish<BR>to give its passwd to anyone in the
organization.<BR><BR>Is there a workaround that I am not aware of?<BR><BR>Best
Regards<BR>Bhavin Turakhia<BR>Founder, Chairman &
CEO<BR>Directi<BR>-------------------------<BR><A
href="http://www.directi.com">http://www.directi.com</A><BR><A
href="http://www.logicboxes.com">http://www.logicboxes.com</A><BR>Tel:
+91-22-56797600<BR>Fax: +91-22-56797510<BR>Board (US): +1 (415) 240 4171 ext
7600<BR>Fax (US): +1 (320) 210
5146<BR>-------------------------<BR><BR></FONT></P></DIV>
</BODY>
</HTML>