Re: "so-called" keyword and layer 3

James Seng/Personal <jseng@pobox.org.sg> Sat, 08 December 2001 05:30 UTC

Return-Path: <ietf-irnss-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GO000F04FB4P1@eListX.com> (original mail from jseng@pobox.org.sg); Sat, 08 Dec 2001 00:30:40 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GO000F01FAWOM@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Sat, 08 Dec 2001 00:30:33 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GO000F01FAROB@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Sat, 08 Dec 2001 00:30:27 -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 <0GO000BHAFABR8@eListX.com> for ietf-irnss@lists.elistx.com; Sat, 08 Dec 2001 00:30:23 -0500 (EST)
Received: from jamessonyvaio (unknown [208.212.202.213]) by mail.i-dns.net (Postfix) with SMTP id 1D04BFFC03; Sat, 08 Dec 2001 13:26:55 +0800 (SGT)
Date: Sat, 08 Dec 2001 13:27:22 +0800
From: James Seng/Personal <jseng@pobox.org.sg>
Subject: Re: "so-called" keyword and layer 3
To: Yves Arrouye <yves@realnames.com>, 'YangWoo Ko' <newcat@spsoft.co.kr>, ietf-irnss@lists.elistx.com
Message-id: <0a9b01c17fa9$0a365ce0$2fc8020a@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=Windows-1252
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <7FC3066C236FD511BC5900508BAC86FE4D8196@trestles.internal.realnames.com>
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>

For what it worth, I do think there might be some value WIPO input would
be useful, at least the perspective of how they see "identifiers" (legal
terms, translated to "names" in engineer-talk).

But we should consider their requirements as we would for end-users.

-James Seng

> > If we do not give a specific group an authority to decide who can
get,
> > let me handle "overseer" issue in an extremely dirty way. Let's add
> > "overseer" as a facet. Then, we have { name string, industry
category,
> > country, overseer } tuple. If overseer is "trademark office" then
all
> > four attribute values are used to find a unique trademark from
trademark
> > db. Else if overseer is "none" (or "keyword" ?) then "industry
category"
> > field will be empty or not used even if supplied. Do you like it ?
>
> Well, I do not want to be the one to cause a dirty solution... My sole
point
> was that there is a manifest conflict between the desire not to
involve
> organizations like WIPO, and proposals that have been done and rely on
this
> organization's work. I don't think adding an overseer will help.
>
> YA
>
>