Security & the consolidated spec
12TCP checks sequence and connection state, but its base protocol does not encrypt or cryptographically authenticate application data.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 7 ↗
RFC 9293 · § 7EXAMPLE
4 / 4
04
Use TCP with the chosen security protocol.
Do not equate a completed TCP handshake with authenticated identity.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
RFC 793 + RFCs 6093 / 6528RFC 9293 § 5
RFC 9293 obsoletes these documents and incorporates their normative TCP requirements, accepted fixes, and additional later guidance. Earlier rationale remains useful.
Read the updated RFC section ↗Add the protection your threat model needs.
- TLS can protect application data carried over TCP; it does not authenticate TCP control flags.
- TCP-AO provides connection authentication and integrity, but not payload confidentiality.
- RFC 9293 consolidates RFC 793 and later normative updates, including urgent-pointer guidance and stronger ISNs.
RFC 9293 § 5 is the explicit change log. Appendix A contains implementation notes; it is not the version-change appendix.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy