[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[idn] Unicode tagging
- To: <idn@ops.ietf.org>
- Subject: [idn] Unicode tagging
- From: "Edmon" <edmon@neteka.com>
- Date: Wed, 16 Aug 2000 10:34:31 -0400
- Delivery-date: Wed, 16 Aug 2000 07:33:58 -0700
- Envelope-to: idn-data@psg.com
>
> > As the information density per octet depends on the encoding used, I
> > do not think we can have this as a measurement. And you are right
> > that the number of characters is not correct either, one character in
> > Chineese can be a whole word. But one example of being fair is that
> > if 63 characters are allowed using ASCII, 63 characters must also be
> > allowed using ISO 8859-1 (or other latinbased character sets).
> > When we use UTF-8, the protocol will have space for more ASCII
characters
> > than ISO 8859-1 characters. To be fair, ASCII must still be restricted
> > to 63 characters even if the protocol have space for more.
> > This restriction is also very important for implementors.
>
> I dont think arbitrary restrictions are good at any machine level. The
only
> arbitrary restrictions should be made through registry policies.
> Technically, names should be verified to be non-existent only after
> searching through the DNS.
>
> >
> > Dan
> >
>