[council] Preparation for NC calll - ACTION REQUESTED
Preparation for first NC call on reform (March
22)
I believe the first thing we need to address is the functions and principles of ICANN. Without understanding what we want ICANN to do, discussing a structure for ICANN will be confused. Stuart Lynn has posted a document listing "What ICANN Does" at: http://www.icann.org/general/toward-mission-statement-07mar02.htm Please consider your answers to these questions for the NC call on March 2: Q1: Do we agree with this posted list of ICANN's functions? Q2: Do we want to delete anything from this list? Q3: Do we want to add anything to this list? Philip ---------------- An edited extract of the first part of the document referenced above follows: OVERVIEW 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. Operations
general operational functions:
(1) maintaining the DNS root zone file, (2) allocating top-level blocks of IPv4 and IPv6 addresses and AS numbers to the regional Internet registries, (3) maintaining 120+ registries of protocol port and parameter numbers, (4) publishing online databases of information about the top-level domain registries included in the DNS root zone file, (5) operating one of the thirteen authoritative DNS root name servers, and coordinating the overall DNS root name server system, (6) publishing the InterNIC website and related functions, (7) operating the .int registry, (8) maintaining common/technical IP address spaces, such as the private-use address space, (9) managing the reverse delegation namespace at the top level, and (10) administering the DNS implementations of certain technical registries, such as .arpa and the legacy infrastructure-related .int zones. administrative and policy functions relating to the generic top-level domain (gTLD) registries: (1) accreditation of competitive registrars; (2) supervising the administration of the Uniform Dispute Resolution Policy; (3) handling of complaints about registrations; (4) monitoring and enforcement of registry and registrar agreements, and (5) implementation of data escrow programs. administrative and policy functions relating to the
country-code top-level domain (ccTLD) registries:
(1) ICANN staff handle, investigate, and process requests for delegation and redelegation, and for changes in the TLD nameservers specified in the root zone file. Security ICANN has the responsibility for policy coordination with respect to the security of the various parts of infrastructure that make up the operational DNS. Policymaking ICANN is responsible for developing and implementing policies related to each of its operational functions. The nature and scope of ICANN's policymaking role differs for each function including: 1. IP address and AS number allocation- responsibility extends only to
global addressing policies.
2. Country-code top-level domain registries (ccTLDs) - global policy
coordination with deference to each local Internet community's responsibility to
set its own registry-level policies (i.e., registration criteria, pricing,
dispute resolution, mechanisms for local community participation and
policymaking, etc.).
3. Protocol numbering - ICANN administers the IANA registries
pursuant to the instructions of the Internet Engineering Task Force
(IETF).
4. gTLDs: a direct and significant role in setting registry-level policies
for the global top-level domain registries (gTLDs), such as .com, .net, .org,
.info, .name, and .biz. In effect, ICANN serves as the global Internet
community's open policymaking forum for the gTLD registries.
Principles for policy In its initial charge from the U.S. Government, embodied in the 1998 White
Paper, ICANN policymaking was to be guided by a set of non-technical principles:
1. preserving stability;
2. promoting competition;
3. relying where possible on private-sector, bottom-up, participatory
mechanisms that reflect the functional and geographic diversity of the Internet;
4. development of efficient dispute resolution alternatives (for the gTLD
registries);
5. promoting accountability in management (for all registries).
These principles are general. A
restatement would be helpful.
---------------------------
(Note: the edits above are intended to simplify the posted document. Please
do read both documents to reassure yourself that the edited version is
faithful to the original. Philip)
|