<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="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:Arial;
        panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:#0563C1;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:#954F72;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:12.0pt;
        font-family:"Times New Roman";}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:Calibri;
        color:windowtext;}
span.msoIns
        {mso-style-type:export-only;
        mso-style-name:"";
        text-decoration:underline;
        color:teal;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:595.0pt 842.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Dear WG Members,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Please see below the action items and discussion notes captured by staff from the meeting on 27 February. <i>These high-level notes are designed to help WG members navigate through the
content of the call and are not meant to be a substitute for the recording.</i> Please also see the recording on the meetings page at: https://community.icann.org/x/l7HDAw.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Emily<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">----------------------------------------------------------------------------------------------------------------------------------------------------------------------------<o:p></o:p></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">Action Items: <o:p></o:p></span></b></p>
<p><b><span style="font-size:11.0pt;font-family:Arial">ACTION ITEM: If people have comments that they make on the call, it would be helpful if they could also insert a written note in the CC2 document reflecting that comment.<o:p></o:p></span></b></p>
<p><b><span style="font-size:11.0pt;font-family:Arial">ACTION ITEM: All WG members should read through text and suggest edits in the document.
<o:p></o:p></span></b></p>
<p><span style="font-size:11.0pt;font-family:Arial"><o:p> </o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial">Notes:<o:p></o:p></span></b></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">2. SOIs</span></b><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- no updates</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">3. </span></b><b><span style="font-size:11.0pt;font-family:Arial;color:black"> Work Track Updates</span><o:p></o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">WT 1 (Sara Bockey)</span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- meeting tomorrow: will focus on systems, communications, and the AGB. If the WG sends questions back to the WT for clarification, the WT will address the questions on the WT call.</span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">WT2 (Michael Flemming)</span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- Call this week will focus on Closed Generics and any questions about CC2 from the full group.</span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">WT3 (Karen Day)</span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- Currently looking at string related issues. Next week’s meeting will focus on confusing similarity objections, sword tool, and community applications.</span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">WT4 (CLO)</span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- Last week, guest presenter Don Hollander spoke about UA.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">4. </span></b><b><span style="font-size:11.0pt;font-family:Arial;color:black"> Community Comment 2 (CC2) first reading (Working document here: https://docs.google.com/document/d/1iZBCVEAJPBYEDg7jLsMHKkNczR_b6-jH2Wl5eVH-WWM/edit?usp=sharing). </span><o:p></o:p></b></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- Page 1, no questions or concerns</span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- Avri added a comment on pg 2 regarding accreditation, no concerns expressed</span><o:p></o:p></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">EDIT: Spell out all acronyms in the text when used for the first time.</span><o:p></o:p></b></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- Question: are we required to use the term accreditation by the Charter or can we use an alternate term, such as certification? Answer: this is the term used in the Charter, but we may not be required to use it. We may want to keep the words as they were in the original document, but add a note describing alternate terminology or a footnote about use of terminology, in general.</span><o:p></o:p></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">ACTION ITEM: If people have comments that they make on the call, it would be helpful if they could also insert a written note in the CC2 document reflecting that comment.</span><o:p></o:p></b></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- Page 3, comments are largely clarifications, no additional comments</span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- Page 4, no additional comments</span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- Page 5, no additional comments</span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- Suggestion for clarification on sentence just before 1.1.1, add to the text after the word “operators” the words “acting as its own RSP.”
<o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">EDIT: In text just before 1.1.1, add to the text after the word “operators” the words “acting as its own RSP.”
<o:p></o:p></span></b></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- Page 5-6 comment from Greg Shatan -- include both benefits and risks or include neither.</span><o:p></o:p></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">EDIT: Greg Shatan and Jeff Neuman will work together on this paragraph regarding benefits and risks in 1.1.1.</span><o:p></o:p></b></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- Page 6 - 1.1.6 – Comment: this question is unclear. Response: The purpose of the question is to say that we could take some findings and lessons learned from the other group. The question could be revised or removed. </span><o:p></o:p></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">Edit: Remove question 1.1.6.</span></b><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">From the chat: </span><span style="color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">Kristina Rosette (Amazon Registry): </span></b><span style="font-size:11.0pt;font-family:Arial;color:black">As someone who is currently going through the Material Subcontracting Arrangement Assignment process, the lesson I'm learning is that we really need an RSP accreditation/certification program.</span><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- 1.1.8 - Suggestion to change "continuous" to "periodic." Clarification - the purpose of the question is once approved, does there need to be a regular review. <o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">EDIT: In 1.1.8, change the word "continuous" to "periodic” and/or clarify further.</span><span style="color:black"><o:p></o:p></span></b></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">From the chat: </span><span style="color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">Rubens Kuhl: </span></b><span style="font-size:11.0pt;font-family:Arial;color:black">If we are confused in what the question means, the community will be more confused. </span><span style="color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">jeff neuman: </span></b><span style="font-size:11.0pt;font-family:Arial;color:black">Agree with Rubens, let's make sure we note that</span><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- 1.1.10 - Request for clarification of the language with respect to grandfathering. Answer: this refers to the grandfathering of entities that already serve as an RSP. </span><span style="color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">EDIT: Clarify text of 1.1.10 with respect to grandfathering of entities that already serve as an RSP.</span></b><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- 1.2 comment on publicity and outreach - suggestion to add a question on this topic.</span><span style="color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">EDIT: Add question on publicity and outreach in 1.2.</span></b><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- 1.2.1.2 - comment requesting clarification on terminology: least developed, developing, developed, underserved. If we are using UN terms, we should mention that. Otherwise we should define terms.<o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">EDIT: In 1.2.1.2, explain the origin of the terms used (least developed, developing, developed, underserved, etc).</span><span style="color:black"><o:p></o:p></span></b></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- 1.2.2 - request to clarify the language of this question. What other support mechanisms are being referenced? <o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">EDIT: In 1.2.2, clarify language around support mechanisms being referenced.</span><span style="color:black"><o:p></o:p></span></b></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- 1.2.3 - request for clarification on what is meant by success metric. Lack of participation has been cited as an issue. AMGlobal report indicated that even with a perfectly designed program, there may be reasons why prospective applicants may not apply. Question may require additional wordsmithing.<o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">EDIT: In 1.2.3, clarify language about success metrics.
</span><span style="color:black"><o:p></o:p></span></b></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">From the chat: </span><span style="color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">Jorge Cancio (GAC Switzerland): </span></b><span style="font-size:11.0pt;font-family:Arial;color:black">on the applicant support: couln't there be an open 1.2.4. question requesting any other suggestions for improving it?</span><span style="color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">EDIT: Add open-ended question at 1.2.4 requesting any other suggestions for improving applicant support. </span></b><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- 1.3.1 Request to amplify and clarify that changes occured at two different times and the timing of the impact on applicants. Response: different applicants may have had impact at different points in time. Do changes made after the application has been submitted have a particularly negative effect?</span><span style="color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">EDIT: In 1.3.1, clarify language regarding the timing of changes and impact at different points in time.<o:p></o:p></span></b></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">From the chat:</span><span style="color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">Trang Nguyen: </span></b><span style="font-size:11.0pt;font-family:Arial;color:black">Application changes are sometimes needed for applicants to address issues raised against their applications, for example to address GAC early warning.</span><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- 1.4 - There is a comment in the document from Greg Shatan on confusion on cost recovery concept and implementation of this concept (throughout the section)</span><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- 1.4 - Comment in the document from Donna Austin also speaks to this distinction</span><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- Comment: it is difficult to implement a cost recovery model.</span><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- 1.4.2 - Comment in the document regarding surplus. Is it true that there was significant surplus? If inaccurate, should be corrected. </span><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- Suggestion to change or remove the word " considerable."</span><span style="color:black">
</span><span style="font-size:11.0pt;font-family:Arial;color:black">(no objections to this comment)</span><span style="color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">EDIT: In 1.4.2, remove the word “considerable.”
<o:p></o:p></span></b></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- 1.4.2 - Comment in the text -- lobbying may have been included in that third bucket which was a non-legal cost, but should be clarified if there were other contingencies.<o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">EDIT: In 1.4.2, clarify specific costs mentioned in relation to contingency.</span><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- 1.4.3 - Comment in the text - what is a strict vs. non-strict cost recovery fee? Reponse: People were concerned if the cost recovery fees were too low or too high. i.e. No other activities would be included to increase the price over some minimum. Suggestion to remove the work "strict." What are the implication of calculating just based on cost recovery vs. cost recovery along with other considerations, such as to prevent squatting and gaming. </span><span style="color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">EDIT: Reword 1.4.3 to clarify the intention of this question.</span><span style="color:black"><o:p></o:p></span></b></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- 1.6.2 – Question in the document regarding application window- response: it was discussed that 3 months may be an appropriate application window in the first round but that a shorter window could be appropriate in the future.</span><span style="color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">EDIT: Reword or remove 1.6.2. This should be a follow-up to an overarching question, not a repeat of a question on overarching issues.</span><span style="color:black"><o:p></o:p></span></b></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- 1.7.1 – Comment: unclear what we are talking about with respect to first come, first serve in this question. Response: this question is asking a hypothetical question as the issue of first come, first serve has not been settled. This is talking about queuing on applications for review (first come, first evaluated). Suggestion for language: "first submitted for order of processing." </span><span style="color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">EDIT: Clarify text in 1.7.1 to explain the use of the term first come, first serve.</span><span style="color:black"><o:p></o:p></span></b></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">From the chat: </span><span style="color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">Laura Watkins (Nominet): </span></b><span style="font-size:11.0pt;font-family:Arial;color:black">order of receipt</span><span style="color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">Alexander Schubert: </span></b><span style="font-size:11.0pt;font-family:Arial;color:black">Order of receipt leads to benefiting portfolio applicants who submit run of the mill applications!</span><span style="color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">Laura Watkins (Nominet): </span></b><span style="font-size:11.0pt;font-family:Arial;color:black">Alexander - I meant as an alternative phrase to replace "1st come 1st served"</span><span style="color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">jeff neuman: </span></b><span style="font-size:11.0pt;font-family:Arial;color:black">I believe we should eliminate question 1.7.3</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:Arial;color:black">EDIT: Delete question 1.7.3.<o:p></o:p></span></b></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- 1.8 - No objections to suggested edits</span><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">-1.9.2 - No objections to moving this question to Applicant Support section. It can remain as an example in 1.9. <o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">EDIT: Move 1.9.2 to Applicant Support section of the document. In 1.9.2, change the words "in particular" to "for example." </span><span style="color:black"><o:p></o:p></span></b></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- We may need to schedule an additional call to continue going over CC2 questions. <o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- IGF meeting 9:00-12:00 and 14:00-17:00 UTC Wed through Fri this week. This will be a potential conflict for some people. If we hold another meeting this week, we should try to avoid these times.<o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">ACTION ITEM: All WG members should read through text and suggest edits in the document.
</span><span style="color:black"><o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">5. </span><span style="font-size:11.0pt;font-family:Arial;color:black"> ICANN58 Planning</span><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- F2F on first day of ICANN58- 8:30 to 11:45 – The group plans to use the CC2 questions as a basis for the conversation, explain context and clarify the questions. If there is time we can also get some answers and feedback on the questions.
There should be equal distribution of time for each WT.</span><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- Wednesday (Day 5) from 17:00 to 18:30 - additional session, community facing and outreach focused.</span><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- New gTLD Program Review session will take place on Monday 13 March at 13.45.</span><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">From the chat: </span><span style="color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">Jorge Cancio (GAC Switzerland): </span></b><span style="font-size:11.0pt;font-family:Arial;color:black">@jeff/@avri: on ICANN 58 I guess GAC Sec will approach you to invite you (and any interested WG members) to the GAC sessions on new gTLDs</span><span style="color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">avri doria: </span></b><span style="font-size:11.0pt;font-family:Arial;color:black">yes Jorge, think we have received the invitation. </span><span style="color:black"><o:p></o:p></span></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">avri doria: </span></b><span style="font-size:11.0pt;font-family:Arial;color:black">we == Jeff and I. since they are open meetings all members should look at participating.</span><span style="color:black"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- We are trying to get through two readings so we can put out a clean set of questions by ICANN58. We won't start the clock on the public comment period until after ICANN58. Responses will not be due until the end of April.</span><o:p></o:p></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- It is still possible that the discussion at ICANN58 will result in further clarification and revision of the questions. </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p><b><span style="font-size:11.0pt;font-family:Arial;color:black">6. </span></b><b><span style="font-size:11.0pt;font-family:Arial;color:black"> AOB<o:p></o:p></span></b></p>
<p><span style="font-size:11.0pt;font-family:Arial;color:black">- None.</span><o:p></o:p></p>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
</div>
</body>
</html>