Size-Limited Bi-directional Remote Procedure Call On Remote Direct Memory Access Transports
draft-ietf-nfsv4-rpcrdma-bidirection-00

The information below is for an old version of the document
Document Type Active Internet-Draft (nfsv4 WG)
Last updated 2015-06-01
Stream IETF
Intended RFC status (None)
Formats plain text pdf html 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)
NFSv4                                                           C. Lever
Internet-Draft                                                    Oracle
Intended status: Experimental                               May 29, 2015
Expires: November 30, 2015

   Size-Limited Bi-directional Remote Procedure Call On Remote Direct
                        Memory Access Transports
                draft-ietf-nfsv4-rpcrdma-bidirection-00

Abstract

   Recent minor versions of NFSv4 work best when ONC RPC transports can
   send ONC RPC transactions in both directions.  This document
   describes conventions that enable RPC-over-RDMA version 1 transport
   endpoints to interoperate when operation in both directions is
   necessary.

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 30, 2015.

Copyright Notice

   Copyright (c) 2015 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 November 30, 2015               [Page 1]
Internet-Draft          RPC-over-RDMA Bidirection               May 2015

   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.  Scope Of This Document  . . . . . . . . . . . . . . . . .   3
     1.3.  Understanding RPC Direction . . . . . . . . . . . . . . .   3
       1.3.1.  Forward Direction . . . . . . . . . . . . . . . . . .   4
       1.3.2.  Backward Direction  . . . . . . . . . . . . . . . . .   4
       1.3.3.  Bi-direction  . . . . . . . . . . . . . . . . . . . .   4
       1.3.4.  XID Values  . . . . . . . . . . . . . . . . . . . . .   4
     1.4.  Rationale For RPC-over-RDMA Bi-Direction  . . . . . . . .   5
       1.4.1.  NFSv4.0 Callback Operation  . . . . . . . . . . . . .   5
       1.4.2.  NFSv4.1 Callback Operation  . . . . . . . . . . . . .   6
     1.5.  Design Considerations . . . . . . . . . . . . . . . . . .   6
       1.5.1.  Backward Compatibility  . . . . . . . . . . . . . . .   7
       1.5.2.  Performance Impact  . . . . . . . . . . . . . . . . .   7
       1.5.3.  Server Memory Security  . . . . . . . . . . . . . . .   7
       1.5.4.  Payload Size  . . . . . . . . . . . . . . . . . . . .   7
   2.  Conventions For Backward Operation  . . . . . . . . . . . . .   8
     2.1.  Flow Control  . . . . . . . . . . . . . . . . . . . . . .   8
       2.1.1.  Forward Credits . . . . . . . . . . . . . . . . . . .   9
       2.1.2.  Backward Credits  . . . . . . . . . . . . . . . . . .   9
     2.2.  Managing Receive Buffers  . . . . . . . . . . . . . . . .   9
       2.2.1.  Client Receive Buffers  . . . . . . . . . . . . . . .  10
       2.2.2.  Server Receive Buffers  . . . . . . . . . . . . . . .  10
       2.2.3.  In the Absense of Backward Direction Support  . . . .  10
     2.3.  Backward Direction Retransmission . . . . . . . . . . . .  11
     2.4.  Backward Direction Message Size . . . . . . . . . . . . .  12
     2.5.  Sending A Backward Direction Call . . . . . . . . . . . .  12
     2.6.  Sending A Backward Direction Reply  . . . . . . . . . . .  13
   3.  Limits To This Approach . . . . . . . . . . . . . . . . . . .  13
     3.1.  Payload Size  . . . . . . . . . . . . . . . . . . . . . .  13
     3.2.  Preparedness To Handle Backward Requests  . . . . . . . .  13
     3.3.  Long Term . . . . . . . . . . . . . . . . . . . . . . . .  14
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .  15
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  15
Show full document text