ICANN/GNSO GNSO Email List Archives

[council]


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

Re: [council] Friendly amendment to VI Charter

  • To: Caroline Greer <cgreer@xxxxxxxxx>
  • Subject: Re: [council] Friendly amendment to VI Charter
  • From: Stéphane Van Gelder <stephane.vangelder@xxxxxxxxx>
  • Date: Sun, 7 Mar 2010 08:49:06 +0100
  • Cc: <council@xxxxxxxxxxxxxx>
  • In-reply-to: <C8FFD98530207F40BD8D2CAD608B50B402787C6F@mtldsvr01.DotMobi.local>
  • List-id: council@xxxxxxxxxxxxxx
  • References: <C8FFD98530207F40BD8D2CAD608B50B402787C6F@mtldsvr01.DotMobi.local>
  • Sender: owner-council@xxxxxxxxxxxxxx

Dear Caroline,

I accept your amendment as friendly.

Thank you.

Stéphane

Le 5 mars 2010 à 11:40, Caroline Greer a écrit :

> Dear All,
>  
> The Registries Stakeholder Group [RySG] would like to propose a friendly 
> amendment to the Vertical Integration Charter circulated by Stéphane.
>  
> For purposes of accuracy and consistency, we believe that Objective #4 should 
> be revised to read: “To identify and clearly articulate the differences 
> between the current restrictions and practices concerning registry-registrar 
> separation and equivalent access, on the one hand, and the options described 
> in the most recent version of the DAG and supporting documents[1] and changes 
> considered by staff, on the other hand.”
>  
> The words “equivalent access” in yellow would replace the words “equal 
> access” that are in the current version of Objective #4. We understand that 
> the Charter Group has recognized the difference between “equal access” and 
> “equivalent access” in its deliberations and has adopted “equivalent access” 
> in other parts of the Charter.
>  
> More generally, the RySG notes that the proposed working definitions in the 
> Charter are neither accurate nor complete and, in certain cases, they 
> represent policy statements.  The RySG underscores the importance of 
> developing standalone definitions for each element of vertical integration.  
> However, these definitions should be developed by experts in competition and 
> antitrust matters and derived from, where possible, language in ICANN 
> contracts and ICANN documentation that uses the relevant terms.     
>  
> Many thanks.
>  
> Kind regards,
>  
> Caroline.
> 
>  
> 
> [1] The working group understands that the DAG is a fluid document.  As a 
> result, the working group will conduct its activities based upon the version 
> of the document available.
>  



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