Re: [Sidrops] Manifest entry filename validation

[Job Snijders <[e-mail]>]

On Thu, Nov 19, 2020 at 12:32:42PM -0500, Stephen Kent wrote:
> 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.

I reworded things a bit:

-----------

The following restrictions are imposed on the names that appear in the fileList:

1. Only a subset of IA5string characters are permitted: a-z, A-Z, 0-9, . (DOT), - (HYPHEN), and _ (UNDERSCORE).

2. Each name MUST be suffixed with the appropriate filename extension defined the object type and MUST be lowercase, e.g., '.cer', '.roa', or '.crl'.

3. The . (DOT) character MUST appear exactly once in a name.