ICANN/GNSO GNSO Email List Archives

[registrars]


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

RE: [registrars] unsanctioned whois concepts (long)

  • To: "'Christopher Ambler'" <chris@xxxxxxxxxx>, <ross@xxxxxxxxxx>
  • Subject: RE: [registrars] unsanctioned whois concepts (long)
  • From: "Tim Ruiz" <tim@xxxxxxxxxxx>
  • Date: Thu, 30 Oct 2003 23:44:57 -0600
  • Cc: "'Rick Wesson'" <wessorh@xxxxxx>, <markjr@xxxxxxxxxxx>, <registrars@xxxxxxxx>
  • Importance: Normal
  • In-reply-to: <8C56D6F8CD834FE-378-22A1@App1>
  • Sender: owner-registrars@xxxxxxxxxxxxxx

Ross,

If you were referring to the transfer key system I was proselytizing
about, I see some of the benefits as follows:

Eliminates the attempt to double confirm and reduces confusion.

More reliable and quicker confirmation resulting in fewer disputes. The
losing registrar is in the best position to confirm.

Faster, almost immediate completion of the transfer.

Whois data accuracy improved as it can be collected directly from the
registrant by the gaining registrar. The key confirms the validity of
the transfer so why force the import of potentially outdated or poorly
parsed data?

A dynamically generated, one use key is more secure than a static auth
code for transfers.

Tim



-----Original Message-----
From: Christopher Ambler [mailto:chris@xxxxxxxxxx] 
Sent: Thursday, October 30, 2003 8:41 PM
To: ross@xxxxxxxxxx
Cc: 'Rick Wesson'; 'Tim Ruiz'; markjr@xxxxxxxxxxx; registrars@xxxxxxxx
Subject: RE: [registrars] unsanctioned whois concepts (long)

>Much clearer - thanks. I'm still short on understanding wrt the 
>specifics of the delta between present and desired state, but I guess
it 
>can wait until you actually make a proposal ;)

I'm writing it up over the weekend. And, to be clear, Tim's comments on
using a key for transfers is a separate issue, though I've noted that
what
I'll be proposing would dovetail with it nicely, and I'll be noting that
in
my writeup.

Christopher







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