RFC 4297: Remote Direct Memory Access (RDMA) over IP Problem Statement
In plain English — editorial summary, not part of the RFC
Overhead due to the movement of user data in the end-system network I/O processing path at high speeds is significant, and has limited the use of Internet protocols in interconnection networks, and the Internet itself -- especially where high bandwidth, low latency, and/or low overhead are required by the hosted application. This document examines this overhead, and addresses an architectural, IP-based "copy avoidance" solution for its elimination, by enabling Remote Direct Memory Access (RDMA). This memo provides information for the Internet community.
Document record
- Document ID
- RFC4297
- Published
- December 2005
- Authors
- A. Romanow; J. Mogul; T. Talpey; S. Bailey
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4296The Architecture of Direct Data Placement (DDP) and Remote Direct Memory Access (RDMA) on Internet ProtocolsCurrent
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
- RFC 4362RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTPUpdated
January 2006
- RFC 4230RSVP Security PropertiesCurrent
December 2005
- RFC 4369Definitions of Managed Objects for Internet Fibre Channel Protocol (iFCP)Obsoleted
January 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?