Internet Engineering Task Force G. Lozano Internet-Draft E. Alvarez Intended status: Informational ICANN Expires: February 16, 2018 August 15, 2017 ICANN Registrar Interfaces draft-icann-registrar-interfaces-00 Abstract This document describes the interfaces provided by ICANN to Registrars and Data Escrow Agents in order to fulfill the data escrow requirements of the Registrar Accreditation Agreement [ICANN-RAA-2013] and the Registrar Data Escrow Specifications [ICANN-RDE-SPEC]. 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 http://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 February 16, 2018. Copyright Notice Copyright (c) 2017 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 (http://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 Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Lozano & Alvarez Expires February 16, 2018 [Page 1] Internet-Draft ICANN Registrar Interfaces August 2017 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 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 . . . . . . . . . . . . . . . . . . . 3 2.2. Data Escrow Agent Reporting . . . . . . . . . . . . . . . 6 3. Technical details of the interfaces . . . . . . . . . . . . . 10 3.1. Registrar Reporting . . . . . . . . . . . . . . . . . . . 11 3.2. Data Escrow Agent Reporting . . . . . . . . . . . . . . . 12 4. Monitoring the status of Registrar Data Escrow . . . . . . . 13 4.1. Monitor a Registrar status . . . . . . . . . . . . . . . 13 4.2. Monitoring Registrar Data Escrow Reports . . . . . . . . 16 4.3. Monitoring Registrar Data Escrow Agent Notifications . . 18 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 6. Security Considerations . . . . . . . . . . . . . . . . . . . 21 7. Change History . . . . . . . . . . . . . . . . . . . . . . . 21 7.1. Version 00 . . . . . . . . . . . . . . . . . . . . . . . 21 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 21 8.1. Normative References . . . . . . . . . . . . . . . . . . 21 8.2. Informative References . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 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 in order to fulfill the data escrow requirements of the Registrar Accreditation Agreement [ICANN-RAA-2013] and the Registrar Data Escrow Specifications [ICANN-RDE-SPEC]. 1.1. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented in order to develop a conforming implementation. Lozano & Alvarez Expires February 16, 2018 [Page 2] Internet-Draft ICANN Registrar Interfaces August 2017 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. o : The base URL used in the reporting interfaces examples must be replaced with the URL indicated by ICANN. o This document uses the term of "Differential" deposit as defined in the Registry Data Escrow Specification (see, [I-D.arias-noguchi-registry-data-escrow]), while the Registrar Data Escrow Specifications [ICANN-RDE-SPEC] refers to the same concept as "Incremental" deposit. 2. Interfaces for Registrar Data Escrow Notifications This section describes the interfaces provided by ICANN to the Registrars and Data Escrow Agents in order to fulfill their reporting requirements related to Registrar Data Escrow Specifications [ICANN-RDE-SPEC]. 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: o The element in the object (see, [I-D.arias-noguchi-dnrd-objects-mapping]) MUST have a value of "Registrar", and the value corresponding to the IANA Registrar ID assigned by ICANN. o 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 Lozano & Alvarez Expires February 16, 2018 [Page 3] Internet-Draft ICANN Registrar Interfaces August 2017 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". o 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 this report, which MUST be the same as the "id" attribute from the . 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: Lozano & Alvarez Expires February 16, 2018 [Page 4] Internet-Draft ICANN Registrar Interfaces August 2017 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 Registrar 9999 2 8 3 Example of a object for an empty data escrow deposit corresponding to a Registrar repository: Lozano & Alvarez Expires February 16, 2018 [Page 5] Internet-Draft ICANN Registrar Interfaces August 2017 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 Registrar 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 successfully processed for verification for a past date where a deposit was scheduled to be received from the Registrar. Lozano & Alvarez Expires February 16, 2018 [Page 6] Internet-Draft ICANN Registrar Interfaces August 2017 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 should be provided in the of the object for the notification 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 the same domain escrow record (e.g. the administrative, technical and billing contact contain 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 that a Data Escrow Agent MAY use to report verification issues for a Registrar data escrow deposit: Lozano & Alvarez Expires February 16, 2018 [Page 7] Internet-Draft ICANN Registrar Interfaces August 2017 +-----------+-------------------------------------------------------+ | Result | Message | | Code | | +-----------+-------------------------------------------------------+ | 2001 | No corresponding hash file found for deposit file. | | 2002 | Hash does not match 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 maximum allowed | | | size. | | 2008 | Data escrow deposit file exceeds maximum allowed | | | number of lines. | | 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. | +-----------+-------------------------------------------------------+ Registrar Data Escrow Deposit Verification Result Codes Example of a object of a Data Escrow Agent notification corresponding to a Registrar repository Data Escrow Deposit: Escrow Agent Inc. 1 Lozano & Alvarez Expires February 16, 2018 [Page 8] Internet-Draft ICANN Registrar Interfaces August 2017 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 Registrar 9999 2 8 3 Lozano & Alvarez Expires February 16, 2018 [Page 9] Internet-Draft ICANN Registrar Interfaces August 2017 3. Technical details of the interfaces Content-type value in the HTTP header: o 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: Lozano & Alvarez Expires February 16, 2018 [Page 10] Internet-Draft ICANN Registrar Interfaces August 2017 3.1. Registrar Reporting The following table lists the result codes of the interface: +---------+---------------------------------------------------------+ | Result | Message | | Code | | +---------+---------------------------------------------------------+ | 1000 | No ERRORs were found and the report has been accepted | | | by ICANN. | | 2001 | The report 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 Registrar repository 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 | element found in the
is not allowed for | | | a Registrar data escrow deposit. | | 2308 | Value for is not allowed. Expected | | | "Registrar" repository type. | +---------+---------------------------------------------------------+ Registrar Data Escrow Reporting Result Codes Lozano & Alvarez Expires February 16, 2018 [Page 11] Internet-Draft ICANN Registrar Interfaces August 2017 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 notification did not validate against the schema. | | 2002 | A DVPN notification exists for that date (). | | 2004 | Notification for a date in the future. The and | | | 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. | | 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. | | 2303 | The Registrar repository 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 | element found in the
is not allowed for a | | | Registrar data escrow deposit. | | 2308 | Value for is not allowed. Expected | | | "Registrar" repository type. | +--------+----------------------------------------------------------+ Data Escrow Agent Reporting Result Codes Lozano & Alvarez Expires February 16, 2018 [Page 12] Internet-Draft ICANN Registrar Interfaces August 2017 4. Monitoring the status of Registrar Data Escrow Registrars MAY monitor the status of the data escrow reporting notifications requirement using the following interfaces that support the GET HTTP verb. The responses provided by the interfaces described below are in JSON format as described in [RFC7159]. 4.1. Monitor a Registrar status Registrars MAY monitor the general reporting status and obtain a list of any outstanding issues using the following interface: /info/status/registrar/ Where: * MUST be substituted with the IANA ID assigned by ICANN to the Registrar being queried. This interface provides a response in JSON format with the following elements: o "registrar" : a JSON object that includes the following elements related to the queried Registrar. * "ianaId" : a string value with the IANA ID assigned by ICANN to the Registrar. * "creationDate" : a string value with the date and time in which the Registrar was created in the system. * "depositSchedule" : a string value indicating the current Data Escrow Deposit schedule, as defined in the Registrar Data Escrow Specifications [ICANN-RDE-SPEC]. Possible values are "None", "Weekly", and "Daily". * "lastFullDate" : a string value indicating the date of the Timeline Watermark ( element) of the most recent FULL deposit that was successfully validated by the Data Escrow Agent. o "reports" : a JSON array of JSON objects corresponding to each report type for the Registrar. Each JSON object includes the following elements: Lozano & Alvarez Expires February 16, 2018 [Page 13] Internet-Draft ICANN Registrar Interfaces August 2017 * "type" : a string value indicating the report type to which the information provided pertains. Possible values are "Dea" and "Registrar". * "enabled" : a boolean value indicating if the report type is enabled for the Registrar. * "status" : a string value indicating the reporting status. A value of "ok" indicates there are no reporting issues, otherwise the value of "unsatisfactory" is shown. * "issues" : an OPTIONAL JSON array comprised of string elements. The "issues" element is included only when the "status" element has a value of "unsatisfactory", and includes an element for each date with a reporting problem found in the corresponding report type. The name of each string element in the "issues" array is the report date in "YYYY-MM-DD" format. The possible values to describe each problem are: + "Missing_Deposit_Full": If the latest notification received from the Data Escrow Agent for the date indicates that a scheduled "Full" deposit was not submitted by the Registrar. + "Missing_Deposit_Diff": If the latest notification received from the Data Escrow Agent for the date indicates that a scheduled "Differential" deposit was not submitted by the Registrar. + "Invalid_Deposit_Full": If the latest notification received from the Data Escrow Agent for the date indicates that a "Full" deposit was submitted to the Data Escrow Agent by the Registrar, but failed the verification process. + "Invalid_Deposit_Diff": If the latest notification received from the Data Escrow Agent for the date indicates that a "Differential" deposit was submitted to the Data Escrow Agent by the Registrar, but failed the verification process. + "No_Report_Received" If no report has been received for the date. o "timestamp" to indicate the date and time in which the response was created. Example of response for a Registrar status check with no reporting issues: Lozano & Alvarez Expires February 16, 2018 [Page 14] Internet-Draft ICANN Registrar Interfaces August 2017 { "registrar" : { "ianaId" : "1", "creationDate" : "2017-10-10T12:22:14.148Z", "depositSchedule" : "Weekly", "lastFullDate" : "2017-09-10" }, "reports" : [ { "type" : "Registrar", "enabled" : false, "status" : "ok" }, { "type" : "Dea", "enabled" : true, "status" : "ok" } ], "timestamp" : "2017-10-13T02:22:14.148Z" } Example of response for a Registrar status check with reporting issues: Lozano & Alvarez Expires February 16, 2018 [Page 15] Internet-Draft ICANN Registrar Interfaces August 2017 { "registrar" : { "ianaId" : "1", "creationDate" : "2017-06-10T12:00:30.101Z", "depositSchedule" : "Daily", "lastFullDate" : "2017-08-10" }, "reports" : [ { "type" : "Registrar", "enabled" : true, "status" : "unsatisfactory", "issues" : { "2017-10-15" : "No_Report_Received", "2017-10-16" : "No_Report_Received" } }, { "type" : "Dea", "enabled" : true, "status" : "unsatisfactory", "issues" : { "2017-10-14" : "Invalid_Deposit_Diff", "2017-10-15" : "Missing_Deposit_Full", "2017-10-16" : "Missing_Deposit_Diff", "2017-10-17" : "No_Report_Received" } } ], "timestamp" : "2017-10-23T02: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: * 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: Lozano & Alvarez Expires February 16, 2018 [Page 16] Internet-Draft ICANN Registrar Interfaces August 2017 o The interface provides a HTTP/404 status code, if a syntactically valid data escrow report has not been received for the queried date. o The interface provides a HTTP/200 status code, if a syntactically valid data escrow report was received for the queried date. An array of JSON objects for the reports received with watermark value that matches the queried date will be included in the response content. Each JSON object includes the following elements: "received" : a string value to indicate the date and time in which the report was received. "report" : a JSON object with the corresponding elements as defined in Section 2. + "id" : a string value with the report ID. + "rydeSpecEscrow" : a string value. + "resend" : a number value. + "created" : a string value. + "kind" : a string value. + "watermark" : a string value. + "counts" : a JSON array with a JSON object for each element included in the received report. The "uri" and "rcdn" attributes are shown as child elements. "domainCount" : a number value indicating the sum of the elements for domain name objects included in the report. Example of response for a Registrar Data Escrow Reporting status check: Lozano & Alvarez Expires February 16, 2018 [Page 17] Internet-Draft ICANN Registrar Interfaces August 2017 [ { "received" : "2017-10-13T00:30:13.741Z", "report" : { "id" : "123456", "rydeSpecEscrow" : "https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf", "resend" : 0, "created" : "2017-10-13T00:01:11.000Z", "kind" : "Full", "watermark" : "2017-10-13T00:00:00.000Z", "counts" : [ { "uri" : "urn:ietf:params:xml:ns:rdeDomain-1.0", "rcdn" : "example", "count" : 2 }, { "uri" : "urn:ietf:params:xml:ns:rdeDomain-1.0", "rcdn" : "test", "count" : 8 }, { "uri" : "urn:ietf:params:xml:ns:rdeDomain-1.0", "rcdn" : "xn--nqvo76h", "count" : 3 } ], "domainCount" : 13 } } ] 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 Possible results are: Lozano & Alvarez Expires February 16, 2018 [Page 18] Internet-Draft ICANN Registrar Interfaces August 2017 o The interface provides a HTTP/404 status code, if a syntactically valid data escrow notification has not been received for the queried date. o The interface provides a HTTP/200 status code, if a syntactically valid data escrow notification was received for the queried date. An array of JSON objects for the notifications received with a value that matches the queried date will be included in the response content. Each JSON object includes the following elements: "received" : a string value to indicate the date and time in which the report was received. "notification" : a JSON object with the corresponding elements as defined in Section 2. + "repDate" : a string value with the report ID. + "status" : a string value. + "results" : a OPTIONAL JSON array with a JSON object for each element included in the received report. The "code" and "domainCount" attributes are shown as child elements. + "deaName" : a string value. + "reDate" : a string value. + "vaDate" : a string value. + "lastFullDate" : a string value. + "report" : a OPTIONAL JSON object as defined in Section 4.2. "domainCount" : a number value indicating the sum of the elements for domain name objects included in the report. Example of a response of a Registrar Data Escrow Agent Notification status check for a date with 2 received notifications: [ { "received" : "2017-10-13T01:30:13.741Z", "notification" : { "repDate" : "2017-10-13", Lozano & Alvarez Expires February 16, 2018 [Page 19] Internet-Draft ICANN Registrar Interfaces August 2017 "status" : "DVFN", "results" : [ { "code" : 2104, "domainCount" : 2, "msg" : "Invalid domain name syntax in Escrow Record." }, { "code" : 2110, "domainCount" : 1, "msg" : "Handle reference by Escrow Record not found." } ], "deaName" : "Escrow Agent Inc.", "reDate" : "2017-10-13T00:00:12.000Z", "vaDate" : "2017-10-13T01:30:01.180Z", "lastFullDate" : "2017-10-06", "report" : { "id" : "123456", "rydeSpecEscrow" : "https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf", "resend" : 0, "created" : "2017-10-13T00:01:11.000Z", "kind" : "Full", "watermark" : "2017-10-13T00:00:00.000Z", "counts" : [ { "uri" : "urn:ietf:params:xml:ns:rdeDomain-1.0", "rcdn" : "example", "count" : 2 }, { "uri" : "urn:ietf:params:xml:ns:rdeDomain-1.0", "rcdn" : "test", "count" : 8 }, { "uri" : "urn:ietf:params:xml:ns:rdeDomain-1.0", "rcdn" : "xn--nqvo76h", "count" : 3 } ], "domainCount" : 13 } } }, { "received" : "2017-10-13T03:57:04.343Z", "notification" : { "repDate" : "2017-10-13", "status" : "DVPN", "deaName" : "Escrow Agent Inc.", "reDate" : "2017-10-13T02:30:12.000Z", "vaDate" : "2017-10-13T03:40:01.180Z", "lastFullDate" : "2017-10-13", "report" : { Lozano & Alvarez Expires February 16, 2018 [Page 20] Internet-Draft ICANN Registrar Interfaces August 2017 "id" : "123457", "rydeSpecEscrow" : "https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf", "resend" : 1, "created" : "2017-10-13T00:01:11.000Z", "kind" : "Full", "watermark" : "2017-10-13T00:00:00.000Z", "counts" : [ { "uri" : "urn:ietf:params:xml:ns:rdeDomain-1.0", "rcdn" : "example", "count" : 2 }, { "uri" : "urn:ietf:params:xml:ns:rdeDomain-1.0", "rcdn" : "test", "count" : 8 }, { "uri" : "urn:ietf:params:xml:ns:rdeDomain-1.0", "rcdn" : "xn--nqvo76h", "count" : 3 } ], "domainCount" : 13 } } }] 5. IANA Considerations TODO 6. Security Considerations TODO 7. Change History 7.1. Version 00 Initial version. 8. References 8.1. Normative References Lozano & Alvarez Expires February 16, 2018 [Page 21] Internet-Draft ICANN Registrar Interfaces August 2017 [I-D.arias-noguchi-dnrd-objects-mapping] Lozano, G., Gould, J., and C. Thippeswamy, "Domain Name Registration Data (DNRD) Objects Mapping", draft-arias- noguchi-dnrd-objects-mapping-06 (work in progress), June 2017. [I-D.arias-noguchi-registry-data-escrow] Lozano, G., "Registry Data Escrow Specification", draft- arias-noguchi-registry-data-escrow-08 (work in progress), June 2017. [I-D.lozano-icann-registry-interfaces] Lozano, G., "ICANN Registry Interfaces", draft-lozano- icann-registry-interfaces-07 (work in progress), January 2015. [ICANN-RDE-SPEC] ICANN, "Registrar Data Escrow specifications", Nov 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, . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, . [RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March 2014, . 8.2. Informative References [ICANN-RAA-2013] ICANN, "2013 Registrar Accreditation Agreement", Jun 2013, . Lozano & Alvarez Expires February 16, 2018 [Page 22] Internet-Draft ICANN Registrar Interfaces August 2017 Authors' Addresses Gustavo Lozano ICANN 12025 Waterfront Drive, Suite 300 Los Angeles 90292 US Phone: +1.3103015800 Email: gustavo.lozano@icann.org Eduardo Alvarez ICANN 12025 Waterfront Drive, Suite 300 Los Angeles 90292 US Phone: +1.3103015800 Email: eduardo.alvarez@icann.org Lozano & Alvarez Expires February 16, 2018 [Page 23]