Network File System (NFS) Direct Data Placement
draft-ietf-nfsv4-rfc5667bis-00

The information below is for an old version of the document
Document Type Active Internet-Draft (nfsv4 WG)
Last updated 2016-06-13
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
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
Obsoletes: 5667 (if approved)                              June 13, 2016
Intended status: Standards Track
Expires: December 15, 2016

            Network File System (NFS) Direct Data Placement
                     draft-ietf-nfsv4-rfc5667bis-00

Abstract

   This document defines the bindings of the various Network File System
   (NFS) versions to the Remote Direct Memory Access (RDMA) operations
   supported by the RPC-over-RDMA transport protocol.  It describes the
   use of direct data placement by means of server-initiated RDMA
   operations into client-supplied buffers for implementations of NFS
   versions 2, 3, 4, and 4.1 over such an RDMA transport.  This document
   obsoletes RFC 5667.

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 December 15, 2016.

Copyright Notice

   Copyright (c) 2016 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
   to this document.  Code Components extracted from this document must

Lever                   Expires December 15, 2016               [Page 1]
Internet-Draft          NFS Direct Data Placement              June 2016

   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
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
     1.2.  Planned Changes To This Document  . . . . . . . . . . . .   2
   2.  Transfers from NFS Client to NFS Server . . . . . . . . . . .   3
   3.  Transfers from NFS Server to NFS Client . . . . . . . . . . .   3
   4.  NFS Versions 2 and 3 Mapping  . . . . . . . . . . . . . . . .   5
   5.  NFS Version 4 Mapping . . . . . . . . . . . . . . . . . . . .   6
     5.1.  NFS Version 4 Callbacks . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   The Remote Direct Memory Access (RDMA) Transport for Remote Procedure
   Call (RPC) [I-D.ietf-nfsv4-rfc5666bis] allows an RPC client
   application to post buffers in a Chunk list for specific arguments
   and results from an RPC call.  The RDMA transport header conveys this
   list of client buffer addresses to the server where the application
   can associate them with client data and use RDMA operations to
   transfer the results directly to and from the posted buffers on the
   client.  The client and server must agree on a consistent mapping of
   posted buffers to RPC.  This document details the mapping for each
   version of the NFS protocol [RFC1094] [RFC1813] [RFC7530] [RFC5661].

1.1.  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].

1.2.  Planned Changes To This Document

   The following changes will be made, relative to [RFC5667]:

   o  References to [RFC5666] will be replaced with references to
      [I-D.ietf-nfsv4-rfc5666bis].  Corrections and updates relative to
      new language in [I-D.ietf-nfsv4-rfc5666bis] will be introduced.

Lever                   Expires December 15, 2016               [Page 2]
Internet-Draft          NFS Direct Data Placement              June 2016

   o  References to obsolete RFCs will be replaced.
Show full document text