RDMA Connection Manager Private Messages For RPC-Over-RDMA Version One
draft-cel-nfsv4-rpcrdma-cm-pvt-msg-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-09-29
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network File System Version 4                                   C. Lever
Internet-Draft                                                    Oracle
Intended status: Experimental                         September 29, 2016
Expires: April 2, 2017

 RDMA Connection Manager Private Messages For RPC-Over-RDMA Version One
                 draft-cel-nfsv4-rpcrdma-cm-pvt-msg-00

Abstract

   This document specifies the format of RDMA-CM Private Data exchanged
   between RPC-over-RDMA Version One peers.  Such messages indicate peer
   support for Remote Invalidation and larger-than-default inline
   thresholds, but can be extended.  The Private Data message format
   defined in this document is experimental only.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

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 April 2, 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

Lever                     Expires April 2, 2017                 [Page 1]
Internet-Draft      RPC-Over-RDMA CM Private Messages     September 2016

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Advertised Transport Capabilities . . . . . . . . . . . . . .   3
   3.  Private Data Message Format . . . . . . . . . . . . . . . . .   4
   4.  Interoperability Considerations . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   RPC-over-RDMA Version One, specified in [I-D.ietf-nfsv4-rfc5666bis],
   enables the use of direct data placement for upper layer protocols
   based on RPC [RFC5531].  However, there are some recognized
   shortcomings of the RPC-over-RDMA Version One protocol.  The two most
   immediate shortcomings are:

   o  Setting up an explicit RDMA operation (RDMA Read or Write) can be
      costly.  The small default size of inline thresholds requires the
      use of explicit RDMA operations even for relatively small messages
      and data payloads.

   o  Unlike most other contemporary RDMA-enabled storage protocols,
      there is no facility in RPC-over-RDMA Version One that enables the
      use of Remote Invalidation [RFC5042].

   The original specification of RPC-over-RDMA Version One provided an
   out-of-band protocol for passing inline threshold settings between
   connected peers.  However, [I-D.ietf-nfsv4-rfc5666bis] deprecates
   this protocol because it was not fully specified and thus it was
   never implemented.

   Work on [I-D.ietf-nfsv4-rfc5666bis] has demonstrated that the RPC-
   over-RDMA Version One protocol as it stands is challenging to extend
   while maintaining interoperability.  Therefore, another out-of-band
   mechanism is required to help relieve these limitations for RPC-over-
   RDMA Version One implementations.

Lever                     Expires April 2, 2017                 [Page 2]
Internet-Draft      RPC-Over-RDMA CM Private Messages     September 2016
Show full document text