<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 9/29/2017 5:28 PM, Tex Texin wrote:<br>
</div>
<blockquote type="cite"
cite="mid:000701d33983$17202d00$45608700$@xencraft.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (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:"MS Mincho";
        panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:SimSun;
        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:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"\@MS Mincho";
        panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
        {font-family:"Yu Gothic";
        panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
        {font-family:"\@Yu Gothic";
        panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
        {font-family:"\@SimSun";
        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:"Times New Roman","serif";
        color:black;}
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
        {mso-style-priority:99;
        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";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";
        color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:black;}
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";
        color:black;}
span.EmailStyle19
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle20
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.EmailStyle22
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";
        color:black;}
.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;}
/* List Definitions */
@list l0
        {mso-list-id:620501298;
        mso-list-template-ids:-1282253108;}
@list l0:level1
        {mso-level-start-at:2;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1
        {mso-list-id:711812304;
        mso-list-template-ids:-1448213124;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
--></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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks
Mark and Asmus.<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
agree about the distinction of script mixing within a label.
The guide should clarify this.<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">Also
support Asmus clarification regarding ASCII vs all of Latin.
<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">For
the attention to mixing digits within a label, I agree
although I would need to review if I can easily know which
digits are widely used vs of historical interest. I don’t
believe that being a bit broad in linkification acceptance
is a problem. The domain registry (and perhaps servers)
should be more restrictive to not allow domains that could
represent spoofing. (I know there are problems with reliance
on registries). Being too restrictive in linkification could
hurt users that need to enter a legitimate URL and can’t.</span></p>
</div>
</blockquote>
<br>
Digits come in sets that are specified as such in the Unicode
Standard (although implicitly: the members of such sets have a
property "decimal digit" and Unicode follows the convention of
encoding these in complete sets from 0-9). Therefore, not linkifying
something that contains a mixture of these sets can be implemented
deterministically (although regex syntax leads to particularly grim
expressions for specifying this constraint, it can be done).<br>
<br>
Realistically, only the modern set of about 30 scripts is of
practical importance, so a scheme that does not track the addition
of future historic alphabets in Unicode would be adequate....<br>
<br>
Where native digits are (largely) historic holdovers, we wouldn't
need them at all, but linkification isn't a good place to filter
those. <br>
<br>
Some reluctance on automatic conversions of "risky" URLs would be a
benefit; it's along the same line as not linkifying something not
under the author's control: the risk for mischief is just too great.<br>
<br>
Forum software that I have been a user of tended to implement three
restrictions that are not related to new TLDs or IDN TLDs:<br>
<br>
1) limit file names by extension (e.g. if the link entered was
supposed to be for an image, do not allow it to link to something
that doesn't have a common image file extension).<br>
<br>
2) disallow any link with a "?" in it - rationale: it's not a static
link and who knows what will be served later (including risky stuff)<br>
<br>
3) require <a class="moz-txt-link-freetext" href="http://">http://</a>, etc., even in text spans that are marked as
being URLs or in link attributes.<br>
<br>
In some cases these restrictions were deliberate decisions by forum
operators - part of reigning in certain kinds of forum spam. <br>
<br>
I feel we need to be cognizant of the needs for limiting the risk
profile of certain operations - in particular where the result then
winds up online to an open audience (as opposed to just sharing
something in a private message). <br>
<br>
The alternative for an operator is to simply blacklist specific TLDs
and domains (and most of those will be any IDNs that are not local
to the operator...). <br>
<br>
<br>
<blockquote type="cite"
cite="mid:000701d33983$17202d00$45608700$@xencraft.com">
<div class="WordSection1">
<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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">And
it seems we need to clarify our implied intent for the
guidance about the “implied intent of user’s entry”. </span><span
style="font-size:11.0pt;font-family:Wingdings;color:#1F497D">J</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
(I couldn’t resist any longer.)</span></p>
</div>
</blockquote>
:)<br>
<blockquote type="cite"
cite="mid:000701d33983$17202d00$45608700$@xencraft.com">
<div class="WordSection1">
<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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Tex<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"><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>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
<a class="moz-txt-link-abbreviated" href="mailto:ua-discuss-bounces@icann.org">ua-discuss-bounces@icann.org</a>
[<a class="moz-txt-link-freetext" href="mailto:ua-discuss-bounces@icann.org">mailto:ua-discuss-bounces@icann.org</a>] <b>On Behalf Of </b>Mark
Svancarek via UA-discuss<br>
<b>Sent:</b> Friday, September 29, 2017 5:04 PM<br>
<b>To:</b> Asmus Freytag; <a class="moz-txt-link-abbreviated" href="mailto:ua-discuss@icann.org">ua-discuss@icann.org</a><br>
<b>Subject:</b> Re: [UA-discuss] UASG010 - Quick Guide
to Linkification<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext">Hmm,
I don’t recall approving that principle (hopefully it was
added while I was out on leave, and not just because I
carelessly failed to notice it was being added).<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext">I
mention that because it seems the opposite of what we could
recommend i.e. we SHOULD allow use of Highly Restrictive and
continue to discourage Moderately Restrictive. Do we need
to revisit this? Sorry if I am just confused.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext">Note
that, as Asmus points out, our concern is about
script-mixing within a label, not use of different scripts
in different labels. Tex’s examples are all the latter, and
should linkify cleanly by UA-ready SW.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext">/marksv<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"
moz-do-not-send="true"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext"><o:p> </o:p></span></a></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";color:windowtext">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext">
<a href="mailto:ua-discuss-bounces@icann.org"
moz-do-not-send="true">ua-discuss-bounces@icann.org</a>
[<a href="mailto:ua-discuss-bounces@icann.org"
moz-do-not-send="true">mailto:ua-discuss-bounces@icann.org</a>]
<b>On Behalf Of </b>Asmus Freytag<br>
<b>Sent:</b> Friday, September 29, 2017 2:40 PM<br>
<b>To:</b> <a href="mailto:ua-discuss@icann.org"
moz-do-not-send="true">ua-discuss@icann.org</a><br>
<b>Subject:</b> Re: [UA-discuss] UASG010 - Quick Guide
to Linkification<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 9/29/2017 2:26 PM, Tex Texin wrote:<span
style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Hi,</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Some
questions:</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="mso-list:l1 level1 lfo1"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Do
I understand correctly, that the recommendation to not
linkify highly restrictive strings means that <a
href="mailto:tex@%E6%99%AE%E9%81%8D%E6%8E%A5%E5%8F%97-%E6%B5%8B%E8%AF%95.%E4%B8%96%E7%95%8C"
moz-do-not-send="true"><span style="color:windowtext">tex@</span><span
style="font-size:12.0pt;font-family:"Yu
Gothic","sans-serif"" lang="JA">普遍接受</span><span
style="font-size:12.0pt">-</span><span
style="font-size:12.0pt;font-family:SimSun;color:windowtext"
lang="JA">测试</span><span style="font-size:12.0pt">.</span><span
style="font-size:12.0pt;font-family:"Yu
Gothic","sans-serif"" lang="JA">世界</span></a></span>
<span
style="font-family:"Calibri","sans-serif"">would
not become a link? Or <a href="http://"
moz-do-not-send="true">http://</a></span> <span
style="font-family:"MS Mincho"" lang="JA">普遍接受</span><span
style="font-family:"Calibri","sans-serif"">-</span><span
style="font-family:SimSun" lang="JA">测试</span><span
style="font-family:"Calibri","sans-serif"">.</span><span
style="font-family:"MS Mincho"" lang="JA">世界</span><span
style="font-family:"Calibri","sans-serif"">.com?</span><o:p></o:p></li>
</ol>
<p class="MsoNormal"><span
style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.25in"><span
style="font-family:"Calibri","sans-serif"">Highly
restrictive means that latin cannot be mixed with Chinese
or Japanese characters.</span><o:p></o:p></p>
</blockquote>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><br>
Some script mixing *within* a label should be restricted as
it is a security risk. Script mixing across a FQDN or
between local part and host seem to be rather likely
scenarios instead.<br>
<br>
For certain scripts, ASCII admixture (just ASCII, not all of
Latin) would be common practice in the writing system and it
may be common enough/benign enough to allow it.<br>
<br>
However, you might also want to address European digits for
those scripts where native digits exist and are widely /
predominantly used, vs. scripts where the native digits are
more of historic/cultural interest. (In Arabic you have
both, depending on the region).<br>
<br>
Mixing digit sets in the same label should be a no-no and
indicated something's not well-formed. <o:p></o:p></span></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-left:.25in"><span
style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo2"><span
style="font-family:"Calibri","sans-serif"">I do not
understand “</span>Linkification should be determined by
the implied intent of the user's entry” <span
style="font-family:"Calibri","sans-serif"">Is
this intended to mean that the scheme (http, mailto,
etc) should be added to form the link? Or some other
determination of intent? If the former, it should be
stated more clearly.</span><o:p></o:p></li>
</ol>
</blockquote>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><br>
My naive interpretation had to do with things like tables or
data records where the purpose of a particular field would
be a URL. <o:p></o:p></span></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span
style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">tex</span><o:p></o:p></p>
<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="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a href="mailto:ua-discuss-bounces@icann.org"
moz-do-not-send="true">ua-discuss-bounces@icann.org</a>
[<a href="mailto:ua-discuss-bounces@icann.org"
moz-do-not-send="true">mailto:ua-discuss-bounces@icann.org</a>]
<b>On Behalf Of </b>Don Hollander<br>
<b>Sent:</b> Thursday, September 28, 2017 11:19 AM<br>
<b>To:</b> Universal Acceptance<br>
<b>Subject:</b> [UA-discuss] UASG010 - Quick Guide to
Linkification</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">A quick update on Linkification<o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">We have published an updated Quick
Guide to Linkification <a
href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuasg.tech%2Fwp-content%2Fuploads%2F2017%2F06%2FUASG010-Quick-Guide-to-Linkification.pdf&data=02%7C01%7Cmarksv%40microsoft.com%7Ce0ff7a322ef44f31a64208d507829df2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636423179950153243&sdata=gGQ5xhFTuJLf1kkFXWsOnfGdOH%2FMb0XbhK7tLiJfqzQ%3D&reserved=0"
moz-do-not-send="true">https://uasg.tech/wp-content/uploads/2017/06/UASG010-Quick-Guide-to-Linkification.pdf</a>
This builds on discussions we had post the UASG meeting in
Seattle in April.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">We are also working on an evaluation of
Linkification in major Social Media Communication
applications. (Here’s the link to the Help Wanted
advertisement - <a
href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuasg.tech%2Fwp-content%2Fuploads%2F2016%2F11%2FHelp-Wanted%25E2%2580%25A6-Linkification-Evaluation-1.0.pdf&data=02%7C01%7Cmarksv%40microsoft.com%7Ce0ff7a322ef44f31a64208d507829df2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636423179950153243&sdata=EuBYBxDZgX1FbvYLIbUE6RKuC4Jhk%2B7DQSrRa5guzH4%3D&reserved=0"
target="_blank" moz-do-not-send="true"><span
style="font-size:11.5pt;font-family:"Arial","sans-serif";color:black;background:#F6F6F6;text-decoration:none">Help
Wanted: Linkification Evaluation</span></a>)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">This evaluation is being built on a
replicable testing platform so that we can readily repeat
the process in the future. While early days, we expect
to provide a preliminary report during the ICANN60
meeting. As we go through the testing it is raising some
additional questions about our Good Practice guide and
expectations. We fully expect that once the evaluation is
completed we’ll again review UASG010 based on real world
experiences.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Don<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">Don Hollander<o:p></o:p></p>
<div>
<p class="MsoNormal">Universal Acceptance Steering
Group<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Skype: don_hollander<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</blockquote>
<p><o:p> </o:p></p>
</div>
</blockquote>
<p><br>
</p>
</body>
</html>