ObsoletedPROPOSED STANDARDIETF stream

RFC 5666: Remote Direct Memory Access Transport for Remote Procedure Call

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8166.

Current version: RFC 8166Remote Direct Memory Access Transport for Remote Procedure Call Version 1

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

This document describes a protocol providing Remote Direct Memory Access (RDMA) as a new transport for Remote Procedure Call (RPC). The RDMA transport binding conveys the benefits of efficient, bulk-data transport over high-speed networks, while providing for minimal change to RPC applications and with no required revision of the application RPC protocol, or the RPC protocol itself. [STANDARDS-TRACK]

Document record

Document ID
RFC5666
Published
January 2010
Authors
T. Talpey; B. Callaghan
Status
PROPOSED STANDARD
Stream
IETF
Area
wit
Pages
34
Also known as
Obsoleted by:
RFC 8166

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.

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?

canonical URL: /rfc/5666-remote-direct-memory-access-transport-for-remote-procedure-call