Analysis of MPA over TCP Operations
draft-elzur-iwarp-mpa-tcp-analysis-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Uri Elzur | ||
| Last updated | 2003-02-06 | ||
| 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
Further explanation and analysis of architectural recommendations contained in the recent Internet-Draft, Marker PDU Aligned Framing for TCP Specification [MPA], is provided. The impact of the following three attributes of MPA over TCP is examined: * packing of multiple DDP ULPDUs into one TCP segment; * simplifying the receiver due to transmitter alignment of DDP headers with TCP headers; and * mistakenly attempting to interoperate an MPA-enabled endpoint with a non-MPA-enabled endpoint.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)