Re: [Tools-discuss] Tools resources that we use: bap

Julian Reschke <> Fri, 05 March 2021 15:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A8F073A26E1 for <>; Fri, 5 Mar 2021 07:28:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SPkPjePSsSEv for <>; Fri, 5 Mar 2021 07:28:36 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 45A003A26B7 for <>; Fri, 5 Mar 2021 07:28:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;; s=badeba3b8450; t=1614958114; bh=p0uMdpdX90pSWbc5UDyy1/6nMzbCWjcBoN3//M0yLFg=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=NQJixdjxFjtd8x8oZ+DqR2H8g16a42DgjpvPRC2+PWyvd4NllOmp09Qj0t6KUN1OJ 0EQgy193RPZ4GkvOV3GuA8GZ9alq58Z2jq32TZB9u7jeIdhbf+qW/AYi8hUZ0DZA5/ kLzUVwDVbvv0Ihia/NLxbj/nHW+4FpOpjSHvZtys=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [] ([]) by (mrgmx105 []) with ESMTPSA (Nemesis) id 1MzhjF-1leYmu3ufR-00vgbV for <>; Fri, 05 Mar 2021 16:28:33 +0100
References: <> <> <> <> <> <> <> <>
From: Julian Reschke <>
Message-ID: <>
Date: Fri, 05 Mar 2021 16:28:31 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:m8zOzyPZ+3Hzak8kgrRQFpaLQPwaY/1Uh1IGtwLwQajQeFn2uQV ZmyEbLtLAZ93yezDn+wIrNLviOp7OdZd8tb9hyy4wgWcAogmesi0W5zQ30UzD9Hf+1wGktq tEfvMZxRikOFXPOtcfntFGnKqQwZrJ6wK1qr/+/3TEwhTd1Rd/y6vmaopPus9YFHbfiUauM sOcvSR9CEZj1n2eDnFsKQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:OfFjwKKYhkg=:AdFTV4nm2aa7hP2qAj58PA tBxYsCXXLllsw9Ly2xzp13LPQD+E58ei1PqkCcOiyvNYp5Sy599d4JsN/ZNsYbsUYH95G/7/o NCppxGoO6LGzNjOzyY4Z2uyaxTLIty0mNb6sJffafFGRfT9Qv9o9Au5fLv49wTAcdkV8vT4aL bXkUqTbpl62P854gAYSab+pPrRakzpq7x8tx+aiP6FWuLeOJ9TEzs2ZSKXX2OeIICCU39QPM8 6mIH0UlzU8968bINzsPFCrhkIg/OM65REwPv6O/KD8t9HjdM46DgqOEhv1M2pGxtyAvCI4yVh fOKGDBNb1GEnVmGKk1EIypxHSYwVqtVkZXwS7/Q9P/w0RtJjRPzBl05OXk22AmkvKoC/iaedy O/jSrXs5tqjhEKz6X0rss7l8+u7TDYEx1CvdUw/cENUfS5ZlElNxY/9fZrVinHePmaD+js9Qv zM9bBIhSfUP3zc5i/FYMfMffwJTDRHCE/mvtnoSw38EefbhEJUECAejC3rqcxbblXUU4gxkIY NeXhO3aCqMvdHOpAbnz+PhagCCBz0t/nIv02OJh9FxVVfQM5Jdge1xzKHFpE0+zXtZ/sTKdCg XekhSFgWKxQO2/VAFuG3Im7POH0YmtdtGw7pcMU9qH9N4TNCwetqdJbuDuPa22TDbKa8f6CW/ J23Sm/Oaop3ba761n/1LO4mPunXuXe9cpcj427IwB0YJAoaImBK4EO50T41RVVmZ11rcK4vEx +0MYIqMYY0n9MjRBlLA2HXfneSoNu+tvUTgPGVVFhbHq6Vj0zdZyFGcebnkbfTvH+iEuFuiLV THO9K/Q69hrgJRneRbPg1GBkHKOr/rGJ9XoHifIIbgBmXzQIae1IpSf58c17bVeG7myLWGuYU kbw/aV8AYiBhKj1tkuPg==
Archived-At: <>
Subject: Re: [Tools-discuss] Tools resources that we use: bap
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 05 Mar 2021 15:28:44 -0000

Am 05.03.2021 um 16:18 schrieb Paul Kyzivat:
> On 3/5/21 9:36 AM, Robert Sparks wrote:
>> Please drop notes to the tools-discuss list or directly to me as you
>> think of things. I'd like for you to catch them as you see you need them.
>> On 3/5/21 2:51 AM, Carsten Bormann wrote:
>>> On 2021-03-05, at 09:39, Stewart Bryant <>
>>> wrote:
>>>> To whom do we send a list of the tools resources that we use?
>>> We could start a discussion thread on tools-discuss.
> I use bap from time to time. Unfortunately AFAIK it is barely
> maintained. After I finished RFC7405 I asked Bill Fenner about
> incorporating support for it in bap. He was very hard to reach. I then
> implemented the necessary updates to bap and submitted a pull request.
> But it was never acted upon. I eventually just gave up.

The http-core editors have their own fork (which does 7405, but also
handles the HTTP #list production). See

> I'd really like to have better support for ABNF in the draft pipeline.
> Ideally ABNF checking would be an automatic part of the process.
> Unfortunately it is hard to do well. Much ABNF in drafts/RFCs has
> dependencies on ABNF in some other document, and those dependencies are
> stated informally so that it takes manual processing to prepare
> something that can be fully checked by bap. If/how to resolve this needs
> discussion and then probably some implementation work.

In HTTP (core), we declare all ABNF productions that we import as prose,
for instance, see

With that, the ABNF at least is self-contained and can be checked
automatically (and we do that in our build process).

Best regards, Julian