RPC-over-RDMA Extension to Manage Transport Properties
draft-dnoveck-nfsv4-rpcrdma-xcharext-03

Document Type Active Internet-Draft (individual)
Last updated 2016-09-24
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                                  D. Noveck
Internet-Draft                                                       HPE
Intended status: Standards Track                      September 24, 2016
Expires: March 28, 2017

         RPC-over-RDMA Extension to Manage Transport Properties
                draft-dnoveck-nfsv4-rpcrdma-xcharext-03

Abstract

   This document specifies an extension RPC-over-RDMA Version Two.  The
   extension enables endpoints of an RPC-over-RDMA connection to
   exchange information which can be used to optimize message transfer.

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 March 28, 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Noveck                   Expires March 28, 2017                 [Page 1]
Internet-Draft     RPC-over-RDMA Transport Properties     September 2016

Table of Contents

   1.  Preliminaries . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
     1.2.  Introduction  . . . . . . . . . . . . . . . . . . . . . .   2
     1.3.  Role Terminology  . . . . . . . . . . . . . . . . . . . .   3
   2.  Transport Properties  . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Property Model  . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Transport Property Groups . . . . . . . . . . . . . . . .   5
     2.3.  Operations Related to Transport Properties  . . . . . . .   6
   3.  Basic Transport Properties  . . . . . . . . . . . . . . . . .   6
     3.1.  Receive Buffer Size . . . . . . . . . . . . . . . . . . .   8
     3.2.  Requester Remote Invalidation . . . . . . . . . . . . . .   9
     3.3.  Backward Request Support  . . . . . . . . . . . . . . . .  10
   4.  New Operations  . . . . . . . . . . . . . . . . . . . . . . .  11
     4.1.  ROPT_CONNPROP: Specify Properties at Connection . . . . .  12
     4.2.  ROPT_REQPROP: Request Modification of Properties  . . . .  13
     4.3.  ROPT_RESPROP: Respond to Request to Modify Transport
           Properties  . . . . . . . . . . . . . . . . . . . . . . .  13
     4.4.  ROPT_UPDPROP: Update Transport Properties . . . . . . . .  15
   5.  XDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  15
     5.1.  Code Component License  . . . . . . . . . . . . . . . . .  16
     5.2.  XDR Proper for Extension  . . . . . . . . . . . . . . . .  18
   6.  Extensibility . . . . . . . . . . . . . . . . . . . . . . . .  19
     6.1.  Additional Properties . . . . . . . . . . . . . . . . . .  19
     6.2.  Experimental Properties . . . . . . . . . . . . . . . . .  20
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  21
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  21
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  21
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  21
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  22
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .  22
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  22

1.  Preliminaries

1.1.  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].

1.2.  Introduction
Show full document text