<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Anne,<div class=""><br class=""></div><div class="">I can say that because it's a fact, one that you keep trying to say different and have to set the record straight each time. </div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 20 Jun 2018, at 20:08, Aikman-Scalese, Anne <<a href="mailto:AAikman@lrrc.com" class="">AAikman@lrrc.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Rubens,<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">I honestly don’t know how you can say that this was not discussed in the Work Track and was only mentioned by me. You are essentially forcing me to copy and paste the language from the email I had attached into this email - to document something which is very clear from the November 30 call. Below I highlight in bold the relevant language regarding the issues raised and the fact that Kurt Pritz was also vocal about this. (Further, even if Kurt had not chimed in, the fact that only one person raises an issue for discussion and public comment does not mean it can be roundly ignored. )</span></div></div></div></blockquote><div><br class=""></div>By definition of consensus, which doesn't compose unanimity, one person/group position doesn't derail a finding. Multistakeholder group working is not about satisfying each and every member. <br class=""><blockquote type="cite" class=""><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(192, 0, 0);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><b class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(192, 0, 0);" class="">Copied and pasted from my confirming email from the November 30 which was circulated to the Work Track 4 list several times:<o:p class=""></o:p></span></b></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">“Items as to which we, as members of the WT 4 group, had input during the call include:<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: "Times New Roman", serif; text-indent: -0.25in;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><span class="">1.<span style="font-style: normal; font-variant-caps: normal; font-weight: normal; font-stretch: normal; font-size: 7pt; line-height: normal; font-family: "Times New Roman";" class=""> <span class="Apple-converted-space"> </span></span></span></span><b class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">At 15 minutes into the call, discussion of policy regarding<span class="Apple-converted-space"> </span></span></b><b class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(192, 0, 0);" class="">aggregated technical evaluation should not affect order of processing applications</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">, subject to the policy-making recommendations of Work Track ___ “as much as feasible (and consistent the order of processing of applications as recommended by Work Track X”. This concept was supported vocally by Kurt Pritz at 18 minutes into the call and said “Additional technical evaluation should not retard or slow down applications….they should retain their place in queue and should not be penalized in any way from a timing standpoint”. Kurt did not like the “as much as feasible” language either. He said it was too vague as policy language.</span></div></div></div></blockquote><div><br class=""></div>Kurt's comment was about additional registry services; his point is that applications trying to innovate and propose new registry services shouldn't be penalised. It has nothing to do with aggregated technical evaluation. </div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: "Times New Roman", serif; text-indent: -0.25in;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><b class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></b></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: "Times New Roman", serif; text-indent: -0.25in;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><span class="">2.<span style="font-style: normal; font-variant-caps: normal; font-weight: normal; font-stretch: normal; font-size: 7pt; line-height: normal; font-family: "Times New Roman";" class=""> <span class="Apple-converted-space"> </span></span></span></span><b class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">At 27 minutes into the call – Registry Services Slide</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""> (Slide 8?) – Clarify the issue Still to Be Defined – “</span><b class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(192, 0, 0);" class="">whether a new gTLD applicant should be required to disclose new services at the time of application</span></b><b class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">”.</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""> Cheryl said this additional bullet is at 34 min into the call. Cheryl also confirms in this discussion that there are in fact three Straw models still under discussion on this question and that this can be clarified in the slides. (The second bullet point is misleading in that it states that RSEP is “<u class="">the</u><span class="Apple-converted-space"> </span>tool” (emphasis added) for proposing new services. This implies a consensus that RSEP trumps the existing policy that requires disclosure of proposed new services in a new gTLD application.) Nowhere in the slides is there a reference to the discussion re the three Straw models. Thus, this is an issue “Still To Be Defined”. As per Cheryl’s comment, “This is clearly being marked out as work still to be done.” Maxim also points out in chat that RSEP is only for registries that have a Registry Agreement and might not be so for Applicants.</span></div></div></div></blockquote><div><br class=""></div>As I mentioned during the calls, there is a confusion between many of the RSEP acronyms: P for Policy, P for Process, P for Procedure. Neither SubPro policy trumps RSEP policy or vice-versa; they define rules for different audiences (applicants x registries). What was said is the SubPro Registry Services would benefit from following the RSEP Process, and this was actually done in 2012 by ICANN's Org own reckoning, </div><div><br class=""></div><div>Since it's not in our charter to redefine the RSEP Policy, we can't even go there; it would be like discussing Transfer Policy in SubPro. </div><div><br class=""></div><div>Registry Services was the topic of many calls before its final discussion in person in San Juan, so quoting just one of its discussions does not bring the whole truth to the matter. </div><div><br class=""></div><div><br class=""></div><div>Rubens</div><div><br class=""></div></div></body></html>