ICANN/GNSO GNSO Email List Archives

[registrars]


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

RE: [registrars] Registrar Resolution

  • To: "Thomas Barrett - EnCirca" <tbarrett@xxxxxxxxxxx>, "registrars" <registrars@xxxxxxxxxxxxxx>
  • Subject: RE: [registrars] Registrar Resolution
  • From: "Nevett, Jonathon" <jnevett@xxxxxxxxxxxxxxxxxxxx>
  • Date: Wed, 21 Mar 2007 17:21:13 -0400
  • In-reply-to: <038301c76bfc$11ee9ed0$6500a8c0@blackdell>
  • References: <20070321115041.4a871ae7d05d2c98d9abb595d392cd69.8f0246cded.wbe@email.secureserver.net> <038301c76bfc$11ee9ed0$6500a8c0@blackdell>
  • Sender: owner-registrars@xxxxxxxxxxxxxx
  • Thread-index: Acdr6pnJ1kOkF0BTSfO16/bkRJJflgAERgKAAACC5HA=
  • Thread-topic: [registrars] Registrar Resolution

Tom:  It is entirely consistent that both ICANN and the RC are calling
for changes.  The resolution has been shared with ICANN, is available on
the registrar public list, has been published on the ICANN GA public
list, and will be shared publicly in Lisbon at a workshop on Monday on
these issues.  Thanks.  Jon

-----Original Message-----
From: owner-registrars@xxxxxxxxxxxxxx
[mailto:owner-registrars@xxxxxxxxxxxxxx] On Behalf Of Thomas Barrett -
EnCirca
Sent: Wednesday, March 21, 2007 5:01 PM
To: 'registrars'
Subject: RE: [registrars] Registrar Resolution

 
This resolution appears to be too little, too late.  Check out the
recent
notice from ICANN:

http://www.icann.org/announcements/announcement-21mar07.htm

Ideally, the RC should send a formal response before the Lisbon meeting
to
have it posted on icann.org.

Tom


-----Original Message-----
From: owner-registrars@xxxxxxxxxxxxxx
[mailto:owner-registrars@xxxxxxxxxxxxxx] On Behalf Of Tim Ruiz
Sent: Wednesday, March 21, 2007 2:51 PM
To: Thomas Barrett - EnCirca
Cc: 'registrars'
Subject: RE: [registrars] Registrar Resolution

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 >>>