<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:Z="urn:schemas-microsoft-com:" 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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:0in;
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.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";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:268851654;
mso-list-type:hybrid;
mso-list-template-ids:-525162966 -209938612 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
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]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Agreed pretty much. Sorry I haven’t followed the
recommendations for the casing, etc. rules, however disambiguating the mapping
and Unicode<->Punycode rules from the disallowed set would “solve” (some
of) the problems that cause IE7 to not look up unassigned characters.<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=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Shawn<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 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"'>
mark.edward.davis@gmail.com [mailto:mark.edward.davis@gmail.com] <b>On Behalf
Of </b>Mark Davis<br>
<b>Sent:</b> , 08, 2008 18:30<br>
<b>To:</b> Erik van der Poel<br>
<b>Cc:</b> Shawn Steele; idna-update@alvestrand.no<br>
<b>Subject:</b> Re: Archaic scripts<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>I agree.<o:p></o:p></p>
<div>
<p class=MsoNormal>On Thu, May 8, 2008 at 4:01 PM, Erik van der Poel <<a
href="mailto:erikv@google.com">erikv@google.com</a>> wrote:<o:p></o:p></p>
<p class=MsoNormal>An unassigned codepoint may be assigned to an uppercase
letter. So a<br>
piece of software that looks up purported U-labels must check whether<br>
it contains any unassigned codepoints. So we should recommend that<br>
such software be restricted (follow certain rules), in order to<br>
achieve interoperability. (MSIE7 refuses to look up domain names<br>
containing unassigned characters.)<br>
<br>
If we lock down the DISALLOWED set too tightly, we may regret it<br>
later. One way to avoid locking it down is to recommend that<br>
burned-in-ROM and other unupgradable software only use protocols that<br>
use LDH- and A-labels. All pieces of software, whether IDNA-aware or<br>
not, are explicitly permitted to look up Punycode labels, without<br>
decoding them to check for DISALLOWED, CONTEXT*, etc.<br>
<br>
On the other hand, we should recommend that protocol and application<br>
developers only use U-labels if they are willing to make their<br>
software upgradable. They need to do this for unassigned codepoints<br>
anyway. So we might as well allow for the possibility of moving some<br>
characters from DISALLOWED to other categories (if and when we<br>
determine that they should be moved, having come up with better<br>
criteria for use in IDNs, more information, clamoring users, etc).<br>
<br>
If we allow for this possibility, we don't need to fret so much about<br>
historic scripts right now. Just dump them in DISALLOWED for now, and<br>
deal with them later, if they ever need to be dealt with.<br>
<span style='color:#888888'><br>
Erik</span><o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><br>
On Thu, May 8, 2008 at 1:59 PM, Shawn Steele <<a
href="mailto:Shawn.Steele@microsoft.com">Shawn.Steele@microsoft.com</a>>
wrote:<br>
> Erik wrote:<br>
><br>
> > This also neatly solves the problem of whether or not
IDNA-unaware and<br>
> > IDNA-aware clients are allowed to look up labels with Punycode
in<br>
> > them. They should always be allowed to do so. Only software
that tries<br>
> > to convert from U-labels to A-labels needs to be restricted.
This is<br>
> > how we can achieve the most reasonable level of
interoperability, in<br>
> > my opinion.<br>
><br>
> I think that conversion U to A conversion does NOT need restriction.
Assuming that the steps in conversion include NFKC or appropriate
mappings, then if a character moves from disallowed to allowed, the conversion
is already known. So no change is required for lookup, even if conversion
is required. The only change would be the software the decides the legality of
the name, which, IMO could be at a different layer.<br>
><br>
> - Shawn<br>
><br>
><br>
><br>
> _______________________________________________<br>
> Idna-update mailing list<br>
> <a href="mailto:Idna-update@alvestrand.no">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><br>
><br>
_______________________________________________<br>
Idna-update mailing list<br>
<a href="mailto:Idna-update@alvestrand.no">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>
</div>
<p class=MsoNormal><br>
<br clear=all>
<br>
-- <br>
Mark <o:p></o:p></p>
</div>
</body>
</html>