Observe a lifetime expiry
04Time Exceeded distinguishes transit TTL expiry from fragment-reassembly timeout.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAMTime Exceeded Message ↗
RFC 792 · Time Exceeded MessageEXAMPLE
3 / 3
03
Return Time Exceeded to the source with identifying original bytes.
Return Time Exceeded to the source with identifying original bytes.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Type 11 code 0 describes TTL expiry in transit; code 1 describes fragment-reassembly timeout.
- Type 11 code 0 describes TTL expiry in transit; code 1 describes fragment-reassembly timeout.
- An error response is feedback, not a guaranteed end-to-end failure signal.
The drawing is a simplified worked example. Follow the linked RFC and its updates for implementation requirements.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy