Re: [idn] amending [IDNA]?

[liana.ydisg@juno.com]

Hi,  Harald:

I am thinking a black box procedure, which can
be at a client site, or at local server site depending
on current network configuration.  If it is at client site,
then any existing transport scheme can be used.  If
it is at a server site, then it works like a gateway to
its current local clients using local character code 
standard, such as in Japan and China. 

idn-label(input, tag-file, input-std, zonefile, idn-name)
input: any input stream as a label in input-std
tag-file: script tags where its code blocks of Unicode table are defined,
	this should be registered and tested before distribution.
 example: lat-  block1	block2	block3
	This allows [nameprep] be divided by tags, and allows 
	mixed scripts within a tagged range. 
zonefile: applied to server site; for a client site, it may be default a
cookie?

All these local parameters shall be a part of config package. For
a user, one has to select a tag and a display code standard. 

Liana


On Tue, 28 Aug 2001 15:14:52 +0200 Harald Tveit Alvestrand
<harald@alvestrand.no> writes:
> 
> 
> --On 17. august 2001 18:03 -0700 liana.ydisg@juno.com wrote:
> 
> > The IDN-label protocol is:
> >
> > idn-label(input, tag-file, input-std, zonefile, idn-name)
> > {
> >   tag = find-tag(input, tag-file, input-std);
> >   switch (tag)
> > 	{
> 
> I take it "idn-label" is a procedure to convert an input string into 
> an IDN 
> label for use in the DNS.
> 
> could you please explain a little more where the tag-file, input-std 
> and 
> zonefile arguments to the IDN-label protocol come from?
> 
> are these local parameters at the client, or does this occur at a 
> different 
> place in the system?
> 
> I do not understand.
> 
>              Harald
> 
> 
>