NFS version 4.0 Trunking Update
draft-ietf-nfsv4-mv0-trunking-update-01

Document Type Active Internet-Draft (nfsv4 WG)
Last updated 2018-07-16
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network File System Version 4                              C. Lever, Ed.
Internet-Draft                                                    Oracle
Updates: 7530 (if approved)                                    D. Noveck
Intended status: Standards Track                                  NetApp
Expires: January 17, 2019                                  July 16, 2018

                    NFS version 4.0 Trunking Update
                draft-ietf-nfsv4-mv0-trunking-update-01

Abstract

   The location-related attribute in NFS version 4.0, fs_locations,
   informs clients about alternate locations of file systems.  An NFS
   version 4.0 client can use this information to handle migration and
   replication of server filesystems.  This document describes how an
   NFS version 4.0 client can additionally use this information to
   discover an NFS version 4.0 server's trunking capabilities.  This
   document updates RFC 7530.

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 https://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 January 17, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (https://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

Lever & Noveck          Expires January 17, 2019                [Page 1]
Internet-Draft           NFSv4.0 Trunking Update               July 2018

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Preliminaries . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  Document Organization . . . . . . . . . . . . . . . . . .   5
     3.3.  Document Goals  . . . . . . . . . . . . . . . . . . . . .   6
   4.  Overview of changes in RFC7530 Section 8  . . . . . . . . . .   6
   5.  Location Attributes (as updated)  . . . . . . . . . . . . . .   7
   6.  Updates to RFC7530 Section 8.4 (Uses of Location Information)   8
     6.1.  Introduction to uses of Location Information (as updated)   8
     6.2.  Trunking Discovery and Detection (to be added)  . . . . .  10
     6.3.  Location Attributes and Connection Type Selection (to be
           added)  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     6.4.  File System Replication and Trunking (as updated) . . . .  11
     6.5.  File System Migration (as updated)  . . . . . . . . . . .  11
     6.6.  Interaction of Trunking, Migration, and Replication (to
           be added) . . . . . . . . . . . . . . . . . . . . . . . .  12
   7.  Location Entries and Server Identity Update (as updated)  . .  13
   8.  Updates to RFC7530 Outside Section Eight  . . . . . . . . . .  14
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  16
     11.2.  Informative References . . . . . . . . . . . . . . . . .  17
   Appendix A.  Section Classification . . . . . . . . . . . . . . .  17
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  18
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18

1.  Introduction

   The NFS version 4.0 specification [RFC7530] defines a migration
   feature which enables the transfer of a file system from one server
   to another without disruption of client activity.  There were a
   number of issues with the original definition of this feature, now
   resolved with the publication of [RFC7931].

   After a migration event, a client must determine whether state
   recovery is necessary.  To do this, it needs to determine whether the
   source and destination server addresses represent the same server
Show full document text