[council] [Ext] RE: GAC Communique

Tue Mar 21 13:44:22 UTC 2023

Thanks Emily.  I think our small teams are pretty active and could move much more quickly on each of the issues than an ad hoc small team trying to get up to speed and remaining consistent with the work of the substantive small teams, but if that is Council Leadership’s decision, I will leave it undisturbed.  😊

Best,
Paul

From: Emily Barabas <emily.barabas at icann.org>
Sent: Tuesday, March 21, 2023 5:07 AM
To: Paul McGrady <paul at elstermcgrady.com>; council at gnso.icann.org
Subject: Re: [Ext] RE: [council] GAC Communique

Hi Paul,

Thanks for brainstorming potential new ways of working. For context, I think the main reason we currently use a single small team to organize the work is the quick turnaround needed for the Communique review. Council typically aims to have the review sent to the GAC before the GAC meets with the Board to go over any clarifying questions about the Communique.

In some cases, our small teams on the relevant subjects may be dormant or may be meeting only on as-needed basis. It may be a challenge to get each of these groups to meet, consolidate responses, and have Council review the final draft in the target timeframe. In practice, we have encouraged relevant SMEs from the different subjects and groups to be a part of the Communique Review. The draft response always goes back to the full Council for review in case anything needs to be added or polished.

With that said, we are still welcoming Councilors to sign up for the Communique Review small team, especially those with expertise in the Communique topics:

  *   GAC Advice: IGO Protections, Registration Data Request System (RDRS), Privacy and Proxy Services
  *   Issues of Importance: Subsequent Rounds of New gTLDs, DNS Abuse, Registration Data, Transparency in GNSO Participation (SOIs), Emergency Assistance Program

Kind regards,
Emily

From: Paul McGrady <paul at elstermcgrady.com<mailto:paul at elstermcgrady.com>>
Date: Monday, 20 March 2023 at 21:08
To: Emily Barabas <emily.barabas at icann.org<mailto:emily.barabas at icann.org>>, "council at gnso.icann.org<mailto:council at gnso.icann.org>" <council at gnso.icann.org<mailto:council at gnso.icann.org>>
Subject: [Ext] 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 [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1829lKsBSn_O0ecSeI4FFLBhLymLAKIs9gx81P_6n3yw/edit?usp=sharing__;!!PtGJab4!6RNq_39fwbFwN0cvfULjeCC6OTY33UjNrFMpmyiKZ13ZGq9KfYy1f3kfdhz3XiOzqrln8gxd-xFhKR2hMTRnIOtKkIM$>

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 [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1ziBDcQ1eqjI_DXIORpnevzqXIaoVo_5LJ60sJvJE5xM/edit?usp=sharing__;!!PtGJab4!6RNq_39fwbFwN0cvfULjeCC6OTY33UjNrFMpmyiKZ13ZGq9KfYy1f3kfdhz3XiOzqrln8gxd-xFhKR2hMTRncSpBqhU$>. 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:image001.png at 01D95BD1.549BCF10]
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.
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/a3b69b99/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 67522 bytes
Desc: image001.png
URL: <https://mm.icann.org/pipermail/council/attachments/20230321/a3b69b99/image001-0001.png>