[gnso-gac-closed-generics] Approach to Remaining Closed Generics Facilitated Dialogue Work

Kathy Kleiman kathy at dnrc.tech
Mon Jul 17 15:25:42 UTC 2023


+1 Manal. I think our discussion in the last meeting was right. As 
people wanted to talk with us at ICANN77 about our draft CG Framework, 
they will want to talk with us about our final CG Framework in ICANN78.

Best, Kathy


On 7/17/2023 8:10 AM, Manal Ismail wrote:
>
> Many thanks Melissa and the Policy team for the shared summary ..
>
> I confirm that the summary accurately reflects what was agreed on the 
> call .. I also agree with Jeff, Nigel and Sophie that we cannot “bind” 
> the GAC, GNSO or ALAC to a certain timeline, and also agree with Jeff 
> and Nigel on remaining available to provide clarification or answer 
> questions at ICANN78 ..
>
> Kind Regards
>
> --Manal
>
> *From:* gnso-gac-closed-generics 
> <gnso-gac-closed-generics-bounces at icann.org> *On Behalf Of *Sophie Hey
> *Sent:* Thursday, July 13, 2023 12:55 PM
> *To:* Nigel Hickson <nigel.hickson at dcms.gov.uk>; jeff at jjnsolutions.com
> *Cc:* gnso-gac-closed-generics at icann.org
> *Subject:* Re: [gnso-gac-closed-generics] Approach to Remaining Closed 
> Generics Facilitated Dialogue Work
>
> Thank you, Melissa for summarising our discussion on Monday.
>
> I agree with the sentiments of Nigel and Jeff – that we cannot “bind” 
> the GAC, GNSO or ALAC, so it should not be part of our timeline. I am 
> fine with the communication of the Framework to the GAC, GNSO, Board 
> and ALAC being part of our timeline and the conclusion of our work.
>
> I also support the approach of the group deciding together whether a 
> discussion should be held under Chatham House Rules.
>
> Sophie Hey
> she/her
> Policy Advisor
> Com Laude
> *T*+44 (0) 20 7421 8250
> *Ext* 252
>
> image <https://comlaude.com/>
>
> /We are pleased to launch our //new YouTube channel/ 
> <https://t-uk.xink.io/Tracking/Index/bhkAAGVfAADl_RQA0>.
>
> *From:* gnso-gac-closed-generics 
> <gnso-gac-closed-generics-bounces at icann.org> *On Behalf Of *Nigel 
> Hickson via gnso-gac-closed-generics
> *Sent:* Wednesday, July 12, 2023 5:47 PM
> *To:* jeff at jjnsolutions.com
> *Cc:* gnso-gac-closed-generics at icann.org
> *Subject:* Re: [gnso-gac-closed-generics] Approach to Remaining Closed 
> Generics Facilitated Dialogue Work
>
> Good evening
>
> Thank you Melissa for this communication noting the agreement we 
> reached on our Call in week.
>
> On points of Jeff; agree that in substance our work is probably done 
> once we deliver the Framework (so to speak); but also agree that it 
> would be very useful for there to be a "listening" session at ICANN78 
> where we could perhaps provide any clarification Community members may 
> want on the Framework (if agreed).
>
> Also agree Jeff that while we would expect definitive reactions at 
> ICANN78 we cannot indeed "bind" the GAC, ALAC, GNSO etc.
>
> all best
>
> Nigel
>
> On Tue, 11 Jul 2023 at 15:50, jeff at jjnsolutions.com 
> <mailto:jeff at jjnsolutions.com><jeff at jjnsolutions.com 
> <mailto:jeff at jjnsolutions.com>> wrote:
>
>     I am in agreement with the path forward and especially with the
>     transparency requirements going forward.  My view has always been,
>     and continues to be, that everything we do is transparent. This
>     means the new mailing list and allowing observers to sign up to
>     receive the emails, and recording our calls and releasing the
>     recordings, transcripts (if any), notes, chats, etc.
>
>     Upon rethinking the time line, I believe our time line should end
>     the week of September 25th. Once we submit the final framework to
>     the community, our work is done.  I am not sure we can set any
>     deadlines for the GAC, GNSO or ALAC (as we have below during ICANN
>     78).  If they do whatever it is that they are going to do by then,
>     great.  If not, its not really our business as this team.  So
>     perhaps we can be available during ICANN 78 to answer questions,
>     but other than that, we should not be responsible for compiling
>     any feedback or anything else once we have turned the framework
>     over to the respective SOs/ACs.  What the SOs / ACs do with it, is
>     up to them.
>
>     Sincerely,
>
>     Jeff
>
>     imap://kathy%40dnrc%2Etech@a2plcpnl0836.prod.iad2.secureserver.net:993/fetch%3EUID%3E.INBOX%3E18593?header=quotebody&part=1.1.2&filename=image004.png
>
>     ------ Original Message ------
>
>     From "Melissa Peters Allgood" <melissa.allgood at icann.org
>     <mailto:melissa.allgood at icann.org>>
>
>     To "gnso-gac-closed-generics at icann.org
>     <mailto:gnso-gac-closed-generics at icann.org>"
>     <gnso-gac-closed-generics at icann.org
>     <mailto:gnso-gac-closed-generics at icann.org>>
>
>     Date 7/11/2023 8:40:06 AM
>
>     Subject [gnso-gac-closed-generics] Approach to Remaining Closed
>     Generics Facilitated Dialogue Work
>
>         Hello all,
>
>         We dedicated our 10 July discussion to determining how the
>         group wants to navigate the next phase of your work. Below
>         please find a summary of our discussion.
>
>         *//*
>
>         */Compiling Community Feedback/*
>
>         As community feedback is submitted, it is being publicly
>         archived
>         <https://mm.icann.org/pipermail/closed-generics-feedback/>on
>         the Closed Generics wiki page
>         <https://community.icann.org/display/GFDOCG/FOR+INPUT%3A+Draft+Framework+for+Closed+Generic+gTLDs>.
>         After the 15 July deadline, staff will consolidate all
>         community feedback into a table for this group to review, in a
>         manner similar to how  public comments in a policy development
>         process are handled. This group will then work through the
>         table during weekly calls and consider the feedback received,
>         denoting the actions (if any) to be taken on each input, and
>         updating the Framework document accordingly. The community
>         input table and any Final Framework will be published on the
>         wiki for transparency.
>
>         */Transparency/*
>
>         Review of community inputs will begin on the 19 July call, and
>         the group broadly agreed that session recordings from this
>         point forward should be posted on the public portion of the
>         wiki space. Group meetings will not be open to live observation.
>
>         The group further agreed that a new mailing list, one which
>         allows for observers to sign up for read-only access, will be
>         created and utilized for discussions pertaining to review of
>         community inputs. Observers will not have the ability to post
>         or contribute to active discussions on the new mailing list.
>
>         In relation to a  possible need to discuss a matter, whether
>         on the mailing list or in-session, under Chatham House Rule,
>         the  group generally agreed that should a participant feel
>         there is such a need, they will make the request directly to
>         Melissa. It is incumbent upon the requester to explain why the
>         situation warrants a more private discussion space. Melissa
>         will then indicate on the open mailing list that such a
>         request has been made and the group will discuss whether the
>         topic should be moved to  the closed mailing list or further
>         discussed in closed session. Where this occurs, the staff will
>         follow the practice to date of publishing high-level  notes
>         without specific attribution on the public wiki page.
>
>         */Approach to the Review of Community Feedback and Input/*
>
>         The group found broad agreement with the following approach to
>         consideration of community inputs:
>
>           * Keep the review at a framework level.
>           * Address areas where the community identifies a need for
>             clarification.
>           * Only modify the substance of the  Draft Framework where
>             community feedback indicates that a substantive point was
>             missed by this group or where there is broad community
>             sentiment that this group got an issue wrong.
>
>               o It was noted that we might need a bit of flexibility
>                 on this point, with the understanding that the group
>                 is focused on moving the overall effort forward and
>                 not relitigating matters that were discussed during
>                 deliberations  on the Draft Framework.
>
>         */Timeline & Scheduling/*
>
>         This timeline is based on a  typical volume  of community
>         input and is subject to change should there be an unusual 
>         number of community submissions. The agreed timeline will be
>         published on the wiki page.
>
>           * 19 July – 21 August
>
>               o The  group will consider community feedback in line
>                 with the approach noted above
>
>           * 28 August – 11 September
>
>               o The group will review draft  text of the Final Framework
>               o Note: 4 September is a US holiday, so we will meet on
>                 6 September instead
>
>           * 18 September
>
>               o Each of you will indicate whether you stand behind the
>                 Final Framework document.
>
>           * 25 September
>
>         oShould there be agreement amongst  the group, the Final
>         Framework document will be sent to the GAC, GNSO Council, and
>         ALAC, for each to indicate whether it supports or does not
>         support the Final Framework.
>
>           * Week of 23 October (ICANN78)
>
>         oDeadline for the GAC, GNSO Council, and ALAC to respond
>         indicating support (or otherwise) for the Final Framework
>         document.
>
>         oThis group will be responsible for compiling and officially
>         transmitting the GAC, GNSO Council, and ALAC feedback on the
>         Final Framework to the GNSO Council. At that point, the work 
>         of the Facilitated Dialogue will be considered  concluded and
>         the group will disband. There will not be an additional round
>         of community feedback on the Final Framework.
>
>         For our calls going forward, the  group had a slight
>         preference for Monday meetings, so calls will rotate between
>         12:30 UTC and 20:00 UTC on Mondays. Exceptions are Wednesday,
>         19 July and 6 September. Terri has sent the relevant meeting
>         invitations.
>
>         I hope that we are  all in agreement as we prepare to begin
>         deliberations of community inputs.
>
>         Please respond to this email indicating your agreement and/or
>         areas of concern (if any) by 18 July 2023 at 23:59 UTC. Thank you!
>
>         All the best,
>
>         Melissa (on behalf of the Policy team supporting the Closed
>         Generics Facilitated Dialogue)
>
>     _______________________________________________
>     gnso-gac-closed-generics mailing list
>     gnso-gac-closed-generics at icann.org
>     <mailto:gnso-gac-closed-generics at icann.org>
>     https://mm.icann.org/mailman/listinfo/gnso-gac-closed-generics
>     <https://mm.icann.org/mailman/listinfo/gnso-gac-closed-generics>
>
>     _______________________________________________
>     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.
>
> ------------------------------------------------------------------------
>
> The contents of this email and any attachments are confidential to the 
> intended recipient. They may not be disclosed, used by or copied in 
> any way by anyone other than the intended recipient. If you have 
> received this message in error, please return it to the sender 
> (deleting the body of the email and attachments in your reply) and 
> immediately and permanently delete it. Please note that Com Laude 
> Group Limited (the “Com Laude Group”) does not accept any 
> responsibility for viruses and it is your responsibility to scan or 
> otherwise check this email and any attachments. The Com Laude Group 
> does not accept liability for statements which are clearly the 
> sender's own and not made on behalf of the group or one of its member 
> entities. The Com Laude Group is a limited company registered in 
> England and Wales with company number 10689074 and registered office 
> at 28-30 Little Russell Street, London, WC1A 2HN England. The Com 
> Laude Group includes Nom-IQ Limited t/a Com Laude, a company 
> registered in England and Wales with company number 5047655 and 
> registered office at 28-30 Little Russell Street, London, WC1A 2HN 
> England; Valideus Limited, a company registered in England and Wales 
> with company number 6181291 and registered office at 28-30 Little 
> Russell Street, London, WC1A 2HN England; Demys Limited, a company 
> registered in Scotland with company number SC197176 and registered 
> office at 15 William Street, South West Lane, Edinburgh, EH3 7LL 
> Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a 
> corporation incorporated in the State of Washington and principal 
> office address at Suite 332, Securities Building, 1904 Third Ave, 
> Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered 
> in Japan with company number 0100-01-190853 and registered office at 
> 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP 
> S.L.U., a company registered in Spain and registered office address at 
> Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see 
> www.comlaude.com <https://comlaude.com/>
>
>
> _______________________________________________
> gnso-gac-closed-generics mailing list
> gnso-gac-closed-generics at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-gac-closed-generics
>
> _______________________________________________
> 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.

-- 
Kathy Kleiman
President, Domain Name Rights Coalition
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/gnso-gac-closed-generics/attachments/20230717/ee4aaa2c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 4071 bytes
Desc: not available
URL: <https://mm.icann.org/pipermail/gnso-gac-closed-generics/attachments/20230717/ee4aaa2c/image002-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 11989 bytes
Desc: not available
URL: <https://mm.icann.org/pipermail/gnso-gac-closed-generics/attachments/20230717/ee4aaa2c/image004-0001.png>


More information about the gnso-gac-closed-generics mailing list