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;
	 Sat, 02 Apr 2005 16:24:11 +0200
X-Sieve: CMU Sieve 2.2
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id BF22A61B41
	for <harald@alvestrand.no>; Sat,  2 Apr 2005 16:24:11 +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 13355-04 for <harald@alvestrand.no>;
 Sat,  2 Apr 2005 16:24:08 +0200 (CEST)
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by eikenes.alvestrand.no (Postfix) with ESMTP id AA32C61AD5
	for <harald@alvestrand.no>; Sat,  2 Apr 2005 16:24:07 +0200 (CEST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHjXD-0007kN-UA; Sat, 02 Apr 2005 09:23:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DHjXC-0007kI-D8
	for ltru@megatron.ietf.org; Sat, 02 Apr 2005 09:23:34 -0500
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 JAA24722
	for <ltru@ietf.org>; Sat, 2 Apr 2005 09:23:32 -0500 (EST)
Received: from [63.247.76.194] (helo=montage.altserver.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHjej-0002pR-79
	for ltru@ietf.org; Sat, 02 Apr 2005 09:31:22 -0500
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 1DHjX1-0003Rd-FM; Sat, 02 Apr 2005 06:23:24 -0800
Message-Id: <6.1.2.0.2.20050402114743.03713610@mail.jefsey.com>
X-Sender: jefsey+jefsey.com@mail.jefsey.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Sat, 02 Apr 2005 16:23:12 +0200
To: "Doug Ewell" <dewell@adelphia.net>,
	"LTRU Working Group" <ltru@ietf.org>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
Subject: Re: [Ltru] Re: Proposed changes to region subtags
In-Reply-To: <00c401c53754$cdfe41e0$030aa8c0@DEWELL>
References: <20050401205735.MVSI2135.mta2.adelphia.net@megatron.ietf.org>
	<00c401c53754$cdfe41e0$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 - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
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 09:23 02/04/2005, Doug Ewell wrote:
>Addison Phillips <addison dot phillips at quest dot com> wrote:
>No objection at all.  I'm ready with record-jar any time you folks are.
>I would appreciate some guidance on the exact flavor of record-jar that
>people want.  There are a few choices to be made:

I need to translate this to our system management language through a simple 
C program.

>- max line length (80, 72, etc.)

No special requirement.

>- character(s) used for comments ("%%" versus "#")

"%%" could help to transliterate it to "//" while "#" may happen to be used 
elsewhere.

>- line breaking convention (backslash-newline, newline-space, etc.)

No special need.

> > The additional rule you suggest would be, btw:
> >
> > 3. Create an M49-based registration for any 3166 code that was
> > withdrawn after Date A and subsequently assigned a new value before
> > Date B (in Cowan's terms).
>
>I'm glad to see this (and the other two rules) expressed as general
>rules, not special exceptions.

Our intent is to add the expiration date of a code to the concerned code 
element. If you have the information very good. We currently miss the 
3166-2 revisions. But it is likely that 3166-2 will not be muched used in 
APMD draft context.
jfc


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