Feodora, et al, I believe we also discussed the larger point regarding whether the data being collected will be representative of what the demand would be if the system were: - more predictable, i.e. if requestors could be certain as to whether their requests would or would not be honored, - faster - easier to use and integrate into their own systems. For the record, I do not believe the data we're seeing is helpful in understanding how a system with the above characteristics would be used. I know it is harder to capture points like this in your summary, but it's nonetheless necessary. Thanks, Steve On Tue, Jul 30, 2024 at 4:07 PM Feodora Hamza via Gnso-rdrs-sc < gnso-rdrs-sc@icann.org> wrote:
Dear members of the Standing Committee,
Please find below the main discussion points and action items from this week`s meeting.
The next meeting is scheduled for Monday, 12 August at 17:30 UTC.
Kind regards,
Feodora and Caitlin
2024-07-29 RDRS Standing Committee - Meeting #13 <https://community.icann.org/pages/viewpage.action?pageId=347373586>
1. Welcome
- The SC chair provided an update on a pending letter to Greg, noting delays due to a demanding project but reassured attendees it remains a priority. The current project deadline is tomorrow, which is anticipated to free up time for additional tasks.
*AI:* SC Chair to finalize and send the letter to GNSO Council.
2. RDRS Usage Metrics Report
- Standing Committee feedback/questions on recent Metrics Usage Report <https://www.icann.org/en/system/files/files/rdrs-usage-metrics-15jul24-en.pd...>
- ICANN Org provided an overview of the metrics, highlighting new additions and clarifying data representations in particular metric 10.
- BC suggested incorporating percentages alongside numerical data in metric 10 to enhance clarity and trend analysis. The feasibility of such an addition was discussed, considering potential volume and expanding requirements.
- SC members raised concerns about data presentation consistency across different metrics.
- SC members queried the high percentage of "not supported" domains compared to the low percentage of ccTLDs.
- ICANN Org explained that unsupported domains include ccTLDs, incorrect formats, or non-existent domains. A significant portion may be due to incorrect domain formats or random strings.
- SC Chair suggested scheduling a detailed discussion with Simon or relevant experts for further clarification on metrics data.
*AI:* ICANN Org to invite Simon or another expert to discuss metrics in the next call.
3. Impressions Document <https://docs.google.com/spreadsheets/d/1XFK-RCT5Nv-KcNgX4eQunkUKgSI35Yc_nUZ6...> Management
4. Impressions Document <https://docs.google.com/spreadsheets/d/1XFK-RCT5Nv-KcNgX4eQunkUKgSI35Yc_nUZ6...> Review & Prioritization
- Farzaneh Badii discussed implementing law enforcement location reporting and distinguishing between "per country" and "per economy" in reports. The goal is accurate jurisdiction reporting for territories like Taiwan.
- ICANN Org confirmed that the dropdown list includes economies and that the technical team has considered this in the system.
- Discussion followed on whether to include all request types or limit to law enforcement, with consensus leaning towards including all types for comprehensive data reporting.
- ICANN Org has removed the change requests without an SC Owner from the main tables and added them to a separate tab.
*AI:* SC members to provide additional information on the specific metric information to be displayed as requested by ICANN Org in the impressions document for item #1 on the requestor tab.
5. AOB
- SC members raised the need to compile responses to the Council regarding assignment questions and suggested evaluating the stability of request data to determine if the project should continue for the full timeline.
- SC Chair proposed improving post-request surveys to gather more comprehensive feedback.
- ICANN Org noted updates to survey communications and ongoing discussions about refining questions and increasing response rates.
*Feodora Hamza*
Policy Development Support Manager (GNSO)
Internet Corporation for Assigned Names and Numbers (ICANN)
* Mobile:* +32 496 30 24 15
*Email:* feodora.hamza@icann.org
*Website:* www.icann.org
_______________________________________________ Gnso-rdrs-sc mailing list -- gnso-rdrs-sc@icann.org To unsubscribe send an email to 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: Sent by a Verified sender] <https://wallet.unumid.co/authenticate?referralCode=tcp16fM4W47y> sender