Notes from 23 January 2018 APAC Space Web Conference

The APAC Space web conference meeting was attended by 40 participants from the region, including registries, registrars, and at-large community. In summary, community were introduced to the revamped ICANN Accountability Indicators and discussed potential topics for the upcoming APAC Space face-to-face meeting. In addition, Holly Raiche highlighted the three ICANN proposed compliance models related to the EU General Data Protection Regulation (GDPR) that require community’s feedback.

The meeting originally intended to discuss the Next-Generation gTLD Registration Directory Services to Replace Whois Policy Development Process (RDS PDP). Unfortunately, Chuck Gomes, PDP Working Group Chair, sent his deep apologies for missing the meeting due to a mix up in timezones. Hence, we will return to the RDS PDP in the next APAC Space @ ICANN61 Community Forum (San Juan).

The meeting recording and presentation slides can be found at the APAC Space Community Wiki webpage here: https://icann-community.atlassian.net/wiki/spaces/GSEAPAC/pages/114296860/APAC+Space.

Key action items following the meeting are:

• Discuss and decide agenda for APAC Space @ ICANN61 Community Forum (San Juan) on the discuss@apacspace.asia mailing list. Potential discussion topics for the next APAC Space include (but not limited to):
  • ICANN Policy Development Process (PDP) on Next-Generation gTLD Registration Directory Services (RDS) to Replace Whois (confirmed)
  • Introduction to ICANN Reviews – newcomers toolkit
  • Introduction to RDS-WHOIS 2 Review (suggested to be dropped)
    • A community member suggested dropping the RDS-WHOIS 2 Review from the agenda because the RDS-WHOIS 2 Review is ongoing and with the existing RDS undergoing changes in the near future, the scope of Review team may be changed.
  • Update on Universal Acceptance Steering Group (UASG) and Internationalized Domain Names (IDNs)
  • ICANN Open Data Initiative (ODI)
    • A community member suggested that community discuss the needs for, and impact of, ODI in light of the recent budget cuts for FY19 within ICANN.
  • ICANN’s Draft FY19 Operating Plan and Budget, and Five-Year Operating Plan Update
    • A community member suggested creating a strong statement regarding prioritising community needs such as for translation

• Provide feedback on proposed compliance models for collecting registration data and implementing registration directory services by 29 January 2018 to gdpr@icann.org. More information can be found in the announcement here: https://www.icann.org/news/blog/data-protection-and-privacy-update-seeking-community-feedback-on-proposed-compliance-models

• Provide public comment to ICANN’s Draft FY19 Operating Plan and Budget, and Five-Year Operating Plan Update. The public comment period closes on 8 March 2018.

• Provide feedback on the revamped ICANN Accountability Indicators.

Community Discussion

• ICANN proposed compliance models
  • Holly Raiche provided an update of the ICANN proposed compliance models. The At-Large Advisory Committee (ALAC) are developing a statement as community feedback here: https://atlarge.icann.org/advice_statements/11003
  • From contracted parties perspective, a community member commented that it was unclear how the proposed compliance model would be chosen and implemented. A one-size-fits-all approach on all contracted parties may have challenges in terms of implementation especially for smaller companies who may not have European clients. Registries Stakeholder Group (RySG) and Registrars Stakeholder Group (RrSG) were preparing a joint comment on the proposed models.

AOB

Upcoming Events: 

• APAC Space @ ICANN61 Community Forum (San Juan)
  • Wednesday, 14 March 2018
  • 8:45AM – 10:15AM (local time) / 12:45PM – 2:15PM (UTC)
  • Remote participation available

• APAC Social @ ICANN61 Community Forum (San Juan)
  • Wednesday, 14 March 2018
  • 5:30PM – 6:30PM (local time)
  • Refreshment and drinks are provided