NFSv4.1 Update for Multi-Server Namespace
draft-dnoveck-nfsv4-mv1-msns-update-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2017-08-27
Replaced by draft-ietf-nfsv4-mv1-msns-update
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
NFSv4                                                          D. Noveck
Internet-Draft                                                    NetApp
Intended status: Standards Track                                C. Lever
Expires: February 28, 2018                                        ORACLE
                                                         August 27, 2017

               NFSv4.1 Update for Multi-Server Namespace
                 draft-dnoveck-nfsv4-mv1-msns-update-00

Abstract

   This document presents clarifications and corrections concerning
   features related to the use of location-related attributes in
   NFSv4.1.  These include migration, which transfers responsibility for
   a file system from one server to another, and trunking which deals
   with the discovery and control of the set of network addresses to use
   to access a file system.  The goal is to arrive at an appropriate set
   of updates to RFC5661.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

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 February 28, 2018.

Copyright Notice

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

Noveck & Lever          Expires February 28, 2018               [Page 1]
Internet-Draft             nfsv4.1-msns-update               August 2017

   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
   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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Summary of Issues . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Relationship of this Document to RFC5661  . . . . . . . . . .   7
   5.  Changes to Section 11 of RFC5661  . . . . . . . . . . . . . .   7
     5.1.  Introduction to Multi-server Namespace  . . . . . . . . .   8
     5.2.  Location-related Terminology  . . . . . . . . . . . . . .   8
     5.3.  Location Attributes . . . . . . . . . . . . . . . . . . .  10
     5.4.  Re-organization of Sections 11.4 and 11.5 of RFC5661  . .  11
     5.5.  Uses of Location Information  . . . . . . . . . . . . . .  11
       5.5.1.  Combining Multiple Uses in a Single Attribute . . . .  12
       5.5.2.  Location Attributes and Trunking  . . . . . . . . . .  13
       5.5.3.  File System Replication . . . . . . . . . . . . . . .  13
       5.5.4.  File System Migration . . . . . . . . . . . . . . . .  14
       5.5.5.  Referrals . . . . . . . . . . . . . . . . . . . . . .  15
       5.5.6.  Changes in a Location Attribute . . . . . . . . . . .  16
   6.  Re-organization of Section 11.7 of RFC5661  . . . . . . . . .  17
   7.  Overview of File Access Transitions . . . . . . . . . . . . .  18
   8.  Effecting Network Address Transitions . . . . . . . . . . . .  18
   9.  Effecting File System Transitions . . . . . . . . . . . . . .  19
     9.1.  File System Transitions and Simultaneous Access . . . . .  20
     9.2.  Filehandles and File System Transitions . . . . . . . . .  20
     9.3.  Fileids and File System Transitions . . . . . . . . . . .  21
     9.4.  Fsids and File System Transitions . . . . . . . . . . . .  22
       9.4.1.  File System Splitting . . . . . . . . . . . . . . . .  22
     9.5.  The Change Attribute and File System Transitions  . . . .  23
     9.6.  Write Verifiers and File System Transitions . . . . . . .  23
     9.7.  Readdir Cookies and Verifiers and File System Transitions  23
     9.8.  File System Data and File System Transitions  . . . . . .  24
     9.9.  Lock State and File System Transitions  . . . . . . . . .  25
   10. Transferring State upon Migration . . . . . . . . . . . . . .  26
Show full document text