Re: [idn] opting out of SC/TC equivalence

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

--On 2001-08-29 13.24 +0200 Harald Tveit Alvestrand <harald@alvestrand.no>
wrote:

>> 2) I assume (since I did not check)  that  about 23,658 code
>> points in Unicode 3.0 has included Hanja and Kanji.
>> The other codepoints in Unicode and future new comers,
>> can be treated on needed base.  This means, only when
>> someone has used in a name at registration time, and
>> supplied the name with a codepoint in Unicode, then the
>> codepoint is added to zonefile.  (Not in [nameprep]?)
>>  If such a character is not in Unicode, then a bit map of the
>> new character has to be provided in the zonefile.  This is
>> the reason, I propose a "Request for Reference to be sent"
>> protocol to be drafted.
> 
> Better check....
> 
> So you foresee a system where
> 
> - User upgrades his data entry system
> - User types a new ideograph into his systemm
> - The client software calls out to some global repository for the
>   new canonical dideograph decomposition of the new ideograph
> - The DNS system looks up the decomposition, not the original codepoint
> - The server knows enough to canonically decompose the zonefile's
> ideograph - All this works correctly for software written by Indian
> programmers for   American companies?
> 
> Seems complicated to me....

I rather see people come with comments on current text about versioning in
the nameprep document than starting all over again with new ideas.
Versioning is complicated, but Mark and myself though quite a lot on the
text which describes how clients and servers are to handle "unassigned"
codepoints.

  paf