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

Follow the next header chain

03

Extension headers form an ordered chain between the fixed header and the upper-layer payload.

Related RFCs and changes

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

DIAGRAM§ 4 ↗
RFC 8200 · § 4EXAMPLE
3 / 3
Follow the next header chainThe parser advances from the base header through two extensions to UDP.IPv6 base headerHop-by-Hop OptionsDestination OptionsUDP header + data606017orderNext Header links identify the next parserIllustrative legal chain; do not scan past headers
03
Reach the upper-layer protocol.

Only after the extension chain does the receiver reach the transport header.

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

Follow each Next Header value in order.

  • Extension headers are processed in their specified order, not by scanning ahead for a preferred header.
  • Hop-by-Hop Options, when present, immediately follows the IPv6 header; processing along the path depends on node configuration.
  • Other extension headers are generally processed at the destination identified by the IPv6 destination address.
DETAILS

An unknown option’s action bits determine whether to skip it or discard the packet, with conditional ICMP behavior. Header handling is not permission for arbitrary in-path insertion.

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 ↗