RE: [council] Draft conclusions of NC discussion on ICANN reform - scope

["Cade,Marilyn S - LGA" <mcade@att.com>]

Philip, I apologize for my tardiness in getting you comments on the draft conclusions. My comments are in [DELETIONS] AND CAPs AS INSERTIONS below. They are intended to clarify RATHER THAN TO substantively change the comments. Marilyn

-----Original Message-----
From: Philip Sheppard [mailto:philip.sheppard@aim.be]
Sent: Thursday, March 28, 2002 8:33 AM
To: NC (list)
Subject: [council] Draft conclusions of NC discussion on ICANN reform - scope

Further to the minutes of the NC meeting, please find below draft conclusions and two proposed recommendations for the NC to consider. (Attached also are the terms of reference adopted by the NC 22 March). At this point the recommendations are intended to relate only to the scope and functions of ICANN. Further recommendations may follow future discussion. These recommendations attempt to reflect the broad view of the discussion on scope and pick up one concrete proposal made regarding the creation of separate divisions to handle specific technical functions. Comments please by e-mail in advance of the April 4 meeting.

Philip

-----------------------------------------------------------------

DRAFT

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 certain technical functions. This would  [ free up top-level staff ] ESTABLISH SEPARATE STAFF FUNCTIONS/REPORTING STRUCTURES  to address policy functions and  [ leave ]administrative /OPERATIONAL   FUNCTIONS   [staff free to fulfil an explicit set of tasks ].  

 

The Names Council  [ felt ] NOTED   that  [ the ] SOME [  greatest ]  danger of mission creep lay in  EXTENDING the areas of security, consumer protection and the creation of infrastructure for at-large membership.

Recommendation 2. ICANN's mission should not be extended beyond that outlined in the note "What ICANN Does" .