Dedicated to preserving the central coordinating functions of the global Internet for the public good.

Progress Report on Performance of IANA Functions
February – April 2000

The Internet Corporation for Assigned Names and Numbers (ICANN) submits this report under Order No. 40SBNT067020 to document performance progress during the period February-April 2000 in performing the function of the Internet Assigned Numbers Authority (the IANA).

General

• The IANA's protocol-assignment responsibilities principally involve assignment and recording of protocol parameter values under standards established by the Internet Engineering Task Force (IETF). On 1 March 2000, ICANN signed a Memorandum of Understanding (MoU) with the IETF concerning the technical work of IANA. That MoU, which was ratified by the ICANN Board on 10 March 2000, defines the technical work to be carried out by the IANA on behalf of the IETF and the Internet Research Task Force. The terms of the MoU are set forth in RFC 2860 (June 2000) (ftp://ftp.ietf.org/rfc/rfc2860.txt).
   
• A number of adjustments to the routine functioning of the IANA occurred to establish a more organized and documented approach to the standards under which assignments are made.
   
• In April 2000, the IANA website http://www.iana.org began its migration from a server operated by the previous contractor, the Information Sciences Institute of the University of Southern California, to a server operated by ICANN.
   
• During the period of this report, approximately 100 e-mails were received by the IANA per day, with approximately 20 relating to protocol applications. Other work performed as part of the IANA function included setup of registries for protocol parameter spaces supporting newly established standards and last-call review of RFCs as pertinent to IANA Considerations.

IANA Function Status:

1) Coordination of the assignment of technical protocol parameters:

• Constantly updated, at: http://www.iana.org/numbers.html.
   
• See also statistical chart below under Protocols.

2) Administrative functions associated with root management:

• IANA report on request for Redelegation of the .pn Top Level Domain. http://www.iana.org/reports/pn-report-11feb00.htm.
   
• IANA report on request for Delegation of the .ps Top Level Domain. http://www.iana.org/reports/ps-report-22mar00.htm.
   
• On 23 February 2000, the ICANN Governmental Advisory Committee (GAC) issued a set of recommended best practices entitled “Principles for the Delegation and Administration of Country Code Top Level Domains.” http://www.icann.org/committees/gac/gac-cctldprinciples-23feb00.htm. This document is the result of discussions among the approximately 30 national governments that participate in the GAC. It includes suggested principles that are pertinent to the considerations employed in root management, including the principle that for all ccTLD delegations there should be in place “a communication-based regime” involving written commitments among the ccTLD delegee, ICANN, and the relevant government or public authority. On 8 March 2000, the members of the GAC (including the United States) issued a communiqué stating that the principles document “represents the views of the national governments, distinct economies and multinational governmental and treaty organisations that comprise the GAC.”

3) Allocation of IP address blocks:

• See statistical chart below under Addresses.

4) Other services:

• Beginning in late-April 2000, IANA assumed responsibility for administration of the .arpa top-level domain in cooperation with the Internet technical community under the guidance of the Internet Architecture Board (IAB), as a limited use domain for Internet infrastructure applications. At the time the IANA assumed this responsibility (which was previously carried out by Network Solutions, Inc.), the .arpa TLD had only a single subdomain, in-addr.arpa. No additions were made during the period covered by this report.
   

Statistical Information:

Protocols

Year 2000	February	March	April
User Ports	105	26	53
Sys Ports	3	0	4
Prot #s	1	1	1
MIME	17	4	3
MIBs	0	8	2
Pr Ent #s	167	210	173
Other	1	2	0

Addresses

Year 2000	February	March	April
Multicast	17	6	1
Cable	3 blk	3 blk	0
AS #s	1 blk	1 blk	0
RIR Alloc	0	0	0

Root Management

During the three-month period covered by this report, the IANA received and sent 589 e-mail messages relating to 71 different ccTLDs. During this period, the IANA submitted requests for 26 changes (21 of which concerned ccTLDs; 20 different ccTLDs were involved) to root-zone information and root-zone-contact information, 21 of which required Commerce Department approval. A monthly breakdown follows:

Year 2000	February	March	April
ccTLD E-mails	332	156	101
ccTLDs Involved	45	36	27
Total Requests	11	8	7
ccTLD Requests	8	7	6
ccTLDs Involved	7	7	6
DOC Approval	7	7	7