"so-called" keyword and layer 3
YangWoo Ko <newcat@peacenet.or.kr> Tue, 04 December 2001 11:55 UTC
Return-Path: <ietf-irnss-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id
<0GNT00M01IFQDW@eListX.com> (original mail from
ietf-irnss-moderator@lists.elistx.com); Tue, 04 Dec 2001 06:55:02 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025
#44856) id <0GNT00I011HLKP@eListX.com> for
ietf-irnss-moderator@lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com);
Tue, 04 Dec 2001 00:48:57 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025
#44856) id <0GNT00I011HLKO@eListX.com> for
ietf-irnss-moderator@lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com) ;
Tue, 04 Dec 2001 00:48:57 -0500 (EST)
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id
<0GNT00I041HKKL@eListX.com> for ietf-irnss-moderator@lists.elistx.com (ORCPT
ietf-irnss@lists.elistx.com); Tue, 04 Dec 2001 00:48:56 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025
#44856) id <0GNT00I011HKKJ@eListX.com> for ietf-irnss@elist.lists.elistx.com
(ORCPT ietf-irnss@lists.elistx.com); Tue, 04 Dec 2001 00:48:56 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025
#44856) id <0GNT00I011HJKI@eListX.com> for ietf-irnss@elist.lists.elistx.com
(ORCPT ietf-irnss@lists.elistx.com); Tue, 04 Dec 2001 00:48:55 -0500 (EST)
Received: from nexus.spsoft.co.kr ([211.254.82.194]) by eListX.com (PMDF
V6.0-025 #44856) with ESMTP id <0GNT00G8G1HHXH@eListX.com> for
ietf-irnss@lists.elistx.com; Tue, 04 Dec 2001 00:48:55 -0500 (EST)
Received: (from newcat@localhost) by nexus.spsoft.co.kr (8.10.0/8.10.0) id
fB45kL024928 for ietf-irnss@lists.elistx.com; Tue, 04 Dec 2001 14:46:21 +0900
Date: Tue, 04 Dec 2001 14:46:21 +0900
From: YangWoo Ko <newcat@peacenet.or.kr>
Subject: "so-called" keyword and layer 3
To: ietf-irnss@lists.elistx.com
Message-id: <20011204144621.A24483@spsoft.co.kr>
MIME-version: 1.0
Content-type: text/plain; charset=euc-kr
Content-disposition: inline
User-Agent: Mutt/1.3.23i
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>
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 ------------------------------------------------*/
- reading...? bmanning
- Re: reading...? Michael Mealling
- Re: "so-called" keyword and layer 3 James Seng/Personal
- Re: reading...? John C Klensin
- RE: "so-called" keyword and layer 3 Yves Arrouye
- RE: "so-called" keyword and layer 3 Yves Arrouye
- Keywords, direct navigation, and search layer 2 (… John C Klensin
- Re: "so-called" keyword and layer 3 YangWoo Ko
- RE: "so-called" keyword and layer 3 Yves Arrouye
- RE: "so-called" keyword and layer 3 Nicolas Popp
- Re: "so-called" keyword and layer 3 Eric Brunner-Williams in Portland Maine
- RE: "Layering" terminology (was: Re: "so-called" … Keith Teare
- "Layering" terminology (was: Re: "so-called" keyw… John C Klensin
- RE: "so-called" keyword and layer 3 John C Klensin
- RE: "so-called" keyword and layer 3 Nicolas Popp
- Re: "so-called" keyword and layer 3 YangWoo Ko
- Re: "so-called" keyword and layer 3 James Seng/Personal
- Re: "so-called" keyword and layer 3 Maynard Kang
- Re: "so-called" keyword and layer 3 YangWoo Ko
- Re: "so-called" keyword and layer 3 YangWoo Ko
- Re: "so-called" keyword and layer 3 YangWoo Ko
- Re: "so-called" keyword and layer 3 YangWoo Ko
- RE: "so-called" keyword and layer 3 John C Klensin
- Re: "so-called" keyword and layer 3 John C Klensin
- Re: "so-called" keyword and layer 3 James Seng/Personal
- RE: "so-called" keyword and layer 3 Nicolas Popp
- Re: "so-called" keyword and layer 3 James Seng/Personal
- Re: "so-called" keyword and layer 3 James Seng/Personal
- Re: "so-called" keyword and layer 3 Eric Brunner-Williams in Portland Maine
- Re: "so-called" keyword and layer 3 James Seng/Personal
- "so-called" keyword and layer 3 YangWoo Ko