Re: [idn] IDN character repertoire, nameprep

["Edmon" <edmon@neteka.com>]

> > ...and since speeding is illegal, we can do away with the highway
> > patrol.
>
> Is this an argument in favor of checking for prohibited names in client
> applications?  Today's client applications don't check for prohibited
> names (like a+b.com), and this hasn't led to any catastrophes.  Today
> canonicalization and prohibition are both performed on the server side.
> Nameprep proposes to perform both functions on the client side.  I'm
> suggesting that a less drastic change (performing canonicalization
> but not prohibition on the client side) may be sufficient, and even
> preferrable.
>

I think it only makes sense to do prohibition in the server end because if a
user types in a "prohibited" name it would probably be non-existent, and
therefore will not resolve anyway.  Just like leading and ending "-" today,
they are "prohibited" but applications usually send it out.  Zone
operators/registries usually do not allow these records to be created.
Edmon