ICANN 83: Difference between revisions
Christiane (talk | contribs) Fixed broken ref |
Christiane (talk | contribs) m + internal link(s) |
||
| Line 12: | Line 12: | ||
}} | }} | ||
'''ICANN 83''' was ICANN's 83rd Public Meeting and the 2025 Policy Forum. It was held in Prague, Czech Republic, from June 9-12, 2025 at the Prague Congress Centre, with the support of local host [[CZ.NIC]], operator of [[.cz]].<ref name="icann83-site">[https://meetings.icann.org/en/meetings/icann83/ ICANN Meetings, "ICANN83 Prague Policy Forum".]</ref> <ref name="icann83-press">[https://www.icann.org/resources/press-material/release-2025-05-28-en ICANN: ICANN83 Policy Forum Set for Prague Amid Key Milestones]</ref> It was the second ICANN Public Meeting held in Prague, following [[ICANN 44]] in 2012.<ref name="icann44">[http://prague44.icann.org/ ICANN: ICANN 44 | '''ICANN 83''' was ICANN's 83rd Public Meeting and the 2025 Policy Forum. It was held in Prague, Czech Republic, from June 9-12, 2025 at the Prague Congress Centre, with the support of local host [[CZ.NIC]], operator of [[.cz]].<ref name="icann83-site">[https://meetings.icann.org/en/meetings/icann83/ ICANN Meetings, "ICANN83 Prague Policy Forum".]</ref> <ref name="icann83-press">[https://www.icann.org/resources/press-material/release-2025-05-28-en ICANN: ICANN83 Policy Forum Set for Prague Amid Key Milestones]</ref> It was the second ICANN Public Meeting held in Prague, following [[ICANN 44]] in 2012.<ref name="icann44">[http://prague44.icann.org/ ICANN Prague: ICANN 44]</ref> | ||
== Overview == | == Overview == | ||
| Line 26: | Line 26: | ||
The official schedule was published on May 19, 2025 on ICANN's Sched instance.<ref name="icann83-sched">[https://www.icann.org/en/announcements/details/icann83-schedule-now-available-19-05-2025-en ICANN Announcements: ICANN83 Schedule Now Available]</ref> <ref name="icann83-sched-site">[https://icann83.sched.com/ Sched: ICANN83 Policy Forum schedule]</ref> | The official schedule was published on May 19, 2025 on ICANN's Sched instance.<ref name="icann83-sched">[https://www.icann.org/en/announcements/details/icann83-schedule-now-available-19-05-2025-en ICANN Announcements: ICANN83 Schedule Now Available]</ref> <ref name="icann83-sched-site">[https://icann83.sched.com/ Sched: ICANN83 Policy Forum schedule]</ref> | ||
== GNSO | == GNSO == | ||
The GNSO Council held its public meeting on June 11, 2025. The agenda combined status updates on key small-team efforts (Board readiness, registration data accuracy, DNS abuse), a broader discussion on ICANN-wide reviews, and an open mic where community members highlighted priorities such as the Uniform Domain Name Dispute Resolution Policy (UDRP).<ref name="gnso">[https://gnso.icann.org/sites/default/files/policy/2025/minutes/minutes-gnso-council-11jun25-en.pdf ICANN GNSO: Minutes of the GNSO Council Meeting 11 June 2025]</ref> | === GNSO Council Public Meeting === | ||
The GNSO Council held its public meeting on June 11, 2025. The agenda combined status updates on key small-team efforts (Board readiness, registration data accuracy, DNS abuse), a broader discussion on ICANN-wide reviews, and an open mic where community members highlighted priorities such as the [[Uniform Domain Name Dispute Resolution Policy|Uniform Domain Name Dispute Resolution Policy (UDRP)]].<ref name="gnso">[https://gnso.icann.org/sites/default/files/policy/2025/minutes/minutes-gnso-council-11jun25-en.pdf ICANN GNSO: Minutes of the GNSO Council Meeting 11 June 2025]</ref> | |||
== Board Readiness Small Team == | == Board Readiness Small Team == | ||
| Line 36: | Line 38: | ||
The Small Team reported on its interviews with Board members focused on how and why specific GNSO recommendations were accepted, rejected, or modified, including issues such as wording problems, perceived bylaw conflicts, cost concerns, and implementation feasibility. | The Small Team reported on its interviews with Board members focused on how and why specific GNSO recommendations were accepted, rejected, or modified, including issues such as wording problems, perceived bylaw conflicts, cost concerns, and implementation feasibility. | ||
The discussion emphasized extracting “lessons learned” that could be translated into practical tools for future GNSO work, for example, checklists for [[Policy Development Process|PDP]] chartering, guidance on anticipating GAC and ALAC advice, and ways to structure PDP outputs so that the Board can act more coherently on them. | The discussion emphasized extracting “lessons learned” that could be translated into practical tools for future GNSO work, for example, checklists for [[Policy Development Process|PDP]] chartering, guidance on anticipating [[Governmental Advisory Committee|GAC]] and [[At-Large Advisory Committee|ALAC]] advice, and ways to structure PDP outputs so that the Board can act more coherently on them. | ||
Councilors highlighted the value of using these findings in future strategic planning sessions (e.g. the Council Strategic Planning Session) and in the SCCI’s work on PDP-related continuous improvement.<ref name="gnso"></ref> | Councilors highlighted the value of using these findings in future strategic planning sessions (e.g. the Council Strategic Planning Session) and in the SCCI’s work on PDP-related continuous improvement.<ref name="gnso"></ref> | ||
| Line 96: | Line 98: | ||
=== ASO === | === ASO === | ||
At ICANN 83 the [[Address Supporting Organization|Address Supporting Organization (ASO)]] and its Address Council (ASO AC) used their Prague agenda primarily to progress work on a new Regional Internet Registry (RIR) governance document that would replace the nearly 25-year-old "Internet Coordination Policy 2 (ICP-2)". The draft document under discussion would: | At ICANN 83 the [[Address Supporting Organization|Address Supporting Organization (ASO)]] and its Address Council (ASO AC) used their Prague agenda primarily to progress work on a new [[Regional Internet Registry (RIR)]] governance document that would replace the nearly 25-year-old "Internet Coordination Policy 2 (ICP-2)". The draft document under discussion would: | ||
* Establish the formal rules by which ICANN and the ASO recognize RIRs. | * Establish the formal rules by which ICANN and the ASO recognize RIRs. | ||
| Line 107: | Line 109: | ||
* A joint ASO–ALAC session to exchange views on IPv4 exhaustion, IPv6 deployment and how address policy intersects with end-user connectivity. | * A joint ASO–ALAC session to exchange views on IPv4 exhaustion, IPv6 deployment and how address policy intersects with end-user connectivity. | ||
* A joint | * A joint ASO–[[Root Server System Advisory Committee|RSSAC]] session focusing on how address distribution policy and routing practices interact with root server operations. | ||
* A joint meeting with the GNSO ISPCP Constituency that allowed access and transit providers to raise operational concerns related to address management. | * A joint meeting with the [[ISPs and Connectivity Providers Constituency|GNSO ISPCP Constituency]] that allowed access and transit providers to raise operational concerns related to address management. | ||
* A joint ASO–GAC session to brief governments on the status of RIR governance discussions and how public authorities participate in RIR policy processes.<ref name=" | * A joint ASO–GAC session to brief governments on the status of RIR governance discussions and how public authorities participate in RIR policy processes.<ref name="por83"></ref> | ||
== ccNSO == | |||
The [[Country Code Names Supporting Organization|Country Code Names Supporting Organization (ccNSO)]] in Prague concentrated on three clusters of work: DNS abuse in the ccTLD space, Internet governance linkages (including [[WSIS+20]]), and financial contribution models for ccTLDs. | |||
The ccNSO program included: | |||
* Tech Day: an open technical workshop for ccTLD and other registry operators focusing on DNS operational and security topics. | |||
* A ccNSO welcome and [[IANA]] update session, where ccTLD operators received operational and service updates related to the IANA functions. | |||
* A meeting of the ccNSO [[Internet Governance Liaison Committee]] (IGLC) examining how [[World Summit on the Information Society|WSIS]] principles had been implemented over the past two decades and the role of ccTLD managers in national and regional Internet governance processes. | |||
* A session of the ccNSO [[Universal Acceptance Committee]] (UAC) analysing why many ccTLDs have not prioritized Universal Acceptance work, the practical obstacles they face, and whether coordination with national regulators or other authorities could accelerate UA adoption.<ref name="por83"></ref> | |||
* Presentation of the [[Second Finance Working Group|Second ccNSO Finance (FIN2) Working Group]]’s final recommendations on voluntary financial contribution models for ccTLDs, based on a survey of ccTLD managers conducted in April 2025. The recommendations aimed to rebalance contributions while preserving their voluntary nature and were scheduled to be taken up by the ccNSO Council in Prague. | |||
The ccNSO also held: | |||
* A ccTLD News Session for operational updates from different regions. | |||
* A [[DNS Abuse Standing Committee|DNS Abuse Standing Committee (DASC)]] session focused specifically on online scams and financial crime linked to domain name abuse, with emphasis on how ccTLDs detect such activity and coordinate response with national authorities. | |||
* A joint session between the ccNSO and the GNSO [[Registries Stakeholder Group|Registry Stakeholder Group (RySG)]] to identify areas of collaboration and possible convergence of practices across ccTLDs and gTLD registries. | |||
The ccNSO Council meeting at ICANN 83 was expected to consider how to move forward with the FIN2 recommendations and to provide guidance to working groups on next steps.<ref name="por83"></ref> | |||
== References == | == References == | ||
{{reflist}} | {{reflist}} | ||