[Ltru] Re: Remove extlang from ABNF?

"Frank Ellermann" <nobody@xyzzy.claranet.de> Tue, 11 December 2007 17:54 UTC

Return-path: <ltru-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J29JN-0008F9-0R; Tue, 11 Dec 2007 12:54:29 -0500
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1J29JL-0008F4-U3 for ltru-confirm+ok@megatron.ietf.org; Tue, 11 Dec 2007 12:54:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J29JL-0008Ev-K3 for ltru@lists.ietf.org; Tue, 11 Dec 2007 12:54:27 -0500
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J29JJ-0005za-D9 for ltru@lists.ietf.org; Tue, 11 Dec 2007 12:54:27 -0500
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1J29Be-0000KE-UN for ltru@lists.ietf.org; Tue, 11 Dec 2007 17:46:30 +0000
Received: from c-134-88-89.hh.dial.de.ignite.net ([62.134.88.89]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ltru@lists.ietf.org>; Tue, 11 Dec 2007 17:46:30 +0000
Received: from nobody by c-134-88-89.hh.dial.de.ignite.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ltru@lists.ietf.org>; Tue, 11 Dec 2007 17:46:30 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ltru@lists.ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Tue, 11 Dec 2007 18:37:52 +0100
Organization: <http://purl.net/xyzzy>
Lines: 26
Message-ID: <fjmhpl$41j$1@ger.gmane.org>
References: <E1J01vI-0003cW-Rd@megatron.ietf.org><019601c83818$b06c3070$6601a8c0@DGBP7M81><DDB6DE6E9D27DD478AE6D1BBBB83579561E51429AA@NA-EXMSG-C117.redmond.corp.microsoft.com> <DDB6DE6E9D27DD478AE6D1BBBB83579561E51429AA@NA-EXMSG-C117.redmond.corp.microsoft.com> <6.0.0.20.2.20071211163740.0a090850@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: c-134-88-89.hh.dial.de.ignite.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1914
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc:
Subject: [Ltru] Re: Remove extlang from ABNF?
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Errors-To: ltru-bounces@ietf.org

Martin Duerst wrote:

> As an extreme example, such a tag may by accident be
> part of a document used for managing a nuclear plant.

Something's wrong with this installation if it depends
on the syntactical well-formedness of <obs-extlang>.

And you could use the same example with a "malicious"
<obs-extlang>, when it survives a syntax check still
allowing non-existent <obs-extlang>s as "well formed".

> With a software update, the document could suddently
> become non-conforming, triggering some error.

It might as well trigger an error in lazy 4646bis code
not prepared to support any <obs-extlang> because they
don't exist.

4646bis code with the new minimal "most perverse tag"
buffer size might correctly identify the non-existing
well-formed <obs-extlang> construct as too long, and
follow a code path not tested for the nuclear plant -
this example isn't compelling, it cuts on both sides.

 Frank



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