ICANN/GNSO GNSO Email List Archives

[registrars]


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

RE: [registrars] Registrar Resolution

  • To: Thomas Barrett - EnCirca <tbarrett@xxxxxxxxxxx>
  • Subject: RE: [registrars] Registrar Resolution
  • From: Tim Ruiz <tim@xxxxxxxxxxx>
  • Date: Wed, 21 Mar 2007 11:50:42 -0700
  • Cc: "'registrars'" <registrars@xxxxxxxxxxxxxx>
  • Reply-to: Tim Ruiz <tim@xxxxxxxxxxx>
  • Sender: owner-registrars@xxxxxxxxxxxxxx
  • User-agent: Web-Based Email 4.9.22

Tom, good points and I agree with the concept, but don't see a need to
include it in the resolution. It is really a part of what we need to
discuss for a more effective compliance program (already included in
the resolution). 


Tim 
 

 -------- Original Message --------
Subject: RE: [registrars] Registrar Resolution
From: "Thomas Barrett - EnCirca" <tbarrett@xxxxxxxxxxx>
Date: Wed, March 21, 2007 1:14 pm
To: "'registrars'" <registrars@xxxxxxxxxxxxxx>

EnCirca supports this resolution.
 
However, I feel that the focus on data escrow misses the real issue. 
Data escrow is of little help once names are deleted and re-registered
by third parties.
 
When RegisterFly failed to fund its registry accounts for renewals,
Klaxons and air raid sirens should have been ringing in the Registry
management offices. (they may well have, but what did they do?)
 
This resolution should include Registry participation as well.  i.e.
What are gTLD registries expected to do when they detect such a
problem?
 
For example, Registries need a process they can invoke to suspend
deletion of names so that ICANN has time to consider compliance and
escrow issues.
 
There should be some language like:
 
Be it resolved that the undersigned registrars call for ICANN Staff to
work with the ICANN Registry and Registrar Constituencies to develop a
process that will detect Registrars who are failing to provide required
services to their customers
 
 
Tom Barrett
EnCirca






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