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

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

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

Abstract

   This document specifies Upper Layer Bindings of Network File System
   (NFS) protocol versions to RPC-over-RDMA transports.  These bindings
   are required to enable RPC-based protocols to use direct data
   placement 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 February 26, 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 February 26, 2017               [Page 1]
Internet-Draft            NFS On RPC-Over-RDMA               August 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.  Changes Since RFC 5667  . . . . . . . . . . . . . . . . .   3
     1.2.  Extending This Upper Layer Binding  . . . . . . . . . . .   4
     1.3.  Requirements Language . . . . . . . . . . . . . . . . . .   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 . . . . . . . . . . . . . . . . . .   4
     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.  DDP-Eligibility . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  Reply Size Estimation . . . . . . . . . . . . . . . . . .   7
     4.3.  NFS Version 4 COMPOUND Considerations . . . . . . . . . .   7
     4.4.  NFS Version 4 Callback  . . . . . . . . . . . . . . . . .   9
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  10
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   An RPC-over-RDMA transport, such as defined in
   [I-D.ietf-nfsv4-rfc5666bis], may employ direct data placement to
   transmit large data payloads associated with RPC transactions.  Each
   RPC-over-RDMA transport header conveys lists of memory locations
   corresponding to XDR data items defined in an Upper Layer Protocol
   (such as NFS).

   To facilitate interoperation, RPC client and server implementations
   must agree in advance on what XDR data items in which RPC procedures
   are eligible for direct data placement (DDP).  This document contains
   material required of Upper Layer Bindings, as specified in
   [I-D.ietf-nfsv4-rfc5666bis], for the following NFS protocol versions:

   o  NFS Version 2 [RFC1094]

   o  NFS Version 3 [RFC1813]

   o  NFS Version 4.0 [RFC7530]

Lever                   Expires February 26, 2017               [Page 2]
Internet-Draft            NFS On RPC-Over-RDMA               August 2016

   o  NFS Version 4.1 [RFC5661]

   o  NFS Version 4.2 [I-D.ietf-nfsv4-minorversion2]

1.1.  Changes Since RFC 5667

   Corrections and updates made necessary by new language in
Show full document text