Versions Compared

Old Version 470

changes.mady.by.user Dan O'Neill

Saved on

compared with

New Version 471

changes.mady.by.user Dan O'Neill

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Item #CategorySource of RequestDate of RequestAction Item RequestAction Owner

Anticipated Completion Date*

Progress Notes
466General11417 June 2020

Kaveh to put KC in touch with Ted Hardie, for a discussion regarding SSR2 recommendation 22.

Kaveh24 June 2020
465General11417 June 2020

Team members to review the proposed changes to recommendation 27 and recommendation 6, as discussed on the call, ahead of final review of the text next week.

Team members24 June 2020
462General11310 June 2020Kerry-Ann to update recommendation 6 to include privacy text once other changes to recommendation 6 have been made.Kerry-Ann24 June 2020
459General1123 June 2020Leadership team to discuss a proposal for the path forward during the leadership meeting on 8 JuneLeader-ship team8 June 2020
457General1123 June 2020Recommendation 27 subteam to look at SAC 107, 108, and 109 to ensure the content of these documents is considered in the revised text.Rec 27 subteam10 June 2020
456General11127 May 2020KC to help find resources related to NCAP and share these with Naveed.KC3 June 2020
455General11127 May 2020Staff to provide information about the implementation of the CCT recommendations that have been accepted by the Board.ICANN org10 June 2020
452General11020 May 2020Review team members to continue to work in subgroups and update the bar chart as work progresses. Review Team1 July 2020
451General11020 May 2020

Staff to update the work plan based on the review team’s new completion date.

ICANN org27 May 2020
450GeneralEmail13 May 2020

Q: It would be great if we could get updates on SSAC recommendations in SAC101v2, SAC097,  and the 4 suggestions in :

https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system_files_files_ssac2019-2D02-2D03may19-2Den.pdf&d=DwICAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=VuRMFw6YascG5ysc1jEHBZgGTtD6QSLrFmqdvMx5FM8&m=BbASPz11QOHrRR5GgjJOp5C9L51Y_6k_tF1cLAskF2Y&s=FnnX_E-dhahAAb2ZkNVh9WqJvF14cFkJXQ2WR8XQXx4&e=

  1. "ICANN Org issue guidance to all registry operators, clarifying expectations for reporting port 43 queries and RDAP queries. The guidance should make clear the purposes and goals of the data collection and the contractual obligations.
  2. SSAC believes that a purpose of gathering the data is to document queries made by the users (consumers) of the registration data service. Registry  operators should exclude the queries they make to their own systems.
  3. It is vital that ICANN collect valid, accurate data regarding RDAP queries. The WHOIS query data is unreliable, but the move to RDAP offers an opportunity to get things right.
  4. ICANN Org's Global Domains Division and Compliance Department should examine the reporting of other metrics per the registry contracts. In  SAC097, the SSAC pointed out irregularities in the reporting of other registry metrics, such as web-based WHOIS queries. The current issue raises the question of whether metrics such as DNS queries are being reported accurately, if they too involve the reporting of self-queries, etc.
ICANN orgTBD
449GeneralEmail11 May 2020Q: It was announced earlier this year that Verisign will give ICANN $20 million over five years, beginning next year, “to support ICANN's initiatives to preserve and enhance the security, stability, and resiliency of the DNS.” Why (were there SSR vulnerabilities identified by Verisign and/or ICANN for which funding was needed)? Would you please provide the SSR2 with details on what specific activities ICANN will be using these funds for, next year and in subsequent years, (beyond the general categories mentioned in Goran’s March 27 announcement). What criteria and process is ICANN using to determine how to spend this SSR money? Goran stated that he “recognizes the request for accountability and transparency regarding how the funds are used and is committed to full transparency to provide the ICANN community the appropriate level of detail when available”-- please provide SSR2 more details on this, including how the funds and expenditures will be reflected and tracked in ICANN’s annual budget and operating plan.ICANN orgTBD
448GeneralEmail5 May 2020Q: ICANN reportedly will be adding supplemental questions and criteria on DNS abuse to the registrar accreditation application (sounds promising). Please provide SSR2 with information about this including: the final or draft supplemental text; how ICANN will assess the answers; whether and how the answers will factor into ICANN’s decision to approve or deny an application; how ICANN will track and hold an approved registrar accountable for the registrar’s statements in the application regarding how the applicant intends to address DNS abuse as a registrar; and whether ICANN has plans to add similar supplemental DNS abuse questions and criteria to registrar contract renewals (why, why not).ICANN orgTBD
442General1078 Apr 2020KC to share proposed text that she believes should be included in the report with regard to prioritization, as articulated on the call.KC 15 Apr 2020

...