RFC 5042: Direct Data Placement Protocol (DDP) / Remote Direct Memory Access Protocol (RDMAP) Security
In plain English — editorial summary, not part of the RFC
This document analyzes security issues around implementation and use of the Direct Data Placement Protocol (DDP) and Remote Direct Memory Access Protocol (RDMAP). It first defines an architectural model for an RDMA Network Interface Card (RNIC), which can implement DDP or RDMAP and DDP. The document reviews various attacks against the resources defined in the architectural model and the countermeasures that can be used to protect the system. Attacks are grouped into those that can be mitigated by using secure communication channels across the network, attacks from Remote Peers, and attacks from Local Peers. Attack categories include spoofing, tampering, information disclosure, denial of service, and elevation of privilege. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5042
- Published
- October 2007
- Authors
- J. Pinkerton; E. Deleganes
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 52
- Also known as
- —
- Updated by:
- RFC 7146
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 5043Stream Control Transmission Protocol (SCTP) Direct Data Placement (DDP) AdaptationUpdated
October 2007
- RFC 5041Direct Data Placement over Reliable TransportsUpdated
October 2007
- RFC 5044Marker PDU Aligned Framing for TCP SpecificationUpdated
October 2007
- RFC 5040A Remote Direct Memory Access Protocol SpecificationUpdated
October 2007
- RFC 5045Applicability of Remote Direct Memory Access Protocol (RDMA) and Direct Data Placement (DDP)Updated
October 2007
- RFC 5046Internet Small Computer System Interface (iSCSI) Extensions for Remote Direct Memory Access (RDMA)Obsoleted
October 2007
- RFC 5047DA: Datamover Architecture for the Internet Small Computer System Interface (iSCSI)Updated
October 2007
- RFC 5048Internet Small Computer System Interface (iSCSI) Corrections and ClarificationsObsoleted
October 2007
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?