IANA: Difference between revisions

Revision as of 18:04, 21 March 2012

The Internet Assigned Numbers Authority is the entity that manages the allocation of global IP Addresses, root zone management related to DNS (Domain Name System) and other Internet Protocols (IP).

Short overview[edit | edit source]

As the Internet evolved, there was a need for a centralized organization which would fulfill the followings tasks/needs:

To take responsibility for managing parameters
To make sure that everyone uses the same protocols and parameters
To coordinate the assignment of identifiers
To ensure that the creation and allocation of addresses and domain names is done accurately, based on principles which are acceptable for everyone.

The organization which was responsible for these tasks/needs is IANA. Due to the Internet growth during the 1990's there was also the need for an organization that would take responsibility over the central registration of domain names and addresses. This is how ICANN (Internet Corporation for Assigned Names and Numbers) was created. ^[1]

ICANN is responsible for the centralization of registration tasks related to IP addresses, DNS assignment and protocol parameters management, but ICANN does not replace IANA. There are many differences between ICANN and IANA, especially regarding their attributions, objectives and responsibilities.

IANA vs ICANN[edit | edit source]

IANA is the institution which runs TLDs (Top-Level Domains) and deals with the assignment of IP addresses and ranges, ports, and other related attributes.^[2]

ICANN, based on the Memorandum of Understanding (MoU), is the institution which runs IANA.

IANA objectives[edit | edit source]

Besides managing the DNS root zone, IANA also manages the .int registry, and the .arpa zone;
Regarding number resources, IANA is entitled to coordinate the global IP respectively AS number space, allocating these to RIRs (Regional Internet Registries);
IANA represents the main repository for number registries and protocol names. ^[3]

Domain Names[edit | edit source]

IANA is responsible for the administration of domain names which involves liaisons of TLD operators, with root name server operators, as well as operating with .int and .arpa zone.

In order to enable and better manage the allocation of Internationalized Domain Names (IDNs), IANA developed "IDN tables" which supply information related to admitted characters in different languages and other TLD related information. ^[4]

Protocol parameters[edit | edit source]

Based on IETF protocols, IANA is responsible with the administration of URI schemes (Uniform Resource Identifier) and character encoding for Internet use.

IP Address[edit | edit source]

IANA is responsible for the delegation of IP Addresses to RIRs. In their turn, each RIR (Regional Internet Registry) is responsible for the allocation of IP addresses depending on the zone/area they are managing. In the same way, when a RIR requests for more IP Addresses for allocation, IANA evaluates the request and is able to make an additional allocation for RIR. ^[5]

IANA Contract[edit | edit source]

Originally, the IANA functions is managed by the Information Sciences Institute (ISI) at the University of Southern California (USC) through the leadership of Dr. Jon Postel under a contract with the Defense Advance Research Project Agency (DARPA).^[6]

In 1997, the United States government under Pres. Bill Clinton's administration approved the transition of the technical management of the Domain Name System (DNS) including the IANA functions to a private sector. On January 30, 1998, the DOC released the Green Paper recommending the establishment of a new private, non-profit organization to take over the management of the DNS. The global internet stakeholders shared their comments and recommendations regarding the Green Paper and were compiled and studied by the NTIA. On June 1998, NTIA published the White Paper, which contains the policy statement of the U.S. government regarding the transition process for the technical management of the DNS to a new corporation that will be created based on the principles stability, competition, private bottom-up coordination and representation.^[7]

On November 25, 1998, the Department of Commerce formally recognized ICANN as the new organization responsible in administering the DNS through a Memorandum of Understanding signed by both parties.^[8]

The Department of Commerce (DOC) awarded a contract to ICANN to manage the IANA functions on February 9, 2000.^[9] The agreement was renewed several times in 2001,^[10] 2003, ^[11] and 2006 ^[12]. The contract in 2006 was modified several times. The latest modification extended ICANN's contract for another 6 months until September 30, 2012.^[13]

DOC Notice of Inquiry on IANA Functions[edit | edit source]

On February 25, 2011, the DOC through NTIA issued a Notice of Inquiry (NOI) to review the IANA functions contract. ICANN's IANA functions contract expires on September 11, 2011. The internet community was encouraged to provide their feedback to the different questions posted by NTIA that aims help improve the operations of the IANA functions.The NOI is the first comprehensive review conducted by the DOC since ICANN took over the responsibilities of the IANA functions in 2000. The deadline for comments was scheduled on March 31, 2011.^[14] ^[15]

ICANN acknowledged the importance of a comprehensive review on the IANA Functions contract. ICANN suggested to change the conditions of the procurement contract between the U.S. government and internet governing body into a Cooperative Agreement. In addition, ICANN also recommended the include the principles of accountability and transparency in the next framework of the agreement and to restrict the scope of the IANA functions. ICANN will continue to perform the existing IANA function by entering separate agreements with the Internet Architecture Board (IAB) and the Internet Engineering Task Force (IETF) to perform the port and protocol parameter registry functions and the management of .arpa top level domain name (TLD).^[16]

On June 14, 2011, DOC issued a Further NOI to solicit public comments regarding its draft Statement of Work (SOW), which consists the summary of comments submitted by the public to the first NOI, the response of the NTIA and the detailed work requirements for the IANA Functions.^[17]

RFP for New IANA Functions Contract[edit | edit source]

Following the NOI, the DOC published a Request for Proposal (RFP) for the new IANA Functions contract on November 10, 2011. Interested entities were encouraged to submit their proposals until December 12, 2011. The next contract is set to commence on April 1, 2012 until March 31, 2015. The entity that will be chosen to carry out the IANA function will have the option to extend the agreement for another 3 years. ^[18]

Some members of the internet community believe that ICANN is expected to win the IANA contract and view NTIA's decision to remove the "consensus report" as a "softening language" and the inclusion of conflict of interest policy is one of the most significant issue facing ICANN.^[19] The issue of conflict of interest was raised by the global internet community after the departure Peter Dengate Thrush from his position as ICANN Chairman and a strong proponent of the new gTLD expansion program immediately joined Minds + Machines, a domain name consulting company. Sen. Ron Wyden called the attention of the DOC on this issue and recommended the inclusion of "strict ethics guidelines" to prevent the revolving door in the next IANA contract.^[20] ^[21]

One week after the publication of the RFP, revised the IANA contract and included the "ban on dealing with groups classified as supporting terrorism. The DOC created a new section on data rights stating that the US governments has unlimited rights in all data delivered by the contractor under the contract and all data first produced in the performance of the contract." A minor revision was made on the wordings of the new gTLDs section. The old version was written IANA must show that ICANN “followed its policy framework” to approve a gTLD. The new version reads; it must have “followed its own policy framework.”^[22]

Requirements for IANA Functions Contract Applicants[edit | edit source]

Entities interested in applying to become the new manager of the IANA Functions must meet the following qualifications:^[23]

The organization/firm must be US-owned and operated or a fully accredited US college or university located within the 50 states on District of Columbia (DC)
Incorporated and organized under the laws of one of the 50 states or DC
Must be physically located within the United Stated during the entire duration of the contract
Demonstrate that all the primary systems and operations will remain in United States and all the core IANA functions identified in the contract must be performed in the US.
Show determination in carrying out its responsibilities in accordance with the standards of the FAR Subpart 9.1
Must be able to comply with all the applicable laws and regulations as well as the conditions and terms in the agreement in pursuant to the solicitation
Demonstrate its capability to perform the required scope of work and has the ability to provide a "complete, reasonable and logical" cost data or projected funding

Interested Applicants[edit | edit source]

Aside from ICANN, three other organizations submitted their proposals to manage the IANA functions including:^[24]

References[edit | edit source]

[1] IANA creations

[2] IANA attributions

[3] IANA Objectives

[4] IANA domains

[5] IANA IP Addresses

[6] Improvement of Technical Management of Internet Names and Addresses; Proposed Rule

[7] Statement of Policy on the Management of Internet Names and Addresses

[8] Second Status Report Under ICANN/US Government Memorandum of Understanding

[9] IANA Contract, February 9, 2000

[10] IANA Contract 2001

[11] IANA Contract 2003

[12] IANA Contract 2006

[13] Modification 10-Extension of IANA Contract

[14] DOC Notice of Inquiry

[15] A full guide to the new IANA contract

[16] ICANN Response to the DOC Notice of Inquiry

[17] Further Notice of Inquiry

[18] IANA RFP-Solicitation Number: SA1301-12-RP-IANA

[19] US puts ICANN contract up for rebid

[20] Senator calls for ICANN ethics controls

[21] So you want to run IANA? An applicant's guide

[22] US quietly revises IANA contract

[23] So you want to run IANA? An applicant's guide

[24] Interested Vendors List

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

[11]

[12]

[13]

[14]

[15]

[16]

[17]

[18]

[19]

[20]

[21]

[22]

[23]

[24]

@@ Line 58: / Line 58: @@
 Some members of the internet community believe that ICANN is expected to win the IANA contract and view NTIA's decision to remove the "consensus report" as a "softening language" and the inclusion of conflict of interest policy is one of the most significant issue facing ICANN.<ref>[http://domainincite.com/us-puts-icann-contract-up-for-rebid/ US puts ICANN contract up for rebid]</ref> The issue of conflict of interest was raised by the global internet community after the departure [[Peter Dengate Thrush]] from his position as ICANN Chairman and a strong proponent of the new [[gTLD]] expansion program immediately joined [[Minds + Machines]], a domain name consulting company. Sen. [[Ron Wyden]] called the attention of the DOC on this issue and recommended the inclusion of "strict ethics guidelines" to prevent the revolving door in the next IANA contract.<ref>[http://domainincite.com/senator-calls-for-icann-ethics-controls/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+DomainIncite+%28DomainIncite.com%29 Senator calls for ICANN ethics controls]</ref> <ref>
 [http://news.dot-nxt.com/2011/11/17/iana-applicant-guide So you want to run IANA? An applicant's guide]</ref>
+One week after the publication of the RFP, revised the IANA contract and included the ''"ban on dealing with groups classified as supporting terrorism. The DOC created a new section on data rights stating that the US governments has unlimited rights in all data delivered by the contractor under the contract and all data first produced in the performance of the contract."'' A minor revision was made on the wordings of the new gTLDs section. The old version was written IANA must show that ICANN “followed its policy framework” to approve a gTLD. The new version reads; it must have “followed its own policy framework.”<ref>[http://domainincite.com/us-quietly-revises-iana-contract/ US quietly revises IANA contract]</ref>
 ===Requirements for IANA Functions Contract Applicants===