[rfc-i] v3imp #8 Fragment tagging on sourcecode

nico at cryptonector.com (Nico Williams) Fri, 23 January 2015 19:08 UTC

From: "nico at cryptonector.com"
Date: Fri, 23 Jan 2015 13:08:03 -0600
Subject: [rfc-i] v3imp #8 Fragment tagging on sourcecode
In-Reply-To: <54C294FC.5000204@alum.mit.edu>
References: <54C20F92.4090400@seantek.com> <54C232FC.1000604@gmx.de> <54C275BC.1040905@alum.mit.edu> <20150123175511.GI2350@localhost> <54C28E3F.4040901@alum.mit.edu> <20150123181608.GJ2350@localhost> <54C294FC.5000204@alum.mit.edu>
Message-ID: <20150123190759.GK2350@localhost>

On Fri, Jan 23, 2015 at 01:37:48PM -0500, Paul Kyzivat wrote:
> Sure, but without a standard way to do it you need a custom
> extractor for every draft. In the case of ABNF, which is widely used
> in drafts, it would be highly desirable to have a single tool that
> could verify the ABNF in any draft.

It's not just about verifying.  It's also about compiling (e.g., ASN.1
modules).  I want to be able to extract the bloody thing.

> Also, the tagging in 5403 diminishes the readability of the draft.

Agreed.

Nico
--