<div dir="ltr"><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small">+1 to move the SubPro IRT liaison item to the agenda. <br></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small">I support Anne's proposal of 2 liaisons. If my memories serve me right, Board used to have 2 liaisons for the EPDP Phase 1, 2 and 2A. I don't see why we can't do the same, especially regarding such complicated PDP as SubPro.</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small">Best,</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small">Manju</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 19, 2023 at 4:06 AM Stephanie E Perrin via council <<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</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">
<div>
<p>I certainly hope that we will have a full discussion of this
issue next week at the Council meeting. We have raise quite a few
reasons why this liaison position is unusual and extremely
important:</p>
<ul>
<li>we wish to proceed with speed, yet there are many complex
issues which will raise policy concerns that have not been
developed to the point of precise direction, so they may have to
return to Council. The liaison will play a key role in ensuring
this happens, hence the need for Council to discuss and choose
that liaison. It's a critical role, so I like the idea of
having 2 co-liaisons, provides different perspectives and some
backup (as this IRT is expected to be a slog)</li>
<li>the speed thing....the pace may be too much for one rep to
cope with</li>
<li>policy vs implementation expertise (my personal favorite). It
is Council's job to ensure policy issues return in a timely
manner for examination, in order that (in the interests of
speed) we do not paper over the cracks in our less specific
language, and proceed to implement in areas which still require
some precision in policy, We need to discuss that expertise,
what we are looking for etc</li>
</ul>
<p>Could we please move this item up in the agenda. I don't wish to
whine as a North American who usually does not have to put up with
Middle-of-the-night meetings, but the meeting next week happens to
be at 1am EDT, 11pm PDT, I fear we may lose a lot of North
Americans as the night goes on. Apologies to our Asia-Pacific
members, I know you suffer all the time.</p>
<p>Cheers Stephanie Perrin<br>
</p>
<div>On 2023-05-16 10:27 a.m., Anne ICANN
via council wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Thanks Jeff. Having just participated in the first
IRT meeting, I think we can all acknowledge that there is a huge
amount of work to be done here. ICANN Org staff (Lars) is
projecting 24 months to get to a final AGB. We all want to work
more quickly than that and there is some thought being given to
having some separate "work streams" in the work plan for the IRT
so that work can be accomplished in parallel. There appears to
be sufficient staff assigned by Org to accommodate this
approach.
<div><br>
</div>
<div>It seems to me that Susan and I could potentially work
together to assume Council Liaison responsibilities to cover
different Final Report Topics. I believe there are certain
topics more easily covered by Susan and certain topics more
easily covered by me. For example, I would always defer to
Susan on RSP Evaluation issues and any issues relating
directly to registry and registrar operations. On the other
hand, I am in a strong position to manage communication in
relation Registry Voluntary Commitments (having participated
on that panel in the past at an ICANN meeting) and on other
issues such as Name Collisions where I have been active on the
Discussion Group for years. (Again, I am retired with no
client interests to advance and my overriding interest is
ICANN organizational effectiveness.)</div>
<div><br>
</div>
<div>For a Work Plan this big, it would be nice to have some
redundancy in the Council Liaison position. I think Susan and
I are well able to collaborate and work together as
Co-Liaisons to the Sub Pro IRT. So after grasping the scope
and the timelines in the first IRT meeting, I would propose
that Council and Leadership consider appointing both of us and
dividing the topics. That division might go along lines to be
determined based on the IRT Work Plan that is adopted by Org.</div>
<div><br>
</div>
<div>Maybe a new approach of "Co-Liaisons" would work best given
that we have two volunteers and a huge number of topics to be
covered. I honestly think Susan and I could work this out and
submit a plan for Council approval.</div>
<div><br>
</div>
<div>Anne<br clear="all">
<div>
<div dir="ltr">
<div dir="ltr">
<div>Anne Aikman-Scalese</div>
GNSO Councilor
<div>NomCom Non-Voting 2022-2024</div>
<div><a href="mailto:anneicanngnso@gmail.com" target="_blank">anneicanngnso@gmail.com</a></div>
</div>
</div>
</div>
<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, May 15, 2023 at
3:20 PM <a href="mailto:jeff@jjnsolutions.com" target="_blank">jeff@jjnsolutions.com</a>
<<a href="mailto:jeff@jjnsolutions.com" target="_blank">jeff@jjnsolutions.com</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">
<div>
<div>
<div>Just to add, and Steve/anyone else feel free to
correct me....</div>
<div><br>
</div>
<div>But I believe the GNSO Liaison to the ODP Role went
to the Standing Selection Committee because it is was
specifically stated that the Liaison did not have to be
a Councilor. However, the Council Liaison to a WG or
IRT (or I guess a GGP) must be a Councilor. Therefore,
the normal Council ways of selecting people apply (and
that is not through the SSC).</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div id="m_8079198827521838285m_-4191649866557523977signature_old" style="clear:both">
<div><br>
</div>
<img src="cid:18831f9ab62886f05a51" border="0"></div>
<div style="clear:both"><br>
</div>
<div><br>
</div>
<div>
<div>------ Original Message ------</div>
<div>From "Steve Chan via council" <<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>></div>
<div>To "Anne ICANN" <<a href="mailto:anneicanngnso@gmail.com" target="_blank">anneicanngnso@gmail.com</a>>;
"Terri Agnew" <<a href="mailto:terri.agnew@icann.org" target="_blank">terri.agnew@icann.org</a>></div>
<div>Cc "<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>"
<<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>>;
"<a href="mailto:liaison6c@gnso.icann.org" target="_blank">liaison6c@gnso.icann.org</a>"
<<a href="mailto:liaison6c@gnso.icann.org" target="_blank">liaison6c@gnso.icann.org</a>>;
"<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>"
<<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>></div>
<div>Date 5/15/2023 5:17:18 PM</div>
<div>Subject Re: [council] Proposed Agenda | GNSO
Council Meeting | Thursday, 25 May 2023</div>
</div>
<div><br>
</div>
<div id="m_8079198827521838285m_-4191649866557523977x33fa5b527da8478">
<blockquote cite="http://1083BCB2-5926-4AC4-9FB1-89A3D8524F28@icann.org" type="cite">
<div>
<p class="MsoNormal">Dear Anne, all,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">To date, the Council has not
relied upon formal procedures to select its
liaisons to either WGs or IRTs as there is almost
always just a single volunteer (or in some cases
none, which requires some prodding and cajoling).
I think the concern here with running through an
Expressions of Interest process, to then be
followed by a Standing Selection Process, is that
they both take time and likely run into the issue
you have identified – the IRT is beginning its
work. That said, my understanding is that at least
the first couple of IRT meetings will be
administrative in nature and that given the
liaison’s role in an IRT is primarily for
escalating disagreements between ICANN org’s
proposed implementation versus WG intent, there
will be little to nothing that requires the
services of the liaison in the early stages . In
other words, the Council should have some time
still to identify its liaison to the IRT.
</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I believe Council leadership is
talking through options and I anticipate that they
will come back to the Council list with a
suggested path forward.
</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Best,</p>
<p class="MsoNormal">Steve</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12pt">From: </span></b><span style="font-size:12pt">council <<a href="mailto:council-bounces@gnso.icann.org" target="_blank">council-bounces@gnso.icann.org</a>>
on behalf of Anne ICANN via council <<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>><br>
<b>Reply-To: </b>Anne ICANN <<a href="mailto:anneicanngnso@gmail.com" target="_blank">anneicanngnso@gmail.com</a>><br>
<b>Date: </b>Monday, May 15, 2023 at 1:53 PM<br>
<b>To: </b>Terri Agnew <<a href="mailto:terri.agnew@icann.org" target="_blank">terri.agnew@icann.org</a>><br>
<b>Cc: </b>"<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>"
<<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>>,
"<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>"
<<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>>,
"<a href="mailto:liaison6c@gnso.icann.org" target="_blank">liaison6c@gnso.icann.org</a>"
<<a href="mailto:liaison6c@gnso.icann.org" target="_blank">liaison6c@gnso.icann.org</a>><br>
<b>Subject: </b>Re: [council] Proposed Agenda
| GNSO Council Meeting | Thursday, 25 May 2023</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Thanks Terri - what is
missing from this agenda is a way forward for
Council to designate a Council Liaison to the
Sub Pro IRT. This work is upon us.
Accordingly, I'll make a Motion to send the task
of naming the Council Liaison to the Standing
Selection Committee with Expression of Interest
to be drafted by staff. (I noticed that this
was how the Council Liaison to the Sub Pro ODP
was handled.)
</p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">I've been asking to get
this on the agenda in some manner since
Friday. I have not heard back from anyone in
Leadership on this topic but would hope to get
a second on the motion. I'll need help from
staff drafting the form of the Motion. </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><span style="color:blue">e.g.
RESOLVED, Council directs staff to prepare
an Expression of Interest form for
volunteers to serve in the role of Council
Liaison to the Subsequent Procedures
Implementation Review Team and to assign the
task of recommending the designated
individual to the Standing Selection
Committee to be acted upon as soon as
feasible with a target date of Day Zero at
ICANN 77 for Council action on the SSC
Recommendation.
</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Thank you,</p>
</div>
<div>
<p class="MsoNormal">Anne<br clear="all">
</p>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Anne Aikman-Scalese</p>
</div>
<p class="MsoNormal">GNSO Councilor </p>
<div>
<p class="MsoNormal">NomCom Non-Voting
2022-2024</p>
</div>
<div>
<p class="MsoNormal"><a href="mailto:anneicanngnso@gmail.com" target="_blank">anneicanngnso@gmail.com</a></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"> </p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal">On Mon, May 15, 2023 at
11:20 AM Terri Agnew via council <<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>>
wrote:</p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<div id="m_8079198827521838285m_-4191649866557523977m_-920863599612499619divtagdefaultwrapper">
<div id="m_8079198827521838285m_-4191649866557523977m_-920863599612499619Signature">
<div id="m_8079198827521838285m_-4191649866557523977m_-920863599612499619divtagdefaultwrapper">
<p style="margin:0in">Dear all,</p>
<p style="margin:0in;font-variant-caps:normal;text-align:start;word-spacing:0px">
<b> </b></p>
<p style="margin:0in;font-variant-caps:normal;text-align:start;word-spacing:0px">
Please find below the final
proposed <span><span style="background:white">agenda</span></span> for
the<span> </span><span>GNSO
Council Meeting </span>on
Thursday, 25 May 2023 at 05:00 UTC</p>
</div>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal">Please note that
all documents referenced in the agenda
have been gathered on a Wiki page for
convenience and easier access:
<a href="https://community.icann.org/x/wIBXDg" target="_blank"><span style="color:rgb(17,85,204)">https://community.icann.org/x/wIBXDg</span></a>. </p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal">This agenda was
established according to the<a href="https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-24oct19-en.pdf__;!!PtGJab4!78u329nw-weEZWQe7wWMMQcMy9H1eLVkNk81khJQ2TAIGydeTelKsUlCJ6O9nbxZvaJD1cyfleD8GzMLMCuNJGACTSk$" target="_blank"><span style="color:black">
</span><span style="color:rgb(17,85,204)">GNSO
Operating Procedures</span>
[gnso.icann.org]</a> v3.5, updated
on 24 October 2019.</p>
<p class="MsoNormal">For convenience:</p>
<ul type="disc">
<li class="MsoNormal" style="color:black;vertical-align:baseline">
An excerpt of the ICANN Bylaws
defining the voting thresholds is
provided in Appendix 1 at the end of
this agenda.</li>
<li class="MsoNormal" style="color:black;vertical-align:baseline">
An excerpt from the Council
Operating Procedures defining the
absentee voting procedures is
provided in Appendix 2 at the end of
this agenda.</li>
</ul>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal">GNSO Council
meeting on Thursday, 25 May at 05:00
UTC:
<a href="https://urldefense.com/v3/__https:/tinyurl.com/ye2a6jyh__;!!PtGJab4!78u329nw-weEZWQe7wWMMQcMy9H1eLVkNk81khJQ2TAIGydeTelKsUlCJ6O9nbxZvaJD1cyfleD8GzMLMCuNRJe0g0w$" target="_blank"><span style="color:rgb(17,85,204)">https://tinyurl.com/ye2a6jyh</span>
[tinyurl.com]</a>. </p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal">(Wednesday) 22:00
Los Angeles; 01:00 Washington DC;
06:00 London; 07:00 Paris; 08:00
Moscow; 15:00 Melbourne </p>
<p class="MsoNormal" style="background:white">
<b> </b></p>
<p class="MsoNormal" style="background:white">
<b>GNSO Council Meeting Remote
Participation:<span style="color:blue">
</span></b><span><a href="https://urldefense.com/v3/__https:/icann.zoom.us/j/97891627902?pwd=RURCTitiNEVwd2UySEk1QkRESmlFZz09__;!!PtGJab4!78u329nw-weEZWQe7wWMMQcMy9H1eLVkNk81khJQ2TAIGydeTelKsUlCJ6O9nbxZvaJD1cyfleD8GzMLMCuNSzOV0_E$" target="_blank"><b><span style="font-size:12pt;color:rgb(5,99,193)">https://icann.zoom.us/j/97891627902?pwd=RURCTitiNEVwd2UySEk1QkRESmlFZz09</span></b>
[icann.zoom.us]</a><b><span style="background:yellow"> </span></b></span></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal" style="background:white">
<span>Councilors should notify the
GNSO Secretariat in advance if they
will not be able to attend and/or
need a dial out call.</span></p>
<p class="MsoNormal">___________________________________</p>
<p class="MsoNormal" style="background:white">
<b>Item 1: Administrative Matters (5
minutes)</b></p>
<p class="MsoNormal" style="background:white">
<span>1.1 - Roll Call</span></p>
<p class="MsoNormal" style="background:white">
<span>1.2 - Updates to Statements of
Interest</span></p>
<p class="MsoNormal" style="background:white">
<span>1.3 - Review / Amend Agenda</span></p>
<p class="MsoNormal" style="background:white">
<span>1.4 - Note the status of minutes
for the previous Council meetings
per the GNSO Operating Procedures: .</span></p>
<p class="MsoNormal" style="background:white">
<span><a href="https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy/2023/minutes/minutes-gnso-council-15mar23-en.pdf__;!!PtGJab4!78u329nw-weEZWQe7wWMMQcMy9H1eLVkNk81khJQ2TAIGydeTelKsUlCJ6O9nbxZvaJD1cyfleD8GzMLMCuNyVhsQQs$" target="_blank"><span style="color:rgb(17,85,204)">Minutes</span>
[gnso.icann.org]</a> of the GNSO
Council meeting on 15 March 2023
were posted on 30 March 2023.</span></p>
<p class="MsoNormal" style="background:white">
<span><a href="https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy/2023/minutes/minutes-gnso-council-20apr23-en.pdf__;!!PtGJab4!78u329nw-weEZWQe7wWMMQcMy9H1eLVkNk81khJQ2TAIGydeTelKsUlCJ6O9nbxZvaJD1cyfleD8GzMLMCuNB1Y19xQ$" target="_blank"><span style="color:rgb(17,85,204);background:white">Minutes</span>
[gnso.icann.org]</a><span style="background:white"> </span>of
the GNSO Council meeting on 20 April
2023 were posted on 07 May 2023.</span></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal" style="background:white">
<b>Item 2: Opening Remarks / Review of
Projects & Action List (5
minutes)</b></p>
<p class="MsoNormal" style="background:white">
<span>2.1 - Review focus areas and
provide updates on specific key
themes / topics, to include review
of<a href="https://urldefense.com/v3/__https:/gnso.icann.org/en/council/project__;!!PtGJab4!78u329nw-weEZWQe7wWMMQcMy9H1eLVkNk81khJQ2TAIGydeTelKsUlCJ6O9nbxZvaJD1cyfleD8GzMLMCuNUESHcxA$" target="_blank"><span style="color:black">
</span><span style="color:rgb(0,82,204)">Projects
List</span> [gnso.icann.org]</a></span><u><span style="color:rgb(0,82,204)">
</span></u><span style="color:rgb(23,43,77)">and</span><span><a href="https://community.icann.org/x/RgZlAg" target="_blank"><span style="color:rgb(23,43,77)">
</span><span style="color:rgb(0,82,204)">Action
Item List. </span></a></span></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal" style="background:white">
<b>Item 3: Consent Agenda (0 minutes) </b></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal" style="background:white">
<b>Item 4: Board request for Council
input on Nominating Committee
(NomCom) rebalancing (15 minutes)</b></p>
<p class="MsoNormal" style="background:white">
<span>On 26 April 2023, the ICANN
Board <a href="https://www.icann.org/en/system/files/correspondence/sinha-to-ducos-26apr23-en.pdf" target="_blank">
<span style="color:rgb(17,85,204)">requested</span></a>
the input of the GNSO Council on the
issue of NomCom rebalancing. </span></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal" style="background:white">
<span>The NomCom is a committee tasked
with selecting key ICANN leadership
positions, including some members of
the ICANN Board of Directors and the
Public Technical Identifiers (PTI)
Board, as well as other positions
within the ICANN community. The
NomCom functions independently from
the Board, the Supporting
Organizations (SOs) and Advisory
Committees (ACs). NomCom delegates
act on behalf of the interests of
the global Internet community and
within the scope of the ICANN
mission and responsibilities
assigned to the NomCom under the
ICANN Bylaws – they do not act in
furtherance of the group that
appointed them to the NomCom.
</span></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal" style="background:white">
<span>The ICANN community has been
discussing the issue of rebalancing
the NomCom for over 10 years, and
the ICANN Board resolved to engage
with the ICANN community to better
understand community views on the
rebalancing.</span></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal" style="background:white">
<span>Specifically, the Board is
seeking input on the following
questions:</span></p>
<ol style="margin-top:0in" type="1" start="1">
<li class="MsoNormal" style="color:black;margin-top:8pt;background:white;vertical-align:baseline">What
does it mean to have a balanced
NomCom at a point in time? For
example, what criteria would you
apply to measure or assess whether
the NomCom is balanced? And further,
how can one test whether or not the
NomCom is balanced?</li>
<li class="MsoNormal" style="color:black;background:white;vertical-align:baseline">
Do you support the view that the
current composition of the NomCom
needs to be rebalanced? Please
explain why or why not.</li>
<li class="MsoNormal" style="color:black;background:white;vertical-align:baseline">
How frequently does the balance need
to be measured or assessed?</li>
<li class="MsoNormal" style="color:black;background:white;vertical-align:baseline">
How do you suggest that the NomCom’s
composition be rebalanced?</li>
<li class="MsoNormal" style="color:black;background:white;vertical-align:baseline">
Who should conduct this work, and
how should it be conducted?</li>
<li class="MsoNormal" style="color:black;background:white;vertical-align:baseline">
How would your community group
prioritize consideration of this
issue within your planning efforts? </li>
</ol>
<p class="MsoNormal" style="margin-top:8pt;background:white">
<span>Here, the Council will discuss
the questions from the Board and
determine whether it would like to
provide input.</span></p>
<p class="MsoNormal" style="background:white">
<span>4.1 Introduction of topic
(Katrina Sataki, Chair of
Organizational Effectiveness
Committee of the Board (OEC))</span></p>
<p class="MsoNormal" style="background:white">
<span>4.2 Council discussion</span></p>
<p class="MsoNormal" style="background:white">
<span>4.3 Next steps </span></p>
<p class="MsoNormal" style="background:white">
<span>
</span></p>
<p class="MsoNormal" style="background:white">
<b>Item 5: COUNCIL DISCUSSION - SubPro
- Progress Update on Recommendations
Marked as Pending (15 minutes)</b></p>
<p class="MsoNormal" style="background:white">
<span>During its informal session at
ICANN76 and the subsequent Council
meeting, the Council
<a href="https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy/2023/minutes/minutes-gnso-council-15mar23-en.pdf__;!!PtGJab4!78u329nw-weEZWQe7wWMMQcMy9H1eLVkNk81khJQ2TAIGydeTelKsUlCJ6O9nbxZvaJD1cyfleD8GzMLMCuNyVhsQQs$" target="_blank">
<span style="color:rgb(17,85,204)">discussed
and agreed</span>
[gnso.icann.org]</a> to task a
small team of interested councilors
to review the recommendations that
the Board placed in a pending status
and suggest to the full Council how
the underlying concerns that caused
the pending status can be best
addressed (i.e., a limited triage
exercise). Interested Councilors
were asked to volunteer for the
Small Team by 15 March 2023.
</span></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal" style="background:white">
<span>Since ICANN76, the Council
SubPro Small Team has met several
times and has completed an initial
run through of the issues chart,
with Board member input on why the
Board placed specific
recommendations into a pending
status. The Council discussed the
main output of that triage effort,
the proposed paths forward for each
pending recommendation, during an
Extraordinary Meeting on 4 May.
During that meeting, the Council
agreed to further task the small
team with taking interim steps
(e.g., provision is clarifying
information, developing speaking
points) in order to support the
Council’s dialogue with the ICANN
Board on 22 May.
</span></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal" style="background:white">
<span>Here, the Council will debrief
after the dialogue with the ICANN
Board and discuss next steps to
ensure that the Council is able to
deliver its plan and timeline to
resolve the pending recommendations.</span></p>
<p class="MsoNormal" style="background:white">
<span>5.1 – Introduction of topic
(Paul McGrady, Small Team Lead) </span></p>
<p class="MsoNormal" style="background:white">
<span>5.2 – Council discussion</span></p>
<p class="MsoNormal" style="background:white">
<span>5.3 – Next steps</span></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal" style="background:white">
<b>Item 6: COUNCIL DISCUSSION -
Internationalized Domain Names
(IDNs) EPDP Timeline (20 minutes)</b></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal" style="margin-bottom:12pt">On 20 May
2021, the GNSO Council approved the<a href="https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy/2021/presentation/EPDPInitiationRequest20May21.pdf__;!!PtGJab4!78u329nw-weEZWQe7wWMMQcMy9H1eLVkNk81khJQ2TAIGydeTelKsUlCJ6O9nbxZvaJD1cyfleD8GzMLMCuN2IQuo1g$" target="_blank"><span style="color:black">
</span><span style="color:rgb(17,85,204)">initiation
request</span> [gnso.icann.org]</a><span style="color:rgb(17,85,204)">
</span>for the EPDP on
Internationalized Domain Names (IDNs)
and adopted its<a href="https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/policy/2021/presentation/CharterGNSOIDNsEPDPWorkingGroup20May21.pdf__;!!PtGJab4!78u329nw-weEZWQe7wWMMQcMy9H1eLVkNk81khJQ2TAIGydeTelKsUlCJ6O9nbxZvaJD1cyfleD8GzMLMCuNXrae-nc$" target="_blank"><span style="color:black">
</span><span style="color:rgb(17,85,204)">charter</span>
[gnso.icann.org]</a>. The EPDP Team
is expected to: </p>
<p class="MsoNormal" style="margin-left:0.75in;vertical-align:baseline">
<span style="font-size:10pt;font-family:Symbol">·</span><span style="font-size:7pt;font-family:"Times New Roman",serif">
</span>Determine the approach for a
consistent definition of all gTLDs;
and </p>
<p class="MsoNormal" style="margin-left:0.75in;vertical-align:baseline">
<span style="font-size:10pt;font-family:Symbol">·</span><span style="font-size:7pt;font-family:"Times New Roman",serif">
</span>Develop policy recommendations
that will eventually allow for the
introduction of variant gTLDs at the
top-level </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">On 24 April 2023,
the EPDP Team published its Phase 1
Initial Report for
<a href="https://www.icann.org/en/public-comment/proceeding/phase-1-initial-report-on-the-internationalized-domain-names-epdp-24-04-2023" target="_blank"><span style="color:rgb(17,85,204)">Public
Comment</span></a>. The Initial
Report includes 68 preliminary
recommendations covering issues
pertaining to gTLD variant definition
and management at the top-level. The
majority of the preliminary
recommendations aim to operationalize
SubPro PDP Outputs in order to allow
for future applications of gTLD
variant labels through the New gTLD
Program.
</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">On 16 March 2023,
the ICANN Board requested the EPDP
Team to deliver an updated project
plan by the last day of ICANN77 that
identifies all charter questions that
will impact the next Applicant
Guidebook, as well as a timeline for
the EPDP Team’s delivery of relevant
recommendations to the GNSO Council.
While the Public Comment proceeding is
ongoing, the EPDP Team started
discussion of its Phase 2 work, which
focuses on issues pertaining to
second-level IDN variant management,
as well as the review of its project
plan in accordance with the Board
request.
</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Here, the GNSO
Council will hear an update on the
EPDP Team’s analysis of its Phase 2
charter questions in relation to the
impact on the next Applicant
Guidebook, as well as a draft project
plan and timeline for the EPDP Team’s
delivery of relevant recommendations
to the GNSO Council.
</p>
<p class="MsoNormal" style="background:white">
<span>6.1 Introduction of topic (Donna
Austin, EPDP Chair)</span></p>
<p class="MsoNormal" style="background:white">
<span>6.2 Council Discussion</span></p>
<p class="MsoNormal" style="background:white">
<span>6.3 Next Steps </span></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal" style="background:white">
<b>Item 7 - COUNCIL DISCUSSION - Work
to Prepare Draft Timeline for Closed
Generics Policy Process (20
minutes)</b></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal" style="background:white">
<span>In March 2023, the ICANN Board
requested that the GAC and GNSO
Council consider engaging in a
facilitated dialogue to develop a
framework for further GNSO policy
work on the issue of Closed
Generics. The GAC and GNSO Council
agreed to the Board’s suggestion and
each appointed six participants for
the dialogue. One participant and
one alternate from the ALAC were
also appointed. Should the GAC-GNSO
facilitated dialogue result in an
agreed framework, the agreements
will be further developed through
the appropriate GNSO policy process.
</span></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal" style="background:white">
<span>Following an initial, informal
meeting at ICANN75 in Kuala Lumpur,
the dialogue participants have since
been meeting regularly via Zoom and
held a substantive two-day
face-to-face meeting in Washington,
D.C. in late January 2023. The
dialogue is hoping to deliver a
draft framework around the end of
May 2023 to the ALAC, GAC, GNSO and
other SOACs for community input.
Groups are expected to have
approximately four weeks to review
that document.
</span></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal" style="background:white">
<span>During its meeting at ICANN76,
the ICANN Board passed a
<a href="https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-16-03-2023-en" target="_blank">
<span style="color:rgb(17,85,204)">resolution</span></a>
adopting a substantial portion of
the outputs from the New gTLD
Subsequent Procedures PDP, setting
in motion the start of the
implementation process for the next
round of new gTLDs. As part of the
resolution, the Board established
deadlines for key deliverables that
will impact the development of the
implementation plan. By 15 June
2023, the Board expects to receive
“A GNSO Council project plan and
timeline for policy work, or an
alternate path, on how to handle
closed generics for the next round
of new gTLDs.”
</span></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal" style="background:white">
<span>Here the Council will discuss
the draft scope of subsequent policy
work to inform preparation of the
timeline for this work.</span></p>
<p class="MsoNormal" style="background:white">
<span>7.1 Introduction of topic (John
McElwaine, Council Vice-Chair)</span></p>
<p class="MsoNormal" style="background:white">
<span>7.2 Council Discussion</span></p>
<p class="MsoNormal" style="background:white">
<span>7.3 Next Steps </span></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal" style="background:white">
<b>Item 8: EPDP Phase 2 Small Team
Progress Update (20 minutes)</b></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal">In February 2023,
the ICANN Board
<a href="https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-special-meeting-of-the-icann-board-27-02-2023-en#section2" target="_blank"><span style="color:rgb(17,85,204)">directed</span></a>
ICANN org <span style="background:rgb(254,254,254)">to
develop and launch the WHOIS
Disclosure System, now called the
Registration Data Request Service
(RDRS), as requested by the GNSO
Council. The Board requested the
RDRS be launched within 11 months,
and, prior to the launch, the Board
recommended Org continue its
engagement with the GNSO Council on
the implementation. The ICANN Board
also requested the GNSO Council to
establish success criteria for the
RDRS. In response, the GNSO Council
updated the
</span><a href="https://community.icann.org/x/PAoiCw" target="_blank"><span style="color:rgb(17,85,204);background:rgb(254,254,254)">assignment</span></a><span style="background:rgb(254,254,254)">
of the EPDP Phase 2 small team to
reflect these new work items. </span></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="background:rgb(254,254,254)">The
small team is expected to engage
with ICANN org throughout the
development and operation of the
System, and in particular consider:</span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:rgb(23,43,77);margin-top:8pt;background:white;vertical-align:baseline"><span style="color:black;background:rgb(254,254,254)">The other topics
identified in the addendum that
the small team did not consider
gating factors but for which it
would be interested to have
further discussions with ICANN org
during the implementation phase to
consider if/how some of these
aspects could be considered to be
added in the current
implementation of [the RDRS] or a
future version;
</span></li>
<li class="MsoNormal" style="color:rgb(23,43,77);background:white;vertical-align:baseline">
<span style="color:black;background:rgb(254,254,254)">Success
criteria for this System, which
should include analysis of
relevant usage data;</span></li>
<li class="MsoNormal" style="color:rgb(23,43,77);background:white;vertical-align:baseline">
<span style="color:black;background:rgb(254,254,254)">How
to best promote and secure
comprehensive use of the system,
both by potential requestors as
well as ICANN accredited
registrars.</span></li>
</ul>
<p class="MsoNormal" style="margin-top:8pt;background:white">
<span style="background:rgb(254,254,254)">In
addition, the small team is expected
to provide the Council with a
recommendation on the approach and
format through which, following
implementation of the system, data
should be reviewed and analyzed to
help inform subsequent decisions on
how to proceed with the SSAD
recommendations. The small team is
expected to provide regular updates
to the GNSO Council on the state of
its progress.
</span></p>
<p class="MsoNormal" style="margin-top:8pt;background:white">
<span> </span></p>
<p class="MsoNormal" style="background:white">
<span style="background:rgb(254,254,254)">Here,
the Council will receive an update
from the EPDP Phase 2 small team on
its progress on defining the success
criteria of the RDRS.</span></p>
<p class="MsoNormal" style="background:white">
<span>8.1 Introduction of topic
(Sebastien Ducos, Small Team Chair)</span></p>
<p class="MsoNormal" style="background:white">
<span>8.2 Council Discussion</span></p>
<p class="MsoNormal" style="background:white">
<span>8.3 Next Steps</span></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal" style="background:white">
<b>Item 9: ANY OTHER BUSINESS (20
minutes)</b></p>
<p class="MsoNormal" style="background:white">
<span>9.1 ICANN77 Day 0 SubPro Session
Planning (Steve Chan)</span></p>
<p class="MsoNormal" style="background:white">
<span>9.2 Accuracy (Marika Konings)</span></p>
<p class="MsoNormal" style="background:white">
<span>9.3 State of Progress from Small
team on DNS Abuse (Mark Datysgeld)</span></p>
<p class="MsoNormal" style="background:white">
<span>9.4 WS2 Framework of
Interpretation for Human Rights
Proposed updates to GNSO Council
templates (Marika Konings)</span></p>
<p class="MsoNormal" style="background:white">
<span> </span></p>
<p class="MsoNormal">_______________________________</p>
<p class="MsoNormal">Appendix 1: GNSO
Council Voting Thresholds (ICANN
Bylaws, Article 11, Section 11.3(i))</p>
<p class="MsoNormal">See<a href="https://www.icann.org/resources/pages/governance/bylaws-en/#article11" target="_blank"><span style="color:black">
</span><span style="color:rgb(17,85,204)">https://www.icann.org/resources/pages/governance/bylaws-en/#article11</span></a>.</p>
<p class="MsoNormal">Appendix 2: GNSO
Council Absentee Voting Procedures
(GNSO Operating Procedures, Section
4.4)</p>
<p class="MsoNormal">See<a href="https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-30jan18-en.pdf__;!!PtGJab4!78u329nw-weEZWQe7wWMMQcMy9H1eLVkNk81khJQ2TAIGydeTelKsUlCJ6O9nbxZvaJD1cyfleD8GzMLMCuN1UnoqcY$" target="_blank"><span style="color:black">
</span><span style="color:rgb(17,85,204)">https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-30jan18-en.pdf</span>
[gnso.icann.org]</a></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><b>References for
Coordinated Universal Time of 05:00
UTC</b> </p>
<p class="MsoNormal">Local time between
March and October in the NORTHERN
hemisphere</p>
<p class="MsoNormal">----------------------------------------------------------------------------</p>
<p class="MsoNormal">California, USA
(PDT) UTC-7 (Wednesday) 22:00 </p>
<p class="MsoNormal">San José, Costa
Rica (CDT) UTC-6 (Wednesday) 23:00 </p>
<p class="MsoNormal">New York/Washington
DC, USA (EDT) UTC-4 01:00</p>
<p class="MsoNormal">Buenos Aires,
Argentina (ART) UTC-3 02:00</p>
<p class="MsoNormal">Rio de Janeiro,
Brazil (BRT) UTC-3 02:00</p>
<p class="MsoNormal">London, United
Kingdom (BST) UTC+1 06:00</p>
<p class="MsoNormal">Kinshasa,
Democratic Republic of Congo (WAT)
UTC+1 06:00</p>
<p class="MsoNormal">Paris, France
(CEST) UTC+2 07:00</p>
<p class="MsoNormal">Moscow, Russia
(MSK) UTC+3 08:00</p>
<p class="MsoNormal">Singapore (SGT)
UTC+8 13:00</p>
<p class="MsoNormal">Melbourne,
Australia (AEST) UTC+10 15:00</p>
<p class="MsoNormal"> ----------------------------------------------------------------------------</p>
<p class="MsoNormal">DST starts on
Sunday 26 March 2023, 2:00 or 3:00
local time (with exceptions) for EU
countries and on Sunday 12 March 2023
for the U.S.</p>
<p class="MsoNormal">DST ends on Sunday
29 October 2023 for EU countries, and
on Sunday 05 November 2023 for the US.</p>
<p class="MsoNormal">----------------------------------------------------------------------</p>
<p class="MsoNormal">For other places
see<a href="https://urldefense.com/v3/__http:/www.timeanddate.com/__;!!PtGJab4!78u329nw-weEZWQe7wWMMQcMy9H1eLVkNk81khJQ2TAIGydeTelKsUlCJ6O9nbxZvaJD1cyfleD8GzMLMCuNa8EtFRI$" target="_blank"><span style="color:black">
</span><span style="color:rgb(17,85,204)">http://www.timeanddate.com</span>
[timeanddate.com]</a> and
<a href="https://urldefense.com/v3/__https:/tinyurl.com/ye2a6jyh__;!!PtGJab4!78u329nw-weEZWQe7wWMMQcMy9H1eLVkNk81khJQ2TAIGydeTelKsUlCJ6O9nbxZvaJD1cyfleD8GzMLMCuNRJe0g0w$" target="_blank"><span style="color:rgb(17,85,204)">https://tinyurl.com/ye2a6jyh</span>
[tinyurl.com]</a>. </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
council mailing list<br>
<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/council" target="_blank">https://mm.icann.org/mailman/listinfo/council</a><br>
<br>
_______________________________________________<br>
By submitting your personal data, you
consent to the processing of your personal
data for purposes of subscribing to this
mailing list accordance with the ICANN
Privacy Policy (<a href="https://www.icann.org/privacy/policy" target="_blank">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (
<a href="https://www.icann.org/privacy/tos" target="_blank">https://www.icann.org/privacy/tos</a>).
You can visit the Mailman link above to
change your membership status or
configuration, including unsubscribing,
setting digest-style delivery or disabling
delivery altogether (e.g., for a vacation),
and so on.
</p>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
council mailing list
<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>
<a href="https://mm.icann.org/mailman/listinfo/council" target="_blank">https://mm.icann.org/mailman/listinfo/council</a>
_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</pre>
</blockquote>
</div>
_______________________________________________<br>
council mailing list<br>
<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/council" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/council</a><br>
<br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</blockquote></div>