Re: "so-called" keyword and layer 3

YangWoo Ko <newcat@spsoft.co.kr> Wed, 05 December 2001 07:45 UTC

Return-Path: <ietf-irnss-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNV00K011J4ZE@eListX.com> (original mail from ietf-irnss-moderator@lists.elistx.com); Wed, 05 Dec 2001 02:45:04 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNU00K01ZOMHX@eListX.com> for ietf-irnss-moderator@lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Wed, 05 Dec 2001 02:05:10 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNU00K01ZOMHW@eListX.com> for ietf-irnss-moderator@lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com) ; Wed, 05 Dec 2001 02:05:10 -0500 (EST)
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNU00K04ZOLHR@eListX.com> for ietf-irnss-moderator@lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Wed, 05 Dec 2001 02:05:09 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNU00K01ZOKHN@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Wed, 05 Dec 2001 02:05:08 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GNU00K01ZOJHM@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Wed, 05 Dec 2001 02:05:08 -0500 (EST)
Received: from nexus.spsoft.co.kr ([211.254.82.194]) by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0GNU00J36ZOIXU@eListX.com> for ietf-irnss@lists.elistx.com; Wed, 05 Dec 2001 02:05:07 -0500 (EST)
Received: (from newcat@localhost) by nexus.spsoft.co.kr (8.10.0/8.10.0) id fB572XT10281 for ietf-irnss@lists.elistx.com; Wed, 05 Dec 2001 16:02:33 +0900
Date: Wed, 05 Dec 2001 16:02:33 +0900
From: YangWoo Ko <newcat@spsoft.co.kr>
Subject: Re: "so-called" keyword and layer 3
In-reply-to: <09de01c17d1b$c072c2e0$1119d73d@jamessonyvaio>
To: ietf-irnss@lists.elistx.com
Message-id: <20011205160233.E8623@spsoft.co.kr>
MIME-version: 1.0
Content-type: text/plain; charset="euc-kr"
Content-disposition: inline
User-Agent: Mutt/1.3.23i
References: <7FC3066C236FD511BC5900508BAC86FE4364AC@trestles.internal.realnames.com> <09de01c17d1b$c072c2e0$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>

(sorry for duped messages)

On Wed, Dec 05, 2001 at 07:30:54AM +0800, James Seng/Personal wrote:
> So, the question I am asking is why people squeeze L2 & L3 together?
> There must be a technical reason or a user requirements which resultant
> in the business decision right?
> 
> But I think you answered that :-) I am interested to know if that is the
> same for Korea.

As you explicitly mention "korea", I can not but answer. ;-)

There is a working group in Korea to deal with keyword. At this working
group, we have been focused on requirements from user's point of view.
>From ordinary user's point of view, they do not care what L2 / L3 is.
One thing which was very clear for us is that there are already big and
doing-well commercial players in directory / search area like Yahoo and
Google. And another point is that in the spectrum from IP address, machine
(or Latin-script-friendly-human) friendly domain name through what people 
get by entering names (or phrases) into directory / search service 
providers, there are missing bands. Especially, due to the fact that we 
will not be able to have fully internationalized domain name ( ML.ML.ML ) 
soon, desire to overcome deficiency has been concentrated on band which 
is very near to domain name band.

I am neither against L2 nor L3. I just want them be flexible (or strict ?)
enough to support or to mitigate these unintended fevers in Korea.

With my best regards

-- 
/*------------------------------------------------
YangWoo Ko : newcat@spsoft.co.kr
We Invent Enterprise Software Solutions
and Make You Secure & Powerful.
------------------------------------------------*/