Internet Engineering Task Force G. Lozano Internet-Draft E. Alvarez Intended status: Informational ICANN Expires: August 31, 2018 February 27, 2018 ICANN Privacy and Proxy Service Provider Interfaces draft-icann-ppsp-interfaces-00 Abstract This document describes the interfaces provided by ICANN to Privacy and Proxy Service Providers and their Data Escrow Agents in order to fulfill the data escrow requirements of the Privacy and Proxy Accreditation Agreement. 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 August 31, 2018. Copyright Notice Copyright (c) 2018 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 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 August 31, 2018 [Page 1] Internet-Draft ICANN PPSP Interfaces February 2018 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 Data Escrow Notifications . . . . . . . . . . 3 2.1. PPSP Data Escrow Reporting . . . . . . . . . . . . . . . 3 2.2. Data Escrow Agent Reporting . . . . . . . . . . . . . . . 5 3. PPSP Quarterly Reporting . . . . . . . . . . . . . . . . . . 9 3.1. Per-Registrar Activity Report . . . . . . . . . . . . . . 9 3.2. Per-TLD Activity Report . . . . . . . . . . . . . . . . . 9 4. Technical details of the interfaces . . . . . . . . . . . . . 10 4.1. PPSP Data Escrow Reporting . . . . . . . . . . . . . . . 11 4.2. Data Escrow Agent Reporting . . . . . . . . . . . . . . . 12 4.3. Per-Registrar Activity Reporting . . . . . . . . . . . . 14 4.4. Per-TLD Activity Reporting . . . . . . . . . . . . . . . 15 5. Monitoring PPSP reporting . . . . . . . . . . . . . . . . . . 16 5.1. Monitoring the reporting status for a PPSP . . . . . . . 16 5.2. Monitoring the status of PPSP Escrow Reports . . . . . . 18 5.3. Monitoring the status of PPSP Data Escrow Agent Notifications . . . . . . . . . . . . . . . . . . . . . . 20 5.4. Monitoring the status of a Per-Registrar Activity Report 23 5.5. Monitoring the status of a Per-TLD Activity Report . . . 24 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 7. Security Considerations . . . . . . . . . . . . . . . . . . . 24 8. Change History . . . . . . . . . . . . . . . . . . . . . . . 25 8.1. Version 00 . . . . . . . . . . . . . . . . . . . . . . . 25 9. Normative References . . . . . . . . . . . . . . . . . . . . 25 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25 1. Introduction This document describes the technical details of the interfaces provided by the Internet Corporation for Assigned Names and Numbers (ICANN) to Privacy and Proxy Service Providers (PPSP) and their Data Escrow Agents in order to fulfill the data escrow requirements of the Privacy and Proxy Accreditation Agreement. 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 Lozano & Alvarez Expires August 31, 2018 [Page 2] Internet-Draft ICANN PPSP Interfaces February 2018 character case presented in order 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. o : The base URL used in the reporting interfaces examples must be replaced with the URL indicated by ICANN. 2. Interfaces for Data Escrow Notifications This section describes the interfaces provided by ICANN to Privacy and Proxy Service Providers and their Data Escrow Agents in order to fulfill their reporting requirements related of the Privacy and Proxy Accreditation Agreement. 2.1. PPSP Data Escrow Reporting To notify that a data escrow deposit has been submitted to a Data Escrow Agent, the ICANN-accredited Privacy and Proxy Service Provider 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 PPSP repository: o The element in the object (see, [I-D.arias-noguchi-dnrd-objects-mapping]) MUST have a value of "PPSP", and the value corresponding to the PPSP's unique ID assigned by ICANN. o A element MUST be included with the corresponding "registrarId" and "rcdn" attributes in the object to indicate the total domains in the data escrow deposit for each Registrar and each Registry Class Domain Name (e.g. .example) combination 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 Lozano & Alvarez Expires August 31, 2018 [Page 3] Internet-Draft ICANN PPSP Interfaces February 2018 "https://www.icann.org/ppsp-de-spec" 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 PPSP 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 "registrarId" or "rcdn" attributes, 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/ppsp-escrow-report// Where: * MUST be substituted by the ID assigned by ICANN to the PPSP for which the report is being provided. * MUST be substituted by 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 Privacy and Proxy Service Providers and Data Escrow Agents. Example of a object for a data escrow deposit corresponding to a PPSP repository: Lozano & Alvarez Expires August 31, 2018 [Page 4] Internet-Draft ICANN PPSP Interfaces February 2018 20171108001 1 https://www.icann.org/ppsp-de-spec 0 2017-10-05T00:15:00.0Z FULL 2017-10-05T00:00:00Z PPSP 1234 6 4 2 2.2. Data Escrow Agent Reporting Data Escrow Agents MAY deliver to ICANN a notification every time a successfully processed deposit is received from a Privacy and Proxy Service Provider, regardless of the final status of the verification process, in addition to a failure notification if a deposit is not received from a Provider on a given date, by sending to ICANN a object as defined in Section 2 of [I-D.lozano-icann-registry-interfaces], using the POST HTTP verb in the interface provided by ICANN at: /report/ppsp-escrow-agent-notification/ Where: * MUST be substituted by the ID assigned by ICANN to the PPSP for which the notification is being provided. A with DRFN (Deposit Receipt Failure Notice) status is used to notify that a PPSP has not submitted a data escrow deposit for a past date where a deposit was scheduled to be received. Lozano & Alvarez Expires August 31, 2018 [Page 5] Internet-Draft ICANN PPSP Interfaces February 2018 The value of the in the object MUST match the data escrow deposit "id". In the case of a with DVFN (Deposit Verification Failure Notice) status, the element MUST 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, where applicable. 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 Privacy and Proxy Service Provider's data escrow deposit: Lozano & Alvarez Expires August 31, 2018 [Page 6] Internet-Draft ICANN PPSP Interfaces February 2018 +-----------+-------------------------------------------------------+ | Result | Message | | Code | | +-----------+-------------------------------------------------------+ | 2001 | No signature file found for deposit file. | | 2002 | Deposit file decryption error. | | 2003 | Split deposit file numbers are not consecutive. | | 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 | Contact handle file missing in the data escrow | | | deposit. | | 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. | | 2112 | Invalid IANA Registrar Id found in Escrow Record. | | 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. | +-----------+-------------------------------------------------------+ PPSP Data Escrow Deposit Verification Result Codes Example of a object of a Data Escrow Agent notification corresponding to a PPSP repository Data Escrow Deposit: Escrow Agent Inc. Lozano & Alvarez Expires August 31, 2018 [Page 7] Internet-Draft ICANN PPSP Interfaces February 2018 1 2017-10-07 DVFN Invalid domain name syntax in Escrow Record. Invalid IANA Registrar Id found in Escrow Record. 2017-10-07T03:15:00.0Z 2017-10-07T05:15:00.0Z 2017-10-01 b4f1ca55-9e0c-4d10-be76-8c53896b4bb6 1 https://www.icann.org/ppsp-de-spec 0 2017-10-07T00:15:00.0Z FULL 2017-10-07T00:00:00Z PPSP 1234 2 8 3 Lozano & Alvarez Expires August 31, 2018 [Page 8] Internet-Draft ICANN PPSP Interfaces February 2018 3. PPSP Quarterly Reporting A set of two of reports may be sent by Privacy and Proxy Service Providers to ICANN: The Per-Registrar Activity Report and Per-TLD Activity Report, as described in the Privacy and Proxy Accreditation Agreement. This section specifies the interfaces provided by ICANN to automate the upload of these reports. 3.1. Per-Registrar Activity Report A Privacy and Proxy Service Provider MAY send the "Per-Registrar Activity Report" as a CSV report as described in the Privacy and Proxy Accreditation Agreement using the PUT HTTP verb in the interface provided by ICANN at: /report/ppsp-activity-registrar// Where: * MUST be substituted by the ID assigned by ICANN to the PPSP for which the report is being provided. * MUST be substituted by the last month of the quarter for which the report is being provided in the form of YYYY-MM. Where 'YYYY' is the year and 'MM' is the two digit month number. For example: 2018-03 3.2. Per-TLD Activity Report A Privacy and Proxy Service Provider MAY send the the "Per-TLD Activity Report" as a CSV report as described in the Privacy and Proxy Accreditation Agreement using the PUT HTTP verb in the interface provided by ICANN at: /report/ppsp-activity-tld// Where: * MUST be substituted by the ID assigned by ICANN to the PPSP for which the report is being provided. * MUST be substituted by the last month of the quarter for which the report is being provided in the form of YYYY-MM. Where 'YYYY' is the year and 'MM' is the two digit month number. For example: 2018-03 Lozano & Alvarez Expires August 31, 2018 [Page 9] Internet-Draft ICANN PPSP Interfaces February 2018 4. 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 Privacy and Proxy Service Provider Reporting interfaces described in Section 2. o The client MUST set "text/csv" in the HTTP header Content-type when using the Per-Registrar and Per-TLD Activity Report interfaces described in Section 3. The interfaces support HTTP streams only (HTTP multi-part forms are not supported). 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 August 31, 2018 [Page 10] Internet-Draft ICANN PPSP Interfaces February 2018 4.1. PPSP Data Escrow 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 PPSP. | | 2302 | The and date should not be before | | | the creation date of the PPSP in the system. | | 2303 | The PPSP 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 | Count element greater than 0 is missing the | | | or attributes in the report | | |
. | | 2306 | Multiple count elements with the same , , and | | | attribute values provided in the
. | | 2307 | element found in the
is not allowed for a | | | PPSP data escrow deposit. | | 2308 | Value for is not allowed. Expected | | | "PPSP" repository type. | +--------+----------------------------------------------------------+ Data Escrow Reporting Result Codes Lozano & Alvarez Expires August 31, 2018 [Page 11] Internet-Draft ICANN PPSP Interfaces February 2018 4.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 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 PPSP. | | 2302 | The and and date should | | | not be before the creation date of the PPSP in the | | | system. | | 2303 | The PPSP 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 | Count element greater than 0 is missing the | | | or attributes in the report | | |
. | | 2306 | Multiple count elements with the same , , and | | | attribute values provided in the
. | | 2307 | element found in the
is not allowed for a | | | PPSP data escrow deposit. | | 2308 | Value for is not allowed. Expected | | | "PPSP" repository type. | | 2309 | A DVFN was received, but the element is | | | missing in the notification. | | 2310 | The specified result code in the element | Lozano & Alvarez Expires August 31, 2018 [Page 12] Internet-Draft ICANN PPSP Interfaces February 2018 | | requires the "domainCount" attribute to be present. | | 2311 | Unrecognized value in the "code" attribute of the | | | element. | +--------+----------------------------------------------------------+ Data Escrow Reporting Result Codes Lozano & Alvarez Expires August 31, 2018 [Page 13] Internet-Draft ICANN PPSP Interfaces February 2018 4.3. Per-Registrar Activity 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 structure of the report is invalid. | | 2002 | A report for that month already exists, the cut-off | | | date already passed. | | 2003 | Negative numeric value present in the report. | | 2004 | Report for a month in the future. | | 2007 | Interface is disabled for this PPSP. | | 2008 | Reported month before the creation date of the PPSP in | | | the system. | | 2101 | Incorrect totals present in the report. | | 2102 | A non ICANN-accredited registrar ID is present in the | | | report. | | 2103 | Values found in the second field of the totals line. | | 2105 | The report is not encoded in UTF-8. Note: reports | | | encoded in US-ASCII are accepted. | +----------+--------------------------------------------------------+ Per-Registrar Activity Report Result Codes Lozano & Alvarez Expires August 31, 2018 [Page 14] Internet-Draft ICANN PPSP Interfaces February 2018 4.4. Per-TLD Activity 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 structure of the report is invalid. | | 2002 | A report for that month already exists, the cut-off | | | date already passed. | | 2003 | Negative numeric value present in the report. | | 2004 | Report for a month in the future. | | 2007 | Interface is disabled for this PPSP. | | 2008 | Reported month before the creation date of the PPSP in | | | the system. | | 2101 | Incorrect totals present in the report. | | 2105 | The report is not encoded in UTF-8. Note: reports | | | encoded in US-ASCII are accepted. | +----------+--------------------------------------------------------+ Per-TLD Activity Report Result Codes Lozano & Alvarez Expires August 31, 2018 [Page 15] Internet-Draft ICANN PPSP Interfaces February 2018 5. Monitoring PPSP reporting Privacy and Proxy Service Providers MAY monitor the reporting status using the following interfaces that support the GET HTTP verb: 5.1. Monitoring the reporting status for a PPSP Privacy and Proxy Service Providers MAY monitor the general reporting status and get a list of any outstanding issues using the following interface: /info/status/ppsp/ Where: * MUST be substituted by the ID assigned by ICANN to the PPSP being queried. This interface provides a element as defined in Section 2 of [I-D.lozano-icann-registry-interfaces] and includes the following report types: o "PPSP_Escrow_Report" : For PPSP Data Escrow Reporting as defined in Section 2.1. The "date" attribute for any reporting issue is provided in "YYYY-MM-DD" format. o "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. o "PPSP_Per_Registrar_Activity_Report" : For PPSP Per-Registrar Activity reporting as defined in Section 3.1. The "date" attribute for any reporting issue is provided in "YYYY-MM" format. o "PPSP_Per_TLD_Activity_Report" : For PPSP Per-TLD Activity reporting as defined in Section 3.2. The "date" attribute for any reporting issue is provided in "YYYY-MM" format. Example of response for a PPSP status check with no reporting issues: Lozano & Alvarez Expires August 31, 2018 [Page 16] Internet-Draft ICANN PPSP Interfaces February 2018 PPSP 1 2017-06-10T12:00:30.101Z Daily 2017-10-21 PPSP_Escrow_Report true ok DEA_Notification true ok PPSP_Per_Registrar_Activity_Report true ok PPSP_Per_TLD_Activity_Report true ok 2017-10-23T02:22:14.148Z Example of response for a PPSP status check with reporting issues: PPSP 1 2017-06-10T12:00:30.101Z Lozano & Alvarez Expires August 31, 2018 [Page 17] Internet-Draft ICANN PPSP Interfaces February 2018 Daily 2017-10-08 PPSP_Escrow_Report true ok DEA_Notification true unsatisfactory PPSP_Per_Registrar_Activity_Report true unsatisfactory PPSP_Per_TLD_Activity_Report true ok 2017-10-23T02:22:14.148Z 5.2. Monitoring the status of PPSP Escrow Reports Privacy and Proxy Service Provoiders MAY monitor the status of the latest Data Escrow notification received using the following interface: Lozano & Alvarez Expires August 31, 2018 [Page 18] Internet-Draft ICANN PPSP Interfaces February 2018 /info/report/ppsp-escrow-report// Where: * MUST be substituted by the ID assigned by ICANN to the PPSP for which the notification is being queried. * MUST be substituted by the day being queried in "YYYY- MM-DD" format. For example: 2017-08-01 Possible results are: 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 element is provided 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 PPSP Data Escrow Reporting status check: Lozano & Alvarez Expires August 31, 2018 [Page 19] Internet-Draft ICANN PPSP Interfaces February 2018 2017-10-13T00:30:13.741Z 20171013001 1 https://www.icann.org/ppsp-de-spec 0 2017-10-13T00:01:11.0Z FULL 2017-10-13T00:00:00.0Z PPSP 1 2 8 3 5.3. Monitoring the status of PPSP Data Escrow Agent Notifications Privacy and Proxy Service Providers and Data Escrow Agents MAY monitor the status of Data Escrow Agent Notifications using the following interface: /info/report/ppsp-escrow-agent-notification// Where: * MUST be substituted by the ID assigned by ICANN to the PPSP for which the notification is being queried. Lozano & Alvarez Expires August 31, 2018 [Page 20] Internet-Draft ICANN PPSP Interfaces February 2018 * MUST be substituted by the day being queried in "YYYY- MM-DD" format. For example: 2017-08-01 Possible results are: 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 element is provided 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 PPSP Data Escrow Agent Notification status check for a date with 2 received notifications: 2017-10-13T01:30:13.741Z Escrow Agent Inc. 1 2017-10-13 DVFN Invalid domain name syntax in Escrow Record. Handle reference by Escrow Record not found. 2017-10-13T00:15:00.0Z Lozano & Alvarez Expires August 31, 2018 [Page 21] Internet-Draft ICANN PPSP Interfaces February 2018 2017-10-13T01:15:00.0Z 2017-10-10 20171013001 1 https://www.icann.org/ppsp-de-spec 0 2017-10-13T00:05:00.0Z FULL 2017-10-13T00:00:00Z PPSP 1 2 8 3 2017-10-14T01:00:00.0Z Escrow Agent Inc. 1 2017-10-13 DVPN 2017-10-13T10:00:00.0Z 2017-10-13T10:15:00.0Z 2017-10-17 Lozano & Alvarez Expires August 31, 2018 [Page 22] Internet-Draft ICANN PPSP Interfaces February 2018 20171013002 1 https://www.icann.org/ppsp-de-spec 1 2017-10-13T09:15:00.0Z FULL 2017-10-13T00:00:00Z PPSP 1 2 8 3 5.4. Monitoring the status of a Per-Registrar Activity Report Privacy and Proxy Service Providers MAY monitor the status of Per- Registrar Activity Report using the following interface that supports the HEAD HTTP verb: /info/report/ppsp-activity-registrar// Where: * MUST be substituted by the ID assigned by ICANN to the PPSP for which the report is being provided. * MUST be substituted by the last month of the quarter being queried in "YYYY-MM" format. For example: 2018-03. Lozano & Alvarez Expires August 31, 2018 [Page 23] Internet-Draft ICANN PPSP Interfaces February 2018 Possible results are: * The interface provides a HTTP/200 status code, if a syntactically valid Per-Registrar Activity report was received for the queried month. * The interface provides a HTTP/404 status code, if a syntactically valid Per-Registrar Activity report has not been received for the queried month. 5.5. Monitoring the status of a Per-TLD Activity Report Privacy and Proxy Service Providers MAY monitor the status of Per-TLD Activity Report using the following interface that supports the HEAD HTTP verb: /info/report/ppsp-activity-tld// Where: * MUST be substituted by the ID assigned by ICANN to the PPSP for which the report is being provided. * MUST be substituted by the last month of the quarter being queried in "YYYY-MM" format. For example: 2018-03. Possible results are: * The interface provides a HTTP/200 status code, if a syntactically valid Per-TLD Activity report was received for the queried month. * The interface provides a HTTP/404 status code, if a syntactically valid Per-TLD Activity report has not been received for the queried month. 6. IANA Considerations TODO 7. Security Considerations TODO Lozano & Alvarez Expires August 31, 2018 [Page 24] Internet-Draft ICANN PPSP Interfaces February 2018 8. Change History 8.1. Version 00 Initial version. 9. Normative References [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.lozano-icann-registry-interfaces] Lozano, G., "ICANN Registry Interfaces", draft-lozano- icann-registry-interfaces-07 (work in progress), January 2015. [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, . Authors' Addresses Gustavo Lozano ICANN 12025 Waterfront Drive, Suite 300 Los Angeles 90292 US Phone: +1.3103015800 Email: gustavo.lozano@icann.org Lozano & Alvarez Expires August 31, 2018 [Page 25] Internet-Draft ICANN PPSP Interfaces February 2018 Eduardo Alvarez ICANN 12025 Waterfront Drive, Suite 300 Los Angeles 90292 US Phone: +1.3103015800 Email: eduardo.alvarez@icann.org Lozano & Alvarez Expires August 31, 2018 [Page 26]