<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><<<span
style="font-size:12.0pt;font-family:"Arial",sans-serif">Interesting
that the NCSG – which is a vociferous proponent of privacy – is
beating the drum for revealing representation. They can’t have
it both ways – protect identities when they want and don’t when
they find it convenient.>></span></p>
<p><span
style="font-size:12.0pt;font-family:"Arial",sans-serif">The
response here is that privacy and transparency are not adverse -
public interest and noncommercial groups regularly advocate for
appropriate privacy AND appropriate transparency. The same
people who are most ardent advocates for privacy are also the
leaders of Freedom of Information legislation and initiatives
around the world. <br>
</span></p>
<p><span
style="font-size:12.0pt;font-family:"Arial",sans-serif">We
need to know how our policymaking groups work; we need clear and
open policy making processes, we need to know who is at the
table influencing policy decisions.</span></p>
<p><span
style="font-size:12.0pt;font-family:"Arial",sans-serif">In
US regulatory agencies, if you meet privately with a policy
maker about an open policy proceeding, you must file an Ex Parte
letter making clear who you represent and what you discussed
with the policy-maker/decision-maker. If you participate in the
process with testimony, white papers, and especially comments,
of course you must say on whose behalf you are filing.</span></p>
<p><span
style="font-size:12.0pt;font-family:"Arial",sans-serif">No,
privacy and transparency part of the very same process - they
work together to make sure that large corporations cannot
control the world. <br>
</span></p>
<p><i><b><span
style="font-size:12.0pt;font-family:"Arial",sans-serif">If
someone wants to draft short comments for us - I'll edit.
Unbelievably busy next week... <br>
</span></b></i></p>
<p><span
style="font-size:12.0pt;font-family:"Arial",sans-serif"><i><b>B</b></i>est,
Kathy<br>
</span></p>
<div class="moz-cite-prefix">On 3/30/2023 10:45 PM, 陳曼茹 Manju Chen
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAMeQZi01VVZfC_DRBMvjH7V6Y6LcUOAtKcEys0qhUVfbSXA=DA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_default"
style="font-family:arial,sans-serif;font-size:small">Hi all,</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">We've
discussed extensively the topic of SOI in Cancun. </div>
<div class="gmail_default"
style="font-family:arial,sans-serif;font-size:small">Please
find below the request from staff for each SG to submit their
statements on this topic by <b
style="font-family:Arial,Helvetica,sans-serif"><u>Friday 7
April .</u></b></div>
<div class="gmail_default"
style="font-family:arial,sans-serif;font-size:small">You can
also find BC's statement below. NCSG could consider whether to
respond since they made an effort mentioning us in their
statement.</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">As I
mentioned before, I'm NOT the NCSG representative but the
Council liaison to the task force. I'd urge our representative
on the task force to draft a statement and circulate it on the
list before submitting it to the task force. I recommend using
the statement NCSG has presented during the Council Town Hall
session in Cancun.</div>
<div class="gmail_default"
style="font-family:arial,sans-serif;font-size:small"><br>
</div>
<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>
<br>
</div>
<br>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">---------- Forwarded message
---------<br>
From: <strong class="gmail_sendername" dir="auto">Marika
Konings</strong> <span dir="auto"><<a
href="mailto:marika.konings@icann.org"
moz-do-not-send="true" class="moz-txt-link-freetext">marika.konings@icann.org</a>></span><br>
Date: Fri, Mar 24, 2023 at 10:27 PM<br>
Subject: Re: [GNSO-SOI-TF] Action Items & Notes: SOI TF
Meeting 01 March 2023 at 14:00 UTC<br>
To: Imran Hossen <<a href="mailto:imran@eysoftbd.com"
moz-do-not-send="true" class="moz-txt-link-freetext">imran@eysoftbd.com</a>>,
Julie Hedlund <<a href="mailto:julie.hedlund@icann.org"
moz-do-not-send="true" class="moz-txt-link-freetext">julie.hedlund@icann.org</a>>,
<a href="mailto:gnso-soi-tf@icann.org"
moz-do-not-send="true" class="moz-txt-link-freetext">gnso-soi-tf@icann.org</a>
<<a href="mailto:gnso-soi-tf@icann.org"
moz-do-not-send="true" class="moz-txt-link-freetext">gnso-soi-tf@icann.org</a>><br>
</div>
<br>
<br>
<div class="msg-9060376619896427723">
<div link="blue" vlink="purple" style="word-wrap:break-word"
lang="en-BE">
<div class="m_-9060376619896427723WordSection1">
<p class="MsoNormal"><span lang="EN-US">Thanks, Imran.
Can you confirm that this is the statement that the
BC would like to include in the report on this
topic?
</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">All, we have a
call scheduled for next week, but we are going to
give everyone a bit more time to consult and prepare
statements on the exemption language for inclusion
in the report. In the meantime, we will also consult
with Manju as the CCOICI liaison to this effort to
see if there are further efforts we can undertake to
bring the group closer together on this issue, or
whether it is time to escalate it to the CCOICI for
resolution. Of course, if there are any new
proposals or changes in views on this topic, feel
free to share these with the list.
</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">The meeting will
be moved to Wednesday 12 April so please submit your
group’s statements
<b><u>by Friday 7 April at the latest</u></b>. </span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">Best regards,</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">Julie &
Marika</span></p>
<p class="MsoNormal"><span> </span></p>
<div
style="border-right:none;border-bottom:none;border-left:none;border-top:1pt
solid rgb(181,196,223);padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span
style="font-size:12pt;color:black">From: </span></b><span
style="font-size:12pt;color:black">GNSO-SOI-TF
<<a href="mailto:gnso-soi-tf-bounces@icann.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">gnso-soi-tf-bounces@icann.org</a>>
on behalf of Imran Hossen <<a
href="mailto:imran@eysoftbd.com" target="_blank"
moz-do-not-send="true"
class="moz-txt-link-freetext">imran@eysoftbd.com</a>><br>
<b>Date: </b>Thursday, 23 March 2023 at 14:29<br>
<b>To: </b>Julie Hedlund <<a
href="mailto:julie.hedlund@icann.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">julie.hedlund@icann.org</a>>,
"<a href="mailto:gnso-soi-tf@icann.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">gnso-soi-tf@icann.org</a>"
<<a href="mailto:gnso-soi-tf@icann.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">gnso-soi-tf@icann.org</a>><br>
<b>Subject: </b>Re: [GNSO-SOI-TF] Action Items
& Notes: SOI TF Meeting 01 March 2023 at 14:00
UTC</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial",sans-serif">Hi,</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:8.0pt"><span
style="font-size:12.0pt;font-family:"Arial",sans-serif">In
terms of my representation of the BC’s position,
I consulted with the BC Chair and I believe
we’re in agreement that the BC is strongly
opposed to this proposal. Reasoning:</span></p>
<p class="MsoNormal" style="margin-bottom:8.0pt"><span
style="font-size:12.0pt;font-family:"Arial",sans-serif"> </span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormal" style="margin-bottom:8.0pt"><span
style="font-size:12.0pt;font-family:"Arial",sans-serif">Contracted
parties and their allies are positioning this
as a transparency issue. That calls for some
skepticism.</span></li>
<li class="MsoNormal" style="margin-bottom:8.0pt"><span
style="font-size:12.0pt;font-family:"Arial",sans-serif">The BC
is not in favor of eliminating a swath of
ICANN participants simply because they are
ethically bound to not disclose their client
relationships. There are myriad reasons – not
the least of which would be the fact that
disclosure of those being represented could
invite even more gaming into the ICANN
system. For example, an attorney representing
a new gTLD applicant could be compelled to
disclose his/her relationship with that
applicant, inviting a competing application.
That’s just one example.</span></li>
<li class="MsoNormal" style="margin-bottom:8.0pt"><span
style="font-size:12.0pt;font-family:"Arial",sans-serif">Proponents
of the rule change have suggested as a
compromise that, should a participant be in
this position, he/she could just disclose the
identity of the client relationship to ICANN
Org or the working group chair. That,
frankly, is preposterous – ICANN is a sieve of
information leakage in the first place, and –
further – such disclosure puts one or two
individuals into a decision-making position on
that person’s participation. ICANN is not in
the business of appointing people who can
arbitrate others’ participation.</span></li>
<li class="MsoNormal" style="margin-bottom:8.0pt"><span
style="font-size:12.0pt;font-family:"Arial",sans-serif">Interesting
that the NCSG – which is a vociferous
proponent of privacy – is beating the drum for
revealing representation. They can’t have it
both ways – protect identities when they want
and don’t when they find it convenient.</span></li>
</ul>
<p class="MsoNormal"
style="margin-bottom:8.0pt;line-height:106%"> </p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal">On Wed, Mar 1, 2023 at 8:47 PM
Julie Hedlund <<a
href="mailto:julie.hedlund@icann.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">julie.hedlund@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:0cm 0cm 0cm
6pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">Dear
All,</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">Please
see below the action items and brief notes
from today’s SOI Task Force meeting on
Wednesday, 01 March 2023 at 14:00 UTC.
These also are posted to the wiki at: <a
href="https://community.icann.org/x/yYXOCg" target="_blank"
moz-do-not-send="true"
class="moz-txt-link-freetext">https://community.icann.org/x/yYXOCg</a>.</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">Kind
regards,</span></p>
<p class="MsoNormal"><span lang="EN-US">Marika
and Julie</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><b><span lang="EN-US">GNSO
SOI TF Meeting on Wednesday 01 March at
14:00 UTC</span></b><span lang="EN-US"></span></p>
<p class="MsoNormal"><b><span lang="EN-US"> </span></b><span
lang="EN-US"></span></p>
<p class="MsoNormal"><b><span lang="EN-US">ACTION
ITEMS:
</span></b><span lang="EN-US"></span></p>
<ol type="1" start="1">
<li class="MsoNormal">
<b><span lang="EN-US">SOI TF members to
provide their position statements on
the exemption language by 24 March
that can be included in the report to
the CCOICI. Staff to specifically
request feedback from IPSPC and BC as
we have yet to hear from those groups.</span></b><span
lang="EN-US"></span></li>
<li class="MsoNormal">
<b><span lang="EN-US">GNSO Secretariat
staff to 1) circulate a Doodle poll to
schedule an informal meeting for
Wednesday or Thursday at ICANN76; 2)
schedule a SOI TF meeting for
Wednesday, 29 March at 1400 UTC.</span></b><span
lang="EN-US"></span></li>
<li class="MsoNormal">
<b><span lang="EN-US">SOI TF members to
suggest possible questions for ICANN
Legal.</span></b><span lang="EN-US"></span></li>
</ol>
<p class="MsoNormal"><b><span lang="EN-US"> </span></b><span
lang="EN-US"></span></p>
<p class="MsoNormal"><b><span lang="EN-US">Notes: </span></b><span
lang="EN-US"></span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">1.
Welcome</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">2.
Consider possible modification of
exemption language whereby represented
individual or entity information is shared
only with WG leadership if exemption is
invoked. See: <a
href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1aFuwubJUiIbXjui9mT6M9n1iSd-N_puL/edit__;!!PtGJab4!6DbG5NBCJY713AFh2289AXAqDrObS3KKfp1qtaYPoJRRvwFpeG9o-t4FgQK9SAnMgW9Fx2DTCZ1XBwFDZ4kheRqu3A$"
target="_blank" moz-do-not-send="true">
https://docs.google.com/document/d/1aFuwubJUiIbXjui9mT6M9n1iSd-N_puL/edit
[docs.google.com]</a>
</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">If no
support for 2:
</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">3.
Positions on exemption language (awaiting
input from ISPCP and BC)</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<ul type="disc">
<li class="MsoNormal">
<span lang="EN-US">RySG will have feedback
soon – it is an interesting compromise.
Also awaiting feedback from the
registrars.</span></li>
<li class="MsoNormal">
<span lang="EN-US">RrSG: A lot of
questions of where these recommendations
go from here. Still could be several
concerns.</span></li>
<li class="MsoNormal">
<span lang="EN-US">If this TF can’t come
to consensus on language, it will go
back to the CCOICI and then to the
Council. The Council would vote on
changes to the Operating Procedures as a
simply majority vote. Also is sent to
the Board.</span></li>
<li class="MsoNormal">
<span lang="EN-US">IPC: Appreciate the
attempt at a compromise, but if you
can’t disclose then you can’t disclose
to the leadership.
</span></li>
<li class="MsoNormal">
<span lang="EN-US">If additional time is
needed to consider, we should take it.
Can also discuss at the ICANN76 Council
meeting. It would be helpful for each
group to state their views for the
CCOICI to consider. Seems that this is
the only point of disagreement in the
revisions to the SOI.</span></li>
<li class="MsoNormal">
<span lang="EN-US">NCSG: Strong opposition
to the existing text.</span></li>
<li class="MsoNormal">
<span lang="EN-US">RySG: We will still
develop some examples to be posted with
the SOI.</span></li>
</ul>
<p class="MsoNormal"
style="margin-left:18.0pt">
<span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">4.
Possible SOI Pilot</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<ul type="disc">
<li class="MsoNormal">
<span lang="EN-US">Not clear that this
will be worth the effort and time if
groups won’t change their views.</span></li>
</ul>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">5.
Possible question to ICANN legal</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<ul type="disc">
<li class="MsoNormal">
<span lang="EN-US">Important to frame the
question and get agreement that this
would be helpful.</span></li>
</ul>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">6.
Confirm next steps</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<ul type="disc">
<li class="MsoNormal">
<span lang="EN-US">Helpful to get
statements of positions from TF member
groups to be included in the report to
the CCOICI to consider.</span></li>
<li class="MsoNormal">
<span lang="EN-US">Deadline by 24 March to
submit their statements on the exemption
language.</span></li>
<li class="MsoNormal">
<span lang="EN-US">Reconvene on 29 March
at 1400 UTC to review the final report.
</span></li>
<li class="MsoNormal">
<span lang="EN-US">No further public
comment period is planned unless the
CCOICI makes changes. Not sure what it
would achieve at this point as this
already an issue that was called out in
public comment.</span></li>
<li class="MsoNormal">
<span lang="EN-US">RrSG: Consider putting
this out for public comment again before
going to Council as people were not
paying attention.</span></li>
<li class="MsoNormal">
<span lang="EN-US">Staff: If we do a
focused public comment we need to agree
on specific question(s) that would yield
responses that could move this forward.
Also there is the opportunity to
socialize among your groups at ICANN76 –
could set up an informal SOI TF meeting
in a sign-up room if available (no
remote access). Is there interest in
this? Possibly but it would need to be
later in the week. Secretariat to do a
Doodle poll.</span></li>
</ul>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><b><span lang="EN-US">ACTION
ITEMS:
</span></b><span lang="EN-US"></span></p>
<ol type="1" start="1">
<li class="MsoNormal">
<b><span lang="EN-US">SOI TF members to
provide their position statements on
the exemption language by 24 March
that can be included in the report to
the CCOICI. Staff to specifically
request feedback from IPSPC and BC as
we have yet to hear from those groups.</span></b><span
lang="EN-US"></span></li>
<li class="MsoNormal">
<b><span lang="EN-US">GNSO Secretariat
staff to 1) circulate a Doodle poll to
schedule an informal meeting for
Wednesday or Thursday at ICANN76; 2)
schedule a SOI TF meeting for
Wednesday, 29 March at 1400 UTC.</span></b><span
lang="EN-US"></span></li>
<li class="MsoNormal">
<b><span lang="EN-US">SOI TF members to
suggest possible questions for ICANN
Legal.</span></b><span lang="EN-US"></span></li>
</ol>
<p class="MsoNormal"><b><span lang="EN-US"> </span></b><span
lang="EN-US"></span></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
GNSO-SOI-TF mailing list<br>
<a href="mailto:GNSO-SOI-TF@icann.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">GNSO-SOI-TF@icann.org</a><br>
<a
href="https://mm.icann.org/mailman/listinfo/gnso-soi-tf"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://mm.icann.org/mailman/listinfo/gnso-soi-tf</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" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a
href="https://www.icann.org/privacy/tos"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">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>
<p class="MsoNormal"><br clear="all">
<br>
-- </p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><b>Imran
Hossen</b></p>
</div>
<div>
<p class="MsoNormal">Managing
Director | CEO</p>
</div>
<div>
<p class="MsoNormal"><b>EyHost
Ltd. </b> | <b>EySoft
IT Solution</b></p>
</div>
<div>
<p class="MsoNormal"><b>Skype:</b>
imran891</p>
</div>
<div>
<p class="MsoNormal"><b>Phone: </b>+8801619474927</p>
</div>
<p class="MsoNormal"><a
href="https://urldefense.com/v3/__http:/www.eysoftbd.com__;!!PtGJab4!6DbG5NBCJY713AFh2289AXAqDrObS3KKfp1qtaYPoJRRvwFpeG9o-t4FgQK9SAnMgW9Fx2DTCZ1XBwFDZ4kNqGv0BQ$"
target="_blank"
moz-do-not-send="true">www.eysoftbd.com
[eysoftbd.com]</a> |
<a
href="https://urldefense.com/v3/__http:/www.eyhost.biz__;!!PtGJab4!6DbG5NBCJY713AFh2289AXAqDrObS3KKfp1qtaYPoJRRvwFpeG9o-t4FgQK9SAnMgW9Fx2DTCZ1XBwFDZ4kVR0ff5w$"
target="_blank"
moz-do-not-send="true">
www.eyhost.biz [eyhost.biz]</a></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
GNSO-SOI-TF mailing list<br>
<a href="mailto:GNSO-SOI-TF@icann.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">GNSO-SOI-TF@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-soi-tf"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://mm.icann.org/mailman/listinfo/gnso-soi-tf</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" moz-do-not-send="true"
class="moz-txt-link-freetext">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" moz-do-not-send="true"
class="moz-txt-link-freetext">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.</div>
<div class="msg-9060376619896427723"><br>
</div>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
NCSG-PC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NCSG-PC@lists.ncsg.is">NCSG-PC@lists.ncsg.is</a>
<a class="moz-txt-link-freetext" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a>
</pre>
</blockquote>
</body>
</html>