<html xmlns:v="urn:schemas-microsoft-com:vml" 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 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 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;}
/* 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;}
span.E-MailFormatvorlage17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.Section1
{page:Section1;}
-->
</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=DE link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Am I understanding right, that this would lead to inaccurate scoring
(pageranks, link popularity etc.)? But it would not lead to sites not being indexed
(you can index both possibly meant documents) and also not to links on the
result pages that lead different users to different documents, because the
links are in punycode anyway?<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Best<br>
Georg<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Von:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
mark.edward.davis@gmail.com [mailto:mark.edward.davis@gmail.com] <b>Im Auftrag
von </b>Mark Davis ?<br>
<b>Gesendet:</b> Mittwoch, 2. Dezember 2009 01:47<br>
<b>An:</b> Georg Ochsner<br>
<b>Cc:</b> Alexander Mayrhofer; Patrik Fältström; Michael Everson; IDNA update
work; Andreas Stötzner<br>
<b>Betreff:</b> Re: Mappings - some examples<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>When you build an index, you
follow links <i>as if the user clicked on them</i>. When the choice is
determinant, this is not a problem. So consider href='<a
href="http://schloss.de">schloß.de</a>'? If all browsers go to <a
href="http://schloss.de">schloss.de</a> (or fail), your choice is easy. That is
the current situation. During the transition period (of years), the choice is
hard, because the answer is not determinant.<br>
<br clear=all>
Mark<br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal>On Tue, Dec 1, 2009 at 12:22, Georg Ochsner <<a
href="mailto:g.ochsner@revolistic.com">g.ochsner@revolistic.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>Hello Mark,</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:11.0pt;color:#1F497D'>I don’t understand why it
would cause problems for search engines. Which would they be more in detail? In
the organic Google results you can link to the punycode version for the new ß
hosts. And you can still link to ASCII ss domains as well. I think this is very
clean actually, really everybody will get to the same hosts from the same
search results. Or is it about crawling or duplicate content, what you mean?</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:11.0pt;color:#1F497D'>Thanks</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:11.0pt;color:#1F497D'>Georg</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<div style='border:none;border-left:solid windowtext 1.5pt;padding:0cm 0cm 0cm 4.0pt;
border-color:-moz-use-text-color -moz-use-text-color -moz-use-text-color blue'>
<div>
<div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0cm 0cm 0cm;
border-color:-moz-use-text-color -moz-use-text-color'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt'>Von:</span></b><span style='font-size:10.0pt'> <a
href="mailto:mark.edward.davis@gmail.com" target="_blank">mark.edward.davis@gmail.com</a>
[mailto:<a href="mailto:mark.edward.davis@gmail.com" target="_blank">mark.edward.davis@gmail.com</a>]
<b>Im Auftrag von </b>Mark Davis ?<br>
<b>Gesendet:</b> Dienstag, 1. Dezember 2009 21:03<o:p></o:p></span></p>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt'><br>
<b>An:</b> Georg Ochsner<br>
<b>Cc:</b> Alexander Mayrhofer; Patrik Fältström; Michael Everson; IDNA update
work; Andreas Stötzner<br>
<b>Betreff:</b> Re: Mappings - some examples<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'>I think
this is somewhat like the TRANSITIONAL strategy that I suggested. The
intermediate browser feature you suggest wouldn't work, however.<br>
<br>
A UI would be really ugly in practice. The venders have found that simple icons
don't alert people - what you have to do is go to a special intermediate page
with strong warnings, and have a Continue and Back button.<br>
<br>
If you are on an old browser, of course, you'd still go to 'ss'.<br>
<br>
And it won't work with search engines (we don't have little men in our servers
at Google who can decide what's real and what's not.<br>
<br>
And it won't work for email (without some really ugly bounceback).<br>
<br clear=all>
Mark<o:p></o:p></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On
Tue, Dec 1, 2009 at 06:45, Georg Ochsner <<a
href="mailto:g.ochsner@revolistic.com" target="_blank">g.ochsner@revolistic.com</a>>
wrote:<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hello
Mark,<br>
<br>
what about a fourth scenario?<br>
<br>
1. IDNA2008 clearly says that ß is PVALID an shall not be mapped to ss anymore.<br>
2. Browsers get an additional feature. It informs users when typing a hostname
with ß that previously they would have been redirected to the ss sibling. And
that they now need to use ss in order to get to the old destination.<o:p></o:p></p>
<blockquote style='border:none;border-left:solid windowtext 1.0pt;padding:0cm 0cm 0cm 6.0pt;
margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt;
border-color:-moz-use-text-color -moz-use-text-color -moz-use-text-color rgb(204, 204, 204)'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>3.
Registries wait until IDNA2008 is spread, let’s say more widely than IDNA2003
is until now. (That is 6 years and with still xx% IE6s out there)<br>
4. Registries inform the registrants and offer a grandfathering registration
(like the .mx registry recently did) that allows all registrants of domain
names with ss to register the ß sibling if they like.<br>
5. Registration is opened to the public and people realize that
"machines" now distinguish ß from ss like humans do.<br>
<br>
Please add more useful steps between 1. and 5. :-)<br>
<br>
Best regards<br>
Georg<br>
<br>
<br>
<br>
-----Ursprüngliche Nachricht-----<br>
Von: <a href="mailto:mark.edward.davis@gmail.com" target="_blank">mark.edward.davis@gmail.com</a>
[mailto:<a href="mailto:mark.edward.davis@gmail.com" target="_blank">mark.edward.davis@gmail.com</a>]
Im Auftrag von Mark Davis ?<br>
Gesendet: Montag, 30. November 2009 19:01<br>
An: Georg Ochsner<br>
Cc: Alexander Mayrhofer; Patrik Fältström; Michael Everson; IDNA update work;
Andreas Stötzner<br>
Betreff: Re: Mappings - some examples<o:p></o:p></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br>
Even for English, IDNA does not permit all valid words: "Joe's Bar"
will not work, because of both the space and the apostrophe and
"Joe'sBar" because of the apostrophe. IDNA2008 explicitly does not
permit all sequences that would be valid words in all languages; nor could it
do otherwise.<br>
<br>
There are two compatibility problems:<o:p></o:p></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>1.
Existing web pages and other documents that contain ß and expect to go to
location X and not Y.<br>
2. There is still an existing body of billions of browsers that will take years
to disappear (as Erik points out, something like 20% of browsers are still
IE6).<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'>Let's
suppose that IDNA2008 allows ß, and that the newer browsers use it (and not a
compatibility scheme like <a href="http://unicode.org/reports/tr46/"
target="_blank">http://unicode.org/reports/tr46/</a>). The only real purpose to
allowing ß is so that you can distinguish from ss. But what happens when Herr
Stosser gets <a href="http://stosser.at" target="_blank">stosser.at</a> and
Herr Stoßer gets <a href="http://stosser.at" target="_blank">stoßer.at</a>?<br>
<br>
Initially, 100% of all browsers will go to the ss form. Nobody will go to
Stoßer's site; his email won't work, etc.: href="<a
href="http://stosser.at" target="_blank">stoßer.at</a>" goes directly to
"<a href="http://stosser.at" target="_blank">stosser.at</a>". Even on
Stoßer's site, absolute intrapage links will go to the 'wrong' place. After a
while, some newer browsers will take page href="<a href="http://stosser.at"
target="_blank">stoßer.at</a>" and go to <a href="http://stosser.at"
target="_blank">stoßer.at</a>, while all the other browsers will go to
href="<a href="http://stosser.at" target="_blank">stosser.at</a>".
The same goes for email. So access to all of those links (and mail, etc.) will
be unreliable, and the subject of security and compatibility problems. As a
result, practically, people would be unable to use href="<a
href="http://stosser.at" target="_blank">stoßer.at</a>" in their web pages
or in email until essentially all existing browsers were supplanted, which will
be maybe 5 years down the line. And during that time, these will also bollux up
all the search engines, since indexing assumes that links don't have ambiguous
targets.<br>
<br>
And that assumes that nobody does use a compatibility mechanism. Another, more
likely, alternative based on our conversations with vendors is that people
disregard that part of IDNA2008, and use a compatibility mechanism like <a
href="http://unicode.org/reports/tr46/" target="_blank">http://unicode.org/reports/tr46/</a>;
that allows the browsers, emailers, search engines and others to keep
functioning correctly - there is no transition. The downside is that you can't
register both <a href="http://stosser.at" target="_blank">stosser.at</a> and <a
href="http://stosser.at" target="_blank">stoßer.at</a>. So of the thousand Herr
Stoßers, instead of one of them getting that name, none of them do; it's like
"Joe'sBar". And, of course, there is the disadvantage of having UTS46
have to exist in the first place.<br>
<br>
The third alternative is the really awful one: the "let a thousand flowers
bloom" scenario. In this scenario, there is no single compatibility
mechanism like <a href="http://unicode.org/reports/tr46/" target="_blank">http://unicode.org/reports/tr46/</a>;
instead, we get different variants from different vendors, and the situation is
chaotic. That is the scenario that the Unicode consortium's members are really
concerned with. While the ideal solution would be an IDNA2008 that maintained
compatibility with IDNA2003, the second best solution is only one compatibility
mechanism; not dozens.<br>
<br>
Mark<br>
<br>
On Mon, Nov 30, 2009 at 07:55, Georg Ochsner <<a
href="mailto:g.ochsner@revolistic.com" target="_blank">g.ochsner@revolistic.com</a>>
wrote:<br>
> -----Ursprüngliche Nachricht-----<br>
> Von: <a href="mailto:idna-update-bounces@alvestrand.no" target="_blank">idna-update-bounces@alvestrand.no</a>
[mailto:<a href="mailto:idna-update-" target="_blank">idna-update-</a><br>
> <a href="mailto:bounces@alvestrand.no" target="_blank">bounces@alvestrand.no</a>]
Im Auftrag von Alexander Mayrhofer<br>
> Gesendet: Montag, 30. November 2009 15:57<br>
<br>
> > I would though be more "on your side" if the number of
domain<br>
> > names that contained ß where say 100 times higher than today<br>
> > in published documents. Because then people would be TOLD to<br>
> > type in something (ß) that mapped to something else (ss) that<br>
> > was registered. That, I claim, is not the case. At least not<br>
> > "heavily".<br>
><br>
> I understand that. And i'm saying that the potential of around 500<br>
> useful "ß" registrations (based on looking through our inventory
of 900k<br>
> domains) is by far not worth the effort.<br>
In several talks with people from the Austrian registry I've now heard this<br>
argument. But I think this decision should not be made depending on<br>
commercial factors. IDNA is in my eyes not a question of return on<br>
investment but about the native use of language in domain names around the<br>
globe. Once more, the Austrian registry can still refuse to have sharp s<br>
registered within their namespace, but maybe other registries pay more<br>
attention to the language aspect than to commercial calculations.<br>
<br>
Best regards<br>
Georg<br>
<br>
_______________________________________________<br>
Idna-update mailing list<br>
<a href="mailto:Idna-update@alvestrand.no" target="_blank">Idna-update@alvestrand.no</a><br>
<a href="http://www.alvestrand.no/mailman/listinfo/idna-update" target="_blank">http://www.alvestrand.no/mailman/listinfo/idna-update</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</body>
</html>