presented by Cloud Registry.
NEW GTLD AGREEMENT SPECIFICATIONS SPECIFICATION 2 DATA ESCROW REQUIREMENTS Registry Operator will engage an independent entity to act as data escrow agent (“Escrow Agent”) for the provision of data escrow services related to the Registry Agreement. The following Technical Specifications set forth in Part A, and Legal Requirements set forth in Part B, will be included in any data escrow agreement between Registry Operator and the Escrow Agent, under which ICANN must be named a third-party beneficiary. In addition to the following requirements, the data escrow agreement may contain other provisions that are not contradictory or intended to subvert the required terms provided below. PART A – TECHNICAL SPECIFICATIONS 1. Deposits. There will be two types of Deposits: Full and Differential. For both types, the universe of Registry objects to be considered for data escrow are those objects necessary in order to offer all of the approved Registry Services. 1.1 “Full Deposit” will consist of data that reflects the state of the registry as of 00:00:00 UTC on each Sunday. 1.2 “Differential Deposit” means data that reflects all transactions that were not reflected in the last previous Full or Differential Deposit, as the case may be. Each Differential Deposit will contain all database transactions since the previous Deposit was completed as of 00:00:00 UTC of each day, but Sunday. Differential Deposits must include complete Escrow Records as specified below that were not included or changed since the most recent full or Differential Deposit (i.e., newly added or modified domain names). Schedule for Deposits. Registry Operator will submit a set of escrow files on a daily basis as follows: 2.1 Each Sunday, a Full Deposit must be submitted to the Escrow Agent by 23:59 UTC. 2.2 The other six days of the week, the corresponding Differential Deposit must be submitted to Escrow Agent by 23:59 UTC. Escrow Format Specification. 3.1 Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-arias-noguchi-registry-data-escrow, see [1]. The aforementioned document describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. Registry Operator will use the draft version available at the time of signing the Agreement, if not already an RFC. Once the specification is published as an RFC, Registry Operator will implement that specification, no later than 180 days after. UTF-8 character encoding will be used. 2. 3. 3.2 Extensions. If a Registry Operator offers additional Registry Services that require submission of additional data, not included above, additional “extension schemas” shall be defined in a case by case base to represent that data. These “extension schemas” will be specified as described in [1]. Data related to the “extensions schemas” will be included in the deposit file described in section 3.1. ICANN and the respective Registry shall work together to agree on such new objects’ data escrow specifications. 28