Visual RFC.
ALL RFCs / RFC 8200
Read the RFC ↗
RFC 8200 / MECHANISMS

Read the fixed IPv6 header

02

The common IPv6 header is 40 octets. Its fields describe the packet and identify the next header.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 3 ↗
RFC 8200 · § 3EXAMPLE
3 / 3
Read the fixed IPv6 headerEndpoint address fields and the Next Header link become explicit parts of the packet layout.FIXED IPv6 HEADER · 40 octetsv6Traffic ClassFlow LabelPayload LengthNext HeaderHop LimitSource · 128 bitsDestination · 128 bitsextension or transportSchematic field layout; widths are not to bit scale
03
Interpret the payload.

Use Next Header rather than assuming the payload begins directly with TCP or UDP.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

A small fixed header starts a potentially longer chain.

  • The version field is 6; source and destination addresses are each 128 bits.
  • Payload Length counts the bytes after the IPv6 base header, including extension headers.
  • Next Header identifies an extension header or an upper-layer protocol; Hop Limit bounds forwarding.
DETAILS

The payload-length field has special handling for jumbograms specified separately. The schematic is not drawn to bit scale.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Addresses identify interfaces
  2. Read the fixed IPv6 header
  3. Follow the next header chain
  4. Fit packets to the path
  5. Reassemble source fragments
  6. Forward with explicit limits
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗