draft-ietf-regext-data-escrow-03.txt   draft-ietf-regext-data-escrow-04.txt 
Network Working Group G. Lozano Network Working Group G. Lozano
Internet-Draft ICANN Internet-Draft ICANN
Intended status: Standards Track Dec 16, 2019 Intended status: Standards Track Jan 08, 2020
Expires: June 18, 2020 Expires: July 11, 2020
Registry Data Escrow Specification Registry Data Escrow Specification
draft-ietf-regext-data-escrow-03 draft-ietf-regext-data-escrow-04
Abstract Abstract
This document specifies the format and contents of data escrow This document specifies the format and contents of data escrow
deposits targeted primarily for domain name registries. However, the deposits targeted primarily for domain name registries. However, the
specification was designed to be independent of the underlying specification was designed to be independent of the underlying
objects that are being escrowed, therefore it could be used for objects that are being escrowed, therefore it could be used for
purposes other than domain name registries. purposes other than domain name registries.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." 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 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. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Problem Scope . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Problem Scope . . . . . . . . . . . . . . . . . . . . . . . . 4
4. General Conventions . . . . . . . . . . . . . . . . . . . . . 5 4. General Conventions . . . . . . . . . . . . . . . . . . . . . 6
4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 6 4.1. Date and Time . . . . . . . . . . . . . . . . . . . . . . 6
5. Protocol Description . . . . . . . . . . . . . . . . . . . . 6 5. Protocol Description . . . . . . . . . . . . . . . . . . . . 6
5.1. Root element <deposit> . . . . . . . . . . . . . . . . . 6 5.1. Root element <deposit> . . . . . . . . . . . . . . . . . 6
5.2. Child <watermark> element . . . . . . . . . . . . . . . . 9 5.2. Child <watermark> element . . . . . . . . . . . . . . . . 9
5.3. Child <rdeMenu> element . . . . . . . . . . . . . . . . . 9 5.3. Child <rdeMenu> element . . . . . . . . . . . . . . . . . 9
5.4. Child <deletes> element . . . . . . . . . . . . . . . . . 10 5.4. Child <deletes> element . . . . . . . . . . . . . . . . . 10
5.5. Child <contents> element . . . . . . . . . . . . . . . . 10 5.5. Child <contents> element . . . . . . . . . . . . . . . . 10
6. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 10 6. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 10
6.1. RDE Schema . . . . . . . . . . . . . . . . . . . . . . . 10 6.1. RDE Schema . . . . . . . . . . . . . . . . . . . . . . . 10
7. Internationalization Considerations . . . . . . . . . . . . . 13 7. Internationalization Considerations . . . . . . . . . . . . . 13
skipping to change at page 2, line 43 skipping to change at page 2, line 43
13.6. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 19 13.6. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 19
13.7. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 19 13.7. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 19
13.8. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 19 13.8. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 19
13.9. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 19 13.9. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 19
13.10. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 19 13.10. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 19
13.11. Changes from 10 to 11 . . . . . . . . . . . . . . . . . 19 13.11. Changes from 10 to 11 . . . . . . . . . . . . . . . . . 19
13.12. Changes from 11 to REGEXT 00 . . . . . . . . . . . . . . 19 13.12. Changes from 11 to REGEXT 00 . . . . . . . . . . . . . . 19
13.13. Changes from version REGEXT 00 to REGEXT 01 . . . . . . 19 13.13. Changes from version REGEXT 00 to REGEXT 01 . . . . . . 19
13.14. Changes from version REGEXT 01 to REGEXT 02 . . . . . . 19 13.14. Changes from version REGEXT 01 to REGEXT 02 . . . . . . 19
13.15. Changes from version REGEXT 02 to REGEXT 03 . . . . . . 20 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. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
14.1. Normative References . . . . . . . . . . . . . . . . . . 20 14.1. Normative References . . . . . . . . . . . . . . . . . . 20
14.2. Informative References . . . . . . . . . . . . . . . . . 20 14.2. Informative References . . . . . . . . . . . . . . . . . 20
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 20 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 21
1. Introduction 1. Introduction
Registry Data Escrow is the process by which a registry periodically Registry Data Escrow is the process by which a registry periodically
submits data deposits to a third-party called an escrow agent. These submits data deposits to a third-party called an escrow agent. These
deposits comprise the minimum data needed by a third-party to resume deposits comprise the minimum data needed by a third-party to resume
operations if the registry cannot function and is unable or unwilling operations if the registry cannot function and is unable or unwilling
to facilitate an orderly transfer of service. For example, for a to facilitate an orderly transfer of service. For example, for a
domain name registry or registrar, the data to be deposited would domain name registry or registrar, the data to be deposited would
include all the objects related to registered domain names, e.g., include all the objects related to registered domain names, e.g.,
skipping to change at page 20, line 13 skipping to change at page 20, line 13
5. Added complete examples of deposits. 5. Added complete examples of deposits.
13.15. Changes from version REGEXT 02 to REGEXT 03 13.15. Changes from version REGEXT 02 to REGEXT 03
1. The <contents> section changed from MUST to SHOULD, in order to 1. The <contents> section changed from MUST to SHOULD, in order to
accommodate an Incremental or Differential Deposit that only accommodate an Incremental or Differential Deposit that only
includes deletes. includes deletes.
2. Editorial updates. 2. Editorial updates.
13.16. Changes from version REGEXT 03 to REGEXT 04
1. Moved [RFC8499] to the Normative References section.
14. References 14. References
14.1. Normative References 14.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet:
Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002,
<https://www.rfc-editor.org/info/rfc3339>. <https://www.rfc-editor.org/info/rfc3339>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS
Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499,
January 2019, <https://www.rfc-editor.org/info/rfc8499>.
14.2. Informative References 14.2. Informative References
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", BCP 205, Code: The Implementation Status Section", BCP 205,
RFC 7942, DOI 10.17487/RFC7942, July 2016, RFC 7942, DOI 10.17487/RFC7942, July 2016,
<https://www.rfc-editor.org/info/rfc7942>. <https://www.rfc-editor.org/info/rfc7942>.
[RFC8499] Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS
Terminology", BCP 219, RFC 8499, DOI 10.17487/RFC8499,
January 2019, <https://www.rfc-editor.org/info/rfc8499>.
Author's Address Author's Address
Gustavo Lozano Gustavo Lozano
Internet Corporation for Assigned Names and Numbers Internet Corporation for Assigned Names and Numbers
12025 Waterfront Drive, Suite 300 12025 Waterfront Drive, Suite 300
Los Angeles 90292 Los Angeles 90292
United States of America United States of America
Phone: +1.310.823.9358 Phone: +1.310.823.9358
Email: gustavo.lozano@icann.org Email: gustavo.lozano@icann.org
 End of changes. 12 change blocks. 
12 lines changed or deleted 18 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/