ICANN ICANN Email List Archives

[gnso-whois-wg]


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

Re: [gnso-whois-wg] Why OPoC Must have Relationship w/ Registrar/ICANN not just Registrant

  • To: "Scoville, Adam" <ascoville@xxxxxxxxx>, gnso-whois-wg@xxxxxxxxx
  • Subject: Re: [gnso-whois-wg] Why OPoC Must have Relationship w/ Registrar/ICANN not just Registrant
  • From: Hugh Dierker <hdierker2204@xxxxxxxxx>
  • Date: Fri, 6 Jul 2007 07:50:39 -0700 (PDT)

No. Making the OPoC a police person is not what WHOIS is about. How can the 
OPoC have what amounts to a fiduciary duty with the registrant and then be 
contractually bound to serve ICANN? I was first of the mind for a registration 
system but then change my mind against it for exactly this reason.
   
  Eric

"Scoville, Adam" <ascoville@xxxxxxxxx> wrote:
        st1\:*{behavior:url(#default#ieooui) }                I think some who 
didn?t attend the San Juan meeting have asked why an agreement with the 
registrar or ICANN is necessary. 
   
  To summarize, a relationship only between the OPoC and the registrant is 
insufficient for the following reason: if the registrant of the domain is in 
some way a bad actor, a wronged third party needs the OPoC to perform its 
functions in order to communicate with the registrant, and to be able to 
identify the registrant sufficient to bring the right legal action against the 
right person in the right place. (If that can?t be done, there is no law on the 
Internet.) 
   
  If the OPoC doesn?t perform its functions, under this scenario, the only 
party the OPoC is responsible to is the bad actor. Moreover, the OPoC may 
complain that the contract the registrant gave her never required her to 
perform the responsibilities we set out. So perhaps the registrant has breached 
the Registration Agreement by failing to require the right responsibilities of 
the OPoC? but all that gives is another reason the registrant is bad, which is 
no help in the original goal of communicating with or bringing legal action 
against the registrant. 
   
  Two ways of binding the OPoC would be accreditation (i.e. ICANN verifies the 
OPoC?s credentials and OPoC agrees to perform it?s responsibilities as a 
condition of accreditation) or acknowledgement (i.e. when nominated as an OPoC, 
the OPoC must in some way acknowledge to the registrar that it is the OPoC and 
its responsibility to perform the specified OPoC functions).
   
  Perhaps with acknowledgement there is no indication ahead of time that the 
OPoC will do its job (as in accreditation), but at least a contractual 
relationship exists (the OPoC must respond to a query, and 
acknowledge?agree?that it must perform its set of responsibilities).
   
  - Adam



       
---------------------------------
Park yourself in front of a world of choices in alternative vehicles.
Visit the Yahoo! Auto Green Center.


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