<div dir="ltr"><div class="gmail_default" style="font-family:arial,sans-serif">Hi Julf,</div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif">If we share this with the NCSG mailing list we will have other members engaged as well hopefully. </div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif">But in my opinion we should ask the Board to do a lightweight human rights impact assessment when they issue their resolutions. They already do risk assessment. See what they say. </div><div class="gmail_default" style="font-family:arial,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,sans-serif">We should seek some clarification on .LB and its redelegation. What do they mean by "transfer" in this resolution <span style="font-family:Arial,Helvetica,sans-serif">a. Transfer of the .LB (Lebanon) top-level domain, do they mean it is a redelegation? We should also tell them what is the process in place when cases like .LB happens. I know it has been ad hoc, the manager suddenly passed away, his organization did not want to take on the responsibility so for awhile it was in limbo. What are the IANA processes on this when emergency like this happens or when civil war and conflict happens. I am specifically talking about this paragraph: </span><span style="font-family:Arial,Helvetica,sans-serif">What concerns or issues were raised by the community?</span></div><span class="gmail_default" style="font-family:arial,sans-serif">"</span>IANA is not aware of any significant issues or concerns raised by the community in relation to this request. Of note, an objection was raised outside of the IANA process. After research, the source and substance of the objection could not be verified.<span class="gmail_default" style="font-family:arial,sans-serif">" There were some concerns raised but it was more of whispering around. Had we had a certain and clear process run by IANA we would not have been whispering. </span><div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif"><span class="gmail_default" style="font-family:arial,sans-serif">Should we express concerns that our public comments were not addressed on the bilateral dns abuse amendment? </span></font></div><div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif"><span class="gmail_default" style="font-family:arial,sans-serif">Also can we tell the Board not to do this question answer format. It has never worked. Can we just have a conversation! </span></font></div><div><font face="arial, sans-serif"><br></font><div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif"><br></font><br><div class="gmail_default" style="font-family:arial,sans-serif"><span style="font-family:Arial,Helvetica,sans-serif"><br></span></div><div class="gmail_default" style="font-family:arial,sans-serif"><span style="font-family:Arial,Helvetica,sans-serif"><br></span></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><font face="verdana, sans-serif">Farzaneh </font></div></div></div></div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 16, 2024 at 9:45 AM Johan Helsingius via NCSG-EC <<a href="mailto:ncsg-ec@lists.ncsg.is">ncsg-ec@lists.ncsg.is</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The 21st is approaching. Any suggestions?<br>
<br>
Julf<br>
<br>
<br>
<br>
-------- Forwarded Message --------<br>
Subject: Fwd: ICANN79 Stakeholders/Board sessions<br>
Date: Wed, 7 Feb 2024 11:01:19 +0100<br>
From: Johan Helsingius <julf@Julf.com><br>
To: NCSG EC <<a href="mailto:ncsg-ec@lists.ncsg.is" target="_blank">ncsg-ec@lists.ncsg.is</a>>, ncsg-pc <<a href="mailto:ncsg-pc@lists.ncsg.is" target="_blank">ncsg-pc@lists.ncsg.is</a>><br>
<br>
We need to have answers to the two questions by 21 February<br>
<br>
- There is an ICANN CEO goal to have the organization develop and <br>
implement a communications and engagement strategy to address the WSIS <br>
20-year review - what are the NCSG’s views on ICANN engagement <br>
priorities and strategies in this space?<br>
<br>
- Engagement with between groups and bodies in the ICANN space is <br>
continuing to evolve, including with the introduction of session in the <br>
Prep Week and breakout rooms on specific issues of current interest - <br>
does the NCSG have views on these new approaches or how to continue <br>
improving engagement strategies?<br>
<br>
Julf<br>
<br>
<br>
<br>
-------- Forwarded Message --------<br>
Subject: ICANN79 Stakeholders/Board sessions<br>
Date: Tue, 6 Feb 2024 21:56:03 +0000<br>
From: Vinciane Koenigsfeld <<a href="mailto:vinciane.koenigsfeld@icann.org" target="_blank">vinciane.koenigsfeld@icann.org</a>><br>
To: <a href="mailto:julf@julf.com" target="_blank">julf@julf.com</a> <<a href="mailto:julf@julf.com" target="_blank">julf@julf.com</a>>, <a href="mailto:benakin@gmail.com" target="_blank">benakin@gmail.com</a> <br>
<<a href="mailto:benakin@gmail.com" target="_blank">benakin@gmail.com</a>>, <a href="mailto:jumaropi@yahoo.com" target="_blank">jumaropi@yahoo.com</a> <<a href="mailto:jumaropi@yahoo.com" target="_blank">jumaropi@yahoo.com</a>>, <br>
<a href="mailto:mcknight.glenn@gmail.com" target="_blank">mcknight.glenn@gmail.com</a> <<a href="mailto:mcknight.glenn@gmail.com" target="_blank">mcknight.glenn@gmail.com</a>><br>
CC: Carlos Reyes <<a href="mailto:carlos.reyes@icann.org" target="_blank">carlos.reyes@icann.org</a>>, Michelle Bright <br>
<<a href="mailto:michelle.bright@icann.org" target="_blank">michelle.bright@icann.org</a>>, Board Ops Team <<a href="mailto:board-ops-team@icann.org" target="_blank">board-ops-team@icann.org</a>>, <br>
Mary Wong <<a href="mailto:mary.wong@icann.org" target="_blank">mary.wong@icann.org</a>>, David Olive <<a href="mailto:david.olive@icann.org" target="_blank">david.olive@icann.org</a>><br>
<br>
<br>
<br>
/Sent on behalf of Tripti Sinha, Chair, ICANN Board of Directors///<br>
<br>
DearNon/c//ommercial Stakeholder Group///Leaders,<br>
<br>
**Please reply no later than Wednesday 21 February 2024**<br>
<br>
The Board and I are very much looking forward to meeting with you All, <br>
in Puerto Rico, for ICANN79 (02-07 March).<br>
<br>
It will be our first meeting of 2024, another important and exciting <br>
year for ICANN as we continue to work together on multiple fronts: the <br>
first phase of applications to the ICANN Grant Program to be opened in <br>
the forthcoming weeks, the new five-year Strategic Plan currently being <br>
drafted and of course the Next Round of new gTLDs, to name a few.<br>
<br>
As announced last year, wehave also continued working on enhancing our <br>
partnership with the community. For the upcoming ICANN Public Meeting <br>
(ICANN79),the Board is planning to hold an open engagement session, <br>
which we hope will be another opportunity for interested community <br>
members to engage directly with the Board on specific topics. *This <br>
session will be part of ICANN79 Prep week and will be held on Wednesday <br>
21 February at 16:30 UTC.*<br>
<br>
This 60-minute engagement session will include three breakout rooms <br>
hosted by different Board members, each covering a different topic. <br>
Following a brief welcome plenary, community members will be asked to <br>
join one of the three breakout rooms for a 40-minute discussion with the <br>
Board hosts for that topic. Attendees will be able to move freely <br>
between the three breakout rooms. The session will conclude with all <br>
attendees coming together to hear each Board host’s summary of the <br>
discussions in their respective breakout rooms.<br>
<br>
**<br>
<br>
*Topic 1: FY26-30 Strategic Planning*<br>
<br>
•Led by Maarten Botterman and Chris Buckridge<br>
<br>
•Format of the engagement: discussion and soliciting input<br>
<br>
•Description: In this breakout room, the Board hosts will seek input <br>
from attendees on how the input from the community – including through <br>
the various environmental scans, strategic trend outlook sessions and <br>
other consultations – can form the basis of the strategic objectives and <br>
goals for the next Five-Year Strategic Plan, and what metrics should be <br>
included as part of the Plan.<br>
<br>
*Topic 2**:**The Board’s Role & Responsibilities **w**hen Board-Adopted <br>
Policies Do Not Address the Problems They Were Developed to Solve*<br>
<br>
• Led by Becky Burr and Alan Barrett<br>
<br>
• Format of the engagement: discussion and input<br>
<br>
• Description: In this breakout room, the Board hosts will <br>
invite community feedback on how to handle situations where it becomes <br>
clear that community-developed gTLD policies adopted by the Board are <br>
superseded by subsequent events or are otherwise not able to, or can no <br>
longer, resolve the problems they were designed to address. There is <br>
currently no Bylaw or process for such a circumstance, other than the <br>
Board requesting that the community initiate another full policy <br>
development process. As the Board continues to engage with the GNSO on <br>
this topic, the community is invited to brainstorm possible solutions.<br>
<br>
*Topic 3: Environmental Sustainability at ICANN*<br>
<br>
• Led by Sally Costerton and León Sanchez<br>
<br>
• Format of the engagement: discussion and soliciting input<br>
<br>
• Description: In this breakout room, the Board hosts will <br>
solicit community input on how to best advance ICANN’s environmental <br>
sustainability efforts, in line with FY24 CEO Goal 8. Drawing on the <br>
expertise of the community will help shape the dialogue for more <br>
sustainable planning for ICANN meetings and operations.<br>
<br>
The Board is very much looking forward to this new engagement <br>
opportunity and hopes that you will participate actively.<br>
<br>
It is to be noted that there will be technical limitations to the use of <br>
breakout rooms such as: no translation or transcription services <br>
available. Yet the ICANN Staff will support this engagement session and <br>
take notes. If this experiment is successful, we could replicate it <br>
moving forward.<br>
<br>
Meanwhile though, it is important that we continue listening to your <br>
specific needsduring our bilateral sessionsand we are also therefore <br>
keeping to the practice of asking questionsto _your_Group ahead of our <br>
joint session in Puerto Rico:<br>
<br>
*- There is an ICANN CEO goal to have the organization develop and <br>
implement a communications and engagement strategy to address the WSIS <br>
20-year review - what are the NCSG’s views on ICANN engagement <br>
priorities and strategies in this space?<br>
<br>
- Engagement with between groups and bodies in the ICANN space is <br>
continuing to evolve, including with the introduction of session in the <br>
Prep Week and breakout rooms on specific issues of current interest - <br>
does the NCSG have views on these new approaches or how to continue <br>
improving engagement strategies?*<br>
<br>
<br>
We look forward to hearing your thoughts on this soon.<br>
<br>
We would be grateful if you could send to Board Operations <br>
(<a href="mailto:board-ops-team@icann.org" target="_blank">board-ops-team@icann.org</a> <mailto:<a href="mailto:board-ops-team@icann.org" target="_blank">board-ops-team@icann.org</a>>) the <br>
questions you would like the Board to address during our face-to-face <br>
meetings. Given the finite time available for these meetings, please <br>
list your questions in order of priority.We would also appreciate <br>
getting your questions no later than *_Wednesday 21 February, 2024_*.<br>
<br>
Looking forward to engaging discussions during Prep Week and ICANN79!<br>
<br>
Best regards,<br>
<br>
Tripti Sinha<br>
<br>
Chair, ICANN Board of Directors<br>
<br>
_______________________________________________<br>
NCSG-EC mailing list<br>
<a href="mailto:NCSG-EC@lists.ncsg.is" target="_blank">NCSG-EC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-ec" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-ec</a><br>
</blockquote></div>