Re: [council] First call conclusions v3 - ICANN functions

[Elisabeth Porteneuve <Elisabeth.Porteneuve@cetp.ipsl.fr>]

Dear Philip,

My apology for not bringing one item to your attention earlier.

I would like to modify the item (3):
   3. ccTLD administrative functions (such as requests for 
      delegation and redelegation).
into:
   3. ccTLD administrative functions (such as updating the 
      IANA database entries concerning ccTLD Managers, 
      or requests for delegation and redelegation).

Thank you !
Elisabeth


> From owner-council@dnso.org Thu Apr  4 13:09 MET 2002
> From: "Philip Sheppard" <philip.sheppard@aim.be>
> To: "NC \(list\)" <council@dnso.org>
> Subject: [council] First call conclusions v3 - ICANN functions
> Date: Thu, 4 Apr 2002 13:10:33 +0200
>
> 
> For clarity, if we accept the changes proposed by NC members et al 
> (subject to clarification on the factual description of ICANN's mission) 
>  the current draft of first call conclusions reads as below.
> Philip
> ------------
> 
> DRAFT version 3
> Scope and mission of ICANN
> In broad terms the NC agreed with the factual description of ICANN's 
> functions listed in "What ICANN Does" at: 
> http://www.icann.org/general/toward-mission-statement-07mar02.htm
> "ICANN is responsible for coordinating the Internet's naming, address 
> allocation, and protocol parameter assignment systems. These systems 
> enable globally unique and universally interoperable identifiers for the 
> benefit of the Internet and its users.
> ICANN's paramount concern is the stability of these services.
> ICANN's role includes both operational and policymaking functions. "
> 
> The ICANN note specifies that ICANN's operations (in broad summary) 
> cover:
> 1. General operational functions (such as IP address allocation, 
> maintaining the DNS root zone file).
> 2. gTLD administrative functions (such as registrar accreditation, 
> supervising the Uniform Dispute Resolution Policy).
> 3. ccTLD administrative functions (such as requests for delegation and 
> redelegation).
> 4. Policy coordination for infrastructure security.
> 5. Policymaking including:
>   5.1. IP address and AS number allocation,
>   5.2  ccTLD global policy coordination,
>   5.3. Protocol numbering via the IANA registries,
>   5.4 gTLD registry-level policies.
> 
> The Names Council specified the following existing functions of ICANN 
> where the NC would like ICANN to do better in carrying them out:
> - ccTLD administrative functions
> - root server administration
> - Registry and Registrar contract enforcement with respect to 
> intellectual property and other existing conditions.
> Recommendation 1: Create clearly delineated divisions within ICANN 
> responsible for the administration of its operational and policy 
> functions. This would establish separate staff functions for policy and  
> operational functions.
> 
> 
> The Names Council felt that the greatest danger of mission creep lay in 
> the areas of security and consumer protection. The creation of 
> infrastructure for at-large membership was also mentioned; however, it 
> was also argued that this topic should not be discussed alongside with 
> ICANN's functions.
> Recommendation 2. ICANN's functions should not be extended beyond what 
> is outlined in the note "What ICANN Does" .
>