| 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. As I recall BIND (which as I pointed out is an implementation of the spec, not the spec itself), makes the checking for prohibited characters in labels optional, so this is not without precedent. -bws
- Re: [idn] IDN character repertoire, nameprep Joel Rowbottom
- Re: [idn] IDN character repertoire, nameprep Edmon
- RE: [idn] IDN character repertoire, nameprep Brian W. Spolarich
- Re: [idn] IDN character repertoire, nameprep Mark Welter
- RE: [idn] IDN character repertoire, nameprep Brian W. Spolarich
- Re: [idn] IDN character repertoire, nameprep Johnny Eriksson
- Re: [idn] IDN character repertoire, nameprep Marc Blanchet
- Re: [idn] IDN character repertoire, nameprep Adam M. Costello
- Re: [idn] IDN character repertoire, nameprep Mark Welter
- Re: [idn] IDN character repertoire, nameprep Adam M. Costello
- Re: [idn] IDN character repertoire, nameprep Brian W. Spolarich
- Re: [idn] IDN character repertoire, nameprep Edmon
- Re: [idn] IDN character repertoire, nameprep John C Klensin
- Re: [idn] IDN character repertoire, nameprep Joel Rowbottom
