Re: "so-called" keyword and layer 3

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

Return-Path: <ietf-irnss-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNT00104OC38Z@eListX.com> (original mail from jseng@pobox.org.sg); Tue, 04 Dec 2001 09:02:27 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNT00101OC18T@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Tue, 04 Dec 2001 09:02:26 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNT00101OC08R@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Tue, 04 Dec 2001 09:02:24 -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 <0GNT00LDDOBOMX@eListX.com> for ietf-irnss@lists.elistx.com; Tue, 04 Dec 2001 09:02:24 -0500 (EST)
Received: from jamessonyvaio (pl069.nas312.n-yokohama.nttpc.ne.jp [210.165.193.69]) by mail.i-dns.net (Postfix) with SMTP id 090C5FFC22; Tue, 04 Dec 2001 21:59:07 +0800 (SGT)
Date: Tue, 04 Dec 2001 21:59:23 +0800
From: James Seng/Personal <jseng@pobox.org.sg>
Subject: Re: "so-called" keyword and layer 3
To: YangWoo Ko <newcat@peacenet.or.kr>, ietf-irnss@lists.elistx.com
Message-id: <055601c17ccb$e99891e0$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>
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 believe the norm of the IETF has not take existing business
requirements into consideration. Their technical input, however, would
be appreciated.

-James Seng

----- Original Message -----
From: "YangWoo Ko" <newcat@peacenet.or.kr>
To: <ietf-irnss@lists.elistx.com>
Sent: Tuesday, December 04, 2001 1:46 PM
Subject: "so-called" keyword and layer 3


> Dear John Klensin and others,
>
> Whether I like it or not, I can not but admit that one of largest
> driving forces on naming service (or business) area is keyword
service.
> John Klensin suggested that "adapting keyword systems to operate
> locally and as part of the third sublayer model proposed here would
> appear to be the best way forward for such systems." This makes sense
> only when the strength of keyword service is localization. But,
> all folks from keyword service busness, eg. realname, netpia, think
> that "direct navigation" - which, in turn, requires lookup or
uniqueness
> of name within given context -  is also a crucial point.
>
> Is there any way to harmonize these two requirements - localization
> and direct navigation - in third sublayer ?
>
> My best regards
>
> --
> /*------------------------------------------------
> YangWoo Ko : newcat@peacenet.or.kr
> PeaceNet / Director
> ------------------------------------------------*/