14,932
edits
Changes
Jump to navigation
Jump to search
Line 25:
Line 25: + Line 50:
Line 51: + + Line 60:
Line 63: − + +
→Topics
#**Impact of [[AltRoot]]s
#**Impact of [[AltRoot]]s
#**[[Name Collision Analysis Project|NCAP]] Study 2 will provide advice for the 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
#*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 SSAC's meeting with 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]]:
#*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]])
#*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"
#**[[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
#**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