IETF Logo Mail Archive

Re: [abnf-discuss] [art] Should RFC 7405 be part of STD 68 now?

Dave Crocker <dcrocker@gmail.com> Tue, 19 December 2023 16:55 UTC

Return-Path: <dcrocker@gmail.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 79B0EC1AE96E; Tue, 19 Dec 2023 08:55:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 mTzU8oTp3tH7; Tue, 19 Dec 2023 08:55:37 -0800 (PST)
Received: from mail-oo1-xc34.google.com (mail-oo1-xc34.google.com [IPv6:2607:f8b0:4864:20::c34]) (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 18ED9C138FA3; Tue, 19 Dec 2023 08:55:32 -0800 (PST)
Received: by mail-oo1-xc34.google.com with SMTP id 006d021491bc7-58dd3528497so3363946eaf.3; Tue, 19 Dec 2023 08:55:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1703004931; x=1703609731; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=EmIRns/Am5eazN08zuozHPNnIcnlgJKpYDSTtlenWWc=; b=dG1xd9QUu166yAyBnVTzbdiT6F/T7lv6KC3kyUzSfahSgvP3W2wf71JPM8nR2rQSp2 zaOOnBmY5Bcd/yEp4L2QaYMwQTOBzTbArOCKyDTxxDStHI3NkPbnZKZZUKr3jpnANR02 9YT5HVtYEjYFivrpgRtPqXMcrthAVl15HZ6dXVRSRLi4h65gYxGb1h5zOOBYclGc+0SY IV7BFQLFB6p/cUCnYfhJQJlkl5UJCJAeZFMBorZrJudHvwPzUU6IuqhSCllWinIt6pQm ex0JOucg2JJW3PwXaFBrMTS3JOzsCMtdiRZ67dXO/X+x3yDraDzpfMZals1CzDh3H+Kb tcEA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703004931; x=1703609731; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=EmIRns/Am5eazN08zuozHPNnIcnlgJKpYDSTtlenWWc=; b=O2xlWinKFKF0avu/9x4/NtTs8JvZTiBjJuFiHM+8lifVXRKZaVf3jPc4kfUtaketVT WdOVVR+CDHOEpEjHk1MNJv/VRX09F92+PHAKWmUTMj0Dk9AKeI3oC1gNMACvK61Xli75 2AzSMtPmyFdtajLX9tAZOE1wsVrg83UFdRWB1+xrUPRx75l8eQTuMKYzpe80d0rEjv8p ulFW5J4Ps00usQgEy/EBegHGxHCQpmPr49L4NYxF1iwFCMLJeVySLH8WlZxqEbuuYiR7 gxHxq4dXFnGB6jHSERcD39FxoABtxHvactCr6vJFPhHpHtMykBexWPND+239+A7gmDTE UL3A==
X-Gm-Message-State: AOJu0YwQXsJtAeHP6rNVdrr5dsbw0zetItvjukYH+Ldd8k+hicACUXfW AcPpHNuuN7fKWkgH/mbGzXBaSZdnOvCVig==
X-Google-Smtp-Source: AGHT+IGWRMeBLDbjW/C1TBWYsPyY4QKteOP5mUMqMeHkgeI4UJE9mWmALwlIvbC1DIimy1NEi7RMGQ==
X-Received: by 2002:a05:6358:919d:b0:172:a707:746 with SMTP id j29-20020a056358919d00b00172a7070746mr9758820rwa.12.1703004930617; Tue, 19 Dec 2023 08:55:30 -0800 (PST)
Received: from [192.168.0.103] (c-98-42-225-165.hsd1.ca.comcast.net. [98.42.225.165]) by smtp.gmail.com with ESMTPSA id x11-20020a056a00188b00b006d7d454e58asm3846495pfh.117.2023.12.19.08.55.30 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 19 Dec 2023 08:55:30 -0800 (PST)
Message-ID: <f88fc51d-d508-41c7-afda-aa4291c71c24@gmail.com>
Date: Tue, 19 Dec 2023 08:55:30 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: "abnf-discuss@ietf.org" <abnf-discuss@ietf.org>
Cc: art@ietf.org
References: <4DD498CF-63E6-48E6-A75A-6E72B72F372E@tzi.org> <aa439241-3834-459f-a6bc-d7907e398566@gmail.com> <65ea22f3-90a2-4b53-acab-9e75e979f2d5@alum.mit.edu> <17282304-6c20-4394-aaac-40f39ec00ba7@gmail.com> <8E015488-DCB5-44DF-8C1D-7C3E1F3B5DAA@tzi.org> <c0facbd2-e9f7-4e31-b0b0-8956de922d1d@gmail.com> <8385e3ca-0a8e-4b84-b08d-068f761ccf92@alum.mit.edu>
From: Dave Crocker <dcrocker@gmail.com>
In-Reply-To: <8385e3ca-0a8e-4b84-b08d-068f761ccf92@alum.mit.edu>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/abnf-discuss/wCgBf0hIhvFqJFNcf1UcaJWhCpQ>
Subject: Re: [abnf-discuss] [art] Should RFC 7405 be part of STD 68 now?
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: Tue, 19 Dec 2023 16:55:37 -0000

On 12/19/2023 8:37 AM, Paul Kyzivat wrote:
> ISTM that the main problem with RFC 7405 now is that, I suspect, many 
> users of ABNF don't know about it. Anything that helps the ABNF using 
> public to become aware would be good. I don't know if adding it to STD 
> 68 would help that. I guess it won't hurt. 

good point.

d/

-- 
Dave Crocker
dcrocker@gmail.com
mast:@dcrocker@mastodon.social
408.329.0791

Volunteer, Silicon Valley Chapter
Information & Planning Coordinator
American Red Cross
dave.crocker2@redcross.org

v2.23.0 | Report a Bug | By Email