Data Escrow: Difference between revisions

Line 1:

{{Glossary|

|note = This article is neutral, but is [[Sponsorship|sponsored]] by [[Iron Mountain]].<br/>Iron Mountain is an information & intellectual property<br/>management company and data escrow provicer.<br/>You can read more about their services [http://www.ironmountain.com/ here].

|logo = IRON Mountain-Logo.png

|silversponsor = ICANNWiki [[Sponsorship|Silver Sponsor]]

}}

'''Data Escrow''' is the act of storing data with a neutral third party<ref>[http://www.guard-it.com/faqs.html Guard-It.com FAQs]</ref> in case of registry or registrar failure, accreditation termination, or accreditation relapse without renewal. [[ICANN]] requires all registrars and gTLD registries to contract with a data escrow provider in order to safeguard registrants.<ref>[http://www.icann.org/en/news/announcements/announcement-2-09nov07-en.htm Implementation of Registrar Data Escrow Program, icann.org]</ref><ref>[http://archive.icann.org/en/tlds/data-escrow-report05mar07.htm ICANN's gTLD Registry Data Escrow Requirements, icann.org]</ref>

Line 9:

Line 15:

In November 2000, ICANN selected seven new gTLDs as part of a proof-of-concept round to expand the Internet name space. Registry Agreements for all 7 of these TLDs contained language based on the draft for the 2001 .com agreement with Verisign. These agreements were entered into between 2001 and 2002, beginning with [[.biz]] and [[.info]] in May 2001.

[[Iron Mountain]] was selected in 2001 to serve as ICANN's preferred provider for registry data escrow.<ref>[http://www.ironmountain.com/Services/Technology-Escrow-Services/Domain-Name-Registry-Data-Escrow.aspx Domain Name Registry Data Escrow, icann.org]</ref>

There are currently 4 active versions of the Registry Escrow Agreement. Most gTLDs use Version 1, which is based off of the 2001 .com agreement; Version 2 is used by [[.travel]]; Version 3 by the [[.aero]], [[.coop]], and [[.museum]] [[sTLD|Sponsored TLDs]]; and Version 4 by [[.name]] and [[.pro]].

Several of the original [[ccTLD]] Sponsorship Agreements and [[MoU]]s also contained provisions for registry escrow. In 2004, however, ICANN moved away from the Sponsorship Agreement and MOU formats, opting for a lightweight Accountability Format, which does not contain detailed provisions for registry escrow, though it does encourage ccTLD managers to operate in a manner complaint to current [[IETF]] standards.<ref>[http://archive.icann.org/en/tlds/data-escrow-report05mar07.htm#Historical ICANN's gTLD Registry Data Escrow Requirements, icann.org]</ref>

~~===Registry Data Escrow Agreement===~~

==Registrar Data Escrow==

@@ Line 1: / Line 1: @@
+{{Glossary|
+|note   = This article is neutral, but is [[Sponsorship|sponsored]] by [[Iron Mountain]].<br/>Iron Mountain is an information & intellectual property<br/>management company and data escrow provicer.<br/>You can read more about their services [http://www.ironmountain.com/ here].
+|logo     = IRON Mountain-Logo.png
+|silversponsor = ICANNWiki [[Sponsorship|Silver Sponsor]]
+}}
 '''Data Escrow''' is the act of storing data with a neutral third party<ref>[http://www.guard-it.com/faqs.html Guard-It.com FAQs]</ref> in case of registry or registrar failure, accreditation termination, or accreditation relapse without renewal. [[ICANN]] requires all registrars and gTLD registries to contract with a data escrow provider in order to safeguard registrants.<ref>[http://www.icann.org/en/news/announcements/announcement-2-09nov07-en.htm Implementation of Registrar Data Escrow Program, icann.org]</ref><ref>[http://archive.icann.org/en/tlds/data-escrow-report05mar07.htm ICANN's gTLD Registry Data Escrow Requirements, icann.org]</ref>
@@ Line 9: / Line 15: @@
 In November 2000, ICANN selected seven new gTLDs as part of a proof-of-concept round to expand the Internet name space. Registry Agreements for all 7 of these TLDs contained language based on the draft for the 2001 .com agreement with Verisign. These agreements were entered into between 2001 and 2002, beginning with [[.biz]] and [[.info]] in May 2001.
+[[Iron Mountain]] was selected in 2001 to serve as ICANN's preferred provider for registry data escrow.<ref>[http://www.ironmountain.com/Services/Technology-Escrow-Services/Domain-Name-Registry-Data-Escrow.aspx Domain Name Registry Data Escrow, icann.org]</ref>
 There are currently 4 active versions of the Registry Escrow Agreement. Most gTLDs use Version 1, which is based off of the 2001 .com agreement; Version 2 is used by [[.travel]]; Version 3 by the [[.aero]], [[.coop]], and [[.museum]] [[sTLD|Sponsored TLDs]]; and Version 4 by [[.name]] and [[.pro]].
 Several of the original [[ccTLD]] Sponsorship Agreements and [[MoU]]s also contained provisions for registry escrow. In 2004, however, ICANN moved away from the Sponsorship Agreement and MOU formats, opting for a lightweight Accountability Format, which does not contain detailed provisions for registry escrow, though it does encourage ccTLD managers to operate in a manner complaint to current [[IETF]] standards.<ref>[http://archive.icann.org/en/tlds/data-escrow-report05mar07.htm#Historical ICANN's gTLD Registry Data Escrow Requirements, icann.org]</ref>
-===Registry Data Escrow Agreement===
 ==Registrar Data Escrow==