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

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 19 December 2023 14:31 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 1CAF4C1AE95F for <abnf-discuss@ietfa.amsl.com>; Tue, 19 Dec 2023 06:31:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.009
X-Spam-Level:
X-Spam-Status: No, score=-7.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alum.mit.edu
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 A44eCAZOTunI for <abnf-discuss@ietfa.amsl.com>; Tue, 19 Dec 2023 06:31:21 -0800 (PST)
Received: from NAM10-BN7-obe.outbound.protection.outlook.com (mail-bn7nam10on2054.outbound.protection.outlook.com [40.107.92.54]) (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 692A6C14F5F2 for <abnf-discuss@ietf.org>; Tue, 19 Dec 2023 06:31:20 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=RXoRC3bVC+WwMcd3MeewbAuTB3TGr0w2gzBVKapZDVAaMKnIvq0Yfirjmyj0GIMNdxNQ4Q8z2MDJy9OzsJ3wNItlOnakipnvlCSBxPQXBB7GLpBUu41qyKB7C+rjp80wEp1kNyD/vh3gF2EcA44nmuHAeupZh6pkMYUL5iWdamvO1VlotaIX9qrSzOHJ5B4DxV7W+Mu8e5R91dpBlq9OLv5fHweAOOPbXwdWKEtdF/OiHvNUxjjog3xiCaLdMFSmbINp9IppgTfHOdqtqrDK8PPFelESSfvsXscRWKviq195nLYVVZAnOuBouPElP/PJUYMkFJRh0oFB61GzZ06qbA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=b1atKMBgi6LSzRR/nd3L7eTiji8AO6usnxUihuyAKgM=; b=HXsdEmMNsMLo37O6xv7NZmYj+s/2cByXIara5wOIvd796rV27Vu36+qR+BN1rcMzz3u9WbBZ55+zwALDNIox/Sqag/YQMfX3uuSWu3ySEArTAKA4QoJujzyP3qx/C0Gfzv+WnbOX1Qrjn4pgTxiq3oAfatum1bY0NmuLr5IodDKynA8bjeMCsiP5iiNd8CFSFW1nEGMUiEp1HNt5/qzODfacDaLuPZA8K26EVGZ8/U66pvR1G1It0vrYp/sXxNUDanOeOF4lEIQCj0y+utG9AGj+WDtXOoSyIAN0YxH/+VX5iaNWd6/NTsj6PftePncgMaAjKUMDSIzfeKc+Hx6cww==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 18.7.68.33) smtp.rcpttodomain=ietf.org smtp.mailfrom=alum.mit.edu; dmarc=pass (p=none sp=none pct=100) action=none header.from=alum.mit.edu; dkim=none (message not signed); arc=none (0)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alum.mit.edu; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=b1atKMBgi6LSzRR/nd3L7eTiji8AO6usnxUihuyAKgM=; b=hTPU9FS8wjwQkkVyAgzl+Nq+nMdTFStadziuzwow7vzb/axBFFRByU4IO3yQcCUBzz1c1mq7M6Ex2rne1krvHfBbBkerclkX/nhppTmrPN51IIQJNidDlFlVOCsYAPt7SGOtYawxCYHE7PiuxIsS0GPS/lqsG0PDzu+MJyYjvCg=
Received: from BYAPR08CA0014.namprd08.prod.outlook.com (2603:10b6:a03:100::27) by MW4PR12MB7013.namprd12.prod.outlook.com (2603:10b6:303:218::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7113.18; Tue, 19 Dec 2023 14:31:15 +0000
Received: from MWH0EPF000989E5.namprd02.prod.outlook.com (2603:10b6:a03:100:cafe::14) by BYAPR08CA0014.outlook.office365.com (2603:10b6:a03:100::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7091.38 via Frontend Transport; Tue, 19 Dec 2023 14:31:15 +0000
X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 18.7.68.33) smtp.mailfrom=alum.mit.edu; dkim=none (message not signed) header.d=none;dmarc=pass action=none header.from=alum.mit.edu;
Received-SPF: Pass (protection.outlook.com: domain of alum.mit.edu designates 18.7.68.33 as permitted sender) receiver=protection.outlook.com; client-ip=18.7.68.33; helo=outgoing-alum.mit.edu; pr=C
Received: from outgoing-alum.mit.edu (18.7.68.33) by MWH0EPF000989E5.mail.protection.outlook.com (10.167.241.132) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7113.14 via Frontend Transport; Tue, 19 Dec 2023 14:31:14 +0000
Received: from [192.168.1.52] (c-73-143-251-114.hsd1.ma.comcast.net [73.143.251.114]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id 3BJEVCV1028052 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for <abnf-discuss@ietf.org>; Tue, 19 Dec 2023 09:31:13 -0500
Message-ID: <5f14c9b7-cefc-40fb-b05a-e63a60d01e02@alum.mit.edu>
Date: Tue, 19 Dec 2023 09:31:12 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: abnf-discuss@ietf.org
References: <4DD498CF-63E6-48E6-A75A-6E72B72F372E@tzi.org>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
In-Reply-To: <4DD498CF-63E6-48E6-A75A-6E72B72F372E@tzi.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-EOPAttributedMessage: 0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: MWH0EPF000989E5:EE_|MW4PR12MB7013:EE_
X-MS-Office365-Filtering-Correlation-Id: 9c424e5b-80b2-4f87-da4c-08dc009f2803
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: RgghZrFEHPFAkzAPebRJoBF5Avf4yESCH3i09W4ZoZhkCfSVveptCXnRm4IW6TwwDHYRaq89P1LWV8TMMk0hmqAwLB02yzwwPZc08WLucydjbm2YYcKFBCKdkcscPyAxLItpK6XTp802f5zfktvbrc+4iyjnGcCOt3CLYcMJXv2/TV3T1hI2HxFMoItUNf+jZeofjnC2Ymvtvv5ds8HanWI8Z9H2QF0zxLMWAI4Ig2DWiQtkLvxkpnyf1IoG2Ev5jRYzmM2M+TjfKA5vF8+EUSXuZ84McqNdGmKCaYxY4d7rNzx6v5V58S9wiIvFbejAai3HCd0WKODJ8/u0AlrBKHMi9oioyDCqtRcOgLL70eIZtAoNu/aLXCjuGaoX8d5hrJML1cMx3XQURzPI+rPcec3cwyPP6kT6Z92b9aEE3TIQD3Zmqz9CGob7wAcZJdfairhCCbp7tgMp+khxya2WQNa2X9Yd7Y3HCe+fxBsd6EZHn9vyezkHSMohcEqVG9xsZ/5TncyCRxhSOpJmftY50vxku6tTHh8VfV2fjmLQGJkxGqL+Sqdfm+ONxVFMaaPmof8R/MqoQ/3riskKfLsgK+yCfQfKQY9hwOqZ5Z/ST1LdDM9DqyKF8ZS7MkE4TXYJoXQ+rVpzFV1hdp7HwU2K8lizUzI2bEoFYhU85df1TiShMgXHUJrPQMxPoovsrcKx9Wa72zxUec33LmcHYkHKarlInEW8j1fcD4RIz17pFLM44vKtJ7HUtZQGhdtry0Lb5Bf3Ew7JpVc5vbLoA/4Phg==
X-Forefront-Antispam-Report: CIP:18.7.68.33; CTRY:US; LANG:en; SCL:1; SRV:; IPV:CAL; SFV:NSPM; H:outgoing-alum.mit.edu; PTR:outgoing-alum.mit.edu; CAT:NONE; SFS:(13230031)(39860400002)(346002)(136003)(396003)(376002)(230922051799003)(82310400011)(451199024)(186009)(1800799012)(64100799003)(46966006)(36840700001)(40470700004)(41320700001)(75432002)(41300700001)(47076005)(36860700001)(70586007)(31696002)(316002)(786003)(6916009)(70206006)(966005)(478600001)(53546011)(86362001)(26005)(5660300002)(336012)(2906002)(8676002)(8936002)(4744005)(2616005)(956004)(40480700001)(356005)(31686004)(40460700003)(82740400003)(7596003)(43740500002); DIR:OUT; SFP:1101;
X-OriginatorOrg: alum.mit.edu
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 19 Dec 2023 14:31:14.7471 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 9c424e5b-80b2-4f87-da4c-08dc009f2803
X-MS-Exchange-CrossTenant-Id: 3326b102-c043-408b-a990-b89e477d582f
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=3326b102-c043-408b-a990-b89e477d582f; Ip=[18.7.68.33]; Helo=[outgoing-alum.mit.edu]
X-MS-Exchange-CrossTenant-AuthSource: MWH0EPF000989E5.namprd02.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW4PR12MB7013
Archived-At: <https://mailarchive.ietf.org/arch/msg/abnf-discuss/KX74zV1lZfb6ztm-UK0NBCTOC0k>
Subject: Re: [abnf-discuss] 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 14:31:25 -0000

As author of RFC 7405 I'm biased. I'm interested to see what others think.

On 12/19/23 3:40 AM, Carsten Bormann wrote:
> Currently, STD 68 (ABNF) only comprises RFC 5234, not RFC 7405 (the case-sensitive strings addition).
> As the latter has been out for 9 years now and seems to be widely implemented, is it time to promote it to be part of STD 68 as well?
> 
> RFC 7405 has one errata report [1], which needs to be rejected (it is suggesting to instead use one of two rather different solutions — this is not what errata reports are for).
> 
> Apart from that, is there anything that is getting in the way of promoting STD 7405 to be part of STD 68?
> 
> (CCing art@, but please reply-to abnf-discuss@.)
> 
> Grüße, Carsten
> 
> 
> [1]: https://www.rfc-editor.org/errata/eid5334
> 
> _______________________________________________
> abnf-discuss mailing list
> abnf-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/abnf-discuss