<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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-AU" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I find these kinds of vague assertions troubling. Not only do they cause drama with little path to resolution, they also increase the barrier to participation
in working groups because new entrants are expected to know (intuitively? through osmosis?) these issues in order to discuss them.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">So if you take nothing else from my email, I ask that everyone please at least clarify predictions of doom with actual evidence matching the prediction.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The advice linked in the email is generic advice regarding LGRs. I’m not clear how a malign TMCH label can cause harm in a registry with label generation rules
that enforce homogeneity and prevent cross language/script homographic attacks. Is this advice for Registries that aren’t using effective LGRs? Is this advice for the TMCH being sued because said malicious registrant can’t actually use their SMD effectively
(because registries prevent the label)? Is this a legal risk or a risk to infrastructure or DNS consumers? Are we going to address legal risks on this mailing list?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">What can’t we trust the TMCH for? What is the risk? <- again is it legal, infrastructure, other..?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I’m concerned that TLDs may not be meeting their SLAs. Is there a mechanism we can use to exchange examples and suggestions without turning it into a finger
pointing exercise? <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">My understanding of EBERO activation is that it is primarily a mechanism to protect registrants and DNS consumers. Are they at risk?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Are contracts a Security, Stability or Resiliency issue? (I realise this post was from another mailing list, where contracts may be of relevance)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Kal<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><br>
<br>
</span><span style="font-size:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> gnso-ssr-bounces@icann.org [mailto:gnso-ssr-bounces@icann.org]
<b>On Behalf Of </b>Mike O'Connor<br>
<b>Sent:</b> Friday, 21 February 2014 3:51 AM<br>
<b>To:</b> GNSO SSR List<br>
<b>Subject:</b> [Gnso-ssr] Broken TMCH?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">hi all,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">here’s a snip from the chat transcript of the recent CEO/Community-Leaders webinar. i’m curious about the “broken TMCH” comment that Patrik made. Patrik (or others) would you like to expand on that? <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">i’m curious whether that would be an SSR topic that one/all of the GNSO constituencies might want to request a review by the SSAC.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">here’s the chat transcript:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoPlainText" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:108.0pt;text-indent:-108.0pt">
Patrik Fältström: I would like to remind everyone that regarding the issues SSAC have seen on broken TMCH has not been acted on, at all. And I urge people to not rely on TMCH yet. In any process.<o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:108.0pt;text-indent:-108.0pt">
Patrik Fältström: <a href="https://www.myicann.org/board-advice#advice-to-board_f=tmch&advice-to-board_d=false">
https://www.myicann.org/board-advice#advice-to-board_f=tmch&advice-to-board_d=false</a><o:p></o:p></p>
<p class="MsoPlainText" style="margin-bottom:12.0pt">Michele Neylon: Security + stability issues should be core<o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:108.0pt;text-indent:-108.0pt">
Michele Neylon: I thought they were core to ICANN’s mission<o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:108.0pt;text-indent:-108.0pt">
Patrik Fältström: I also want to point out that we do have new gTLDs that are so broken technically that I think various clauses that say EBERO could be invoked has matched.<o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:108.0pt;text-indent:-108.0pt">
Michele Neylon: Patrik - already?<o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:108.0pt;text-indent:-108.0pt">
Michele Neylon: wow<o:p></o:p></p>
<p class="MsoPlainText" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:108.0pt;text-indent:-108.0pt">
Patrik Fältström: Part from me supporting the issue that Michele mentioned, that the fact people in some legislations cannot sign contracts with ICANN due to US-centric clauses is something that MUST be addresses, or else our enemies might be
able to say that "the internal ICANN change processes does not work"<o:p></o:p></p>
<div>
<p class="MsoNormal"><br>
<span style="font-size:9.0pt;font-family:"Helvetica","sans-serif";color:black">PHONE: 651-647-6109, FAX: 866-280-2356, WEB:
<a href="http://www.haven2.com">www.haven2.com</a>, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)</span>
<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>