Re: [idn] Document Status?

["Edmon Chung" <edmon@neteka.com>]

fine.  aside from making the doc more readable to ppl who need to use it on
development works, whatelse do we need to add to IDNA?  Personally I dont
quite like the new bidi arrangement, but since I know nothing about the
languages, I have nothing much to offer.  Except perhaps that I do know that
Chinese also has a bidi issue!  I havent seen anyone raise this, but sure
enough Chinese could be written from right to left with English words going
left to right.  Pretty much like the Arabic case.  Anyway, that was not my
point... Other than that, I think the IDNA framework is fairly stable now,
whether it is because people are just too tired to keep talking about it or
that we have successfully dealt with the mulitple issues and found some
ground that we could live with.  Going forward, there are really just two
things I can see that needs real thoughts:

1. A set of possible transition schemes that will get us from here to IDNA
2. Do we want anything beyond IDNA?  Perhaps a protocol that handles the
binary correctly...

what are your thoughts on the remaining issues anyway?

Edmon


----- Original Message -----
From: "Dave Crocker" <dhc@dcrocker.net>
To: "Edmon Chung" <edmon@neteka.com>
Cc: "Eric A. Hall" <ehall@ehsco.com>; <idn@ops.ietf.org>
Sent: Tuesday, September 03, 2002 6:47 PM
Subject: Re: [idn] Document Status?


> At 05:38 PM 9/3/2002 -0400, Edmon Chung wrote:
> >I cannot agree more to Eric's analogy.  To me the key is that IDN has to
be
> >used in multiple apps and it is therefore important we consider that.
>
> TCP is used in multiple apps.  I guess we had better not standardize it
> until we have considered that.
>
> HTTP is used in multiple apps.  I guess we...
>
> You are confusing host-specific implementation issues with network
protocol
> issues.
>
> > > Furthermore, MIME and its constituent application protocols are being
> > > extended so that binary data *CAN* be transferred ...
> >
> >This is what IDNA has not provided us with and what we probably should
> >consider.  I am not sure when... but now might be a good time to start.
>
> Actually, now is a particularly bad time to start.
>
> Starting now provides excellent distraction from the necessary focus on
the
> immediate work, namely IDNA.
>
> d/
>
>
> ----------
> Dave Crocker <mailto:dave@tribalwise.com>
> TribalWise, Inc. <http://www.tribalwise.com>
> tel +1.408.246.8253; fax +1.408.850.1850
>
>
>