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 <0GNV00L052X2DI@eListX.com> (original mail from ietf-irnss-moderator@lists.elistx.com); Wed, 05 Dec 2001 03:15:02 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNT00301UIYVO@eListX.com> for ietf-irnss-moderator@lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Tue, 04 Dec 2001 11:16:10 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNT00301UIXVN@eListX.com> for ietf-irnss-moderator@lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com) ; Tue, 04 Dec 2001 11:16:09 -0500 (EST)
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNT00304UIXVK@eListX.com> for ietf-irnss-moderator@lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Tue, 04 Dec 2001 11:16:09 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNT00301UIWVI@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Tue, 04 Dec 2001 11:16:08 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNT00301UIWVH@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Tue, 04 Dec 2001 11:16:08 -0500 (EST)
Received: from nexus.spsoft.co.kr ([211.254.82.194]) by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0GNT00LP4UIUMX@eListX.com> for ietf-irnss@lists.elistx.com; Tue, 04 Dec 2001 11:16:08 -0500 (EST)
Received: (from newcat@localhost) by nexus.spsoft.co.kr (8.10.0/8.10.0) id fB4GDWM32368 for ietf-irnss@lists.elistx.com; Wed, 05 Dec 2001 01:13:32 +0900
Date: Wed, 05 Dec 2001 01:13:32 +0900
From: YangWoo Ko <newcat@peacenet.or.kr>
Subject: Re: "so-called" keyword and layer 3
In-reply-to: <087e01c17cd9$b3444db0$1119d73d@jamessonyvaio>
To: ietf-irnss@lists.elistx.com
Message-id: <20011205011332.A32163@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> <20011204234906.D30341@spsoft.co.kr> <087e01c17cd9$b3444db0$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>
Dear Jame Seng, On Tue, Dec 04, 2001 at 11:38:06PM +0800, James Seng/Personal wrote: > I think you got my point. IDN success or failure is really independent > of IRNSS. You got exactly one half of my point. I do not understand why you think "direct navigation" is only a business requirement. Then, what about "localization", "industry categories" ? Are they 100 % pure natural born technical IETF-style requirements ? I do not think so. All of them just reflects call from real (whether it means commercial or not) world. Please let me know your rationale in your heart which makes you neglect this requirement so easily. > 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. I am going to meet some of them soon. I will alert them to be prepared for this BoF and not to be a surprise show actors. Regards PS. Subscirber checking rule of this mailing list looks somewhat stricter than needed. ;-( -- /*------------------------------------------------ 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