SCTP compatible delivery subsystem
draft-otis-record-delivery-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Douglas Otis | ||
| Last updated | 2001-05-09 | ||
| 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 is to allow record based equipment a common record offload layer suitable for other protocols. As all storage protocols anticipate hardware acceleration, it becomes incumbent to provide this hardware a generic structure that can be applied to many protocols and yet allow an unencumbered feature set. The structures defined for SCTP [RFC2960] were developed to provide record based solutions and are well suited for this common record offload layer. This document will assume either direct use of SCTP, a modified SCTP common header used as a TCP option, or this modified SCTP common header placed within the TCP byte stream. SCTP conventions will be used to enable enhanced features such as connection recovery in lieu of other techniques. The sequential handling of delineated records is done in accordance with SCTP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)