<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font size="+1"><font face="Lucida Grande">I rather like
Wolf-Ulrich's amendment, sets the right tone and I think
addresses Susan's concerns expeditiously.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">Stephanie</font></font><br>
</p>
<br>
<div class="moz-cite-prefix">On 2017-11-02 09:39, Wolf-Ulrich.Knoben
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:7e910d76-046b-337a-4517-3707b19cee77@t-online.de">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p>I'm fine in general with the statement. Thanks Heather and
James! Maybe to address the "button" issue a small insertion
(see attached in <b>bold</b>) could be done underlining our
understanding that it is in the community's remit to release the
button.</p>
<p>Best regards</p>
<p>Wolf-Ulrich<br>
</p>
<br>
<div class="moz-cite-prefix">Am 02.11.2017 um 15:55 schrieb Susan
Kawaguchi:<br>
</div>
<blockquote type="cite"
cite="mid:CAJjzonHj10tHx7uD+gr8oKzFNbsj3Cj+xugnSdKGoPUT6f4X7w@mail.gmail.com">
<meta http-equiv="Context-Type" content="text/html;
charset=UTF-8">
<div dir="ltr">I am concerned there is no clear call for action
regarding removing the suspension on the team. What is the
path forward for the team? Do they wait until someone else
does the following? Is the team responsible for addressing
these issues and give themselves the sign off? Does the Board
get final say or what about the SO/AC's?
<div><br>
<div><span>"address issues relating to the scope,
composition and participation, resource utilization, and
overall work plan of the Review"</span><br>
</div>
</div>
<div><span><br>
</span></div>
<div><span>Who is responsible for determining all of the above
have been addressed? If the team meets on Friday then do
they work on these issues but need oversight? </span></div>
<div><span><br>
</span></div>
<div><span>I do not want to delay this letter but if we do not
provide clarity then the confusion continues to reign. </span></div>
<div><span><br>
</span></div>
<div><span>I appreciate the language referring to the board I
think you captured the right tone. </span></div>
<div><span><br>
</span></div>
<div><span>Susan</span></div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Nov 2, 2017 at 3:47 PM,
Drazek, Keith via council <span dir="ltr"><<a
href="mailto:council@gnso.icann.org" target="_blank"
moz-do-not-send="true">council@gnso.icann.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote">
<div lang="EN-US">
<div class="m_5484730301850554755WordSection1">
<p class="MsoNormal">Thanks Heather. I think this
looks good. I assume you meant to type “reached the
point of *<b>no</b>* further modifications?”</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">If this is the final text, I
support it.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">If any further edits are made,
I’d suggest changing the work “tasked” in the first
paragraph to “request” so it doesn’t sound like the
Board is telling the SO/ACs what to do. They really
don’t have that power IMO. Here’s that suggested
text:</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">The Chairs of ICANN’s Supporting
Organizations (SOs) and Advisory Committees (ACs)
acknowledge the 28 October 2017 announcement from
the Board of Directors, pausing the work of the
Security, Stability and Resiliency Review Team
(SSR2-RT), and the Board's <span> request</span> in
sessions this week that the SOs and ACs address
concerns raised by the Board, Organizational
Effectiveness Committee (OEC), and the Security and
Stability Advisory Committee (SSAC).<br>
<br>
</p>
<p class="MsoNormal">Thanks to you and James for all
your work on this important communication.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Keith</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><a
name="m_5484730301850554755__MailEndCompose"
moz-do-not-send="true"> </a></p>
<span></span>
<p class="MsoNormal"><b>From:</b> <a
href="mailto:council-bounces@gnso.icann.org"
target="_blank" moz-do-not-send="true">council-bounces@gnso.icann.org</a>
[mailto:<a
href="mailto:council-bounces@gnso.icann.org"
target="_blank" moz-do-not-send="true">council-bounces@gnso.<wbr>icann.org</a>]
<b>On Behalf Of </b>Heather Forrest<br>
<b>Sent:</b> Thursday, November 02, 2017 3:37 PM<br>
<b>To:</b> GNSO Council List <<a
href="mailto:council@gnso.icann.org"
target="_blank" moz-do-not-send="true">council@gnso.icann.org</a>><br>
<b>Subject:</b> [EXTERNAL] [council] Fwd:
[soac-chairs] Draft Statement SSR2</p>
<div>
<div class="h5">
<p class="MsoNormal"> </p>
<div>
<div>
<div>
<div>
<div>
<blockquote>
<p class="MsoNormal">Dear GNSO Council
colleagues,</p>
</blockquote>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Following the
Board's meeting with SSR2 and then
meeting with SO/AC leaders this
afternoon, we have reached the point
of further modifications to the
SO/AC communication below.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">As James noted in
our Wrap-Up meeting today, this is
very much a negotiated effort, and
drafting by committee has had all
the usual challenges. We have added
the note of thanks and tried to
strengthen the forward-looking
concerns. The draft below has our,
Brad Verd and Kristina Sataki's
inputs. It is now making the
rounds. It is a product of drafting
by committee, so it still needs a
look with fresh eyes for typos etc.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">My view is let's
try not to re-open negotiation
unless it's absolutely imperative.
I'm inclined to suggest that any
lingering GNSO-specific concerns
that we want to hammer home can go
into a GNSO-specific response. Any
objections?</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Best wishes,</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Heather</p>
</div>
<blockquote>
<p class="MsoNormal"><br>
STATEMENT FROM SO/AC CHAIRS ON THE
SUSPENSION OF THE SECURITY AND
STABILITY REVIEW<br>
<br>
The Chairs of ICANN’s Supporting
Organizations (SOs) and Advisory
Committees (ACs) acknowledge the 28
October 2017 announcement from the
Board of Directors, pausing the work
of the Security, Stability and
Resiliency Review Team (SSR2-RT),
and the Board's having tasked the
SOs and ACs in sessions this week
with addressing concerns raised by
the Board, Organizational
Effectiveness Committee (OEC), and
the Security and Stability Advisory
Committee (SSAC).<br>
<br>
Collectively, we accept
responsibility for getting SSR2-RT
restarted <b>by the community </b>as
expeditiously as possible. During
various sessions throughout ICANN60,
our groups have met with the Board
and/or members of SSR2-RT to hear
their concerns. We intend to
continue to consult with our
respective communities, and each
other, to assess and address issues
relating to the scope, composition
and participation, resource
utilization, and overall work plan
of the Review.<br>
<br>
Additionally, the Board’s unilateral
decision to suspend the work of a
key accountability mechanism has
raised questions that go to the
independence of SSR2-RT, and
specific reviews going forward. As a
follow-on effort, we intend to
examine the selection and scoping
process for review teams, and
develop a clear and predictable
process for raising and addressing
concerns about review teams. We also
intend to carefully consider the
Board's action, with a view to
preventing similar instances in the
future. We look forward to working
collaboratively with the Board,
SSR2-RT and the broader community on
this task.</p>
</blockquote>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Finally, we wish
to acknowledge the efforts of our
colleagues on the SSR2-RT to date,
and thank them for their continued
commitment towards security,
stability and resiliency. </p>
</div>
<div>
<div>
<blockquote>
<p class="MsoNormal"> </p>
</blockquote>
<blockquote>
<p class="MsoNormal"><br>
[Signatures] Alan (ALAC), Patrik
(SSAC), Katrina (ccNSO), Thomas
(GAC outgoing), Manal (GAC
incoming), James (GNSO
outgoing), Heather (GNSO
incoming), Tripti Sinha(RSSAC
Co-Chair and Brad Verd (RSSAC
Co-Chair), (Etc.)<br>
<br>
Cheers,<br>
Brad</p>
<div>
<div>
<p class="MsoNormal"><br>
<br>
On 11/2/17, 1:30 AM, "<a
href="mailto:soac-chairs-bounces@icann.org"
target="_blank"
moz-do-not-send="true">soac-chairs-bounces@icann.org</a>
on behalf of Verd, Brad via
soac-chairs" <<a
href="mailto:soac-chairs-bounces@icann.org"
target="_blank"
moz-do-not-send="true">soac-chairs-bounces@icann.org</a>
on behalf of <a
href="mailto:soac-chairs@icann.org"
target="_blank"
moz-do-not-send="true">soac-chairs@icann.org</a>>
wrote:<br>
<br>
I don't’ know if anyone
has the pen on the document,
and in order to have the
statement reviewed and
agreed in time for the
public forum I would need to
see the current version of
the statement. I assume the
changes which I have seen on
this thread are accounted
for and we have ensured
there are no further
suggestions. In light of
the time schedule one
possible way forward is that
we could create a google doc
and work to consensus in
that manner.<br>
<br>
Cheers,<br>
Brad<br>
<br>
On 11/2/17, 1:03 AM, "<a
href="mailto:soac-chairs-bounces@icann.org" target="_blank"
moz-do-not-send="true">soac-chairs-bounces@icann.org</a>
on behalf of Katrina Sataki"
<<a
href="mailto:soac-chairs-bounces@icann.org"
target="_blank"
moz-do-not-send="true">soac-chairs-bounces@icann.org</a>
on behalf of <a
href="mailto:katrina@nic.lv"
target="_blank"
moz-do-not-send="true">katrina@nic.lv</a>>
wrote:<br>
<br>
<br>
I think there’s a
common understanding that we
as chairs cannot decide
(anything) without
consulting our communities
first. However, I think that
we do not need to consult
our communities if that’s ok
for us “to consult with our
respective communities” (<br>
<br>
I am in favour of
issuing this statement
today. After our meeting
with the Board perhaps?<br>
<br>
Thanks!<br>
<br>
]{atrina<br>
<br>
<br>
<br>
On 02/11/2017,
06:53, "Patrik Fältström"
<<a
href="mailto:soac-chairs-bounces@icann.org"
target="_blank"
moz-do-not-send="true">soac-chairs-bounces@icann.org</a>
on behalf of <a
href="mailto:paf@frobbit.se"
target="_blank"
moz-do-not-send="true">paf@frobbit.se</a>>
wrote:<br>
<br>
All,<br>
<br>
Today we have
the public forum
15:45-18:30.<br>
<br>
Do we think we
can send a note today, and
if so before the public
forum? I do understand that
even if you as individuals
think the text "is ok", you
must pass the text via your
respective communities and
because of that sending the
note "now" is not possible
for any definition of "now"
:-)<br>
<br>
So no stress. I
just want to be aware of
your respective timelines,
so that I know this (if
possible) before my meeting
with ICANN Board 1030-1130
today and specifically the
public forum at which I
might as SSAC Chair have to
go to the microphone.<br>
<br>
FWIW, I am ok
with the text.<br>
<br>
Patrik<br>
<br>
On 2 Nov 2017,
at 7:14, Verd, Brad via
soac-chairs wrote:<br>
<br>
> Is there a
“clean” version with updates
that can be shared so we
have time to cogitate on it?<br>
><br>
> Cheers,<br>
> Brad<br>
><br>
><br>
> From: <<a
href="mailto:soac-chairs-bounces@icann.org" target="_blank"
moz-do-not-send="true">soac-chairs-bounces@icann.org</a><wbr>>
on behalf of Tripti Sinha
<<a
href="mailto:tsinha@umd.edu"
target="_blank"
moz-do-not-send="true">tsinha@umd.edu</a>><br>
> Date:
Wednesday, November 1, 2017
at 10:05 AM<br>
> To: Heather
Forrest <<a
href="mailto:haforrestesq@gmail.com"
target="_blank"
moz-do-not-send="true">haforrestesq@gmail.com</a>>,
Katrina Sataki <<a
href="mailto:katrina@nic.lv"
target="_blank"
moz-do-not-send="true">katrina@nic.lv</a>><br>
> Cc: SO-AC
Chairs List <<a
href="mailto:soac-chairs@icann.org"
target="_blank"
moz-do-not-send="true">soac-chairs@icann.org</a>><br>
> Subject:
[EXTERNAL] Re: [soac-chairs]
Draft Statement SSR2<br>
><br>
> Katrina -
interesting perspective. The
reason why I was suggesting
those words is for exactly
that reason - that accepting
responsibility means the
board is giving us the
responsibility. I believe
those words should go into
the bylaws should they be
adjusted. Tasking, in my
opinion, is a less
authoritative word and
simply assigns a task with a
defined goal. Responsibility
is greater. Not that I
disagree that that may
happen but it needs to be in
the bylaws.<br>
><br>
> Anyway,
just my opinion.<br>
><br>
> Tripti<br>
><br>
><br>
> On Wed, Nov
1, 2017 at 4:07 PM Katrina
Sataki <<a
href="mailto:katrina@nic.lv"
target="_blank"
moz-do-not-send="true">katrina@nic.lv</a><mailto:<a
href="mailto:katrina@nic.lv" target="_blank" moz-do-not-send="true">katrina<wbr>@nic.lv</a>>>
wrote:<br>
> Dear All,<br>
><br>
> I am not
sure about “consider
ourselves tasked” as this
might (again) raise
questions on the Board’s
authority. Maybe “recognise
our responsibility as stated
in the Bylaws” or something
if “accept responsibility”
does not work here?<br>
> Agree with
other proposed edits.<br>
><br>
> ]{atrina<br>
><br>
><br>
> From: <<a
href="mailto:soac-chairs-bounces@icann.org" target="_blank"
moz-do-not-send="true">soac-chairs-bounces@icann.org</a><wbr><mailto:<a
href="mailto:soac-chairs-bounces@icann.org" target="_blank"
moz-do-not-send="true">soac-chairs-bounces@<wbr>icann.org</a>>>
on behalf of Tripti Sinha
<<a
href="mailto:tsinha@umd.edu"
target="_blank"
moz-do-not-send="true">tsinha@umd.edu</a><mailto:<a
href="mailto:tsinha@umd.edu" target="_blank" moz-do-not-send="true">tsinha@<wbr>umd.edu</a>>><br>
> Date:
Wednesday, 1 November 2017
at 13:43<br>
> To: Heather
Forrest <<a
href="mailto:haforrestesq@gmail.com"
target="_blank"
moz-do-not-send="true">haforrestesq@gmail.com</a><<wbr>mailto:<a
href="mailto:haforrestesq@gmail.com" target="_blank"
moz-do-not-send="true">haforrestesq@gmail.com</a>><wbr>><br>
> Cc: SO-AC
Chairs List <<a
href="mailto:soac-chairs@icann.org"
target="_blank"
moz-do-not-send="true">soac-chairs@icann.org</a><mailto:<a
href="mailto:soac-chairs@icann.org" target="_blank"
moz-do-not-send="true"><wbr>soac-chairs@icann.org</a>>><br>
> Subject:
Re: [soac-chairs] Draft
Statement SSR2<br>
><br>
> All,<br>
><br>
> I am adding
a recommended edit included
below. Thanks.<br>
><br>
> - Tripti<br>
><br>
><br>
> On Wed, Nov
1, 2017 at 2:23 AM, Heather
Forrest <<a
href="mailto:haforrestesq@gmail.com"
target="_blank"
moz-do-not-send="true">haforrestesq@gmail.com</a><<wbr>mailto:<a
href="mailto:haforrestesq@gmail.com" target="_blank"
moz-do-not-send="true">haforrestesq@gmail.com</a>><wbr>>
wrote:<br>
> Thanks
Patrick, James. Pleased to
join you all (albeit a few
hours prematurely) on this
list.<br>
><br>
> I have
suggested 2 edits in-line
below for the group's
consideration. Nb in
addition I have added a
hyphen in 'follow-on'.<br>
><br>
> Best
wishes,<br>
><br>
> Heather<br>
><br>
><br>
><br>
> On Wed, Nov
1, 2017 at 4:50 PM, Patrik
Fältström <<a
href="mailto:paf@frobbit.se"
target="_blank"
moz-do-not-send="true">paf@frobbit.se</a><mailto:<a
href="mailto:paf@frobbit.se" target="_blank" moz-do-not-send="true">paf@<wbr>frobbit.se</a>>>
wrote:<br>
> Good!<br>
><br>
> We should
remember to add people to
this list when we rotate
them in. They then remove us
when they feel to :-)<br>
><br>
> Welcome
Heather!<br>
><br>
> Patrik<br>
><br>
> On 1 Nov
2017, at 9:35, James M.
Bladel wrote:<br>
><br>
>> And,
for the avoidance of doubt,
I’ve asked Staff to add
Heather to this list, so I
can stop forgetting to
manually cc: her. She will
instruct Staff when I need
to be dropped. :)<br>
>><br>
>> Thanks
-<br>
>><br>
>> J.<br>
>>
--------------<br>
>> James
Bladel<br>
>> GoDaddy<br>
>><br>
>> On Nov
1, 2017, 09:31 +0400, James
M. Bladel <<a
href="mailto:jbladel@godaddy.com"
target="_blank"
moz-do-not-send="true">jbladel@godaddy.com</a><mailto:<a
href="mailto:jbladel@godaddy.com" target="_blank" moz-do-not-send="true">jb<wbr>ladel@godaddy.com</a>>>,
wrote:<br>
>> As
discussed (below). let’s
make this better.<br>
>><br>
>>
STATEMENT FROM SO/AC CHAIRS
ON THE SUSPENSION OF THE
SECURITY AND STABILITY
REVIEW<br>
>><br>
>> The
Chairs of ICANN’s Supporting
Organizations (SOs) and
Advisory Committees (ACs)
acknowledge the 27 October
2017 announcement from the
Board of Directors, pausing
the work of the Security,
Stability and Resiliency
Review Team (SSR2-RT), and
tasking the SOs and ACs to
address concerns raised by
the Board, Organizational
Effectiveness Committee
(OEC), the Security and
Stability Advisory Committee
(SSAC), and others [HF: I
propose deleting 'and
others', and suggest we
stick to the documented
statements of concern rather
than give credence to the
Board's having acted based
on casually made
statements].<br>
>><br>
>>
Collectively, we accept
responsibility [Tripti: I
recommend replacing "accept
responsibility" with
"consider ourselves tasked"]
for getting SSR2-RT back on
track and [HF: is it
helpful/necessary to include
the phrase 'back on track
and'? Can we not just at
this point look to
'restarted as expeditiously
as possible'?] restarted as
expeditiously as possible.
During various sessions
throughout ICANN60, our
groups have met with the
board and/or members of
SSR2-RT to hear their
concerns. We intend to
consult with our respective
communities, and each other,
to address these issues
relating to the scope,
composition and
participation, resource
utilization, and overall
work plan of the Review.<br>
>><br>
>>
Additionally, this incident
has raised questions that
affect the independence of
SSR2-RT, and specific
reviews going forward. As a
follow-on effort, we intend
to examine the selection
& scoping process for
review teams, and develop a
clear and predictable
process for raising and
addressing concerns for
active review teams already
underway. We look forward to
working collaboratively with
the Board, SSR2 and the
broader community on this
task.<br>
>><br>
>>
[Signatures]<br>
>> Alan,
Patrik, Katrina, Thomas (GAC
outgoing), Manal (GAC
incoming), James (GNSO
outgoing), Heather (GNSO
incoming), Tripti, Brad,
(Etc.)<br>
>><br>
>> Thanks
-<br>
>><br>
>> J.<br>
>>
--------------<br>
>> James
Bladel<br>
>> GoDaddy<br>
>><br>
>>
______________________________<wbr>_________________<br>
>>
soac-chairs mailing list<br>
>> <a
href="mailto:soac-chairs@icann.org"
target="_blank"
moz-do-not-send="true">soac-chairs@icann.org</a><mailto:<a
href="mailto:soac-chairs@icann.org" target="_blank"
moz-do-not-send="true">s<wbr>oac-chairs@icann.org</a>><br>
>> <a
href="https://mm.icann.org/mailman/listinfo/soac-chairs"
target="_blank"
moz-do-not-send="true">
https://mm.icann.org/mailman/<wbr>listinfo/soac-chairs</a><br>
><br>
><br>
>
______________________________<wbr>_________________<br>
> soac-chairs
mailing list<br>
> <a
href="mailto:soac-chairs@icann.org"
target="_blank"
moz-do-not-send="true">soac-chairs@icann.org</a><mailto:<a
href="mailto:soac-chairs@icann.org" target="_blank"
moz-do-not-send="true">s<wbr>oac-chairs@icann.org</a>><br>
> <a
href="https://mm.icann.org/mailman/listinfo/soac-chairs"
target="_blank"
moz-do-not-send="true">
https://mm.icann.org/mailman/<wbr>listinfo/soac-chairs</a><br>
><br>
>
______________________________<wbr>_________________
soac-chairs mailing list <a
href="mailto:soac-chairs@icann.org" target="_blank"
moz-do-not-send="true">soac-chairs@icann.org</a><mailto:<a
href="mailto:soac-chairs@icann.org" target="_blank"
moz-do-not-send="true">s<wbr>oac-chairs@icann.org</a>>
<a
href="https://mm.icann.org/mailman/listinfo/soac-chairs"
target="_blank"
moz-do-not-send="true">https://mm.icann.org/mailman/<wbr>listinfo/soac-chairs</a><br>
><br>
>
______________________________<wbr>_________________<br>
> soac-chairs
mailing list<br>
> <a
href="mailto:soac-chairs@icann.org"
target="_blank"
moz-do-not-send="true">soac-chairs@icann.org</a><br>
> <a
href="https://mm.icann.org/mailman/listinfo/soac-chairs"
target="_blank"
moz-do-not-send="true">
https://mm.icann.org/mailman/<wbr>listinfo/soac-chairs</a><br>
______________________________<wbr>_________________<br>
soac-chairs
mailing list<br>
<a
href="mailto:soac-chairs@icann.org"
target="_blank"
moz-do-not-send="true">soac-chairs@icann.org</a><br>
<a
href="https://mm.icann.org/mailman/listinfo/soac-chairs"
target="_blank"
moz-do-not-send="true">
https://mm.icann.org/mailman/<wbr>listinfo/soac-chairs</a><br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
soac-chairs mailing
list<br>
<a
href="mailto:soac-chairs@icann.org"
target="_blank"
moz-do-not-send="true">soac-chairs@icann.org</a><br>
<a
href="https://mm.icann.org/mailman/listinfo/soac-chairs"
target="_blank"
moz-do-not-send="true">
https://mm.icann.org/mailman/<wbr>listinfo/soac-chairs</a><br>
<br>
<br>
______________________________<wbr>_________________<br>
soac-chairs mailing list<br>
<a
href="mailto:soac-chairs@icann.org"
target="_blank"
moz-do-not-send="true">soac-chairs@icann.org</a><br>
<a
href="https://mm.icann.org/mailman/listinfo/soac-chairs"
target="_blank"
moz-do-not-send="true">https://mm.icann.org/mailman/<wbr>listinfo/soac-chairs</a><br>
<br>
</p>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
council mailing list<br>
<a href="mailto:council@gnso.icann.org"
moz-do-not-send="true">council@gnso.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/council"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/<wbr>listinfo/council</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
council mailing list
<a class="moz-txt-link-abbreviated" href="mailto:council@gnso.icann.org" moz-do-not-send="true">council@gnso.icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/council" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/council</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
council mailing list
<a class="moz-txt-link-abbreviated" href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/council">https://mm.icann.org/mailman/listinfo/council</a>
</pre>
</blockquote>
<br>
</body>
</html>