Jump to content

Root Zone Management: Difference between revisions

From ICANNWiki
Jessica (talk | contribs)
No edit summary
Christiane (talk | contribs)
m Christiane moved page RZM to Root Zone Management: Standardize
 
(No difference)

Latest revision as of 20:36, 24 June 2024

The DSN Root Zone Management System (RZM) is the automated system used to process change requests for TLDs [1] and to delegate new gTLDs once they have passed PDT.[2]

History[edit | edit source]

The RZM was created to process change requests more efficiently and was launched on July 21, 2011 by ICANN, Verisign, and NTIA.[3] It automated the previously manual process and gave the additional benefits of allowing more transparency and decreasing processing time.[1] In late fall 2022, IANA upgraded the RZM with the aim of providing more features for administering top-level domains (TLDs). With the upgrade, TLD managers can authorize additional people to interact with IANA with custom authorization levels according to their roles in their organization. It gives managers the flexibility to tailor configurations for improved cybersecurity. Other improvements include the ability to submit multiple requests simultaneously. For registries that manage many TLDs, a preliminary application programming interface streamlines their bulk updates. A session at ICANN 75 was dedicated to providing an in-depth overview of the new features.[4]

New gTLD system[edit | edit source]

In the new gTLD application process, once an applicant has received their delegation token from IANA, the applicant can enter it on IANA's Delegate a New Generic Top-Level Domain page in order to assume "operational responsibility" of the new gTLD [2]. According to a statement by ICANN, Verisign, and NTIA, RZM can process "at least 100 new gTLDs per week." [5] However, there was some apprehension that Verisign would not delegate new gTLDs due to stability concerns. [6] This statement has been largely debunked. Despite Verisign's ongoing concerns over stability, it has been delegating new gTLDs. [7][8]

References[edit | edit source]