|
IPv6 Datagram Main Header Format
(Page 3 of 3)
Key Changes to Main Header Between IPv4 and IPv6
To summarize, the IPv6 main header
compares to the IPv4 header as follows:
- Unchanged Fields: Three fields are used
the same way and retain the same name (though they have different content
and/or size): Version, Source Address and Destination
Address.
- Renamed Fields: Two fields are used the
same way but renamed: Traffic Class and Hop Limit.
- Modified Fields: Two fields are used in
a way similar way to their IPv4 predecessors but are slightly different
in meaning and also renamed: Payload Length and Next Header.
- Added Fields: There is one new field:
Flow Label.
- Removed Fields: To cut down on header
length and unnecessary work, five IPv4 header fields are removed from
the IPv6 header:
- Internet Header Length: No longer
needed, as the main IPv6 header is fixed in length at 40 bytes.
- Identification, Flags,
Fragment Offset: These are used for fragmentation, which
is done less in IPv6 than IPv4, so these fields are now found only when
needed in the Fragmentation
extension header.
- Header Checksum: The decision was
made to eliminate header checksum calculations in IPv6. It was viewed
as redundant with higher-layer error-checking and data link layer CRC
calculations. This saves processing time for routers and 2 bytes in
the datagram header.
In addition, while options were formerly
considered part of the main header in IPv4, they
are separate in IPv6.
| If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support! |
|
|
Home -
Table Of Contents - Contact Us
The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005
© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.
|