<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 name=Title content=""><meta name=Keywords content=""><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:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:12.0pt;
font-family:Calibri;}
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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Calibri;}
span.EmailStyle18
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle26
{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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:46729819;
mso-list-type:hybrid;
mso-list-template-ids:112485654 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1
{mso-list-id:243993655;
mso-list-type:hybrid;
mso-list-template-ids:719346058 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l2
{mso-list-id:546259865;
mso-list-type:hybrid;
mso-list-template-ids:168080638 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l3
{mso-list-id:1347826283;
mso-list-type:hybrid;
mso-list-template-ids:-351401384 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l3:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l3:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l3:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l3:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l3:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l3:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l3:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l3:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l3:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l4
{mso-list-id:1712264305;
mso-list-type:hybrid;
mso-list-template-ids:-1257197584 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l4:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l4:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l4:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l4:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l4:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l4:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l4:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l4:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l4:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l5
{mso-list-id:1828327649;
mso-list-type:hybrid;
mso-list-template-ids:2103998634 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l5:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l5:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l5:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l5:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l5:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l5:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l5:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l5:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l5:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l6
{mso-list-id:2077704385;
mso-list-type:hybrid;
mso-list-template-ids:-308614452 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l6:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l6:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l6:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l6:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l6:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l6:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l6:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l6:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l6:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l7
{mso-list-id:2115242374;
mso-list-type:hybrid;
mso-list-template-ids:-165931230 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l7:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l7:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l7:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l7:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l7:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l7:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l7:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l7:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l7:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style></head><body bgcolor=white lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt'>Dear WG Members,<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt'> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt'>Please see below the action items and discussion notes captured by staff from the meeting on 19 December. <i>These high-level notes are designed to help PDP WG members navigate through the content of the call and are not meant as a substitute for the transcript or recording</i>. The MP3, transcript, and chat room notes are provided separately and are posted on the wiki at: <a href="https://community.icann.org/display/NGSPP/1.+WG+Meetings"><span style='color:#0B4CB4'>https://community.icann.org/display/NGSPP/1.+WG+Meetings</span></a>.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt'> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt'>Best regards,<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt'>Julie<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt'> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt'>Julie Hedlund, Policy Director<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:10.5pt'> <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Actions/Discussion Notes: New gTLD Subsequent Procedures PDP WG Meeting, 19 December</span></b><span style='font-size:10.5pt'><o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'> </span></b><span style='font-size:10.5pt'><o:p></o:p></span></p><p class=MsoNormal><b><i><span style='font-size:10.5pt'>1. Work Track Brief Updates<o:p></o:p></span></i></b></p><p class=MsoNormal><span style='font-size:10.5pt'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt'>Work Track 1 – Sara Bockey and Christa Taylor</span></u><span style='font-size:10.5pt'>: Met on 12 December. Discussed applicant support, application process and cost, and application submission period and queuing. No further meetings through the end of December.<o:p></o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt'>Work Track 2 -- Phil Buckingham:</span></u><span style='font-size:10.5pt'> We are considering changing the time of the call in the New Year - still every other Thursday . 2 Our first call in the new year willl be on the COI / LOC issues . Any applicant with prior experiences/ problems re: Round 1 on this Q50 - feedback would be much appreciated - 3 WT2 received a really excellent email from Kurt Pritz re categories / registry agreement . Your feedback / responses on this would be much appreciated <o:p></o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt'>Work Track 3 -- Karen Day and Robin Gross</span></u><span style='font-size:10.5pt'>: Meeting tomorrow. Ensure that WT members review the materials for tomorrow's discussion on Legal Rights Objections is on the wiki at : https://community.icann.org/display/NGSPP/4.4.3+Objections<o:p></o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt'>Work Track 4 -- Ruben's Kuhl</span></u><span style='font-size:10.5pt'>: Discussions from Hyderabad. (Work Track) Consensus all ongoing on doing technical capability after the process. Also discussing financial. We have a Work Track call on 22 December, but facing competition from Christmas and Santa Claus, so any objection to canceling? [No objections were received and the call cancellation notice was send out.]<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'><o:p> </o:p></span></p><p class=MsoNormal><b><i><span style='font-size:10.5pt'>2. CC1 Review, cont. (Please see attached as XLS and PDF; iterative versions always captured here - <a href="https://community.icann.org/x/3B6OAw.)">https://community.icann.org/x/3B6OAw.)</a><o:p></o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:10.5pt'><o:p> </o:p></span></i></b></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Actions:<i> </i></span></b><span style='font-size:10.5pt'>Come back with principles related to the responses to CC1.<b><i><o:p></o:p></i></b></span></p><p class=MsoNormal><b><i><span style='font-size:10.5pt'><o:p> </o:p></span></i></b></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Discussion Notes:<o:p></o:p></span></b></p><p class=MsoNormal><span style='font-size:10.5pt'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Subject 4: Predictability should be maintained or enhanced without sacrificing flexibility. In the event changes must be introduced into the new gTLD Application process, the disruptive effect to all parties should be minimized.<o:p></o:p></span></b></p><p class=MsoNormal><span style='font-size:10.5pt'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt'>4.a. Was the round of 2012 sufficiently predictable given external factors, while balancing the need to be flexible?</span></u><span style='font-size:10.5pt'> [Reading from the tool, responses 4aR1-3.]<u><o:p></o:p></u></span></p><p class=MsoNormal><span style='font-size:10.5pt'><o:p> </o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l4 level1 lfo9'><![if !supportLists]><span style='font-size:10.5pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:10.5pt'>There were changes introduced only after we saw what the applications were like. Will still have some corrections to make along the way.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l4 level1 lfo9'><![if !supportLists]><span style='font-size:10.5pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:10.5pt'>Should have learned a lot, but there are a couple of things we can flag. GAC advice was a big factor in slowing down two thirds of the applications.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l4 level1 lfo9'><![if !supportLists]><span style='font-size:10.5pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:10.5pt'>A lot of these issues will have been sorted out since we are working on them. The comment on GAC advice is interesting and we'll need to talk about it in Work Track 3 -- how to deal with GAC advice after the round has started?<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l4 level1 lfo9'><![if !supportLists]><span style='font-size:10.5pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:10.5pt'>We need to look at patterns of the kind of advice we got in the processes we build so that (GAC advice) doesn't come out of the blue. The advice forced us to look at how the TLDs would be used and the semantics.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l4 level1 lfo9'><![if !supportLists]><span style='font-size:10.5pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:10.5pt'>To think about: Let's say in Work Track 2 we finalize the geographic names issue and then the process starts, but someone submits an application and a government (GAC or anyone else) has a problem with that? Do we have to let it go? Is there a policy against opening up issues? What should be the response from ICANN?<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l4 level1 lfo9'><![if !supportLists]><span style='font-size:10.5pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:10.5pt'>I don't see how in the Bylaws we can say that GAC can't give advice.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l4 level1 lfo9'><![if !supportLists]><span style='font-size:10.5pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:10.5pt'>A conversation in the RySG group, such as two characters at the second level, if there is GAC advice it should be based in international law.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l4 level1 lfo9'><![if !supportLists]><span style='font-size:10.5pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:10.5pt'>What is the international law? This is a good question and one that Work Track 2 will need to look at. To bring it up a level -- what factors should the ICANN community look at as to whether it merits changing a process midway through.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l4 level1 lfo9'><![if !supportLists]><span style='font-size:10.5pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:10.5pt'>The GAC seems to always find a loop hole to object later. Isn't the Accountability Work Stream 2 working on the role of governments in providing advice? No, Accountability is not addressing this.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l4 level1 lfo9'><![if !supportLists]><span style='font-size:10.5pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:10.5pt'>The GAC is working with us, so presumably we will try to cover these issues, but I don't think there is anything we can do if a government wants to raise an objection.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l4 level1 lfo9'><![if !supportLists]><span style='font-size:10.5pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:10.5pt'>But would ICANN be justified in saying that you originally said it was okay, we can apply this to the next window?<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l4 level1 lfo9'><![if !supportLists]><span style='font-size:10.5pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:10.5pt'>Seems natural that in the first round that there were a lot of issues that couldn't be predicted. There had been GAC principles on new gTLDs back as far as 2007. This is a process that should be ongoing.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l4 level1 lfo9'><![if !supportLists]><span style='font-size:10.5pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:10.5pt'>GAC is much more active.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l4 level1 lfo9'><![if !supportLists]><span style='font-size:10.5pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:10.5pt'>Think about it in terms of SSAC bringing an objection. Based on the implications (same with the GAC) it will be a judgment call.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt'>4.c. What are the impacts on applicants, users, and related parties from a process that lacks predictability</span></u><span style='font-size:10.5pt'>? [Reading from the tool, responses 4cR1-3.]<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'><o:p> </o:p></span></p><ul style='margin-top:0in' type=disc><li class=MsoNormal style='mso-list:l2 level1 lfo12'><span style='font-size:10.5pt'>Asking for agreement on: Kurt Pritz: Combining two of my earlier comments: (1) a risk to DNS stability or clear violation of some public interest; (2) a change based on information that was unknowable when the process was developed.<o:p></o:p></span></li></ul><ul style='margin-top:0in' type=disc><li class=MsoNormal style='mso-list:l3 level1 lfo11'><span style='font-size:10.5pt'>This could be a starting basis for a framework. Ask for volunteers for a drafting team, or the Chairs or staff? Get the points down.<o:p></o:p></span></li></ul><p class=MsoNormal><span style='font-size:10.5pt'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt'>4.b. Do the changes implemented as a result of the establishment of CCWGs and the adoption of the principles and processes from the Policy and Implementation Working Group suffice to maintain predictability of the application process while at the same time provide for the needed flexibilty to address changes of circumstances.</span></u><span style='font-size:10.5pt'> [Reading from the tool, responses 4b.R1-3.]<o:p></o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt'>4.d. Any other issues related to this overarching subject? </span></u><span style='font-size:10.5pt'> [Reading from the tool, responses 4dR1-3.]<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'>If this group got to the point later had a consensus on how an implementation review team could work we could do that later.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'>From the chat:<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Rubens Kuhl</span></b><u><span style='font-size:10.5pt'>:</span></u><span style='font-size:10.5pt'> A truism: a longer process will be less predictable than a shorter process. So if we make it shorter, it gets more predictable. <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Klaus Stoll</span></b><span style='font-size:10.5pt'>: We did learning by doing the first time round and should learn valuable lessons and implement them. Maybe we should create a list of lessons learned.<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Kurt Pritz</span></b><span style='font-size:10.5pt'>: I think the question for this group might be, "Is there consensus that the application / evaluation / delegation procedure should be more predictable than the last round and aspire to be predictable and consistent with the Guidebook?"<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Jorge Cancio (GAC Switzerland):</span></b><span style='font-size:10.5pt'> GAC Advice was (from our point of viwe, of course) something that was also due to the fact that we were engaging in the very first exercise of this kind. And some of the issues raised by the GAC after the start of the round had already been reaised before, but perhaps there had been not a full agreement on how to factor it in.<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Kurt Pritz: @ Rubens</span></b><span style='font-size:10.5pt'>: The policy could say that there is a pretty high bar for amending the process after launch, i.e., a risk to DNS stability or clear violation of some public interest<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Robin Gross:</span></b><span style='font-size:10.5pt'> What is ICANN required to do with the GAC advice, especially if it comes late?<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Rubens Kuhl</span></b><span style='font-size:10.5pt'>: Kurt, I would like to see the same thresholds existing today in the RA... like the board can issue emergency security policies, so they could intervene in the application process in case of risk to DNS stability. But for public interest issues, there would be either (a) something community-wide as a consensus policy or (b) full voted agreement between applicants and ICANN consenst. <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Donna Austin, Neustar: </span></b><span style='font-size:10.5pt'>@Robin - i think that's an important question - what does late mean and what's the consequence.<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Robin Gross:</span></b><span style='font-size:10.5pt'> Especially when GAC was involved in the working groups that created the GNSO policy, and subsequently wants to provide possibly different advice?<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Donna Austin, Neustar:</span></b><span style='font-size:10.5pt'> @Kavouss - i was using it as an example and providing views of an SG other than the GAC.<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Christa Taylor: </span></b><span style='font-size:10.5pt'>Depends on the substance of the change..<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Kurt Pritz:</span></b><u><span style='font-size:10.5pt'> </span></u><span style='font-size:10.5pt'>Two thoughts that are not thought through: (1) If the GAC provides advice, the Board should be required to deal with it on a timely basis, with the timing to be spelt out in the procedure. (2) Maybe post-launch comments can only be based on new information that was not available before the launch <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Klaus Stoll</span></b><span style='font-size:10.5pt'>: We should not lose the lessons learned and make a list of Changes and issues,and lessons learned.<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Cheryl Langdon-Orr (CLO):</span></b><span style='font-size:10.5pt'> the merit is probably The question and the Test <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Robin Gross</span></b><u><span style='font-size:10.5pt'>:</span></u><span style='font-size:10.5pt'> We should look at what ICANN's bylaws require for GNSO policy development. And specifically the process by which the board is to resolve differences between GNSO developed policy and GAC advice.<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Annebeth Lange, ccNSO</span></b><span style='font-size:10.5pt'>: I think it is in place to remind of the GAC Principles on new gTLDs: ICANN should avoid country, territory or place names, and country, territory or regional language or people descriptions, unless in agreement with the relevant governments or public authorities. <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Mathieu Weill</span></b><span style='font-size:10.5pt'>: No, Accountability WS2 is not addressing this<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Donna Austin, Neustar</span></b><span style='font-size:10.5pt'>: @Annebeth, those principles existed prior to the 2012 round and were taken into account at that time. On what basis do you propose that agreements made for the 2012 round be re-opened?<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Tom Dale (ACIG GAC Secretariat):</span></b><span style='font-size:10.5pt'> WS2 sub-group on transparency is looking at ICANN-government relations, but not the role of the GAC.<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Annebeth Lange, ccNSO</span></b><span style='font-size:10.5pt'>: What I mean, Donna, is that in 2012 round country & territory names based on ISO 3166 were taken out - for this round. If they are taken in again in the next round, these principles should be taken into account, so that a support/non-objection should be necessary to make it a gTLD<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Rubens Kuhl</span></b><span style='font-size:10.5pt'>: I think the question is whether advice that amounts to the deferrence required to deal with GAC Consensus Advice can occur after date X. GAC can always issue advice, governments can issue them, I can issue advice by writing a letter to the board... <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Annebeth Lange, ccNSO</span></b><span style='font-size:10.5pt'>: In my view it does not make sense that a capitol needs support/non-objection, but a country/territory should not need it. This includes 3-letter codes on the ISO-3166 list representing countries. <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Cheryl Langdon-Orr (CLO):</span></b><span style='font-size:10.5pt'> we should also recognise that the GAC now is, more proactivly engaged now <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Donna Austin, Neustar</span></b><span style='font-size:10.5pt'>: thanks Annebeth<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Martin Sutton:</span></b><span style='font-size:10.5pt'> It appears all are in agreement that there was lack of predictability in the last round. Based on this, should we simply list the specific issues that have been raised, check where there has been a change since, and whether the changes have improved predictability? Where no change has occurred against a specific issue, review and consider if a change is needed. As we channel specifics through the WTs, we should also use this as a checkpoint to see if we have sufficiently improved predictability.<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Cheryl Langdon-Orr (CLO):</span></b><span style='font-size:10.5pt'> the merits are again the issue yes as Alan said. <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Mathieu Weill:</span></b><span style='font-size:10.5pt'> Agree with Alan, ICANN Bylaws are clear on the importance of security, stability and public interest, predictability will never prevail over these factors<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Annebeth Lange, ccNSO:</span></b><span style='font-size:10.5pt'> And public interest also includes politics. On the other hand, the more uncertainties we can get rid of before launching, the better. That will, in my view, give us a faster next round than last time.<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Steve Coates</span></b><span style='font-size:10.5pt'>: To Jeff's point, this is why launch times need to be more predictable. <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Christa Taylor</span></b><span style='font-size:10.5pt'>: perhaps categories <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Kurt Pritz</span></b><span style='font-size:10.5pt'>: Combining two of my earlier comments: (1) a risk to DNS stability or clear violation of some public interest; (2) a change based on information that was unknowable when the process was developed<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Donna Austin, Neustar</span></b><span style='font-size:10.5pt'>: Agree with Kurt, particularly on 2). <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Cheryl Langdon-Orr (CLO):</span></b><span style='font-size:10.5pt'> yup<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Martin Sutton:</span></b><span style='font-size:10.5pt'> @Kurt - we could test your formula on the changes that were made during the last application phase.<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>avri doria</span></b><span style='font-size:10.5pt'>: all of the contentful comments seem to end up in the notes.<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Kavouss Arasteh 2:</span></b><span style='font-size:10.5pt'> Cheryl, what is the meaning of yup in standard communication standard?<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Vanda Scartezini</span></b><u><span style='font-size:10.5pt'>:</span></u><span style='font-size:10.5pt'> Agree with Kurt too<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Christa Taylor</span></b><span style='font-size:10.5pt'>: +1<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Jorge Cancio (GAC Switzerland):</span></b><span style='font-size:10.5pt'> We have to be aware that the role of GAC early warning and GAC consensus advice was part of the AGB of 2012 and therefore part of the rules of the game<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Vanda Scartezini:</span></b><span style='font-size:10.5pt'> we can put our green to give you a better view<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Cheryl Langdon-Orr (CLO<u>):</u></span></b><span style='font-size:10.5pt'> I agree with KuRT<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Phil Buckingham</span></b><span style='font-size:10.5pt'>: +1 to Kurt 's comment <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Kristina Rosette (Amazon Registry): </span></b><span style='font-size:10.5pt'>@Kurt: Is there a reason you didn't include security in #1 or was it presumed? @Kurt: To be clear, the "security" in "security and stability"?<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Jorge Cancio (GAC Switzerland):</span></b><span style='font-size:10.5pt'> what is being asked?<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Kurt Pritz:</span></b><span style='font-size:10.5pt'> @ Kristine: DNS security, stability, resiliency<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Cheryl Langdon-Orr (CLO):</span></b><span style='font-size:10.5pt'> I assumed presumed<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Jorge Cancio (GAC Switzerland):</span></b><span style='font-size:10.5pt'> Politics, and policy are difficult to be reduced to a formula<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Phil Buckingham</span></b><span style='font-size:10.5pt'>: + 1 CLO presumed and overriding <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Jorge Cancio (GAC Switzerland): </span></b><span style='font-size:10.5pt'>+ 1 Mathieu on staff/Board changes<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Annebeth Lange, ccNSO</span></b><span style='font-size:10.5pt'>: +1<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Jorge Cancio (GAC Switzerland</span></b><u><span style='font-size:10.5pt'>)</span></u><span style='font-size:10.5pt'>: I feel the GAC answer on 4 b) also answers some points made before on the GAC role<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Mathieu Weill:</span></b><span style='font-size:10.5pt'> Would this test apply to changes introduced by staff into the process? It is my impression that there is an area for larger improvements in predictability <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Subject 5: Community engagement in new gTLD application processes<o:p></o:p></span></b></p><p class=MsoNormal><span style='font-size:10.5pt'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt'>5.a Are there circumstances in which the application window should be frozen while unforeseen policy issues are considered and resolved? If so, should there be a threshold or standard that must be reach before considering freezing an application window?</span></u><span style='font-size:10.5pt'> [Reading from the tool, responses 5aR1-3.]<o:p></o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt'>5.b. If the Board is faced with questions that cannot be addressed by the policy recommendations they were sent, must the Board bring the issue back to the GNSO and PDP process (e.g. the GNSO Expedited PDP or GNSO Guidance Process)?</span></u><span style='font-size:10.5pt'> [Reading from the tool, responses 5b.R1-3.]<o:p></o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt'>5.c. Should a standard be established to discriminate between issues that must be resolved during an open application window and those that can be postponed until a subsequent application window</span></u><span style='font-size:10.5pt'>? [Reading from the tool, responses 5cR1-3.]<o:p></o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt'>5d. Any other issues related to this overarching subject?</span></u><span style='font-size:10.5pt'> [Reading from the tool, responses 5dR1-3.]<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'>From the chat:<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Donna Austin, Neustar</span></b><span style='font-size:10.5pt'>: Who would make the determination on what is 'severe'<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>avri doria</span></b><span style='font-size:10.5pt'>: and the Board deciding it was so? without the EC objecting.<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Donna Austin, Neustar</span></b><span style='font-size:10.5pt'>: Some could say we experienced that in 2012 with Names Collision.<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>avri doria</span></b><span style='font-size:10.5pt'>: True, Donna. Except no EC and no coming back to the community.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Subject 6. Limiting applications in total and/or per entity during an application window.<o:p></o:p></span></b></p><p class=MsoNormal><span style='font-size:10.5pt'> <o:p></o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt'>6a. Should a limit for the total number of applications for an application window and/or from a single entity be established? If so, what should be the limiting factor (e.g. total applicaitons, total number of strings, etc.) and why?</span></u><span style='font-size:10.5pt'> <o:p></o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt'>6b. If a limit for the total number of applications for an application window and/or from a single entity is established, how would the appropriate amount of applications be set to establish this limit?</span></u><span style='font-size:10.5pt'> <o:p></o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt'>6.c: If a limit for the total number of applications for an application window and/or from a single entity is established, what mechanism(s) could be used to enforce limit(s)?<o:p></o:p></span></u></p><p class=MsoNormal><u><span style='font-size:10.5pt'>6.d: How would a limit on the total number of applications for an application window and/or from a single entity impact fees?<o:p></o:p></span></u></p><p class=MsoNormal><u><span style='font-size:10.5pt'>6.e: Would limits to the total number of applications for an application window and/or from a single entity be considered anti-competitive? Please explain</span></u><span style='font-size:10.5pt'>.<o:p></o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt'>6.f: Do limits to the total number of applications for an application window and/or from a single entity favor “insiders?<o:p></o:p></span></u></p><p class=MsoNormal><u><span style='font-size:10.5pt'>6.g: Any other issues related to this overarching subject:<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:10.5pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'>[Reading from the tool, responses to each question.]<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'>Seems that people speaking and commenting in the chat are not in favor of limits, but to make sure the process is not dominated by insiders.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'>From the chat:<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Vanda Scartezini</span></b><span style='font-size:10.5pt'>: i beleive limit is not realistic at all. I am for free competition and oepen opportunity to all who wants to apply<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Annebeth Lange, ccNSO</span></b><span style='font-size:10.5pt'>: But is it fair, Vanda, that those companies with a lot of money can affort to apply for many, but "newcomers" have problems doing that? Wasn't one of the reasons behind opening up that there should be fair competition?<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Vanda Scartezini</span></b><span style='font-size:10.5pt'>: this time, less money had a problem to apply more for lack of timely information than really lack of money at least in our region<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Kurt Pritz</span></b><span style='font-size:10.5pt'>: @ Annebeth: I think interfering with markets in a way to abet less financial applicants is not workable; I think your concern is best address by the Applicant Support question<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Rubens Kuhl</span></b><span style='font-size:10.5pt'>: I think the competitive angle is per-string, so those who apply for many are diluting their strength (low or high) among many strings and making it actually easier for the focused applicants. .club and .cloud registries are examples of that from the 2012-round. <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Jorge Cancio (GAC Switzerland):</span></b><span style='font-size:10.5pt'> The key is again to have an effective outreach, that interested stakeholders have a fair say v-a-v strings that may interest them, that community based applications work, and that the applicant support program really works<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Annebeth Lange, ccNSO</span></b><span style='font-size:10.5pt'>: I think this is especially important for new markets, like Africa<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Cheryl Langdon-Orr (CLO):</span></b><span style='font-size:10.5pt'> agree Jorge <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Annebeth Lange, ccNSO</span></b><span style='font-size:10.5pt'>: Agree, Jorge<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Cheryl Langdon-Orr (CLO):</span></b><span style='font-size:10.5pt'> yes Annebeth <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Vanda Scartezini:</span></b><span style='font-size:10.5pt'> agree with Rubens. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'><o:p> </o:p></span></p><p class=MsoNormal><b><i><span style='font-size:10.5pt'>3. Any other business: <o:p></o:p></span></i></b></p><p class=MsoNormal><span style='font-size:10.5pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'>Look for a poll on the 0300 UTC Monday meeting falling on Sunday evening. Substitute for 0300 UTC Tuesday (fall on Monday evening).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'><o:p> </o:p></span></p></div></body></html>