No subject

8.8.  Vestigial Locking Infrastructure From V4.0

          .......................

   Also, there are a number of fields, present in existing operations



Shepler, et al.          Expires January 2, 2008              [Page 160]
^L
Internet-Draft            NFSv4 Minor Version 1                July 2007


   related to locking that have no use in minor version one.  They were
   used in minor version zero to perform functions now provided in a
   different fashion.

   o  Sequence ids used to sequence requests for a given state-owner and
      to provide retry protection, now provided via sessions.

   o  Client IDs used to identify the client associated with a given
      request.  Client identification is now available using the client
      ID associated with the current session, without needing an
      explicit client ID field.

   Such vestigial fields in existing operations should be set by the
   client to zero.  When they are not, the server MUST return an
   NFS4ERR_INVAL error.

------=_Part_35089_3981613.1189714110105
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Just a note that draft-ietf-nfsv4-minorversion1-13.txt has not changed
the draft-ietf-nfsv4-minorversion10.txt language concerning the
requriement to zero sequence id's and client id's in existing
operations related to locking (OPEN, LOCK, LOCKU, etc).<br>
<br>
Since the October Bakeathon uses draft-ietf-nfsv4-minorversion1-13.txt,
we expect this behaviour. Maybe I missed something - but I thought that
at the Austin bakeathon it was decided that the server could ignore
vestigial locking sequence id and client ids....<br>
<br>
--&gt;Andy <br>
<br>