Oversight
We do not set the policies by which the IANA registries are administered. Instead, we implement policies developed by the communities each registry serves, in a neutral and responsible manner, and our performance in doing so is monitored by various oversight bodies.
Policy Development
Each of the IANA functions has its own policy community:
- Domain names. Policy affecting the domain name system is developed through ICANN's multistakeholder processes, principally its supporting organizations for generic and country-code names — the GNSO and the ccNSO — with advice from ICANN's advisory committees.
- Number resources. Global policy for IP addresses and autonomous system numbers is developed within the five Regional Internet Registry communities and ratified through ICANN's Address Supporting Organization.
- Protocol parameters. The Internet Engineering Task Force (IETF) standards process defines the protocol parameter registries and the policies for making assignments in them, with architectural guidance from the Internet Architecture Board.
Oversight Bodies
- Customer Standing Committee (CSC). Monitors our monthly naming performance reports against established service level expectations on behalf of the naming community.
- Root Zone Evolution Review Committee (RZERC). Reviews proposed architectural changes to the content of the DNS root zone and the systems that maintain it.
- IETF. Oversees the protocol parameter function under a memorandum of understanding with ICANN, reviewed annually through supplemental agreements.
- Regional Internet Registries. Review performance of the number resource function under their service level agreement with ICANN.
- PTI Board and ICANN. Corporate accountability for the delivery of the functions, described in Governance.
Community Engagement
To keep improving our operations, we actively engage with the communities we serve. As well as participating in ICANN forums, we take part in meetings and discussions with TLD operators, Regional Internet Registries, and other relevant communities, and provide staffed helpdesks at key meetings for one-to-one interaction with users of our services, such as protocol developers and operators of critical Internet infrastructure.