Re: [GNSO-EPDPP2-SmallTeam] RDRS Data Dictionary
Dear Small Team members, Marc was kind enough to inform me of a clerical error in the Metrics tab, where lines 14 and 15 were duplicative. I have removed the duplicated line item (line 15) and added the cut off sentence in line 14. I have attached the revised document as V1.1. I would also like to add that this document is subject to change, as the system development progresses. We do not envision major changes, but there may be minor adjustments in the future. Regards, Yuko From: GNSO-EPDPP2-SmallTeam <gnso-epdpp2-smallteam-bounces@icann.org> on behalf of Yuko Yokoyama <yuko.yokoyama@icann.org> Date: Wednesday, April 19, 2023 at 12:02 PM To: "gnso-epdpp2-smallteam@icann.org" <gnso-epdpp2-smallteam@icann.org> Subject: [GNSO-EPDPP2-SmallTeam] RDRS Data Dictionary Dear Small Team members, Please see attached ICANN org’s data dictionary for the Registration Data Request Service. This document provides all the data fields captured in the system from both requestor and registrar sides, in a more digestible manner than the ones in the Design Paper<https://www.icann.org/en/system/files/files/whois-disclosure-system-design-p...>. * Tab 1: All the data fields captured in the requestor side of the System * Tab 2: All the data fields captured in the registrar side of the System * Tab 3: Reporting criteria specified in the Addendum [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...> and whether those are reportable Please note, this document is being shared for the purpose of transparency and to showcase that the reporting criteria that are specified in the Addendum can be achieved with the data elements being collected. Additionally, our aim is that this document can aid in the Small Team’s discussion should it wish to add additional reporting criteria. We would like to add that ICANN org will not share any raw data collected through the System with external parties outside the System. While we understand the importance of transparency and accountability, we also want to ensure that ICANN org respects the privacy and the confidentiality of the requests logged through the system. The monthly reports will provide the necessary metrics as detailed in the Addendum, along with any other metrics deemed necessary by the Small Team to the extent that the data is available in a systematic manner, with the metrics being based on numerical and usage data. It should be noted that certain data elements listed in the data dictionary, for example, names of requestors, evidence and attachments, will not be analyzed or used as metrics for any other purpose that would go beyond gathering usage data. ICANN org ensured that the principles of privacy-by-design are embedded in the System’s design and development from its inception. Principles such as role-based data access limitation, data minimization, and data retention, were carefully considered and the publication of raw data would violate these principles. It is also important to remember that the purpose of this proof-of-concept system is not to perform contextual or content analysis, for example, evaluating the legitimacy of registrars’ disclosure decisions or analyzing outcome trends. We want to emphasize that GNSO Council's request and the ICANN Board's direction is to implement a cost-effective system that will simplify the process for submitting and receiving requests for nonpublic gTLD registration data for both the requestors and registrars and to report on usage of this system to help inform the Council–Board consultations on the next steps for the SSAD recommendations. Regards, Yuko Yokoyama Program Director Strategic Initiatives, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +1 310 578 8693 Mobile: +1 310 745 1517 E-mail: yuko.yokoyama@icann.org<mailto:yuko.yokoyama@icann.org> www.icann.org<http://www.icann.org/>
Hi, Thanks for sending this out, Yuko! I think we had discussed adding two reporting points (email thread subject “RDRS (née WDS) Reporting Points”): - Number of Requests by Requestor (may be pseudonymized/anonymized if needed) - Denial rate by reason type It looks like these didn’t make it into the Success Criteria or spreadsheet, did we decide not to do them after all and I missed it? Thanks. -- Sarah Wyld, CIPP/E Policy & Privacy Manager Pronouns: she/they swyld@tucows.com From: Yuko Yokoyama Sent: April 19, 2023 3:28 PM To: gnso-epdpp2-smallteam@icann.org Subject: Re: [GNSO-EPDPP2-SmallTeam] RDRS Data Dictionary Dear Small Team members, Marc was kind enough to inform me of a clerical error in the Metrics tab, where lines 14 and 15 were duplicative. I have removed the duplicated line item (line 15) and added the cut off sentence in line 14. I have attached the revised document as V1.1. I would also like to add that this document is subject to change, as the system development progresses. We do not envision major changes, but there may be minor adjustments in the future. Regards, Yuko From: GNSO-EPDPP2-SmallTeam <gnso-epdpp2-smallteam-bounces@icann.org> on behalf of Yuko Yokoyama <yuko.yokoyama@icann.org> Date: Wednesday, April 19, 2023 at 12:02 PM To: "gnso-epdpp2-smallteam@icann.org" <gnso-epdpp2-smallteam@icann.org> Subject: [GNSO-EPDPP2-SmallTeam] RDRS Data Dictionary Dear Small Team members, Please see attached ICANN org’s data dictionary for the Registration Data Request Service. This document provides all the data fields captured in the system from both requestor and registrar sides, in a more digestible manner than the ones in the Design Paper. • Tab 1: All the data fields captured in the requestor side of the System • Tab 2: All the data fields captured in the registrar side of the System • Tab 3: Reporting criteria specified in the Addendum [gnso.icann.org] and whether those are reportable Please note, this document is being shared for the purpose of transparency and to showcase that the reporting criteria that are specified in the Addendum can be achieved with the data elements being collected. Additionally, our aim is that this document can aid in the Small Team’s discussion should it wish to add additional reporting criteria. We would like to add that ICANN org will not share any raw data collected through the System with external parties outside the System. While we understand the importance of transparency and accountability, we also want to ensure that ICANN org respects the privacy and the confidentiality of the requests logged through the system. The monthly reports will provide the necessary metrics as detailed in the Addendum, along with any other metrics deemed necessary by the Small Team to the extent that the data is available in a systematic manner, with the metrics being based on numerical and usage data. It should be noted that certain data elements listed in the data dictionary, for example, names of requestors, evidence and attachments, will not be analyzed or used as metrics for any other purpose that would go beyond gathering usage data. ICANN org ensured that the principles of privacy-by-design are embedded in the System’s design and development from its inception. Principles such as role-based data access limitation, data minimization, and data retention, were carefully considered and the publication of raw data would violate these principles. It is also important to remember that the purpose of this proof-of-concept system is not to perform contextual or content analysis, for example, evaluating the legitimacy of registrars’ disclosure decisions or analyzing outcome trends. We want to emphasize that GNSO Council's request and the ICANN Board's direction is to implement a cost-effective system that will simplify the process for submitting and receiving requests for nonpublic gTLD registration data for both the requestors and registrars and to report on usage of this system to help inform the Council–Board consultations on the next steps for the SSAD recommendations. Regards, Yuko Yokoyama Program Director Strategic Initiatives, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +1 310 578 8693 Mobile: +1 310 745 1517 E-mail: yuko.yokoyama@icann.org www.icann.org
Hi Sarah, If I recall well, I think it was something the small team was going to go back to after seeing the data model so we can include it in the agenda for Monday’s meeting so the small team can discuss whether in addition to your suggestions there are any other reporting points that the small team wants to propose to ICANN org be included? Best regards, Marika From: GNSO-EPDPP2-SmallTeam <gnso-epdpp2-smallteam-bounces@icann.org> on behalf of Sarah Wyld <swyld@tucows.com> Date: Thursday, 20 April 2023 at 19:27 To: Yuko Yokoyama <yuko.yokoyama@icann.org>, "gnso-epdpp2-smallteam@icann.org" <gnso-epdpp2-smallteam@icann.org> Subject: Re: [GNSO-EPDPP2-SmallTeam] RDRS Data Dictionary Hi, Thanks for sending this out, Yuko! I think we had discussed adding two reporting points (email thread subject “RDRS (née WDS) Reporting Points”): * Number of Requests by Requestor (may be pseudonymized/anonymized if needed) * Denial rate by reason type It looks like these didn’t make it into the Success Criteria [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1aGcf02uYXXLQC...> or spreadsheet, did we decide not to do them after all and I missed it? Thanks. -- Sarah Wyld, CIPP/E Policy & Privacy Manager Pronouns: she/they swyld@tucows.com<mailto:swyld@tucows.com> From: Yuko Yokoyama<mailto:yuko.yokoyama@icann.org> Sent: April 19, 2023 3:28 PM To: gnso-epdpp2-smallteam@icann.org<mailto:gnso-epdpp2-smallteam@icann.org> Subject: Re: [GNSO-EPDPP2-SmallTeam] RDRS Data Dictionary Dear Small Team members, Marc was kind enough to inform me of a clerical error in the Metrics tab, where lines 14 and 15 were duplicative. I have removed the duplicated line item (line 15) and added the cut off sentence in line 14. I have attached the revised document as V1.1. I would also like to add that this document is subject to change, as the system development progresses. We do not envision major changes, but there may be minor adjustments in the future. Regards, Yuko From: GNSO-EPDPP2-SmallTeam <gnso-epdpp2-smallteam-bounces@icann.org> on behalf of Yuko Yokoyama <yuko.yokoyama@icann.org> Date: Wednesday, April 19, 2023 at 12:02 PM To: "gnso-epdpp2-smallteam@icann.org" <gnso-epdpp2-smallteam@icann.org> Subject: [GNSO-EPDPP2-SmallTeam] RDRS Data Dictionary Dear Small Team members, Please see attached ICANN org’s data dictionary for the Registration Data Request Service. This document provides all the data fields captured in the system from both requestor and registrar sides, in a more digestible manner than the ones in the Design Paper<https://www.icann.org/en/system/files/files/whois-disclosure-system-design-p...>. * Tab 1: All the data fields captured in the requestor side of the System * Tab 2: All the data fields captured in the registrar side of the System * Tab 3: Reporting criteria specified in the Addendum [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy...> and whether those are reportable Please note, this document is being shared for the purpose of transparency and to showcase that the reporting criteria that are specified in the Addendum can be achieved with the data elements being collected. Additionally, our aim is that this document can aid in the Small Team’s discussion should it wish to add additional reporting criteria. We would like to add that ICANN org will not share any raw data collected through the System with external parties outside the System. While we understand the importance of transparency and accountability, we also want to ensure that ICANN org respects the privacy and the confidentiality of the requests logged through the system. The monthly reports will provide the necessary metrics as detailed in the Addendum, along with any other metrics deemed necessary by the Small Team to the extent that the data is available in a systematic manner, with the metrics being based on numerical and usage data. It should be noted that certain data elements listed in the data dictionary, for example, names of requestors, evidence and attachments, will not be analyzed or used as metrics for any other purpose that would go beyond gathering usage data. ICANN org ensured that the principles of privacy-by-design are embedded in the System’s design and development from its inception. Principles such as role-based data access limitation, data minimization, and data retention, were carefully considered and the publication of raw data would violate these principles. It is also important to remember that the purpose of this proof-of-concept system is not to perform contextual or content analysis, for example, evaluating the legitimacy of registrars’ disclosure decisions or analyzing outcome trends. We want to emphasize that GNSO Council's request and the ICANN Board's direction is to implement a cost-effective system that will simplify the process for submitting and receiving requests for nonpublic gTLD registration data for both the requestors and registrars and to report on usage of this system to help inform the Council–Board consultations on the next steps for the SSAD recommendations. Regards, Yuko Yokoyama Program Director Strategic Initiatives, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +1 310 578 8693 Mobile: +1 310 745 1517 E-mail: yuko.yokoyama@icann.org<mailto:yuko.yokoyama@icann.org> www.icann.org<http://www.icann.org/>
Great, thanks Marika! Discussing on Monday works for me 😊 -- Sarah Wyld, CIPP/E Policy & Privacy Manager Pronouns: she/they swyld@tucows.com From: Marika Konings Sent: April 20, 2023 1:39 PM To: Sarah Wyld; Yuko Yokoyama; gnso-epdpp2-smallteam@icann.org Subject: Re: [GNSO-EPDPP2-SmallTeam] RDRS Data Dictionary Hi Sarah, If I recall well, I think it was something the small team was going to go back to after seeing the data model so we can include it in the agenda for Monday’s meeting so the small team can discuss whether in addition to your suggestions there are any other reporting points that the small team wants to propose to ICANN org be included? Best regards, Marika From: GNSO-EPDPP2-SmallTeam <gnso-epdpp2-smallteam-bounces@icann.org> on behalf of Sarah Wyld <swyld@tucows.com> Date: Thursday, 20 April 2023 at 19:27 To: Yuko Yokoyama <yuko.yokoyama@icann.org>, "gnso-epdpp2-smallteam@icann.org" <gnso-epdpp2-smallteam@icann.org> Subject: Re: [GNSO-EPDPP2-SmallTeam] RDRS Data Dictionary Hi, Thanks for sending this out, Yuko! I think we had discussed adding two reporting points (email thread subject “RDRS (née WDS) Reporting Points”): - Number of Requests by Requestor (may be pseudonymized/anonymized if needed) - Denial rate by reason type It looks like these didn’t make it into the Success Criteria [docs.google.com] or spreadsheet, did we decide not to do them after all and I missed it? Thanks. -- Sarah Wyld, CIPP/E Policy & Privacy Manager Pronouns: she/they swyld@tucows.com From: Yuko Yokoyama Sent: April 19, 2023 3:28 PM To: gnso-epdpp2-smallteam@icann.org Subject: Re: [GNSO-EPDPP2-SmallTeam] RDRS Data Dictionary Dear Small Team members, Marc was kind enough to inform me of a clerical error in the Metrics tab, where lines 14 and 15 were duplicative. I have removed the duplicated line item (line 15) and added the cut off sentence in line 14. I have attached the revised document as V1.1. I would also like to add that this document is subject to change, as the system development progresses. We do not envision major changes, but there may be minor adjustments in the future. Regards, Yuko From: GNSO-EPDPP2-SmallTeam <gnso-epdpp2-smallteam-bounces@icann.org> on behalf of Yuko Yokoyama <yuko.yokoyama@icann.org> Date: Wednesday, April 19, 2023 at 12:02 PM To: "gnso-epdpp2-smallteam@icann.org" <gnso-epdpp2-smallteam@icann.org> Subject: [GNSO-EPDPP2-SmallTeam] RDRS Data Dictionary Dear Small Team members, Please see attached ICANN org’s data dictionary for the Registration Data Request Service. This document provides all the data fields captured in the system from both requestor and registrar sides, in a more digestible manner than the ones in the Design Paper. • Tab 1: All the data fields captured in the requestor side of the System • Tab 2: All the data fields captured in the registrar side of the System • Tab 3: Reporting criteria specified in the Addendum [gnso.icann.org] and whether those are reportable Please note, this document is being shared for the purpose of transparency and to showcase that the reporting criteria that are specified in the Addendum can be achieved with the data elements being collected. Additionally, our aim is that this document can aid in the Small Team’s discussion should it wish to add additional reporting criteria. We would like to add that ICANN org will not share any raw data collected through the System with external parties outside the System. While we understand the importance of transparency and accountability, we also want to ensure that ICANN org respects the privacy and the confidentiality of the requests logged through the system. The monthly reports will provide the necessary metrics as detailed in the Addendum, along with any other metrics deemed necessary by the Small Team to the extent that the data is available in a systematic manner, with the metrics being based on numerical and usage data. It should be noted that certain data elements listed in the data dictionary, for example, names of requestors, evidence and attachments, will not be analyzed or used as metrics for any other purpose that would go beyond gathering usage data. ICANN org ensured that the principles of privacy-by-design are embedded in the System’s design and development from its inception. Principles such as role-based data access limitation, data minimization, and data retention, were carefully considered and the publication of raw data would violate these principles. It is also important to remember that the purpose of this proof-of-concept system is not to perform contextual or content analysis, for example, evaluating the legitimacy of registrars’ disclosure decisions or analyzing outcome trends. We want to emphasize that GNSO Council's request and the ICANN Board's direction is to implement a cost-effective system that will simplify the process for submitting and receiving requests for nonpublic gTLD registration data for both the requestors and registrars and to report on usage of this system to help inform the Council–Board consultations on the next steps for the SSAD recommendations. Regards, Yuko Yokoyama Program Director Strategic Initiatives, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +1 310 578 8693 Mobile: +1 310 745 1517 E-mail: yuko.yokoyama@icann.org www.icann.org
participants (3)
-
Marika Konings -
Sarah Wyld -
Yuko Yokoyama