From b1d61f2762150eb429b3155cb8eb96b3f03849a5 Mon Sep 17 00:00:00 2001 From: Andy Adamson Date: Tue, 18 Nov 2014 16:28:03 -0500 Subject: [PATCH 3/3] Remove suggesting using GSSv3 child handle for lease renewal Signed-off-by: Andy Adamson --- nfsv42_middle_copy.xml | 18 +++--------------- 1 file changed, 3 insertions(+), 15 deletions(-) diff --git a/nfsv42_middle_copy.xml b/nfsv42_middle_copy.xml index 8118b72..d48f44b 100644 --- a/nfsv42_middle_copy.xml +++ b/nfsv42_middle_copy.xml @@ -954,21 +954,9 @@
- The secure inter-server copy depends upon both the source server - and the destination server keeping the copy_from_auth and - copy_to_auth RPCSEC_GSS3 context handles valid during the copy. The - client SHOULD use the copy_from_auth RPCSEC_GSS3 context handle for - the NFSv4 lease renewing operation to the source server, and - the copy_to_auth RPCSEC_GSS3 context handle for the NFSv4 lease - renewing operation to the destination server during the copy - to periodically - determine the continued validity of the respective GSS3 handles. - A periodic RPC NULL call can also be used for this purpose. - - - - If the client determines that either handle becomes - invalid during a copy, then the copy MUST be aborted by the client + If the client determines that either the copy_from_auth or + the copy_to_auth handle becomes invalid during a copy, + then the copy MUST be aborted by the client sending an OFFLOAD_CANCEL to both the source and destination servers and destroying the respective copy related context handles as described in . -- 1.9.3 (Apple Git-50)