James Seng wrote:
"There is a genuine user problem here (though whether one should
actually solve it is still an open question)."
If DNS was run more like a search system the possibilities of address
resolution are endless. The same is true of ENUM lookups as well. All we
need is Root Search Servers and well known addresses for them and poof.
DNS goes away and a fully TCP based authenticated http type query and
response API could seamlessly replace DNS.
Todd Glassey
It is a genuine user problem but I disagree with your latter statement.
It is not an open question it must be solved. It is a serious enough
problem for Chinese that it must be resolve for the Chinese user. The
open question is "how", not "if".
For some background on CJK ideograph, you may refer to an expired
draft I wrote many years ago
http://james.seng.sg/files/draft-ietf-idn-cjk-01.pdf
RFC 3743 will also be a good point of reference.
-James Seng
On Sat, Nov 7, 2009 at 3:33 AM, Andrew Sullivan <[email protected]
<mailto:[email protected]>> wrote:
On Fri, Nov 06, 2009 at 07:06:38PM +0000, Alex Bligh wrote:
> I should probably declare my hand in that I think in most cases the
> variant stuff is a non-problem (blocking is adequate apart from
> where the user is likely to mistype themselves)
According to some people I'm inclined to believe (I can't say this
from personal experience), in non-alphabetic scripts there is indeed a
serious problem with respect to variants. It's not actually like the
case of (say) colour vs. color, because users tend to have access to
one version or another of the "same" character, but that character is
actually encoded under Unicode as a different character. This is, I
am led to believe, a very common problem in areas where, for instance,
Simplified and Traditional Chinese characters are both in regular use.
The upshot is that every competent user of the language will recognize
two different arrangements of symbols as "the same word", each user
will be able to type one or the other of the arrangements (but not
both) at their keyboard, and yet the two different arrangements do not
constitute equvalent labels. So, it's as though by configuring your
system with locale en-CA, you were _unable_ to type "color.com
<http://color.com>" into a
resolution context. There is a genuine user problem here (though
whether one should actually solve it is still an open question).
Best,
A
--
Andrew Sullivan
[email protected] <mailto:[email protected]>
Shinkuro, Inc.
_______________________________________________
DNSOP mailing list
[email protected] <mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/dnsop
------------------------------------------------------------------------
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.425 / Virus Database: 270.14.52/2485 - Release Date: 11/06/09 19:39:00
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
