Message-Id: <6.2.1.2.2.20050716021707.0544ed60@mail.afrac.org>
Date: Sat, 16 Jul 2005 02:46:48 +0200
To: Karen_Broome@spe.sony.com,
	"Peter Constable" <petercon@microsoft.com>
From: r&d afrac <rd@afrac.org>
Subject: RE: [Ltru] Last call: IANA adaptation of the UN disclaimer
In-Reply-To: <OFB0140EA9.E38047C8-ON8825703F.007D62A9-8825703F.007E3E13@
	spe.sony.com>
References: <OFB0140EA9.E38047C8-ON8825703F.007D62A9-8825703F.007E3E13@spe.sony.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ltru@ietf.org
Precedence: list
Sender: ltru-bounces@lists.ietf.org
Errors-To: ltru-bounces@lists.ietf.org

At 00:55 16/07/2005, Karen_Broome@spe.sony.com wrote:
>Yes, I think Randy's findings on the lack of this type of text in other
>registries validates our initial gut instinct that this was a political
>rather than technical statement

Dear Karen,
The matter of the RFC 3066 is political. And it is qualified as such. The 
question is: is it technically necessary. The response is obviously "no". 
Multiple specialised tags would far better address the need. The langtag 
only introduce an arbitrary correlation not wanted by the ISO Members.

The IETF system makes that in the WG you cannot remove text, just add text. 
Since I cannot remove the whole text, I just keep proposing correct things. 
When they oppose they build a good case to refuse the whole thing 
afterward. I am sorry for that, but there is no other way foreseen by the 
Internet standard process to kill a detrimental proposition.

>-- whether we generally agree with its
>content or not. If there is a disclaimer to be made,

There is a disclaimer to be made. No one expect it to be perfect (see next 
comment). My target was just to illustrate the doctrine of this WG.  This 
WG documents an absolute Registry (the Registries quoted by Randy are 
absolute: they create their codes). Randy, Peter and you show that you do 
not care about the copyrights of ISO and UN. As if you were removing the 
copyright mentions when you paste an Open Source piece of code.

>I think that IANA/ICANN is the one to draft the text and perhaps it should 
>be in the context of all registries managed by the organization.

Do not worry: this is exactly what will happen. The Registry will be 
published by the new IANA director (Doug Barton is quitting) under legal 
responsibility of ICANN and ISOC (IASA). So, there is a long, long legal 
debate ahead. This particular response about the UN disclaimer will 
probably be an important point for the lawyers of IANA, ISOC and ISO.
jfc


_______________________________________________
Ltru mailing list
Ltru@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/ltru