Re: [Sidrops] Manifest entry filename validation

Di Ma <madi@rpstir.net> Tue, 24 November 2020 05:34 UTC

Return-Path: <madi@rpstir.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 6D2A33A0DDC for <sidrops@ietfa.amsl.com>; Mon, 23 Nov 2020 21:34:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 GKJrFLfsvfnH for <sidrops@ietfa.amsl.com>; Mon, 23 Nov 2020 21:33:59 -0800 (PST)
Received: from out20-13.mail.aliyun.com (out20-13.mail.aliyun.com [115.124.20.13]) (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 D90B73A0DD9 for <sidrops@ietf.org>; Mon, 23 Nov 2020 21:33:57 -0800 (PST)
X-Alimail-AntiSpam: AC=CONTINUE; BC=0.3163746|-1; CH=green; DM=|CONTINUE|false|; DS=CONTINUE|ham_system_inform|0.211977-0.000279342-0.787743; FP=0|0|0|0|0|-1|-1|-1; HT=ay29a033018047212; MF=madi@rpstir.net; NM=1; PH=DS; RN=2; RT=2; SR=0; TI=SMTPD_---.J-XAXsE_1606196031;
Received: from 10.99.106.113(mailfrom:madi@rpstir.net fp:SMTPD_---.J-XAXsE_1606196031) by smtp.aliyun-inc.com(10.147.42.16); Tue, 24 Nov 2020 13:33:52 +0800
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.20.0.2.21\))
From: Di Ma <madi@rpstir.net>
In-Reply-To: <73eae8a5-a400-cb45-7fbc-9cc7f79be804@verizon.net>
Date: Tue, 24 Nov 2020 13:33:50 +0800
Cc: sidrops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D2C7BBA-3BD1-40DE-A0D8-21646D651262@rpstir.net>
References: <18CC986C-97FA-41F6-A530-F782D3104A31@ripe.net> <73eae8a5-a400-cb45-7fbc-9cc7f79be804@verizon.net>
To: Stephen Kent <stkent=40verizon.net@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3654.20.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/7c7wh4mr5DFStj7z0g_w9G46E5g>
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: Tue, 24 Nov 2020 05:34:01 -0000

Steve,

I am in favor of your suggestion, based on our experience of developing and maintaining RP software .

Di

> 2020年11月20日 01:32,Stephen Kent <stkent=40verizon.net@dmarc.ietf.org> 写道:
> 
> How about the following text:
> 
> 
> 
> 
> Section 4.2.2
> �
> To promote interoperability across file systems, the following restrictions are imposed on the file names that appear in the fileList:
> �
> 1. Only a subset of IA5string characters are permitted: a-z, A-Z, 0-9, . (dot), - (dash), and _ (underscore).
> 2. No blank file names are permitted.
> 3. Single and double dot (. and ..) file names are prohibited.
> 4. The three-character filename extension defined for each object type MUST be present and MUST be lowercase, e.g., cer, roa, and crl.
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops
>