IETF Logo Mail Archive

Re: [abnf-discuss] Mail regarding draft-seantek-constrained-abnf

Sean Leonard <dev+ietf@seantek.com> Sat, 09 July 2016 07:04 UTC

Return-Path: <dev+ietf@seantek.com>
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 A870712D11B; Sat, 9 Jul 2016 00:04:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no
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 zRcdJFm9T4z7; Sat, 9 Jul 2016 00:04:44 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (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 41E6E12D113; Sat, 9 Jul 2016 00:04:44 -0700 (PDT)
Received: from [192.168.123.151] (unknown [75.83.2.34]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id A993D509B6; Sat, 9 Jul 2016 03:04:42 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_A1F71F3E-2388-43CA-A827-8B4778DE544F"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Sean Leonard <dev+ietf@seantek.com>
In-Reply-To: <017701d1d95c$ebf89310$c3e9b930$@hansfords.net>
Date: Sat, 09 Jul 2016 00:04:40 -0700
Message-Id: <8FE8DD7A-D2A0-4A74-8805-A22F38A6853D@seantek.com>
References: <20160708121202.A3E5D12D19F@ietfa.amsl.com> <43d3ffea-57de-f7ef-e740-e448564008ed@alum.mit.edu> <bf12cdc4-8d17-d6aa-cc01-5afad19127ac@seantek.com> <017701d1d95c$ebf89310$c3e9b930$@hansfords.net>
To: Jonathan Hansford <jonathan@hansfords.net>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/abnf-discuss/1RxVhq32C2pU7Ojq0AFntl0XCNk>
Cc: draft-seantek-constrained-abnf@ietf.org, Paul Kyzivat <pkyzivat@alum.mit.edu>, abnf-discuss@ietf.org
Subject: Re: [abnf-discuss] Mail regarding draft-seantek-constrained-abnf
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: Sat, 09 Jul 2016 07:04:46 -0000

> On Jul 8, 2016, at 2:08 PM, Jonathan Hansford <jonathan@hansfords.net> wrote:
> 
> Paul and Sean,
>  
> Thanks for the replies. Life is too hectic at the moment, but I’m hoping I will find some time to properly read the I-D and your replies and see how it would all work for me. Is there a parser for constrained ABNF at the moment?

Not yet, but you are welcome to write one. :)

Sean

v2.23.0 | Report a Bug | By Email