No subject

8.8.&nbsp; Vestigial Locking Infrastructure From V4.0<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .......................<br>
<br>
&nbsp;&nbsp; Also, there are a number of fields, present in existing operations<br>
<br>
<br>
<br>
Shepler, et al.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Expires January 2,
2008&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
[Page 160]<br>
^L<br>
Internet-Draft&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
NFSv4 Minor Version
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
July 2007<br>
<br>
<br>
&nbsp;&nbsp; related to locking that have no use in minor version one.&nbsp; They were<br>
&nbsp;&nbsp; used in minor version zero to perform functions now provided in a<br>
&nbsp;&nbsp; different fashion.<br>
<br>
&nbsp;&nbsp; o&nbsp; Sequence ids used to sequence requests for a given state-owner and<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to provide retry protection, now provided via sessions.<br>
<br>
&nbsp;&nbsp; o&nbsp; Client IDs used to identify the client associated with a given<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; request.&nbsp; Client identification is now available using the client<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ID associated with the current session, without needing an<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; explicit client ID field.<br>
<br>
&nbsp;&nbsp; Such vestigial fields in existing operations should be set by the<br>
&nbsp;&nbsp; client to zero.&nbsp; When they are not, the server MUST return an<br>
&nbsp;&nbsp; NFS4ERR_INVAL error.<br>
<br>
<br>

------=_Part_35089_3981613.1189714110105--