--- id: "iana" kind: "glossary-term" title: "IANA" language: "en" category: "Industry roles and organizations" updated: "2026-10-10T10:28:55Z" canonical: "https://tldlog.com/glossary/iana/" translations: es: "https://tldlog.com/es/glosario/iana/" de: "https://tldlog.com/de/glossar/iana/" fr: "https://tldlog.com/fr/glossaire/iana/" it: "https://tldlog.com/it/glossario/iana/" pt-BR: "https://tldlog.com/pt/glossario/iana/" ru: "https://tldlog.com/ru/glossariy/iana/" zh-Hans: "https://tldlog.com/zh/cihui/iana/" --- # IANA Internet Assigned Numbers Authority The functions that keep the internet's unique identifiers coordinated, including managing the DNS root zone, IP address pools and protocol number lists. PTI (Public Technical Identifiers), an ICANN affiliate, performs these functions today. IANA's root zone database lists every TLD and its manager. IANA, the Internet Assigned Numbers Authority, keeps the public lists that make internet names, addresses and technical codes mean the same thing everywhere. It applies rules written by others; it does not make them. Since 1 October 2016 an ICANN affiliate called PTI does this work, with no United States government approval step. ## What IANA is For the internet to work as one network, each domain name and IP address must belong to a single party, and all software must read protocol codes the same way. IANA maintains the authoritative public registries that record these assignments. The role is a public service: the registries are openly published and the services are free. IANA calls itself a neutral steward. It does not set the policies for its registries; it implements those developed by the communities each registry serves. It does not decide which TLDs should exist. The work goes back to the record-keeping of the first network experiments in the 1970s. Today "IANA" names the functions; the organisation that performs them is Public Technical Identifiers (PTI). ## The three IANA functions: names, numbers and protocol parameters **Names.** IANA manages the DNS root zone, the top of the naming hierarchy. It assigns the manager of each TLD, records the technical delegation data and publishes the Root Zone Database. Policy comes from ICANN, mainly through the GNSO for generic names and the ccNSO for country codes. **Numbers.** IANA coordinates IP addresses and the autonomous system (AS) numbers used to route traffic. It allocates large pools of addresses to the five RIRs (AFRINIC, APNIC, ARIN, LACNIC and RIPE NCC), not to internet service providers or end users, except in special cases. Global number policy comes from the RIR communities and is ratified through ICANN's Address Supporting Organization (ASO). RIRs handle numbers, not domain names. **Protocol parameters.** These are the codes and numbers used inside internet protocols. Under RFC 2860 (June 2000), IANA assigns them only as RFCs direct. ## IANA, PTI and ICANN: how they fit PTI is a California nonprofit public benefit corporation formed in 2016. ICANN is its sole member, and PTI's only purpose is to deliver the IANA functions. Its board combines directors appointed by ICANN and directors drawn from the community. ICANN holds the obligations and subcontracts the work to PTI, with one agreement per function: - names: the ICANN–PTI Naming Function Agreement, which sets service levels for root zone management; - protocol parameters: a memorandum of understanding between ICANN and the IETF, plus annual agreements; - numbers: a service level agreement (SLA) between ICANN and the five RIRs. The ICANN Bylaws add safeguards. Changes to PTI's articles of incorporation need the approval of the Empowered Community, and fees charged by PTI under the naming contract must be based on its direct costs. ## Stewardship transition of 2016 ICANN has performed the IANA functions since 1999. From 2000 to 2016, a contract with the NTIA, part of the United States Department of Commerce, governed how. Under it, United States government approval was a mandatory step for root zone change requests. In March 2014 the NTIA set criteria for ending this role and asked ICANN to convene the global multistakeholder community. The community wrote proposals to replace the NTIA's stewardship and strengthen ICANN's accountability; they met the criteria and were approved. The last IANA functions contract lapsed on 30 September 2016, and the transition was completed on 1 October 2016. That day PTI began performing the functions, with the same staff and the same website, `www.iana.org`. New accountability rules came into force at the same time, giving the community direct recourse when it disagrees with ICANN or its Board. The Affirmation of Commitments, a 2009 agreement between ICANN and the Department of Commerce, had required regular community reviews of ICANN. Once those reviews had moved into Article 4 of the ICANN Bylaws, ICANN and the NTIA ended it by mutual agreement on 6 January 2017. The NTIA stayed in ICANN as the United States member of the GAC. ## Who checks IANA's work - **Customer Standing Committee (CSC).** Every month it checks PTI's naming performance against the service levels in the naming contract and publishes its findings. It can ask for problems to be fixed and escalate them to the ccNSO and GNSO, but cannot start a special review itself. Under the Bylaws as of October 2026, it has two gTLD registry representatives, two ccTLD representatives and one PTI liaison. - **IANA Naming Function Review (IFR).** The first was due by 1 October 2018; under the same Bylaws, the next ones follow at least every five years, with special reviews possible. - **Separation, as a last resort.** PTI can be replaced as naming operator only if an IFR recommends it, supermajorities of the ccNSO and GNSO Councils approve, the public is consulted and the ICANN Board agrees. - **Other checks.** The Root Zone Evolution Review Committee (RZERC) reviews proposed architectural changes to the root zone. The RIRs and the IETF review the number and protocol functions. As of October 2026, IANA reports meeting 100% of its service levels in all three functions from June to August 2026; its weakest naming month in the previous year was December 2025, at 94%. A worked example: a ccTLD manager wants to change its TLD's name servers in the root zone. It submits the change through IANA's online interface for TLD managers. No United States government approval applies, and PTI's handling counts toward the service levels the CSC reviews each month. ## Sources - [About IANA](https://www.iana.org/about) - [About the IANA stewardship transition](https://www.iana.org/help/pti-transition) - [ICANN Bylaws (Articles 16 to 19)](https://www.icann.org/en/governance/bylaws) - [Performance (IANA)](https://www.iana.org/performance) ## related terms - [PTI](https://tldlog.com/glossary/pti/) - [ICANN](https://tldlog.com/glossary/icann/) - [root zone](https://tldlog.com/glossary/root-zone/) - [delegation (TLD)](https://tldlog.com/glossary/delegation/)