ICANN Compliance use case
One of the use cases in Mark's list that we never got to was that of ICANN Contractual Compliance (CC). I would like to propose that we include this in our final report. The rationale is as follows: - provision of current data to ICANN is a contractual requirement - automated availability of such data will streamline and speed up ICANN CC operations and will reduce the load on CPs. To be specific, I am proposing that: Requests for redacted RDS data fields from ICANN Contractual Compliance, made in support of investigations associated with compliance issues, be fully automated within the SSAD. As far as I understand, CP are contractually obligated to respond to such requests and therefore the automation does not expose them to any additional risk. ICANN CC would of course be bound to only make such requests in support of investigations and are bound to treat the data just as they would if they had received it via today's manual channels. Alan
+1 Alan. As additional value, this evidences controllership by ICANN, which should diminish CP controllership and associated liability. Brian J. King Director of Internet Policy and Industry Affairs T +1 443 761 3726 markmonitor.com MarkMonitor Protecting companies and consumers in a digital world -----Original Message----- From: Gnso-epdp-team <gnso-epdp-team-bounces@icann.org> On Behalf Of Alan Greenberg Sent: Wednesday, April 8, 2020 11:54 AM To: EPDP <gnso-epdp-team@icann.org> Subject: [Gnso-epdp-team] ICANN Compliance use case One of the use cases in Mark's list that we never got to was that of ICANN Contractual Compliance (CC). I would like to propose that we include this in our final report. The rationale is as follows: - provision of current data to ICANN is a contractual requirement - automated availability of such data will streamline and speed up ICANN CC operations and will reduce the load on CPs. To be specific, I am proposing that: Requests for redacted RDS data fields from ICANN Contractual Compliance, made in support of investigations associated with compliance issues, be fully automated within the SSAD. As far as I understand, CP are contractually obligated to respond to such requests and therefore the automation does not expose them to any additional risk. ICANN CC would of course be bound to only make such requests in support of investigations and are bound to treat the data just as they would if they had received it via today's manual channels. Alan _______________________________________________ Gnso-epdp-team mailing list Gnso-epdp-team@icann.org https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_li... _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_p... ) and the website Terms of Service (https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_t... ). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
I disagree. This would fall under the ICANN purpose and I can see dozens of reasons why this cannot be automated. As you rightly stated, we never discussed it and therefore it is not fit for inclusion in our report. Compliance also has a record of asking for more than they need. -- Volker A. Greimann General Counsel and Policy Manager *KEY-SYSTEMS GMBH* T: +49 6894 9396901 M: +49 6894 9396851 F: +49 6894 9396851 W: www.key-systems.net Key-Systems GmbH is a company registered at the local court of Saarbruecken, Germany with the registration no. HR B 18835 CEO: Oliver Fries and Robert Birkner Part of the CentralNic Group PLC (LON: CNIC) a company registered in England and Wales with company number 8576358. On Wed, Apr 8, 2020 at 5:56 PM Alan Greenberg <alan.greenberg@mcgill.ca> wrote:
One of the use cases in Mark's list that we never got to was that of ICANN Contractual Compliance (CC).
I would like to propose that we include this in our final report.
The rationale is as follows:
- provision of current data to ICANN is a contractual requirement - automated availability of such data will streamline and speed up ICANN CC operations and will reduce the load on CPs.
To be specific, I am proposing that:
Requests for redacted RDS data fields from ICANN Contractual Compliance, made in support of investigations associated with compliance issues, be fully automated within the SSAD.
As far as I understand, CP are contractually obligated to respond to such requests and therefore the automation does not expose them to any additional risk. ICANN CC would of course be bound to only make such requests in support of investigations and are bound to treat the data just as they would if they had received it via today's manual channels.
Alan
_______________________________________________ Gnso-epdp-team mailing list Gnso-epdp-team@icann.org https://mm.icann.org/mailman/listinfo/gnso-epdp-team _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
participants (3)
-
Alan Greenberg -
King, Brian -
Volker Greimann