RE: [gnso-dow123] RE: [council] RE: WHOIS combined task force call 1 March 2005

["Tim Ruiz" <tim@xxxxxxxxxxx>]

Thanks Paul. In fact, the only Registrant data we're required to collect is
the Name and Postal Address.

So as long as the transfer policy is what it is, anything we can do to help
automate the process again would be helpful. Such as making the Registrant
email address available to other registrars, at least going forward.

We might be able to get something changed during the three month review
process, but I'm not counting on that.

Tim


-----Original Message-----
From: owner-gnso-dow123@xxxxxxxxx [mailto:owner-gnso-dow123@xxxxxxxxx] On
Behalf Of Paul Stahura
Sent: Monday, February 28, 2005 1:16 PM
To: Tim Ruiz; Bruce Tonkin
Cc: Chris Disspain; gnso-dow123@xxxxxxxxxxxxxx; council@xxxxxxxxxxxxxx
Subject: RE: [gnso-dow123] RE: [council] RE: WHOIS combined task force call
1 March 2005

Tim, I agree. It should be a requirement that the registrant's email
should be made available to the gaining registrar.
Most registrars, including eNom, collect the email address (and phone
number, etc) of the Registered Name Holder (registrant), but I seem to
remember that is not an ICANN requirement.  I think it could have been
because NSI did not gather that info at the time the agreements were
developed.  I know that showing the registrant's email address is not an
ICANN requirement, but it could be the case that some registrars do not
even have that information so they would not be able to show it, even if
they were required to do so, especially for legacy names prior to a
policy change requiring them to collect and output it.


Paul

-----Original Message-----
From: owner-gnso-dow123@xxxxxxxxx [mailto:owner-gnso-dow123@xxxxxxxxx]
On Behalf Of Tim Ruiz
Sent: Monday, February 28, 2005 2:21 AM
To: Bruce Tonkin
Cc: Chris Disspain; gnso-dow123@xxxxxxxxxxxxxx; council@xxxxxxxxxxxxxx
Subject: RE: [gnso-dow123] RE: [council] RE: WHOIS combined task force
call 1 March 2005

I'd like to point out an issue with the current (new) transfer process
that needs to be considered here.

Right now, there is no requirement to display the email address of the
Registrant in the Whois of gTLDs. So most gaining registrars use the
email address of the Administrative Contact to confirm transfer
requests. The problem we have seen, and I am sure others as well to one
degree or another, is that even after a "good" transfer is completed
(confirmed by the Administrative Contact), the Registrant sometimes
comes forward and says they did not authorize it. Under the current
policy, we have to reverse the transfer or risk going into a dispute
that the gaining registrar will lose and pay for.

Since the Registrant has ultimate authority over a transfer, and that
makes sense, then their email address should at least be available to
Registrars in any tiered access model. At least as long as the transfer
policy is what it is.

Tim

 
-------- Original Message --------
Subject: [gnso-dow123] RE: [council] RE: WHOIS combined task force call
1 March 2005
From: "Bruce Tonkin" <Bruce.Tonkin@xxxxxxxxxxxxxxxxxx>
Date: Sun, February 27, 2005 10:48 pm
To: council@xxxxxxxxxxxxxx
Cc: "Chris Disspain" <ceo@xxxxxxxxxxx>, gnso-dow123@xxxxxxxxxxxxxx

Hello Marilyn,

>  We are also still looking for cc's who use a form of tiered access. 

The WHOIS task force may wish to invite Chris Disspain, the CEO of .au
Domain Administration (auDA) which is the policy body for .au, to
explain the mechanism used in Australia.

.au uses a tiered access structure.

There are three tiers.

(1) public access (see http://whois.ausregistry.com.au/ ), which
provides the following information:

Domain Name: 
Last Modified: 
Registrar ID: 
Registrar Name: 
Status: 
Registrant name: 
Registrant ID: 
Registrant ROID: 
Registrant Contact Name: 
Registrant Email: 
Tech ID: 
Tech Name: 
Tech Email: 
Name Server: 
Name Server IP: 
Name Server:
Name Server IP:

(2) Registrar access.  A registrar can access the full records for the
names under their management, and can also access other registry
records, if the registrant provides them with an access password
(auth_info).  The access password is typically provided by a registrant
that wishes to transfer to the registrar.  The registrar is able to
retrieve the full record as part of the process of authenticating the
transfer request.

(3) Law enforcement access.  An Australian law enforcement agency may
make a request to auDA for access to particular records in writing.
auDA has full access to all records for this purpose.


Regards,
Bruce Tonkin
Registrars representative on the GNSO Council