<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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
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:656687613;
mso-list-type:hybrid;
mso-list-template-ids:-1224051776 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;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoPlainText">Dear NCAP Discussion Group, <o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> Attached please find: <o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoPlainText" style="mso-list:l0 level1 lfo1">The notes and action items from the 24 April meeting<o:p></o:p></li><li class="MsoPlainText" style="mso-list:l0 level1 lfo1">Jay’s presentation on the overview of the project including definition of name collisions<o:p></o:p></li><li class="MsoPlainText" style="mso-list:l0 level1 lfo1">The latest full project proposal<o:p></o:p></li></ul>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> Please also find the study 1 proposal in google doc format. As Jim mentioned on the call, DG members are encouraged to provide feedback on 1) the study goals, 2) anything that needs to be clarified, and 3) gaps in deliverables and
tasks. <o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><a href="https://docs.google.com/document/d/15f1Kh2vuY0yF9SelocGrPOguYPXDeFYZ0lTqx3fU_gI/edit?usp=sharing">https://docs.google.com/document/d/15f1Kh2vuY0yF9SelocGrPOguYPXDeFYZ0lTqx3fU_gI/edit?usp=sharing</a><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> Please review this document ahead of tomorrow’s call and provide your input.
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Best<o:p></o:p></p>
<p class="MsoPlainText">Steve<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">On 4/24/19, 6:49 PM, "NCAP-Discuss on behalf of Rubens Kuhl" <ncap-discuss-bounces@icann.org on behalf of rubensk@nic.br> wrote:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> I'll do a bit of copy-paste here to the comfort of NCAP WP participants, but first I need to stress that since this is an initial report, it doesn't reflect any consensus, and it also don't carry minority views that could be totally
opposed for what's in it. <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> Identified issues:<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <span lang="ZH-CN" style="font-family:DengXian">●</span> APD lists included a number of desirable terms and trademarks to be only available after the launch cycle of the TLD, interacting badly with launch programs, marketing initiatives
and RPMs. <o:p></o:p></p>
<p class="MsoPlainText"> <span lang="ZH-CN" style="font-family:DengXian">●</span> The after-the-fact nature of establishing the framework severely impacted time-to-market of approved TLDs.<o:p></o:p></p>
<p class="MsoPlainText"> <span lang="ZH-CN" style="font-family:DengXian">●</span> Late start of controlled interruption added to more delays.
<o:p></o:p></p>
<p class="MsoPlainText"> <span lang="ZH-CN" style="font-family:DengXian">●</span> The Work Track has not reached an agreement on TLDs with a higher than usual risk level (.home, .corp and .mail).<o:p></o:p></p>
<p class="MsoPlainText"> <span lang="ZH-CN" style="font-family:DengXian">●</span> Some TLDs contradicted the framework by having both wildcard controlled interruption and delegated domain names.<o:p></o:p></p>
<p class="MsoPlainText"> <span lang="ZH-CN" style="font-family:DengXian">●</span> Risks were overplayed by some actors and downplayed by others, making it harder for the ICANN organization to choose an accepted risk level.
<o:p></o:p></p>
<p class="MsoPlainText"> <span lang="ZH-CN" style="font-family:DengXian">●</span> Some side effects of controlled interruption for specific SLDs required disabling controlled interruption for the whole TLD.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> Overall tone<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <span lang="ZH-CN" style="font-family:DengXian">●</span> Expanding 2012 Framework with categorization of low, aggravated, and high risk, on elaborating
<span lang="ZH-CN" style="font-family:DengXian">“</span>do not apply<span lang="ZH-CN" style="font-family:DengXian">”</span> and
<span lang="ZH-CN" style="font-family:DengXian">“</span>exercise care<span lang="ZH-CN" style="font-family:DengXian">”</span> lists;
<o:p></o:p></p>
<p class="MsoPlainText"> <span lang="ZH-CN" style="font-family:DengXian">●</span> Keeping readiness requirement for life-threatening collisions; and
<o:p></o:p></p>
<p class="MsoPlainText"> <span lang="ZH-CN" style="font-family:DengXian">●</span> For low-risk strings, on starting controlled interruption as soon as possible and delegate execution to ICANN.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> Recommendations:<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> 2.7.8.c.1: Include a mechanism to evaluate the risk of name collisions in the TLD evaluation process as well during the transition to delegation phase.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> 2.7.8.c.3: Efforts should be undertaken to create a “Do Not Apply” list of TLD strings that pose a substantial name collision risk whereby application for such strings would not be allowed to be submitted.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> 2.7.8.c.4: In addition, a second list of TLDs should be created (if possible) of strings that may not pose as high of a name collision risk as the “Do Not Apply” list, but for which there would be a strong presumption that a specific
mitigation framework would be required.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> 2.7.8.c.5: Allow every application, other than those on the “do not apply” list, to file a name collision mitigation framework with their application.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> 2.7.8.c.6: During the evaluation period, a test should be developed to evaluate the name collision risk for every applied-for string, putting them into 3 baskets: high risk, aggravated risk, and low risk. Provide clear guidance to
applicants in advance for what constitutes high risk, aggravated risk, and low risk.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> 2.7.8.c.7: High risk strings would not be allowed to proceed and would be eligible for some form of a refund.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> 2.7.8.c.8: Aggravated risk strings would require a non-standard mitigation framework to move forward in the process; the proposed framework would be evaluated by an RSTEP panel.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> 2.7.8.c.9: Low risk strings would start controlled interruption as soon as such finding is reached, recommended to be done by ICANN org for a minimum period of 90 days (but likely more considering the typical timeline for evaluation,
contracting and delegation).<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> 2.7.8.c.10: If controlled interruption (CI) for a specific label is found to cause disruption, ICANN org could decide to disable CI for that label while the disruption is fixed, provided that the minimum CI period still applied to
that string.<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> ======<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> There were also some questions that tried to get more community input on specific topics. The comments received from the community can be seen at<o:p></o:p></p>
<p class="MsoPlainText"> https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_spreadsheets_d_133WbhWYB4M4kT6DqSfiCR2-2Dij7jxNkLj5EWZL-2DNA95M_edit-23gid-3D1737964707&d=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=O16Ko7V_SvDE5jZHxFQsUEzduEwmIp0AxPl2Gzy-KTc&m=Bs5FzZTLCjEHwvQhyFJ0-3JWKPvSBjxZ7mh1tSerd04&s=1nsT0_nt779MREg1PbdNHORxa1wqMZ5IZxhkoD8JqIU&e=<o:p></o:p></p>
<p class="MsoPlainText"> (sheet 2.7.8 Name Collisions)<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> The WG has yet to go thru the recommendations and comments to produce a final report, which may come this calendar year.
<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> From the WG discussions and comments, I noticed that there are those that believe the 3-tier classification (High/Aggravated/Low Risk) might not be achievable, and also some doubt where a "Do Not Apply" list could be made or not.
Whether this will cause merging of High and Aggravated but allowing a mitigation framework to be filed even for the High Risk strings, subject to the string plus mitigation being approved or denied, and changing the "Do Not Apply" list to "Apply at your own
risk", is yet to be seen. <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> There are also those not comfortable with other themes, but I don't see a direct link to the NCAP WP work. But the content is all there so anyone can take their own judgement on that.
<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> Rubens<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"> _______________________________________________<o:p></o:p></p>
<p class="MsoPlainText"> NCAP-Discuss mailing list<o:p></o:p></p>
<p class="MsoPlainText"> NCAP-Discuss@icann.org<o:p></o:p></p>
<p class="MsoPlainText"> https://mm.icann.org/mailman/listinfo/ncap-discuss<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
</div>
</body>
</html>