Graceful close
10A FIN ends one direction after its earlier bytes. The peer can still send in the other direction.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 3.6 ↗
RFC 9293 · § 3.6EXAMPLE
5 / 5
05
Retain closing state.
This helps handle retransmitted FINs and separates connection incarnations.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Close the stream in order.
- FIN occupies sequence space and is acknowledged.
- A half-close can leave the reverse direction usable.
- The endpoint that completes the active-close path normally waits in TIME-WAIT for 2 MSL.
FIN and ACK can be combined with other traffic. The familiar four arrows are an illustrative case, not a required packet count.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy