Re: Versioning (Re: [idn] The layers and character handling inDNS)

[Patrik Fältström <paf@cisco.com>]

At 18.28 -0500 01-02-19, John C Klensin wrote:
>  > - in the human-readable string. Will be pelted with rotten
>>  bananas. - in the DNS entry for the name. But since we can't
>>  get to the DNS-stored entry before we have done nameprep, the
>>  chicken-and-egg conundrum strikes again. - in the global
>>  /hosts.txt file?????
>>
>>  For any existing name, Nameprep can't change.
>
>Again, requires perfect wisdom.  Since we don't have that, I
>think you are adding to my argument that the current approach
>just cannot work.

We don't do the algorithms in nameprep. UTC does.

I claim they are better than we (as you say we don't have knowledge 
about these things) and that we don't have any other choice than 
pointing at them. Have anyone done a better job than UTC regarding 
normalization and case folding and creation of one charset? If so, 
the discussion is interesting whether we should go with UTC or 
someone else, depending on how many bugs there is in their tables.

NOT doing this solution and only a dictionary solution (something I 
think we need regardless) means staying with the subset of ascii 
accepted as "hostnames" for a very very long time. I don't see the 
market wanting to wait for that -- which includes changing all 
protocols, and all applications.

    paf