Network File System (NFS) Upper Layer Binding To RPC-Over-RDMA
draft-ietf-nfsv4-rfc5667bis-01

The information below is for an old version of the document
Document Type Active Internet-Draft (nfsv4 WG)
Last updated 2016-06-30
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 30, 2016
Intended status: Standards Track
Expires: January 1, 2017

     Network File System (NFS) Upper Layer Binding To RPC-Over-RDMA
                     draft-ietf-nfsv4-rfc5667bis-01

Abstract

   This document specifies the Upper Layer Bindings of Network File
   System (NFS) protocol versions to RPC-over-RDMA transports.  Such
   Upper Layer Bindings are required to enable RPC-based protocols to
   use direct data placement when conveying large data payloads on RPC-
   over-RDMA transports.  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 January 1, 2017.

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

Lever                    Expires January 1, 2017                [Page 1]
Internet-Draft            NFS On RPC-Over-RDMA                 June 2016

   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 . . . . . . . . . . . . . . . . . .   3
     1.2.  Changes Since RFC 5667  . . . . . . . . . . . . . . . . .   3
     1.3.  Planned Changes To This Document  . . . . . . . . . . . .   4
   2.  Conveying NFS Operations On RPC-Over-RDMA Transports  . . . .   4
     2.1.  Use Of The Read List  . . . . . . . . . . . . . . . . . .   4
     2.2.  Use Of The Write List . . . . . . . . . . . . . . . . . .   5
     2.3.  Construction Of Individual Chunks . . . . . . . . . . . .   5
     2.4.  Use Of Long Calls And Replies . . . . . . . . . . . . . .   5
   3.  NFS Versions 2 And 3 Upper Layer Binding  . . . . . . . . . .   5
   4.  NFS Version 4 Upper Layer Binding . . . . . . . . . . . . . .   6
     4.1.  NFS Version 4 COMPOUND Considerations . . . . . . . . . .   7
     4.2.  NFS Version 4 Callbacks . . . . . . . . . . . . . . . . .   8
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Remote Direct Memory Access Transport for Remote Procedure Call,
   Version One [I-D.ietf-nfsv4-rfc5666bis] (RPC-over-RDMA) enables the
   use of direct data placement to accelerate the transmission of large
   data payloads associated with RPC transactions.

   Each RPC-over-RDMA transport header can convey lists of memory
   locations involved in direct transfers of data payloads.  These
   memory locations correspond to XDR data items defined in an Upper
   Layer Protocol (such as NFS).

   To facilitate interoperation, RPC client and server implementations
   must agree on what XDR data items in which RPC procedures are
   eligible for direct data placement (DDP).

   This document specifies the set of XDR data items in each of the
   following NFS protocol versions that are eligible for DDP.  It also
   contains additional material required of Upper Layer Bindings as
   specified in [I-D.ietf-nfsv4-rfc5666bis].

   o  NFS Version 2 [RFC1094]

Lever                    Expires January 1, 2017                [Page 2]
Internet-Draft            NFS On RPC-Over-RDMA                 June 2016

   o  NFS Version 3 [RFC1813]

   o  NFS Version 4.0 [RFC7530]
Show full document text