<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt">Dear </span>Working Group members,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Please see below the notes from the meeting on 20 February 1500 UTC.
<b><i>These high-level notes are designed to help WG members navigate through the content of the call and are not a substitute for the recording, transcript, or the chat,</i></b> which will be posted at:
<a href="https://community.icann.org/display/NGSPP/2020-02-20+New+gTLD+Subsequent+Procedures+PDP">
https://community.icann.org/display/NGSPP/2020-02-20+New+gTLD+Subsequent+Procedures+PDP</a>.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Kind regards,<br>
Julie<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Notes and Action Items:</b><o:p></o:p></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b>Actions:</b><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">ACTION ITEM: Call for proposals on how to address closed generics to be discussed in one of the remote PDP ICANN67 sessions. Deadline is 29 February 2020.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>Notes:</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">1. Review Agenda/Statements of Interest: No updates provided.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">2. Review draft final recommendations – see attached Working Document and here:<a href="https://docs.google.com/document/d/1kUlmZH8nxWTgfcRluA5FxLheMm4XhhOwkRt7om52aQU/edit?usp=sharing">https://docs.google.com/document/d/1kUlmZH8nxWTgfcRluA5FxLheMm4XhhOwkRt7om52aQU/edit?usp=sharing</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">2.7.3 Closed Generics (page 33)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-- This is an opportunity to treat this as a unique policy setting process.<o:p></o:p></p>
<p class="MsoNormal">-- We should explore what can be done going forward rather than looking at what was done.<o:p></o:p></p>
<p class="MsoNormal">-- The definition of the term “generic” would be the definition that is in the agreement itself in Spec 11.<o:p></o:p></p>
<p class="MsoNormal">-- The question is: Is there any situation where you would support a closed generic?<o:p></o:p></p>
<p class="MsoNormal">-- Suggestion: “A closed generic could be considered for approval by the ICANN board if there is a compelling reason presented in the application that indicates it would NOT be in the public interest to have the gTLD open.”<o:p></o:p></p>
<p class="MsoNormal">-- We don’t have the evidence that there is a severe problem because we’ve never allowed it in the first place.<o:p></o:p></p>
<p class="MsoNormal">-- If we say there can be no closed generics, but we do acknowledge that registries should be able to be creative and innovative. <o:p></o:p></p>
<p class="MsoNormal">-- List out the problems that people face and see if we can overcome those specific problems.<o:p></o:p></p>
<p class="MsoNormal">-- Suggest: "If you restrict access to your gTLD there will be an expectation that you might be forced to revert to an open registry - UNLESS you can prove that the restrictions are serving the Public Interest."<o:p></o:p></p>
<p class="MsoNormal">-- Question: What is the status quo if we do nothing? The WG has different views on that. Is it the AGB? Or is it implementation? Answer: It’s more productive at this point to see if there is a solution.<o:p></o:p></p>
<p class="MsoNormal">-- Question: What is the impact on previous applicants who opened their TLDs as a result of the last round?<o:p></o:p></p>
<p class="MsoNormal">-- It would also be good if folks could articulate the harm in closed generics because I'm really sure I have a good understanding on that either.<o:p></o:p></p>
<p class="MsoNormal">-- We need to say that we believe the default is: 1) the AGB and they are allowed; or 2) the implementation and they are not allowed; or 3) that it is out of our scope to interpret the Board resolution and the Board has to say.<o:p></o:p></p>
<p class="MsoNormal">-- Look at the list of cons in the Initial Report as the identified problem.<o:p></o:p></p>
<p class="MsoNormal">-- What about putting into the AGB: "In the 2012 round the board denied to contract closed generic registries on the basis of GAC advice (no public benefit). There is an expectation that in absence of compelling proof of Public Interest
any closed generic might be denied contracting again."<o:p></o:p></p>
<p class="MsoNormal">-- Can’t send thousands of applications to the Board, so restrict to not-for-profits. The problem with coming up with a rule is that we can’t even come up with a good example.<o:p></o:p></p>
<p class="MsoNormal">ACTION ITEM: Call for proposals on how to address closed generics to be discussed in one of the remote PDP ICANN67 sessions. Deadline is 29 February 2020.
<o:p></o:p></p>
</div>
</body>
</html>