Bureaucrats, steward, Administrators, translator
875
edits
Changes
mLine 12:
Line 12: − + Line 20:
Line 20: − + + + + − + + − + Line 33:
Line 37: − + Line 45:
Line 49: + Line 50:
Line 55: + + + + − + + + + + + Line 70:
Line 84: + +
Christiane moved page ICANN 73 - San Juan* to ICANN 73 over redirect: Standardize
| historicalimport =
| historicalimport =
}}
}}
'''ICANN 73''' is the seventh [[ICANN Meetings|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<ref name="onlineres">[https://www.icann.org/resources/board-material/resolutions-2021-11-04-en Resolutions (2021.11.4.01-02 and .04) of the Board], November 4, 2021</ref> At the same meeting, the board confirmed their intention to hold a hybrid in-person and online meeting for [[ICANN 74 - The Hague|ICANN 74]] in The Hague.<ref name="onlineres" /> The board cited numerous factors both, directly and indirectly, related to the pandemic.<ref name="73blog">[https://www.icann.org/en/announcements/details/icann73-to-be-virtual-meeting-board-affirms-intent-to-hold-hybrid-icann74-4-11-2021-en ICANN.org - ICANN 73 to be a Virtual Meeting], November 4, 2021</ref> The meeting schedule will use the time zone of the intended host (UTC -4).
'''ICANN 73''' is the seventh [[ICANN Meetings|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.<ref name="onlineres">[https://www.icann.org/resources/board-material/resolutions-2021-11-04-en Resolutions (2021.11.4.01-02 and .04) of the Board], November 4, 2021</ref> At the same meeting, the board confirmed their intention to hold a hybrid in-person and online meeting for [[ICANN 74 - The Hague|ICANN 74]] in The Hague.<ref name="onlineres" /> The board cited numerous factors both, directly and indirectly, related to the pandemic.<ref name="73blog">[https://www.icann.org/en/announcements/details/icann73-to-be-virtual-meeting-board-affirms-intent-to-hold-hybrid-icann74-4-11-2021-en ICANN.org - ICANN 73 to be a Virtual Meeting], November 4, 2021</ref> The meeting schedule will use the time zone of the intended host (UTC -4).
==Board Actions==
==Board Actions==
==Topics==
==Topics==
# [[SUBPRO]]
# [[SUBPRO]]
#*[[IDN]]s will be prioritized (board)
#*[[ICANN Organization]] will deliver ODA by October 31, 2022.
#*ICANN Org expects Module 6 (terms and conditions) of the [https://newgtlds.icann.org/en/applicants/agb Applicant Guidebook] to require the highest level of effort to update, followed by the addition of new material and Modules 4 (string contention procedures) and 5 (transition to delegation).<ref>New gTLD Subsequent Procedures: Operational Design Phase, ICANN 73</ref>
#*[[IDN]]s will be prioritized, and this increase in non-traditional and IDN gTLDs will accelerate Universal Acceptance adoption.
#*[https://gac.icann.org/advice/correspondence/incoming/20220306/gac-gnso-council-consultation-on-closed-generics Closed generics]
#*[https://gac.icann.org/advice/correspondence/incoming/20220306/gac-gnso-council-consultation-on-closed-generics Closed generics]
#*The Brand Registry Group conveyed strong interest in proceeding toward subsequent rounds of new gTLDs
#*[[Name Collision]]
#*[[Name Collision]]
#**Impact of [[AltRoot]]s
#**Impact of [[AltRoot]]s
#**[[Name Collision Analysis Project|NCAP]] Study 2 will provide advice for next round of gTLD applicants (released Summer 2022)
#**[[Name Collision Analysis Project|NCAP]] Study 2 will provide advice for the next round of gTLD applicants (released Summer 2022)
#* In the [[CPH]]'s meeting with the board, [[Samantha Demetriou]] asked the board, "How do we avoid [[ODP]]s in the future?"
#[[DNS Abuse]]
#[[DNS Abuse]]
#*[[Malicious Domain]]s vs [[Compromised Domain]s
#*[[Malicious Domain]]s vs [[Compromised Domain]]s
#*Gac concerns:
#*Gac concerns:
#*CcNSO perspective:
#*CcNSO perspective:
#** 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], especially [https://www.icann.org/en/system/files/correspondence/dawson-to-icann-board-07mar22-en.pdf its broad definition of DNS abuse]
#* [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]
#**In the public forum, [[Steve Del Bianco]] asked about type 1 (malicious domains registered in batch used for c&cbotnet attacks and spam) and what ICANN can do about it
#**In the public forum, Steve del Bianco asked about type 1 (malicious domains registered in batch used for c&c botnet attacks and spam) and what ICANN can do about it
# [[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)
#*[[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
#[[GPI]]:
#[[GPI]]:
#*[[Avri Doria]]: Is it useful? I don’t know. But it was necessary, especially for the Board. It gives a language, tools, a methodology that is reproducible. We’ve got to see if it’s sufficient to the task. The determination has to come from the bottom up but a whole new set of procedures did not need to be generated. The GPI is like what the [[PDP]] does, but for the board. It is not mandatory in general, but at the moment it is necessary for the SSAD and SUBPRO.
#*GPI offers Board a tool and methodology to formalize and systemize their reasoning when they determine whether an action is in the GPI
#*GPI offers Board a tool and methodology to formalize and systemize their reasoning when they determine whether an action is in the GPI
#*[https://www.lewisroca.com/people-Anne-Aikman-Scalese 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.
#*[https://www.lewisroca.com/people-Anne-Aikman-Scalese 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.
#*pilot to be applied to [[SSAD]] and [[SUBPRO]]
#*pilot to be applied to [[SSAD]] and [[SUBPRO]]
#[[Prioritization Framework]]/Timeframe/How to clear the Board docket faster:
#[[Prioritization Framework]]/Timeframe/How to clear the Board docket faster:
#*In the [[ICANN Board]] and [[CSG]], the board indicated that Auction proceeds probably won’t be prioritized immediately
#*In SSAC's meeting with the board, SSAC Chair [[Rod Rasmussen]] asked, In light of the prioritization framework, what will ICANN Board do when SSAC recommendations align, are unique, or differ from other SO/AC advice. [[Maarten Botterman]] responded, the PF won’t resolve conflicts in advice.
#*[[ccNSO]]: ICANN Org should give status updates and answers more quickly
#*[[ccNSO]]: ICANN Org should give status updates and answers more quickly
#* In the ccNSO's meeting with the board, [[Becky Burr]] commented, "The entire [[ICANN Community]] has said the ICANN Board needs to move more quickly. Prioritization will help clarify what should happen, but it won’t speed things up. We have to figure out how to do that. We hear you loud and clear on bottlenecks and logjams."
#*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]]:
#* In the public forum, Icann.org being in different scripts and languages at the second level and/or top level was discussed, as a [[CCWG]] issue
#*CcNSO is focused on IDNs and UA
#*CcNSO is focused on IDNs and UA
#*[[UASG]] moving it forward: who will help us and how?
#*[[UASG]] moving it forward: who will help us and how?
#Internet Legislation and geopolitics
#[[Engagement#GE|Internet Legislation vis-a-vis Geopolitics]]
#*The Discussion Forum on Geopolitical, Legislative, and Regulatory Developments will become a regular feature of ICANN meetings from now on
#*The Discussion Forum on Geopolitical, Legislative, and Regulatory Developments will become a regular feature of ICANN meetings from now on
#*Very active [[Internet Governance]] [https://www.pch.net/meetings schedule] in 2022
#*Very active [[Internet Governance]] [https://www.pch.net/meetings schedule] in 2022
#*There is a politicization of technical issues, such as protocols, wherein governments try to regulate people by legislating technical ([[Mark Datysgeld]] and [[Goran Marby]])
#*[[Data Privacy]]
#*[[Data Privacy]]
#**[[Werner Staub]]: Accountability and privacy feel opposed right now, and we’ve got to change that. [[Becky Burr]]: respectfully disagreed. "Bad actors have to be held accountable but access to data has to be regulated"
#[[Alternative Roots]]
#[[Alternative Roots]]
#*[[John Cain]]: If it is not using the signed version of the ICANN published root, it’s an alternate root; BlockChain does not equal AltRoot and there are many many great uses for blockchain technologies
#*[[Alan Greenberg]]: we need a hyper-root pointing to the alternative roots!
#* the [[NARALO]] and Public Forum sessions focused on the present and future of altroots
#* the [[NARALO]] and Public Forum sessions focused on the present and future of altroots
#**In the public forum, there was a discussion around whether ICANN could explore why people are turning to alternative roots (what are they missing from the DNS) and see if the ICANN community can apply those principles to the DNS
==Dates==
==Dates==
==References==
==References==
{{reflist}}
{{reflist}}
[[Category:ICANN Meetings]]