Re: [abnf-discuss] Deviant form of ABNF in RFC 989/1049/1341/1521/2045/2397

Paul Overell <paul@bayleaf.org.uk> Mon, 24 April 2023 08:53 UTC

Return-Path: <paul@bayleaf.org.uk>
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 AF2DEC151B11 for <abnf-discuss@ietfa.amsl.com>; Mon, 24 Apr 2023 01:53:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.898
X-Spam-Level:
X-Spam-Status: No, score=-6.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bayleaf-org-uk.20221208.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SWsdX4SYPNRV for <abnf-discuss@ietfa.amsl.com>; Mon, 24 Apr 2023 01:53:23 -0700 (PDT)
Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3468AC14CE3F for <abnf-discuss@ietf.org>; Mon, 24 Apr 2023 01:53:20 -0700 (PDT)
Received: by mail-wm1-x332.google.com with SMTP id 5b1f17b1804b1-3f19afc4fbfso18657625e9.2 for <abnf-discuss@ietf.org>; Mon, 24 Apr 2023 01:53:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bayleaf-org-uk.20221208.gappssmtp.com; s=20221208; t=1682326398; x=1684918398; h=content-transfer-encoding:in-reply-to:disposition-notification-to :from:content-language:references:to:subject:user-agent:mime-version :date:message-id:from:to:cc:subject:date:message-id:reply-to; bh=g1ztDFS/4s7ysl9dTUF0DS/N8L9Wn0P3eOYOLi2YiHI=; b=pubXWT3uwBAvASdiDb5pQzZnqaDi08YKu4EQP/Ok9Twklo+VkU2KLbwSqmcYqSRl9p ptGGD3jEMLS5Zmf2SiEaHF2+EHsb9qaGOJ8h0ejw/SaRoNzYY2KrK7rExleN9QtLd5tB uJhHo66AYYo+RHbB74YyUUrlm75DWggwDmGG4qRWipKPmkKMH4ONBGjHP1vUPrA9Bv9n JiU+A8Gw9whqegVAQneWs5/BSHaWV8rUPY1OYv5vxDTyta9d3ko6OoD4roPRpYJnOvHO dOMl/Z8AtQ61kipdYT2h98F7ej5cfk/glQ39YnlBrkceQqSGwOkkExUHga2Sz7eE4wda ib0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682326398; x=1684918398; h=content-transfer-encoding:in-reply-to:disposition-notification-to :from:content-language:references:to:subject:user-agent:mime-version :date:message-id:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=g1ztDFS/4s7ysl9dTUF0DS/N8L9Wn0P3eOYOLi2YiHI=; b=UM68fBgTG1w+ns//dVSXiEPYsOVOQOdUD3HONiznonFYOgcMBHTcyNrtgXfwWxTJz8 pny4wHN2b0H4FkbMH/ogtZ7QEks0vRQTfUuWa1bmR/x69FF4ulripshTESiUi7flxwZh XcmQOVu1F5Z/pBcw3q6ffWLWAOIp1CZOy8GhCucj5VvHdBM3SFJMDrM7z/K/G70TN9Y/ kai3+eQhP0GmOqoLD2mG7coUXAq1xWAZcPujpIFEFq0mMvVnePPZSVNUiXQcK2iqK/Zq 1+1hCMo3gxaIvifVgP39NduF2enUvdmZyNR3jItjPPF2bsBWB8Mk6ldgdsnyp+XF0415 BeGw==
X-Gm-Message-State: AAQBX9flPweCdif0nUZ5RCFnhwiBwaQbTBWBNg4jnWK1VfM1KBNm/QkS YOUacxlFMT93ylUu1ghM3HcICRGyt4oHxISGLq4=
X-Google-Smtp-Source: AKy350bEdqA58AUpnnDzyOVeX6IIizQ5FEY/dMEdcKlit7BwnSmE4rYjjBWwtJZBc28yuymGvkPfow==
X-Received: by 2002:adf:de04:0:b0:2fb:2508:c96 with SMTP id b4-20020adfde04000000b002fb25080c96mr9651044wrm.50.1682326398208; Mon, 24 Apr 2023 01:53:18 -0700 (PDT)
Received: from [192.168.1.53] (178.254.7.51.dyn.plus.net. [51.7.254.178]) by smtp.gmail.com with ESMTPSA id b1-20020a5d45c1000000b002fdeafcb132sm10273527wrs.107.2023.04.24.01.53.17 for <abnf-discuss@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 24 Apr 2023 01:53:17 -0700 (PDT)
Message-ID: <bafd6a7c-7551-70bb-c7c3-0a1cca569d61@bayleaf.org.uk>
Date: Mon, 24 Apr 2023 09:53:16 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.1
To: abnf-discuss@ietf.org
References: <1A81876F-C7E3-4060-8705-BC23CCF9D0D4@tzi.org> <a422e000-dd9e-7f4f-1486-29b5754bd4d3@gmail.com>
Content-Language: en-GB
From: Paul Overell <paul@bayleaf.org.uk>
In-Reply-To: <a422e000-dd9e-7f4f-1486-29b5754bd4d3@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/abnf-discuss/pE3Jnl6QHUp4e2hUi-mnohhiU8w>
Subject: Re: [abnf-discuss] Deviant form of ABNF in RFC 989/1049/1341/1521/2045/2397
X-BeenThere: abnf-discuss@ietf.org
X-Mailman-Version: 2.1.39
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, 24 Apr 2023 08:53:23 -0000

Hi,

I remember raising this issue when we were working on RFC2234, =, := and 
::= were discussed.

= from RFC822, RFC733 also used by Wirth (1977) and the BSI (now ISO) 
meta language.

::= from the Algol 60 report, AFAIK the original BNF

:= in use in some other RFCs, perhaps this was misremembered Algol 60, 
confusing ::= with its assignment operator :=

We settled on =


Regards

On 23/04/2023 23:06, Dave Crocker wrote:
> On 4/23/2023 2:42 PM, Carsten Bormann wrote:
>> Does anyone remember the history that made this alternative form 
>> appear, teeter on for a while, and then pretty much go away?
>> Was there any other difference apart from “:=“?
>
> I don't know anything about this variant.  For those who need a wider 
> context:  Through the 1970s and 1980s, there were lots of variants of 
> BNF.  We did one for RFC733, continued into RFC822, and it happened to 
> become popular with other folk.  So, RFC822 got incorporated into all 
> sorts of non-email specifications, to get it's form of ABNF.
>
> The later splitting out of the ABNF into a separate RFC was, really, 
> just to make specific citation easier, rather than for technical 
> reasons.  But of course, since we had the hood up,...
>
> d/
>
-- 
Paul Overell