Return-Path: Received: from murder ([unix socket]) by eikenes.alvestrand.no (Cyrus v2.2.8-Mandrake-RPM-2.2.8-4.2.101mdk) with LMTPA; Sun, 11 Sep 2005 15:22:30 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 9DE03320097 for ; Sun, 11 Sep 2005 15:22:30 +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 03785-10 for ; Sun, 11 Sep 2005 15:22:23 +0200 (CEST) X-Greylist: domain auto-whitelisted by SQLgrey-1.4.8 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by eikenes.alvestrand.no (Postfix) with ESMTP id 2DB12320095 for ; Sun, 11 Sep 2005 15:22:23 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EERjl-0003aM-Bo; Sun, 11 Sep 2005 09:19:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EERjc-0003YP-Fk for ltru@megatron.ietf.org; Sun, 11 Sep 2005 09:19:09 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02887 for ; Sun, 11 Sep 2005 09:18:52 -0400 (EDT) Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EERnR-0004LX-2R for ltru@ietf.org; Sun, 11 Sep 2005 09:23:02 -0400 Received: from ver78-2-82-241-91-24.fbx.proxad.net ([82.241.91.24] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1EERjL-0005U6-Uo; Sun, 11 Sep 2005 06:18:48 -0700 Message-Id: <6.2.3.4.2.20050911144508.047be0f0@mail.afrac.org> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Sun, 11 Sep 2005 14:55:26 +0200 To: Frank Ellermann , ltru@ietf.org From: r&d afrac Subject: Re: [Ltru] Re: The LTRU initialization document In-Reply-To: <43241D6D.6BCD@xyzzy.claranet.de> References: <02BD58E66D8134A92F365882@scan.jck.com> <013101c5b550$313fc0c0$030aa8c0@DEWELL> <20050910021615.GK7608@NYCMJCOWA2> <005201c5b5c9$efe5dcc0$7f1afea9@oemcomputer> <3420D2009FB39F5A23C2B5DE@scan.jck.com> <432394E1.5999@xyzzy.claranet.de> <77AAF63860A1726F496DCB4B@scan.jck.com> <43241D6D.6BCD@xyzzy.claranet.de> 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 - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - afrac.org X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Cc: iesg@iesg.org X-BeenThere: ltru@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Language Tag Registry Update working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ltru-bounces@ietf.org Errors-To: ltru-bounces@ietf.org X-Virus-Scanned: by amavisd-new at alvestrand.no At 14:05 11/09/2005, Frank Ellermann wrote: >Any solution designed to exist in parallel with 3066 would be >completely different, because it's not forced to be backwards compatible. This is uncorrect. There is a total confusion between backward compatibility and conformance. Any new format including the RFC 3066 format will be backward compatible. The Draft demands for ever new releases to stay compatible only with RFC 3066, and invents new constraints to that end. I note that this "backward compatibility" which excludes the support of most of user needs, includes the introduction of the support of "scripts" , interestingly enough a word not even used by RFC 3066. jfc _______________________________________________ Ltru mailing list Ltru@ietf.org https://www1.ietf.org/mailman/listinfo/ltru