RDMA / TCP
draft-williams-rdmatcp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | James A. Williams | ||
| Last updated | 2000-09-28 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes a format for encapsulating RDMA (remote direct memory access) information within a TCP data stream. No changes or modification to TCP of any sort are required. This is not intended to be a protocol, but rather a common format that may be shared by multiple client protocols, for instance VI/TCP and iSCSI. By using a common format it is hoped that design of NICs supporting these multiple protocols can be simplified. Sufficient information is included in the RDMA message format to allow determination of the protocol message units, as will as the ability to process an incoming RDMA request even if previous packets are missing and awaiting retransmission. In addition a CRC-32 is included in each segment to enhance the checksum coverage included in TCP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)