Remote Direct Memory Access (RDMA) Protocol Extensions (RFC7306)
Original Publication Date: 2014-Jun-01
Included in the Prior Art Database: 2014-Jun-27
Internet Society Requests For Comment (RFCs)
H. Shah: AUTHOR [+5]
The RDMA Protocol [RFC5040] provides capabilities for zero-copy data communications that preserve memory protection semantics, enabling more efficient network protocol implementations. The RDMA Protocol is part of the iWARP family of specifications which also include RFC 5041 [RFC5041], RFC 5044 [RFC5044], and RFC 6581 [RFC6581]. This document specifies the following extensions to the RDMA Protocol (RDMAP):
Internet Engineering Task Force (IETF) H. Shah Request for Comments: 7306 Broadcom Corporation Category: Standards Track F. Marti ISSN: 2070-1721 W. Noureddine A. Eiriksson Chelsio Communications, Inc. R. Sharp Intel Corporation June 2014
Remote Direct Memory Access (RDMA) Protocol Extensions
This document specifies extensions to the IETF Remote Direct Memory Access Protocol (RDMAP) as specified in RFC 5040. RDMAP provides read and write services directly to applications and enables data to be transferred directly into Upper-Layer Protocol (ULP) Buffers without intermediate data copies. The extensions specified in this document provide the following capabilities and/or improvements: Atomic Operations and Immediate Data.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7306.
Shah, et al. Standards Track [Page 1]
RFC 7306 RDMA Protocol Extensions June 2014
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must ...