<div dir="ltr"><div dir="ltr">Good evening </div><div dir="ltr"><br></div><div dir="ltr">Thank you Melissa for this communication noting the agreement we reached on our Call in week. </div><div dir="ltr"><br></div><div>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). </div><div><br></div><div>Also agree Jeff that while we would expect definitive reactions at ICANN78 we cannot indeed "bind" the GAC, ALAC, GNSO etc. </div><div><br></div><div>all best </div><div><br></div><div>Nigel </div><div dir="ltr"><div><br></div><div><br><div><br></div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 11 Jul 2023 at 15:50, <a href="mailto:jeff@jjnsolutions.com" target="_blank">jeff@jjnsolutions.com</a> <<a href="mailto:jeff@jjnsolutions.com" target="_blank">jeff@jjnsolutions.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<div><div>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.</div><div><br></div><div>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.</div><div><br></div><div><br></div><div>Sincerely,</div><div><br></div><div>Jeff</div><div><br></div><div><br></div>
<div><br></div><div id="m_-6971526983716388139m_2115424978724227884m_1492021632885430462signature_old" style="clear:both"><div><br></div><img src="cid:18949aaaa4b6570be861" border="0"></div><div style="clear:both"><br></div>
<div><br></div>
<div>
<div>------ Original Message ------</div>
<div>From "Melissa Peters Allgood" <<a href="mailto:melissa.allgood@icann.org" target="_blank">melissa.allgood@icann.org</a>></div>
<div>To "<a href="mailto:gnso-gac-closed-generics@icann.org" target="_blank">gnso-gac-closed-generics@icann.org</a>" <<a href="mailto:gnso-gac-closed-generics@icann.org" target="_blank">gnso-gac-closed-generics@icann.org</a>></div>
<div>Date 7/11/2023 8:40:06 AM</div>
<div>Subject [gnso-gac-closed-generics] Approach to Remaining Closed Generics Facilitated Dialogue Work</div></div><div><br></div>
<div id="m_-6971526983716388139m_2115424978724227884m_1492021632885430462xc8384406fa2b4ad"><blockquote cite="http://6AF4416A-8E95-4CE9-AF21-B85EBF16DCBD@icann.org" type="cite">
<div>
<div>
<div>
<p style="margin:0in">Hello all,<u></u><u></u></p>
<p style="margin:0in"> <u></u><u></u></p>
<p style="margin:0in">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.<u></u><u></u></p>
<p style="margin:0in"><b><i> </i></b><u></u><u></u></p>
<p style="margin:0in"><b><i>Compiling Community Feedback</i></b><u></u><u></u></p>
<p style="margin:0in">As community feedback is submitted, it is being publicly
<a href="https://mm.icann.org/pipermail/closed-generics-feedback/" target="_blank">archived</a> on the Closed Generics
<a href="https://community.icann.org/display/GFDOCG/FOR+INPUT%3A+Draft+Framework+for+Closed+Generic+gTLDs" target="_blank">wiki page</a>. 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.
<u></u><u></u></p>
<p style="margin:0in"> <u></u><u></u></p>
<p style="margin:0in"><b><i>Transparency</i></b><u></u><u></u></p>
<p style="margin:0in">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.
<u></u><u></u></p>
<p style="margin:0in"> <u></u><u></u></p>
<p style="margin:0in">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.
<u></u><u></u></p>
<p style="margin:0in"> <u></u><u></u></p>
<p style="margin:0in">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.
<u></u><u></u></p>
<p style="margin:0in"> <u></u><u></u></p>
<p style="margin:0in"><b><i>Approach to the Review of Community Feedback and Input</i></b><u></u><u></u></p>
<p style="margin:0in">The group found broad agreement with the following approach to consideration of community inputs:<u></u><u></u></p>
<ul style="margin-top:0in" type="disc">
<li style="color:black;margin-top:0in;margin-bottom:0in;vertical-align:baseline">
Keep the review at a framework level.<u></u><u></u></li><li style="color:black;margin-top:0in;margin-bottom:0in;vertical-align:baseline">
Address areas where the community identifies a need for clarification.<u></u><u></u></li><li style="color:black;margin-top:0in;margin-bottom:0in;vertical-align:baseline">
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.<u></u><u></u></li></ul>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<li style="color:black;margin-top:0in;margin-bottom:0in;vertical-align:baseline">
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.<u></u><u></u></li></ul>
</ul>
<p style="margin:0in"> <u></u><u></u></p>
<p style="margin:0in"><b><i>Timeline & Scheduling</i></b><u></u><u></u></p>
<p style="margin:0in">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.<u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"><br>
<br>
<u></u><u></u></span></p>
<ul style="margin-top:0in" type="disc">
<li style="color:black;margin-top:0in;margin-bottom:0in;vertical-align:baseline">
19 July – 21 August<u></u><u></u></li></ul>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<li style="color:black;margin-top:0in;margin-bottom:0in;vertical-align:baseline">
The group will consider community feedback in line with the approach noted above<u></u><u></u></li></ul>
</ul>
<ul style="margin-top:0in" type="disc">
<li style="color:black;margin-top:0in;margin-bottom:0in;vertical-align:baseline">
28 August – 11 September<u></u><u></u></li></ul>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<li style="color:black;margin-top:0in;margin-bottom:0in;vertical-align:baseline">
The group will review draft text of the Final Framework<u></u><u></u></li><li style="color:black;margin-top:0in;margin-bottom:0in;vertical-align:baseline">
Note: 4 September is a US holiday, so we will meet on 6 September instead<u></u><u></u></li></ul>
</ul>
<ul style="margin-top:0in" type="disc">
<li style="color:black;margin-top:0in;margin-bottom:0in;vertical-align:baseline">
18 September<u></u><u></u></li></ul>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="circle">
<li style="color:black;margin-top:0in;margin-bottom:0in;vertical-align:baseline">
Each of you will indicate whether you stand behind the Final Framework document.<u></u><u></u></li></ul>
</ul>
<ul style="margin-top:0in" type="disc">
<li style="color:black;margin-top:0in;margin-bottom:0in;vertical-align:baseline">
25 September<u></u><u></u></li></ul>
<p style="margin-right:0in;margin-bottom:0in;margin-left:1in;vertical-align:baseline">
<span style="font-size:10pt;font-family:"Courier New"">o<span style="font-style:normal;font-variant:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"Times New Roman"">
</span></span>Should 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.<u></u><u></u></p>
<ul style="margin-top:0in" type="disc">
<li style="color:black;margin-top:0in;margin-bottom:0in;vertical-align:baseline">
Week of 23 October (ICANN78)<u></u><u></u></li></ul>
<p style="margin-right:0in;margin-bottom:0in;margin-left:1in;vertical-align:baseline">
<span style="font-size:10pt;font-family:"Courier New"">o<span style="font-style:normal;font-variant:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"Times New Roman"">
</span></span>Deadline for the GAC, GNSO Council, and ALAC to respond indicating support (or otherwise) for the Final Framework document.<u></u><u></u></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:1in;vertical-align:baseline">
<span style="font-size:10pt;font-family:"Courier New"">o<span style="font-style:normal;font-variant:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"Times New Roman"">
</span></span>This 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.
<u></u><u></u></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:0.75in">
<u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p style="margin:0in">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.
<u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p style="margin:0in"><span style="color:red"> </span>I hope that we are all in agreement as we prepare to begin deliberations of community inputs. <u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p style="margin:0in"><span style="color:red">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!</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:11pt">All the best, <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Melissa (on behalf of the Policy team supporting the Closed Generics Facilitated Dialogue)<u></u><u></u></span></p>
</div>
</blockquote></div>
</div>_______________________________________________<br>
gnso-gac-closed-generics mailing list<br>
<a href="mailto:gnso-gac-closed-generics@icann.org" target="_blank">gnso-gac-closed-generics@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-gac-closed-generics" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-gac-closed-generics</a><br>
<br>
_______________________________________________<br>
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 (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). 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.</div></blockquote></div>
</div>