Message-Id: <6.2.1.2.2.20050512014536.0459d930@mail.jefsey.com>
Date: Thu, 12 May 2005 01:55:10 +0200
To: "Addison Phillips" <addison.phillips@quest.com>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
Subject: RE: [Ltru] Re: [psg.com #954] all aliases must be equally supported
In-Reply-To: <634978A7DF025A40BFEF33EB191E13BC0B5A6CFC@irvmbxw01.quest.c
 om>
References: <634978A7DF025A40BFEF33EB191E13BC0B5A6CFC@irvmbxw01.quest.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

On 01:22 12/05/2005, Addison Phillips said:
>Uh... The items in the registry all have dates attached to them. And they 
>are in their own canonical table over which the registry draft has 
>ironclad control. We are discussing rules for the maintenance of canonical 
>values and stability of those values in that registry. The use of ISO 3166 
>to provide some of the values in that table does not mean that the 
>registry cedes control to the ISO 3166 MA. Defining rules for how the 
>registry tracks ISO 3166 is what we are about here, since creating 
>separate standards for these things is unappealing.

Can you document the interest of a canonical table over which you want to 
have ironclad control? You create there your own standard. What for? Your 
job is not to maintain a canonical base but to tell users what a code used 
at a given date meant in the ISO table. It could change every year, you do 
not mind. Not your concern. Your concern (look at the charter) is to make 
sure the users know what is each subtag in the format and reach the proper 
version value. The registry does not cede control to the ISO 3166 MA, the 
ISO 3166 MA _HAS_ control, the registry just copy it in a readable form for 
your usage. Otherwise it conflicts.
jfc



_______________________________________________
Ltru mailing list
Ltru@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/ltru