<html xmlns:v="urn:schemas-microsoft-com:vml" 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)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
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><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Correct, the WT4 call is scheduled to start at 20:00 UTC in 45 minutes.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Best,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Terri<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> gnso-newgtld-wg-wt4-bounces@icann.org [mailto:gnso-newgtld-wg-wt4-bounces@icann.org] <b>On Behalf Of </b>Martin Sutton<br><b>Sent:</b> Thursday, June 8, 2017 2:12 PM<br><b>To:</b> Aikman-Scalese, Anne <AAikman@lrrc.com><br><b>Cc:</b> gnso-newgtld-wg-wt4@icann.org<br><b>Subject:</b> Re: [Gnso-newgtld-wg-wt4] WT4 Call Agenda<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Oh good, I’m early :-) <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks Donna.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p><div><div><div><div><p class=MsoNormal><b><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black'>Martin Sutton</span></b><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black'>Executive Director<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black'>Brand Registry Group<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black'><a href="mailto:martin@brandregistrygroup.org">martin@brandregistrygroup.org</a><o:p></o:p></span></p></div></div></div></div><p class=MsoNormal><o:p> </o:p></p><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On 8 Jun 2017, at 11:25, Aikman-Scalese, Anne <<a href="mailto:AAikman@lrrc.com">AAikman@lrrc.com</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Technical Advice Needed</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p></div><div style='margin-left:.5in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>1.</span><span style='font-size:7.0pt;color:#1F497D'> <span class=apple-converted-space> </span></span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>How to deal with new applications that may present high risk strings in an orderly fashion that does not subject applicants and others to investment of time and money that is wasted. (This should include advice as to how to coordinate evaluation of special names with IETF.)</span><o:p></o:p></p></div><div style='margin-left:.5in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>2.</span><span style='font-size:7.0pt;color:#1F497D'> <span class=apple-converted-space> </span></span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Updated technical advice on DITL as the most valuable measure of name collision issues (as per “off the cuff” advice from JAS recently received.) Are you saying that we use DITL, but don’t use any apd information? Or are you saying use apd information, but apply controlled interruption to those names? If so, does controlled interruption answer the concerns of brands where brand names are purchased during Sunrise and then subject to controlled interruption procedures?</span><o:p></o:p></p></div><div style='margin-left:.5in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>3.</span><span style='font-size:7.0pt;color:#1F497D'> <span class=apple-converted-space> </span></span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Updated technical advice on the period of controlled interruption – can and should it be shortened? (RySG comments mention Interisle and talk about seeking additional technical advice. RySG notes that Advisors should not have any conflicts of interest.)</span><o:p></o:p></p></div><div style='margin-left:.5in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>4.</span><span style='font-size:7.0pt;color:#1F497D'> <span class=apple-converted-space> </span></span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Technical advice on individual label review.</span><o:p></o:p></p></div><div style='margin-left:.5in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>5.</span><span style='font-size:7.0pt;color:#1F497D'> <span class=apple-converted-space> </span></span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Technical advice on the overall restructuring of the current version of the Name Collision Framework to the extent we believe changes should be considered. (Please note the existing Name Collision Framework does not contain a process for identifying high risk strings). The existing Name Collision Framework should be submitted to technical experts along with any recommendations and questions we may have for the purpose of getting expert advice on the best methods for updating the Framework for the next round.</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Put more bluntly, if we do not obtain more updated expert technical advice on name collision issues and how to handle them going forward, we are the ones “guessing”.</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p></div><div><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 align=left style='border-collapse:collapse;margin-left:6.75pt;margin-right:6.75pt'><tr><td width=336 valign=top style='width:3.5in;padding:0in 5.4pt 0in 5.4pt'><div><p class=MsoNormal style='mso-element:frame;mso-element-frame-hspace:8.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly'><b><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:#AF272F'>Anne E. Aikman-Scalese</span></b><o:p></o:p></p></div></td></tr><tr><td width=336 valign=top style='width:3.5in;padding:0in 5.4pt 0in 5.4pt'><div><p class=MsoNormal style='mso-element:frame;mso-element-frame-hspace:8.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly'><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:#323232'>Of Counsel</span><o:p></o:p></p></div></td></tr><tr><td width=336 valign=top style='width:3.5in;padding:0in 5.4pt 0in 5.4pt'><div><p class=MsoNormal style='mso-element:frame;mso-element-frame-hspace:8.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly'><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:#323232'>520.629.4428 office</span><o:p></o:p></p></div></td></tr><tr><td width=336 valign=top style='width:3.5in;padding:0in 5.4pt 0in 5.4pt'></td></tr><tr><td width=336 valign=top style='width:3.5in;padding:0in 5.4pt 0in 5.4pt'><div><p class=MsoNormal style='mso-element:frame;mso-element-frame-hspace:8.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly'><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:#323232'>520.879.4725 fax</span><o:p></o:p></p></div></td></tr><tr><td width=336 valign=top style='width:3.5in;padding:0in 5.4pt 0in 5.4pt'><div><p class=MsoNormal style='mso-element:frame;mso-element-frame-hspace:8.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly'><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:#1F497D'><a href="mailto:AAikman@lrrc.com" target="_new" title="Email User"><span style='color:#323232'>AAikman@lrrc.com</span></a></span><o:p></o:p></p></div></td></tr><tr><td width=336 valign=top style='width:3.5in;padding:0in 5.4pt 0in 5.4pt'><div><p class=MsoNormal style='mso-element:frame;mso-element-frame-hspace:8.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly'><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:#323232'>_____________________________</span><o:p></o:p></p></div></td></tr><tr><td width=336 valign=top style='width:3.5in;padding:0in 5.4pt 0in 5.4pt'><div><p class=MsoNormal style='mso-element:frame;mso-element-frame-hspace:8.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly'><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:#1F497D'><image003.png></span><o:p></o:p></p></div></td></tr><tr><td width=336 valign=top style='width:3.5in;padding:0in 5.4pt 0in 5.4pt'><div><p class=MsoNormal style='mso-element:frame;mso-element-frame-hspace:8.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly'><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:#323232'>Lewis Roca Rothgerber Christie LLP</span><o:p></o:p></p></div></td></tr><tr><td width=336 valign=top style='width:3.5in;padding:0in 5.4pt 0in 5.4pt'><div><p class=MsoNormal style='mso-element:frame;mso-element-frame-hspace:8.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly'><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:#323232'>One South Church Avenue, Suite 700</span><o:p></o:p></p></div></td></tr><tr><td width=336 valign=top style='width:3.5in;padding:0in 5.4pt 0in 5.4pt'><div><p class=MsoNormal style='mso-element:frame;mso-element-frame-hspace:8.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly'><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:#323232'>Tucson, Arizona 85701-1611</span><o:p></o:p></p></div></td></tr><tr><td width=336 valign=top style='width:3.5in;padding:0in 5.4pt 0in 5.4pt'><div><p class=MsoNormal style='mso-element:frame;mso-element-frame-hspace:8.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly'><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:#1F497D'><a href="http://lrrc.com/" target="_new" title="Lewis Roca Rothgerber Christie Webpage"><span style='color:#323232'>lrrc.com</span></a></span><o:p></o:p></p></div></td></tr><tr><td width=336 valign=top style='width:3.5in;padding:0in 5.4pt 0in 5.4pt'></td></tr></table></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><br clear=all></span><o:p></o:p></p></div><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif'>From:</span></b><span class=apple-converted-space><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif'> </span></span><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif'>Rubens Kuhl [<a href="mailto:rubensk@nic.br"><span style='color:purple'>mailto:rubensk@nic.br</span></a>]<span class=apple-converted-space> </span><br><b>Sent:</b><span class=apple-converted-space> </span>Wednesday, June 07, 2017 5:53 PM<br><b>To:</b><span class=apple-converted-space> </span>Aikman-Scalese, Anne<br><b>Cc:</b><span class=apple-converted-space> </span><a href="mailto:gnso-newgtld-wg-wt4@icann.org"><span style='color:purple'>gnso-newgtld-wg-wt4@icann.org</span></a><br><b>Subject:</b><span class=apple-converted-space> </span>Re: [Gnso-newgtld-wg-wt4] WT4 Call Agenda</span><o:p></o:p></p></div></div></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><p class=MsoNormal>Hi Anne. <o:p></o:p></p></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><p class=MsoNormal>Responses inline. <o:p></o:p></p></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Rubens et al,</span><o:p></o:p></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Looks as though my attachment of a zip file with apd reports caused some problems in delivery. Resending without apd reports attached.</span><o:p></o:p></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Anne</span><o:p></o:p></p></div></div></div></blockquote><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><p class=MsoNormal>Just another anecdotal evidence of the size of APD files, I believe... to add another, some DNS zones we provisioned for back-end registry customers were larger than most of the DNS zones we ever provisioned. <o:p></o:p></p></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><p class=MsoNormal><br><br><br><o:p></o:p></p></div><div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Rubens,</span><o:p></o:p></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Regarding Items 4 and 5 of the agenda for Thursday’s call, I note that SSAC Advice as to name collisions is still in the “open” phase at the ICANN Board. The advice includes SSAC 062 - Phase 2 – “Evaluate and Consider” and SSAC 90 – Phase 1 “Request Understood” by the Board. Open advice from SSAC to the Board should not be lumped in with other CC2 comments. After all, this is the Security and Stability Advisory Committee to ICANN. <span class=apple-converted-space> </span></span><o:p></o:p></p></div></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><p class=MsoNormal>SAC 90 is more of the "Conflicting TLD Allocations" theme than name collisions per se. One possible conflict that a possible name collision could cause is that if two organisations decide differently how to handle a TLD that is said to be prone to collisions, that would be in the realm of the SAC 90 SSAC advice. <o:p></o:p></p></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><p class=MsoNormal>Regarding SAC 62, it has two recommendations, one regarding high risk strings and the other regarding trial delegations; the final Name Collision Framework ended up not having trial delegations, so this part was fully accepted by the board. The one regarding strings still remains to be seen, since there is no closure on that yet... so that might be why it's listed as open. <o:p></o:p></p></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><p class=MsoNormal>And since the 2012-round high-risk strings are not in scope for this PDP, we don't have to address directly that part of the advice, although being recognisant of the possibility of high-risk strings. <o:p></o:p></p></div></div><div><div><p class=MsoNormal><br><br><br><o:p></o:p></p></div><div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>There are also a number of comments to CC2 which express frustration at the process followed in the 2012 round given that application fees were paid and “unicorn” high collision risks were not identified until much later. <span class=apple-converted-space> </span></span><o:p></o:p></p></div></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><p class=MsoNormal>Considering that SSAC advice, Internet-Drafts, CircleID articles and Root Server information public information already mentioned .home and .corp, I don't agree with them being identified until much later. On the other hand, .mail, or more properly dotless mail, fits the description, IMHO. <o:p></o:p></p></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><p class=MsoNormal><br><br><br><o:p></o:p></p></div><div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>To put it mildly, this was not an orderly process. Thus, I would say that this issue of “high risk” strings needs to be given priority by our Track 4 Team since it is a “threshold” issue for any applicant. If we don’t have individual string review, how can these high risk strings be identified in new applications? Did we learn anything from the 2012 round? (Put another way, this WG cannot afford to take the “ostrich” approach to the “unicorn” high risk TLD strings.)</span><o:p></o:p></p></div></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><p class=MsoNormal>I think we did learn a few things. Stay tuned for the call. ;-)<o:p></o:p></p></div></div><div><p class=MsoNormal><br><br><br><o:p></o:p></p></div><div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Although Jeff indicates the 2012 high risk TLDs (.home, .corp, .mail) are subject to “separate processes”, I believe that given the open SSAC Advice to the Board, these high risk “unicorn” applications (whether old or new) will likely all be considered by the Board on the same basis once a policy for the next round is determined based on policy recommendations provided by the GNSO and the Advisory Committees. </span><o:p></o:p></p></div></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><p class=MsoNormal>That's a guess, and while that might become true or not, since it's not in our charter we can only considerer subsequent procedures for this specific topic. If the Board later uses a paradigm the PDP suggests, it's up to them. The only case we know for sure that will happen is closed generics. <o:p></o:p></p></div></div><div><div><p class=MsoNormal><br><br><br><o:p></o:p></p></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> Separately, both Interisle and JAS Advisors indicated that DITL (Day in the Life) statistics were the most valuable measures for assessing name collision risk. I think both also endorsed the 90 day Controlled Interruption period. </span> <o:p></o:p></p></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><p class=MsoNormal>I'm not sure Interisle mentioned the duration of the CI period, it would be interesting to add their views on that as well if they are published somewhere. <o:p></o:p></p></div></div><div><div><p class=MsoNormal><br><br><br><o:p></o:p></p></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Lastly, I note that the International Trademark Association has filed comments related to the fact that due to the Alternate Path to Delegation (“apd”) lists generated by the 2012 round, a number of brand names were blocked and were not subject to a second Sunrise when released. This is a significant issue for brand owners which also needs to be addressed as a policy matter. (See attached apd reports by TLD as of 12 November 2013.)</span><o:p></o:p></p></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><p class=MsoNormal>The APD lists were a shortcut to be used while the framework was being developed, but I'm sure no one would suggest it to be done again. For instance, after ICANN approved the framework, registries were forbidden to use APD lists and would instead obliged to use wildcard controlled interruption. So while this was a source of anguish and sorrow for both registries and trademark owners, it's now just a bad memory, like Digital Archery, TAS bugs etc. <o:p></o:p></p></div></div><div><div><p class=MsoNormal><br><br><br><o:p></o:p></p></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>I am hopeful that leadership for Sub Pro and for this Work Track will recognize that expert advice on these questions is needed. Accordingly, we should be soliciting estimates from qualified technical advisors and seeking funds in relation to obtaining advice on these highly technical questions. </span><o:p></o:p></p></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><p class=MsoNormal>I'm not sure we need advice beyond what we already got from SSAC, JAS, INTA and RySG, considering our scope. I believe we could require such advice if we were to deal with .home, .corp, and .mail, but that is not in our plate... besides that, what reasons do you see to need to such an advice during the PDP ? There might be, so if you could elaborate (either on the list or during the call)... <o:p></o:p></p></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><p class=MsoNormal>Best,<o:p></o:p></p></div></div><div><div><p class=MsoNormal>Rubens<o:p></o:p></p></div></div><div><div><p class=MsoNormal> <o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=3 width="100%" align=center></div><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial",sans-serif;color:gray'><br>This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.<span class=apple-converted-space> </span><br></span><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>_______________________________________________<br>Gnso-newgtld-wg-wt4 mailing list<br></span><a href="mailto:Gnso-newgtld-wg-wt4@icann.org"><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif;color:purple'>Gnso-newgtld-wg-wt4@icann.org</span></a><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'><br></span><a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt4"><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif;color:purple'>https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt4</span></a><o:p></o:p></p></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>