Jump to content

ICANN 73: Difference between revisions

From ICANNWiki
Jessica (talk | contribs)
Jessica (talk | contribs)
No edit summary
Line 30: Line 30:
#*CcNSO perspective:
#*CcNSO perspective:
#*org/board:  
#*org/board:  
#**[https://www.icann.org/en/announcements/details/icann-expands-dnsticr-to-monitor-terms-related-to-russia-ukraine-war-09-03-2022-en DNSTICR] originally for covid will now be used for Ukraine crisis
#**[https://www.icann.org/en/announcements/details/icann-expands-dnsticr-to-monitor-terms-related-to-russia-ukraine-war-09-03-2022-en DNSTICR] originally for covid will now be used for the Ukraine crisis
#** DNS abuse trending down and ICANN Org investigating why
#** DNS abuse trending down and ICANN Org investigating why
#* [https://op.europa.eu/en/publication-detail/-/publication/7d16c267-7f1f-11ec-8c40-01aa75ed71a1 EC DNS abuse study]  
#* [https://op.europa.eu/en/publication-detail/-/publication/7d16c267-7f1f-11ec-8c40-01aa75ed71a1 EC DNS abuse study], especially [https://www.icann.org/en/system/files/correspondence/dawson-to-icann-board-07mar22-en.pdf its broad definition of DNS abuse]
# [[SSAD]]
# [[SSAD]]
#* discussion over whether it should go forward and if so, which parts: a ticketing format & let’s see with the pilot) and at what cost/does cost matter (board/GNSO council)
#* discussion over whether it should go forward and if so, which parts: a ticketing format & let’s see with the pilot) and at what cost/does cost matter (board/GNSO council)
Line 38: Line 38:
# COVID Fatigue affecting morale:
# COVID Fatigue affecting morale:
#*[[AC]]s worry the board doesn’t value their advice and contributions, discussed at length in [[SSAC]], [[GAC]] and [[ALAC]] meetings with board
#*[[AC]]s worry the board doesn’t value their advice and contributions, discussed at length in [[SSAC]], [[GAC]] and [[ALAC]] meetings with board
#*Board is overwhelmed with the number of recommendations and want the gnso to give them actionable recommendations; frustrated by European Data Protection Board’s slow to no advice on what to do about data accuracy research; frustrated with govt reps legislating around ICANN policies that they don’t like
#*Board is overwhelmed with the number of recommendations and wants the GNSO to focus on actionable recommendations; frustrated by European Data Protection Board’s slow to no advice on what to do about [[Data Accuracy]] research; frustrated with govt reps legislating around ICANN policies when they dislike ICANN actions
#*[[GNSO Council]] is considering its options to get its recommendations reviewed and implemented and want the board to develop and apply a target timeline
#*[[GNSO Council]] is considering its options to get its recommendations reviewed and implemented and want the board to develop and apply a target timeline
#*[https://phe.tbe.taleo.net/phe03/ats/careers/v2/searchResults?org=ICANN&cws=37 ICANN Org is hiring 37 staffers], which should shorten response times from ICANN Org, the pandemic has slowed things down
#*[https://phe.tbe.taleo.net/phe03/ats/careers/v2/searchResults?org=ICANN&cws=37 ICANN Org is hiring 37 staffers], which should shorten response times from ICANN Org; the pandemic has slowed things down
#*[[:Category:ICANN Staff|ICANN Staffers]] may feel under attack because some in the community are criticizing ICANN Org, but the community needs to be able to point out problems when there are issues in the system and to be able to talk about them.  
#*[[:Category:ICANN Staff|ICANN Staffers]] may feel under attack because some in the community are criticizing ICANN Org, but the community needs to be able to point out problems when there are issues in the system and to be able to talk about them.  
#*[[ccNSO]]: [[ICANN Community]] needs to communicate informally with [[ICANN Board]] and each other to speed things up
#*[[ccNSO]]: [[ICANN Community]] needs to communicate informally with [[ICANN Board]] and each other to speed things up
Line 48: Line 48:
#*Gnso worried it’s an opportunity to relitigate
#*Gnso worried it’s an opportunity to relitigate
#*pilot to be applied to [[SSAD]] and [[SUBPRO]]
#*pilot to be applied to [[SSAD]] and [[SUBPRO]]
#Prioritization/Timeframe/way to speed things up:
#[[Prioritization Framework]]/Timeframe/How to clear the Board docket faster:
#*ccNSO: Give status updates and answer more quickly
#*[[ccNSO]]: ICANN Org should give status updates and answers more quickly
#*ICANN Board: we oversee the [[ICANN Organization|org]], so SO/AC members should email the board directly to expedite and resolve issues and get status updates for instance from ICANN Legal
#*ICANN Board: we oversee the [[ICANN Organization|org]], so SO/AC members should email the board directly to expedite and resolve issues and get status updates for instance from ICANN Legal
#[[Universal Acceptance]]:
#[[Universal Acceptance]]:

Revision as of 18:41, 14 March 2022

Dates: Prep Week: February 22-24, 2022

Community Forum: March 7-10, 2022

Location: San Juan, Puerto Rico (UTC -4)
Venue: Virtual
Website: ICANN 73 (registration required)

ICANN 73 is the seventh ICANN Meeting to be held online only due to the COVID pandemic. The ICANN Board made the decision to convert the San Juan meeting to virtual in November 2021[1] At the same meeting, the board confirmed their intention to hold a hybrid in-person and online meeting for ICANN 74 in The Hague.[1] The board cited numerous factors both, directly and indirectly, related to the pandemic.[2] The meeting schedule will use the time zone of the intended host (UTC -4).

Board Actions[edit | edit source]

Topics[edit | edit source]

  1. SUBPRO
  2. DNS Abuse
  3. SSAD
    • discussion over whether it should go forward and if so, which parts: a ticketing format & let’s see with the pilot) and at what cost/does cost matter (board/GNSO council)
    • SSAC public meeting: discussion of SAC118: no, SSAD should not be implemented
  4. COVID Fatigue affecting morale:
    • ACs worry the board doesn’t value their advice and contributions, discussed at length in SSAC, GAC and ALAC meetings with board
    • Board is overwhelmed with the number of recommendations and wants the GNSO to focus on actionable recommendations; frustrated by European Data Protection Board’s slow to no advice on what to do about Data Accuracy research; frustrated with govt reps legislating around ICANN policies when they dislike ICANN actions
    • GNSO Council is considering its options to get its recommendations reviewed and implemented and want the board to develop and apply a target timeline
    • ICANN Org is hiring 37 staffers, which should shorten response times from ICANN Org; the pandemic has slowed things down
    • ICANN Staffers may feel under attack because some in the community are criticizing ICANN Org, but the community needs to be able to point out problems when there are issues in the system and to be able to talk about them.
    • ccNSO: ICANN Community needs to communicate informally with ICANN Board and each other to speed things up
  5. GPI:
    • GPI offers Board a tool and methodology to formalize and systemize their reasoning when they determine whether an action is in the GPI
    • Anne Aikman-Scalese: the Board has a fiduciary duty to act in the Global Public Interest within the scope of its Mission. Otherwise, there would be no reason for the ByLaws to contain provisions that allow it to override GAC Advice by a 60% vote or to override GNSO Policy advice by a 2/3 majority vote. The GPI goes beyond MSM policymaking.
    • Gnso worried it’s an opportunity to relitigate
    • pilot to be applied to SSAD and SUBPRO
  6. Prioritization Framework/Timeframe/How to clear the Board docket faster:
    • ccNSO: ICANN Org should give status updates and answers more quickly
    • ICANN Board: we oversee the org, so SO/AC members should email the board directly to expedite and resolve issues and get status updates for instance from ICANN Legal
  7. Universal Acceptance:
    • CcNSO is focused on IDNs and UA
    • UASG moving it forward: who will help us and how?

Dates[edit | edit source]

  • Application period for ICANN's Pandemic Internet Access Reimbursement Program started on January 24, 2022.
  • Prep Week schedule released: February 7, 2022[4]
  • Community Forum schedule released: February 14, 2022
  • ICANN Prep Week: February 22-24, 2022
  • ICANN 73: March 7-10, 2022

References[edit | edit source]