Added to Favorites

Related Searches

Definitions

A cyclic redundancy check (CRC) is a type of function that takes as input a data stream of any length, and produces as output a value of a certain space, commonly a 32-bit integer. The term CRC denotes either the function or the function's output. A CRC can be used as a checksum to detect accidental alteration of data during transmission or storage. CRCs are popular because they are simple to implement in binary hardware, are easy to analyze mathematically, and are particularly good at detecting common errors caused by noise in transmission channels. The CRC was invented by W. Wesley Peterson, and published in his 1961 paper. The IEEE-recommended 32-bit CRC used in Ethernet and elsewhere appeared at a telecommunications conference in 1975.
## Introduction

A CRC is an error-detecting code. Its computation resembles a long division operation in which the quotient is discarded and the remainder becomes the result, with the important distinction that the arithmetic used is the carry-less arithmetic of a finite field. The length of the remainder is always less than or equal to the length of the divisor, which therefore determines how long the result can be. The definition of a particular CRC specifies the divisor to be used, among other things.## CRCs and data integrity vs. correctness

CRCs are not, by themselves, suitable for protecting against intentional alteration of data (for example, in authentication applications for data security), because their convenient mathematical properties make it easy to compute the CRC adjustment required to match any given change to the data.## Computation of CRC

To compute an n-bit binary CRC, line the bits representing the input in a row, and position the (n+1)-bit pattern representing the CRC's divisor (called a "polynomial") underneath the left-hand end of the row. Here is the first calculation for computing a 3-bit CRC:## Mathematics of CRC

Mathematical analysis of this division-like process reveals
how to pick a divisor that guarantees good error-detection
properties. In this analysis, the digits of the bit strings
are thought of as the coefficients of a polynomial in some
variable x -- coefficients that are elements of the finite
field GF(2) instead of more familiar numbers. This
"polynomial trick" allows bit strings to be viewed as
elements of a ring. A ring is, loosely
speaking, a set of elements somewhat like numbers, that can
be operated on by an operation that somewhat resembles
addition and another operation that somewhat resembles
multiplication, these operations possessing many of the
familiar arithmetic properties of commutativity,
associativity, and distributivity. Many analytical tools
commonly used with numbers also work on rings, and this is
why the "polynomial" view helps the analysis.
## Specifying a CRC

The concept of the CRC as an error-detecting code gets
complicated when an implementer or standards committee turns
it into a practical system. Here are some of the
complications:## Commonly used and standardized CRCs

While cyclic redundancy checks form part of several standards, they are not themselves standardized to the point of adopting one algorithm of each degree worldwide: there are three known CRC-12 polynomials, at least eight documented variations of CRC-16, and three of CRC-32. The polynomials usually seen are not the most efficient ones possible. Between 1993 and 2004 Koopman, Castagnoli and others surveyed the space of polynomials up to 16 bits, and of 24 and 32 bits, finding examples that have much better performance (in terms of Hamming distance for a given message size) than the polynomials of earlier protocols, and publishing the best of these with the aim of improving the error detection capacity of future standards. In particular, iSCSI has adopted one of the findings of this research.

## Designing CRC polynomials

The selection of generator polynomial is the most important part of implementing the CRC algorithm. The polynomial must be chosen to maximize the error detecting capabilities while minimizing overall collision probabilities.## References

## See also

## External links

### Online tools

Although CRCs can be constructed using any finite field, all commonly used CRCs employ the finite field GF(2). This is the field of two elements, usually called 0 and 1, comfortably matching computer architecture. The rest of this article will discuss only these binary CRCs, but the principles are more general.

An important reason for the popularity of CRCs for detecting the accidental alteration of data is their efficiency guarantee. Typically, an n-bit CRC, applied to a data block of arbitrary length, will detect any single error burst not longer than n bits (in other words, any single alteration that spans no more than n bits of the data), and will detect a fraction 1-2^{-n} of all longer error bursts. Errors in both data transmission channels and magnetic storage media tend to be distributed non-randomly (i.e. are "bursty"), making CRCs' properties more useful than alternative schemes such as multiple parity checks.

The simplest error-detection system, the parity bit, is in fact a trivial CRC: it uses the two-bit-long divisor 11.

It is often falsely assumed that when a message and its CRC are received from an open channel and the CRC matches the message's calculated CRC then the message cannot have been altered in transit.

This assumption is false because CRC is not really encryption at all: it is supposed to be used for data integrity checks, but is occasionally assumed to be used for encryption. When a CRC is calculated, the message is left in cleartext and the constant-size CRC is tacked onto the end (i.e. the message can be read just as easily).

Although CRCs share a problem with message digests in that there cannot be a 1:1 relationship between all possible messages and all possible CRCs, the CRC function fares worse because it is not a trapdoor function. That is, it is easy to generate other messages that result in the same CRC, especially messages similar to the original. By design however, a message that is too similar (differing only by a trivial noise pattern) will have a dramatically different CRC and thus be detected.

Alternatively the message could just be intercepted and replaced by a phony message with a new, phony CRC (creating a packet that would be verified by any Data-Link entity). So CRCs can be relied upon to verify integrity but not correctness.

In contrast, an effective way to protect messages against intentional tampering is by the use of a message authentication code such as HMAC.

11010011101100 <--- Input 1011 <--- divisor (4 Bits) -------------- 01100011101100 <--- result

If the input bit above the leftmost divisor bit is 0, do nothing and move the divisor to the right by one bit. If the input bit above the leftmost divisor bit is 1, the divisor is exclusive-ORed into the input (in other words, the input bit above each 1-bit in the divisor is toggled). The divisor is then shifted one bit to the right, and the process is repeated until the divisor reaches the right-hand end of the input row. Here is the last calculation:

00000000001110 <--- result of multiplication calculation1011 <--- divisor-------------- 00000000000101 <--- remainder (3 bits)

Since the leftmost divisor bit zeroed every input bit it touched, when this process ends the only bits in the input row that can be nonzero are the n bits at the right-hand end of the row. These n bits are the remainder of the division step, and will also be the value of the CRC function (unless the chosen CRC specification calls for some postprocessing).

- Sometimes an implementation prefixes a fixed bit pattern to the bitstream to be checked. This is useful when clocking errors might insert 0-bits in front of a message, an alteration that would otherwise leave the CRC unchanged.
- Sometimes an implementation appends n 0-bits (n being the size of the CRC) to the bitstream to be checked before the polynomial division occurs. This has the convenience that the CRC of the original bitstream with the CRC appended is exactly zero, so the CRC can be checked simply by performing the polynomial division on the expanded bitstream and comparing the remainder with zero.
- Sometimes an implementation exclusive-ORs a fixed bit pattern into the remainder of the polynomial division.
- Bit order: Some schemes view the low-order bit of each byte as "first", which then during polynomial division means "leftmost", which is contrary to our customary understanding of "low-order". This convention makes sense when serial-port transmissions are CRC-checked in hardware, because some widespread serial-port transmission conventions transmit bytes least-significant bit first.
- Byte order: With multi-byte CRCs, there can be confusion over whether the byte transmitted first (or stored in the lowest-addressed byte of memory) is the least-significant byte or the most-significant byte. For example, some 16-bit CRC schemes swap the bytes of the CRC.
- Omission of the high-order bit of the divisor polynomial: Since the high-order bit is always 1, and since an $n$-bit CRC must be defined by an $(n+1)$-bit divisor which overflows an $n$-bit register, some writers assume that it is unnecessary to mention the divisor's high-order bit.

Far from being arbitrarily chosen the popular CRC-32 polynomial, recommended by the IEEE and used by V.42, Ethernet, FDDI and ZIP and PNG files among others, is the generating polynomial of a Hamming code and was selected for its error detection performance. Even so it is outperformed by the Castagnoli CRC-32C polynomial used in iSCSI.

The table below lists only the polynomials of the various algorithms in use. Any particular protocol can impose pre-inversion, post-inversion and reversed bit ordering as described above. CRCs in proprietary protocols might use a complicated initial value and final XOR for obfuscation but this does not add cryptographic strength to the algorithm.

Note: in this table the high-order bit is omitted; see Specifying a CRC above.

Name | Polynomial | Representations: normal or reversed (reverse of reciprocal) |
---|---|---|

CRC-1 | $x\; +\; 1$ (most hardware; also known as parity bit) | 0x1 or 0x1 (0x1) |

CRC-4-ITU | $x^4\; +\; x\; +\; 1$ (ITU G.704, p. 12) | 0x3 or 0xC (0x9) |

CRC-5-ITU | $x^5\; +\; x^4\; +\; x^2\; +\; 1$ (ITU G.704, p. 9) | 0x15 or 0x15 (0x1A) |

CRC-5-USB | $x^5\; +\; x^2\; +\; 1$ (USB token packets) | 0x05 or 0x14 (0x12) |

CRC-6-ITU | $x^6\; +\; x\; +\; 1$ (ITU G.704, p. 3) | 0x03 or 0x30 (0x21) |

CRC-7 | $x^7\; +\; x^3\; +\; 1$ (telecom systems, MMC,SD) | 0x09 or 0x48 (0x44) |

CRC-8-ATM | $x^8\; +\; x^2\; +\; x\; +\; 1$ (ATM HEC) | 0x07 or 0xE0 (0x83) |

CRC-8-CCITT | $x^8\; +\; x^7\; +\; x^3\; +\; x^2\; +\; 1$ (1-Wire bus) | 0x8D or 0xB1 (0xC6) |

CRC-8-Dallas/Maxim | $x^8\; +\; x^5\; +\; x^4\; +\; 1$ (1-Wire bus) | 0x31 or 0x8C (0x98) |

CRC-8 | $x^8\; +\; x^7\; +\; x^6\; +\; x^4\; +\; x^2\; +\; 1$ | 0xD5 or 0xAB (0xEA ) |

CRC-8-SAE J1850 | $x^8\; +\; x^4\; +\; x^3\; +\; x^2\; +\; 1$ | 0x1D or 0xB8 (0x8E) |

CRC-10 | $x^\{10\}\; +\; x^9\; +\; x^5\; +\; x^4\; +\; x\; +\; 1$ | 0x233 or 0x331 (0x319) |

CRC-11 | $x^\{11\}\; +\; x^9\; +\; x^8\; +\; x^7\; +\; x^2\; +\; 1$ (FlexRay) | 0x385 or 0x50E (0x5C2) |

CRC-12 | $x^\{12\}\; +\; x^\{11\}\; +\; x^3\; +\; x^2\; +\; x\; +\; 1$ (telecom systems, ) | 0x80F or 0xF01 (0xC07) |

CRC-15-CAN | $x^\{15\}\; +\; x^\{14\}\; +\; x^\{10\}\; +\; x^8\; +\; x^7\; +\; x^4\; +\; x^3\; +\; 1$ | 0x4599 or 0x4CD1 (0x62CC) |

CRC-16-Fletcher | Not a CRC; see Fletcher's checksum | Used in Adler-32 A & B CRCs |

CRC-16-CCITT | $x^\{16\}\; +\; x^\{12\}\; +\; x^5\; +\; 1$ (X.25, V.41, CDMA, Bluetooth, XMODEM, HDLC,PPP, IrDA, BACnet; known as CRC-CCITT, MMC,SD) | 0x1021 or 0x8408 (0x8810 ) |

CRC-16-DNP | $x^\{16\}\; +\; x^\{13\}\; +\; x^\{12\}\; +\; x^\{11\}\; +\; x^\{10\}\; +\; x^8\; +\; x^6\; +\; x^5\; +\; x^2\; +\; 1$ (DNP, IEC 870, M-Bus) | 0x3D65 or 0xA6BC (0x9EB2) |

CRC-16-IBM | $x^\{16\}\; +\; x^\{15\}\; +\; x^2\; +\; 1$ (SDLC, USB, many others; also known as CRC-16) | 0x8005 or 0xA001 (0xC002) |

CRC-24-Radix-64 | $x^\{24\}\; +\; x^\{23\}\; +\; x^\{18\}\; +\; x^\{17\}\; +\; x^\{14\}\; +\; x^\{11\}\; +\; x^\{10\}\; +\; x^7\; +\; x^6\; +\; x^5\; +\; x^4\; +\; x^3\; +\; x\; +\; 1$ (FlexRay) | 0x864CFB or 0xDF3261 (0xC3267D) |

CRC-30 | $x^\{30\}\; +\; x^\{29\}\; +\; x^\{21\}\; +\; x^\{20\}\; +\; x^\{15\}\; +\; x^\{13\}\; +\; x^\{12\}\; +\; x^\{11\}\; +\; x^\{8\}\; +\; x^\{7\}\; +\; x^\{6\}\; +\; x^\{2\}\; +\; x\; +\; 1$ (CDMA) | 0x2030B9C7 or 0x38E74301 (0x30185CE3) |

CRC-32-Adler | Not a CRC; see Adler-32 | See Adler-32 |

CRC-32-IEEE 802.3 | $x^\{32\}\; +\; x^\{26\}\; +\; x^\{23\}\; +\; x^\{22\}\; +\; x^\{16\}\; +\; x^\{12\}\; +\; x^\{11\}\; +\; x^\{10\}\; +\; x^8\; +\; x^7\; +\; x^5\; +\; x^4\; +\; x^2\; +\; x\; +\; 1$ (V.42, MPEG-2, PNG ) | 0x04C11DB7 or 0xEDB88320 (0x82608EDB ) |

CRC-32C (Castagnoli) | $x^\{32\}\; +\; x^\{28\}\; +\; x^\{27\}\; +\; x^\{26\}\; +\; x^\{25\}\; +\; x^\{23\}\; +\; x^\{22\}\; +\; x^\{20\}\; +\; x^\{19\}\; +\; x^\{18\}\; +\; x^\{14\}\; +\; x^\{13\}\; +\; x^\{11\}\; +\; x^\{10\}\; +\; x^9\; +\; x^8\; +\; x^6\; +\; 1$ | 0x1EDC6F41 or 0x82F63B78 (0x8F6E37A0 ) |

CRC-32K (Koopman) | $x^\{32\}\; +\; x^\{30\}\; +\; x^\{29\}\; +\; x^\{28\}\; +\; x^\{26\}\; +\; x^\{20\}\; +\; x^\{19\}\; +\; x^\{17\}\; +\; x^\{16\}\; +\; x^\{15\}\; +\; x^\{11\}\; +\; x^\{10\}\; +\; x^\{7\}\; +\; x^\{6\}\; +\; x^\{4\}\; +\; x^\{2\}\; +\; x\; +\; 1$ | 0x741B8CD7 or 0xEB31D82E (0xBA0DC66B ) |

CRC-64-ISO | $x^\{64\}\; +\; x^4\; +\; x^3\; +\; x\; +\; 1$ (HDLC — ISO 3309) | 0x000000000000001B or 0xD800000000000000 (0x800000000000000D) |

CRC-64-ECMA-182 | $x^\{64\}\; +\; x^\{62\}\; +\; x^\{57\}\; +\; x^\{55\}\; +\; x^\{54\}\; +\; x^\{53\}\; +\; x^\{52\}\; +\; x^\{47\}\; +\; x^\{46\}\; +\; x^\{45\}\; +\; x^\{40\}\; +\; x^\{39\}\; +\; x^\{38\}\; +\; x^\{37\}\; +\; x^\{35\}\; +\; x^\{33\}\; +$ $x^\{32\}\; +\; x^\{31\}\; +\; x^\{29\}\; +\; x^\{27\}\; +\; x^\{24\}\; +\; x^\{23\}\; +\; x^\{22\}\; +\; x^\{21\}\; +\; x^\{19\}\; +\; x^\{17\}\; +\; x^\{13\}\; +\; x^\{12\}\; +\; x^\{10\}\; +\; x^9\; +\; x^7\; +\; x^4\; +\; x\; +\; 1$ (as described in ECMA-182 p.63) | 0x42F0E1EBA9EA3693 or 0xC96C5795D7870F42 (0xA17870F5D4F51B49) |

Known to exist, but technologically defunct -- mainly replaced by cryptographic hash functions

- CRC-128 (IEEE)
- CRC-256 (IEEE)

The most important attribute of the polynomial is its length (the number of the highest nonzero coefficient), because of its direct influence of the length of the computed checksum.

The most commonly used polynomial lengths are

- 9 bits (CRC-8)
- 17 bits (CRC-16)
- 33 bits (CRC-32)
- 65 bits (CRC-64)

When creating a new CRC polynomial or improving an existing CRC the general mathematical advice is to use an irreducible polynomial that satisfies all polynomical irreducibility constraints from modular arithmetics.

- Irreducibility in this case means that the polynomial cannot be divided by any polynomial except itself and 1 with zero remainder.
- Reducible polynomials can still be used, but their error correcting and detecting capabilities will be less effective. Some applications may choose to use reducible polynomials under certain conditions.

The properties of the generator polynomial can be derived from the algorithm definition

- CRCs with more than one nonzero coefficients are able to detect all single bit errors in the input message.
- CRCs can be used to detect all double bit errors in the input message shorter than 2^k, where k is the length of the longest irreducible part of the polynomial.
- If the CRC polynomial is divided by x + 1 then no polynomial with odd number of nonzero coefficients can be divided by it. Hence, it can be used to detect odd number of errors in the input message (like single bit parity function).
- CRC polynomials detect (single) burst errors shorter than the number of the position of the highest polynomial coefficient.

General category

Specific Technological References

- Easy to understand CRC32 C++ Source Code
- Free CRC Source Code from the Boost C++ Libraries
- The CRC Pitstop
- Williams, R. (1993-09) A Painless Guide to CRC Error Detection Algorithms
- Understanding Cyclic Redundancy Check
- Black, R. (1994-02) Fast CRC32 in Software; algorithm 4 is used in Linux and info-zip's zip and unzip.
- Kounavis, M. and Berry, F. (2005). A Systematic Approach to Building High Performance, Software-based, CRC generators, Slicing-by-4 and slicing-by-8 algorithms
- CRC32: Generating a checksum for a file, C++ implementation by Brian Friesen
- CRC16 to CRC64 collision research
- Reversing CRC - Theory and Practice.
- 'CRC-Analysis with Bitfilters'.
- Another Bad CRC Reading Tool, but free
- MathPages - Cyclic Redundancy Checks
- Tool for Bad CRC Reading with advanced options
- A CRC calculation utility and C source code generator written in Python. (MIT licence)
- CRC Encoding - C# Implementation by Marcel de Wijs
- Cyclic Redundancy Check: theory, practice, hardware, and software with emphasis on CRC-32. A sample chapter from Henry S. Warren, Jr. Hacker's Delight.

- Free CRC Verilog Circuit generator
- Online CRC32 and CRC32B calculator (uses IEEE 802.3 polynomial)
- Online Tool to compute common CRCs (8/16/32/64) from strings
- Online CRC calculator
- Another online CRC calculator
- A third online CRC calculator
- Online CRC Tool: Generator of synthesizable CRC functions
- Online Char (ASCII), HEX, Binary, Base64, etc... Encoder/Decoder with MD2, MD4, MD5, SHA1+2, CRC, etc. hashing algorithms

Wikipedia, the free encyclopedia © 2001-2006 Wikipedia contributors (Disclaimer)

This article is licensed under the GNU Free Documentation License.

Last updated on Thursday October 09, 2008 at 20:33:22 PDT (GMT -0700)

View this article at Wikipedia.org - Edit this article at Wikipedia.org - Donate to the Wikimedia Foundation

This article is licensed under the GNU Free Documentation License.

Last updated on Thursday October 09, 2008 at 20:33:22 PDT (GMT -0700)

View this article at Wikipedia.org - Edit this article at Wikipedia.org - Donate to the Wikimedia Foundation

Copyright © 2014 Dictionary.com, LLC. All rights reserved.