Document Actions

IANA

IANA LogoLearn more about the NTIA's plans to transition out of IANA stewardship

The Internet Assigned Numbers Authority (IANA) is responsible for the global coordination of the DNS Root, IP addressing, and other Internet protocol resources. It is a set of functions that is currently contracted out by the National Telecommunications and Information Administration (NTIA), an agency in the U.S. Department of Commerce. The IANA function is currently carried out by ICANN.

With regard to Internet number resources, IANA's role is to allocate IP addresses and AS Numbers from the pools of unallocated resources to the Regional Internet Registries (RIRs) according to their needs, and to document protocol assignments made by the IETF. When an RIR requires more IP addresses for allocation or assignment within its region, IANA makes an additional allocation to the RIR.

IANA does not make allocations directly to ISPs or end users except in specific circumstances, such as allocations of multicast addresses or other protocol-specific needs.

Global Policy Development

The policies under which the IANA role is carried out are referred to as Global Addressing Policies, and must be agreed to by all of the five RIR communities. Any new policy proposal must go through the Policy Development Process in each RIR and be ratified by each community, and this process will then be reviewed by the ASO Address Council (ASO AC) before the new global policy is adopted.

More information:

 

IANA News

IANA Stewardship Transition

On 1 October 2016, the IANA functions contract that the U.S Government had with ICANN was allowed to expire. This was the final step in a community-led IANA stewardship transition process that began in 2014. Oversight of IANA is now the responsibility of the Names, Numbers and Protocol Parameters communities that rely on its services. This page has archived documents and announcements relating to the IANA stewardship transition:

Cooperation Working Group

The Cooperation Working Group is an open forum for discussion focusing on collaboration between the private and public sectors on Internet matters. This kind of collaboration has taken on increased prominence in recent years, as the wider Internet community strives to ensure that all voices are heard and the interests of all parties are considered. Fostering more open dialogue between all stakeholders is vital to ensuring the continued stability of the Internet. To post a message to the list, send an email to cooperation-wg@ripe.net. Please note that only subscribers can post messages.

RIPE NCC to Assign LISP EID Prefixes

From today, the RIPE NCC performs registry functions for IPv6 Endpoint ID (EID) prefixes for Locator/Identifier Separation Protocol (LISP). LISP is an experimental "map-and-encapsulate" protocol developed by the Internet Engineering Task Force's (IETF's) LISP Working Group. The IANA has assigned an IPv6 prefix for LISP EID space in accordance with RFC7954, which the RIPE NCC is now managing in accordance with RFC7955.

IANA Stewardship Transition Completed

On 1 October 2016, the IANA functions contract that the United States Government had with ICANN was allowed to expire. This represents the final step in the community-led IANA stewardship transition process that began in 2014. Oversight of IANA is now the responsibility of the Names, Numbers and Protocol Parameters communities that rely on its services.

RIPE NCC Receives /18 from IANA’s Recovered Pool

On 1 September 2016, the RIPE NCC and other Regional Internet Registries (RIRs) were each allocated the equivalent of a /18 of IPv4 address space from the Internet Assigned Numbers Authority (IANA).

ICANN 55: IANA, Accountability and Public Safety

ICANN 55 was held from 5-10 March 2016 in Marrakech, Morocco, and marked another milestone in the march towards transition of the IANA functions stewardship to the global Internet community. RIPE NCC Executive Board members, staff and RIPE community participants took part in meetings throughout the week, discussing issues ranging from IANA stewardship and the accountability of ICANN to the accuracy of RIR whois databases.

RIPE NCC Receives /15 from IANA's Recovered Pool

Yesterday, on 1 March 2016, the RIPE NCC and other Regional Internet Registries (RIRs) were each allocated the equivalent of a /15 of IPv4 address space from the Internet Assigned Numbers Authority (IANA). The RIPE NCC received the IPv4 address ranges 45.65.64.0/18, 147.78.0.0/16, 192.144.0.0/18 and 192.145.0.0/17. We are currently adding these to our available pool.

RIPE NCC Receives /14 from IANA's Recovered IPv4 Pool

Yesterday, on 2 September 2015, the RIPE NCC and other Regional Internet Registries (RIRs) were each allocated a /14 of IPv4 address space from the Internet Assigned Numbers Authority (IANA). The RIPE NCC received the IPv4 address ranges 45.66.0.0/15, 139.28.0.0/16 and 152.89/16. We are currently adding this to our available pool.

ICANN 50: Talking IANA and Accountability

More than 3,000 people gathered in London last week to participate in the largest ever ICANN meeting. Some of the key issues discussed included the evolution of IANA stewardship arrangements and ICANN's accountability to its many stakeholders.

Legacy IPv4 Address Space Returned to IANA

On 22 April 2014, the RIPE NCC handed over 5,376 returned legacy IPv4 addresses to IANA. This is the second time the RIPE NCC has returned legacy IPv4 addresses to IANA. For more information, please see the original news item and related documents.

Get Involved

The Cooperation Working Group is an open forum for discussion focusing on collaboration between the private and public sectors on Internet matters. This kind of collaboration has taken on increased prominence in recent years, as the wider Internet community strives to ensure that all voices are heard and the interests of all parties are considered. Fostering more open dialogue between all stakeholders is vital to ensuring the continued stability of the Internet. To post a message to the list, send an email to cooperation-wg@ripe.net. Please note that only subscribers can post messages.