Stream Control Transmission Protocol (SCTP) Checksum Change
The information below is for an old version of the document that is already published as an RFC.
This is an older version of an Internet-Draft that was ultimately published as RFC 3309.
|Authors||Randall R. Stewart , Jonathan Stone , Douglas Otis|
|Last updated||2013-03-02 (Latest revision 2002-05-07)|
|RFC stream||Internet Engineering Task Force (IETF)|
|Additional resources||Mailing list discussion|
|IESG||IESG state||RFC 3309 (Proposed Standard)|
|Responsible AD||Allison J. Mankin|
|IESG note||Published: RFC 3309|
|Send notices to||<email@example.com>, <firstname.lastname@example.org>|
A new Request for Comments is now available in online RFC libraries. RFC 3309 Title: Stream Control Transmission Protocol (SCTP) Checksum Change Author(s): J. Stone, R. Stewart, D. Otis Status: Standards Track Date: September 2002 Mailbox: email@example.com, firstname.lastname@example.org, email@example.com Pages: 17 Characters: 34670 Updates: 2960 I-D Tag: draft-ietf-tsvwg-sctpcsum-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3309.txt Stream Control Transmission Protocol (SCTP) currently uses an Adler-32 checksum. For small packets Adler-32 provides weak detection of errors. This document changes that checksum and updates SCTP to use a 32 bit CRC checksum. This document is a product of the Transport Area Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information.