[nfsv4] draft-haynes-nfsv4-delstid-00 comments

[Mike Kupfer <[e-mail]>]

Here's my feedback on draft-haynes-nfsv4-delstid-00.  I've omitted a
couple comments that were already covered by Dave Noveck.  Apologies
for not getting this written up earlier.

* Comments on delegated timestamps

Another use case for delegated timestamps would be when the client has
a lot of dirty data for the file and an application asks for the
file's mtime.  My understanding is that the Linux client delays the
stat() call until the dirty data is written back.  If the client can
specify the mtime, then there's no need to wait for the writeback to
finish.

The current proposal disallows setting the timestamp to an earlier
time, and it disallows setting the timestamp to a time in the future.
Are those restrictions really necessary?  If yes, then the spec should
discuss how the client can make such changes (e.g., in response to a
user specifying a time via the "touch" command).  (And don't NetApp
and EMC have some scheme where a file can be made immutable and
unremovable by a series of steps that include changing the access
time?)

When the spec talks about the server accepting the time values from
the client, I assume that the server is allowed to lose precision, as
per Section 2.2.1 of RFC 7530.

* Editorial nits

- Page 1
  - serveral -> several
  - opeing -> opening
- Page 2
  - semnatics -> semantics
- Page 5
  - Those references to "microversion" should all be "minor version",
    shouldn't they?
  - documuent -> document
  - Section Section -> Section
- Page 7
  - negiotiate -> negotiate
- Page 8
  - prequisite -> prerequisite
  - Section 4.1: "With a server" -> "When a server"

regards,
mike