<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>
</p>
<p style="margin-bottom: 0in">Hello advisors. ICANN held a hybrid
meeting in Den Hague, Holland in June. I attended virtually.
During this session At Large
leaders held 10 sessions covering the three tracks of policy,
outreach and engagement, and operations. Below is a brief
description
of the four sessions related to Internet policy issues. I just
thought a broad outline of some of the issues under the microscope
might be of interest.<br>
</p>
<p style="margin-bottom: 0in"><b>• “Evolving the DNS Abuse
Conversation: An End User’s Perspective – The Role of At-Large”
(DNS abuse issues that can be mitigated at this level are
limited mostly to phishing, pharming, malware, spam when it
involves malware and botnets)<br>
</b></p>
<b>
</b>
<p style="margin-bottom: 0in">This session was a follow-up on the
ICANN73 plenary session “Evolving the DNS Abuse Conversation.”The
session focused on the role of the
At-Large community in mitigating DNS abuse. Speakers:</p>
<p style="margin-bottom: 0in">Presented on current ICANN org
activities related to DNS abuse.</p>
<p style="margin-bottom: 0in">Explored the At-Large role as an
advocate for end users in mitigating domain name abuse resulting
from
maliciously registered domain names and compromised websites,
including providing specific examples from the five RALOs. </p>
<p style="margin-bottom: 0in">Discussed the challenges and
opportunities relating to reporting cases of DNS abuse. </p>
<p style="margin-bottom: 0in"><b>• “Closed Generics: Finding a
Balance”</b><b><font face="Times New Roman, serif"><font
size="3"> (</font></font></b><b><font color="#202124"><font
face="Times New Roman, serif"><font size="3"><span
style="font-style: normal">a
top level domain representing a string that is a generic
name or term
under which domains are registered and usable
exclusively by the
registry operator or its affiliates. e.g. imagine if
Amazon were
allowed to own .book or if General Motors owned .cars)</span></font></font></font></b></p>
<b>
</b>
<p style="margin-bottom: 0in">During this session, the At-Large
community heard an introduction to closed generics and the current
situation. A proposal focusing on closed generics and the public
interest was presented as a possible approach to further develop
an
At-Large position on the topic.</p>
<p style="margin-bottom: 0in"> <b>• “Shaping the European Union’s
Digital Future: Sovereignty, Legal, and Regulatory Frameworks”
(The EU is very actively designing legislation to enable a more
integrated approach to cybersecurity and curtailing the powers
of giant techno firms)<br>
</b></p>
<b>
</b>
<p style="margin-bottom: 0in">This session focused on current
regulatory activities within the European Union, including the
Network and Information Security (NIS2) Directive and the DNS4EU
project. Various views were provided on the regulatory activities
and
the potential impact on end users. </p>
<p style="margin-bottom: 0in"><b>• “Internet Governance and
Multistakeholderism in Terms/Time of Emergency”(The current
crisis is the war in Ukraine but the discussion included actions
around hurricanes and other natural disasters)<br>
</b></p>
<b>
</b>
<p style="margin-bottom: 0in">The At-Large experience in times of
emergency across the regions was presented from the point of view
of
each of the five RALOs. Case studies from emergencies such as
natural
disasters and war were presented. The need to act quickly with
quality equipment was also highlighted. The various actions by
ICANN
org related to the situation in Ukraine as well as other
emergencies
were discussed <br>
</p>
<p style="margin-bottom: 0in">I am happy to answer questions about
any of this policy areas.</p>
<p style="margin-bottom: 0in">Marita<br>
</p>
<p style="margin-bottom: 0in"><br>
</p>
<p style="margin-bottom: 0in"><br>
</p>
<p style="margin-bottom: 0in"><br>
</p>
</body>
</html>