Line 1: |
Line 1: |
− | {{Glossary|
| + | '''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] or [https://www.escrowtech.com EscrowTech International, Inc.]</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> Both registry and registry escrows follow the same system: a weekly full deposit on Sundays, and a partial deposit on all other days containing all new data since the last full deposit.<ref>[http://www.icann.org/en/resources/registrars/data-escrow/registrar-escrow-08nov01-en.htm Registrar Data Escrow, icann.org]</ref><ref>[http://www.cloudregistry.net/agb/#text/p267 New gTLD Applicant Guidebook]</ref> |
− | |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 provider.<br/>You can read more about their services [http://www.ironmountain.com/ here].
| |
− | |logo = IRON Mountain-Logo.png
| |
− | |link = http://icannwiki.com/index.php/Iron_Mountain
| |
− | |goldsponsor = ICANNWiki [[Sponsorship|Gold 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] or [https://www.escrowtech.com EscrowTech International, Inc.]</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> Both registry and registry escrows follow the same system: a weekly full deposit on sundays, and a partial deposit on all other days containing all new data since the last full deposit.<ref>[http://www.icann.org/en/resources/registrars/data-escrow/registrar-escrow-08nov01-en.htm Registrar Data Escrow, icann.org]</ref><ref>[http://www.cloudregistry.net/agb/#text/p267 New gTLD Applicant Guidebook]</ref> | |
| | | |
| ==Registry Data Escrow== | | ==Registry Data Escrow== |
Line 15: |
Line 8: |
| The original Registry Agreement, which lasted from 1999-2001, between ICANN and [[Network Solutions]] (and later [[Verisign]]) contained provisions for registry data escrow for the [[.com]], [[.net]], and [[.org]] [[gTLD]]s. In May 2001, ICANN entered into a new Registry Agreement with Verisign for .com, which included expanded escrow provisions. At that time they also entered into separate agreements for [[.org]] and [[.net]]. | | The original Registry Agreement, which lasted from 1999-2001, between ICANN and [[Network Solutions]] (and later [[Verisign]]) contained provisions for registry data escrow for the [[.com]], [[.net]], and [[.org]] [[gTLD]]s. In May 2001, ICANN entered into a new Registry Agreement with Verisign for .com, which included expanded escrow provisions. At that time they also entered into separate agreements for [[.org]] and [[.net]]. |
| | | |
− | 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. | + | In November 2000, ICANN selected seven new gTLDs as part of a proof-of-concept round to expand the Internet namespace. 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> | | [[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> |
Line 21: |
Line 14: |
| 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]]. | | 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> | + | 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 compliant 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> |
| | | |
| ==Registrar Data Escrow== | | ==Registrar Data Escrow== |