Message-Id: <6.2.1.2.2.20050708132837.04055660@mail.afrac.org>
Date: Fri, 08 Jul 2005 13:37:25 +0200
To: "Dylan N. Pierce" <dylanpierce@megared.net.mx>,
	Randy Presuhn <randy_presuhn@mindspring.com>, ltru@ietf.org
From: r&d afrac <rd@afrac.org>
Subject: Re: [Ltru] [psg.com #1061] eliminate (or proscribe) Private Use Tags
In-Reply-To: <42CE4312.2080203@megared.net.mx>
References: <T71fe6a8d870a01f0197f88@lonsmime01.rit.reuters.com>
	<42CD543E.1060304@megared.net.mx> <20050707185227.GD876@NYCMJCOWA2>
	<008d01c58353$6969e900$7f1afea9@oemcomputer>
	<42CE134B.1000009@megared.net.mx>
	<004601c58392$2d9795a0$7f1afea9@oemcomputer>
	<42CE4312.2080203@megared.net.mx>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 
Precedence: list
Sender: ltru-bounces@lists.ietf.org
Errors-To: ltru-bounces@lists.ietf.org

At 11:10 08/07/2005, Dylan N. Pierce wrote:
>Randy Presuhn wrote:
>>Would a stronger version of this (or the following paragraphs address the
>>concerns?  If so, proposed text would be appreciated.
>
>Another way of looking at the concern.

is to respect the charter and retrocompatibility with RFC 3066. We 
extensively use and plan to use "x-tags".

The way we see (from our perspectibe) it is that x-tags are the standard 
format:
- "x-"    is the language tag indicating sequence and we experimentaly use 
<x-en> to signify that the text enters/finish English </x-en>
- "xn--" is an extended name (punycoded name) (we experimentaly use <xn--> 
and </xn--> to mean that the text was punny coded and to be restored)
The Draft sequence are default special cases.

Obviously if "x-" retrocompabilty was not assured, we would have no more 
problem in introducing "x-tags" as a separate taging system.
jfc


_______________________________________________
Ltru mailing list
Ltru@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/ltru