<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Melissa,</p>
<p>My answers below. I do have some questions about the Information
you/we are proposing to share with the GNSO Council. I think we
can be broader and more inclusive of ideas already discussed<font
color="#00ff00"><b>.</b></font></p>
<p>Timeline:</p>
<p>1. Fine.</p>
<p>2. April 26th fine.</p>
<p>3. April 19th, the early call I can make. I may not be able to
attend a later call, but support its scheduling if others do. OK
for another staff member to step in - although we'll miss you! <br>
</p>
<p class="MsoNormal"> <b><i>Increasing transparency</i></b>
</p>
<p class="MsoNormal">Assuming the group agrees upon a framework,
once that work is shared with the broader community would you like
to increase transparency into the work you’ve done? If so, options
include:
</p>
<ol style="margin-top:0in" type="1" start="1">
<li class="MsoListParagraphCxSpFirst"
style="margin-left:0in;mso-add-space:auto;mso-list:l0 level1
lfo2">
Open the wiki page, making call recordings and notes publicly
available. ==> <b>I think once we release the version to
circulate to the Community at the end of the month, we can
open things up. We are still covered by our agreed-upon
confidentiality and practices now, and to get to the finish
line of our Framework for circulation by the end of the month,
we should not change our agreed-upon rules of operation. I do
not think we should open the current drafts we are working on
- for the very reasons we discussed all along. </b><br>
</li>
<li class="MsoListParagraphCxSpLast"
style="margin-left:0in;mso-add-space:auto;mso-list:l0 level1
lfo2">
Allow observers to attend future calls, including the two
sessions scheduled for ICANN77. => <b>Starting after our
publication at the end of April (which I think is what you
mean).</b></li>
</ol>
<p><b><i>Information to share with GNSO Council while you deliberate
on substantive framework elements</i></b>
</p>
Melissa wrote: <<
<p class="MsoNormal">“To the extent this group agrees upon a
framework, the expectation is that it will include types of
things/information that will be requested of applicants to be
included in the application, elements that will be evaluated in
the application process, and protections following implementation,
likely PICs. The dialogue group is also likely to provide a list
of policy areas where the policy process needs to do further work
to fill in gaps within the framework.”>></p>
<p class="MsoNormal"><br>
</p>
<p class="MsoNormal"><b>==> I think we are too detailed here,
including with details we have not agreed to (and truly don't
need at this time). I suggest the following abbreviated language
(for the reasons below): </b><b><br>
</b></p>
<p class="MsoNormal">“To the extent this group agrees upon a
framework, the expectation is that it will include types of
things/information that will be requested of applicants to be
included in the application, elements that will be evaluated in
the application process, and protections following implementation
[add: over the course of the gTLD contract]. The dialogue group is
also likely to provide a list of policy areas where the policy
process needs to do further work to fill in gaps within the
framework.”>></p>
<p class="MsoNormal"><b><br>
</b></p>
<p class="MsoNormal"><b>==> The change: Let's delete "like PICs"
as we have not agreed on it at all. What we discussed is putting
post-contract obligations into the Registry Agreement, and we
followed that with discussion(s) of where these ongoing registry
obligations would go, including at least two discussions (I
think) of <u>Specification 13, </u>for .BRAND gTLDs (the other
group of closed gTLDs), where they lay everything out clearly
for their initial and ongoing obligations. We also discussed
that PICs/Public Interest Commitments might be a very messy
place to put these important ongoing closed generic gTLD
obligations. While we may include some ideas in our Framework
and its explanatory documents, for the GNSO Council, I think
these too words are drilling down on details beyond our scope.
If we delete "like PICs," I'm good with this - and support this
message to Council. <br>
</b></p>
<p class="MsoNormal"><br>
</p>
<p class="MsoNormal">Best regards,</p>
<p class="MsoNormal">Kathy<br>
</p>
<p class="MsoNormal"><br>
</p>
<p class="MsoNormal"><br>
</p>
<div class="moz-cite-prefix">On 4/11/2023 5:35 PM, Melissa Peters
Allgood wrote:<br>
</div>
<blockquote type="cite"
cite="mid:F7918B32-9059-4A31-91F6-34AB77A62744@icann.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 11 6 4 2 2 2 2 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}div.WordSection1
{page:WordSection1;}ol
{margin-bottom:0in;}ul
{margin-bottom:0in;}</style>
<div class="WordSection1">
<p class="MsoNormal">Hi all, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In the interest of dedicating our call time
to framework substance, I was hoping we could resolve a few
outstanding matters on this mailing list. Please respond to
each question.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><i>Timeline (email and document from
Mary Wong on 3 April attached)<o:p></o:p></i></b></p>
<ol style="margin-top:0in" type="1" start="1">
<li class="MsoListParagraphCxSpFirst"
style="margin-left:0in;mso-add-space:auto;mso-list:l1 level1
lfo1">
Are there any objections?<o:p></o:p></li>
<li class="MsoListParagraphCxSpMiddle"
style="margin-left:0in;mso-add-space:auto;mso-list:l1 level1
lfo1">
Is anyone opposed to adding a call on 26 April? <o:p></o:p>
<ol style="margin-top:0in" type="a" start="1">
<li class="MsoListParagraphCxSpMiddle"
style="margin-left:0in;mso-add-space:auto;mso-list:l1
level2 lfo1">
If you agree, this will give us 4 calls (12 April, 19
April, 24 April, and 26 April) to work through the
strawman document and review the agreed framework
outputs before sharing with the broader community.
<o:p></o:p></li>
</ol>
</li>
<li class="MsoListParagraphCxSpMiddle"
style="margin-left:0in;mso-add-space:auto;mso-list:l1 level1
lfo1">
I can only make the first 45 minutes of the 19 April call,
currently scheduled for 12:30 UTC. Are you opposed to
another org staff member stepping in to complete that call?<o:p></o:p>
<ol style="margin-top:0in" type="a" start="1">
<li class="MsoListParagraphCxSpLast"
style="margin-left:0in;mso-add-space:auto;mso-list:l1
level2 lfo1">
The alternative is to move the 19 April call to 20:00
UTC the same day and I will be present the entire time.<o:p></o:p></li>
</ol>
</li>
</ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><i>Increasing transparency<o:p></o:p></i></b></p>
<p class="MsoNormal">Assuming the group agrees upon a framework,
once that work is shared with the broader community would you
like to increase transparency into the work you’ve done? If
so, options include:
<o:p></o:p></p>
<ol style="margin-top:0in" type="1" start="1">
<li class="MsoListParagraphCxSpFirst"
style="margin-left:0in;mso-add-space:auto;mso-list:l0 level1
lfo2">
Open the wiki page, making call recordings and notes
publicly available. <o:p></o:p></li>
<li class="MsoListParagraphCxSpLast"
style="margin-left:0in;mso-add-space:auto;mso-list:l0 level1
lfo2">
Allow observers to attend future calls, including the two
sessions scheduled for ICANN77.
<o:p></o:p></li>
</ol>
<p class="MsoNormal">Please respond with your preferred
approach. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><i>Information to share with GNSO
Council while you deliberate on substantive framework
elements<o:p></o:p></i></b></p>
<p class="MsoNormal">In the interest of working in parallel with
other groups, is there any objection to the following
information being shared with GNSO Council while you
deliberate on framework elements:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">“To the extent this group agrees upon a
framework, the expectation is that it will include types of
things/information that will be requested of applicants to be
included in the application, elements that will be evaluated
in the application process, and protections following
implementation, likely PICs. The dialogue group is also likely
to provide a list of policy areas where the policy process
needs to do further work to fill in gaps within the
framework.”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you for your continued dedication.
The end is in sight.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Melissa<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
gnso-gac-closed-generics mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gnso-gac-closed-generics@icann.org">gnso-gac-closed-generics@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-gac-closed-generics">https://mm.icann.org/mailman/listinfo/gnso-gac-closed-generics</a>
_______________________________________________
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 class="moz-txt-link-freetext" href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/tos">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.</pre>
</blockquote>
</body>
</html>