draft-ietf-regext-data-escrow-02.txt		draft-ietf-regext-data-escrow-03.txt
	Network Working Group G. Lozano		Network Working Group G. Lozano
	Internet-Draft ICANN		Internet-Draft ICANN
	Intended status: Standards Track Nov 25, 2019		Intended status: Standards Track Dec 16, 2019
	Expires: May 28, 2020		Expires: June 18, 2020
	Registry Data Escrow Specification		Registry Data Escrow Specification
	draft-ietf-regext-data-escrow-02		draft-ietf-regext-data-escrow-03
	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 May 28, 2020.		This Internet-Draft will expire on June 18, 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 42 ¶		skipping to change at page 2, line 42 ¶
	13.5. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 18		13.5. Changes from 04 to 05 . . . . . . . . . . . . . . . . . 18
	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
	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 . . . . . . . . . . . . . . . . . . . . . . . . 20
	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
	skipping to change at page 10, line 22 ¶		skipping to change at page 10, line 22 ¶
	This section of the deposit SHOULD NOT be present in Full Deposits.		This section of the deposit SHOULD NOT be present in Full Deposits.
	When rebuilding a registry it SHOULD be ignored if present in a Full		When rebuilding a registry it SHOULD be ignored if present in a Full
	Deposit.		Deposit.
	The specification for each object to be escrowed MUST declare the		The specification for each object to be escrowed MUST declare the
	identifier to be used to reference the object to be deleted.		identifier to be used to reference the object to be deleted.
	5.5. Child <contents> element		5.5. Child <contents> element
	This element of the deposit contains the objects in the deposit. It		This element of the deposit contains the objects in the deposit. It
	MUST be present in all type of deposits. It contains the data for		SHOULD be present in all type of deposits. It contains the data for
	the objects to be escrowed. The actual objects have to be specified		the objects to be escrowed. The actual objects have to be specified
	individually.		individually.
	In the case of Incremental or Differential Deposits, the objects		In the case of Incremental or Differential Deposits, the objects
	indicate whether the object was added or modified after the base		indicate whether the object was added or modified after the base
	previous deposit. In order to distinguish between one and the other,		previous deposit. In order to distinguish between one and the other,
	it will be sufficient to check existence of the referenced object in		it will be sufficient to check existence of the referenced object in
	the previous deposit.		the previous deposit.
	When applying Incremental or Differential Deposits (when rebuilding		When applying Incremental or Differential Deposits (when rebuilding
	skipping to change at page 12, line 7 ¶		skipping to change at page 12, line 7 ¶
	<!-- Root element -->		<!-- Root element -->
	<element name="deposit" type="rde:escrowDepositType"/>		<element name="deposit" type="rde:escrowDepositType"/>
	<!-- RDE types -->		<!-- RDE types -->
	<complexType name="escrowDepositType">		<complexType name="escrowDepositType">
	<sequence>		<sequence>
	<element name="watermark" type="dateTime"/>		<element name="watermark" type="dateTime"/>
	<element name="rdeMenu" type="rde:rdeMenuType"/>		<element name="rdeMenu" type="rde:rdeMenuType"/>
	<element name="deletes" type="rde:deletesType" minOccurs="0"/>		<element name="deletes" type="rde:deletesType" minOccurs="0"/>
	<element name="contents" type="rde:contentsType"/>		<element name="contents" type="rde:contentsType" minOccurs="0"/>
	</sequence>		</sequence>
	<attribute name="type" type="rde:depositTypeType" use="required"/>		<attribute name="type" type="rde:depositTypeType" use="required"/>
	<attribute name="id" type="rde:depositIdType" use="required"/>		<attribute name="id" type="rde:depositIdType" use="required"/>
	<attribute name="prevId" type="rde:depositIdType"/>		<attribute name="prevId" type="rde:depositIdType"/>
	<attribute name="resend" type="unsignedShort" default="0"/>		<attribute name="resend" type="unsignedShort" default="0"/>
	</complexType>		</complexType>
	<!-- Menu type -->		<!-- Menu type -->
	<complexType name="rdeMenuType">		<complexType name="rdeMenuType">
	<sequence>		<sequence>
	skipping to change at page 12, line 39 ¶		skipping to change at page 12, line 39 ¶
	<element name="delete" type="rde:deleteType" abstract="true" />		<element name="delete" type="rde:deleteType" abstract="true" />
	<complexType name="deleteType">		<complexType name="deleteType">
	<complexContent>		<complexContent>
	<restriction base="anyType"/>		<restriction base="anyType"/>
	</complexContent>		</complexContent>
	</complexType>		</complexType>
	<!-- Contents Type -->		<!-- Contents Type -->
	<complexType name="contentsType">		<complexType name="contentsType">
	<sequence maxOccurs="unbounded">		<sequence minOccurs="0" maxOccurs="unbounded">
	<element ref="rde:content"/>		<element ref="rde:content"/>
	</sequence>		</sequence>
	</complexType>		</complexType>
	<element name="content" type="rde:contentType" abstract="true" />		<element name="content" type="rde:contentType" abstract="true" />
	<complexType name="contentType">		<complexType name="contentType">
	<complexContent>		<complexContent>
	<restriction base="anyType"/>		<restriction base="anyType"/>
	</complexContent>		</complexContent>
	</complexType>		</complexType>
	skipping to change at page 17, line 51 ¶		skipping to change at page 17, line 51 ¶
	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
	protocol.		protocol.
	5. Moved <eppParams> element to be child of <contents>		5. Moved <eppParams> element to be child of <contents>.
	6. Text improvements in the Introduction, Terminology, and Problem		6. Text improvements in the Introduction, Terminology, and Problem
	Scope per Jay's suggestion.		Scope per Jay's suggestion.
	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.
	13.3. Changes from 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>
	skipping to change at page 18, line 42 ¶		skipping to change at page 18, line 43 ¶
	13.4. Changes from 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.
	13.5. Changes from 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.
	13.6. Changes from 05 to 06		13.6. Changes from 05 to 06
	1. Fix resend definition.		1. Fix resend definition.
	13.7. Changes from 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.
	13.8. Changes from 07 to 08		13.8. Changes from 07 to 08
	1. Ping update		1. Ping update.
	13.9. Changes from 08 to 09		13.9. Changes from 08 to 09
	1. Ping update.		1. Ping update.
	13.10. Changes from 09 to 10		13.10. Changes from 09 to 10
	1. Implementation Status section was added		1. Implementation Status section was added.
	13.11. Changes from 10 to 11		13.11. Changes from 10 to 11
	1. Ping update.		1. Ping update.
	13.12. Changes from 11 to REGEXT 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.13. Changes from version REGEXT 00 to REGEXT 01		13.13. Changes from version REGEXT 00 to REGEXT 01
	1. Privacy consideration section was added		1. Privacy consideration section was added.
	13.14. Changes from version REGEXT 01 to REGEXT 02		13.14. Changes from version REGEXT 01 to REGEXT 02
	1. Updated the Security Considerations section to make the language		1. Updated the Security Considerations section to make the language
	normative		normative.
	2. Updated the rde XML schema to remove the dependency with the		2. Updated the rde XML schema to remove the dependency with the
	eppcom namespace reference		eppcom namespace reference.
	3. Editorial updates		3. Editorial updates.
	4. Remove the reference to RFC 5730		4. Remove the reference to RFC 5730.
	5. Added complete examples of deposits		5. Added complete examples of deposits.
			13.15. Changes from version REGEXT 02 to REGEXT 03
			1. The <contents> section changed from MUST to SHOULD, in order to
			accommodate an Incremental or Differential Deposit that only
			includes deletes.
			2. Editorial updates.
	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>.
End of changes. 20 change blocks.
	20 lines changed or deleted		30 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/