Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updated by:

RFC 9293

Authors:

A. Ramaiah
R. Stewart
M. Dalal

Stream:

IETF

Source:

tcpm (wit)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5961

Discuss this RFC: Send questions or comments to the mailing listtcpm@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5961

Abstract

TCP has historically been considered to be protected against spoofedoff-path packet injection attacks by relying on the fact that it isdifficult to guess the 4-tuple (the source and destination IPaddresses and the source and destination ports) in combination withthe 32-bit sequence number(s). A combination of increasing windowsizes and applications using longer-term connections (e.g., H-323 orBorder Gateway Protocol (BGP) [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.