RFC 4296: The Architecture of Direct Data Placement (DDP) and Remote Direct Memory Access (RDMA) on Internet Protocols
In plain English — editorial summary, not part of the RFC
This document defines an abstract architecture for Direct Data Placement (DDP) and Remote Direct Memory Access (RDMA) protocols to run on Internet Protocol-suite transports. This architecture does not necessarily reflect the proper way to implement such protocols, but is, rather, a descriptive tool for defining and understanding the protocols. DDP allows the efficient placement of data into buffers designated by Upper Layer Protocols (e.g., RDMA). RDMA provides the semantics to enable Remote Direct Memory Access between peers in a way consistent with application requirements. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4296
- Published
- December 2005
- Authors
- S. Bailey; T. Talpey
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5532Network File System (NFS) Remote Direct Memory Access (RDMA) Problem StatementCurrent
May 2009
- RFC 5666Remote Direct Memory Access Transport for Remote Procedure CallObsoleted
January 2010
- RFC 5667Network File System (NFS) Direct Data PlacementObsoleted
January 2010
- RFC 4297Remote Direct Memory Access (RDMA) over IP Problem StatementCurrent
December 2005
- RFC 4336Problem Statement for the Datagram Congestion Control Protocol (DCCP)Current
March 2006
- RFC 4340Datagram Congestion Control Protocol (DCCP)Updated
March 2006
- RFC 4341Profile for Datagram Congestion Control Protocol (DCCP) Congestion Control ID 2: TCP-like Congestion ControlUpdated
March 2006
- RFC 4342Profile for Datagram Congestion Control Protocol (DCCP) Congestion Control ID 3: TCP-Friendly Rate Control (TFRC)Updated
April 2006
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?