Re: "so-called" keyword and layer 3

James Seng/Personal <jseng@pobox.org.sg> Tue, 04 December 2001 15:41 UTC

Return-Path: <ietf-irnss-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNT00204SWIX8@eListX.com> (original mail from jseng@pobox.org.sg); Tue, 04 Dec 2001 10:41:06 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNT00201SWHX6@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Tue, 04 Dec 2001 10:41:06 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNT00201SWHX5@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Tue, 04 Dec 2001 10:41:05 -0500 (EST)
Received: from mail.i-dns.net (mail.i-dns.net [203.126.116.228]) by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0GNT0016KSW4D4@eListX.com> for ietf-irnss@lists.elistx.com; Tue, 04 Dec 2001 10:41:05 -0500 (EST)
Received: from jamessonyvaio (pl048.nas312.n-yokohama.nttpc.ne.jp [210.165.193.48]) by mail.i-dns.net (Postfix) with SMTP id 4D659FFC17; Tue, 04 Dec 2001 23:37:49 +0800 (SGT)
Date: Tue, 04 Dec 2001 23:38:06 +0800
From: James Seng/Personal <jseng@pobox.org.sg>
Subject: Re: "so-called" keyword and layer 3
To: YangWoo Ko <newcat@peacenet.or.kr>
Cc: ietf-irnss@lists.elistx.com
Message-id: <087e01c17cd9$b3444db0$1119d73d@jamessonyvaio>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
Content-type: text/plain; charset=ks_c_5601-1987
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <20011204144621.A24483@spsoft.co.kr> <055601c17ccb$e99891e0$1119d73d@jamessonyvaio> <20011204234906.D30341@spsoft.co.kr>
List-Owner: <mailto:ietf-irnss-help@lists.elistx.com>
List-Post: <mailto:ietf-irnss@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:ietf-irnss-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:ietf-irnss-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-irnss>
List-Help: <http://lists.elistx.com/elists/admin.shtml>, <mailto:ietf-irnss-request@lists.elistx.com?body=help>
List-Id: <ietf-irnss.lists.elistx.com>

Ko,

I think you got my point. IDN success or failure is really independent
of IRNSS. We do know that whatever the case, there are certain
limitation of IDN whereby IRNSS is designed to solve.

If there are Korean keyword providers (and there are many!) who have
technical requirements to bring forward, please help them to bring them
to this group. I undestand communication is going to be a problem but
that is where you can help. I am sure John and others here are happy to
hear them.

John's draft is unique in the sense that there is a "business model"
section in it but it is definately not a norm. But lets try to keep
business issues out of it unless of course John feels that he wants
feedback on his "business plan section". If that is the case, I have no
comments :-)

-James Seng

----- Original Message -----
From: "YangWoo Ko" <newcat@peacenet.or.kr>
To: "James Seng/Personal" <jseng@pobox.org.sg>
Cc: <ietf-irnss@lists.elistx.com>
Sent: Tuesday, December 04, 2001 10:49 PM
Subject: Re: "so-called" keyword and layer 3


> On Tue, Dec 04, 2001 at 09:59:23PM +0800, James Seng/Personal wrote:
> > I believe the norm of the IETF has not take existing business
> > requirements into consideration. Their technical input, however,
would
> > be appreciated.
>
> Dear Jame Seng,
>
> Thank you for comment. I did not mention "direct navigaion" as a
business
> requirement. This is required for Klensin's search model to fulfill
its
> basic purpose - "Save our DNS ! Let it work and be used as it was
designed
> for !"
>
> There have been several approaches to fill up the difference between
DNS
> itself and what (non Latin script) people expect DNS to be. As there
was
> no standard to address this issue, commercial companies jumped into
this
> area to mine gold. These miners happened to (under)mine DNS as a side
> effect. So, we are hearing emergency call from DNS related areas. IDN
and
> Klensin's search is going to answer this call.
>
> If IDN WG succeeded in standardization and we suceeded in deploying
it,
> (personally I really hope so) it could relieve this burden and
Klensin's
> search would concentrate on other issues. But, when considering
Klensin's
> search, we would better not assume so many things. So, I still think
that
> some name service which supports "direct navigation" and hence serves
as
> an alternative to "internationalized network resource name" is needed
> to lessen unnecessary and even harmful overload on DNS and to prevent
> Internet be tangled along boarders of "so-called" keyword service
> providers.
>
> My best regards
>
> --
> /*------------------------------------------------
> YangWoo Ko : newcat@peacenet.or.kr
> PeaceNet / Director
> ------------------------------------------------*/