[Sidrops] John Scudder's Yes on draft-ietf-sidrops-cms-signing-time-07: (with COMMENT)

[John Scudder via Datatracker <[e-mail]>]

John Scudder has entered the following ballot position for
draft-ietf-sidrops-cms-signing-time-07: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-sidrops-cms-signing-time/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for this clean and easy to read document. I have two small comments.

### Section 2

   To avoid needless re-transfers of unchanged files in consecutive
   rsync synchronizations, [I-D.timbru-sidrops-publication-server-bcp]
   recommends the use of so-called 'deterministic' (normalized)
   timestamps for files.  When the content of a file is unchanged,
   Repository Operators SHOULD ensure that the last modification
   timestamp of the file remains unchanged as well.

Is the RFC 2119 keyword a new requirement you are introducing in this document?
If it’s a quote from the draft you cite, please make it clear that’s what it is.

### Section 2.2

   If an RP uses RRDP to synthesize a filesystem hierarchy for the
   repository, then synchronizing to the corresponding directory
   directly is an option.  Alternatively, the RP can synchronize to a
   new (empty) directory using the _--compare-dest=DIR_ rsync feature,
   in order to avoid retrieving files that are already available by way
   of the synthesized filesystem hierarchy stemming from previous RRDP
   fetches.

I found this difficult to follow. Something like this would’ve been easier for
me —

NEW:

   If an RP used RRDP to synthesize a filesystem hierarchy for the
   repository, then when it must fall back to rsync one option is
   synchronizing to the corresponding directory
   directly.  Alternatively, the RP can synchronize to a
   new (empty) directory using the _--compare-dest=DIR_ rsync feature,
   in order to avoid retrieving files that are already available by way
   of the synthesized filesystem hierarchy stemming from previous RRDP
   fetches.