ICANN/GNSO GNSO Email List Archives

[registrars]


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

Re: [registrars] Please Respond: Expiry and Create dates in OPoC

  • To: Ross Rader <ross@xxxxxxxxxx>
  • Subject: Re: [registrars] Please Respond: Expiry and Create dates in OPoC
  • From: Thomas Keller <tom@xxxxxxxxxx>
  • Date: Mon, 30 Oct 2006 11:00:31 +0100
  • Cc: Bruce Tonkin <Bruce.Tonkin@xxxxxxxxxxxxxxxxxx>, Registrars Constituency <registrars@xxxxxxxxxxxxxx>
  • In-reply-to: <45415142.7080007@tucows.com>
  • Organization: Schlund + Partner AG
  • References: <57AD40AED823A7439D25CD09604BFB54036EE181@balius.mit> <45415142.7080007@tucows.com>
  • Sender: owner-registrars@xxxxxxxxxxxxxx
  • User-agent: Mutt/1.5.9i

however the problem is solved technically I think this is the way to go.
We as registrars should start to differentiate more between "public
data" that is easily accessed and registration data that is needed for
"administrative" purposes.

Best,

tom

Am 26.10.2006 schrieb Ross Rader:
> Bruce Tonkin wrote:
> 
> >(b) Port-43 WHOIS only providing such data to authenticated parties (ie
> >you can have two WHOIS addresses - one for anonymous access that doesn't
> >provide such dates, and one for access by a party that signs the
> >equivalent of a zonefile access agreement).
> 
> it might be worthwhile looking at encryption options instead of setting 
> up different services - this is just an implementation detail, but I 
> think encryption might scale better. In any event, I am receptive to the 
> submission made - it might make for a fair middle ground, especially if 
> there is an auth layer that lives above registrant auth that allows 
> registrars to tell if the request they are seeing has been signed by a 
> registrar or some other third party.
> 
> -ross
> 
> 
> 

Gruss,

tom

(__)        
(OO)_____  
(oo)    /|\	A cow is not entirely full of
  | |--/ | *    milk some of it is hamburger!
  w w w  w  



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