RFC 8166: Remote Direct Memory Access Transport for Remote Procedure Call Version 1
In plain English — editorial summary, not part of the RFC
This document specifies a protocol for conveying Remote Procedure Call (RPC) messages on physical transports capable of Remote Direct Memory Access (RDMA). This protocol is referred to as the RPC-over- RDMA version 1 protocol in this document. It requires no revision to application RPC protocols or the RPC protocol itself. This document obsoletes RFC 5666.
Document record
- Document ID
- RFC8166
- Published
- June 2017
- Authors
- C. Lever; W. Simpson; T. Talpey
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 55
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8167Bidirectional Remote Procedure Call on RPC-over-RDMA TransportsCurrent
June 2017
- RFC 8164Opportunistic Security for HTTP/2Current
May 2017
- RFC 8154Parallel NFS (pNFS) Small Computer System Interface (SCSI) LayoutCurrent
May 2017
- RFC 8178Rules for NFSv4 Extensions and Minor VersionsCurrent
July 2017
- RFC 8187Indicating Character Encoding and Language for HTTP Header Field ParametersCurrent
September 2017
- RFC 8188Encrypted Content-Encoding for HTTPCurrent
June 2017
- RFC 8132PATCH and FETCH Methods for the Constrained Application Protocol (CoAP)Current
April 2017
- RFC 8108Sending Multiple RTP Streams in a Single RTP SessionCurrent
March 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?