ICANN/GNSO GNSO Email List Archives


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

[ga] Registerfly & Data Escrow

  • To: Roberto Gaetano <roberto@xxxxxxxxx>, ga@xxxxxxxxxxxxxx
  • Subject: [ga] Registerfly & Data Escrow
  • From: Danny Younger <dannyyounger@xxxxxxxxx>
  • Date: Tue, 27 Feb 2007 05:20:56 -0800 (PST)
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=ZPpbDMFKzhLf2z4eaAQTe0UnEwhw1JFoMbunDnPDH8d/7pUFfGMRg4p0UiQFT20XcqBhmTLF229G+mvplLteZehzQjPqy4VmRbr1wMPHfPi+40/ftDgl5iaHd7KGBDxcrJLgKUrDkvPuqX6DZ/0VHolPQO6EOKBQcnBVADJKC40=;
  • In-reply-to: <200702262141.l1QLf73F010809@smtp01.icann.org>
  • Sender: owner-ga@xxxxxxxxxxxxxx


I would like to discuss section 3.6 of the Registrar
Accreditation Agreement (Data Escrow) in light of the
documentation breaches cited in ICANN's recent Notice
to registerfly. 

This particular section requires that an electronic
copy of the registrar database be sent to ICANN on a

At issue is whether ICANN has been negligent with
respect to enforcing the data escrow contract language
to the degree that registrants have suffered owing to
such negligence.

The ICANN Notice to registerfly contained this
example:  "the Whois information for the 220
Registered Names held by that party had been changed
to reflect Kevin Medina as the Registered Name Holder
instead of the customer."

If data was routinely escrowed, then no rogue
registrars would be attempting arbitrary WHOIS

My question to you:  Is the registrar community
generally in compliance with data escrow provisions,
or do we still have a major problem that remains
unaddressed by ICANN's Compliance Staff?  

Note:  The last Registrar Compliance Update (October
2006) didn't even mention the word escrow.

Best regards,

The fish are biting. 
Get more visitors on your site using Yahoo! Search Marketing.

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