RFC 8167: Bidirectional Remote Procedure Call on RPC-over-RDMA Transports

In plain English — editorial summary, not part of the RFC

Minor versions of Network File System (NFS) version 4 newer than minor version 0 work best when Remote Procedure Call (RPC) transports can send RPC transactions in both directions on the same connection. This document describes how RPC transport endpoints capable of Remote Direct Memory Access (RDMA) convey RPCs in both directions on a single connection.

Document record

Document ID

RFC8167

Published

June 2017

Authors

C. Lever

Status

PROPOSED STANDARD

Stream

IETF

Area

wit

Pages

13

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC8167

Topics

• NFS-over-RDMA
• RPC-over-RDMA

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 8166Remote Direct Memory Access Transport for Remote Procedure Call Version 1Updated

  June 2017

• RFC 8267Network File System (NFS) Upper-Layer Binding to RPC-over-RDMA Version 1Current

  October 2017

• RFC 8797Remote Direct Memory Access - Connection Manager (RDMA-CM) Private Data for RPC-over-RDMA Version 1Current

  June 2020

• RFC 8164Opportunistic Security for HTTP/2Current

  May 2017

• RFC 8178Rules for NFSv4 Extensions and Minor VersionsCurrent

  July 2017

• RFC 8154Parallel NFS (pNFS) Small Computer System Interface (SCSI) LayoutCurrent

  May 2017

• RFC 8187Indicating Character Encoding and Language for HTTP Header Field ParametersCurrent

  September 2017

• RFC 8188Encrypted Content-Encoding for HTTPCurrent

  June 2017

Also filed under

• PROPOSED STANDARD
• 2017
• IETF stream
• wit area