Parse IPv6 extension headers without assuming a fixed upper-layer offset

Use this document to resolve one bounded operational decision: Parse IPv6 extension headers without assuming a fixed upper-layer offset. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official RFC 8200 — Internet Protocol, Version 6 (IPv6) Specification from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

• IPv6 optional internet-layer headers form a Next Header chain, and the first value that is not an extension header identifies the following upper-layer header. The research record locates this support at Section 4 (IPv6 Extension Headers), Next Header chain.
• Except for Hop-by-Hop Options, extension headers are not processed, inserted, or deleted by transit nodes before the packet reaches its destination. The research record locates this support at Section 4 (IPv6 Extension Headers), transit processing rule.
• A destination must process extension headers strictly in their on-wire order and cannot scan ahead to process a later header first. The research record locates this support at Section 4 (IPv6 Extension Headers), destination processing order.

Only the traced statements above are asserted as source facts. Apply the review to address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains after confirming that the source and deployed context match.

What the source does not establish

This RFC evidence supports only the named network-protocol decision; it does not select vendor settings, topology, capacity, or an acceptable failure mode. A correct source interpretation can still be inapplicable to a particular design. Confirm DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring, ownership, and change authority instead of treating documented behavior as a deployment guarantee.

Applicability questions

• For source statement 1 at Section 4 (IPv6 Extension Headers), Next Header chain, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Section 4 (IPv6 Extension Headers), transit processing rule, which observable configuration, record, or test can confirm applicability here?
• For source statement 3 at Section 4 (IPv6 Extension Headers), destination processing order, which observable configuration, record, or test can confirm applicability here?
• Within address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains, which versions, roles, and configuration states define the review population?
• Could DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring invalidate the test, hide a failure, or change applicability?
• Who owns the decision, and which observation requires stopping, escalation, or rollback?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. Record the source location, examined part of address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains, observed and expected states, owner, and reason for deviation.

Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring. Handle credentials, keys, recovery data, and personal information through approved secure channels.

Verification and evidence

Build a reproducible chain from Section 4 (IPv6 Extension Headers), Next Header chain; Section 4 (IPv6 Extension Headers), transit processing rule; Section 4 (IPv6 Extension Headers), destination processing order to the observed environment. Useful domain evidence includes configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results; label every item with scope, timestamp, collector, and stable identifier.

Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.

Official references

• RFC 8200 — Internet Protocol, Version 6 (IPv6) Specification — RFC Editor / Internet Engineering Task Force