RFC 5961: Improving TCP's Robustness to Blind In-Window Attacks
In plain English — editorial summary, not part of the RFC
TCP has historically been considered to be protected against spoofed off-path packet injection attacks by relying on the fact that it is difficult to guess the 4-tuple (the source and destination IP addresses and the source and destination ports) in combination with the 32-bit sequence number(s). A combination of increasing window sizes and applications using longer-term connections (e.g., H-323 or Border Gateway Protocol (BGP) [STANDARDS-TRACK]
Document record
- Document ID
- RFC5961
- Published
- August 2010
- Authors
- A. Ramaiah; R. Stewart; M. Dalal
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 19
- Also known as
- —
- Updated by:
- RFC 9293
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5927ICMP Attacks against TCPCurrent
July 2010
- RFC 7739Security Implications of Predictable Fragment Identification ValuesCurrent
February 2016
- RFC 9416Security Considerations for Transient Numeric Identifiers Employed in Network ProtocolsCurrent
July 2023
- RFC 6056Recommendations for Transport-Protocol Port RandomizationCurrent
January 2011
- RFC 4953Defending TCP Against Spoofing AttacksCurrent
July 2007
- RFC 8768Constrained Application Protocol (CoAP) Hop-Limit OptionCurrent
March 2020
- RFC 9414Unfortunate History of Transient Numeric IdentifiersCurrent
July 2023
- RFC 9415On the Generation of Transient Numeric IdentifiersCurrent
July 2023
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?