Root Zone Management: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=Overview= | =Overview= | ||
The DSN Root Zone Management System (RZM) is the automated system used to process change requests for | The DSN Root Zone Management System (RZM) is the automated system used to process change requests for [[TLD]]s <ref name="System View"> https://www.iana.org/help/rzm-system </ref> and to delegate new [[gTLD]]s once they have passed PDT<ref name="Delegate"> https://rzm.iana.org/rzm/newdelegation;jsessionid=573581408146FD71B45A8447A52AF099 </ref>. | ||
=History= | =History= | ||
It was originally created to process change requests more efficiently and was launched July 21, 2011 by [[ICANN]], [[Verisign]], and [[NTIA]]. <ref> http://blog.icann.org/2012/08/rzm-is-one-year-old/ Sokolova, Nadia. RZM Is 1 Year Old. </ref> Automating the previously manual process provided the additional benefits of allowing more transparency and decreasing processing time. <ref name="System View"></ref> | It was originally created to process change requests more efficiently and was launched July 21, 2011 by [[ICANN]], [[Verisign]], and [[NTIA]]. <ref> http://blog.icann.org/2012/08/rzm-is-one-year-old/ Sokolova, Nadia. RZM Is 1 Year Old. </ref> Automating the previously manual process provided the additional benefits of allowing more transparency and decreasing processing time. <ref name="System View"></ref> | ||
| Line 10: | Line 10: | ||
=References= | =References= | ||
<references/> | <references/> | ||
[[Category:New gTLD Program]] | |||
__NOTOC__ | |||
Revision as of 08:31, 20 December 2014
Overview[edit | edit source]
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]
It was originally created to process change requests more efficiently and was launched July 21, 2011 by ICANN, Verisign, and NTIA. [3] Automating the previously manual process provided the additional benefits of allowing more transparency and decreasing processing time. [1]
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." [4] However, there was some apprehension that Verisign would not delegate new gTLDs due to stability concerns. [5] This statement has been largely debunked. Despite Verisign's ongoing concerns over stability, it has been delegating new gTLDs. [6][7]
- IANA's Delegating a generic top-level domain page provides instructions for new gTLD delegation.
- See New TLD contracting for more information on the new gTLD registration process.
References[edit | edit source]
- ↑ 1.0 1.1 https://www.iana.org/help/rzm-system
- ↑ 2.0 2.1 https://rzm.iana.org/rzm/newdelegation;jsessionid=573581408146FD71B45A8447A52AF099
- ↑ http://blog.icann.org/2012/08/rzm-is-one-year-old/ Sokolova, Nadia. RZM Is 1 Year Old.
- ↑ http://domainincite.com/10961-icann-verisign-and-ntia-ready-for-100-new-gtlds-per-week Murphy, Kevin. ICANN, Verisign, and NTIA 'Ready for 100 new gTLDs Per Week'
- ↑ http://domainincite.com/13979-ntia-alarmed-as-verisign-hints-that-it-will-not-delegate-new-gtlds Murphy, Kevin. NTIA Alarmed as Verisign Hints that It Will Not Delegate New gTLDs
- ↑ http://domainincite.com/15274-german-geo-ruhr-enters-the-root Murphy, Kevin. German Geo Ruhr Enters the Root, 11 Dec. 2013
- ↑ http://blogs.verisigninc.com/blog/entry/verisign_delegates_four_new_gtlds Kane, Pat. Verisign Delegates Four New gTLDs to the Root Zone, 23 Oct. 2013