Return-Path: <ltru-bounces@lists.ietf.org>
Received: from murder ([unix socket])
	 by eikenes.alvestrand.no (Cyrus v2.2.8-Mandrake-RPM-2.2.8-4.2.101mdk) with LMTPA;
	 Mon, 04 Apr 2005 01:24:20 +0200
X-Sieve: CMU Sieve 2.2
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id D0B6261B5B
	for <harald@alvestrand.no>; Mon,  4 Apr 2005 01:24:20 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
 by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 10089-05 for <harald@alvestrand.no>;
 Mon,  4 Apr 2005 01:24:16 +0200 (CEST)
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 10F0661B46
	for <harald@alvestrand.no>; Mon,  4 Apr 2005 01:24:15 +0200 (CEST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DIERC-0005bo-9X; Sun, 03 Apr 2005 19:23:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DIERA-0005bj-7x
	for ltru@megatron.ietf.org; Sun, 03 Apr 2005 19:23:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06530
	for <ltru@ietf.org>; Sun, 3 Apr 2005 19:23:19 -0400 (EDT)
Received: from [63.247.76.195] (helo=montage.altserver.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DIEYv-0007uY-PP
	for ltru@ietf.org; Sun, 03 Apr 2005 19:31:27 -0400
Received: from lns-p19-1-idf-82-251-95-81.adsl.proxad.net ([82.251.95.81]
	helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44)
	id 1DIEQw-0005iW-QE; Sun, 03 Apr 2005 16:23:11 -0700
Message-Id: <6.1.2.0.2.20050403230438.02f6eb60@mail.jefsey.com>
X-Sender: jefsey+jefsey.com@mail.jefsey.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Mon, 04 Apr 2005 01:23:02 +0200
To: "Doug Ewell" <dewell@adelphia.net>,
	"LTRU Working Group" <ltru@ietf.org>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
Subject: Re: [Ltru] Re: Registry in record-jar format
In-Reply-To: <001101c53888$27ca3c40$030aa8c0@DEWELL>
References: <20050403160207.FFYP2140.mta3.adelphia.net@megatron.ietf.org>
	<001101c53888$27ca3c40$030aa8c0@DEWELL>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: 
X-BeenThere: ltru@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Language Tag Registry Update working group discussion list
	<ltru.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>,
	<mailto:ltru-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@lists.ietf.org>
List-Help: <mailto:ltru-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>,
	<mailto:ltru-request@lists.ietf.org?subject=subscribe>
Sender: ltru-bounces@lists.ietf.org
Errors-To: ltru-bounces@lists.ietf.org
X-Virus-Scanned: amavisd-new at alvestrand.no

At 22:03 03/04/2005, Doug Ewell wrote:
>JFC (Jefsey) Morfin <jefsey at jefsey dot com> wrote:
>
> > The first thing you are to publish in a compilation - as in every open
> > source code - is the list of your sources and of their intellectual
> > property rights or acknowledgements. So everyone can make its own
> > compilation.
>
>I thought one of the things we wanted to avoid was having everyone make
>his own compilation.  That's how we end up with mismatched versions and
>incompatible implementations.

Dear Doug,
the Internet is the "adherence of the people to the network of the people 
by the people". There is no "we" able to decide anything. You can only 
convince by the quality, the usefulness and the availability of the service 
you propose. Consensus is not a rule, it is a prerequisite which does not 
give any warranty of success ("not all RFCs become standards"). Looking for 
consensus is only an incentive to be good and professional. The flaw is to 
ask friends on a list "what do you want" instead of "what will the users 
want (to pay for?)" (and to try to ban those disagreeing with your own 
vision!). There is a basic network law: everything permitted by the code 
which may hurt, be fun, make money, or be useful to some will be attempted 
and may develop. Another on a closed or global network is "everything 
another member thinks bad for him is bad for you".

Obviously everyone who is not happy with yours will do his own compilation 
(I only wait for yours to know if I can make it compatible with the ones I 
make for many years) - this is the very nature of competition and of 
networking!  This is why you have two priorities:
- make me happy enough so I do not develop my own solution and I can use yours
- if I continue developing mine our solutions stay compatible with all the 
others. This is the only interest of the IANA registration. This is why I 
keep asking about the target.

The target cannot be to build and maintain a table avoiding mismatched 
versions and incompatible implementations controlled by a lawyer and 
enforced by a cop. It can only be to propose practices which will preserve 
end to end compatibility between the different implementations and versions 
which may attract the users.

I know, multilateral, intelligent and distributed networking calls for more 
skills, vision and work than for the prototype unilateral, default and 
centralized network.

jfc


_______________________________________________
Ltru mailing list
Ltru@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/ltru