[nfsv4] RFC: VERIFY/NVERIFY for the POSIX draft ACL attributes in the extension

[Rick Macklem <[e-mail]>]

Hi,

I just posted about the who string issue for VERIFY/NVERIFY.

There is also one specific to the POSIX draft ACL attributes.
Unlike NFSv4 attributes, the order of the ACEs in the ACL
does not affect access semantics.

As such, should two POSIX draft ACL attributes with the
same ACEs, but in different order be consider the "same"
for VERIFY/NVERIFY?
--> It turns out this is very difficult to implement for the
      current Linux knfsd server (not sure about others,
      except FreeBSD, where implementation could be
      done either way).

One simple solution would be to not allow the POSIX
draft access and default ACL attributes to be used for
VERIFY/NVERIFY.

What do others think w.r.t. putting this prohibition in
the draft?

Thanks in advance for any comments, rick
ps: I am not aware of any extant client that does
      VERIFY/NVERIFY for Acl, Dacl, Owner or
      Owner_group.