idnits 2.17.1 

draft-sheinwald-iscsi-crc-02.txt:
  Skipping this file; it looks like a tombstone file to me.
--------------------------------------------------------------------------------

1	A new Request for Comments is now available in online RFC libraries.

3	        RFC 3385

5	        Title:      Internet Protocol Small Computer System Interface
6	                    (iSCSI) Cyclic Redundancy Check (CRC)/Checksum
7	                    Considerations
8	        Author(s):  D. Sheinwald, J. Satran, P. Thaler, V. Cavanna
9	        Status:     Informational
10	        Date:       September 2002
11	        Mailbox:    julian_satran@il.ibm.com,
12	                    Dafna_Sheinwald@il.ibm.com,
13	                    pat_thaler@agilent.com, vince_cavanna@agilent.com,
14	        Pages:      23
15	        Characters: 53450
16	        Updates/Obsoletes/SeeAlso:    None

18	        I-D Tag:    draft-sheinwald-iscsi-crc-02.txt

20	        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3385.txt

22	In this memo, we attempt to give some estimates for the probability of
23	undetected errors to facilitate the selection of an error detection
24	code for the Internet Protocol Small Computer System Interface
25	(iSCSI).

27	We will also attempt to compare Cyclic Redundancy Checks (CRCs) with
28	other checksum forms (e.g., Fletcher, Adler, weighted checksums), as
29	permitted by available data.

31	This memo provides information for the Internet community.  It does
32	not specify an Internet standard of any kind.  Distribution of this
33	memo is unlimited.

35	This announcement is sent to the IETF list and the RFC-DIST list.
36	Requests to be added to or deleted from the IETF distribution list
37	should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
38	added to or deleted from the RFC-DIST distribution list should
39	be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

41	Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
42	an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
43	help: ways_to_get_rfcs.  For example:

45	        To: rfc-info@RFC-EDITOR.ORG
46	        Subject: getting rfcs

48	        help: ways_to_get_rfcs

50	Requests for special distribution should be addressed to either the
51	author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
52	specifically noted otherwise on the RFC itself, all RFCs are for
53	unlimited distribution.echo
54	Submissions for Requests for Comments should be sent to
55	RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
56	Authors, for further information.