Re: [idn] Update Charter revision 2

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

----- Original Message ----- 
From: "David Hopwood" <david.hopwood@zetnet.co.uk>
> 
> It is worth pointing out that:
> 
>  - IDNA does not satisfy requirements 11 (since it allows unassigned
>    codepoints in queries without versioning) and 18 (since it allows
>    more than one representation of a name, differing in case),
> 
> IMHO there is little point in publishing a document specifying
> requirements that are unachievable.
> > 
> > [11] The protocol should handle with care new revisions of the CCS.
> > Undefined codepoints should not be allowed unless a new revision of
> > the protocol can handle it. Protocol revisions should be tagged.
> 
> The current version of nameprep allows unassigned code points in queries
> without revision tagging, for good reasons.
> 
> => [11] The proposal should handle with care new revisions of the CCS.
> => Proposals MUST discuss how undefined codepoints are handled.

I agree on this modification.

current nameprep I-D:

  1) old nameprep's applications may find its unassigned code points in
      received queries that come from newer nameprep's applications.
  2) but, old nameprep cannot generate ACE labels with at least one
      unassigned code point.

2) requires  old nameprep applications should be upgraded to
support newly assigned script. Auto-update  features will help 
some interative applications, but may not be available  for  
non-interative/offline-mode idn-aware applications or embedded IDNA
applets / OCX components which has no human or outerworld interaction.
Some disruption/failure in service may be caused by this latter situation.

Soobk Lee