Re: [idn] call for comments for REORDERING

["Soobok Lee" <lsb@postel.co.kr>]

HI, James

I will answer one by one for your  questions.

----- Original Message ----- 
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>; "Martin Duerst" <duerst@w3.org>
Sent: Friday, October 19, 2001 10:09 AM
Subject: Re: [idn] call for comments for REORDERING


> 
> And with the existing draft, it does not explain how it going to deal
> with new codepoints in ISO10646 in the future, nor does it explain the
> process to implementing them. The critia here is stablity - if new code
> is added and tables for re-ordering expand, then the algorithm should
> not make existing names invalided.

REORDERING's mapping occurs within each script block, NOT across script blocks.
Therefore, new additions of script block won't invalidate or collide
with existing names. Even additions of new rarely used characters in 
existing script block won't affect the performance of REORDERING.
In this respect, REORDERING maintains stability over time.

Current IDNA/nameprep does not prohibit, but discourage including unassigned code points in legal IDN labels, because new normalization/case mappings
would be defined on them in the future. some ACE labels including unsigned code block (tagalog?) might be proven invalid in the future. Nameprep/NFKC Versioning tag schems using new ACE prefix will be needed in the future, i guess.

Therefore, REORDERING  follows the same IDNA/nameprep recommendations on the issues
of new SCTIPT blocks/unsigned code points. 

This statements will be included in the final version of REORDERING I-D.

Thanks.

Soobok Lee