--- 1/draft-ietf-regext-simple-registration-reporting-06.txt 2022-06-08 15:13:10.353683178 -0700 +++ 2/draft-ietf-regext-simple-registration-reporting-07.txt 2022-06-08 15:13:10.405684497 -0700 @@ -1,18 +1,18 @@ Internet Engineering Task Force J. Yee, Ed. Internet-Draft J. Galvin Intended status: Informational Donuts -Expires: 8 September 2022 7 March 2022 +Expires: 10 December 2022 8 June 2022 Simple Registration Reporting - draft-ietf-regext-simple-registration-reporting-06 + draft-ietf-regext-simple-registration-reporting-07 Abstract Domain name registries (the producer) and registrars (the consumer) report to each other by sharing bulk information through files. This document creates two IANA registries to establish a standard reporting mechanism between domain name registries and registrars. The first IANA registry lists standard data elements and their syntax for inclusion in the files. The second IANA registry lists standard reports based on the standard data elements. Each report is a file @@ -30,21 +30,21 @@ 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 8 September 2022. + This Internet-Draft will expire on 10 December 2022. Copyright Notice Copyright (c) 2022 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 @@ -57,94 +57,93 @@ 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 2. Data Element Specification . . . . . . . . . . . . . . . . . 4 2.1. General Information Data Elements . . . . . . . . . . . . 5 2.1.1. TLD . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.1.2. Server_TRID . . . . . . . . . . . . . . . . . . . . . 5 2.1.3. Domain . . . . . . . . . . . . . . . . . . . . . . . 5 2.1.4. Transaction_Type . . . . . . . . . . . . . . . . . . 5 2.1.5. Object_Type . . . . . . . . . . . . . . . . . . . . . 5 - 2.1.6. DateTime . . . . . . . . . . . . . . . . . . . . . . 5 - 2.1.7. Term . . . . . . . . . . . . . . . . . . . . . . . . 5 + 2.1.6. Date_Time . . . . . . . . . . . . . . . . . . . . . . 5 + 2.1.7. Period . . . . . . . . . . . . . . . . . . . . . . . 5 2.1.8. Fee . . . . . . . . . . . . . . . . . . . . . . . . . 6 2.1.9. Currency . . . . . . . . . . . . . . . . . . . . . . 6 2.1.10. Status . . . . . . . . . . . . . . . . . . . . . . . 6 2.1.11. Registrar . . . . . . . . . . . . . . . . . . . . . . 6 - 2.1.12. Period . . . . . . . . . . . . . . . . . . . . . . . 6 + 2.1.12. Period_Unit . . . . . . . . . . . . . . . . . . . . . 6 2.1.13. Description . . . . . . . . . . . . . . . . . . . . . 6 2.2. Domain Price Data Elements . . . . . . . . . . . . . . . 6 - 2.2.1. Domain_Create . . . . . . . . . . . . . . . . . . . . 6 - 2.2.2. Domain_Renew . . . . . . . . . . . . . . . . . . . . 6 - 2.2.3. Domain_Transfer . . . . . . . . . . . . . . . . . . . 7 - 2.2.4. Domain_Restore . . . . . . . . . . . . . . . . . . . 7 - 2.2.5. Trade . . . . . . . . . . . . . . . . . . . . . . . . 7 + 2.2.1. Price_Domain_Create . . . . . . . . . . . . . . . . . 6 + 2.2.2. Price_Domain_Renew . . . . . . . . . . . . . . . . . 7 + 2.2.3. Price_Domain_Transfer . . . . . . . . . . . . . . . . 7 + 2.2.4. Price_Domain_Restore . . . . . . . . . . . . . . . . 7 + 2.2.5. Price_Domain_Trade . . . . . . . . . . . . . . . . . 7 2.3. Timestamp Data Elements . . . . . . . . . . . . . . . . . 7 - 2.3.1. Start_Date . . . . . . . . . . . . . . . . . . . . . 7 + 2.3.1. Available_Date . . . . . . . . . . . . . . . . . . . 7 2.3.2. Deleted_Date . . . . . . . . . . . . . . . . . . . . 7 - 2.3.3. RGP_Date . . . . . . . . . . . . . . . . . . . . . . 7 - 2.3.4. Purge_Date . . . . . . . . . . . . . . . . . . . . . 7 - 2.3.5. Updated_Date . . . . . . . . . . . . . . . . . . . . 7 - 2.3.6. Create_Date . . . . . . . . . . . . . . . . . . . . . 8 - 2.3.7. Expiry_Date . . . . . . . . . . . . . . . . . . . . . 8 + 2.3.3. Redemption_End_Date . . . . . . . . . . . . . . . . . 7 + 2.3.4. Pending_Delete_Date . . . . . . . . . . . . . . . . . 7 + 2.3.5. Updated_Date . . . . . . . . . . . . . . . . . . . . 8 + 2.3.6. Created_Date . . . . . . . . . . . . . . . . . . . . 8 + 2.3.7. Expiration_Date . . . . . . . . . . . . . . . . . . . 8 2.4. Registration Information Data Elements . . . . . . . . . 8 2.4.1. Registrar_ID . . . . . . . . . . . . . . . . . . . . 8 - 2.4.2. Server_Registrant_ID . . . . . . . . . . . . . . . . 8 + 2.4.2. Registrant_ID . . . . . . . . . . . . . . . . . . . . 8 2.4.3. DNSSEC . . . . . . . . . . . . . . . . . . . . . . . 8 2.4.4. Server_Contact_ID . . . . . . . . . . . . . . . . . . 8 2.4.5. Contact_Type . . . . . . . . . . . . . . . . . . . . 8 - 2.4.6. Contact_Name . . . . . . . . . . . . . . . . . . . . 8 - 2.4.7. In_use . . . . . . . . . . . . . . . . . . . . . . . 9 - 2.4.8. Nameserver_Host . . . . . . . . . . . . . . . . . . . 9 - 2.4.9. Nameserver_IP . . . . . . . . . . . . . . . . . . . . 9 + 2.4.6. Contact_Name . . . . . . . . . . . . . . . . . . . . 9 + 2.4.7. Linked . . . . . . . . . . . . . . . . . . . . . . . 9 + 2.4.8. Host_Name . . . . . . . . . . . . . . . . . . . . . . 9 + 2.4.9. Host_IP . . . . . . . . . . . . . . . . . . . . . . . 9 2.4.10. Client_Contact_ID . . . . . . . . . . . . . . . . . . 9 3. Report Definition Specification . . . . . . . . . . . . . . . 9 3.1. Domain Transaction . . . . . . . . . . . . . . . . . . . 10 3.2. Premium Name . . . . . . . . . . . . . . . . . . . . . . 11 - 3.3. Domain RGP . . . . . . . . . . . . . . . . . . . . . . . 11 - 3.4. Reserved Domain . . . . . . . . . . . . . . . . . . . . . 12 - 3.5. Domain Inventory . . . . . . . . . . . . . . . . . . . . 12 - 3.6. Contact Inventory . . . . . . . . . . . . . . . . . . . . 13 - 3.7. Host Inventory . . . . . . . . . . . . . . . . . . . . . 14 - 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 - 4.1. Report Specification . . . . . . . . . . . . . . . . . . 15 - 4.1.1. Designated Expert Evaluation Criteria . . . . . . . . 15 - 4.1.2. Registration Procedure . . . . . . . . . . . . . . . 16 - 4.1.2.1. Required Information . . . . . . . . . . . . . . 16 - 4.1.2.2. Registration Processing . . . . . . . . . . . . . 17 - 4.1.2.3. Updating Report Definition Registry Entries . . . 17 - 4.2. Initial assignments . . . . . . . . . . . . . . . . . . . 18 - 4.2.1. Data Element Definition in IANA Registry . . . . . . 18 - 4.2.2. Report Definition in IANA Registry . . . . . . . . . 29 - 5. Security Considerations . . . . . . . . . . . . . . . . . . . 32 - 6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 32 - 7. Internationalization Considerations . . . . . . . . . . . . . 32 - 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 32 - 8.1. Normative References . . . . . . . . . . . . . . . . . . 32 - 8.2. Informative References . . . . . . . . . . . . . . . . . 33 - Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 34 - Appendix B. File Naming Convention . . . . . . . . . . . . . . . 34 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34 + 3.3. Domain RGP . . . . . . . . . . . . . . . . . . . . . . . 12 + 3.4. Reserved Domain . . . . . . . . . . . . . . . . . . . . . 13 + 3.5. Domain Inventory . . . . . . . . . . . . . . . . . . . . 13 + 3.6. Contact Inventory . . . . . . . . . . . . . . . . . . . . 14 + 3.7. Host Inventory . . . . . . . . . . . . . . . . . . . . . 15 + 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 + 4.1. Report Specification . . . . . . . . . . . . . . . . . . 16 + 4.1.1. Designated Expert Evaluation Criteria . . . . . . . . 16 + 4.1.2. Registration Procedure . . . . . . . . . . . . . . . 17 + 4.1.2.1. Required Information . . . . . . . . . . . . . . 17 + 4.1.2.2. Registration Processing . . . . . . . . . . . . . 18 + 4.1.2.3. Updating Report Definition Registry Entries . . . 18 + 4.2. Initial assignments . . . . . . . . . . . . . . . . . . . 19 + 4.2.1. Data Element Definition in IANA Registry . . . . . . 19 + 4.2.2. Report Definition in IANA Registry . . . . . . . . . 30 + 5. Security Considerations . . . . . . . . . . . . . . . . . . . 33 + 6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 33 + 7. Internationalization Considerations . . . . . . . . . . . . . 33 + 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 33 + 8.1. Normative References . . . . . . . . . . . . . . . . . . 33 + 8.2. Informative References . . . . . . . . . . . . . . . . . 34 + Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 35 + Appendix B. File Naming Convention . . . . . . . . . . . . . . . 35 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35 1. Introduction Currently, domain name registry operators (the producer) create and set their own domain name registration reports for use by their registrars (the consumer). Among the distinctions that vary by producer 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 may be a CSV file that tends to allow for straightforward importation or a PDF file that can be problematic to import. In addition, - although there are a number of best practice reports that have - evolved, these are not currently documented as such, which results in - a fair amount of customization on the part of the consumers to import - data. + although there are a number of best practices that have evolved, + these are not currently documented as such, which results in a fair + amount of customization on the part of the consumers to import data. This document standardizes the name and syntax of the data elements to be used across all existing domain name registration reports and creates an IANA registry of them to facilitate their evolution, including adding additional data elements as needed. In addition, a known set of existing standard reports using the aforementioned data elements is specified in another IANA registry to facilitate the evolution of the reports and adding additional report definitions as needed. @@ -175,20 +174,24 @@ 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 specified. The name of the data element MUST be unique and this characteristic MUST be enforced by the registry. The name is used in the report definition (in the next section) to alert the consumer as to what to expect in the file and how to import the data element. Character encoding recommendation for data elements is specified in Section 7. + The data elements adopt the same naming convention, where all the + leading character of each word use upper-case and the rest in lower- + case, and each word join with symobl underbars as a word separator. + The subsections below comprise an initial list of known data elements commonly being used between producers and consumers as of the date of publication of this document. The title of the subsection is the data element name for the data element. Data element names in the IANA registry MUST be unique and MUST be processed as case insensitive. 2.1. General Information Data Elements 2.1.1. TLD @@ -211,26 +214,26 @@ The type of transform action made to the domain object (e.g., create, delete, update, transfer, renew) as specified in RFC 5730 [RFC5730] Section 2.9.3. 2.1.5. Object_Type The object type involved in the report. In the EPP environment, an object could be domain RFC 5731 [RFC5731], contact RFC 5733 [RFC5733], or host RFC 5732 [RFC5732]. -2.1.6. DateTime +2.1.6. Date_Time The timestamp of the transaction recorded in the system. Dates and Times MUST be expressed as defined in RFC 5731 [RFC5731] Section 2.4. -2.1.7. Term +2.1.7. Period The number of units added to the domain registration period in RFC 5731 [RFC5731] in create, renew or transfer transforms. If there is no , the default value set out-of-band by the registry should be used. 2.1.8. Fee The amount of money charged or returned (shown as a negative value) to the registrar. The numeric format MUST conform to the currency @@ -238,124 +241,127 @@ "balanceType" as defined in RFC 8748 [RFC8748]. 2.1.9. Currency The currency used in the money charged as documented above in Section 2.1.8. The currency code should follow the ISO 4217 [ISO4217] standard. 2.1.10. Status - The status of the domain object. It MUST be one of the values - specified in RFC 5731 [RFC5731] Section 2.3. + The status or statuses of the domain object. It MUST be one of the + values specified in RFC 5731 [RFC5731] Section 2.3. If there are + multiple statuses, each must be separated by symbol commma, with the + whole string under double quotes as specified in RFC 4180 [RFC4180] 2.1.11. Registrar The name of the registrar. This data element is text/string with no - naming convention enforced. + naming convention enforced. The string must be under double quotes + if it contains comma symbol as specified in RFC 4180 [RFC4180] -2.1.12. Period +2.1.12. Period_Unit - The type of time (year, month) in 'Term' described above in + The type of time (year, month) in 'Period' described above in Section 2.1.7. The value of 'year' and 'month' are referenced to pUnitType value 'y' and 'm' respectively. pUnitType is specified in RFC 5731 [RFC5731]. 2.1.13. Description Additional information regarding the current entry in the report. It is provided by the producer and its actual value is a matter of local policy. This data element is text/string with no naming convention enforced. 2.2. Domain Price Data Elements -2.2.1. Domain_Create +2.2.1. Price_Domain_Create The fee charged to create the domain. The format must conform to "balanceType" as defined in RFC 8748 [RFC8748]. -2.2.2. Domain_Renew +2.2.2. Price_Domain_Renew The fee charged to renew the domain. The format must conform to "balanceType" as defined in RFC 8748 [RFC8748]. -2.2.3. Domain_Transfer +2.2.3. Price_Domain_Transfer The fee charged to transfer the domain. The format must conform to "balanceType" as defined in RFC 8748 [RFC8748]. -2.2.4. Domain_Restore +2.2.4. Price_Domain_Restore The fee charged to restore the domain. The format must conform to "balanceType" as defined in RFC 8748 [RFC8748]. -2.2.5. Trade +2.2.5. Price_Domain_Trade The fee charged to trade the domain. The format must conform to "balanceType" as defined in RFC 8748 [RFC8748]. 2.3. Timestamp Data Elements -2.3.1. Start_Date +2.3.1. Available_Date The timestamp of when the domain object becomes available. The date and time format follows the "type=dateTime" specification as defined in RFC 5731 [RFC5731]. 2.3.2. Deleted_Date The timestamp of when the domain was deleted. The date and time format follows the "type=dateTime" specification as defined in RFC 5731 [RFC5731]. -2.3.3. RGP_Date +2.3.3. Redemption_End_Date The timestamp of when the domain will complete its redemption grace period. The date and time format follows the "type=dateTime" specification as defined in RFC 5731 [RFC5731]. -2.3.4. Purge_Date +2.3.4. Pending_Delete_Date The timestamp of when the domain will be purged and become available again. The date and time format follows the "type=dateTime" specification as defined in RFC 5731 [RFC5731]. 2.3.5. Updated_Date The timestamp of the last time the domain object was updated. The date and time format follows the "type=dateTime" specification as defined in RFC 5731 [RFC5731]. -2.3.6. Create_Date +2.3.6. Created_Date The timestamp of when the domain object was allocated. The date and time format follows the "type=dateTime" specification as defined in RFC 5731 [RFC5731]. -2.3.7. Expiry_Date +2.3.7. Expiration_Date The timestamp of when the domain object will expire. The date and time format follows the "type=dateTime" specification as defined in RFC 5731 [RFC5731]. 2.4. Registration Information Data Elements 2.4.1. Registrar_ID The identifier assigned to the registrar. If the registrar is accredited under ICANN, it MUST be the registrar's IANA ID [IANA_Registrar_IDs]. Otherwise it is a value known between the producer and the consumer, set via an out-of-band mechanism and unique within all reports of the producer. -2.4.2. Server_Registrant_ID +2.4.2. Registrant_ID The identifier, issued by EPP server, assigned to the contact object that is associated as registrant of the domain name that MUST conform to "clIDType" specified in RFC 5730 [RFC5730]. 2.4.3. DNSSEC The value MUST be either 'YES' or 'NO' to indicate whether the domain is DNSSEC signed. @@ -368,58 +374,60 @@ The value MUST be one of value as defined by "contactAttrType" in RFC 5731 [RFC5731]. 2.4.6. Contact_Name The name of the contact object. Usually it is the name of an individual or an organization as described in RFC 5733 [RFC5733] Section 2.3. -2.4.7. In_use +2.4.7. Linked The value MUST be either "YES" or "NO" to indicate whether the contact object is associated with a domain object. -2.4.8. Nameserver_Host +2.4.8. Host_Name The full domain name of the host object as defined in RFC 5732 [RFC5732] Section 2.1. The name MUST be in A-label format as defined by RFC5890 [RFC5890]. -2.4.9. Nameserver_IP +2.4.9. Host_IP The IP address of the host object. The syntax of the IPv4 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]. If it contains mutliple IP + addresses, each must be separated by symbol comma with the whole + string under double quotes as specified in RFC 4180 [RFC4180] 2.4.10. Client_Contact_ID The identifier of the contact object assigned by the registrar and MUST conform to "clIDType" specified in RFC 5730 [RFC5730]. 3. Report Definition Specification Each report specification conceptually represents a file of comma separated values [RFC4180] (commonly called a CSV file) where the values are selected from the data elements specified above. The first row of the file is a comma separated list of data element names as specified in the data element registry. The remaining rows of the file are the unordered sets of data elements, one set per row, where - each row is one transaction in the report. + each row is one record in the report. Each data element in a set conceptually represents the column heading - in a printed report. + in a report. A consumer MUST be able to receive data elements that are not recognized and MAY skip them accordingly, both in the header row and - in the transaction rows. + in the record rows. A report is specified in the report registry with two pieces of information. First is the name of the report. This can be whatever is appropriate as defined by the producer of the report. The name of the report MUST be unique and this characteristic MUST be enforced by registry. Second is the ordered list of data element names of what is included in the report. The data element names MUST be listed in the data element registry specified above. The data element names and the @@ -429,186 +437,207 @@ The subsections below comprise an initial list of standard reports commonly being used between producers and consumers as of the date of publication of this document. The title of the subsection is the report name. The report name in the IANA registry MUST be unique and MUST be processed as case insensitive. 3.1. Domain Transaction Name of report: domain_transaction + Description: This report keeps records of actions taken by registrar + or the registry system on the domain under registrar's management + that changed the domain's status, charge or refund fee to registrar. + +==================+========================+ | Data Element | Reference | +==================+========================+ | TLD | RFC XXXX Section 2.1.1 | +------------------+------------------------+ | Server_TRID | Section 2.1.2 | +------------------+------------------------+ | Domain | Section 2.1.3 | +------------------+------------------------+ - | DateTime | Section 2.1.6 | + | Date_Time | Section 2.1.6 | +------------------+------------------------+ | Registrar_ID | Section 2.4.1 | +------------------+------------------------+ | Registrar | Section 2.1.11 | +------------------+------------------------+ | Transaction_Type | Section 2.1.4 | +------------------+------------------------+ - | Period | Section 2.1.12 | + | Period_Unit | Section 2.1.12 | +------------------+------------------------+ - | Term | Section 2.1.7 | + | Period | Section 2.1.7 | +------------------+------------------------+ | Fee | Section 2.1.8 | +------------------+------------------------+ | Currency | Section 2.1.9 | +------------------+------------------------+ | Description | Section 2.1.13 | +------------------+------------------------+ Table 1: Transaction Report Definition Table 3.2. Premium Name Name of report: premium_name - +=================+========================+ + Description: This report list the domain and its price that is + different, ususally higher, from the regular price + +=======================+========================+ | Data Element | Reference | - +=================+========================+ + +=======================+========================+ | TLD | RFC XXXX Section 2.1.1 | - +-----------------+------------------------+ + +-----------------------+------------------------+ | Domain | Section 2.1.3 | - +-----------------+------------------------+ + +-----------------------+------------------------+ | Status | Section 2.1.10 | - +-----------------+------------------------+ + +-----------------------+------------------------+ | Description | Section 2.1.13 | - +-----------------+------------------------+ + +-----------------------+------------------------+ | Currency | Section 2.1.9 | - +-----------------+------------------------+ - | Domain_Create | Section 2.2.1 | - +-----------------+------------------------+ - | Domain_Renew | Section 2.2.2 | - +-----------------+------------------------+ - | Domain_Transfer | Section 2.2.3 | - +-----------------+------------------------+ - | Domain_Restore | Section 2.2.4 | - +-----------------+------------------------+ - | Start_Date | Section 2.3.1 | - +-----------------+------------------------+ + +-----------------------+------------------------+ + | Price_Domain_Create | Section 2.2.1 | + +-----------------------+------------------------+ + | Price_Domain_Renew | Section 2.2.2 | + +-----------------------+------------------------+ + | Price_Domain_Transfer | Section 2.2.3 | + +-----------------------+------------------------+ + | Price_Domain_Restore | Section 2.2.4 | + +-----------------------+------------------------+ + | Available_Date | Section 2.3.1 | + +-----------------------+------------------------+ - Table 2: Premium Name Report Definition - Table + Table 2: Premium Name Report Definition Table 3.3. Domain RGP Name of report: domain_rgp - +==============+========================+ + + Description: This report tracks the domains under registrar's + management that are deleted and in the Redemption Grace Period (RGP). + + +=====================+========================+ | Data Element | Reference | - +==============+========================+ + +=====================+========================+ | TLD | RFC XXXX Section 2.1.1 | - +--------------+------------------------+ + +---------------------+------------------------+ | Domain | Section 2.1.3 | - +--------------+------------------------+ + +---------------------+------------------------+ | Deleted_Date | Section 2.3.2 | - +--------------+------------------------+ - | RGP_Date | Section 2.3.3 | - +--------------+------------------------+ - | Purge_Date | Section 2.3.4 | - +--------------+------------------------+ + +---------------------+------------------------+ + | Redemption_End_Date | Section 2.3.3 | + +---------------------+------------------------+ + | Pending_Delete_Date | Section 2.3.4 | + +---------------------+------------------------+ - Table 3: Domain RGP Report Definition - Table + Table 3: Domain RGP Report Definition Table 3.4. Reserved Domain Name of report: reserved_domain + Description: This report lists name that are reserved by the registry + system and the domain's current status. + +==============+========================+ | Data Element | Reference | +==============+========================+ | TLD | RFC XXXX Section 2.1.1 | +--------------+------------------------+ | Domain | Section 2.1.3 | +--------------+------------------------+ | Status | Section 2.1.10 | +--------------+------------------------+ Table 4: Reserved Domain Report Definition Table 3.5. Domain Inventory Name of report: domain_inventory - +======================+========================+ + + Description: This report lists all domain currently under the + registrar's management and its related attributes. + + +=================+========================+ | Data Element | Reference | - +======================+========================+ + +=================+========================+ | TLD | RFC XXXX Section 2.1.1 | - +----------------------+------------------------+ + +-----------------+------------------------+ | Domain | Section 2.1.3 | - +----------------------+------------------------+ + +-----------------+------------------------+ | Updated_Date | Section 2.3.5 | - +----------------------+------------------------+ + +-----------------+------------------------+ | Registrar_ID | Section 2.4.1 | - +----------------------+------------------------+ - | Create_Date | Section 2.3.6 | - +----------------------+------------------------+ - | Expiry_Date | Section 2.3.7 | - +----------------------+------------------------+ - | Server_Registrant_ID | Section 2.4.2 | - +----------------------+------------------------+ + +-----------------+------------------------+ + | Created_Date | Section 2.3.6 | + +-----------------+------------------------+ + | Expiration_Date | Section 2.3.7 | + +-----------------+------------------------+ + | Registrant_ID | Section 2.4.2 | + +-----------------+------------------------+ | DNSSEC | Section 2.4.3 | - +----------------------+------------------------+ + +-----------------+------------------------+ | Status | Section 2.1.10 | - +----------------------+------------------------+ + +-----------------+------------------------+ - Table 5: Domain Inventory Report Definition Table + Table 5: Domain Inventory Report + Definition Table 3.6. Contact Inventory Name of report: contact_inventory + + Description: This report lists all contact created by the registrar + and any assocations it has to any domains. + +===================+================+ | Data Element | Reference | +===================+================+ | Server_Contact_ID | Section 2.4.4 | +-------------------+----------------+ | Client_Contact_ID | Section 2.4.10 | +-------------------+----------------+ | TLD | Section 2.1.1 | +-------------------+----------------+ | Domain | Section 2.1.3 | +-------------------+----------------+ | Contact_Type | Section 2.4.5 | +-------------------+----------------+ | Contact_Name | Section 2.4.6 | +-------------------+----------------+ | Updated_Date | Section 2.3.5 | +-------------------+----------------+ - | INUSE | Section 2.4.7 | - +-------------------+----------------+ - | Registrar_ID | Section 2.4.1 | + | Linked | Section 2.4.7 | +-------------------+----------------+ Table 6: Contact Inventory Report Definition Table 3.7. Host Inventory Name of report: host_inventory - +=================+=======================+ + Description: This reports list all the host objects and its + attributes under registrar's management. + + +==============+=======================+ | Data Element | Reference | - +=================+=======================+ + +==============+=======================+ | TLD | RFCXXXX Section 2.1.1 | - +-----------------+-----------------------+ - | Nameserver_Host | Section 2.4.8 | - +-----------------+-----------------------+ - | Nameserver_IP | Section 2.4.9 | - +-----------------+-----------------------+ + +--------------+-----------------------+ + | Host_Name | Section 2.4.8 | + +--------------+-----------------------+ + | Host_IP | Section 2.4.9 | + +--------------+-----------------------+ Table 7: Host Inventory Report Definition Table 4. IANA Considerations This section describes the format of the IANA Registration Report Registry, which has two tables described below, and the procedures used to populate and manage the registry entries. @@ -835,37 +864,37 @@ IESG, iesg@ietf.org Status: Active ---- END FORM ---- ---- BEGIN FORM ---- Name of data element: - DateTime + Date_Time Reference: This RFC Section 2.1.6 Registrant: IESG, iesg@ietf.org Status: Active ---- END FORM ---- ---- BEGIN FORM ---- Name of data element: - Term + Period Reference: This RFC Section 2.1.7 Registrant: IESG, iesg@ietf.org Status: Active @@ -915,21 +944,21 @@ IESG, iesg@ietf.org Status: Active ---- END FORM ---- ---- BEGIN FORM ---- Name of data element: - Period + Period_Unit Reference: This RFC Section 2.1.12 Registrant: IESG, iesg@ietf.org Status: Active @@ -947,85 +976,85 @@ IESG, iesg@ietf.org Status: Active ---- END FORM ---- ---- BEGIN FORM ---- Name of data element: - Domain_Create + Price_Domain_Create Reference: This RFC Section 2.2.1 Registrant: IESG, iesg@ietf.org Status: Active ---- END FORM ---- ---- BEGIN FORM ---- Name of data element: - Domain_Renew + Price_Domain_Renew Reference: This RFC Section 2.2.2 Registrant: IESG, iesg@ietf.org Status: Active ---- END FORM ---- ---- BEGIN FORM ---- Name of data element: - Domain_Transfer + Price_Domain_Transfer Reference: This RFC Section 2.2.3 Registrant: IESG, iesg@ietf.org Status: Active ---- END FORM ---- ---- BEGIN FORM ---- Name of data element: - Domain_Restore + Price_Domain_Restore Reference: This RFC Section 2.2.4 Registrant: IESG, iesg@ietf.org Status: Active ---- END FORM ---- ---- BEGIN FORM ---- Name of data element: - Start_Date + Available_Date Reference: This RFC Section 2.3.1 Registrant: IESG, iesg@ietf.org Status: Active @@ -1043,37 +1072,37 @@ IESG, iesg@ietf.org Status: Active ---- END FORM ---- ---- BEGIN FORM ---- Name of data element: - RGP_Date + Redemption_End_Date Reference: This RFC Section 2.3.3 Registrant: IESG, iesg@ietf.org Status: Active ---- END FORM ---- ---- BEGIN FORM ---- Name of data element: - Purge_Date + Pending_Delete_Date Reference: This RFC Section 2.3.4 Registrant: IESG, iesg@ietf.org Status: Active @@ -1091,37 +1120,37 @@ IESG, iesg@ietf.org Status: Active ---- END FORM ---- ---- BEGIN FORM ---- Name of data element: - Create_Date + Created_Date Reference: This RFC Section 2.3.6 Registrant: IESG, iesg@ietf.org Status: Active ---- END FORM ---- ---- BEGIN FORM ---- Name of data element: - Expiry_Date + Expiration_Date Reference: This RFC Section 2.3.7 Registrant: IESG, iesg@ietf.org Status: Active @@ -1139,21 +1168,21 @@ IESG, iesg@ietf.org Status: Active ---- END FORM ---- ---- BEGIN FORM ---- Name of data element: - Server_Registrant_ID + Registrant_ID Reference: This RFC Section 2.4.2 Registrant: IESG, iesg@ietf.org Status: Active @@ -1219,53 +1248,53 @@ IESG, iesg@ietf.org Status: Active ---- END FORM ---- ---- BEGIN FORM ---- Name of data element: - INUSE + Linked Reference: This RFC Section 2.4.7 Registrant: IESG, iesg@ietf.org Status: Active ---- END FORM ---- ---- BEGIN FORM ---- Name of data element: - Nameserver_Host + Host_Name Reference: This RFC Section 2.4.8 Registrant: IESG, iesg@ietf.org Status: Active ---- END FORM ---- ---- BEGIN FORM ---- Name of data element: - Nameserver_IP + Host_IP Reference: This RFC Section 2.4.9 Registrant: IESG, iesg@ietf.org Status: Active @@ -1511,34 +1540,20 @@ Extensible Provisioning Protocol", March 2021, . 8.2. Informative References [IANA_Registrar_IDs] Internet Assigned Numbers Authority, "IANA Assignments - Registrar IDs", 2020, . - [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, - DOI 10.17487/RFC2629, June 1999, - . - - [RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC - Text on Security Considerations", BCP 72, RFC 3552, - DOI 10.17487/RFC3552, July 2003, - . - - [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an - IANA Considerations Section in RFCs", RFC 5226, - DOI 10.17487/RFC5226, May 2008, - . - Appendix A. Acknowledgements The authors would like to thank Roger Carney, Jody Kolker, Tobias Sattler, and bestpractice.domains for their reviews and suggestions. Appendix B. File Naming Convention TBD on file naming convention suggestion Authors' Addresses