RDMA Connection Manager Private Data For RPC-Over-RDMA Version 1
draft-ietf-nfsv4-rpcrdma-cm-pvt-data-07
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Active Internet-Draft (nfsv4 WG) | |
| Author | Chuck Lever | ||
| Last updated | 2020-02-20 (latest revision 2020-01-31) | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats | pdf htmlized (tools) htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Brian Pawlowski | ||
| Shepherd write-up | Show (last changed 2019-10-30) | ||
| IESG | IESG state | IESG Evaluation::Revised I-D Needed | |
| Consensus Boilerplate | Yes | ||
| Telechat date |
Needs a YES. Needs 7 more YES or NO OBJECTION positions to pass. |
||
| Responsible AD | Magnus Westerlund | ||
| Send notices to | Spencer Shepler <spencer.shepler@gmail.com>, Thomas Haynes <loghyr@gmail.com>, Brian Pawlowski <beepee@gmail.com> | ||
| IANA | IANA review state | IANA OK - Actions Needed | |
Network File System Version 4 C. Lever
Internet-Draft Oracle
Updates: 8166 (if approved) January 31, 2020
Intended status: Standards Track
Expires: August 3, 2020
RDMA Connection Manager Private Data For RPC-Over-RDMA Version 1
draft-ietf-nfsv4-rpcrdma-cm-pvt-data-07
Abstract
This document specifies the format of RDMA-CM Private Data exchanged
between RPC-over-RDMA version 1 peers as part of establishing a
connection. The addition of the private data payload specified in
this document is an optional extension that does not alter the RPC-
over-RDMA version 1 protocol. This document updates RFC 8166.
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 https://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 August 3, 2020.
Copyright Notice
Copyright (c) 2020 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
(https://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 August 3, 2020 [Page 1]
Internet-Draft RPC-Over-RDMA CM Private Data January 2020
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. Advertised Transport Properties . . . . . . . . . . . . . . . 3
3.1. Inline Threshold Size . . . . . . . . . . . . . . . . . . 3
3.2. Remote Invalidation . . . . . . . . . . . . . . . . . . . 4
4. Private Data Message Format . . . . . . . . . . . . . . . . . 5
4.1. Interoperability Considerations . . . . . . . . . . . . . 6
4.1.1. Interoperability with RPC-over-RDMA Version 1
Implementations . . . . . . . . . . . . . . . . . . . 7
4.1.2. Interoperability Amongst RDMA Transports . . . . . . 7
5. Updating the Message Format . . . . . . . . . . . . . . . . . 7
5.1. Feature Support Flags . . . . . . . . . . . . . . . . . . 8
5.2. Inline Threshold Values . . . . . . . . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7.1. Guidance for Designated Experts . . . . . . . . . . . . . 10
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
8.1. Normative References . . . . . . . . . . . . . . . . . . 10
8.2. Informative References . . . . . . . . . . . . . . . . . 11
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
The RPC-over-RDMA version 1 transport protocol [RFC8166] enables
payload data transfer using Remote Direct Memory Access (RDMA) for
upper-layer protocols based on Remote Procedure Calls (RPC)
[RFC5531]. The terms "Remote Direct Memory Access" (RDMA) and
"Direct Data Placement" (DDP) are introduced in [RFC5040].
The two most immediate shortcomings of RPC-over-RDMA version 1 are:
o Setting up an RDMA data transfer (via RDMA Read or Write) can be
costly. The small default size of messages transmitted using RDMA
Send forces the use of RDMA Read or Write operations even for
relatively small messages and data payloads.
The original specification of RPC-over-RDMA version 1 provided an
out-of-band protocol for passing inline threshold values between
connected peers [RFC5666]. However, [RFC8166] eliminated support
for this protocol making it unavailable for this purpose.
Lever Expires August 3, 2020 [Page 2]
Internet-Draft RPC-Over-RDMA CM Private Data January 2020
o Unlike most other contemporary RDMA-enabled storage protocols,
Show full document text