Forward with explicit limits
06Hop Limit changes at each forwarding node. Flow Label and Traffic Class express different treatment information.
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
03
Stop forwarding.
The next router discards the packet; Traffic Class or Flow Label does not override this limit.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Do not confuse forwarding metadata with a security guarantee.
- A forwarding node decrements Hop Limit by one and discards a packet whose Hop Limit reaches zero.
- Traffic Class and Flow Label are distinct fields; their detailed use is specified in other RFCs.
- IPv6 has no base-header checksum; upper-layer checksums use an IPv6 pseudo-header.
IPv6 alone does not guarantee confidentiality or authenticated peers. Security mechanisms require their own protocols and configuration.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy