Cybertelecom Federal Internet Law & Policy An Educational Project

IANA

The IANA Function: "The IANA functions are a set of interdependent technical functions that enable the continued efficient operation of the Internet. The IANA functions include: (1) the coordination of the assignment of technical Internet protocol parameters; (2) the processing of change requests to the authoritative root zone file of the DNS and root key signing key (KSK) management; (3) the allocation of Internet numbering resources; and (4) other services related to the management of the .ARPA and .INT top-level domains (TLDs).

"ICANN as the IANA functions operator processes changes to three different databases. First, ICANN distributes the protocol parameters or Internet standards developed by the Internet Engineering Task Force (IETF). Second, it allocates IP numbers to the Regional Internet Registries (RIR) who then distribute IP numbers to Internet Service Providers. Third, ICANN processes change requests or updates to the authoritative root zone file or “address book” of the DNS from top level domain name operators - those companies or institutions that manage .com, .org, .us, .uk, etc. In all three cases ICANN’s role is to implement the policies or requests at the direct instruction of the various IANA functions customers.

"NTIA’s role in the IANA functions includes the clerical role of administering changes to the authoritative root zone file and, more generally, serving as the historic steward of the DNS via the administration of the IANA functions contract. NTIA has never substituted its judgment for that of the IANA customers." Myths and Facts on NTIA Announcement on Intent to Transition Key Internet Domain Name Functions, April 2, 2011

History

The management and assignment of IP numbers was originally handled by Jon Postel, who volunteered for the position. This became known as the Internet Assigned Numbers Authority (IANA). Jon Postel worked for USC/ISI. The IANA function was originally funded by DOD (DARPA and DCA). IANA did not have a legal existence. It was a function - something that Jon Postel did as part of his employment at ISI.

The IANA website at one point read: "The IANA is chartered by the Internet Society (ISOC) and the Federal Network Council (FNC) to act as the clearinghouse to assign and coordinate the use of the numerous Internet protocol parameters." [Rony p 122]

IANA Transition

• Letter from ICANN CEO on Completion of IANA Transition Implementation Tasks, NTIA 10/6/16
• Department of Commerce--Property Implications of Proposed Transition of U.S. Government Oversight of Key Internet Technical Functions GAO B-327398: Sep 12, 2016 ("It is unlikely that either the authoritative root zone file—the public “address book” for the top level of the Internet domain name system—or the Internet domain name system as a whole, is U.S. Government property under Article IV. We did not identify any Government-held copyrights, patents, licenses, or other traditional intellectual property interests in either the root zone file or the domain name system. It also is doubtful that either would be considered property under common law principles, because no entity appears to have a right to their exclusive possession or use. ")
• Fact Sheet: The IANA Stewardship Transition Explained NTIA Sept. 14, 2016 ("The United States does not control the Internet. No one controls or owns the Internet (link is external). It is a decentralized network of networks that has operated with the cooperation and through the consensus of a wide array of stakeholders, predominantly from the private sector. The Internet is not ours to give away. By supporting multistakeholder Internet governance, we make certain the Internet becomes no other nations’ to take. ")
• Q and A on IANA Stewardship Transition NTIA Aug. 16, 2016 ("NTIA’s legacy role related to the IANA functions is largely clerical. NTIA verifies that ICANN followed established policies and procedures in processing changes to the root zone file before authorizing Verisign, the root zone file maintainer, to implement them. The root zone file is the authoritative registry containing the lists of names and addresses for all top level domains, effectively the Internet’s phone book. NTIA has no operational role with respect to the protocol parameter and numbering functions.")
• Updates on the NTIA Transition Aug. 16, 2016
• Letter to ICANN CEO Marby Regarding IANA Stewardship Transition Status Update
• Seventh Quarterly Report on the IANA Transition August 3, 2016
• IANA Stewardship Transition Proposal Assessment Report June 9 2016
• Q and A on IANA Stewardship Transition June 9 2016
• "NTIA commissioned a panel of corporate governance experts including Columbia Law Professor John Coffee, Brooklyn Law Professor Dana Brakman Reiser, and The Berkman Center for Internet & Society at Harvard University to review the ICANN accountability provisions."
• What They’re Saying: Reaction to NTIA’s Assessment of the IANA Stewardship Transition Proposal June 16, 2016 by NTIA
• NTIA Finds IANA Stewardship Transition Proposal Meets Criteria to Complete Privatization June 9 2016 ("The U.S. Commerce Department’s National Telecommunications and Information Administration (NTIA) announced today that the proposal developed by the global Internet multistakeholder community meets the criteria NTIA outlined in March 2014 when it stated its intent to transition the U.S. Government’s stewardship role for the Internet domain name system (DNS) technical functions, known as the Internet Assigned Numbers Authority (IANA) functions.")
• Larry Strickling, Reviewing the IANA Transition Proposal, NTIA March 11, 2016 (" the Internet community - made up of businesses, technical experts, academics and civil society - has risen to the challenge by developing a transition plan that has achieved broad community support. The community delivered that proposal to NTIA yesterday (link is external), marking the culmination of the largest multistakeholder process ever undertaken. Stakeholders spent more than 26,000 working hours on the proposal, exchanged more than 33,000 messages on mailing lists, and held more than 600 meetings and calls. ")
• Consolidated Appropriations Act, 2016
• "SEC. 539. (a) None of the funds made available by this Act may be used to relinquish the responsibility of the National Telecommunications and Information Administration, during fiscal year 2016, with respect to Internet domain name system functions, including responsibility with respect to the authoritative root zone file and the Internet Assigned Numbers Authority functions. (b) Notwithstanding any other law, subsection (a) of this section shall not apply in fiscal year 2017."
• Remarks by Lawrence E. Strickling, Assistant Secretary of Commerce for Communications and Information, State of the Net Conference, Washington, DC, January 27, 2015: "At the outset, let me address the impact of last December's appropriations act on the transition planning process. From the day of our announcement last March, some, including members of Congress, have raised questions and concerns about the transition. We welcome their interest and acknowledge the validity of many of these concerns. We think it is important that questions about the transition be addressed and answered. We also believe that a robust, open and transparent multistakeholder process is the best vehicle for ensuring that result. Nothing in the appropriations act affects the activities of industry, civil society and the technical community to develop the transition plan we called for last March. We expect their work to continue and look forward to its conclusion. The act does restrict NTIA from using appropriated dollars to relinquish our stewardship during fiscal year 2015 with respect to Internet domain name system functions. We take that seriously. Accordingly, we will not use appropriated funds to terminate the IANA functions contract with ICANN prior to the contract's current expiration date of September 30, 2015. Nor will we use appropriated dollars to amend the cooperative agreement with Verisign to eliminate NTIA's role in approving changes to the authoritative root zone file prior to September 30. On these points, there is no ambiguity. The legislative language, however, makes it equally clear that Congress did not expect us to sit on the sidelines this year. The act imposes regular reporting requirements on NTIA to keep Congress apprised of the transition process. To meet those requirements, NTIA will actively monitor the discussions and activities within the multistakeholder community as it develops the transition plan. We will participate in meetings and discussions with ICANN, Verisign, other governments and the stakeholder community with respect to the transition. We will continue to represent the United States at the meetings of ICANN's Governmental Advisory Committee. We will provide informal feedback where appropriate. We are as aware as anyone that we should not do anything that interferes with an open and participatory multistakeholder process. We support a process where all ideas are welcome and where participants are able to test fully all transition options. Nonetheless, the community should proceed as if it has only one chance to get this right. Everyone has the responsibility to participate as they deem appropriate. If, by asking questions, we can ensure that the community develops a well-thought-out plan that answers all reasonable concerns, we will do so. "
• Internet Assigned Numbers Authority Stewardship Transition Consolidated Proposal and Internet Corporation for Assigned Names and Numbers Accountability Enhancements; Request for Comments, NTIA, 80 Fed. Reg. 153 August 10, 2015
• Notice of Comment Periods on Transitioning NTIA’s IANA Stewardship Role August 11, 2015 NTIA
• "In recent days both the IANA Stewardship Transition Coordination Group (ICG) and the Cross Community Working Group (CCWG) on Enhancing ICANN Accountability have posted their proposals for review and final public comment. Comments are due September 8, 2015, for the ICG’s proposal (link is external) and September 12, 2015, for the CCWG’s proposal (link is external)."
• 06/21/2015 Remarks of Lawrence E. Strickling Assistant Secretary of Commerce for Communications and Information ICANN Meeting
• 05/13/15 Second Quarterly Report on the Transition of the Stewardship of the Internet Assigned Numbers Authority (IANA) Functions
• ICANN. Transition of NTIA’s Stewardship of the IANA Functions: Process to Develop the Proposal and Next Steps, accessed May 4, 2015
• 3/14/15 NTIA Announces Intent to Transition Key Internet Domain Name Function
• August 17, 2015 An Update on the IANA Transition, NTIA ("we plan to extend our IANA contract with ICANN for one year to September 30, 2016. Beyond 2016, we have options to extend the contract for up to three additional years if needed")
• 2/25/15 Testimony of Assistant Secretary Strickling before the Senate Committee on Commerce, Science, and Transportation on “Preserving the Multistakeholder Model of Internet Governance”
• 2/11/15 First Quarterly Report on the Transition of the Stewardship of the Internet Assigned Numbers Authority (IANA) Functions
• 1/27/15 Remarks by Assistant Secretary Strickling at the State of the Net Conference 1/27/2015
• 12/16/14 NTIA’s Role in Root Zone Management
• 12/4/14 Remarks by Assistant Secretary Strickling at the PLI/FCBA Telecommunications Policy & Regulation Institute
• 6/23/14 Remarks by Assistant Secretary Strickling at ICANN High Level Governmental Meeting
• 4/25/14 Official Statement by the USG Delegation to NETmundial
• NTIA Announces Intent to Transition Key Internet Domain Name Functions March 14, 2014
• To support and enhance the multistakeholder model of Internet policymaking and governance, the U.S. Commerce Department’s National Telecommunications and Information Administration (NTIA) today announces its intent to transition key Internet domain name functions to the global multistakeholder community. As the first step, NTIA is asking the Internet Corporation for Assigned Names and Numbers (ICANN) to convene global stakeholders to develop a proposal to transition the current role played by NTIA in the coordination of the Internet’s domain name system (DNS).
• "Consistent with the clear policy expressed in bipartisan resolutions of the U.S. Senate and House of Representatives (S.Con.Res.50 and H.Con.Res.127), which affirmed the United States support for the multistakeholder model of Internet governance, NTIA will not accept a proposal that replaces the NTIA role with a government-led or an inter-governmental organization solution."
• 4/24/14 Myths and Facts on NTIA Announcement on Intent to Transition Key Internet Domain Name Functions
• 4/02/2014 IANA Transition Testimony and Related Material
• Assessment of the Transition of the Technical Coordination and Management of the Internet's Domain Name and Addressing System Proceeding Comments Due June 8, 2009. Docket No. 090420688-9689-01 Fed Reg April 24 
• The Continued Transition of the Technical Coordination and Management of the Internet Domain Name and Addressing System Docket No. 060519136-6136-01 Comments due July 7, 2006. Public meeting 2:00 p.m. to 5:00 p.m. July 26, 2006. NTIA Notice: The United States Department of Commerce's National Telecommunications and Information Administration (NTIA) seeks comment on the continuation of the transition of the technical coordination and management of the Internet domain name and addressing system (Internet DNS) to the private sector. In June 1998, the Department issued a statement of policy on the privatization of the Internet DNS, which among other things articulated four primary functions for global Internet DNS coordination and management, the need to have these functions performed by the private sector and four principles to guide the transition to private sector management of the Internet DNS. On June 30, 2005, NTIA released the U.S. Principles on the Internet's Domain Name and Addressing System further elaborating on these issues. The Department of Commerce seeks comment regarding the progress of this transition and announces a public meeting to be held on July 26, 2006, to discuss issues associated with this transition.
• NTIA letter to ICANN regarding Reform, NTIA 7/19/02
• Statement of Policy on the Management of Internet Names and Addresses 1998 (Initiating transition of IANA function.)

IANA Transition Legislation

"H.R. 4342 (the DOTCOM Act) was approved by the House Energy and Commerce Committee on May 8, 2014, to prohibit the NTIA from relinquishing responsibility over the Internet domain name system until the Government Accountability Office (GAO) submits a report to Congress examining the ramifications of the proposed transfer. The language of H.R. 4342 was successfully added as an amendment to H.R. 4435, the FY2015 National Defense Authorization Act, which was passed by the House on May 22, 2014. The Senate’s FY2015 National Defense Authorization bill (S. 2410) and the House and Senate FY2015 Commerce,Justice, Science appropriation bills (H.R. 4660/S. 2437) also address the proposed transition. Additionally, other bills introduced into the 113th Congress (H.R. 4367 and H.R. 4398) would place limits on NTIA’s ability to transfer its authority over certain domain name functions. " [CRS DNS i 2014]

IANA Transition Hearings

• Senate Judiciary Hearing Protecting Internet Freedom: Implications of Ending U.S. Oversight of the Internet Sept.14, 2016
• Testimony of Assistant Secretary Strickling on Protecting Internet Freedom: Implications of Ending U.S. Oversight of the Internet Sept. 14, 2016
• House Commerce Committee: Privatizing the Internet Assigned Number Authority Thursday, March 17, 2016 - 10:15am
• House Commerce Committee: Stakeholder Perspectives on the IANA Transition Wednesday, May 13, 2015 - 2:00pm
• Senate Commerce Committee May 24, 2016 Examining the Multistakeholder Plan for Transitioning the Internet Assigned Number Authority

IANA Transition News

• David Ignatius, Let the Geeks Rule the Internet, Washington Post August 2, 2016 ("Crocker and Chehade argue that continuation of this peculiar, independent, tech-driven body is in fact the only way to keep the system open and honest. Crocker explains the protections that ICANN has designed into the system. If any nation, or private hacker, tried to introduce bad information into the architecture, it would be detected instantly. And sabotaging domain names would be impossible because the information is so widely distributed. A committee of engineers, drawn from the United States, Europe and Asia, will oversee the “root” system that Postel created. Another global panel of engineers will guard the system’s security. ")
• David Post, Some Congressional Confusion About the Internet and the 'IANA Transition', Washington Post Oct. 2, 2015 ("The transition involves nothing more than the termination of a series of contracts, pursuant to which ICANN was performing certain services for and on behalf of the U.S. government (including management of the Internet’s critical “root zone file”). There is no “territory” or “property” being transferred. It’s true that ICANN will, post-transition, be managing the root zone file on its own; but the file is not government “property.” It’s a simple text file that consists of a list of all of the currently recognized top-level domains (.com, .net, .biz, .museum, .br, .jp, .uk …) and the Internet location of the nameservers that support each of them.")
• David Post, Internet Governance: What if the Sky Really is Falling, Washington Post May 4, 2015 ("before we complete this transition to a global non-governmental institution for all DNS management functions, we need to be re-assured that safeguards are firmly in place to insure that something like this doesn’t happen, that whoever is in charge of DNS policy-making sticks to its knitting.")
• Philip S. Crowin, NTIA Says Cromnibus Bars IANA Transition During Current Contract Term CircleID Jan. 27, 2015
• Matthew Shears, Protect the Internet: Support the IANA Transition, CDT Jan. 7, 2015
• Protect the Internet: Keep the Contract with ICANN, WAPO Editorial January 5, 2015 ("The problem is that no one yet has a convincing explanation for how the multi-stakeholder model will be immune to pernicious influences from governments. Independent voices from global nongovernmental interests are supposed to suffuse the ICANN system and provide a self-correcting ethos. But civil society in many countries is deeply connected to the state, and those states will try to manipulate or control as much as they can. Details of the technical transition are being hammered out, but the accountability measures and controls that will be vital to establishing and preserving a legitimate global Internet governance are taking longer.")

 

NTIA / ICANN Contracts for IANA Function

• Federal Register Notice : Internet Assigned Numbers Authority (IANA) Functions Further Notice of Inquiry:

  NTIA is seeking public comment on a draft statement of work, a key element of the procurement process for the new IANA functions contract. (471 KB PDF) Posted June 10, 2011

  SUMMARY: Critical to the Internet Domain Name System (DNS) is the continued performance of the Internet Assigned Numbers Authority (IANA) functions. The IANA functions have historically included: (1) the coordination of the assignment of technical Internet protocol parameters; (2) the administration of certain responsibilities associated with Internet DNS root zone management; (3) the allocation of Internet numbering resources; and (4) other services related to the management of the ARPA and INT top-level domains (TLDs). The Internet Corporation for Assigned Names and Numbers (ICANN) currently performs the IANA functions, on behalf of the United States Government, through a contract with United States Department of Commerce's National Telecommunications and Information Administration (NTIA). On February 25, 2011, NTIA released a Notice of Inquiry (NOI) to obtain public comment on enhancing the performance of the IANA functions. NTIA received comments from a range of stakeholders: governments, private sector entities, and individuals. After careful consideration of the record, NTIA is now seeking public comment through a Further Notice of Inquiry (FNOI) on a draft statement of work (Draft SOW), a key element of the procurement process for the new IANA functions contract.

• DEPARTMENT OF COMMERCE National Telecommunications and Information Administration [Docket No. 110207099-1099-01] RIN 0660-XA23 Request for Comments on the Internet Assigned Numbers Authority (IANA) Functions

  SUMMARY: The United States Department of Commerce's National Telecommunications and Information Administration (NTIA) remains committed to preserving a stable and secure Internet Domain Name System (DNS). Critical to the DNS is the continued performance of the Internet Assigned Numbers Authority (IANA) functions. The IANA functions have historically included: (1) The coordination of the assignment of technical Internet protocol parameters; (2) the administration of certain responsibilities associated with Internet DNS root zone management; (3) the allocation of Internet numbering resources; and (4) other services related to the management of the .ARPA and INT top-level domains. The Internet Corporation for Assigned Names and Numbers (ICANN) currently performs the IANA functions, on behalf of the United States Government, through a contract with NTIA . Given the September 30, 2011 expiration of this contract, NTIA is seeking public comment to enhance the performance of the IANA functions in the development and award of a new IANA functions contract.

• ICANN Contract Term Extended : NTIA exercised the option to extend the term of the IANA Functions contract with ICANN for Option Year Three covering the 1-year period of October 1, 2009 through September 30, 2010.
  September 1, 2009
• ICANN Contract Term Extended : NTIA exercised the option to extend the term of the IANA Functions contract with ICANN for Option Year Two covering the 1-year period of October 1, 2008 through September 30, 2009.
  September 4, 2008
• ICANN Contract Term Extended : NTIA exercised the option to extend the term of the IANA Functions contract with ICANN for Option Year One covering the 1-year period of October 1, 2007 through September 30, 2008.
  Posted 09-27-2007
• ICANN Awarded Contract for Internet Domain Name Technical Functions: NTIA awarded a sole source contract to the Internet Corporation for Assigned Names and Numbers (ICANN) to perform technical functions supporting the Internet Domain Name system.
  ICANN Contract [ -- Acrobat PDF --]
  ICANN proposal incorporated into contract [Acrobat PDF]
  Updated 09-05-2006
• IANA Functions Pre solicitation Notice
  A pre solicitation notice announcing the Department's intent to award a sole-source, no-cost purchase order to the Internet Corporation for Assigned Names and Numbers for the performance of the IANA functions
  . Pre solicitation notice to award purchase order to ICANN (Acrobat PDF format)
  . Modification of Pre solicitation notice (Acrobat PDF format)
  . IANA Functions Statement of Work (Acrobat PDF format)
• Modification 5 to the contract with the Internet Corporation for Assigned Names and Numbers (ICANN) for Internet Assigned Numbers Authority (IANA) functions. (in pdf format) April 1, 2006
• Modification 4: NTIA exercised the option to extend the term of the contract for Option Period Three (Item No. 0004) for the six month period of October 1, 2005 through March 31, 2006. The contract was also modified to include changes to the content of reporting deliverables and new metrics for performance. (in pdf format)
• Modification 3 to the contract with the Internet Corporation for Assigned Names and Numbers (ICANN) for Internet Assigned Numbers Authority (IANA) functions. (in pdf format) August 30, 2004
• Modification 2 to the contract with the Internet Corporation for Assigned Names and Numbers (ICANN) for Internet Assigned Numbers Authority (IANA) functions. September 16, 2003
• D -- Operation of the Internet Assigned Numbers Authority (IANA) functions. Pre solicitation Notice Jan 28 2003
• Modification 1 to the contract with the Internet Corporation for Assigned Names and Numbers (ICANN) for Internet Assigned Numbers Authority (IANA) functions. August 28, 2003
• New contract with the Internet Corporation for Assigned Names and Numbers (ICANN) for Internet Assigned Numbers Authority (IANA) functions effective April 1st. Although ICANN has performed these functions on behalf of the Commerce Department since February 2000, the new Statement of Work reflects an evolution in performance of tasks such as coordination of the assignment of technical protocol parameters, administrative functions associated with root server management, and allocation of Internet numbering resources. Requirements mandating quarterly statistical and narrative information and the development of new processing metrics are included in the new contract. March 13, 2003
• NTIA exercised the option to extend the term of the contract with ICANN for IANA functions for Option Period Two (Item No. 0003) for the six-month period of 10/01/2002 through 03/31/2003. October 1, 2002
• Amendment 2 to the IANA Functions Purchase Order . August 17, 2002
• NTIA exercised the option to extend the term of the contract with ICANN for IANA functions for Option Period One (Item No. 0002) for the six-month period of 04/01/2002 through 09/30/2002. April 1, 2002
• Internet Assigned Numbers Authority Purchase Order #2 in Word or pdf format. March 21, 2001
• Purchase Order February 9, 2000 (47MB pdf file).
• Modification 1 September 8, 2000
• Modification 2 October 1, 2000
• NTIA: IANA Documents

Hearings

• INTERNET DOMAIN NAMES, PART I THURSDAY, SEPTEMBER 25, 1997 U.S. House of Representatives, Committee on Science, Subcommittee on Basic Research, Washington, DC.
  • Testimony of Jon Postel: As a side task to this research work, I took on the task of keeping some lists of names and numbers and conventions that were parts of the protocols that were developed to support the computer communication. Over the years, this task grew fairly slowly even though the ARPANET and then the Internet grew very rapidly. In about 1989, the name Internet Assigned Numbers Authority or IANA was adopted to describe this sort of keeping of the list function and coordination activity.

  Currently, the IANA coordinates the assignment and the use of various Internet protocol conventions, manages at the top level the Internet address space, and has a role in the management of domain names. Specifically regarding domain names, it's involved in the technical decisions about the locations and equipment used for the root name servers, the qualifications of applicants to manage what's called the country code top level domains, and in evaluating additions to the established set of top level domain names of the generic top level domain names.
      This IANA role seems to be somewhat difficult to understand, but perhaps an analogy with the telephone system can help. When telephone engineers decide that a new area code is needed because the number of telephone numbers in a metropolitan area say has grown, they need to attain a new area code. To do this, they contact an office that manages something called the North American Telephone Numbering Plan, or the Naming Authority Council. This authority keeps a list of area codes that have already been used and the ones that are available and a few other conventions of the system. So in some ways, the IANA is the equivalent of the Telephone Naming Authority, numbering authority for the Internet.
      The role of IANA is much more one of coordination than of control. The IANA tends to implement the consensus of the Internet community and its policies and decisions about the allocations of addresses, names and the maintenance of those various protocol conventions.
      I would also like to point out that the Internet operates in a climate of sort of a dynamic tension between competition and cooperation. Much of the work of the decision making in the Internet is based on a consensus-building approach. There are many examples of this. Perhaps the most basic is the competition between service providers. Service providers compete vigorously to obtain the most customers, but at the same time, they must cooperate to provide the end to end service that the customers demand of being able to contact anyone else anywhere in the Internet. There are many other examples of the way things work in the Internet, where there is a tension between cooperation and competition.

   On the subject of the domain names system, which is the topic of this hearing, I will make a few remarks. The main reason for concern about the domain names system at this time is that registration of domain names has become a business rather than a public service. There is essentially one company in a substantially monopoly position. It is important that there be competition in a business environment to provide good service at fair prices due to the market forces that apply in such a situation. So I think the motivation for the transition that we are going through is essentially to overcome this sort of monopoly situation and evolve into a competitive situation.
      I believe the plan developed by the IAHC process is the best available alternative of the way to introduce this competition, and that the plan as developed as this concept of shared registries, which allow name portability between registration service providers. They are somewhat akin to the 800 number portability in the telephone system.
      This transition is a very important matter and is appropriate for the government to be concerned about it. However, the evolution of the Internet through the IAHC plan seems to be on track. I think it is very important for the government to be concerned, and yet not get involved as long as good things seem to be happening through that plan.
      There are a few issues that were mentioned in the charter for this hearing. I would like to touch on those very briefly. As I have just said, the federal role should be one of being supportive of the DNS transition to a fully self-regulated system, but not necessarily take any particular action as long as that seems to be going on track.
      There is a question about the database and the data that's been developed by Network Solutions in its work to date. My view is that the data that's currently publicly available that is used to operate the system should be made publicly available and made available to the government. There may be other data that Network Solutions has developed for its business purposes. That is completely a separate matter.
  
  On the issue of the infrastructure funds, this fund has been developed of $30 million or so, I think care should be taken to understand that fund was contributed by a certain set of people, the businesses and the users of the Internet, and that the use of that fund should benefit those people that contributed to it, and not necessarily be diverted to other interesting government projects. On the Administration plan, it's I think still in the formation stages, so I don't really have any comments yet on that plan.
      In conclusion, I would like to say I think the general plan developed by the international ad hoc committee should move ahead in a steady and careful fashion. The plan provides for competition between registration agents serving the user community. It calls for cooperation in managing and maintaining the unique data base of registered names. This again is modeled on something that we do in many places in the Internet.
      There may be aspects of the plan that need some adjustments or fine tuning. I think those can be accommodated as the plan moves foreword. I expect that there's a role for the IANA to continue to be involved in the sort of high level overall management of the Internet.
      I have tried to keep these remarks brief, and would be pleased to expand on any of these topics in response to your questions. Thank you.

 

Timeline

• 2011 Feb. 3: Last IP Address Blocks handed down from IANA to RIRs
• 2000 the Department of Commerce entered into a contract with ICANN for ICANN to do the IANA function
• 1999 IANA function was transferred to ICANN
• 1998:
  • 26th October: First Meeting ICANN [Houston]
  • Green Paper and then White Paper Published. See NTIA
  • October: Jon Postel dies
  • Jon Postel redirects Root away from NetSol and to IANA. White House calls and tells him to stop. [Donelan] [Wikipedia] [Houston ("January 1998 also saw Jon Postel redirect the authority point of the root server constellation to his own root server, and this move caused considerable angst in Washington. Heated words were exchanged, intervention from the FBI was threatened, and Jon backed down.")]
• 1997: Rogue Registry Sues IANA, CNET (Feb. 28, 1997) (IANA / Jon Postel sued by Image Online Design claiming that IANA had promisted it the new gTLD ".WEB")
• 1993: Classless Interdomain Routing
• 1991: "NIC transitioned to Government Systems Inc., who subcontracted the work to Network Solutions, Inc." [ISOC p 2]
• 1990: J Reynolds, J. Postel, Network Working Group RFC 1060, Assigned Numbers March 1990 (first reference to IANA: "This RFC will be updated periodically, and in any case current information can be obtained from the Internet Assigned Numbers Authority (IANA).")
• 1988 IANA (at ISI) was funded by DARPA. This contract expired in 1997.
• 1987: "the responsibility for the assignment of IP numbers and ASNs was assumed by the Hostmaster at the DDN Network Information Center." [ISOC p 2]
• 1983: Joyce Reynolds begins to assist with the IANA function
• 1977: Postel joins the staff of University of Southern California 's Information Sciences Institute
• 1969:
  • Jon Postel volunteers, as a part of the Network Working Group, to manage the networks names and numbers, what will become the IANA function. Postel, according to histories, kept track of network number assignments in a paper notebook.
  • Steve Crocker, Network Working Group RFC 3, Documentation Conventions, April 1969 ("The Network Working Group (NWG) is concerned with the HOST software, the strategies for using the network, and initial experiments with the network.")

References

• RFC 2860, Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority (June 2000)
• Geoff Houston, How Did We Get Here? A Look Back at the History of IANA, CIRCLEID Oct. 23, 2016