Re: [Sidrops] Manifest entry filename validation

[Job Snijders <[e-mail]>]

On Tue, Nov 24, 2020 at 09:42:46AM -0500, Stephen Kent wrote:
> I think we're getting closer to a rigorous description. I like your concise
> text, but it doesn't cite the relevant list of allowed extensions, as
> suggested by Tim.  Also, the requirement that extensions be lowercase
> is redundant - RFC 6481 already dictates this for manifests, ROAs,
> CRLs, GB records, and  (all types of) certs.
> 
> Thus I suggest the following:
> 
> Section 4.2.2 "Names in FileAndHash objects"
> 
> Names that appear in the fileList MUST consist of one or more characters chosen
> from the set a-z, A-Z, 0-9, - (HYPHEN), or _ (UNDERSCORE), followed by a single .
> (DOT), followed by a three-letter extension. The extension MUST be one of those
> enumerated in the "RPKI Repository Naming Scheme" registry maintained by IANA [IANA]
> 
> As an example, 'vixxBTS_TVXQ-2pmGOT7.cer' is a valid filename.
> 
> add the following Normative Reference entry:
> 
> [IANA] https://www.iana.org/assignments/rpki/rpki.xhtml#name-schemes

OK for me, thank you all for picking at this until it looked right

Kind regards,

Job