ICANN/GNSO GNSO Email List Archives

[registrars]


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

RE: [registrars] FW: [dow1tf] TR: IPC constituency statement for Whois TF1

  • To: "'ross@xxxxxxxxxx'" <ross@xxxxxxxxxx>, Tim Ruiz <tim@xxxxxxxxxxx>
  • Subject: RE: [registrars] FW: [dow1tf] TR: IPC constituency statement for Whois TF1
  • From: Paul Stahura <stahura@xxxxxxxx>
  • Date: Tue, 30 Mar 2004 18:13:31 -0800
  • Cc: registrars@xxxxxxxx
  • Sender: owner-registrars@xxxxxxxxxxxxxx

What happens with thick registries?
.com and .net will switch to EPP, and who knows, probably thick EPP.
Do we get to choose "b allow registrars to manage the service as they see
fit" by not providing them with the whois information?
Are you proposing we be allowed to not give the info to anyone?  Or are you
saying they we give it to them (registries) but they cannot setup port-43
access to it (just web based access, presumably with appropriate anti-mining
measures in place)?
Also Tim, you said severely restricted if not shut off port-43.  What does
severely restricted mean to you?  For example, if TF2 says the data output
is just name, dns pointers, and registrar (no personally identifiable
stuff), is that sufficient to not be turned off completely?

I wouldn't mind having a conf call on this so we can discuss at high
bandwidth.  If interested, let me know and I will set it up.

Paul

-----Original Message-----
From: Ross Wm. Rader [mailto:ross@xxxxxxxxxx] 
Sent: Tuesday, March 30, 2004 3:10 PM
To: Tim Ruiz
Cc: 'Paul Stahura'; registrars@xxxxxxxx
Subject: Re: [registrars] FW: [dow1tf] TR: IPC constituency statement for
Whois TF1

On 3/30/2004 5:49 PM Tim Ruiz noted that:

> Ross,
> 
> To be clear, I think port 43 should only be used to facilitate transfers.
> Your option b) below would be a good second best as long as it included
not
> having to support it at all (except for transfers).
> 
> As far as bulk access, I feel the same way. That option should not exist
at
> all, but something like b) might be an acceptable alternative.

It would have to include the option of dealing with it in any way each 
registrar sees fit - including not offering it.

Same goes for bulk access. In both cases, I think we end up with a 
situation where some registrars would choose to continue to offer it, 
some would offer the data via other mechanisms and others still would 
deal with it in ways that we haven't thought of. In all cases, I think 
it is critical to deal with the problem in a way that preserves these 
options.

Simply eliminating them favors one outcome over others and doesn't 
provide registrars with a proper opportunity to "compete" for the 
right answer.


-- 


                        -rwr








                 "Don't be too timid and squeamish about your actions.
                                            All life is an experiment.
                             The more experiments you make the better."
						- Ralph Waldo Emerson

Got Blog? http://www.blogware.com
My Blogware: http://www.byte.org



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