<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family: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:DengXian;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:"\@DengXian";
        panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Calibri",sans-serif;}
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.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:11.0pt;
        font-family:"Calibri",sans-serif;}
span.EmailStyle18
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;
        font-family:"Calibri",sans-serif;}
@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:97722420;
        mso-list-template-ids:795111540;}
@list l0:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level2
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level5
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level8
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1
        {mso-list-id:1273708620;
        mso-list-template-ids:-889553916;}
@list l1:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level2
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:"Courier New";
        mso-bidi-font-family:"Times New Roman";}
@list l1:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l1:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l1:level5
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l1:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l1:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l1:level8
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l1:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black">Dear Sunrise Sub Team members,</span></p>
<p style="margin:0in;margin-bottom:.0001pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black">As announced,  this thread is being opened for final mailing list discussions related to
<b>Sunrise Agreed Charter Question 3</b>, including <b>Individual Proposals #10 and #11</b>.
</span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black">We ask that you review the
<b>Summary Table</b> <b>(as of 16 April 2019) </b>and provide any additional input you may have to the “<b>tentative answers & preliminary recommendations</b>” in relation to the Agreed Charter Question, and
<b>draft answers </b>to the following questions regarding the individual proposals:
</span></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="color:black">a. Should the Sub Team recommend that the full WG consider including this Individual Proposal in the Initial Report for the solicitation of public comment?<o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="color:black">b. In light of the Individual Proposal, are any modifications to the current “tentative answers & preliminary recommendations” needed?
<o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="color:black">c. Should any additional Sub Team recommendations be made in relation to the agreed Sunrise charter question?<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black">Unless the Sub Team Co-Chairs determine otherwise, this discussion thread will remain open until
<b>23:59 UTC on 15 May 2019</b>. Comments/input provided past the closing date or outside this discussion thread will not be taken into account when compiling the final Sub Team member input.</span></p>
<p style="margin:0in;margin-bottom:.0001pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="color:black;background:yellow">Summary Table</span><span style="color:black"> (Pages 15-20)</span></b></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black">The draft answers, preliminary recommendations, and links to the relevant individual proposals are in the latest Summary Table (as of 16 April 2019):</span></p>
<p style="margin:0in;margin-bottom:.0001pt"><a href="https://community.icann.org/download/attachments/102138618/%5BSunrise%20Summary%20Table%5D%20%2816%20April%202019%29.pdf?version=1&modificationDate=1555515624235&api=v2"><span style="color:#1155CC">https://community.icann.org/download/attachments/102138618/%5BSunrise
 Summary Table%5D %2816 April 2019%29.pdf?version=1&modificationDate=1555515624235&api=v2</span></a><span style="color:black">.
</span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black"> </span></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="color:black;background:yellow">Agreed Sunrise Charter Question 3(a)-(b)</span><span style="color:black"> (Pages 15-17)</span></b></p>
<p style="margin:0in;margin-bottom:.0001pt"><i><span style="color:black">(a) Should Registry Operators be required to create a mechanism that allows trademark owners to challenge the determination that a second level name is a Premium Name or Reserved Name?</span></i></p>
<p style="margin:0in;margin-bottom:.0001pt"><i><span style="color:black">(b) Additionally, should Registry Operators be required to create a release mechanism in the event that a Premium Name or Reserved Name is challenged successfully, so that the trademark
 owner can register that name during the Sunrise Period?</span></i></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><u><span style="color:black">Proposed Answer</span></u><span style="color:black">:</span></b><span style="color:black"> ICANN Org should establish a uniform mechanism that allows trademark owners to challenge a
 determination by a Registry Operator that a second level name is a "Premium Name" or a "Reserved Name" during the Sunrise Period. ICANN Org should require Registry Operators to create a release mechanism in the event that a Premium Name or Reserved Name is
 challenged successfully, so that the trademark owner can register that name during the Sunrise Period.</span></p>
<p style="margin:0in;margin-bottom:.0001pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><u><span style="color:black">Draft Recommendation</span></u><span style="color:black">:
</span></b><span style="color:black">The Sub Team recommends that ICANN Org establish a uniform mechanism to allow trademark owners to challenge a Registry Operator’s determination that a second level name is a “Premium Name” or “Reserved Name”. The Sub Team
 recommends, further, that the following Implementation Guidance guide the Implementation Review Team (IRT), which will be created to implement approved policy recommendations from this PDP:</span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo3;vertical-align:baseline">
<span style="font-size:11.0pt">The mechanism could be a component of an enhanced Sunrise Dispute Resolution Procedure (SDRP), where the challenger brings the issue to the Registry Operator first via a formal process within the registry, with the possibility
 of an appeal to a neutral third party if the initial direct registry interaction does not result in the desired outcome for the challenger.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo3;vertical-align:baseline">
<span style="font-size:11.0pt">If the challenger ultimately prevails, the Registry Operator would be required to change the designation of the domain name at issue such that it is no longer identified as a "Premium Name" or a "Reserved Name" and becomes available
 for registration by the challenger.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo3;vertical-align:baseline">
<span style="font-size:11.0pt">As part of the proposed challenge mechanism, a defense, or ground for denying the challenge, should be that the registry must continue designating a certain name as "reserved" to comply with other ICANN policies or applicable
 law or due to other reasonable justifications.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo3;vertical-align:baseline">
<span style="font-size:11.0pt">The IRT should consider building carve-outs/caveats into the suggested challenge mechanism. The challenge mechanism is not an absolute/automatic challenge; it should include the legitimate grounds for the Premium Name designation
 or Reserved Name status.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo3;vertical-align:baseline">
<span style="font-size:11.0pt">To avoid overcomplication, the IRT should consider restricting the challenge mechanism to unique non-dictionary trademarks that are recorded in the Trademark Clearinghouse, and/or consider placing a numeric limit on the number
 of Reserved Names challenged by a trademark owner.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo3;vertical-align:baseline">
<span style="font-size:11.0pt">The IRT should consider modeling the challenge mechanism after the Passive Holding doctrine developed in Uniform Domain Name Dispute Resolution Policy (UDRP) jurisprudence, with clear definitions to prevent potential misinterpretation
 by the panelists.<o:p></o:p></span></li></ul>
<p style="margin:0in;margin-bottom:.0001pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="color:black;background:yellow">Agreed Sunrise Charter Question 3(c)</span><span style="color:black"> (Pages 16-17)</span></b></p>
<p style="margin:0in;margin-bottom:.0001pt"><i><span style="color:black">(c) What concerns might be raised by either or both of these requirements?
</span></i></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><u><span style="color:black">Proposed Answer:</span></u><span style="color:black">
</span></b><span style="color:black">One Sub Team member noted that Registry Operators may be concerned that any change to the Reserved list will affect their ability to run the required real-time platforms. This may subsequently result in unpredictable consequences,
 including: violating applicable law/ICANN policies, raising security and stability concerns, undermining Spec 11, rendering the reserved GEO TLDs ineffective. The Sub Team member also noted that Registry Operators may have concerns about gaming by trademark
 owners and the number of challenges brought by multiple trademark owners that registries have difficulty handling.</span></p>
<p style="margin:0in;margin-bottom:.0001pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black">Another Sub Team member noted the concern that the suggested challenge mechanism may be of little/infrequent use due to the subjectivity, complications, and expense, as well as potentially
 fewer domain name applications in the next round of TLDs.</span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><u><span style="color:black">Draft Recommendation:
</span></u></b><span style="color:black">The Sub Team recommends that the RPM Working Group refer the following question to the SubPro Working Group: would it be feasible to recommend that the names recorded in the TMCH either cannot be designated premium or
 can be designated premium at a certain price ceiling as an exception to ICANN’s position about pricing?</span></p>
<p style="margin:0in;margin-bottom:.0001pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="color:black;background:yellow">Individual Proposals</span><span style="color:black">
</span></b></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black">Please reference the following pages in the Summary Table for the draft answers to the three questions regarding the individual proposals. Links to the individual proposals are also included
 below. </span></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="color:black">Proposal #10 (Pages 17-18)</span></b><span style="color:black">:</span><a href="https://community.icann.org/download/attachments/102146375/Proposal%2310.pdf?api=v2"><span style="color:black">
</span><span style="color:#1155CC">https://community.icann.org/download/attachments/102146375/Proposal%2310.pdf?api=v2</span></a></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="color:black">Proposal #11 (Pages 21-22):</span></b><a href="https://community.icann.org/download/attachments/102146375/Proposal%2311.pdf?api=v2"><span style="color:black">
</span><span style="color:#1155CC">https://community.icann.org/download/attachments/102146375/Proposal%2311.pdf?api=v2</span></a></p>
<p style="margin:0in;margin-bottom:.0001pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black">Best Regards,</span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black">Mary, Julie, Ariel</span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
</body>
</html>