NFSv4.0 migration: Specification Update
draft-ietf-nfsv4-rfc3530-migration-update-04

NFSv4                                                     D. Noveck, Ed.
Internet-Draft
Updates: 3530 (if approved)                                    P. Shivam
Intended status: Standards Track                                C. Lever
Expires: September 30, 2014                                     B. Baker
                                                                  ORACLE
                                                          March 29, 2014

                NFSv4.0 migration: Specification Update
              draft-ietf-nfsv4-rfc3530-migration-update-04

Abstract

   The migration feature of NFSv4 allows for responsibility for a single
   filesystem to move from one server to another, without disruption to
   clients.  Recent implementation experience has shown problems in the
   existing specification for this feature in NFSv4.0.  This document
   clarifies and corrects the NFSv4.0 specification (RFC3530 and
   possible successors) to address these problems.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 30, 2014.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

Noveck, et al.         Expires September 30, 2014               [Page 1]
Internet-Draft           nfsv4-3530-migr-update               March 2014

   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Client Identity Definition  . . . . . . . . . . . . . . . . .   5
     4.1.  Differences from Replaced Sections  . . . . . . . . . . .   5
     4.2.  Client Identity data items  . . . . . . . . . . . . . . .   5
     4.3.  Server Release of Client ID . . . . . . . . . . . . . . .  10
     4.4.  client id string Approaches . . . . . . . . . . . . . . .  10
     4.5.  Non-Uniform client id string Approach . . . . . . . . . .  12
     4.6.  Uniform client id string Approach . . . . . . . . . . . .  13
     4.7.  Mixing client id string Approaches  . . . . . . . . . . .  15
     4.8.  Trunking Determination when using Uniform client id
           strings . . . . . . . . . . . . . . . . . . . . . . . . .  16
     4.9.  Client id string construction details . . . . . . . . . .  22
   5.  Locking and Multi-Server Namespace  . . . . . . . . . . . . .  23
     5.1.  Changes from Replaced Sections  . . . . . . . . . . . . .  23
     5.2.  Lock State and Filesystem Transitions . . . . . . . . . .  24
     5.3.  Migration and State . . . . . . . . . . . . . . . . . . .  24
       5.3.1.  Migration and clientid's  . . . . . . . . . . . . . .  26
       5.3.2.  Migration and state owner information . . . . . . . .  27
     5.4.  Replication and State . . . . . . . . . . . . . . . . . .  31
     5.5.  Notification of Migrated Lease  . . . . . . . . . . . . .  31
     5.6.  Migration and the Lease_time Attribute  . . . . . . . . .  34
   6.  Server Implementation Considerations  . . . . . . . . . . . .  34
     6.1.  Relation of Locking State Transfer to Other Aspects of
           Filesystem Motion . . . . . . . . . . . . . . . . . . . .  34
     6.2.  Preventing Locking State Modification During Transfer . .  36
   7.  Additional Changes  . . . . . . . . . . . . . . . . . . . . .  39
     7.1.  Summary of Additional Changes from Previous Documents . .  39
     7.2.  NFS4ERR_CLID_INUSE definition . . . . . . . . . . . . . .  40
     7.3.  NFS4ERR_DELAY return from RELEASE_LOCKOWNER . . . . . . .  40
     7.4.  Operation 35: SETCLIENTID - Negotiate Client ID . . . . .  41