[image: ICANN Announcement Alerts] *IANA Naming Function Review Team Community Webinar <https://newsalerts.icann.org/q2EC0d08PD0N0302R0ga002>* 24 September 2020 LOS ANGELES – 21 September 2020 – Today, the Internet Assigned Numbers Authority (IANA) Naming Function Review Team (IFRT) has announced that it is in the final stages of completing its Initial Report. The IFRT will be holding a webinar for the community regarding one of their proposed recommendations that would require an amendment to the IANA Naming Functions Contract <https://newsalerts.icann.org/E0d0C0gERb80N02E2300P02> between the Internet Corporation for Assigned Names and Numbers (ICANN) and its affiliate Public Technical Identifiers (PTI). This amendment may be of particular interest to country code top-level domain (ccTLD) and generic top-level domain (gTLD) registry operators. Per the ICANN Bylaws <https://newsalerts.icann.org/z0282dP0000RNc32CgF0E00>, Article 18, Section 18.5.d.(a): "*The IFRT may recommend, among other things to the extent reasonably related to the IFR responsibilities set forth in Section 18.3, amendments to the IANA Naming Function Contract, IANA Naming Function SOW and/or the CSC Charter. The IFRT shall, at a minimum, take the following steps before an amendment to either the IANA Naming Function Contract, IANA Naming Function SOW or CSC Charter is proposed:……(iii) Conduct a public input session for ccTLD and gTLD registry operators.*" The IFRT noted that the IANA Naming Functions Contract <https://newsalerts.icann.org/E0d0C0gERb80N02E2300P02> contains a requirement relating to the formatting of IANA's monthly Root Operations Audit Reports <https://newsalerts.icann.org/v0080N3d0dPECgG2R022000> and this requirement can be considered obsolete. The IFRT therefore recommends that: *In Article 7 Section 7.1 (a) the IFRT recommends that this statement "The relevant policies under which the changes are made shall be noted within each monthly report" be removed from the contract, as it is a legacy statement from the NTIA contract that is no longer required.* The IFRT encourages all interested parties, and in particular ccTLD and gTLD registry operators, to join the scheduled informational webinar to learn more. Webinar Information *Date:* 29 September 2020 *Time:* 17:00 – 17:30 UTC *Webinar Link:* https://icann.zoom.us/j/96824197988?pwd=TGpISnFnck1TblpQdkthd0lHUzRxdz09 <https://newsalerts.icann.org/dd0Pg2eN320E800R0H020C0> *Passcode:* IFRT_09/29 A recording of the webinar will be made available on the IFRT's Wiki page <https://newsalerts.icann.org/m000NI20002d2Pg8R3f0CE0> and you may submit questions and comments at any time via their public email list input-to-IFRT@icann.org <https://newsalerts.icann.org/TJNC30g020008Rg20P02dE0>. For more information on the webinar, click here <https://newsalerts.icann.org/uhN0008R0P0d0K023g2CE20>. About IFR The IANA Naming Functions Review (IFR) is one of the accountability mechanisms created as part of the IANA stewardship transition to ensure that ICANN, via its affiliate Public Technical Identifiers (PTI), meets the needs and expectations of its naming customers. About ICANN ICANN's mission is to help ensure a stable, secure, and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. About PTI Public Technical Identifiers (PTI) is an affiliate of ICANN responsible for performing the IANA functions, which include management of the Domain Name System root zone, the global Internet Protocol address space and other protocol parameters that support Internet operation. PTI was formed in 2016 following a transition of stewardship to the multistakeholder community that relies upon the IANA functions. PTI performs the IANA functions under contract with ICANN. [image: shadow] *[image: Twitter] <https://newsalerts.icann.org/iL3C0NR2giP00d000822E00>* [image: Facebook] <https://newsalerts.icann.org/ujN0008R0P0d0M023g2CE20> [image: Instagram] <https://newsalerts.icann.org/R00P082R2d0020g0CkE3NN0> [image: Linkedin] <https://newsalerts.icann.org/v0080N3l0dPECgO2R022000> [image: YouTube] <https://newsalerts.icann.org/l3R2P000P28g0E2d00N0m0C> [image: shadow1] Unsubscribe <https://newsalerts.icann.org/wR8EN0dCP0000g2Q0022n03> | https://www.icann.org <https://newsalerts.icann.org/DCo000R0ER800302PN2g0d2> <https://newsalerts.icann.org/wR8EN0dCP0000g2S0022p03>