Dear Colleagues, We will not have a meeting on Tuesday, as the attached will be easier to review on your own. We won't have a meeting the following week, either, as that is ICANN62. We're planning to meet again on 3 July. I have attached several documents for your review: 1. The latest version of the 4 RRI specifications required for data escrow and quarterly reporting. 2. The PP data escrow specification, updated to support the standalone data escrow model (the previous draft proposed to allow an affiliated registrar to make its data escrow deposits through the affiliated PP provider, rather than the other way around). Please note that we are still working on documentation that will be required to support the allowance for registrar-affiliated PPs to meet their data escrow requirements as part of the registrar's data escrow deposit procedures. This will likely involve an addendum either to the registrar data escrow agreement or the pp data escrow agreement-I will share a concrete proposal on that when we have it. For PPs that follow the registrar-supported data escrow model, there are three requirements that will apply (these will be included in the data escrow agreement): * Privacy and Proxy Service customer information escrowed through Affiliate Registrar(s) data escrow deposits must include for each domain name: the PPSP identifier assigned by ICANN to the Provider, the domain name ROID, notwithstanding the requirements and format defined by the Registrar Data Escrow Specifications. The Affiliate Registrar(s) will deliver to ICANN (using the API described in https://tools.ietf.org/html/draft-icann-registrar-interfaces) a statement that includes a copy of the report generated upon creation of each Registrar data escrow Deposit that states that the Deposit has been inspected by the Registrar to be complete and accurate. The preparation and submission of this statement must be performed by the Affiliate Registrar(s) or its designee, provided that such designee may not be the Escrow Agent or any of Escrow Agent's Affiliates. * The Provider will deliver each day to ICANN (using the API described in https://tools.ietf.org/html/draft-icann-ppsp-interfaces) a statement from Provider that states that the Provider has verified that the Privacy and Proxy Services customer information submitted in Affiliate Registrar(s) data escrow deposits is complete, accurate and includes the contact information corresponding to each and all of the Provider's customers. The preparation and submission of this statement must be performed by the Provider or its designee, provided that such designee may not be the Escrow Agent or any of Escrow Agent's Affiliates. Provider will include the Deposit's <id> in its statement. The preparation and submission of this statement must be performed by the Provider or its designee, provided that such designee may not be the Escrow Agent or any of Escrow Agent's Affiliates. Provider will generate and include a Deposit's <id> in its statement. * The Provider will include the contact information corresponding to each and all of the Provider's customers through Affiliate Registrar(s) data escrow deposits, otherwise the Provider will be obligated to comply with the Data Escrow obligations in the Privacy and Proxy Service Provider Data Escrow Specifications. If you have questions or comments, please send them to the list. Thanks, and have a great weekend! Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins@icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>