SCTP Dynamic Checksum selection
draft-ahmed-tsvwg-sctpdsum-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Haseeb Ahmed | ||
| Last updated | 2001-08-24 | ||
| 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
When SCTP was initially accepted as RFC2960 the Adler-32 checksum was specified to be used. However, inlight of issues raised in [STONE] it has been proposed that a more robust algorithm such as [CRC-32] be used instead. This poses compatibility problems for existing implementations of SCTP that are already using the Adler-32 algorithm for computing checksums. This document proposes a dynamic method to preserve backward compatibility between the two checksum algorithms.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)