Re: [Sidrops] Manifest entry filename validation

Ties de Kock <tdekock@ripe.net> Mon, 23 November 2020 15:00 UTC

Return-Path: <tdekock@ripe.net>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62B2C3A0E90 for <sidrops@ietfa.amsl.com>; Mon, 23 Nov 2020 07:00:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level:
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ripe.net
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 2P7WRugV7qqF for <sidrops@ietfa.amsl.com>; Mon, 23 Nov 2020 07:00:34 -0800 (PST)
Received: from molamola.ripe.net (molamola.ripe.net [IPv6:2001:67c:2e8:11::c100:1371]) (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 028BB3A0E82 for <sidrops@ietf.org>; Mon, 23 Nov 2020 07:00:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ripe.net; s=s1-ripe-net; h=To:Cc:Date:Subject:Mime-Version:Content-Type:Message-Id: From; bh=6p6bLJrv1jqx8wS57pCmlQzmohYeyH/e9kvULc9W3nQ=; b=k50YGnyEtQDf3c2Lc7c8 pw9QD+AlwDz4W/7SR+aWppWd/grYRBQdbydKFNDlPsx8fle3oPcPhKBzLFRQhDOTJGRy2J9pyC8j3 BBk2OJmoabdcrgOHYD904x0w+VWKrlHcIFLufZQeD5vJK9yN/+tUBaGUbjA56CBIY9GIsK1WZGG1u Ng3i4PDShi2srblLoCGVRIkmmXFvpa6humxQk21aHIZlYvp1X+jcEd+amvmcyDSqdckuQUD3tatX7 kBY71cS+tpWXZ3IzWbH0AiGcH6Wu67b1L5CoJdjKzF0AuQzHnjK4/0BIZlBdESBJCaDeNqMP+5hM7 nK5oQiFKHN1YrA==;
Received: from bufobufo.ripe.net ([193.0.23.13]:51422) by molamola.ripe.net with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from <tdekock@ripe.net>) id 1khDKR-0006qR-IX; Mon, 23 Nov 2020 16:00:31 +0100
Received: from sslvpn.ipv6.ripe.net ([2001:67c:2e8:9::c100:14e6] helo=[IPv6:2001:67c:2e8:1200::646]) by bufobufo.ripe.net with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from <tdekock@ripe.net>) id 1khDKR-0004Li-GG; Mon, 23 Nov 2020 16:00:31 +0100
From: Ties de Kock <tdekock@ripe.net>
Message-Id: <DB542A6C-A0CB-4F0A-9D15-B06AA3B98875@ripe.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0145DF86-652D-4351-8CDD-BD1140EFB214"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Mon, 23 Nov 2020 16:00:31 +0100
In-Reply-To: <X7bVOm2uzffEWbMY@bench.sobornost.net>
Cc: sidrops@ietf.org
To: Job Snijders <job@ntt.net>
References: <18CC986C-97FA-41F6-A530-F782D3104A31@ripe.net> <73eae8a5-a400-cb45-7fbc-9cc7f79be804@verizon.net> <X7aywnRgq3ubVUBu@bench.sobornost.net> <X7bVOm2uzffEWbMY@bench.sobornost.net>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-ACL-Warn: Delaying message
X-RIPE-Signature: 059faafd1cc22ebb05e1592c815fe1e1c5d8760b6bcba14b845495fb8d5988c9
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/3mN1WdgIWSAlGPH5M6m0HgONFf8>
Subject: Re: [Sidrops] Manifest entry filename validation
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Nov 2020 15:00:42 -0000

Hi,

> On 19 Nov 2020, at 21:27, Job Snijders <job@ntt.net> wrote:
> 
> 2. Each name MUST be suffixed with the appropriate filename extension defined for the object type, and MUST be lowercase, e.g., '.cer' or '.roa'.


A request for clarification: Do you intend this to convey that filenames
have to be completely lower-case?

The current phrasing is slightly ambiguous and can be read to include "each name
MUST be lowercase", while the examples show that the extension must be lower-case.

Kind regards,
Ties