Internet Assigned Numbers Authority

From Wikipedia, the free encyclopedia
Jump to: navigation, search
IANA
IANA Logo
Founded 1988
Founder(s) U.S. government
Headquarters
Key people Elise Gerich
Focus(es) Manage DNS root zones
Owner ICANN
Website www.iana.org

The Internet Assigned Numbers Authority (IANA) is a department of ICANN, a nonprofit private American corporation, which oversees global IP address allocation, autonomous system number allocation, root zone management in the Domain Name System (DNS), media types, and other Internet Protocol-related symbols and numbers.[1][2]

Prior to the establishment of ICANN primarily for this purpose in 1998, IANA was administered principally by Jon Postel at the Information Sciences Institute (ISI) of the University of Southern California (USC) situated at Marina Del Ray (Los Angeles), under a contract USC/ISI had with the United States Department of Defense, until ICANN was created to assume the responsibility under a United States Department of Commerce contract.

Responsibilities[edit]

IANA is broadly responsible for the allocation of globally unique names and numbers that are used in Internet protocols that are published as Request for Comments documents. These documents describe methods, behaviors, research, or innovations applicable to the working of the Internet and Internet-connected systems. IANA also maintains a close liaison with the Internet Engineering Task Force (IETF) and RFC Editorial team in fulfilling this function.

In the case of the two major Internet namespaces, namely IP addresses and domain names, extra administrative policy and delegation to subordinate administrations is required because of the multi-layered distributed use of these resources.

IP addresses[edit]

IANA delegates allocations of IP address blocks to Regional Internet Registries (RIRs). Each RIR allocates addresses for a different area of the world. Collectively the RIRs have created the Number Resource Organization formed as a body to represent their collective interests and ensure that policy statements are coordinated globally.

The RIRs divide their allocated address pools into smaller blocks and delegate them in their respective operating regions to Internet service providers and other organizations. Since the introduction of the CIDR system, IANA typically allocates address space in the size of /8 prefix blocks for IPv4 and /23 to /12 prefix blocks from the 2000::/3 IPv6 block to requesting regional registries as needed.

Domain names[edit]

IANA administers the data in the root nameservers, which form the top of the hierarchical DNS tree. This task involves liaising with top-level domain operators, the root nameserver operators, and ICANN's policy making apparatus.

ICANN also operates the .int registry for international treaty organizations, the .arpa zone for Internet infrastructure purposes, including reverse DNS service, and other critical zones such as root-servers.

Protocol parameters[edit]

IANA administers many parameters of IETF protocols. Examples include the names of Uniform Resource Identifier (URI) schemes and character encodings recommended 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.

Time zone database[edit]

The IANA time zone database holds the time zone differences and rules for the various regions of the world and allows this information to be mirrored and used by computers and other electronic devices to keep accurate track of time zones through the Internet.

IANA resumed operation of the database on October 16, 2011, after the Astrolabe, Inc. v. Olson et al.[3] lawsuit and the database's eventual shutdown.[4][5]

Oversight[edit]

IANA is managed by the Internet Corporation for Assigned Names and Numbers (ICANN) under contract to the United States Department of Commerce (DOC) and pursuant to an agreement with the IETF.[2] The Department of Commerce also provides an ongoing oversight function, whereby it verifies additions and changes made in the DNS root zone to ensure IANA complies with its policies. The IAB, on behalf of the IETF, has the ability to terminate its agreement for ICANN to perform IANA work with six months notice.

On January 28, 2003 the Department of Commerce, 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 U.S. Department of Commerce extended its IANA contract with ICANN by an additional five years, subject to annual renewals.[6]

Since ICANN is managing a worldwide resource, but being controlled by U.S. interests, a number of proposals have been brought forward to decouple the IANA function from ICANN.[citation needed]

On March 14, 2014, the U.S. Department of Commerce announced its intent to transition key Internet domain name functions to the global multistakeholder community. [7][8]

History[edit]

IANA was established informally as a reference to various technical functions for the ARPANET, that Jon Postel and Joyce K. Reynolds performed at the University of California at Los Angeles (UCLA) and at the University of Southern California's Information Sciences Institute.

On March 26, 1972, Vint Cerf and Jon Postel at UCLA called for establishing a socket number catalog in RFC 322. Network administrators were asked to submit a note or place a phone call, "describing the function and socket numbers of network service programs at each HOST".[9] This catalog was subsequently published as RFC 433 in December 1972.[10] In it Postel first proposed a registry of assignments of port numbers to network services, calling himself the czar of socket numbers.[11]

The first reference to the name "IANA" in the RFC series is in RFC 1060, published in 1990 by Postel and Reynolds at USC-ISI, 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.[12]

In 1995, the National Science Foundation authorized Network Solutions to assess domain name registrants a $50 fee per year for the first two years, 30 percent of which was to be deposited in the Intellectual Infrastructure Fund (IIF), a fund to be used for the preservation and enhancement of the intellectual infrastructure of the Internet.[13] There was widespread dissatisfaction with this concentration of power (and money) in one company, and people looked to IANA for a solution. Postel wrote up a draft[14] on IANA and the creation of new top level domains. He was trying to institutionalize IANA. In retrospect, this would have been valuable, since he unexpectedly died about two years later.

In January 1998, Postel was threatened by US Presidential science advisor Ira Magaziner with the statement "You'll never work on the Internet again" after Postel collaborated with root server operators to test using a root server other than Network Solutions' "A" root to act as the authority over the root zone. Demonstrating that control of the root was from the IANA rather than from Network Solutions would have clarified IANA's authority to create new top-level domains as a step to resolving the DNS Wars, but he ended his effort after Magaziner's threat, and died not long after.[15][16]

Jon Postel managed the IANA function from its inception on the ARPANET until his death in October 1998. By his almost 30 years of "selfless service",[17] Postel created his de facto authority to manage key parts of the Internet infrastructure. After his death, Joyce K. Reynolds, who had worked with him for many years, managed the transition of the IANA function to ICANN.

Starting in 1988, IANA was funded by the U.S. government under a contract between the Defense Advanced Research Projects Agency and the Information Sciences Institute. This contract expired in April 1997, but was extended to preserve IANA.

  • On December 24, 1998, USC entered into a transition agreement with the Internet Corporation for Assigned Names and Numbers ICANN, transferring the IANA project to ICANN, effective January 1, 1999, thus making IANA an operating unit of ICANN.[18]
  • In June 1999, at its Oslo meeting, IETF signed an agreement with ICANN concerning the tasks that IANA would perform for the IETF; this is published as RFC 2860.
  • On February 8, 2000, the Department of Commerce entered into an agreement with ICANN for ICANN to perform the IANA functions.[19]
  • In November 2003, Doug Barton was appointed IANA manager.
  • In 2005, David Conrad was appointed as IANA manager.
  • in 2010, Elise Gerich was appointed as IANA manager.

See also[edit]

References[edit]

  1. ^ "About IANA - Introduction to IANA". Retrieved 17 December 2011. 
  2. ^ a b B. Carpenter, F. Baker, M. Roberts (June 2000). MoU Between IETF and ICANN concerning IANA. IETF. RFC 2860. https://tools.ietf.org/html/rfc2860.
  3. ^ "Astrolabe, Inc. v. Olson et al". 2011-10-06. Retrieved 2011-10-16. 
  4. ^ "ICANN rescues time zone database". 2011-10-16. Retrieved 2011-10-16. 
  5. ^ "IANA - Time Zone Database". 2011-10-16. Retrieved 2011-10-16. 
  6. ^ ICANN awarded net administration until 2011 by The Register
  7. ^ "NTIA Announces Intent to Transition Key Internet Domain Name Functions". United States Department of Commerce. Retrieved 15 March 2014. 
  8. ^ "U.S. Plans to Give Up Oversight of Web Domain Manager". Wall Street Journal. 14 March 2014. Retrieved 15 March 2014. 
  9. ^ V. Cerf, J. Postel (26 March 1972). Well Known Socket Numbers. IETF. RFC 322. https://tools.ietf.org/html/rfc322.
  10. ^ Jon Postel, Nancy Neigus (22 December 1972). Socket Number List. IETF. RFC 433. https://tools.ietf.org/html/rfc433.
  11. ^ J. Postel (30 May 1972). Proposed Standard Socket Numbers. IETF. RFC 349. https://tools.ietf.org/html/rfc349.
  12. ^ J. Postel, J. Reynolds (March 1990). Assigned Numbers. IETF. RFC 1060. https://tools.ietf.org/html/rfc1060.
  13. ^ "NTIA DNS Statement of Policy". June 1998. 
  14. ^ J. Postel (June 1996). New Registries and the Delegation of International Top Level Domains. IETF. I-D draft-postel-iana-itld-admin-0. http://tools.ietf.org/html/draft-postel-iana-itld-admin-01.
  15. ^ Damien Cave (July 2, 2002). "It's time for ICANN to go". Salon.com. 
  16. ^ Dave Farber (July 2, 2002). "a comment on Gilmore: ICANN Must Go (good insights)". Interesting-people mailing list. 
  17. ^ V. Cerf (October 1998). I Remember IANA. IETF. RFC 2468. https://tools.ietf.org/html/rfc2468.
  18. ^ "USC ICANN Transition Agreement". ICANN. Retrieved 15 March 2013. 
  19. ^ "IANA Functions Contract". Dept of Commerce/NTIA. Retrieved 15 March 2013. 

External links[edit]