ICANN/GNSO GNSO Email List Archives

[registrars]


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

RE: [registrars] More clauses removed from new .NET Contract

  • To: <registrars@xxxxxxxx>
  • Subject: RE: [registrars] More clauses removed from new .NET Contract
  • From: "Bruce Tonkin" <Bruce.Tonkin@xxxxxxxxxxxxxxxxxx>
  • Date: Mon, 8 Aug 2005 08:52:07 +1000
  • Sender: owner-registrars@xxxxxxxxxxxxxx
  • Thread-index: AcWbikjFRrkuyJLASsKTGnbbZtPnjwAF/PsQ
  • Thread-topic: [registrars] More clauses removed from new .NET Contract

Hello Bhavin,

Have a look at

Article VII SPECIAL PROVISIONS

See Section 7.1 Registry-Registrar Agreement
(a) Access to Registry Services

Not sure how this compares to the old agreement, but it does set out the
provisions for non-discriminatory access.

Regards,
Bruce
 

> -----Original Message-----
> From: owner-registrars@xxxxxxxxxxxxxx 
> [mailto:owner-registrars@xxxxxxxxxxxxxx] On Behalf Of Bhavin Turakhia
> Sent: Monday, 8 August 2005 6:01 AM
> To: registrars@xxxxxxxx
> Subject: [registrars] More clauses removed from new .NET Contract
> 
> 
> Check out another clause below. The older .NET Agreement had 
> a specific clause which laid out that all registrars will be 
> treated fairly. This whole clause is missing in the new .NET 
> agreement. I have pasted the clause below for reference. I 
> don't see why a clause whose title was "Fair treatment of 
> ICANN-Accredited Regisrars" should be REMOVED.
> 
> I must clarify here that by the older .NET Agreement I mean 
> the one prevailing before the RFP was posted.
> 
> Please click on the link below to access this agreement -
> 
> *
> http://www.icann.org/tlds/agreements/verisign/registry-agmt-ne
t-25may01.htm
> 
> 3.5 Fair Treatment of ICANN-Accredited Registrars.
> 
> 3.5.1 Registry Operator shall provide all ICANN-Accredited 
> Registrars that have Registry-Registrar Agreements in effect, 
> and that are in compliance with the terms of such agreements, 
> equivalent access to Registry Operator's Registry Services, 
> including to its shared registration system.
> 
> 3.5.2 Registry Operator shall certify to ICANN every six 
> months, using the objective criteria set forth in Appendix H, 
> that Registry Operator is providing all such ICANN-Accredited 
> Registrars with equivalent access to its Registry Services, 
> including to its shared registration system.
> 
> ........
> 
> 3.5.5 Registry Operator will ensure, in a form and through 
> ways described in Appendix H, that the revenues and assets of 
> Registry Operator are not utilized to advantage registrars 
> that are affiliated with Registry Operator to the detriment 
> of other ICANN-Accredited Registrars. For purposes of this 
> Subsection 3.5.5, funds distributed to debt or equity 
> participants in Registry Operator shall no longer be deemed 
> revenues and assets of Registry Operator once they are distributed.
> 
> ........
> 
> - Bhavin
> 
> 




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