[idn] A Search-based access model & SC/TC conversion

[=?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>]

Hi !  Klensin:
           May  I  ask a question related in draft-klensin-dns-search-01.txt
?
2. A three (or four) search-layer environment.
(1) The DNS, with the existing lookup mechanisms
(2) A restricted, facet-based, search system.
(3) Commercial, localized, and potentially topic-specific, search
   environments.
(4) Something else?

          The current existed and used Letter-Digit-Hyphen DNS server is the
Layer1 mechanism. Now ,what is the layer of   nameprep + IDNA  ?  Actually,
the native coded multilingual domain name  will be treated by AP and passed
to nameprep module and transfomed to ACE name, the ACE name will be feed to
resolver of LDH-DNS , so it is backward compatible to pure ASCII  domain
name.
           The input of resolver module is the interface of Layer2 and
Layer1   ?
> >
> > If you can come up with a proposal that describes what to do
> > about ALL the Han characters in Unicode, I will be very happy
> > to hear it.
> >
>
> And, unless whatever is done is isolated -- through procedures,
> structure, or layering-- in a way that is robust, accessible to
          I think the procedures, stucture, or layering is the module above
layer1 ?
But it must be between name-input of AP and Layer 1 input interface . My
question is
what is the relation betwwen IDNA , Layer 3 , Layaer 2 , nameprep and  Layer
1 ?
Does IDNA and nameprep are in the layer of  Layer 2 ?  How a restrict facet
search system  communicate with Layer1 thru which module ?

> all users of URLs based in the Chinese language, and that does
> not fragment the Internet, we also need to be sure that the
> tables and mechanisms that do SC/TC equivalence don't
> accidentally map Kanji or Hangul into SC.

    Does there are a defined port or module interface to let the isolated
function module can be link to cooperation ?  Thanks !

L.M.Tseng