Re: Layer 2 and "idn identities" (was: Re: [idn] what are the IDN identifiers?)

liana Ye <liana.ydisg@juno.com> Fri, 07 December 2001 09:17 UTC

Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16780 for <idn-archive@lists.ietf.org>; Fri, 7 Dec 2001 04:17:50 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1) id 16CGyB-000FPk-00 for idn-data@psg.com; Fri, 07 Dec 2001 01:06:59 -0800
Received: from m2.boston.juno.com ([64.136.24.65]) by psg.com with esmtp (Exim 3.33 #1) id 16CGyA-000FPd-00 for idn@ops.ietf.org; Fri, 07 Dec 2001 01:06:58 -0800
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VVLRvc78EsZs6+O3132nL5Xw==">
Received: (from liana.ydisg@juno.com) by m2.boston.juno.com (jqueuemail) id GM2XU69B; Fri, 07 Dec 2001 04:05:36 EST
To: idn@ops.ietf.org
Date: Fri, 07 Dec 2001 01:06:59 -0600
Subject: Re: Layer 2 and "idn identities" (was: Re: [idn] what are the IDN identifiers?)
Message-ID: <20011207.010659.-355179.0.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.5
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 0-17,19-28
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana Ye <liana.ydisg@juno.com>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The solution that I have descibed for TC/SC problem,
as well as associated CJK problem using lanugage tag
is in 
http://search.ietf.org/internet-drafts/draft-liana-idn-map-00.txt

and phonetic encoding of IDN identifiers is described in

http://search.ietf.org/internet-drafts/draft-ietf-idn-step-01.txt

Updated versions of both will be submitted if I have 
 enough supports for the idea to be discussed and 
developed  in the group.  I need 7 supports. 

Thanks.

Liana


On Fri, 7 Dec 2001 13:14:20 +0800 "James Seng/Personal"
<jseng@pobox.org.sg> writes:
> > To get IETF interested in a solution, there are typically two step.
> > 1. Conviencing the IETF it is a worthwhile problem to solve
> > 2. Presenting the solution to the IETF
> 
> ...and conviencing the IETF it is a feasible solution
> 
> james
>