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

The information below is for an old version of the document
Document Type Active Internet-Draft (nfsv4 WG)
Last updated 2016-05-02
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state In WG Last Call
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to (None)
Network File System Version 4                                   C. Lever
Internet-Draft                                                    Oracle
Intended status: Standards Track                             May 2, 2016
Expires: November 3, 2016

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

Abstract

   Recent minor versions of NFSv4 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 November 3, 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 November 3, 2016                [Page 1]
Internet-Draft         Bidirectional RPC-over-RDMA              May 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.  Rationale For 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.  Managing Receive Buffers  . . . . . . . . . . . . . . . .   7
   5.  Protocol For Backward Operation . . . . . . . . . . . . . . .   8
     5.1.  Sending A Backward Direction Call . . . . . . . . . . . .   8
     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  . . . . . . . .  10
   7.  Backward Direction Upper Layer Binding  . . . . . . . . . . .  11
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   11. Normative References  . . . . . . . . . . . . . . . . . . . .  12
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   The purpose of this document is to enable bi-directional RPC
   operation on RPC-over-RDMA protocol versions that do not have
   specific protocol facilities for backward direction operation.
   Backward direction RPC transactions enable the operation of NFSv4.1,
   and in particular pNFS.

   For example, using the protocol described in this document, RPC
   transactions can be conveyed in both directions on the same RPC-over-
   RDMA Version One connection without changes to the Version One header
   XDR description.  Therefore this document does not update
   [I-D.ietf-nfsv4-rfc5666bis].

   Providing an Upper Layer Binding for NFSv4.x callback operations is
   outside the scope of this document.

Lever                   Expires November 3, 2016                [Page 2]
Internet-Draft         Bidirectional RPC-over-RDMA              May 2016

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text