<div dir="auto">Hi Julf,<div dir="auto"><br></div><div dir="auto">First of all, my apologies for delayed responses. I am still on the road.</div><div dir="auto"><br></div><div dir="auto">Regarding David, he hasn't been responsive for a while now. I think we might need to at least look for a temporary replacement. <br><br><div data-smartmail="gmail_signature" dir="auto">Warmly, <br>Tomslin</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 6 Apr 2023, 16:49 Johan Helsingius, <<a href="mailto:julf@julf.com">julf@julf.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Tomslin,<br>
<br>
David never responded to my email (and the deadline is tomorrow). Maybe<br>
you should try to contact David and see if he is still able to continue<br>
as our representative?<br>
<br>
Julf<br>
<br>
<br>
-------- Forwarded Message --------<br>
Subject: Re: [NCSG-PC] Fwd: [GNSO-SOI-TF] Action Items & Notes: SOI TF <br>
Meeting 01 March 2023 at 14:00 UTC<br>
Date: Fri, 31 Mar 2023 18:16:19 +0200<br>
From: Johan Helsingius <julf@Julf.com><br>
To: David Cake <<a href="mailto:dave@davecake.net" target="_blank" rel="noreferrer">dave@davecake.net</a>><br>
CC: <a href="mailto:ncsg-pc@lists.ncsg.is" target="_blank" rel="noreferrer">ncsg-pc@lists.ncsg.is</a><br>
<br>
David,<br>
<br>
Will you be able to circulate a draft statement (that needs to also<br>
specifically address the comment from BC)?<br>
<br>
Julf<br>
<br>
On 31/03/2023 04:45, 陳曼茹 Manju Chen wrote:<br>
> Hi all,<br>
> <br>
> We've discussed extensively the topic of SOI in Cancun.<br>
> Please find below the request from staff for each SG to submit their <br>
> statements on this topic by *_Friday 7 April ._*<br>
> You can also find BC's statement below. NCSG could consider whether to <br>
> respond since they made an effort mentioning us in their statement.<br>
> <br>
> As I mentioned before, I'm NOT the NCSG representative but the Council <br>
> liaison to the task force. I'd urge our representative on the task force <br>
> to draft a statement and circulate it on the list before submitting it <br>
> to the task force. I recommend using the statement NCSG has presented <br>
> during the Council Town Hall session in Cancun.<br>
> <br>
> Best,<br>
> Manju<br>
> <br>
> <br>
> <br>
> ---------- Forwarded message ---------<br>
> From: *Marika Konings* <<a href="mailto:marika.konings@icann.org" target="_blank" rel="noreferrer">marika.konings@icann.org</a> <br>
> <mailto:<a href="mailto:marika.konings@icann.org" target="_blank" rel="noreferrer">marika.konings@icann.org</a>>><br>
> Date: Fri, Mar 24, 2023 at 10:27 PM<br>
> Subject: Re: [GNSO-SOI-TF] Action Items & Notes: SOI TF Meeting 01 March <br>
> 2023 at 14:00 UTC<br>
> To: Imran Hossen <<a href="mailto:imran@eysoftbd.com" target="_blank" rel="noreferrer">imran@eysoftbd.com</a> <mailto:<a href="mailto:imran@eysoftbd.com" target="_blank" rel="noreferrer">imran@eysoftbd.com</a>>>, Julie <br>
> Hedlund <<a href="mailto:julie.hedlund@icann.org" target="_blank" rel="noreferrer">julie.hedlund@icann.org</a> <mailto:<a href="mailto:julie.hedlund@icann.org" target="_blank" rel="noreferrer">julie.hedlund@icann.org</a>>>, <br>
> <a href="mailto:gnso-soi-tf@icann.org" target="_blank" rel="noreferrer">gnso-soi-tf@icann.org</a> <mailto:<a href="mailto:gnso-soi-tf@icann.org" target="_blank" rel="noreferrer">gnso-soi-tf@icann.org</a>> <br>
> <<a href="mailto:gnso-soi-tf@icann.org" target="_blank" rel="noreferrer">gnso-soi-tf@icann.org</a> <mailto:<a href="mailto:gnso-soi-tf@icann.org" target="_blank" rel="noreferrer">gnso-soi-tf@icann.org</a>>><br>
> <br>
> <br>
> Thanks, Imran. Can you confirm that this is the statement that the BC <br>
> would like to include in the report on this topic? ____<br>
> <br>
> __ __<br>
> <br>
> All, we have a call scheduled for next week, but we are going to give <br>
> everyone a bit more time to consult and prepare statements on the <br>
> exemption language for inclusion in the report. In the meantime, we will <br>
> also consult with Manju as the CCOICI liaison to this effort to see if <br>
> there are further efforts we can undertake to bring the group closer <br>
> together on this issue, or whether it is time to escalate it to the <br>
> CCOICI for resolution. Of course, if there are any new proposals or <br>
> changes in views on this topic, feel free to share these with the list. ____<br>
> <br>
> __ __<br>
> <br>
> The meeting will be moved to Wednesday 12 April so please submit your <br>
> group’s statements *_by Friday 7 April at the latest_*. ____<br>
> <br>
> __ __<br>
> <br>
> Best regards,____<br>
> <br>
> __ __<br>
> <br>
> Julie & Marika____<br>
> <br>
> __ __<br>
> <br>
> *From: *GNSO-SOI-TF <<a href="mailto:gnso-soi-tf-bounces@icann.org" target="_blank" rel="noreferrer">gnso-soi-tf-bounces@icann.org</a> <br>
> <mailto:<a href="mailto:gnso-soi-tf-bounces@icann.org" target="_blank" rel="noreferrer">gnso-soi-tf-bounces@icann.org</a>>> on behalf of Imran Hossen <br>
> <<a href="mailto:imran@eysoftbd.com" target="_blank" rel="noreferrer">imran@eysoftbd.com</a> <mailto:<a href="mailto:imran@eysoftbd.com" target="_blank" rel="noreferrer">imran@eysoftbd.com</a>>><br>
> *Date: *Thursday, 23 March 2023 at 14:29<br>
> *To: *Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" target="_blank" rel="noreferrer">julie.hedlund@icann.org</a> <br>
> <mailto:<a href="mailto:julie.hedlund@icann.org" target="_blank" rel="noreferrer">julie.hedlund@icann.org</a>>>, "<a href="mailto:gnso-soi-tf@icann.org" target="_blank" rel="noreferrer">gnso-soi-tf@icann.org</a> <br>
> <mailto:<a href="mailto:gnso-soi-tf@icann.org" target="_blank" rel="noreferrer">gnso-soi-tf@icann.org</a>>" <<a href="mailto:gnso-soi-tf@icann.org" target="_blank" rel="noreferrer">gnso-soi-tf@icann.org</a> <br>
> <mailto:<a href="mailto:gnso-soi-tf@icann.org" target="_blank" rel="noreferrer">gnso-soi-tf@icann.org</a>>><br>
> *Subject: *Re: [GNSO-SOI-TF] Action Items & Notes: SOI TF Meeting 01 <br>
> March 2023 at 14:00 UTC____<br>
> <br>
> __ __<br>
> <br>
> Hi,____<br>
> <br>
> In terms of my representation of the BC’s position, I consulted with the <br>
> BC Chair and I believe we’re in agreement that the BC is strongly <br>
> opposed to this proposal. Reasoning:____<br>
> <br>
> ____<br>
> <br>
> * Contracted parties and their allies are positioning this as a<br>
> transparency issue. That calls for some skepticism.____<br>
> * The BC is not in favor of eliminating a swath of ICANN participants<br>
> simply because they are ethically bound to not disclose their client<br>
> relationships. There are myriad reasons – not the least of which<br>
> would be the fact that disclosure of those being represented could<br>
> invite even more gaming into the ICANN system. For example, an<br>
> attorney representing a new gTLD applicant could be compelled to<br>
> disclose his/her relationship with that applicant, inviting a<br>
> competing application. That’s just one example.____<br>
> * Proponents of the rule change have suggested as a compromise that,<br>
> should a participant be in this position, he/she could just disclose<br>
> the identity of the client relationship to ICANN Org or the working<br>
> group chair. That, frankly, is preposterous – ICANN is a sieve of<br>
> information leakage in the first place, and – further – such<br>
> disclosure puts one or two individuals into a decision-making<br>
> position on that person’s participation. ICANN is not in the<br>
> business of appointing people who can arbitrate others’<br>
> participation.____<br>
> * Interesting that the NCSG – which is a vociferous proponent of<br>
> privacy – is beating the drum for revealing representation. They<br>
> can’t have it both ways – protect identities when they want and<br>
> don’t when they find it convenient.____<br>
> <br>
> ____<br>
> <br>
> __ __<br>
> <br>
> On Wed, Mar 1, 2023 at 8:47 PM Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" target="_blank" rel="noreferrer">julie.hedlund@icann.org</a> <br>
> <mailto:<a href="mailto:julie.hedlund@icann.org" target="_blank" rel="noreferrer">julie.hedlund@icann.org</a>>> wrote:____<br>
> <br>
> Dear All,____<br>
> <br>
> ____<br>
> <br>
> Please see below the action items and brief notes from today’s SOI<br>
> Task Force meeting on Wednesday, 01 March 2023 at 14:00 UTC. These<br>
> also are posted to the wiki at: <a href="https://community.icann.org/x/yYXOCg" rel="noreferrer noreferrer" target="_blank">https://community.icann.org/x/yYXOCg</a><br>
> <<a href="https://community.icann.org/x/yYXOCg" rel="noreferrer noreferrer" target="_blank">https://community.icann.org/x/yYXOCg</a>>.____<br>
> <br>
> ____<br>
> <br>
> Kind regards,____<br>
> <br>
> Marika and Julie____<br>
> <br>
> ____<br>
> <br>
> *GNSO SOI TF Meeting on Wednesday 01 March at 14:00 UTC*____<br>
> <br>
> **____<br>
> <br>
> *ACTION ITEMS: *____<br>
> <br>
> 1. *SOI TF members to provide their position statements on the<br>
> exemption language by 24 March that can be included in the<br>
> report to the CCOICI. Staff to specifically request feedback<br>
> from IPSPC and BC as we have yet to hear from those groups.*____<br>
> 2. *GNSO Secretariat staff to 1) circulate a Doodle poll to<br>
> schedule an informal meeting for Wednesday or Thursday at<br>
> ICANN76; 2) schedule a SOI TF meeting for Wednesday, 29 March at<br>
> 1400 UTC.*____<br>
> 3. *SOI TF members to suggest possible questions for ICANN Legal.*____<br>
> <br>
> **____<br>
> <br>
> *Notes: *____<br>
> <br>
> ____<br>
> <br>
> 1. Welcome____<br>
> <br>
> ____<br>
> <br>
> 2. Consider possible modification of exemption language whereby<br>
> represented individual or entity information is shared only with WG<br>
> leadership if exemption is invoked. See:<br>
> <a href="https://docs.google.com/document/d/1aFuwubJUiIbXjui9mT6M9n1iSd-N_puL/edit" rel="noreferrer noreferrer" target="_blank">https://docs.google.com/document/d/1aFuwubJUiIbXjui9mT6M9n1iSd-N_puL/edit</a> [<a href="http://docs.google.com" rel="noreferrer noreferrer" target="_blank">docs.google.com</a>] <<a href="https://urldefense.com/v3/__https:/docs.google.com/document/d/1aFuwubJUiIbXjui9mT6M9n1iSd-N_puL/edit__;!!PtGJab4!6DbG5NBCJY713AFh2289AXAqDrObS3KKfp1qtaYPoJRRvwFpeG9o-t4FgQK9SAnMgW9Fx2DTCZ1XBwFDZ4kheRqu3A$" rel="noreferrer noreferrer" target="_blank">https://urldefense.com/v3/__https:/docs.google.com/document/d/1aFuwubJUiIbXjui9mT6M9n1iSd-N_puL/edit__;!!PtGJab4!6DbG5NBCJY713AFh2289AXAqDrObS3KKfp1qtaYPoJRRvwFpeG9o-t4FgQK9SAnMgW9Fx2DTCZ1XBwFDZ4kheRqu3A$</a>> ____<br>
> <br>
> ____<br>
> <br>
> If no support for 2: ____<br>
> <br>
> ____<br>
> <br>
> 3. Positions on exemption language (awaiting input from ISPCP and<br>
> BC)____<br>
> <br>
> ____<br>
> <br>
> * RySG will have feedback soon – it is an interesting compromise.<br>
> Also awaiting feedback from the registrars.____<br>
> * RrSG: A lot of questions of where these recommendations go from<br>
> here. Still could be several concerns.____<br>
> * If this TF can’t come to consensus on language, it will go back<br>
> to the CCOICI and then to the Council. The Council would vote<br>
> on changes to the Operating Procedures as a simply majority<br>
> vote. Also is sent to the Board.____<br>
> * IPC: Appreciate the attempt at a compromise, but if you can’t<br>
> disclose then you can’t disclose to the leadership. ____<br>
> * If additional time is needed to consider, we should take it. <br>
> Can also discuss at the ICANN76 Council meeting. It would be<br>
> helpful for each group to state their views for the CCOICI to<br>
> consider. Seems that this is the only point of disagreement in<br>
> the revisions to the SOI.____<br>
> * NCSG: Strong opposition to the existing text.____<br>
> * RySG: We will still develop some examples to be posted with the<br>
> SOI.____<br>
> <br>
> ____<br>
> <br>
> 4. Possible SOI Pilot____<br>
> <br>
> ____<br>
> <br>
> * Not clear that this will be worth the effort and time if groups<br>
> won’t change their views.____<br>
> <br>
> ____<br>
> <br>
> 5. Possible question to ICANN legal____<br>
> <br>
> ____<br>
> <br>
> * Important to frame the question and get agreement that this<br>
> would be helpful.____<br>
> <br>
> ____<br>
> <br>
> 6. Confirm next steps____<br>
> <br>
> ____<br>
> <br>
> * Helpful to get statements of positions from TF member groups to<br>
> be included in the report to the CCOICI to consider.____<br>
> * Deadline by 24 March to submit their statements on the exemption<br>
> language.____<br>
> * Reconvene on 29 March at 1400 UTC to review the final report. ____<br>
> * No further public comment period is planned unless the CCOICI<br>
> makes changes. Not sure what it would achieve at this point as<br>
> this already an issue that was called out in public comment.____<br>
> * RrSG: Consider putting this out for public comment again before<br>
> going to Council as people were not paying attention.____<br>
> * Staff: If we do a focused public comment we need to agree on<br>
> specific question(s) that would yield responses that could move<br>
> this forward. Also there is the opportunity to socialize among<br>
> your groups at ICANN76 – could set up an informal SOI TF meeting<br>
> in a sign-up room if available (no remote access). Is there<br>
> interest in this? Possibly but it would need to be later in the<br>
> week. Secretariat to do a Doodle poll.____<br>
> <br>
> ____<br>
> <br>
> *ACTION ITEMS: *____<br>
> <br>
> 1. *SOI TF members to provide their position statements on the<br>
> exemption language by 24 March that can be included in the<br>
> report to the CCOICI. Staff to specifically request feedback<br>
> from IPSPC and BC as we have yet to hear from those groups.*____<br>
> 2. *GNSO Secretariat staff to 1) circulate a Doodle poll to<br>
> schedule an informal meeting for Wednesday or Thursday at<br>
> ICANN76; 2) schedule a SOI TF meeting for Wednesday, 29 March at<br>
> 1400 UTC.*____<br>
> 3. *SOI TF members to suggest possible questions for ICANN Legal.*____<br>
> <br>
> **____<br>
> <br>
> _______________________________________________<br>
> GNSO-SOI-TF mailing list<br>
> <a href="mailto:GNSO-SOI-TF@icann.org" target="_blank" rel="noreferrer">GNSO-SOI-TF@icann.org</a> <mailto:<a href="mailto:GNSO-SOI-TF@icann.org" target="_blank" rel="noreferrer">GNSO-SOI-TF@icann.org</a>><br>
> <a href="https://mm.icann.org/mailman/listinfo/gnso-soi-tf" rel="noreferrer noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-soi-tf</a><br>
> <<a href="https://mm.icann.org/mailman/listinfo/gnso-soi-tf" rel="noreferrer noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-soi-tf</a>><br>
> <br>
> _______________________________________________<br>
> By submitting your personal data, you consent to the processing of<br>
> your personal data for purposes of subscribing to this mailing list<br>
> accordance with the ICANN Privacy Policy<br>
> (<a href="https://www.icann.org/privacy/policy" rel="noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/policy</a><br>
> <<a href="https://www.icann.org/privacy/policy" rel="noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>>) and the website Terms of<br>
> Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/tos</a><br>
> <<a href="https://www.icann.org/privacy/tos" rel="noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>>). You can visit the Mailman link<br>
> above to change your membership status or configuration, including<br>
> unsubscribing, setting digest-style delivery or disabling delivery<br>
> altogether (e.g., for a vacation), and so on.____<br>
> <br>
> <br>
> <br>
> -- ____<br>
> <br>
> *Imran Hossen*____<br>
> <br>
> Managing Director | CEO____<br>
> <br>
> *EyHost Ltd. * | *EySoft IT Solution*____<br>
> <br>
> *Skype:* imran891____<br>
> <br>
> *Phone: *+8801619474927____<br>
> <br>
> <a href="http://www.eysoftbd.com" rel="noreferrer noreferrer" target="_blank">www.eysoftbd.com</a> [<a href="http://eysoftbd.com" rel="noreferrer noreferrer" target="_blank">eysoftbd.com</a>] <br>
> <<a href="https://urldefense.com/v3/__http:/www.eysoftbd.com__;!!PtGJab4!6DbG5NBCJY713AFh2289AXAqDrObS3KKfp1qtaYPoJRRvwFpeG9o-t4FgQK9SAnMgW9Fx2DTCZ1XBwFDZ4kNqGv0BQ$" rel="noreferrer noreferrer" target="_blank">https://urldefense.com/v3/__http:/www.eysoftbd.com__;!!PtGJab4!6DbG5NBCJY713AFh2289AXAqDrObS3KKfp1qtaYPoJRRvwFpeG9o-t4FgQK9SAnMgW9Fx2DTCZ1XBwFDZ4kNqGv0BQ$</a>> | <a href="http://www.eyhost.biz" rel="noreferrer noreferrer" target="_blank">www.eyhost.biz</a> [<a href="http://eyhost.biz" rel="noreferrer noreferrer" target="_blank">eyhost.biz</a>] <<a href="https://urldefense.com/v3/__http:/www.eyhost.biz__;!!PtGJab4!6DbG5NBCJY713AFh2289AXAqDrObS3KKfp1qtaYPoJRRvwFpeG9o-t4FgQK9SAnMgW9Fx2DTCZ1XBwFDZ4kVR0ff5w$" rel="noreferrer noreferrer" target="_blank">https://urldefense.com/v3/__http:/www.eyhost.biz__;!!PtGJab4!6DbG5NBCJY713AFh2289AXAqDrObS3KKfp1qtaYPoJRRvwFpeG9o-t4FgQK9SAnMgW9Fx2DTCZ1XBwFDZ4kVR0ff5w$</a>>____<br>
> <br>
> _______________________________________________<br>
> GNSO-SOI-TF mailing list<br>
> <a href="mailto:GNSO-SOI-TF@icann.org" target="_blank" rel="noreferrer">GNSO-SOI-TF@icann.org</a> <mailto:<a href="mailto:GNSO-SOI-TF@icann.org" target="_blank" rel="noreferrer">GNSO-SOI-TF@icann.org</a>><br>
> <a href="https://mm.icann.org/mailman/listinfo/gnso-soi-tf" rel="noreferrer noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-soi-tf</a> <br>
> <<a href="https://mm.icann.org/mailman/listinfo/gnso-soi-tf" rel="noreferrer noreferrer" target="_blank">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 <br>
> personal data for purposes of subscribing to this mailing list <br>
> accordance with the ICANN Privacy Policy <br>
> (<a href="https://www.icann.org/privacy/policy" rel="noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/policy</a> <br>
> <<a href="https://www.icann.org/privacy/policy" rel="noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>>) and the website Terms of Service <br>
> (<a href="https://www.icann.org/privacy/tos" rel="noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/tos</a> <<a href="https://www.icann.org/privacy/tos" rel="noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>>). <br>
> You can visit the Mailman link above to change your membership status or <br>
> configuration, including unsubscribing, setting digest-style delivery or <br>
> disabling delivery altogether (e.g., for a vacation), and so on.<br>
> <br>
> <br>
> _______________________________________________<br>
> NCSG-PC mailing list<br>
> <a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank" rel="noreferrer">NCSG-PC@lists.ncsg.is</a><br>
> <a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br>
</blockquote></div>