NFS version 4.0 Trunking Update
draft-cel-nfsv4-mv0-trunking-update-00

Document Type Active Internet-Draft (individual)
Last updated 2017-11-13
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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)
Network File System Version 4                              C. Lever, Ed.
Internet-Draft                                                    Oracle
Updates: 7530 (if approved)                                    D. Noveck
Intended status: Standards Track                                  NetApp
Expires: May 17, 2018                                  November 13, 2017

                    NFS version 4.0 Trunking Update
                 draft-cel-nfsv4-mv0-trunking-update-00

Abstract

   Location-related attributes in NFS version 4.0 are used to support
   the migration and replication of server file systems.  In this
   document, we describe an additional use for these attributes as a
   mechanism to enable client discovery of an NFS version 4.0 server's
   trunking capabilities.  The interaction of trunking with migration
   and replication is also clarified.  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 May 17, 2018.

Copyright Notice

   Copyright (c) 2017 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
   include Simplified BSD License text as described in Section 4.e of

Lever & Noveck            Expires May 17, 2018                  [Page 1]
Internet-Draft           NFSv4.0 Trunking Update           November 2017

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

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, which
   are described in [I-D.ietf-nfsv4-migration-issues], and are resolved
   with the publication of [RFC7931].

   The latter document introduces into NFS version 4.0 a means of
   trunking detection as a means to determine whether two network
   addresses are connected to the same NFS version 4.0 server instance.
   Even though migration recovery is closely related to handling
   trunking, the NFS version 4.0 specification remains without a
Show full document text