[Tsvwg] RFC 3309 on Stream Control Transmission Protocol (SCTP) Checksum Change

rfc-editor@rfc-editor.org Mon, 30 September 2002 22:24 UTC

Message-Id: <200209302222.g8UMMSD10406@gamma.isi.edu>
To: IETF-Announce:;
Cc: rfc-editor@rfc-editor.org, tsvwg@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 30 Sep 2002 15:22:28 -0700
Subject: [Tsvwg] RFC 3309 on Stream Control Transmission Protocol (SCTP) Checksum Change
Sender: tsvwg-admin@ietf.org
Errors-To: tsvwg-admin@ietf.org
Precedence: bulk

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:    jonathan@dsg.stanford.edu, rrs@cisco.com,
                    dotis@sanlight.net
        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.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc3309.txt"><ftp://ftp.isi.edu/in-notes/rfc3309.txt>

[Tsvwg] RFC 3309 on Stream Control Transmission P… rfc-editor