Internet Protocol Small Computer System Interface (iSCSI) Cyclic Redundancy Check (CRC)/Checksum Considerations
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 3385.
|Authors||Dafna Sheinwald, Patricia Thaler , Julian Satran , Vincente Cavanna|
|Last updated||2020-01-21 (Latest revision 2002-04-16)|
|RFC stream||Legacy stream|
|RFC Editor Note||(None)|
|IESG||IESG state||RFC 3385 (Informational)|
|Responsible AD||Allison J. Mankin|
|Send notices to||(None)|
A new Request for Comments is now available in online RFC libraries. RFC 3385 Title: Internet Protocol Small Computer System Interface (iSCSI) Cyclic Redundancy Check (CRC)/Checksum Considerations Author(s): D. Sheinwald, J. Satran, P. Thaler, V. Cavanna Status: Informational Date: September 2002 Mailbox: firstname.lastname@example.org, Dafna_Sheinwald@il.ibm.com, email@example.com, firstname.lastname@example.org, Pages: 23 Characters: 53450 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-sheinwald-iscsi-crc-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3385.txt In this memo, we attempt to give some estimates for the probability of undetected errors to facilitate the selection of an error detection code for the Internet Protocol Small Computer System Interface (iSCSI). We will also attempt to compare Cyclic Redundancy Checks (CRCs) with other checksum forms (e.g., Fletcher, Adler, weighted checksums), as permitted by available data. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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.