[NCSG-PC] Fwd: [GNSO-SOI-TF] Action Items & Notes: SOI TF Meeting 01 March 2023 at 14:00 UTC
Johan Helsingius
julf at Julf.com
Fri Mar 31 19:16:19 EEST 2023
David,
Will you be able to circulate a draft statement (that needs to also
specifically address the comment from BC)?
Julf
On 31/03/2023 04:45, 陳曼茹 Manju Chen wrote:
> Hi all,
>
> We've discussed extensively the topic of SOI in Cancun.
> Please find below the request from staff for each SG to submit their
> statements on this topic by *_Friday 7 April ._*
> You can also find BC's statement below. NCSG could consider whether to
> respond since they made an effort mentioning us in their statement.
>
> 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.
>
> Best,
> Manju
>
>
>
> ---------- Forwarded message ---------
> From: *Marika Konings* <marika.konings at icann.org
> <mailto:marika.konings at icann.org>>
> Date: Fri, Mar 24, 2023 at 10:27 PM
> Subject: Re: [GNSO-SOI-TF] Action Items & Notes: SOI TF Meeting 01 March
> 2023 at 14:00 UTC
> To: Imran Hossen <imran at eysoftbd.com <mailto:imran at eysoftbd.com>>, Julie
> Hedlund <julie.hedlund at icann.org <mailto:julie.hedlund at icann.org>>,
> gnso-soi-tf at icann.org <mailto:gnso-soi-tf at icann.org>
> <gnso-soi-tf at icann.org <mailto:gnso-soi-tf at icann.org>>
>
>
> Thanks, Imran. Can you confirm that this is the statement that the BC
> would like to include in the report on this topic? ____
>
> __ __
>
> 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. ____
>
> __ __
>
> The meeting will be moved to Wednesday 12 April so please submit your
> group’s statements *_by Friday 7 April at the latest_*. ____
>
> __ __
>
> Best regards,____
>
> __ __
>
> Julie & Marika____
>
> __ __
>
> *From: *GNSO-SOI-TF <gnso-soi-tf-bounces at icann.org
> <mailto:gnso-soi-tf-bounces at icann.org>> on behalf of Imran Hossen
> <imran at eysoftbd.com <mailto:imran at eysoftbd.com>>
> *Date: *Thursday, 23 March 2023 at 14:29
> *To: *Julie Hedlund <julie.hedlund at icann.org
> <mailto:julie.hedlund at icann.org>>, "gnso-soi-tf at icann.org
> <mailto:gnso-soi-tf at icann.org>" <gnso-soi-tf at icann.org
> <mailto:gnso-soi-tf at icann.org>>
> *Subject: *Re: [GNSO-SOI-TF] Action Items & Notes: SOI TF Meeting 01
> March 2023 at 14:00 UTC____
>
> __ __
>
> Hi,____
>
> 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:____
>
> ____
>
> * Contracted parties and their allies are positioning this as a
> transparency issue. That calls for some skepticism.____
> * 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.____
> * 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.____
> * 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.____
>
> ____
>
> __ __
>
> On Wed, Mar 1, 2023 at 8:47 PM Julie Hedlund <julie.hedlund at icann.org
> <mailto:julie.hedlund at icann.org>> wrote:____
>
> Dear All,____
>
> ____
>
> 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: https://community.icann.org/x/yYXOCg
> <https://community.icann.org/x/yYXOCg>.____
>
> ____
>
> Kind regards,____
>
> Marika and Julie____
>
> ____
>
> *GNSO SOI TF Meeting on Wednesday 01 March at 14:00 UTC*____
>
> **____
>
> *ACTION ITEMS: *____
>
> 1. *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.*____
> 2. *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.*____
> 3. *SOI TF members to suggest possible questions for ICANN Legal.*____
>
> **____
>
> *Notes: *____
>
> ____
>
> 1. Welcome____
>
> ____
>
> 2. Consider possible modification of exemption language whereby
> represented individual or entity information is shared only with WG
> leadership if exemption is invoked. See:
> https://docs.google.com/document/d/1aFuwubJUiIbXjui9mT6M9n1iSd-N_puL/edit [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/document/d/1aFuwubJUiIbXjui9mT6M9n1iSd-N_puL/edit__;!!PtGJab4!6DbG5NBCJY713AFh2289AXAqDrObS3KKfp1qtaYPoJRRvwFpeG9o-t4FgQK9SAnMgW9Fx2DTCZ1XBwFDZ4kheRqu3A$> ____
>
> ____
>
> If no support for 2: ____
>
> ____
>
> 3. Positions on exemption language (awaiting input from ISPCP and
> BC)____
>
> ____
>
> * RySG will have feedback soon – it is an interesting compromise.
> Also awaiting feedback from the registrars.____
> * RrSG: A lot of questions of where these recommendations go from
> here. Still could be several concerns.____
> * 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.____
> * IPC: Appreciate the attempt at a compromise, but if you can’t
> disclose then you can’t disclose to the leadership. ____
> * 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.____
> * NCSG: Strong opposition to the existing text.____
> * RySG: We will still develop some examples to be posted with the
> SOI.____
>
> ____
>
> 4. Possible SOI Pilot____
>
> ____
>
> * Not clear that this will be worth the effort and time if groups
> won’t change their views.____
>
> ____
>
> 5. Possible question to ICANN legal____
>
> ____
>
> * Important to frame the question and get agreement that this
> would be helpful.____
>
> ____
>
> 6. Confirm next steps____
>
> ____
>
> * Helpful to get statements of positions from TF member groups to
> be included in the report to the CCOICI to consider.____
> * Deadline by 24 March to submit their statements on the exemption
> language.____
> * Reconvene on 29 March at 1400 UTC to review the final report. ____
> * 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.____
> * RrSG: Consider putting this out for public comment again before
> going to Council as people were not paying attention.____
> * 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.____
>
> ____
>
> *ACTION ITEMS: *____
>
> 1. *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.*____
> 2. *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.*____
> 3. *SOI TF members to suggest possible questions for ICANN Legal.*____
>
> **____
>
> _______________________________________________
> GNSO-SOI-TF mailing list
> GNSO-SOI-TF at icann.org <mailto:GNSO-SOI-TF at icann.org>
> https://mm.icann.org/mailman/listinfo/gnso-soi-tf
> <https://mm.icann.org/mailman/listinfo/gnso-soi-tf>
>
> _______________________________________________
> 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
> (https://www.icann.org/privacy/policy
> <https://www.icann.org/privacy/policy>) and the website Terms of
> Service (https://www.icann.org/privacy/tos
> <https://www.icann.org/privacy/tos>). 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.____
>
>
>
> -- ____
>
> *Imran Hossen*____
>
> Managing Director | CEO____
>
> *EyHost Ltd. * | *EySoft IT Solution*____
>
> *Skype:* imran891____
>
> *Phone: *+8801619474927____
>
> www.eysoftbd.com [eysoftbd.com]
> <https://urldefense.com/v3/__http:/www.eysoftbd.com__;!!PtGJab4!6DbG5NBCJY713AFh2289AXAqDrObS3KKfp1qtaYPoJRRvwFpeG9o-t4FgQK9SAnMgW9Fx2DTCZ1XBwFDZ4kNqGv0BQ$> | www.eyhost.biz [eyhost.biz] <https://urldefense.com/v3/__http:/www.eyhost.biz__;!!PtGJab4!6DbG5NBCJY713AFh2289AXAqDrObS3KKfp1qtaYPoJRRvwFpeG9o-t4FgQK9SAnMgW9Fx2DTCZ1XBwFDZ4kVR0ff5w$>____
>
> _______________________________________________
> GNSO-SOI-TF mailing list
> GNSO-SOI-TF at icann.org <mailto:GNSO-SOI-TF at icann.org>
> https://mm.icann.org/mailman/listinfo/gnso-soi-tf
> <https://mm.icann.org/mailman/listinfo/gnso-soi-tf>
>
> _______________________________________________
> 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
> (https://www.icann.org/privacy/policy
> <https://www.icann.org/privacy/policy>) and the website Terms of Service
> (https://www.icann.org/privacy/tos <https://www.icann.org/privacy/tos>).
> 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.
>
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
More information about the NCSG-PC
mailing list