Why would "bite me" be an issue? This is the real world an anything goes.
Check out www.f---you.com (replace each "-" with letters you may feel would
make this URL offensive) and you will see that there's no forbidden
territory on the Internet.
-Eric
----- Original Message -----
From: "Derek J. Balling" <[EMAIL PROTECTED]>
To: "Tiger Technologies" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, August 23, 2000 2:05 PM
Subject: Re: Not ASCII chars in domain name ???
> Any chance that in doing so, one might inadvertantly register an
> offensive foreign word?
>
> e.g., if I register my ADASASKLDLJSA.com, and ADASASKLDLJSA happens
> to un-encode to "bite me" under some character set, isn't that an
> issue?
>
> D
>
> At 12:49 PM -0700 8/23/00, Tiger Technologies wrote:
> >At 8/23/00 12:15 PM, Charles Daminato wrote:
> >
> >>Based on this encoding system - is there any chance that two strings
using
> >>different character sets would translate to the same ASCII string?
> >>
> >>That would definitely cause problems (and is mathematically rare, but
> >>still statistically possible).
> >
> >No, no two script systems can generate the same UTF-5 Unicode encoding.
> >
> >The only danger is that an encoded Unicode string would match an
> >unencoded ASCII string as currently used in the DNS, but you can check
> >for that as you go along: in the unlikely event a Unicode-encoded string
> >matches an existing ASCII domain/TLD/etc, you just won't be able to
> >register/use that domain/TLD because it's already taken.
> >
> >--
> >Robert L Mathews, Tiger Technologies
>
>
>
