--- 1/draft-ietf-regext-data-escrow-03.txt 2020-01-09 09:13:17.387849522 -0800 +++ 2/draft-ietf-regext-data-escrow-04.txt 2020-01-09 09:13:17.431850644 -0800 @@ -1,18 +1,18 @@ Network Working Group G. Lozano Internet-Draft ICANN -Intended status: Standards Track Dec 16, 2019 -Expires: June 18, 2020 +Intended status: Standards Track Jan 08, 2020 +Expires: July 11, 2020 Registry Data Escrow Specification - draft-ietf-regext-data-escrow-03 + draft-ietf-regext-data-escrow-04 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,43 +23,43 @@ 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 June 18, 2020. + This Internet-Draft will expire on July 11, 2020. Copyright Notice - Copyright (c) 2019 IETF Trust and the persons identified as the + Copyright (c) 2020 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 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents - 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 + 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Problem Scope . . . . . . . . . . . . . . . . . . . . . . . . 4 - 4. General Conventions . . . . . . . . . . . . . . . . . . . . . 5 + 4. General Conventions . . . . . . . . . . . . . . . . . . . . . 6 4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 6 5. Protocol Description . . . . . . . . . . . . . . . . . . . . 6 5.1. Root element . . . . . . . . . . . . . . . . . 6 5.2. Child element . . . . . . . . . . . . . . . . 9 5.3. Child element . . . . . . . . . . . . . . . . . 9 5.4. Child element . . . . . . . . . . . . . . . . . 10 5.5. Child element . . . . . . . . . . . . . . . . 10 6. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 10 6.1. RDE Schema . . . . . . . . . . . . . . . . . . . . . . . 10 7. Internationalization Considerations . . . . . . . . . . . . . 13 @@ -78,24 +78,25 @@ 13.6. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 19 13.7. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 19 13.8. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 19 13.9. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 19 13.10. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 19 13.11. Changes from 10 to 11 . . . . . . . . . . . . . . . . . 19 13.12. Changes from 11 to REGEXT 00 . . . . . . . . . . . . . . 19 13.13. Changes from version REGEXT 00 to REGEXT 01 . . . . . . 19 13.14. Changes from version REGEXT 01 to REGEXT 02 . . . . . . 19 13.15. Changes from version REGEXT 02 to REGEXT 03 . . . . . . 20 + 13.16. Changes from version REGEXT 03 to REGEXT 04 . . . . . . 20 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 14.1. Normative References . . . . . . . . . . . . . . . . . . 20 14.2. Informative References . . . . . . . . . . . . . . . . . 20 - Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 20 + Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 21 1. Introduction Registry Data Escrow is the process by which a 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 cannot 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, e.g., @@ -874,51 +875,56 @@ 5. Added complete examples of deposits. 13.15. Changes from version REGEXT 02 to REGEXT 03 1. The section changed from MUST to SHOULD, in order to accommodate an Incremental or Differential Deposit that only includes deletes. 2. Editorial updates. +13.16. Changes from version REGEXT 03 to REGEXT 04 + + 1. Moved [RFC8499] to the Normative References section. + 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, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . + [RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS + Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499, + January 2019, . + 14.2. Informative References [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running Code: The Implementation Status Section", BCP 205, RFC 7942, DOI 10.17487/RFC7942, July 2016, . - [RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS - Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499, - January 2019, . - Author's Address + Gustavo Lozano Internet Corporation for Assigned Names and Numbers 12025 Waterfront Drive, Suite 300 Los Angeles 90292 United States of America Phone: +1.310.823.9358 Email: gustavo.lozano@icann.org