Re: "so-called" keyword and layer 3

YangWoo Ko <newcat@peacenet.or.kr> Wed, 05 December 2001 08:15 UTC

Return-Path: <ietf-irnss-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNV00L092X3DI@eListX.com> (original mail from ietf-irnss-moderator@lists.elistx.com); Wed, 05 Dec 2001 03:15:03 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNT00101QO1ZR@eListX.com> for ietf-irnss-moderator@lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Tue, 04 Dec 2001 09:52:49 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNT00101QO0ZQ@eListX.com> for ietf-irnss-moderator@lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com) ; Tue, 04 Dec 2001 09:52:48 -0500 (EST)
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNT00104QO0ZN@eListX.com> for ietf-irnss-moderator@lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Tue, 04 Dec 2001 09:52:48 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNT00101QNZZL@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Tue, 04 Dec 2001 09:52:48 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNT00101QNZZK@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Tue, 04 Dec 2001 09:52:47 -0500 (EST)
Received: from nexus.spsoft.co.kr ([211.254.82.194]) by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0GNT0012JQNXD4@eListX.com> for ietf-irnss@lists.elistx.com; Tue, 04 Dec 2001 09:52:47 -0500 (EST)
Received: (from newcat@localhost) by nexus.spsoft.co.kr (8.10.0/8.10.0) id fB4En6a31583; Tue, 04 Dec 2001 23:49:06 +0900
Date: Tue, 04 Dec 2001 23:49:06 +0900
From: YangWoo Ko <newcat@peacenet.or.kr>
Subject: Re: "so-called" keyword and layer 3
In-reply-to: <055601c17ccb$e99891e0$1119d73d@jamessonyvaio>
To: James Seng/Personal <jseng@pobox.org.sg>
Cc: ietf-irnss@lists.elistx.com
Message-id: <20011204234906.D30341@spsoft.co.kr>
MIME-version: 1.0
Content-type: text/plain; charset=euc-kr
Content-disposition: inline
User-Agent: Mutt/1.3.23i
References: <20011204144621.A24483@spsoft.co.kr> <055601c17ccb$e99891e0$1119d73d@jamessonyvaio>
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>

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
------------------------------------------------*/