<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 25 Dec 2018, at 21:58, John Levine <<a href="mailto:john.levine@standcore.com" class="">john.levine@standcore.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">In article <<a href="mailto:2eb428e5-ed29-a914-23e3-7889b427b69d@ix.netcom.com" class="">2eb428e5-ed29-a914-23e3-7889b427b69d@ix.netcom.com</a>> you write:<br class="">
<blockquote type="cite" class="">What about "www." being an optional subdomain?<br class="">
<br class="">
How are the techniques used to handle this different from having an IDN <br class="">
alias?<br class="">
</blockquote>
<br class="">
I think it's pretty safe to assume that <a href="http://foo.com" class="">foo.com</a> and
<a href="http://www.foo.com" class="">www.foo.com</a> are in<br class="">
the same language, and if one redirects to the other, nobody will be<br class="">
confused. Even so, getting it to work right is not totally trivial.<br class="">
The two names need their own SSL certificates, or if there's one cert<br class="">
it has to be validated for both names. If the site uses cookies as<br class="">
most do to manage site logins or user options, it has to be sure the<br class="">
cookies for the two names are kept in sync or all forced to one of the<br class="">
names.<br class="">
<br class="">
None of this is terribly hard, but it's not automatic either.<br class="">
<br class="">
<blockquote type="cite" class="">Yes, I did note the passage on language negotiation, but how is that
<br class="">
different from sites that can be accessed via ccTLDs in addition to a <br class="">
domain name in a gTLD. That's a pattern typical for many global <br class="">
organizations.<br class="">
</blockquote>
<br class="">
Same answer, except that if one name isn't a subdomain of the other,<br class="">
the login and option cookie problems are a lot harder.<br class="">
<br class="">
<blockquote type="cite" class="">How are any of these issues materially different from offering your site
<br class="">
with multiple localized names?<br class="">
</blockquote>
<br class="">
The point, which I apparently wrongly thought was obvious, is that none<br class="">
of this multi-name stuff works automatically, and telling people "just<br class="">
add a bunch of IDN names and EAI addresses" is not going to end well.<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>There is one part that can happen automatically. If the web authors have used relative addressing throughout their website then the url will automatically inherit the Domain Name being used on entry. So if
<a href="http://icann.org" class="">icann.org</a> is used on entry then <a href="http://icann.org" class="">
icann.org</a> will show and stick in the browser address bar. If icann.संगठन is used on entry then icann.संगठन will show and stick in the browser address bar.</div>
<div><br class="">
</div>
<div>Whether or not one then adapts website content according to which Domain Name is used is a different issue</div>
<div><br class="">
</div>
<div>André Schappo</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div class=""><br class="">
R's,<br class="">
John<br class="">
<br class="">
PS:<br class="">
<br class="">
<blockquote type="cite" class="">PS: some non-European scripts can have variants that work similar to
<br class="">
case-equivalence. If you want to institute loose matching of e-mail <br class="">
usernames based on them, you'd have to roll your own -<br class="">
</blockquote>
<br class="">
Yes, people who are working about EAI are aware of the way that local<br class="">
part matching works. Since every mail system already has its own<br class="">
loose matching rules, it's not a new problem but it's not one that<br class="">
anyone has thought much about for EAI mail addresses. I can<br class="">
definitely tell you that without loose address matching that matches<br class="">
user expectations, whatever they are, your customers will hate you and<br class="">
decide that your system is unusable.<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
<div class="">
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); font-family: "Arial Unicode MS"; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
🌏 🌍 🌎<br class="">
André Schappo<br class="">
<a href="mailto:%E5%B0%8F%E5%B1%B1@%E7%94%B5%E9%82%AE.%E5%9C%A8%E7%BA%BF?Subject=%E4%BD%A0%E5%A5%BD%E5%B0%8F%E5%B1%B1%F0%9F%98%9C" class="">小山@电邮.在线?Subject=你好小山😜</a><br class="">
<a href="https://schappo.blogspot.co.uk" class="">schappo.blogspot.co.uk</a><br class="">
<a href="https://twitter.com/andreschappo" class="">twitter.com/andreschappo</a><br class="">
<a href="https://weibo.com/andreschappo?is_all=1" class="">weibo.com/andreschappo?is_all=1</a><br class="">
<a href="https://groups.google.com/forum/#!forum/computer-science-curriculum-internationalization" class="">groups.google.com/forum/#!forum/computer-science-curriculum-internationalization</a><br class="">
<br class="">
</div>
</div>
</div>
<br class="">
</body>
</html>