#1437 Possible wrong version flag value when making .ZIP archive with NTFS timestamp

[quanta]

When creating .ZIP archive with NTFS timestamps, the version needed to extract field for the stored file's header is not affected. However, the NTFS timestamps are stored in the extra field 0x000A that was introduced in PKZIP 2.50 for Windows, which also supports Deflate64 compression. By this logic, NTFS timestamp feature should raise the version needed to extract field value to at least 2.1. However, the current .ZIP File Format Specification does not define minimum feature version for storing NTFS timestamp, so the version needed to extract field value for this particular feature would be 1.0, even though no PKWARE archiver with version made by field lower than 2.1 is capable of recognizing or storing NTFS timestamps in .ZIP archive (PKZIP for DOS 2.50=2.5, SecureZIP 9 for Windows=6.2).

The real question is, should version needed to extract field value be set to 2.1 or higher when it is a feature not defined in version needed to extract description .ZIP File Format Specification, but is never used in PKWARE product with version made by field lower than 2.1? As a comparison, SecureZIP 9 for Windows sets version needed to extract field to 2.0 when using Deflate compression, even though SecureZIP 9 for Windows also stores NTFS timestamps.