IETF Logo Mail Archive

Re: [abnf-discuss] ABNF updates

Paul Kyzivat <paul.kyzivat@comcast.net> Mon, 21 November 2016 15:32 UTC

Return-Path: <paul.kyzivat@comcast.net>
X-Original-To: abnf-discuss@ietfa.amsl.com
Delivered-To: abnf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3583B1296B9 for <abnf-discuss@ietfa.amsl.com>; Mon, 21 Nov 2016 07:32:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0J-siaauoErj for <abnf-discuss@ietfa.amsl.com>; Mon, 21 Nov 2016 07:32:51 -0800 (PST)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31A6D1294EA for <abnf-discuss@ietf.org>; Mon, 21 Nov 2016 07:32:51 -0800 (PST)
Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by resqmta-ch2-08v.sys.comcast.net with SMTP id 8qX4ckudg84vj8qaQcnRhX; Mon, 21 Nov 2016 15:32:50 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1479742370; bh=nIQQaTcniMREScd9DAsgvnPqkO3jthUk+WErD9AGQq4=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=JxYITrqXwyNJdKKd4LCRDFmt1X4NNHJ505/zG95BYwssaK5w9QYyXV7zcLL7KgWUU RwCBafickdtoUuAVeAKMPMM0lSwN6MY+w4q01fasiCa7tDyR4d3dXmA5P/YeE1lU02 CEwp3L3JtdfDm30Eogrh3xD2jcM9WyNwQUWZ2C9CGyRwEQgtuXzsyf9Na3KQTsgk6H FpG9U0e7XlqlKOqMDVRihFH2ATqYG9lcSBYmR8wvtHg6WxOHElWf3lkyhySso0C+1x dAKnaChPnND3looLpZyOFYGLYYxnG/4IdKR+lNQD6dNlLu2UpVzGiCrZZcImG8Mzs2 fziXoXO8wI5JQ==
Received: from [192.168.1.110] ([73.186.127.100]) by resomta-ch2-12v.sys.comcast.net with SMTP id 8qaPc473NcolR8qaQcaOrk; Mon, 21 Nov 2016 15:32:50 +0000
To: abnf-discuss@ietf.org
References: <583213D9.7050107@gmail.com>
From: Paul Kyzivat <paul.kyzivat@comcast.net>
Message-ID: <64cf89fe-55fa-fb1c-9c22-0e8ed8013623@comcast.net>
Date: Mon, 21 Nov 2016 10:32:49 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <583213D9.7050107@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfKAZjJhWTdWar32jC6geeL53VJsSXaX+iaifrywilvzqzsqbpHhOVXBbgJEcJwWP+9TtBRHFVA55rOL7LEpwrN/XajFcte7fNsJVwIxiVTfJQJ9U7+hF 22FDvf0WZH69m5JzhrW1Fam+t0LpUt7laUkMgaJl2vwoQ/j0+E277Xb1GqkqFfLuuyafB/+EBlU+Ug==
Archived-At: <https://mailarchive.ietf.org/arch/msg/abnf-discuss/ALzD2xGYuz00ydd6jszsDqwTOhQ>
Subject: Re: [abnf-discuss] ABNF updates
X-BeenThere: abnf-discuss@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "General discussion about tools, activities and capabilities involving the ABNF meta-language" <abnf-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/abnf-discuss>, <mailto:abnf-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/abnf-discuss/>
List-Post: <mailto:abnf-discuss@ietf.org>
List-Help: <mailto:abnf-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/abnf-discuss>, <mailto:abnf-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Nov 2016 15:32:53 -0000

On 11/20/16 4:21 PM, Doug Royer wrote:

> The current ABNF is somewhat easy to understand. The constrained draft
> is not somewhat easy to understand.
>
> I just don't see the constrained proposal as making future drafts more
> clear to a reader. Perhaps it does make it easier for a programmer. And
> where would making it easier for a programmer stop?

Is your problem with the syntax, or with the concept?

If the syntax, then do you have any thoughts about how to improve it?

> However external reference stuff will be great in helping avoid
> misunderstandings by specifying exactly what is being referenced. And it
> eliminates using comments a the protocol definition which I have missed
> more than once, or incorrectly applied to the line above or below the
> correct ABNF.

Indeed. I believe that formalizing external references is good for both 
human readers and automated processing.

	Thanks,
	Paul

v2.23.0 | Report a Bug | By Email