Internet Engineering Task Force G.L. Lozano Internet-Draft E.A. Alvarez Intended status: Informational ICANN Expires: 17 March 2023 13 September 2022 ICANN Registrar Interfaces draft-icann-registrar-interfaces-09 Abstract This document describes the interfaces provided by ICANN to Registrars and Data Escrow Agents to fulfill the data escrow requirements of the Registrar Accreditation Agreement and the Registrar Data Escrow Specifications. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. 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 17 March 2023. 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 and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Lozano & Alvarez Expires 17 March 2023 [Page 1] Internet-Draft ICANN Registrar Interfaces September 2022 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Date and Time . . . . . . . . . . . . . . . . . . . . . . 3 1.3. Common elements used in this specification . . . . . . . 3 2. Interfaces for Registrar Data Escrow Notifications . . . . . 3 2.1. Registrar Reporting . . . . . . . . . . . . . . . . . . . 4 2.2. Data Escrow Agent Reporting . . . . . . . . . . . . . . . 6 3. Technical details of the interfaces . . . . . . . . . . . . . 12 3.1. Registrar Reporting . . . . . . . . . . . . . . . . . . . 12 3.2. Data Escrow Agent Reporting . . . . . . . . . . . . . . . 14 4. Monitoring Registrar reporting . . . . . . . . . . . . . . . 15 4.1. Monitoring the reporting status of a Registrar . . . . . 15 4.2. Monitoring Registrar Data Escrow Reports . . . . . . . . 18 4.3. Monitoring Registrar Data Escrow Agent Notifications . . 20 5. Internationalization Considerations . . . . . . . . . . . . . 22 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 22 7.1. Implementation in the gTLD space . . . . . . . . . . . . 23 8. Security Considerations . . . . . . . . . . . . . . . . . . . 23 9. Change History . . . . . . . . . . . . . . . . . . . . . . . 23 9.1. Version 00 . . . . . . . . . . . . . . . . . . . . . . . 24 9.2. Version 01 . . . . . . . . . . . . . . . . . . . . . . . 24 9.3. Version 02 . . . . . . . . . . . . . . . . . . . . . . . 24 9.4. Version 03 . . . . . . . . . . . . . . . . . . . . . . . 24 9.5. Version 04 . . . . . . . . . . . . . . . . . . . . . . . 24 9.6. Version 05 . . . . . . . . . . . . . . . . . . . . . . . 24 9.7. Version 06 . . . . . . . . . . . . . . . . . . . . . . . 24 9.8. Version 07 . . . . . . . . . . . . . . . . . . . . . . . 24 9.9. Version 08 . . . . . . . . . . . . . . . . . . . . . . . 25 9.10. Version 09 . . . . . . . . . . . . . . . . . . . . . . . 25 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 10.1. Normative References . . . . . . . . . . . . . . . . . . 25 10.2. Informative References . . . . . . . . . . . . . . . . . 26 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 1. Introduction This document describes the technical details of the interfaces provided by the Internet Corporation for Assigned Names and Numbers (ICANN) to Registrars and Data Escrow Agents to fulfill the data escrow requirements of the Registrar Accreditation Agreement [ICANN-RAA-2013] and the Registrar Data Escrow Specifications [ICANN-RDE-SPEC]. Extensible Markup Language (XML) 1.0 as described in [W3C.REC-xml-20081126] is used in this specification. Lozano & Alvarez Expires 17 March 2023 [Page 2] Internet-Draft ICANN Registrar Interfaces September 2022 The provisioning of credentials and authentication methods used in the interfaces is outside of this document's scope. 1.1. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented to develop a conforming implementation. 1.2. Date and Time Numerous fields indicate "date and time", such as the creation and receipt dates for data escrow deposits. These fields SHALL contain timestamps indicating the date and time in UTC as specified in [RFC3339], with no offset from the zero meridian. 1.3. Common elements used in this specification Common elements used in this specification are explained in this section. * : The base URL used in the reporting interfaces examples must be replaced with the URL indicated by ICANN. * This document uses the term of "Differential" deposit as defined in the Registry Data Escrow Specification (see, [RFC8909]), while the Registrar Data Escrow Specifications [ICANN-RDE-SPEC] refers to the same concept as "Incremental" deposit. * A-label and NR-LDH, as defined in [RFC5890]. 2. Interfaces for Registrar Data Escrow Notifications This section describes the interfaces provided by ICANN to the Registrars and Data Escrow Agents to fulfill their reporting requirements related to Registrar Data Escrow Specifications [ICANN-RDE-SPEC]. Lozano & Alvarez Expires 17 March 2023 [Page 3] Internet-Draft ICANN Registrar Interfaces September 2022 2.1. Registrar Reporting To notify that a data escrow deposit has been submitted to a Data Escrow Agent, the ICANN-accredited Registrar sends a object (see, [I-D.lozano-icann-registry-interfaces]) to ICANN. The following considerations apply for a object corresponding to a data escrow deposit for a Registrar repository: * The element in the object (see, [RFC9022]) MUST be present and have a value corresponding to the IANA Registrar ID assigned by ICANN. * A element MUST be included with the corresponding "rcdn" attribute in the object to indicate the total domains in the Registrar repository for each Registry Class Domain Name (e.g., example) with at least one domain name allocation at a specific point in time (watermark), regardless of the type of deposit: full or differential. - If the "https://www.icann.org/en/system/files/files/rde-specs- 09nov07-en.pdf" specification is being used as the , then the "uri" attribute in the elements for domain names MUST have a value of "urn:ietf:params:xml:ns:rdeDomain-1.0". * To indicate that a Registrar repository has no domain names, one element MUST be included with the "uri" attribute value of "urn:ietf:params:xml:ns:rdeDomain-1.0", no "rcdn" attribute, and a value of 0 (zero). The object for each deposit successfully sent to the Data Escrow Agent is sent using the PUT HTTP verb in the interface provided by ICANN at: /report/registrar-escrow-report// Where: - MUST be substituted with the IANA Registrar ID assigned by ICANN for which the report is being provided. - MUST be substituted with the identifier assigned to the report, which MUST be the same as the "id" attribute from the . Lozano & Alvarez Expires 17 March 2023 [Page 4] Internet-Draft ICANN Registrar Interfaces September 2022 Note: The interface supports overwriting the information of a particular report to support asynchronous interfaces between Registrars and Data Escrow Agents. Example of a object for a data escrow deposit corresponding to a Registrar repository: 20170801001 1 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 0 2017-08-01T00:15:00.0Z FULL 2017-08-01T00:00:00Z 9999 2 8 3 Example of a object for an empty data escrow deposit corresponding to a Registrar repository: Lozano & Alvarez Expires 17 March 2023 [Page 5] Internet-Draft ICANN Registrar Interfaces September 2022 20170801001 1 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 0 2017-08-01T00:15:00.0Z FULL 2017-08-01T00:00:00Z 9999 0 2.2. Data Escrow Agent Reporting The Registrar Data Escrow Specification requires that Registrar Data Escrow Agents deliver to ICANN a notification every time a successfully processed deposit is received from the Registrar regardless of the final status of the verification process, in addition to a failure notification if a scheduled deposit is not received from a Registrar. In order to satisfy this requirement, the Data Escrow Agent sends to ICANN a object as defined in Section 2 of [I-D.lozano-icann-registry-interfaces], to ICANN using the POST HTTP verb in the interface provided by ICANN at: /report/registrar-escrow-agent-notification/ Where: - MUST be substituted with the IANA Registrar ID assigned by ICANN for which the notification is being provided. A with DRFN (Deposit Receipt Failure Notice) status is used to notify that a data escrow deposit has not been processed for verification for a past date where a deposit was scheduled to be received from the Registrar. Lozano & Alvarez Expires 17 March 2023 [Page 6] Internet-Draft ICANN Registrar Interfaces September 2022 In addition to the considerations listed in Section 2.1 for the object of the notification, if the data escrow deposit does not include an , a unique value MUST be generated by the Data Escrow Agent to reference the deposit and it MUST be provided in the element. In the case of a with DVFN (Deposit Verification Failure Notice) status, the element MUST be present and include a object for each deposit verification error condition and specify in the corresponding "domainCount" attribute the number of domain names with such error conditions. Note: an error condition may be present several times in the same domain escrow record (e.g., the administrative, technical and billing contact contains invalid email syntax). In this case only one domain name is affected by the error condition, therefore the "domainCount" attribute value must be increased by one in the corresponding object. The following table defines the result codes and messages that a Data Escrow Agent could use to report verification issues found in a Registrar data escrow deposit. When using result codes 2102, 2103, 2104, 2105, 2106, 2107, 2108, 2109, or 2110, the "domainCount" attribute MUST be present. +=============+=====================================================+ | Result Code | Message | +=============+=====================================================+ | 2001 | No corresponding hash file found for deposit file. | +-------------+-----------------------------------------------------+ | 2002 | Hash does not match the corresponding deposit | | | file. | +-------------+-----------------------------------------------------+ | 2003 | Invalid hash file format. | +-------------+-----------------------------------------------------+ | 2004 | Data escrow deposit PGP signature verification | | | error. | +-------------+-----------------------------------------------------+ | 2005 | Archive includes unrecognized files. | +-------------+-----------------------------------------------------+ | 2006 | Invalid encoding for data escrow deposit file. | +-------------+-----------------------------------------------------+ | 2007 | Data escrow deposit file size exceeds the maximum | | | allowed size. | +-------------+-----------------------------------------------------+ | 2008 | Data escrow deposit file exceeds the maximum | | | allowed number of lines. | Lozano & Alvarez Expires 17 March 2023 [Page 7] Internet-Draft ICANN Registrar Interfaces September 2022 +-------------+-----------------------------------------------------+ | 2101 | Unrecognized data escrow deposit file CSV header. | +-------------+-----------------------------------------------------+ | 2102 | Escrow Record structure does not conform with CSV | | | header definition. | +-------------+-----------------------------------------------------+ | 2103 | Escrow Record found missing data in required | | | field(s). | +-------------+-----------------------------------------------------+ | 2104 | Invalid domain name syntax in Escrow Record. | +-------------+-----------------------------------------------------+ | 2105 | Invalid email syntax in Escrow Record. | +-------------+-----------------------------------------------------+ | 2106 | Invalid hostname syntax in Escrow Record. | +-------------+-----------------------------------------------------+ | 2107 | Invalid date syntax in Escrow Record. | +-------------+-----------------------------------------------------+ | 2108 | Invalid phone syntax in Escrow Record. | +-------------+-----------------------------------------------------+ | 2109 | Duplicate domain or handle Escrow Record found in | | | deposit. | +-------------+-----------------------------------------------------+ | 2110 | Handle reference by Escrow Record not found. | +-------------+-----------------------------------------------------+ | 2201 | "Full" data escrow deposit expected but received | | | "Differential" instead. | +-------------+-----------------------------------------------------+ | 2202 | Data Escrow deposit date is in the future. | +-------------+-----------------------------------------------------+ | 2203 | A data escrow deposit has been already | | | successfully verified for that date. | +-------------+-----------------------------------------------------+ Table 1: Registrar Data Escrow Deposit Verification Result Codes Example of a object of a Data Escrow Agent notification corresponding to a Registrar Data Escrow deposit that was not received or could not be processed for verification: Lozano & Alvarez Expires 17 March 2023 [Page 8] Internet-Draft ICANN Registrar Interfaces September 2022 Escrow Agent Inc. 1 2017-06-17 DRFN 2017-06-10 Example of a object of a Data Escrow Agent notification corresponding to a Registrar repository Data Escrow deposit that has passed the verification process: Lozano & Alvarez Expires 17 March 2023 [Page 9] Internet-Draft ICANN Registrar Interfaces September 2022 Escrow Agent Inc. 1 2017-06-17 DVPN 2017-06-17T03:15:00.0Z 2017-06-17T05:15:00.0Z 2017-06-17 20170617001 1 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 0 2017-06-17T00:15:00.0Z FULL 2017-06-17T00:00:00Z 9999 2 6 1 Example of a object of a Data Escrow Agent notification corresponding to a Registrar repository Data Escrow deposit that has failed the verification process: Lozano & Alvarez Expires 17 March 2023 [Page 10] Internet-Draft ICANN Registrar Interfaces September 2022 Escrow Agent Inc. 1 2017-06-17 DVFN Invalid domain name syntax in Escrow Record. Handle reference by Escrow Record not found. 2017-06-17T03:15:00.0Z 2017-06-17T05:15:00.0Z 2017-06-14 20170617001 1 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 0 2017-06-17T00:15:00.0Z FULL 2017-06-17T00:00:00Z 9999 2 8 3 3. Technical details of the interfaces Content-type value in the HTTP header: * The client MUST set "text/xml" in the HTTP header Content-type when using the Data Escrow Agent Reporting and Registrar Reporting interfaces described in Section 2. After successfully receiving and processing an input, the interfaces return any of the HTTP status codes described in Section 4 of [I-D.lozano-icann-registry-interfaces]. The following sections provide the IIRDEA Result Codes that can be expected in the object from each interface: 3.1. Registrar Reporting The following table lists the result codes of the interface: Lozano & Alvarez Expires 17 March 2023 [Page 12] Internet-Draft ICANN Registrar Interfaces September 2022 +========+========================================================+ | Result | Message | | Code | | +========+========================================================+ | 1000 | No ERRORs were found and the report has been accepted | | | by ICANN. | +--------+--------------------------------------------------------+ | 2001 | The request did not validate against the schema. | +--------+--------------------------------------------------------+ | 2004 | Report for a date in the future. The and | | | date should not be in the future. | +--------+--------------------------------------------------------+ | 2005 | Version is not supported. | +--------+--------------------------------------------------------+ | 2006 | The in the element and the in the | | | URL path do not match. | +--------+--------------------------------------------------------+ | 2301 | Interface is disabled for this Registrar. | +--------+--------------------------------------------------------+ | 2302 | The and date should not be before | | | the creation date of the Registrar in the system. | +--------+--------------------------------------------------------+ | 2303 | The in the
and the in | | | the URL path do not match. | +--------+--------------------------------------------------------+ | 2304 | Report regarding an differential deposit received when | | | a full deposit was expected (). | +--------+--------------------------------------------------------+ | 2305 | attribute missing in count element provided in | | | the
. | +--------+--------------------------------------------------------+ | 2306 | Multiple count elements with the same and | | | attribute values provided in the
. | +--------+--------------------------------------------------------+ | 2307 | Missing required element in the
. | +--------+--------------------------------------------------------+ | 2312 | An invalid NR-LDH label or A-label was found or the | | | domain name syntax is invalid in the attribute. | +--------+--------------------------------------------------------+ | 2313 | INCR is not supported. | +--------+--------------------------------------------------------+ Table 2: Registrar Data Escrow Reporting Result Codes Lozano & Alvarez Expires 17 March 2023 [Page 13] Internet-Draft ICANN Registrar Interfaces September 2022 3.2. Data Escrow Agent Reporting The following table lists the result codes of the interface: +========+=============================================+ | Result | Message | | Code | | +========+=============================================+ | 1000 | No ERRORs were found and the notification | | | has been accepted by ICANN. | +--------+---------------------------------------------+ | 2001 | The request did not validate against the | | | schema. | +--------+---------------------------------------------+ | 2002 | A DVPN notification exists for that date | | | (). | +--------+---------------------------------------------+ | 2004 | Notification for a date in the future. The | | | , , and | | | date should not be in the future. | +--------+---------------------------------------------+ | 2005 | Version is not supported. | +--------+---------------------------------------------+ | 2201 | The and in the | | | notification do not match. | +--------+---------------------------------------------+ | 2203 | A Deposit Verification Pass Notice (DVPN) | | | notification was received, but the Domain | | | Name count is missing in the
. | +--------+---------------------------------------------+ | 2204 | The notification for the report "id" | | | already exists. | +--------+---------------------------------------------+ | 2207 | A DVPN or DVFN was received, but the | | | element is missing in the | | | notification. | +--------+---------------------------------------------+ | 2208 | A DRFN was received, but a element | | | exists in the notification. | +--------+---------------------------------------------+ | 2209 | and elements must not be | | | present in a DRFN. | +--------+---------------------------------------------+ | 2301 | Interface is disabled for this Registrar. | +--------+---------------------------------------------+ | 2302 | The and and | | | date should not be before the creation date | | | of the Registrar in the system. | Lozano & Alvarez Expires 17 March 2023 [Page 14] Internet-Draft ICANN Registrar Interfaces September 2022 +--------+---------------------------------------------+ | 2303 | The in the
and the | | | in the URL path do not match. | +--------+---------------------------------------------+ | 2304 | Notification regarding an differential | | | deposit received when a full deposit was | | | expected (). | +--------+---------------------------------------------+ | 2305 | attribute missing in count element | | | provided in the
. | +--------+---------------------------------------------+ | 2306 | Multiple count elements with the same | | | and attribute values provided in the | | |
. | +--------+---------------------------------------------+ | 2307 | Missing required element in the | | |
. | +--------+---------------------------------------------+ | 2309 | A DVFN was received, but the | | | element is missing in the notification. | +--------+---------------------------------------------+ | 2310 | The specified result code in the | | | element requires the "domainCount" | | | attribute to be present. | +--------+---------------------------------------------+ | 2311 | Unrecognized value in the "code" attribute | | | of the element. | +--------+---------------------------------------------+ | 2312 | An invalid NR-LDH label or A-label was | | | found or the domain name syntax is invalid | | | in the attribute. | +--------+---------------------------------------------+ | 2313 | INCR is not supported. | +--------+---------------------------------------------+ Table 3: Data Escrow Agent Reporting Result Codes 4. Monitoring Registrar reporting Registrars MAY monitor the status of the data escrow reporting notifications requirement using the following interfaces that support the GET HTTP verb. 4.1. Monitoring the reporting status of a Registrar Registrars MAY monitor the general reporting status and obtain a list of any outstanding issues using the following interface: Lozano & Alvarez Expires 17 March 2023 [Page 15] Internet-Draft ICANN Registrar Interfaces September 2022 /info/status/registrar/ Where: - MUST be substituted with the IANA ID assigned by ICANN to the Registrar being queried. This interface provides a element as defined in Section 2 of [I-D.lozano-icann-registry-interfaces] that uses the element and includes the following values: * "Registrar_Escrow_Report" : For Registrar Data Escrow Reporting as defined in Section 2.1. The "date" attribute for any reporting issue is provided in "YYYY-MM-DD" format. * "DEA_Notification" : For Data Escrow Agent Notifications as defined in Section 2.2. The "date" attribute for any reporting issue is provided in "YYYY-MM-DD" format. Example of response for a Registrar status check with no reporting issues: Lozano & Alvarez Expires 17 March 2023 [Page 16] Internet-Draft ICANN Registrar Interfaces September 2022 HTTP/1.1 200 OK Content-Type: application/xml Content-Length: 1125 9999 2017-06-10T12:00:30.101Z Daily 2017-10-15 Registrar_Escrow_Report false ok DEA_Notification true ok 2017-10-20T02:22:14.148Z Example of response for a Registrar status check with reporting issues: Lozano & Alvarez Expires 17 March 2023 [Page 17] Internet-Draft ICANN Registrar Interfaces September 2022 HTTP/1.1 200 OK Content-Type: application/xml Content-Length: 1604 9999 2017-06-10T12:00:30.101Z Daily 2017-10-08 Registrar_Escrow_Report true ok DEA_Notification true unsatisfactory 2017-10-20T02:22:14.148Z 4.2. Monitoring Registrar Data Escrow Reports Registrars MAY monitor the status of their Data Escrow reports using the following interface: /info/report/registrar-escrow-report// Where: Lozano & Alvarez Expires 17 March 2023 [Page 18] Internet-Draft ICANN Registrar Interfaces September 2022 - MUST be substituted with the IANA ID assigned by ICANN to the Registrar being queried. - MUST be substituted with the date being queried in "YYYY-MM-DD" format. For example: 2017-08-01. Possible results are: * The interface provides a HTTP/200 status code with a element in the response content as defined in Section 2 of [I-D.lozano-icann-registry-interfaces], listing each successfully received with watermark value that matches the queried date. Example of response for a Registrar Data Escrow Reporting status check: Lozano & Alvarez Expires 17 March 2023 [Page 19] Internet-Draft ICANN Registrar Interfaces September 2022 HTTP/1.1 200 OK Content-Type: application/xml Content-Length: 1194 2017-10-13T00:30:13.741Z 20171013001 1 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 0 2017-10-13T00:01:11.000Z FULL 2017-10-13T00:00:00.00Z 9999 10 1 4.3. Monitoring Registrar Data Escrow Agent Notifications Registrars and Data Escrow Agents MAY monitor the status of Data Escrow Agent Notifications using the following interface: /info/report/registrar-escrow-agent-notification// Where: - MUST be substituted with the IANA ID assigned by ICANN to the Registrar being queried. - MUST be substituted with the date being queried in "YYYY-MM-DD" format. For example: 2017-08-01. Lozano & Alvarez Expires 17 March 2023 [Page 20] Internet-Draft ICANN Registrar Interfaces September 2022 Possible results are: * The interface provides a HTTP/200 status code with a element in the response content as defined in Section 2 of [I-D.lozano-icann-registry-interfaces], listing each successfully received with a watermark value that matches the queried date. Example of a response of a Registrar Data Escrow Agent Notification status check for a date with two received notifications: HTTP/1.1 200 OK Content-Type: application/xml Content-Length: 2578 2017-10-17T23:59:59.0Z Escrow Agent Inc. 1 2017-10-17 DRFN 2017-10-14 2017-10-18T06:00:00.0Z Escrow Agent Inc. 1 2017-10-17 DVPN 2017-10-18T03:15:00.0Z 2017-10-18T05:15:00.0Z Lozano & Alvarez Expires 17 March 2023 [Page 21] Internet-Draft ICANN Registrar Interfaces September 2022 2017-10-17 20171017001 1 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 0 2017-10-17T00:15:00.0Z FULL 2017-10-17T00:00:00Z 9999 10 1 5. Internationalization Considerations The interfaces described in this document use XML, which provides native support for encoding information using the Unicode character set and its more compact representations including UTF-8. Conformant XML processors recognize both UTF-8 and UTF-16. Though XML includes provisions to identify and use other character encodings through use of an "encoding" attribute in an declaration, use of UTF-8 is RECOMMENDED. 6. IANA Considerations No actions are required from IANA. 7. Implementation Status Note to RFC Editor: Please remove this section and the reference to RFC 7942 [RFC7942] before publication. This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in RFC 7942 [RFC7942]. The description of implementations in this section is Lozano & Alvarez Expires 17 March 2023 [Page 22] Internet-Draft ICANN Registrar Interfaces September 2022 intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. According to RFC 7942 [RFC7942], "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit". 7.1. Implementation in the gTLD space Organization: ICANN Name: Registrar Data Escrow Specifications Description: Data Escrow Agents, and ICANN implement this specification. ICANN receives daily notifications from Data Escrow Agents using this specification. Level of maturity: production. Coverage: all aspects of this specification are implemented. Version compatibility: versions 00 - 04 are known to be implemented. Contact: gustavo.lozano@icann.org URL: https://www.icann.org/en/system/files/files/rde-specs- 09nov07-en.pdf 8. Security Considerations The interfaces described in this document MUST be provided using HTTPS. The recommendations in [RFC7525] MUST be implemented. 9. Change History [[RFC Editor: Please remove this section.]] Lozano & Alvarez Expires 17 March 2023 [Page 23] Internet-Draft ICANN Registrar Interfaces September 2022 9.1. Version 00 Initial version. 9.2. Version 01 * Added clarifications, list of result codes that require the "domainCount" attribute to be present, and additional examples of objects in Section 2.2. * Removed HTTP/404 from the possible results of interfaces to monitor data escrow notifications and registrar reports. 9.3. Version 02 1. Ping update. 9.4. Version 03 1. Ping update. 9.5. Version 04 1. Ping update. 9.6. Version 05 1. IANA Considerations section added. 2. Implementation section added. 3. Internationalization Considerations status section added. 4. Security section added. 5. Editorial updates. 9.7. Version 06 1. Ping update. 9.8. Version 07 1. Citations for RFCs that were recently published. Lozano & Alvarez Expires 17 March 2023 [Page 24] Internet-Draft ICANN Registrar Interfaces September 2022 9.9. Version 08 1. Ping update. 9.10. Version 09 1. Ping update. 10. References 10.1. Normative References [I-D.lozano-icann-registry-interfaces] Lozano, G. and E. Alvarez, "ICANN Registry Interfaces", Work in Progress, Internet-Draft, draft-lozano-icann- registry-interfaces-18, 13 September 2022, . [ICANN-RDE-SPEC] ICANN, "Registrar Data Escrow specifications", 9 November 2007, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [RFC8909] Lozano, G., "Registry Data Escrow Specification", RFC 8909, DOI 10.17487/RFC8909, November 2020, . [RFC9022] Lozano, G., Gould, J., and C. Thippeswamy, "Domain Name Registration Data (DNRD) Objects Mapping", RFC 9022, DOI 10.17487/RFC9022, May 2021, . Lozano & Alvarez Expires 17 March 2023 [Page 25] Internet-Draft ICANN Registrar Interfaces September 2022 [W3C.REC-xml-20081126] Bray, T., Paoli, J., Sperberg-McQueen, C. M., Maler, E., and F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth Edition) REC-xml-20081126", November 2008, . 10.2. Informative References [ICANN-RAA-2013] ICANN, "2013 Registrar Accreditation Agreement", June 2013, . [RFC5890] Klensin, J., "Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework", RFC 5890, DOI 10.17487/RFC5890, August 2010, . [RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre, "Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May 2015, . [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running Code: The Implementation Status Section", BCP 205, RFC 7942, DOI 10.17487/RFC7942, July 2016, . Authors' Addresses Gustavo Lozano ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, 90292 United States of America Phone: +1.3103015800 Email: gustavo.lozano@icann.org Eduardo Alvarez ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, 90292 United States of America Phone: +1.3103015800 Email: eduardo.alvarez@icann.org Lozano & Alvarez Expires 17 March 2023 [Page 26]