checksum
Click on the red underlined text to get to the source
... IP addresses are listed in their dotted-
decimal notation [RFC1123]. Length and checksum values are present
as decimal integers.
...
...
An iterative method SHOULD be used to calculate checksums, as the
length field will vary based on the size of the checksum.
...
... method SHOULD be used to calculate checksums, as the
length field will vary based on the size of the checksum.
The payload ...
... Bit-masks, where present have been converted into human-readable
values. Length and checksum and port values are present as decimal
integers.
...
... <window size="1"/>
<urgent pointer="0"/>
<checksum value="2988"/>
<tcp.options>
<tcp.end kind="0"/>
...
... Bit-masks, where present have been converted into human-readable
values. Length and checksum and port values are present as decimal
integers.
...
... element MUST be used as in section 2.1. An
iterative method SHOULD be used to calculate checksums as in section
2.1.
...
... version, tos, total.length, id, flags, offset, ttl,
protocol, checksum, source, destination, options,
padding)>
...
... ELEMENT checksum EMPTY>
<!-- 0 <= checksum <= 65535 (over header only) -->
<!ATTLIST checksum ...
... -->
<!-- the pseudoheader is only included for checksum calculations -->
<!ELEMENT tcp (tcp.pseudoheader?, tcp.header ...
... ELEMENT tcp.header (src, dest, sequence, acknowledgement, offset,
reserved, control, window, checksum, urgent,
tcp.options, padding)>
...