A checksum is used solely to see if a file has changed or to see if two files contain exactly the same data. The chances of two different files having the same checksum is very, very small.
If you change a file in any way, even by one byte, the checksum will change.
Every packet has a new set of error detection assigned to it, the Checksum is a part of this process. The error correction occurs in the transport layer where the ACK will fail and the receiving host will request the packet to be sent again.
RIP messages are wrapped in a UDP package, which already has a checksum.
A checksum is used to determine that the information sent using the protocol has not been corrupted en-route.
Only TCP will automatically discard a packet with a bad checksum. UDP packets have a checksum field, but it is rarely used, and then only by the application (not UDP itself)
A checksum (also known as a hash sum) is a small size datum computed from a block of digital data. One would use a checksum to detect errors that could have been introduced during storage.
7b
yes
128
If the checksum did change during transmission, wouldn't that mean a transmission error occurred? Any compression or encryption in the middle of transmission affects the data at that moment, but that's the wrong time to try to calculate a checksum for comparison purposes. (Unless it is yet another layer of error checking, used after compression/encryption but before transmission, and again after reception but before decompression/decryption.)
00000000
A checksum is a part of almost any number you want to include self-verification. Some examples are credit card numbers, bank account numbers, computer file "fingerprints," and computer security codes. See related links for a more detailed explaination of ways checksum is calculated.
CKSM