[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] Alpha Online
Hi ! All:
I think there are some confusing in here.
1.People using non-ASCII want their non-ASCII characters after ACE encoding
can keep the information of original character case in the
2.The alphabet case of ASCII-ACE-STRING can be preserved and keep in
3.The comparison of ASCII-ACE-STRING is still case insensitive in DNS and
4.That is say to do ASCII-STRING comparison in DNS or URI must forced the
ASCII-ACE-STRING to lower case and can not be recovering of these original
information FOREVER is over requirement/specification.
5.No one want to violate the backward compatibility of DNS and URI.
> There are lots of postings here (I just rejoined this mailing list)
> presuming that case sensitive domain names are reasonable or even
> Yet RFC 1035 "Domain Names - Implementation and Specification" says
> (on page 8):
> Note that while upper and lower case letters are allowed in domain
> names, no significance is attached to the case. That is, two names
> the same spelling but different case are to be treated as if
> And RFC 2616 "HTTP/1.1" in section 3.2.3 "URI Comparison says
> (on page 20):
> When comparing two URIs to decide if they match or not, a client
> SHOULD use a case-sensitive octet-by-octet comparison of the entire
> URIs, with these exceptions:
> - A port that is empty or not given is equivalent to the default
> port for that URI-reference;
> >>>> - Comparisons of host names MUST be case-insensitive;
> - Comparisons of scheme names MUST be case-insensitive;
> - An empty abs_path is equivalent to an abs_path of "/".
> It's likely that the attempt to retroactively introduce case sensitive
> domain names will simply break almost all deployed Internet software.
> - Ira McDonald
> High North Inc
> -----Original Message-----
> From: D. J. Bernstein [mailto:firstname.lastname@example.org]
> Sent: Wednesday, February 06, 2002 5:28 PM
> To: email@example.com
> Subject: Re: [idn] Alpha Online
> The question remains: Will an Alpha Online organization be allowed to
> register qol.com, with q changed to a lowercase alpha?
> Or will ICANN take the domain name away and give it to AOL, because the
> uppercase version of the name is visually identical to AOL.COM? Is it
> okay if Alpha Online never uses the uppercase version of the name, and
> client software doesn't automatically convert names to uppercase?
> The question is whether case insensitivity will---beyond imposing huge
> software costs and creating huge new opportunities for fraud---prevent
> legitimate users from registering perfectly reasonable domain names.
> Dave Crocker writes:
> > predictions about trademark disputes are best left to experienced
> > trademark attorneys.
> I will readily agree that the exact definition of ``likelihood of
> confusion'' in trademark law is beyond your legal experience. However,
> I'm sure you can grasp the fact that the picture
> has a conflict with the identical picture
> even though one of the A's is represented inside a computer as the Latin
> A while the other one is represented as the Greek Alpha.