draft-ietf-regext-data-escrow-00.txt   draft-ietf-regext-data-escrow-01.txt 
Network Working Group G. Lozano Network Working Group G. Lozano
Internet-Draft ICANN Internet-Draft ICANN
Intended status: Standards Track Jun 18, 2019 Intended status: Standards Track Aug 26, 2019
Expires: December 20, 2019 Expires: February 27, 2020
Registry Data Escrow Specification Registry Data Escrow Specification
draft-ietf-regext-data-escrow-00 draft-ietf-regext-data-escrow-01
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 December 20, 2019. This Internet-Draft will expire on February 27, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
skipping to change at page 2, line 25 skipping to change at page 2, line 25
5.3. Child <rdeMenu> element . . . . . . . . . . . . . . . . . 7 5.3. Child <rdeMenu> element . . . . . . . . . . . . . . . . . 7
5.4. Child <deletes> element . . . . . . . . . . . . . . . . . 8 5.4. Child <deletes> element . . . . . . . . . . . . . . . . . 8
5.5. Child <contents> element . . . . . . . . . . . . . . . . 8 5.5. Child <contents> element . . . . . . . . . . . . . . . . 8
6. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 9 6. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 9
6.1. RDE Schema . . . . . . . . . . . . . . . . . . . . . . . 9 6.1. RDE Schema . . . . . . . . . . . . . . . . . . . . . . . 9
7. Internationalization Considerations . . . . . . . . . . . . . 12 7. Internationalization Considerations . . . . . . . . . . . . . 12
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
9. Implementation Status . . . . . . . . . . . . . . . . . . . . 13 9. Implementation Status . . . . . . . . . . . . . . . . . . . . 13
9.1. Implementation in the gTLD space . . . . . . . . . . . . 13 9.1. Implementation in the gTLD space . . . . . . . . . . . . 13
10. Security Considerations . . . . . . . . . . . . . . . . . . . 14 10. Security Considerations . . . . . . . . . . . . . . . . . . . 14
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15 11. Privacy Considerations . . . . . . . . . . . . . . . . . . . 15
12. Change History . . . . . . . . . . . . . . . . . . . . . . . 15 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15
12.1. Changes from version 00 to 01 . . . . . . . . . . . . . 15 13. Change History . . . . . . . . . . . . . . . . . . . . . . . 15
12.2. Changes from version 01 to 02 . . . . . . . . . . . . . 16 13.1. Changes from 00 to 01 . . . . . . . . . . . . . . . . . 15
12.3. Changes from version 02 to 03 . . . . . . . . . . . . . 16 13.2. Changes from 01 to 02 . . . . . . . . . . . . . . . . . 16
12.4. Changes from version 03 to 04 . . . . . . . . . . . . . 17 13.3. Changes from 02 to 03 . . . . . . . . . . . . . . . . . 17
12.5. Changes from version 04 to 05 . . . . . . . . . . . . . 17 13.4. Changes from 03 to 04 . . . . . . . . . . . . . . . . . 17
12.6. Changes from version 05 to 06 . . . . . . . . . . . . . 17 13.5. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 17
12.7. Changes from version 06 to 07 . . . . . . . . . . . . . 17 13.6. Changes from 05 to 06 . . . . . . . . . . . . . . . . . 17
12.8. Changes from version 07 to 08 . . . . . . . . . . . . . 17 13.7. Changes from 06 to 07 . . . . . . . . . . . . . . . . . 17
12.9. Changes from version 08 to 09 . . . . . . . . . . . . . 17 13.8. Changes from 07 to 08 . . . . . . . . . . . . . . . . . 17
12.10. Changes from version 09 to 10 . . . . . . . . . . . . . 17 13.9. Changes from 08 to 09 . . . . . . . . . . . . . . . . . 18
12.11. Changes from version 10 to 11 . . . . . . . . . . . . . 18 13.10. Changes from 09 to 10 . . . . . . . . . . . . . . . . . 18
12.12. Changes from version 11 to 00 . . . . . . . . . . . . . 18 13.11. Changes from 10 to 11 . . . . . . . . . . . . . . . . . 18
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 13.12. Changes from 11 to REGEXT 00 . . . . . . . . . . . . . . 18
13.1. Normative References . . . . . . . . . . . . . . . . . . 18 13.13. Changes from version REGEXT 00 to REGEXT 01 . . . . . . 18
13.2. Informative References . . . . . . . . . . . . . . . . . 18 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 18 14.1. Normative References . . . . . . . . . . . . . . . . . . 18
14.2. Informative References . . . . . . . . . . . . . . . . . 18
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
Registry Data Escrow is the process by which an Registry periodically Registry Data Escrow is the process by which an 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 can not function and is unable or operations if the registry can not function and is unable or
unwilling to facilitate an orderly transfer of service. For example, unwilling to facilitate an orderly transfer of service. For example,
for a domain name registry or registrar the data to be deposited for a domain name registry or registrar the data to be deposited
would include all the objects related to registered domain names, would include all the objects related to registered domain names,
skipping to change at page 15, line 5 skipping to change at page 15, line 5
authenticate the identity of the Escrow Agent before submitting any authenticate the identity of the Escrow Agent before submitting any
data. data.
Additionally, the Registry and the Escrow Agent should use integrity Additionally, the Registry and the Escrow Agent should use integrity
checking mechanisms to ensure the data transmitted is what the source checking mechanisms to ensure the data transmitted is what the source
intended. It is recommended that specifications defining format and intended. It is recommended that specifications defining format and
semantics for particular business models define an algorithm that semantics for particular business models define an algorithm that
Escrow Agents and Third-Party Beneficiaries could use to validate the Escrow Agents and Third-Party Beneficiaries could use to validate the
contents of the data escrow deposit. 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 Special suggestions that have been incorporated into this document
were provided by James Gould, Edward Lewis, Jaap Akkerhuis, Lawrence were provided by James Gould, Edward Lewis, Jaap Akkerhuis, Lawrence
Conroy, Marc Groeneweg, Michael Young, Chris Wright, Patrick Mevzek, Conroy, Marc Groeneweg, Michael Young, Chris Wright, Patrick Mevzek,
Stephen Morris, Scott Hollenbeck, Stephane Bortzmeyer, Warren Kumari, Stephen Morris, Scott Hollenbeck, Stephane Bortzmeyer, Warren Kumari,
Paul Hoffman, Vika Mpisane, Bernie Hoeneisen, Jim Galvin, Andrew Paul Hoffman, Vika Mpisane, Bernie Hoeneisen, Jim Galvin, Andrew
Sullivan, Hiro Hotta, Christopher Browne, Daniel Kalchev, David Sullivan, Hiro Hotta, Christopher Browne, Daniel Kalchev, David
Conrad, James Mitchell, Francisco Obispo, Bhadresh Modi and Alexander Conrad, James Mitchell, Francisco Obispo, Bhadresh Modi and Alexander
Mayrhofer. Mayrhofer.
Shoji Noguchi and Francisco Arias participated as co-authors until Shoji Noguchi and Francisco Arias participated as co-authors until
version 07 providing invaluable support for this document. 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 <domain> element 1. Included DNSSEC elements as part of the basic <domain> element
as defined in RFC 5910. as defined in RFC 5910.
2. Included RGP elements as part of the basic <domain> element as 2. Included RGP elements as part of the basic <domain> element as
defined in RFC 3915. defined in RFC 3915.
3. Added support for IDNs and IDN variants. 3. Added support for IDNs and IDN variants.
4. Eliminated the <summary> element and all its subordinate 4. Eliminated the <summary> element and all its subordinate
skipping to change at page 16, line 19 skipping to change at page 16, line 27
16. Populated the "Extension Example" section. 16. Populated the "Extension Example" section.
17. Added <deDate> element under <domain> element. 17. Added <deDate> element under <domain> element.
18. Added <icannID> element under <registrar> element. 18. Added <icannID> element under <registrar> element.
19. Added <eppParams> element under root element. 19. Added <eppParams> element under root element.
20. Fixed some typographical errors and omissions. 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" 1. Added definition for "canonical" in the "IDN variants Handling"
section. section.
2. Clarified that "blocked" and "reserved" IDN variants are 2. Clarified that "blocked" and "reserved" IDN variants are
optional. optional.
3. Made <rdeRegistrar:authInfo> optional. 3. Made <rdeRegistrar:authInfo> optional.
4. Introduced substitutionGroup as the mechanism for extending the 4. Introduced substitutionGroup as the mechanism for extending the
skipping to change at page 16, line 47 skipping to change at page 17, line 7
7. Removed <trDate> from <rdeDomain> and added <trnData> instead, 7. Removed <trDate> from <rdeDomain> and added <trnData> instead,
which include all the data from the last (pending/processed) which include all the data from the last (pending/processed)
transfer request transfer request
8. Removed <trDate> from <rdeContact> and added <trnData> instead, 8. Removed <trDate> from <rdeContact> and added <trnData> instead,
which include all the data from the last (pending/processed) which include all the data from the last (pending/processed)
transfer request transfer request
9. Fixed some typographical errors and omissions. 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. 1. Separated domain name objects from protocol.
2. Moved <extension> elements to be child of <deletes> and 2. Moved <extension> elements to be child of <deletes> and
<contents>, additionally removed <extension> element from <contents>, additionally removed <extension> element from
<rdeDomain>,<rdeHost>, <rdeContact>,<rdeRegistrar> and <rdeIDN> <rdeDomain>,<rdeHost>, <rdeContact>,<rdeRegistrar> and <rdeIDN>
elements. elements.
3. Modified the definition of <rde:id> and <rde:prevId>. 3. Modified the definition of <rde:id> and <rde:prevId>.
4. Added <rdeMenu> element under <deposit> element. 4. Added <rdeMenu> element under <deposit> element.
5. Fixed some typographical errors and omissions. 5. Fixed some typographical errors and omissions.
12.4. Changes from version 03 to 04 13.4. Changes from 03 to 04
1. Removed <eppParams> objects. 1. Removed <eppParams> objects.
2. Populated the "Extension Guidelines" section. 2. Populated the "Extension Guidelines" section.
3. Fixed some typographical errors and omissions. 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 1. Fixes to the XSD
2. Extension Guidelines moved to dnrd-mappings draft 2. Extension Guidelines moved to dnrd-mappings draft
3. Fixed some typographical errors and omissions. 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. 1. Fix resend definition.
12.7. Changes from version 06 to 07 13.7. Changes from 06 to 07
1. Editorial updates. 1. Editorial updates.
2. schemaLocation removed from RDE Schema. 2. schemaLocation removed from RDE Schema.
12.8. Changes from version 07 to 08 13.8. Changes from 07 to 08
1. Ping update 1. Ping update
12.9. Changes from version 08 to 09 13.9. Changes from 08 to 09
1. Ping update. 1. Ping update.
12.10. Changes from version 09 to 10 13.10. Changes from 09 to 10
1. Implementation Status section was added 1. Implementation Status section was added
12.11. Changes from version 10 to 11 13.11. Changes from 10 to 11
1. Ping update. 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. 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 [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>.
13.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>.
[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,
<https://www.rfc-editor.org/info/rfc5730>. <https://www.rfc-editor.org/info/rfc5730>.
[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
 End of changes. 21 change blocks. 
39 lines changed or deleted 54 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/