Hi Steve and Team, I think that indeed the idea would be indeed to collect the requestor’s country for all requests – by making it a mandatory field, pre-populating it with the User country as already set in the ICANN User profile, but allowing for it to be corrected on the request form. I assume we will use our Country field and may continue using the term Country in this context, but I understand the ask was “per country” and “per economy”, the distinction being that a few “economies” operate their own law enforcement without clearly appearing in a country list – Taiwan comes to mind. In our nomenclatures we already use the notion of Territory – in ccTLDs for example – which might be also a relevant level of granularity. For that reason we should help the user by pre-populating with what information we have, but leave the field open to user input – as opposed to a locked field or a finite dropdown list. This may lead to odd entries, but I believe we will have to live with it. Country, Economy or Territory data is not PII to my knowledge, there should be no issue collecting it. We can then add a metric per Country in our reporting, but for NCSG purposes, I understand we would also then need an LEA-specific country metric, either as a country per requestor type metric, or as two tables: LEA Requests per Country and Any Request per Country. Comments, thoughts? Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_2249938427] +33612284445 France & Australia sebastien@registry.godaddy<mailto:sebastien@registry.godaddy> From: Steve Crocker via Gnso-rdrs-sc <gnso-rdrs-sc@icann.org> Date: Friday, 3 May 2024 at 6:28 PM To: farzaneh badii <farzaneh.badii@gmail.com> Cc: gnso-rdrs-sc@icann.org <gnso-rdrs-sc@icann.org> Subject: [Gnso-rdrs-sc] Re: NCSG request: LEA's country/economy Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Let me expand Farzaneh's suggestion to include the requestor's country on every request, not just requests from law enforcement. The registrar's determination of whether or not to provide the requested data may well depend, at least in part, on the jurisdiction of the requestor. Thanks, Steve On Thu, May 2, 2024 at 1:41 PM farzaneh badii via Gnso-rdrs-sc <gnso-rdrs-sc@icann.org<mailto:gnso-rdrs-sc@icann.org>> wrote: Dear all, Excited to have joined the team. Per our previous conversation, NCSG would like to discuss the possibility of reporting the location (the country/economy) of law enforcement agencies that submit requests to the RDRS. In order to report on that, the system needs to capture the location/country of the LEAs. For the next meeting, we wanted to discuss the technical preparedness needed to capture the data. Here is NCSG's request with examples of industry actors that report on LEAs' country/economy : https://docs.google.com/document/d/1Lyj-g5y8JLBSf-dHm81Cf_bFDRBEeZ-KgYYy44at... I have also added our request to the RDRS Impressions document: https://docs.google.com/document/d/14b6bG1Odmx-pLkTHrLSNiqAA4JCky2bewidHa5Yt... Please do not hesitate to reach out if you have questions about this request or in need of further clarification. Best regards, Farzaneh _______________________________________________ Gnso-rdrs-sc mailing list -- gnso-rdrs-sc@icann.org<mailto:gnso-rdrs-sc@icann.org> To unsubscribe send an email to gnso-rdrs-sc-leave@icann.org<mailto:gnso-rdrs-sc-leave@icann.org> _______________________________________________ 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. -- Sent by a Verified [Image removed by sender. Sent by a Verified sender]<https://wallet.unumid.co/authenticate?referralCode=tcp16fM4W47y> sender
