- Internet Assigned Numbers Authority
The Internet Assigned Numbers Authority (IANA) is the entity that oversees global IP address allocation, DNS root zone management, media types, and other
Internetprotocol assignments. It is operated by ICANN.
Prior to the establishment of
ICANNfor this purpose, IANA was administered primarily by Jon Postelat the Information Sciences Instituteat the University of Southern California, under a contract USC/ISI had with the United States Department of Defense, until ICANN was made to assume the responsibility under a United States Department of Commercecontract.
IANA is broadly responsible for the allocation of globally-unique names and numbers that are used in Internet protocols that are published as RFC documents. It maintains a close liaison with the
IETFand RFC Editorin fulfilling this function.
In the case of relatively high-profile subsets of protocol numbers - namely
IP addressesand domain names, extra policy and handling is required and the allocation process is handled in more specific methods. This is to cope with the multi-layered administration of these resources.
IANA delegates local registrations of IP addresses to Regional Internet Registries (RIRs). Each RIR allocates addresses for a different area of the world. Collectively the RIRs form part of the
Number Resource Organizationformed as a body to represent their collective interests and ensure that policy statements are coordinated globally.
IANA delegates the allocation of IPv4 addresses to RIRs in large blocks (typically in the size of "/8", or 224 addresses, or more at a time), and the RIRs then re-allocate smaller blocks in the regions to ISPs and other organizations.
There is also a process for the delegation and allocation of
IPv6addresses, but there is currently little delegation pressure on blocks of IPv6 addresses, as supply vastly exceeds demand.
IANA administers the data in the
root nameservers, which is the top of the hierarchial DNS tree. This task involves liaising with top-level domainoperators, as well as root nameserver operators, and ICANN's policy making apparatus.
It also operates the
.intregistry for intergovernmental organisations, the .arpazone for protocol administration purposes and reverse DNS lookups, and other critical zones such as root-servers.net.
IANA administers those parameters of
IETFprotocols for which in the middle registry is necessary. Examples include the names of URI schemes and of character encodings approved for use on the Internet. This task is undertaken under the oversight of the Internet Architecture Board, and the agreement governing the work is published in RFC 2860.
IANA is managed by the
Internet Corporation for Assigned Names and Numbers(ICANN) under contract to the United States Department of Commerce(DOC). The Department of Commerce also provides an ongoing oversight function, whereby it verifies additions and changes made in the root to ensure IANA complies with its policies.
January 28, 2003the DOC, via the Acquisition and Grants Office of the National Oceanic and Atmospheric Administration, issued a notice of intent to grant ICANN the IANA contract for three more years. It invited alternative offerors to submit in writing a detailed response on how they could meet the requirements themselves. Such responses were to be received no later than 10 days following publication of the invitation and the decision on whether to open the "tender" to competition was to remain solely within the discretion of the government.
In August 2006 the DOC extended its IANA contract with ICANN for a further five years, subject to annual renewals. [http://www.theregister.co.uk/2006/08/16/icann_awarded_iana/]
The relationship between ICANN and the ccTLDs and RIRs can best be described as highly political, and there have been a number of proposals to decouple the IANA function from ICANN completely. However, it is widely believed that it would be impractical to change the current control structure without risking fracturing the Internet.
History of IANA
IANA was established informally as a reference to various technical functions the
Information Sciences Instituteperformed for the United States Department of DefenseAdvanced Research Project Agency on the ARPANET.
The earliest reference to a registry function is probably RFC 322, published on March 26, 1972, which had
Vint Cerfand Jon Postelestablishing a "socket registry" - this registry was published in the RFC series as RFC 433 in December 1972.
The first reference to the name "IANA" in the RFC series is in RFC 1060, published in 1990, but the function, and the term, was well established long before that; RFC 1174 says that "Throughout its entire history, the Internet system has employed a central Internet Assigned Numbers Authority (IANA)...", and RFC 1060 lists a long series of earlier editions of itself, starting with RFC 349.
Jon Postelmanaged the IANA function from its inception until his death in October 1998.After his death, Joyce Reynolds, who had worked with him on IANA for many years, managed the transition of the IANA function to ICANN.
The reason why Postel had the authority to perform the IANA function was that he had always done it in his position at the Information Sciences Institute, under its DoD contract, and did it well.
Starting in 1988, IANA was funded by the U.S. government under a contract between the
Defense Advanced Research Projects Agencyand Information Sciences Institute(ISI). This contract expired in April 1997, but was extended to preserve IANA's function.
On December 24, 1998, USC entered into a transition agreement with the Internet Corporation for Assigned Names and Numbers
ICANN, transferring the IANA function to ICANN, effective January 1, 1999, thus making IANA an operating unit of ICANN.
On February 8, 2000, the DoC entered into an agreement with ICANN to perform the IANA functions.
In June 1999, at its Oslo meeting,
IETFsigned an agreement with ICANNon the tasks that IANA would perform for the IETF; this is published as RFC 2860.
In November 2003,
Doug Bartonwas appointed IANA manager.
In 2005, David Conrad was appointed as IANA manager.
* [http://www.iana.org/ IANA website]
* [http://www.nro.net/ Numbers Resource Organization]
* [http://mail.canarie.ca/MLISTS/news/0700.html COOK report on Internet, June 1997]
* [http://www.icann.org/general/usc-icann-transition-agreement.htm ISI/ICANN transition agreement]
* [http://www.ntia.doc.gov/ntiahome/domainname/iana.htm IANA Functions Purchase Order of the United States Department of Commerce]
* [http://www.icann.org/general/iana-contract-17mar03.htm ICANN contract for IANA, March 2003]
Wikimedia Foundation. 2010.