Message-Id: <6.2.1.2.2.20050619182551.057729a0@mail.afrac.org>
Date: Wed, 22 Jun 2005 13:00:33 +0200
To: mentors@dot-root.com
From: r&d afrac <rd@afrac.org>
In-Reply-To: <634978A7DF025A40BFEF33EB191E13BC0BD55DDE@irvmbxw01.quest.c
 om>
References: <634978A7DF025A40BFEF33EB191E13BC0BD55DDE@irvmbxw01.quest.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: langtags@afrac.org, ltru@ietf.org
Subject: [Ltru] QED
Precedence: list
Sender: ltru-bounces@lists.ietf.org
Errors-To: ltru-bounces@lists.ietf.org

At 17:34 19/06/2005, Addison Phillips wrote:
>I'm not feeding the trolls, no matter what they choose to call themselves.

Dear Dot-Rooters,
I told you the way you would be accepted ... QED.

Further to the technical concertation meeting you invited me on Monday, I 
wish to repeat:
1. thank you for assuming my relay for a few weeks and even participating.
2. I agree with your responsible attitude towards Addison. An authors' 
trolling does affect his documents.
3. AFRAC has no objection so far to the WG-ltru Chairs. They may play 
wisely due to circumstances and authors (see above).

I also confirm that:
- AFRAC will present a Draft if the debate over the Charter is not carried 
on, or if the results stay negative for Internet users.
- this Draft will be introduced through the WG-ltru if possible.
- http://rfc3066.org has been activated. It is a site for all.

The AFRAC positions I documented:

- IETF/AFRAC/INTLNET are involved in networking, not in 
lingustic/terminology. A language is a relation protocol within a space of 
exchanges. A langtag is a possible code for an SoE. We need to be 
consistant with ISO 11179 as an SoE can correlate with any standard.
- RFC 3066's simplicity is to be preserved and increased. Current Draft's 
is "unreadable" (we have to propose a langtag ... :-)).
- this way all the documents, works and RFCs which refer to RFC 3066/BC 47 
will be respected.
- if it does not go through we will publish a Draft/TNS on x-tags (Mr. 
Charles: we will warn every developper to support long private subtags).
- every solution is to be ISO 11179, ISO 639-1/2/3/4/5/6 and ISO 3166-1/2 
conformant..
- it will conform to ISO 15924 as per the directions given by ISO 639-4
- E.164, X.121, N.49 and INTLFILE will be supported too.
- we will support all the experimentation charters you presented. However 
we need you to proceed by the book: please document the status of your 
generic NIC project - we need to address the externet registry first. 
Gositer 0.3 should be ready as far as I am concerned (the current AFRAC 
site is built with it).
- we expect to port the INTLFILE to five hexa codes by mid-August. I still 
wait for the Chinese root elements from MINC.
- we disapprove the idea of setting-up an ietf-languages@rfc3066.org 
mailing list except if this is an experimental list, within the framework 
of an rfc3066.org Draft.

A specialised face to face meeting is called on Tuesday September 6 (or 
13th?) in Versailles over the RFC 3066 drafts, the x-tags format, their 
IPv6 access grids, the metalang metamodel, the report on the dot-root 
testing the Varsaw meeting. If you have other topics to rise, please advise 
Intlnet secretariat. Members of the WG-ltru will be welcome if.

I am not sure I am in Paris at the time of the IETF meeting and I doubt 
AFRAC will want to spend $ 500 for it. I suppose I will attend one or two 
Guest Events. We could propose a WG-ltru F2F meeting as a diner in Paris or 
Versailles if some are interested (and here in first part of August?) 
Pascal: we could do something in Luxembourg after the ccTLD Meeting?

jfc

                  


_______________________________________________
Ltru mailing list
Ltru@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/ltru