<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">hi all,<div><br></div><div>this is a two-for-one deal — another SSAC-report thread AND a procedure. SAC060 came out in July, this Label Generation Rules procedure implementation report was just released for comment yesterday. it would be helpful to me to have a discussion about both at the same time, since SSAC seems to be making recommendations that bear, at least in part, on this procedure. i’m happy to split this topic in two if they really AREN’T about the same thing. :-)</div><div><br></div><div>i will be the first to admit that i’m coming from behind on this issue. Chris Wright was kind enough to take me through the baby steps i needed to get a really basic introduction to the IDN Variant topic. we made a short series of videos from that conversation and you can view them on the ISPCP site. Chris did all the heavy lifting, i just listened and learned (a lot). here’s the link for those of you who’d like to get that briefing on the basics.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><a href="http://www.ispcp.info/policy-resources/idns-a-brief-whirlwind-tour/">http://www.ispcp.info/policy-resources/idns-a-brief-whirlwind-tour/</a></div><div><br></div><div>i’ve included the Executive Summary of SAC060 and a link to the newly-released procedure below. here’s my little list of questions:</div><div><br></div><div>- how does the new procedure align with the SSAC findings? </div><div><br></div><div>- are there gaps, overlaps, conflicts between the two?</div><div><br></div><div>- is this even possible? reading both reports, i am struck by how nuanced this conversation is, especially in the “Procedure” document, and wonder if it will be possible to implement something like this.</div><div><br></div><div>- are there things that the GNSO (community or PDP) can do to help at this time? </div><div><br></div><div>mikey</div><div><br></div><div> </div><div><br></div><div><br></div><div><div>here’s a link to SAC060 — <a href="https://www.icann.org/en/groups/ssac/documents/sac-060-en.pdf">https://www.icann.org/en/groups/ssac/documents/sac-060-en.pdf</a></div><div><br></div><div>here’s the Executive Summary from SAC060, including brief summaries of the recommendations (sorry, once again there’s a little trouble with the formatting)</div><div>
<div class="page" title="Page 4">
<div class="section">
<div class="layoutArea">
<div class="column"><p><span style="font-size: 16pt; font-weight: 700;">Executive Summary
</span></p><p><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">At the request of the Board of Directors of the Internet Corporation for Assigned Names
and Numbers (ICANN), the ICANN Security and Stability Advisory Committee (SSAC)
provides comments and advice regarding ICANN’s Report on Examining the User
Experience Implications of Active Variant TLDs.</span><span style="font-size: 6.000000pt; font-family: 'TimesNewRomanPSMT'; vertical-align: 5.000000pt">1
</span></p><p><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">With respect to that Report the SSAC makes the following recommendations:
</span></p><p><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">Recommendation 1: </span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">The root zone must use one and only one set of Label Generation
Rules (LGR).
</span></p><p><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">Recommendation 2: </span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">ICANN must maintain a secure, stable, and objective process to
resolve cases in which some members of the community (e.g., an applicant for a TLD) do
not agree with the result of the LGR calculations.
</span></p><p><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">Recommendation 3: </span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">ICANN should concentrate foremost on the rules for the root zone.
</span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">Recommendation 4: </span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">ICANN should coordinate and encourage adoption of these rules at
</span></p><p><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">the second and higher levels as a starting point by:
</span></p>
<ul>
<li style="font-size: 12.000000pt; font-family: 'Symbol'"><p><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">Updating the IDN Implementation Guidelines and recognizing that a modified
version of these rules or a review or appeals process must be required to address
special cases for the first and second levels;
</span></p>
</li>
<li style="font-size: 12.000000pt; font-family: 'Symbol'"><p><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">Maintaining and publishing a central repository of rules for second- level domain
labels (2LDs) for all Top Level Domains (TLDs), encouraging TLD operators to
publish their LGRs publicly in the repository maintained by ICANN; and
</span></p>
</li>
<li style="font-size: 12.000000pt; font-family: 'Symbol'"><p><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">Conducting specific training and outreach sessions in cooperation with generic
TLD (gTLD) and country code TLD (ccTLD) operators who intend to launch
Internationalized Domain Name (IDN) 2LDs or IDN TLDs, with a focus on
consistency of user experience. The outreach should include among others
registrants, end users, and application developers.
</span></p><p><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">Recommendation 5: </span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">Be very conservative with respect to the code points that are
permitted in root zone labels.
</span></p><p><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">Recommendation 6: </span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">Because the removal of a delegation from the root zone can have
significant non-local impact, new rules added to a LGR must, as far as possible, be
backward compatible so that new versions of the LGR do not produce results that are
incompatible with historical (existent) activations.</span></p><p><span style="font-size: 12pt; font-family: TimesNewRomanPS; font-weight: 700;">Recommendation 7: </span><span style="font-size: 12pt; font-family: TimesNewRomanPSMT;">Should ICANN decide to implement safeguards, it should
distinguish two types of failure modes when a user expects a variant to work, but it is not
implemented: denial of service versus misconnection.</span></p>
<div class="page" title="Page 5">
<div class="layoutArea">
<div class="column"><p><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">Recommendation 8: </span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">A process should be developed to activate variants from allocatable
variants in LGR.
</span></p><p><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">Recommendation 9: </span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">ICANN must ensure that Emergency Back-End Registry Operator
(EBERO) providers support variant TLDs, and that parity exists for variant support in all
relevant systems and functions associated with new TLD components.
</span></p><p><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">Recommendation 10: </span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">The current rights protection regime associated with the
Trademark Clearinghouse (TMCH) process is susceptible to homographic attacks. The
roles of the involved parties, specifically registrars, registries, and TMCH, related to
matching must be made clear.
</span></p><p><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">Recommendation 11: </span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">When registries calculate variant sets for use in validation during
registration, such calculations must be done against all of the implemented LGRs
covering the script in which the label is applied for.
</span></p><p><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">Recommendation 12: </span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">The matching algorithm for TMCH must be improved.
</span></p><p><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">Recommendation 13: </span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">The TMCH must add support for IDN variant TLDs. Particularly
during the TM Claims service, a name registered under a TLD that has allocated variant
TLDs should trigger trademark holder notifications for the registration of the name in all
of its allocated variant TLDs.
</span></p>
</div>
</div>
</div><p><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'"><span style="font-size: 12pt; font-family: TimesNewRomanPS; font-weight: 700;">Recommendation 14: </span><span style="font-size: 12pt;">ICANN should ensure that the number of strings that are activated
is as small as possible.</span> </span></p>
</li>
</ul>
</div>
</div>
</div>
</div><div><br></div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><br></div><br><div>
<title>ICANN News Alert</title>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<meta content="icann, internet, internet corporation for assigned names and numbers, iana" name="keywords">
<meta content="Internet Corporation for Assigned Names and Numbers" name="description">
<style type="text/css">
table.convey {
font-family: Arial, Helvetica, sans-serif;
border: 1px solid #d8d8d8;
border-collapse: collapse;
}
table.convey td {
border: 1px solid #d8d8d8;
padding: .5em;
}
table.convey .dark {
background-color: #dedede;
}
table.convey .light {
background-color: #f8f8f8;
}
</style>
<div style="background-color: rgb(255, 255, 255); font-family: arial; font-size: small;">
<div style="width: 758px; padding: 10px; border: 1px solid rgb(204, 204, 204); margin-left: auto; margin-right: auto;">
<div style="width: 738px; margin-left: auto; margin-right: auto;"><a href="http://www.icann.org/"><img alt="ICANN" src="http://www.icann.org/images/gradlogo_bow.jpg" style="border: 0px none; width: 94px; height: 94px; float: left; margin-top: 0px; margin-right: 10px;"></a>
<h2>News Alert</h2><p style="margin: 0px 0px 10px; font-family: arial; font-size: small;"><a href="http://www.icann.org/en/news/announcements/announcement-2-03mar14-en.htm">http://www.icann.org/en/news/announcements/announcement-2-03mar14-en.htm</a></p>
<hr style="margin: 20px 0px 0px;">
<h2 style="clear: left; margin-bottom: 0px;">IDN Variant TLDs – LGR Procedure Implementation – Maximal Starting Repertoire Version 1 is Now Open for Public Comment</h2><p style="margin: 15px 0px 0px;">3 March 2014</p><div> <br class="webkit-block-placeholder"></div>
<table class="convey">
<tbody><tr>
<td class="light"><strong>Forum Announcement:</strong></td>
<td>Comment Period Opens on</td>
<td class="light"><strong>Date:</strong></td>
<td>3 March 2014</td>
</tr>
<tr>
<td class="light"><strong>Categories/Tags:</strong></td>
<td colspan="3"><ul>
<li>Internationalized Domain Names</li>
<li>IDN</li>
<li>IDN Variant TLD</li>
<li>new gTLD</li>
</ul> </td>
</tr>
<tr>
<td class="light"><strong>Purpose (Brief):</strong></td>
<td colspan="3"><p>As first deliverable under the "<a href="http://www.icann.org/en/resources/idn/variant-tlds/lgr-procedure-20mar13-en.pdf">Procedure to Develop and Maintain Label Generation Rules for the Root Zone With Respect to IDN Labels</a>" [PDF, 772 KB] (the Procedure), ICANN is releasing for public comment version 1 of the Maximal Starting Repertoire (MSR-1). The contents of MSR-1 and the detailed rationale behind its development are described in "<a href="http://www.icann.org/en/resources/idn/variant-tlds/msr-overview-rationale-27feb14-en.pdf">Maximal Starting Repertoire – MSR-1-Overview and Rationale</a>" [PDF, 393 KB].</p>
</td>
</tr>
<tr>
<td class="light"><strong>Public Comment Box Link:</strong></td>
<td colspan="3"><a href="http://www.icann.org/en/news/public-comment/msr-03mar14-en.htm">http://www.icann.org/en/news/public-comment/msr-03mar14-en.htm</a></td>
</tr>
</tbody></table>
</div>
</div>
<br><br><table border="0" cellspacing="0" cellpadding="0" width="100%">
<tbody><tr>
<td width="100%" bgcolor="#ffffff"><p style="font-family:arial,helvetica,sans-serif; font-size:12px; line-height:20px; color:#5e5e5e; margin: 0px 0px 5px;">This message was sent to <a href="mailto:mike@haven2.com">mike@haven2.com</a> from:</p><p style="font-family:arial,helvetica,sans-serif; font-size:12px; line-height:20px; color:#5e5e5e; margin: 0px 0px 5px;">ICANN | 12025 Waterfront Drive
Suite 300 | Los Angeles, CA 90094-2536</p>
</td>
<td width="2%" bgcolor="#ffffff"><p style="font-family:arial,helvetica,sans-serif; font-size:9px; line-height:13px; color:#5e5e5e;">Email Marketing by
<a href="http://www.icontact.com/a.pl/144186" target="_blank"><img src="http://app.icontact.com/images/icontact_tryFree.gif" alt="iContact - Try It Free!" border="0"></a></p>
</td>
</tr>
</tbody></table>
<table border="0" cellpadding="0" cellspacing="0">
<tbody><tr>
<td bgcolor="#FFFFFF">
<a href="http://app.icontact.com/icp/mmail-mprofile.pl?r=14994551&l=6333&s=WBF0&m=931939&c=165637" style="font-family: Arial, Helvetica, san-serif; font-size: 12px; line-height: 20px; color: #115880; font-weight: bold; text-decoration: none;">
Manage Your Subscription
</a>
</td>
</tr>
</tbody></table>
<img src="http://click.icptrack.com/icp/track.php?msgid=931939&act=WBF0&r=14994551&c=165637" width="1" height="1">
</div>
</div></blockquote></div><br><div apple-content-edited="true">
<br class="Apple-interchange-newline"><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; ">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>
</div>
<br></div></body></html>