[council] GAC Communique

[Jeff Neuman]

Paul,

Before we farm out any of the relevant sections of the Communique to any other groups, lets decide amongst ourselves whether all of these items need to have a comment from the GNSO.

For example, I do not believe we should comment on the SOI stuff because that is still a work in progress within the applicable GNSO Committee.  I am also not sure there is anything in the DNS Abuse section that would require a response because it is merely just re-affirming what it said in the past – namely, that it considers accurate WHOIS information to be important and encourages the contracted parties to continue to take proactive measures…..

That said, we may want to comment on SubPro, the IRT on ePDP Phase 1, IGOs and Privacy/Proxy.

But I leave it up to you all.

Sincerely,

jeff



[cid:image002.png at 01D95BE0.1C75BBA0]
Jeffrey J. Neuman
Founder & CEO
JJN Solutions, LLC
p: +1.202.549.5079
E: jeff at jjnsolutions.com<mailto:jeff at jjnsolutions.com>
http://jjnsolutions.com


From: council <council-bounces at gnso.icann.org> On Behalf Of Paul McGrady via council
Sent: Monday, March 20, 2023 4:08 PM
To: Emily Barabas <emily.barabas at icann.org>; council at gnso.icann.org
Subject: Re: [council] GAC Communique

Thanks Emily.  Not to mess with what has always worked in the past, but we have several small teams set up for most of the items in the communique.  Would it make more sense to have those items referred to the respective Council small team (DNS Abuse, SubPro, REDDRESS system, etc.) for the relevant small team to draft a response?  We can then take the “homeless” items and assign them to the relevant Council liaison (for example, whomever is the liaison for the Task Force that has raised the issue of the SOI expansion) to take the first cut at those?  Could we just appoint someone then to gather those draft responses by date X rather than empaneling & doodling another small team?  Just a thought.

Best,
Paul



From: council <council-bounces at gnso.icann.org<mailto:council-bounces at gnso.icann.org>> On Behalf Of Emily Barabas via council
Sent: Monday, March 20, 2023 2:54 PM
To: council at gnso.icann.org<mailto:council at gnso.icann.org>
Subject: Re: [council] GAC Communique

Dear Councilors,

To support the small group’s work in reviewing the Communique, here is the standard Google Doc for responding to Advice items, with the ICANN76 Advice filled into the first two columns: https://docs.google.com/document/d/1829lKsBSn_O0ecSeI4FFLBhLymLAKIs9gx81P_6n3yw/edit?usp=sharing

The staff support team has also prepared a Google Doc to assist the small group in organizing its thoughts on Issues of Importance, to the extent that the small group would like to suggest responses on those items: https://docs.google.com/document/d/1ziBDcQ1eqjI_DXIORpnevzqXIaoVo_5LJ60sJvJE5xM/edit?usp=sharing. As noted in the template, the small group may suggest, and Council will determine the method of delivering each response item (for example via correspondence or dialogue) to the target audience (for example the GAC or Board).

Staff will follow up with the Councilors listed below with a doodle poll to set up a meeting. If there are other Councilors who would like to join the small group, please respond on list and we will make sure you get the doodle, as well.

Kind regards,
Emily


From: council <council-bounces at gnso.icann.org<mailto:council-bounces at gnso.icann.org>> on behalf of Jeff Neuman via council <council at gnso.icann.org<mailto:council at gnso.icann.org>>
Reply to: Jeff Neuman <jeff at jjnsolutions.com<mailto:jeff at jjnsolutions.com>>
Date: Monday, 20 March 2023 at 16:33
To: "council at gnso.icann.org<mailto:council at gnso.icann.org>" <council at gnso.icann.org<mailto:council at gnso.icann.org>>
Subject: [council] GAC Communique

All,

Please find enclosed the GAC Communique from Cancun.  I have not yet gone through this, so I am sending it as I get it.  I believe  Mark, Susan, Manju, Bruna and Desiree have volunteered to review and provide comment.  I will work with staff to set up a Google Doc for our response.

Sincerely,

Jeff

[cid:image003.png at 01D95BE0.1C75BBA0]
Jeffrey J. Neuman
Founder & CEO
JJN Solutions, LLC
p: +1.202.549.5079
E: jeff at jjnsolutions.com<mailto:jeff at jjnsolutions.com>
http://jjnsolutions.com [jjnsolutions.com]<https://urldefense.com/v3/__http:/jjnsolutions.com__;!!PtGJab4!4RdeEYal8bsxlKvd_3prjpnKRL4sBT-iT_hz8uIWqpv76JlQgKm4Ba_4gwXne5-0vrH0k0bBYYAYMAkVNuvFXeMb43nLIA$>


This email originated from outside the firm. Please use caution.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/council/attachments/20230321/1273730d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 67520 bytes
Desc: image002.png
URL: <https://mm.icann.org/pipermail/council/attachments/20230321/1273730d/image002-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 67521 bytes
Desc: image003.png
URL: <https://mm.icann.org/pipermail/council/attachments/20230321/1273730d/image003-0001.png>