[council] GAC Communique

Anne ICANN anneicanngnso at gmail.com
Tue Mar 21 19:19:56 UTC 2023


Hi Jeff and Paul.  Maybe you guys should let the small team meet first to
address these questions and before a draft is prepared by anyone?
Anne
Anne Aikman-Scalese
GNSO Councilor
NomCom Non-Voting 2022-2024
anneicanngnso at gmail.com


On Tue, Mar 21, 2023 at 12:14 PM Jeff Neuman via council <
council at gnso.icann.org> wrote:

> Understood, but the decision ultimately is for the Council.  Leadership
> can help guide if you want them to.
>
> As Emily stated, it is sometimes harder to get small teams to respond.  I
> would be happy to put together a first draft of a response if you would
> like.  I can send that around in next 24 hours.
>
> Remember our response if most helpful to the Board if we can get it in
> prior to the Board meeting with the GAC on the Communique.
>
> Sincerely,
>
>
> Jeffrey J. Neuman
> Founder & CEO
> JJN Solutions, LLC
> Jeff at JJNSolutions.com
> +1.202.549.5079
> Http://www.jjnsolutions.com
>
>
> ------------------------------
> *From:* Paul McGrady <paul at elstermcgrady.com>
> *Sent:* Tuesday, March 21, 2023 10:33 AM
> *To:* Jeff Neuman <jeff at jjnsolutions.com>; Emily Barabas <
> emily.barabas at icann.org>; council at gnso.icann.org <council at gnso.icann.org>
> *Subject:* RE: [council] GAC Communique
>
>
> Thanks Jeff.  Neither you nor I are Council Leadership so it is up to them
> to decide how they want to handle.  I am merely suggesting a different
> process since we have all of these Small Teams now and the “way we have
> always done it” may not be the most efficient or fulsome way.  But, again,
> this is up to Council Leadership and not me.
>
>
>
> Best,
>
> Paul
>
>
>
>
>
> *From:* Jeff Neuman <jeff at jjnsolutions.com>
> *Sent:* Tuesday, March 21, 2023 9:30 AM
> *To:* Paul McGrady <paul at elstermcgrady.com>; Emily Barabas <
> emily.barabas at icann.org>; council at gnso.icann.org
> *Subject:* RE: [council] GAC Communique
>
>
>
> 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
>
>
>
>
>
>
>
> Jeffrey J. Neuman
>
> Founder & CEO
>
> JJN Solutions, LLC
>
> p: +1.202.549.5079
>
> E: 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> *On Behalf Of *Emily
> Barabas via council
> *Sent:* Monday, March 20, 2023 2:54 PM
> *To:* 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> on behalf of Jeff Neuman
> via council <council at gnso.icann.org>
> *Reply to: *Jeff Neuman <jeff at jjnsolutions.com>
> *Date: *Monday, 20 March 2023 at 16:33
> *To: *"council at gnso.icann.org" <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
>
>
>
> Jeffrey J. Neuman
>
> Founder & CEO
>
> JJN Solutions, LLC
>
> p: +1.202.549.5079
>
> E: 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.
> _______________________________________________
> council mailing list
> council at gnso.icann.org
> https://mm.icann.org/mailman/listinfo/council
>
> _______________________________________________
> 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) and
> the website Terms of Service (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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/council/attachments/20230321/46c89166/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 67520 bytes
Desc: not available
URL: <https://mm.icann.org/pipermail/council/attachments/20230321/46c89166/image001-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 67521 bytes
Desc: not available
URL: <https://mm.icann.org/pipermail/council/attachments/20230321/46c89166/image002-0001.png>


More information about the council mailing list