Bi-directional Remote Procedure Call On RPC-over-RDMA Transports
draft-ietf-nfsv4-rpcrdma-bidirection-05

The information below is for an old version of the document
Document Type Active Internet-Draft (nfsv4 WG)
Last updated 2016-11-28 (latest revision 2016-06-09)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Spencer Shepler
Shepherd write-up Show (last changed 2016-11-28)
IESG IESG state AD Evaluation
Consensus Boilerplate Yes
Telechat date
Responsible AD Spencer Dawkins
Send notices to "Spencer Shepler" <spencer.shepler@gmail.com>
Network File System Version 4                                   C. Lever
Internet-Draft                                                    Oracle
Intended status: Standards Track                            June 9, 2016
Expires: December 11, 2016

    Bi-directional Remote Procedure Call On RPC-over-RDMA Transports
                draft-ietf-nfsv4-rpcrdma-bidirection-05

Abstract

   Minor versions of NFSv4 newer than NFSv4.0 work best when ONC RPC
   transports can send Remote Procedure Call transactions in both
   directions on the same connection.  This document describes how RPC-
   over-RDMA transport endpoints convey RPCs in both directions on a
   single connection.

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 11, 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
   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.

Lever                   Expires December 11, 2016               [Page 1]
Internet-Draft         Bidirectional RPC-over-RDMA             June 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Understanding RPC Direction . . . . . . . . . . . . . . . . .   3
     2.1.  Forward Direction . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Backward Direction  . . . . . . . . . . . . . . . . . . .   4
     2.3.  Bi-directional Operation  . . . . . . . . . . . . . . . .   4
     2.4.  XID Values  . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Immediate Uses Of Bi-Directional RPC-over-RDMA  . . . . . . .   5
     3.1.  NFSv4.0 Callback Operation  . . . . . . . . . . . . . . .   5
     3.2.  NFSv4.1 Callback Operation  . . . . . . . . . . . . . . .   6
   4.  Flow Control  . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Backward Credits  . . . . . . . . . . . . . . . . . . . .   7
     4.2.  Inline Thresholds . . . . . . . . . . . . . . . . . . . .   7
     4.3.  Managing Receive Buffers  . . . . . . . . . . . . . . . .   7
   5.  Sending And Receiving Backward Operations . . . . . . . . . .   8
     5.1.  Sending A Backward Direction Call . . . . . . . . . . . .   9
     5.2.  Sending A Backward Direction Reply  . . . . . . . . . . .   9
     5.3.  Backward Direction Chunks . . . . . . . . . . . . . . . .   9
     5.4.  Backward Direction Retransmission . . . . . . . . . . . .  10
   6.  In the Absence of Backward Direction Support  . . . . . . . .  11
   7.  Considerations For Upper Layer Bindings . . . . . . . . . . .  11
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   11. Normative References  . . . . . . . . . . . . . . . . . . . .  13
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   The purpose of this document is to enable concurrent operation in
   both directions on a single transport connection using RPC-over-RDMA
   protocol versions that do not have specific facilities for backward
   direction operation.

   Backward direction RPC transactions are necessary for the operation
   of NFSv4.1, and in particular, of pNFS, though any Upper Layer
   Protocol implementation may make use of them.  An Upper Layer Binding
   for NFSv4.x callback operation is additionally required (see
   Section 7), but is not provided in this document.

   For example, using the approach described herein, RPC transactions
   can be conveyed in both directions on the same RPC-over-RDMA Version
   One connection without changes to the the XDR description of RPC-
   over-RDMA Version One.  This document does not modify the XDR or
Show full document text