Jump to content

IANA: Difference between revisions

From ICANNWiki
Marie Cabural (talk | contribs)
Marie Cabural (talk | contribs)
Line 52: Line 52:
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.<ref>[http://www.ntia.doc.gov/files/ntia/publications/fr_iana_furthernoi_06142011.pdf Further Notice of Inquiry]</ref>
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.<ref>[http://www.ntia.doc.gov/files/ntia/publications/fr_iana_furthernoi_06142011.pdf Further Notice of Inquiry]</ref>


===DOC Published RFP for New IANA Functions Contract===
===RFP for New IANA Functions Contract===
Following the NOI, the DOC published a Request for Proposal (RFP) for the new IANA Functions contract. Interested entities were encouraged to submit their proposals until December 12, 2011.<ref>[https://www.fbo.gov/?s=opportunity&mode=form&id=c564af28581edb2a7b9441eccfd6391d&tab=core&_cview=0 IANA RFP-Solicitation Number: SA1301-12-RP-IANA]</ref>
Following the NOI, the DOC published a Request for Proposal (RFP) for the new IANA Functions contract. Interested entities were encouraged to submit their proposals until December 12, 2011.<ref>[https://www.fbo.gov/?s=opportunity&mode=form&id=c564af28581edb2a7b9441eccfd6391d&tab=core&_cview=0 IANA RFP-Solicitation Number: SA1301-12-RP-IANA]</ref>



Revision as of 06:48, 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. Interested entities were encouraged to submit their proposals until December 12, 2011.[18]

References[edit | edit source]