draft-ietf-regext-simple-registration-reporting-00.txt		draft-ietf-regext-simple-registration-reporting-01.txt
	Internet Engineering Task Force J.Y,. Yee, Ed.		Internet Engineering Task Force J.Y,. Yee, Ed.
	Internet-Draft J.G,. Galvin		Internet-Draft J.G,. Galvin
	Intended status: Informational Afilias		Intended status: Informational Afilias
	Expires: 3 December 2020 1 June 2020		Expires: 14 January 2021 13 July 2020
	Simple Registration Reporting		Simple Registration Reporting
	draft-ietf-regext-simple-registration-reporting-00		draft-ietf-regext-simple-registration-reporting-01
	Abstract		Abstract
	Domain name registries and registrars report to each other by sharing		Domain name registries and registrars report to each other by sharing
	bulk information through files. This document creates two IANA		bulk information through files. This document creates two IANA
	registries to create a standard reporting mechanism between domain		registries to create a standard reporting mechanism between domain
	name registries and registrars. The first IANA registry lists		name registries and registrars. The first IANA registry lists
	standard data elements and their syntax for inclusion in the files.		standard data elements and their syntax for inclusion in the files.
	The second IANA registry lists standard reports based on the standard		The second IANA registry lists standard reports based on the standard
	data elements. Each report is a file formatted as a CSV file. The		data elements. Each report is a file formatted as a CSV file. The
	skipping to change at page 1, line 41 ¶		skipping to change at page 1, line 41 ¶
	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 3 December 2020.		This Internet-Draft will expire on 14 January 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 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 (https://trustee.ietf.org/		Provisions Relating to IETF Documents (https://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	and restrictions with respect to this document. Code Components		and restrictions with respect to this document. Code Components
	extracted from this document must include Simplified BSD License text		extracted from this document must include Simplified BSD License text
	as described in Section 4.e of the Trust Legal Provisions and are		as described in Section 4.e of the Trust Legal Provisions and are
	provided without warranty as described in the Simplified BSD License.		provided without warranty as described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4		1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
	2. Data Element Specification . . . . . . . . . . . . . . . . . 4		2. Data Element Specification . . . . . . . . . . . . . . . . . 4
	2.1. General Information Fields . . . . . . . . . . . . . . . 5		2.1. General Information Fields . . . . . . . . . . . . . . . 4
	2.1.1. TLD . . . . . . . . . . . . . . . . . . . . . . . . . 5		2.1.1. TLD . . . . . . . . . . . . . . . . . . . . . . . . . 4
	2.1.2. Server_TRID . . . . . . . . . . . . . . . . . . . . . 5		2.1.2. Server_TRID . . . . . . . . . . . . . . . . . . . . . 4
	2.1.3. Domain . . . . . . . . . . . . . . . . . . . . . . . 5		2.1.3. Domain . . . . . . . . . . . . . . . . . . . . . . . 5
	2.1.4. Transaction_Type . . . . . . . . . . . . . . . . . . 5		2.1.4. Transaction_Type . . . . . . . . . . . . . . . . . . 5
	2.1.5. Ojbect_Type . . . . . . . . . . . . . . . . . . . . . 5		2.1.5. Ojbect_Type . . . . . . . . . . . . . . . . . . . . . 5
	2.1.6. DateTime . . . . . . . . . . . . . . . . . . . . . . 5		2.1.6. DateTime . . . . . . . . . . . . . . . . . . . . . . 5
	2.1.7. Term . . . . . . . . . . . . . . . . . . . . . . . . 5		2.1.7. Term . . . . . . . . . . . . . . . . . . . . . . . . 5
	2.1.8. Fee . . . . . . . . . . . . . . . . . . . . . . . . . 6		2.1.8. Fee . . . . . . . . . . . . . . . . . . . . . . . . . 5
	2.1.9. Currency . . . . . . . . . . . . . . . . . . . . . . 6		2.1.9. Currency . . . . . . . . . . . . . . . . . . . . . . 5
	2.1.10. Status . . . . . . . . . . . . . . . . . . . . . . . 6		2.1.10. Status . . . . . . . . . . . . . . . . . . . . . . . 5
	2.1.11. Registrar . . . . . . . . . . . . . . . . . . . . . . 6		2.1.11. Registrar . . . . . . . . . . . . . . . . . . . . . . 6
	2.1.12. Period . . . . . . . . . . . . . . . . . . . . . . . 6		2.1.12. Period . . . . . . . . . . . . . . . . . . . . . . . 6
	2.1.13. Description . . . . . . . . . . . . . . . . . . . . . 6		2.1.13. Description . . . . . . . . . . . . . . . . . . . . . 6
	2.2. Domain Price Fields . . . . . . . . . . . . . . . . . . . 6		2.2. Domain Price Fields . . . . . . . . . . . . . . . . . . . 6
	2.2.1. Domain_Create . . . . . . . . . . . . . . . . . . . . 6		2.2.1. Domain_Create . . . . . . . . . . . . . . . . . . . . 6
	2.2.2. Domain_Renew . . . . . . . . . . . . . . . . . . . . 6		2.2.2. Domain_Renew . . . . . . . . . . . . . . . . . . . . 6
	2.2.3. Domain_Transfer . . . . . . . . . . . . . . . . . . . 7		2.2.3. Domain_Transfer . . . . . . . . . . . . . . . . . . . 6
	2.2.4. Domain_Restore . . . . . . . . . . . . . . . . . . . 7		2.2.4. Domain_Restore . . . . . . . . . . . . . . . . . . . 6
	2.3. Timestamp Fields . . . . . . . . . . . . . . . . . . . . 7		2.3. Timestamp Fields . . . . . . . . . . . . . . . . . . . . 6
	2.3.1. Start_Date . . . . . . . . . . . . . . . . . . . . . 7		2.3.1. Start_Date . . . . . . . . . . . . . . . . . . . . . 6
	2.3.2. Deleted_Date . . . . . . . . . . . . . . . . . . . . 7		2.3.2. Deleted_Date . . . . . . . . . . . . . . . . . . . . 7
	2.3.3. RGP_Date . . . . . . . . . . . . . . . . . . . . . . 7		2.3.3. RGP_Date . . . . . . . . . . . . . . . . . . . . . . 7
	2.3.4. Purge_Date . . . . . . . . . . . . . . . . . . . . . 7		2.3.4. Purge_Date . . . . . . . . . . . . . . . . . . . . . 7
	2.3.5. Updated_Date . . . . . . . . . . . . . . . . . . . . 7		2.3.5. Updated_Date . . . . . . . . . . . . . . . . . . . . 7
	2.3.6. Create_Date . . . . . . . . . . . . . . . . . . . . . 8		2.3.6. Create_Date . . . . . . . . . . . . . . . . . . . . . 7
	2.3.7. Expiry_Date . . . . . . . . . . . . . . . . . . . . . 8		2.3.7. Expiry_Date . . . . . . . . . . . . . . . . . . . . . 7
	2.4. Registration Information Fields . . . . . . . . . . . . . 8		2.4. Registration Information Fields . . . . . . . . . . . . . 7
	2.4.1. Registrar_ID . . . . . . . . . . . . . . . . . . . . 8		2.4.1. Registrar_ID . . . . . . . . . . . . . . . . . . . . 7
	2.4.2. Server_Registrant_ID . . . . . . . . . . . . . . . . 8		2.4.2. Server_Registrant_ID . . . . . . . . . . . . . . . . 8
	2.4.3. DNSSEC . . . . . . . . . . . . . . . . . . . . . . . 8		2.4.3. DNSSEC . . . . . . . . . . . . . . . . . . . . . . . 8
	2.4.4. Server_Contact_ID . . . . . . . . . . . . . . . . . . 8		2.4.4. Server_Contact_ID . . . . . . . . . . . . . . . . . . 8
	2.4.5. Contact_Type . . . . . . . . . . . . . . . . . . . . 8		2.4.5. Contact_Type . . . . . . . . . . . . . . . . . . . . 8
	2.4.6. Contact_Name . . . . . . . . . . . . . . . . . . . . 8		2.4.6. Contact_Name . . . . . . . . . . . . . . . . . . . . 8
	2.4.7. INUSE . . . . . . . . . . . . . . . . . . . . . . . . 9		2.4.7. INUSE . . . . . . . . . . . . . . . . . . . . . . . . 8
	2.4.8. Nameserver_Host . . . . . . . . . . . . . . . . . . . 9		2.4.8. Nameserver_Host . . . . . . . . . . . . . . . . . . . 8
	2.4.9. Nameserver_IP . . . . . . . . . . . . . . . . . . . . 9		2.4.9. Nameserver_IP . . . . . . . . . . . . . . . . . . . . 8
	2.4.10. Client_Contact_ID . . . . . . . . . . . . . . . . . . 9		2.4.10. Client_Contact_ID . . . . . . . . . . . . . . . . . . 8
	3. Report Definition Specification . . . . . . . . . . . . . . . 9		3. Report Definition Specification . . . . . . . . . . . . . . . 9
	3.1. Transaction Report . . . . . . . . . . . . . . . . . . . 10		3.1. Transaction Report . . . . . . . . . . . . . . . . . . . 9
	3.2. Premium Name Report . . . . . . . . . . . . . . . . . . . 10		3.2. Premium Name Report . . . . . . . . . . . . . . . . . . . 10
	3.3. Domain RGP Report . . . . . . . . . . . . . . . . . . . . 11		3.3. Domain RGP Report . . . . . . . . . . . . . . . . . . . . 11
	3.4. Reserved Domain Report . . . . . . . . . . . . . . . . . 11		3.4. Reserved Domain Report . . . . . . . . . . . . . . . . . 11
	3.5. Domain Inventory Report . . . . . . . . . . . . . . . . . 12		3.5. Domain Inventory Report . . . . . . . . . . . . . . . . . 12
	3.6. Contact Inventory Report . . . . . . . . . . . . . . . . 12		3.6. Contact Inventory Report . . . . . . . . . . . . . . . . 12
	3.7. Host Inventory Report . . . . . . . . . . . . . . . . . . 13		3.7. Host Inventory Report . . . . . . . . . . . . . . . . . . 13
	4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13		4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
	5.1. Field Definition . . . . . . . . . . . . . . . . . . . . 13		5.1. Field Definition . . . . . . . . . . . . . . . . . . . . 13
	5.2. Report Definition . . . . . . . . . . . . . . . . . . . . 14		5.2. Report Definition . . . . . . . . . . . . . . . . . . . . 14
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 14		6. Security Considerations . . . . . . . . . . . . . . . . . . . 14
	7. Internationalization Considerations . . . . . . . . . . . . . 14		7. Internationalization Considerations . . . . . . . . . . . . . 14
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 14		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
	8.1. Normative References . . . . . . . . . . . . . . . . . . 14		8.1. Normative References . . . . . . . . . . . . . . . . . . 14
	8.2. Informative References . . . . . . . . . . . . . . . . . 15		8.2. Informative References . . . . . . . . . . . . . . . . . 15
	Appendix A. File Naming Convention . . . . . . . . . . . . . . . 15		Appendix A. File Naming Convention . . . . . . . . . . . . . . . 16
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
	1. Introduction		1. Introduction
	Currently, domain name registry operators (the producer) create and		Currently, domain name registry operators (the producer) create and
	set their own domain name registration reports for use by their		set their own domain name registration reports for use by their
	registrars (the consumer). Among the distinctions that vary by		registrars (the consumer). Among the distinctions that vary by
	producers is the syntax of the data provided, e.g., date formats, and		producers is the syntax of the data provided, e.g., date formats, and
	the format of the collection of the data provided, e.g., the report		the format of the collection of the data provided, e.g., the report
	may be a CSV file that tends to allow for straightforward importation		may be a CSV file that tends to allow for straightforward importation
	or a PDF file that can be problematic to import. In addition,		or a PDF file that can be problematic to import. In addition,
	skipping to change at page 4, line 33 ¶		skipping to change at page 4, line 33 ¶
	passed from the producer to the consumer. The primary purposes of		passed from the producer to the consumer. The primary purposes of
	the IANA registry of data elements are to ensure that each data		the IANA registry of data elements are to ensure that each data
	element is assigned a unique name and that the syntax of each data		element is assigned a unique name and that the syntax of each data
	element is specified.		element is specified.
	The name of the data element MUST be unique and this characteristic		The name of the data element MUST be unique and this characteristic
	MUST be enforced by registry. The name is used in the report		MUST be enforced by registry. The name is used in the report
	definition (in the next section) to alert the consumer as to what to		definition (in the next section) to alert the consumer as to what to
	expect in the file and how to import the data element.		expect in the file and how to import the data element.
	The field names MUST NOT contain any whitespace and MAY use US-ASCII
	underscores (_) as a separator.
	The US-ASCII comma (,) and backslash (\) are special and MUST NOT
	appear in any field name or data element value. In order to include
	either character it must be quoted as follows.
	* COMMA - to insert a comma precede it with a backslash thus (\,).
	* BACKSLASH - to insert a backslash precede it with a backslash thus
	(\\).
	The syntax of the data element MAY be whatever is appropriate for the
	information to be passed. In most cases it will be imported from
	other standard specifications where the data element is already
	defined for use in other protocols. In all cases the syntax
	restriction mentioned above MUST be respected.
	The subsections below comprise an initial list of known data elements		The subsections below comprise an initial list of known data elements
	commonly being used between producers and consumers as of the date of		commonly being used between producers and consumers as of the date of
	publication of this document. The title of the subsection is the		publication of this document. The title of the subsection is the
	field name for the data element.		field name for the data element.
	2.1. General Information Fields		2.1. General Information Fields
	2.1.1. TLD		2.1.1. TLD
	The string of the top level domain involved that SHOULD be in A-LABEL		The string of the top level domain involved that SHOULD be in A-LABEL
	format.		format as defined by RFC 5890 [RFC5890].
	2.1.2. Server_TRID		2.1.2. Server_TRID
	The transaction identifier issued by EPP Server. The format MUST		The transaction identifier issued by EPP Server. The format MUST
	conform to "type:trIDStringType" as specified in RFC 5730 [RFC5730].		conform to "type:trIDStringType" as specified in RFC 5730 [RFC5730].
	2.1.3. Domain		2.1.3. Domain
	This is the domain name in EPP RFC 5731 [RFC5731] domain object and		This is the domain name in EPP RFC 5731 [RFC5731] domain object and
	it SHOULD be in A-Label format.		it SHOULD be in A-Label format.
	skipping to change at page 8, line 22 ¶		skipping to change at page 7, line 49 ¶
	The timestamp of the domain object will expire. The date and time		The timestamp of the domain object will expire. The date and time
	format follows the "type=dateTime" specification as defined in RFC		format follows the "type=dateTime" specification as defined in RFC
	5731 [RFC5731].		5731 [RFC5731].
	2.4. Registration Information Fields		2.4. Registration Information Fields
	2.4.1. Registrar_ID		2.4.1. Registrar_ID
	The identifier assigned to the registrar. If the registrar is		The identifier assigned to the registrar. If the registrar is
	accredited under ICANN, it MUST be the registrar's IANA ID.		accredited under ICANN, it MUST be the registrar's IANA ID
	Otherwise it is a value known between the producer and the consumer.		[IANA_Registrar_IDs]. Otherwise it is a value known between the
			producer and the consumer.
	2.4.2. Server_Registrant_ID		2.4.2. Server_Registrant_ID
	The identifier assigned to the contact object that is associated as		The identifier assigned to the contact object that is associated as
	registrant of the domain name that MUST conform to "clIDType"		registrant of the domain name that MUST conform to "clIDType"
	specified in RFC 5730 [RFC5730].		specified in RFC 5730 [RFC5730].
	2.4.3. DNSSEC		2.4.3. DNSSEC
	The value MUST be either 'YES' or 'NO' to indicate whether the domain		The value MUST be either 'YES' or 'NO' to indicate whether the domain
	skipping to change at page 9, line 28 ¶		skipping to change at page 9, line 8 ¶
	MUST conform to RFC 791 [RFC0791]. The syntax of the IPv6 address		MUST conform to RFC 791 [RFC0791]. The syntax of the IPv6 address
	MUST conform to RFC 4291 [RFC4291].		MUST conform to RFC 4291 [RFC4291].
	2.4.10. Client_Contact_ID		2.4.10. Client_Contact_ID
	The identifier of the contact object assigned by registrar.		The identifier of the contact object assigned by registrar.
	3. Report Definition Specification		3. Report Definition Specification
	Each report specification conceptually represents a file of comma		Each report specification conceptually represents a file of comma
	separated values (commonly called a CSV file) where the values are		separated values [RFC4180] (commonly called a CSV file) where the
	selected from the data elements specified above. The first row of		values are selected from the data elements specified above. The
	the file is a comma separated list of field names as specified in the		first row of the file is a comma separated list of field names as
	data element registry. The remaining rows of the file are the		specified in the data element registry. The remaining rows of the
	unordered sets of data elements, one set per row, where each row is		file are the unordered sets of data elements, one set per row, where
	one transaction in the report.		each row is one transaction in the report.
	Each data element conceptually represents the column heading in a		Each data element conceptually represents the column heading in a
	printed report. The first row represents the column headings and		printed report. The first row represents the column headings and
	each succeeding row represents a transaction of the report.		each succeeding row represents a transaction of the report.
	A consumer MUST be able to receive data elements that are not		A consumer MUST be able to receive data elements that are not
	recognized and MAY skip them accordingly, both in the header row and		recognized and MAY skip them accordingly, both in the header row and
	in the transaction rows.		in the transaction rows.
	A report is specified in the report registry with two pieces of		A report is specified in the report registry with two pieces of
	skipping to change at page 10, line 12 ¶		skipping to change at page 9, line 41 ¶
	specified above. The field names and the data MUST appear in the		specified above. The field names and the data MUST appear in the
	report in the order listed in the report registry.		report in the order listed in the report registry.
	The subsections below comprise an initial list of standard reports		The subsections below comprise an initial list of standard reports
	commonly being used between producers and consumers as of the data of		commonly being used between producers and consumers as of the data of
	publication of this document. The title of the subsection is the		publication of this document. The title of the subsection is the
	report name.		report name.
	3.1. Transaction Report		3.1. Transaction Report
	+------------------+------------------------+		[Note] There is a new column in this report that is not added to
	| Field | Reference |		other reports. There are discussions on whether to define if each
	+==================+========================+		field is mandatory. The column was added to this report only for
	| TLD | RFC XXXX Section 2.1.1 |		visualation and to further discussion. This paragraph will be
	+------------------+------------------------+		removed once working group discussed and reached consensus on
	| Server_TRID | Section 2.1.2 |		direction.
	+------------------+------------------------+
	| Domain | Section 2.1.3 |		+==================+========================+===========+
	+------------------+------------------------+		| Field | Reference | Mandatory |
	| DateTime | Section 2.1.6 |		+==================+========================+===========+
	+------------------+------------------------+		| TLD | RFC XXXX Section 2.1.1 | N |
	| Registrar_ID | Section 2.4.1 |		+------------------+------------------------+-----------+
	+------------------+------------------------+		| Server_TRID | Section 2.1.2 | Y |
	| Registrar | Section 2.1.11 |		+------------------+------------------------+-----------+
	+------------------+------------------------+		| Domain | Section 2.1.3 | Y |
	| Transaction_Type | Section 2.1.4 |		+------------------+------------------------+-----------+
	+------------------+------------------------+		| DateTime | Section 2.1.6 | Y |
	| Period | Section 2.1.12 |		+------------------+------------------------+-----------+
	+------------------+------------------------+		| Registrar_ID | Section 2.4.1 | Y |
	| Term | Section 2.1.7 |		+------------------+------------------------+-----------+
	+------------------+------------------------+		| Registrar | Section 2.1.11 | Y |
	| Fee | Section 2.1.8 |		+------------------+------------------------+-----------+
	+------------------+------------------------+		| Transaction_Type | Section 2.1.4 | Y |
	| Currency | Section 2.1.9 |		+------------------+------------------------+-----------+
	+------------------+------------------------+		| Period | Section 2.1.12 | Y |
	| Description | Section 2.1.13 |		+------------------+------------------------+-----------+
	+------------------+------------------------+		| Term | Section 2.1.7 | N |
			+------------------+------------------------+-----------+
			| Fee | Section 2.1.8 | Y |
			+------------------+------------------------+-----------+
			| Currency | Section 2.1.9 | Y |
			+------------------+------------------------+-----------+
			| Description | Section 2.1.13 | N |
			+------------------+------------------------+-----------+
	Table 1: Transaction Report Definition Table		Table 1: Transaction Report Definition Table
	3.2. Premium Name Report		3.2. Premium Name Report
	+-----------------+------------------------+		+=================+========================+
	| Field | Reference |		| Field | Reference |
	+=================+========================+		+=================+========================+
	| TLD | RFC XXXX Section 2.1.1 |		| TLD | RFC XXXX Section 2.1.1 |
	+-----------------+------------------------+		+-----------------+------------------------+
	| Domain | Section 2.1.3 |		| Domain | Section 2.1.3 |
	+-----------------+------------------------+		+-----------------+------------------------+
	| Status | Section 2.1.10 |		| Status | Section 2.1.10 |
	+-----------------+------------------------+		+-----------------+------------------------+
	| Description | Section 2.1.13 |		| Description | Section 2.1.13 |
	+-----------------+------------------------+		+-----------------+------------------------+
	skipping to change at page 11, line 24 ¶		skipping to change at page 11, line 17 ¶
	| Domain_Restore | Section 2.2.4 |		| Domain_Restore | Section 2.2.4 |
	+-----------------+------------------------+		+-----------------+------------------------+
	| Start_Date | Section 2.3.1 |		| Start_Date | Section 2.3.1 |
	+-----------------+------------------------+		+-----------------+------------------------+
	Table 2: Premium Name Report Definition		Table 2: Premium Name Report Definition
	Table		Table
	3.3. Domain RGP Report		3.3. Domain RGP Report
	+--------------+------------------------+		+==============+========================+
	| Field | Reference |		| Field | Reference |
	+==============+========================+		+==============+========================+
	| TLD | RFC XXXX Section 2.1.1 |		| TLD | RFC XXXX Section 2.1.1 |
	+--------------+------------------------+		+--------------+------------------------+
	| Domain | Section 2.1.3 |		| Domain | Section 2.1.3 |
	+--------------+------------------------+		+--------------+------------------------+
	| Deleted_Date | Section 2.3.2 |		| Deleted_Date | Section 2.3.2 |
	+--------------+------------------------+		+--------------+------------------------+
	| RGP_Date | Section 2.3.3 |		| RGP_Date | Section 2.3.3 |
	+--------------+------------------------+		+--------------+------------------------+
	| Purge_Date | Section 2.3.4 |		| Purge_Date | Section 2.3.4 |
	+--------------+------------------------+		+--------------+------------------------+
	Table 3: Domain RGP Report Definition		Table 3: Domain RGP Report Definition
	Table		Table
	3.4. Reserved Domain Report		3.4. Reserved Domain Report
	+--------+------------------------+		+========+========================+
	| Field | Reference |		| Field | Reference |
	+========+========================+		+========+========================+
	| TLD | RFC XXXX Section 2.1.1 |		| TLD | RFC XXXX Section 2.1.1 |
	+--------+------------------------+		+--------+------------------------+
	| Domain | Section 2.1.3 |		| Domain | Section 2.1.3 |
	+--------+------------------------+		+--------+------------------------+
	| Status | Section 2.1.10 |		| Status | Section 2.1.10 |
	+--------+------------------------+		+--------+------------------------+
	Table 4: Reserved Domain Report		Table 4: Reserved Domain Report
	Definition Table		Definition Table
	3.5. Domain Inventory Report		3.5. Domain Inventory Report
	+----------------------+------------------------+		+======================+========================+
	| Field | Reference |		| Field | Reference |
	+======================+========================+		+======================+========================+
	| TLD | RFC XXXX Section 2.1.1 |		| TLD | RFC XXXX Section 2.1.1 |
	+----------------------+------------------------+		+----------------------+------------------------+
	| Domain | Section 2.1.3 |		| Domain | Section 2.1.3 |
	+----------------------+------------------------+		+----------------------+------------------------+
	| Updated_Date | Section 2.3.5 |		| Updated_Date | Section 2.3.5 |
	+----------------------+------------------------+		+----------------------+------------------------+
	| Registrar_ID | Section 2.4.1 |		| Registrar_ID | Section 2.4.1 |
	+----------------------+------------------------+		+----------------------+------------------------+
	skipping to change at page 12, line 35 ¶		skipping to change at page 12, line 33 ¶
	+----------------------+------------------------+		+----------------------+------------------------+
	| DNSSEC | Section 2.4.3 |		| DNSSEC | Section 2.4.3 |
	+----------------------+------------------------+		+----------------------+------------------------+
	| Status | Section 2.1.10 |		| Status | Section 2.1.10 |
	+----------------------+------------------------+		+----------------------+------------------------+
	Table 5: Domain Inventory Report Definition Table		Table 5: Domain Inventory Report Definition Table
	3.6. Contact Inventory Report		3.6. Contact Inventory Report
	+-------------------+----------------+		+===================+================+
	| Field | Reference |		| Field | Reference |
	+===================+================+		+===================+================+
	| Server_Contact_ID | Section 2.4.4 |		| Server_Contact_ID | Section 2.4.4 |
	+-------------------+----------------+		+-------------------+----------------+
	| Client_Contact_ID | Section 2.4.10 |		| Client_Contact_ID | Section 2.4.10 |
	+-------------------+----------------+		+-------------------+----------------+
	| TLD | Section 2.1.1 |		| TLD | Section 2.1.1 |
	+-------------------+----------------+		+-------------------+----------------+
	| Domain | Section 2.1.3 |		| Domain | Section 2.1.3 |
	+-------------------+----------------+		+-------------------+----------------+
	skipping to change at page 13, line 14 ¶		skipping to change at page 13, line 11 ¶
	| INUSE | Section 2.4.7 |		| INUSE | Section 2.4.7 |
	+-------------------+----------------+		+-------------------+----------------+
	| Registrar_ID | Section 2.4.1 |		| Registrar_ID | Section 2.4.1 |
	+-------------------+----------------+		+-------------------+----------------+
	Table 6: Contact Inventory Report		Table 6: Contact Inventory Report
	Definition Table		Definition Table
	3.7. Host Inventory Report		3.7. Host Inventory Report
	+-----------------+-----------------------+		+=================+=======================+
	| Field | Reference |		| Field | Reference |
	+=================+=======================+		+=================+=======================+
	| TLD | RFCXXXX Section 2.1.1 |		| TLD | RFCXXXX Section 2.1.1 |
	+-----------------+-----------------------+		+-----------------+-----------------------+
	| Nameserver_Host | Section 2.4.8 |		| Nameserver_Host | Section 2.4.8 |
	+-----------------+-----------------------+		+-----------------+-----------------------+
	| Nameserver_IP | Section 2.4.9 |		| Nameserver_IP | Section 2.4.9 |
	+-----------------+-----------------------+		+-----------------+-----------------------+
	Table 7: Host Inventory Report		Table 7: Host Inventory Report
	skipping to change at page 14, line 49 ¶		skipping to change at page 14, line 46 ¶
	8.1. Normative References		8.1. Normative References
	[RFC0791] Postel, J., "Internet Protocol", September 1981,		[RFC0791] Postel, J., "Internet Protocol", September 1981,
	<https://www.rfc-editor.org/info/rfc791>.		<https://www.rfc-editor.org/info/rfc791>.
	[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>.
			[RFC4180] Shafranovich, Y., "IP Version 6 Addressing Architecture",
			February 2006, <https://www.rfc-editor.org/info/rfc4180>.
	[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing		[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
	Architecture", February 2006,		Architecture", February 2006,
	<https://www.rfc-editor.org/info/rfc4291>.		<https://www.rfc-editor.org/info/rfc4291>.
	[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",		[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
	August 2009, <https://www.rfc-editor.org/info/rfc5730>.		August 2009, <https://www.rfc-editor.org/info/rfc5730>.
	[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)		[RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
	Domain Name Mapping", August 2009,		Domain Name Mapping", August 2009,
	<https://www.rfc-editor.org/info/rfc5731>.		<https://www.rfc-editor.org/info/rfc5731>.
	[RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)		[RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
	Host Mapping", August 2009,		Host Mapping", August 2009,
	<https://www.rfc-editor.org/info/rfc5732>.		<https://www.rfc-editor.org/info/rfc5732>.
	[RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)		[RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
	Contact Mapping", August 2009,		Contact Mapping", August 2009,
	<https://www.rfc-editor.org/info/rfc5733>.		<https://www.rfc-editor.org/info/rfc5733>.
			[RFC5890] Klensin, J., "Extensible Provisioning Protocol (EPP)
			Contact Mapping", August 2009,
			<https://www.rfc-editor.org/info/rfc5890>.
	[RFC8748] Carney, R. and J. Frakes, "Registry Fee Extension for the		[RFC8748] Carney, R. and J. Frakes, "Registry Fee Extension for the
	Extensible Provisioning Protocol", March 2020,		Extensible Provisioning Protocol", March 2020,
	<https://www.rfc-editor.org/info/rfc8748>.		<https://www.rfc-editor.org/info/rfc8748>.
	8.2. Informative References		8.2. Informative References
			[IANA_Registrar_IDs]
			Internet Assigned Numbers Authority, "IANA Assignments -
			Registrar IDs", 2020, <https://www.iana.org/assignments/
			registrar-ids/registrar-ids.xhtml>.
	[ISO4217] International Organization for Standardization, "ISO 4217		[ISO4217] International Organization for Standardization, "ISO 4217
	Currency Codes", 2018, <https://www.currency-		Currency Codes", 2018, <https://www.currency-
	iso.org/dam/downloads/lists/list_one.xml>.		iso.org/dam/downloads/lists/list_one.xml>.
	[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,		[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
	DOI 10.17487/RFC2629, June 1999,		DOI 10.17487/RFC2629, June 1999,
	<https://www.rfc-editor.org/info/rfc2629>.		<https://www.rfc-editor.org/info/rfc2629>.
	[RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC		[RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC
	Text on Security Considerations", BCP 72, RFC 3552,		Text on Security Considerations", BCP 72, RFC 3552,
End of changes. 25 change blocks.
	84 lines changed or deleted		87 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/