[Sidrops] Paul Wouters' Yes on draft-ietf-sidrops-cms-signing-time-07: (with COMMENT)

[Paul Wouters via Datatracker <[e-mail]>]

Paul Wouters 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:
----------------------------------------------------------------------

The abstract seems overly long and best moved to the Introduction. I would only
keep the last paragraph of the Abstract. Although it seems already mostly
repeated in the Introduction so just removing the first two paragraphs would
probably be good as well.

        This document advances the aforementioned concept

Advance from what to what? I think you mean "from optional to mandatory" ?

In section 2.2, it talks about omitting transfers and sparse backups, but it
does not mention it creates hardlinks for files that need no transfering from
the reference directory, at least how I use rsync, eg with --archive which
means "-rlptgoD". (this is fact the way I still do backups, creating daily
trees that are full directory sets per day all using hardlinks for unmodified
files). With this option, it does the things the document talks about, like
using original datestamp, perms, modes, etc.