--- 1/draft-ietf-regext-data-escrow-00.txt 2019-08-26 17:14:19.883689953 -0700 +++ 2/draft-ietf-regext-data-escrow-01.txt 2019-08-26 17:14:19.919690862 -0700 @@ -1,18 +1,18 @@ Network Working Group G. Lozano Internet-Draft ICANN -Intended status: Standards Track Jun 18, 2019 -Expires: December 20, 2019 +Intended status: Standards Track Aug 26, 2019 +Expires: February 27, 2020 Registry Data Escrow Specification - draft-ietf-regext-data-escrow-00 + draft-ietf-regext-data-escrow-01 Abstract This document specifies the format and contents of data escrow deposits targeted primarily for domain name registries. However, the specification was designed to be independent of the underlying objects that are being escrowed, therefore it could be used for purposes other than domain name registries. Status of This Memo @@ -23,21 +23,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on December 20, 2019. + This Internet-Draft will expire on February 27, 2020. Copyright Notice Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -60,38 +60,40 @@ 5.3. Child element . . . . . . . . . . . . . . . . . 7 5.4. Child element . . . . . . . . . . . . . . . . . 8 5.5. Child element . . . . . . . . . . . . . . . . 8 6. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 9 6.1. RDE Schema . . . . . . . . . . . . . . . . . . . . . . . 9 7. Internationalization Considerations . . . . . . . . . . . . . 12 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 9. Implementation Status . . . . . . . . . . . . . . . . . . . . 13 9.1. Implementation in the gTLD space . . . . . . . . . . . . 13 10. Security Considerations . . . . . . . . . . . . . . . . . . . 14 - 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15 - 12. Change History . . . . . . . . . . . . . . . . . . . . . . . 15 - 12.1. Changes from version 00 to 01 . . . . . . . . . . . . . 15 - 12.2. Changes from version 01 to 02 . . . . . . . . . . . . . 16 - 12.3. Changes from version 02 to 03 . . . . . . . . . . . . . 16 - 12.4. Changes from version 03 to 04 . . . . . . . . . . . . . 17 - 12.5. Changes from version 04 to 05 . . . . . . . . . . . . . 17 - 12.6. Changes from version 05 to 06 . . . . . . . . . . . . . 17 - 12.7. Changes from version 06 to 07 . . . . . . . . . . . . . 17 - 12.8. Changes from version 07 to 08 . . . . . . . . . . . . . 17 - 12.9. Changes from version 08 to 09 . . . . . . . . . . . . . 17 - 12.10. Changes from version 09 to 10 . . . . . . . . . . . . . 17 - 12.11. Changes from version 10 to 11 . . . . . . . . . . . . . 18 - 12.12. Changes from version 11 to 00 . . . . . . . . . . . . . 18 - 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 - 13.1. Normative References . . . . . . . . . . . . . . . . . . 18 - 13.2. Informative References . . . . . . . . . . . . . . . . . 18 - Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 18 + 11. Privacy Considerations . . . . . . . . . . . . . . . . . . . 15 + 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15 + 13. Change History . . . . . . . . . . . . . . . . . . . . . . . 15 + 13.1. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 15 + 13.2. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 16 + 13.3. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 17 + 13.4. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 17 + 13.5. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 17 + 13.6. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 17 + 13.7. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 17 + 13.8. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 17 + 13.9. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 18 + 13.10. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 18 + 13.11. Changes from 10 to 11 . . . . . . . . . . . . . . . . . 18 + 13.12. Changes from 11 to REGEXT 00 . . . . . . . . . . . . . . 18 + 13.13. Changes from version REGEXT 00 to REGEXT 01 . . . . . . 18 + 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 + 14.1. Normative References . . . . . . . . . . . . . . . . . . 18 + 14.2. Informative References . . . . . . . . . . . . . . . . . 18 + Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 19 1. Introduction Registry Data Escrow is the process by which an Registry periodically submits data deposits to a third party called an Escrow Agent. These deposits comprise the minimum data needed by a third party to resume operations if the registry can not function and is unable or unwilling to facilitate an orderly transfer of service. For example, for a domain name registry or registrar the data to be deposited would include all the objects related to registered domain names, @@ -655,37 +657,46 @@ authenticate the identity of the Escrow Agent before submitting any data. Additionally, the Registry and the Escrow Agent should use integrity checking mechanisms to ensure the data transmitted is what the source intended. It is recommended that specifications defining format and semantics for particular business models define an algorithm that Escrow Agents and Third-Party Beneficiaries could use to validate the contents of the data escrow deposit. -11. Acknowledgments +11. Privacy Considerations + + This specification defines a format that may be used to escrow + personal data. The process of data escrow is governed by a legal + document agreed by the parties, and such legal document must regulate + the particularities regarding the protection of personal data. + +12. Acknowledgments Special suggestions that have been incorporated into this document were provided by James Gould, Edward Lewis, Jaap Akkerhuis, Lawrence Conroy, Marc Groeneweg, Michael Young, Chris Wright, Patrick Mevzek, Stephen Morris, Scott Hollenbeck, Stephane Bortzmeyer, Warren Kumari, Paul Hoffman, Vika Mpisane, Bernie Hoeneisen, Jim Galvin, Andrew Sullivan, Hiro Hotta, Christopher Browne, Daniel Kalchev, David Conrad, James Mitchell, Francisco Obispo, Bhadresh Modi and Alexander Mayrhofer. Shoji Noguchi and Francisco Arias participated as co-authors until version 07 providing invaluable support for this document. -12. Change History +13. Change History -12.1. Changes from version 00 to 01 + [[RFC Editor: Please remove this section.]] + +13.1. Changes from 00 to 01 1. Included DNSSEC elements as part of the basic element as defined in RFC 5910. 2. Included RGP elements as part of the basic element as defined in RFC 3915. 3. Added support for IDNs and IDN variants. 4. Eliminated the element and all its subordinate @@ -717,21 +728,21 @@ 16. Populated the "Extension Example" section. 17. Added element under element. 18. Added element under element. 19. Added element under root element. 20. Fixed some typographical errors and omissions. -12.2. Changes from version 01 to 02 +13.2. Changes from 01 to 02 1. Added definition for "canonical" in the "IDN variants Handling" section. 2. Clarified that "blocked" and "reserved" IDN variants are optional. 3. Made optional. 4. Introduced substitutionGroup as the mechanism for extending the @@ -745,95 +756,99 @@ 7. Removed from and added instead, which include all the data from the last (pending/processed) transfer request 8. Removed from and added instead, which include all the data from the last (pending/processed) transfer request 9. Fixed some typographical errors and omissions. -12.3. Changes from version 02 to 03 +13.3. Changes from 02 to 03 1. Separated domain name objects from protocol. 2. Moved elements to be child of and , additionally removed element from ,, , and elements. 3. Modified the definition of and . 4. Added element under element. 5. Fixed some typographical errors and omissions. -12.4. Changes from version 03 to 04 +13.4. Changes from 03 to 04 1. Removed objects. 2. Populated the "Extension Guidelines" section. 3. Fixed some typographical errors and omissions. -12.5. Changes from version 04 to 05 +13.5. Changes from 04 to 05 1. Fixes to the XSD 2. Extension Guidelines moved to dnrd-mappings draft 3. Fixed some typographical errors and omissions. -12.6. Changes from version 05 to 06 +13.6. Changes from 05 to 06 1. Fix resend definition. -12.7. Changes from version 06 to 07 +13.7. Changes from 06 to 07 1. Editorial updates. 2. schemaLocation removed from RDE Schema. -12.8. Changes from version 07 to 08 +13.8. Changes from 07 to 08 1. Ping update -12.9. Changes from version 08 to 09 +13.9. Changes from 08 to 09 1. Ping update. -12.10. Changes from version 09 to 10 +13.10. Changes from 09 to 10 1. Implementation Status section was added -12.11. Changes from version 10 to 11 +13.11. Changes from 10 to 11 1. Ping update. -12.12. Changes from version 11 to 00 +13.12. Changes from 11 to REGEXT 00 1. Internet Draft (I-D) adopted by the REGEXT WG. -13. References +13.13. Changes from version REGEXT 00 to REGEXT 01 -13.1. Normative References + 1. Privacy consideration section was added + +14. References + +14.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, . -13.2. Informative References +14.2. Informative References [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, . [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running