ACM SIGCOMM Computer Communication Review Association for Computing Machinery For example, in one example, a host sends fewer TCP SACK blocks then it could in another one, a host does not include SACK information in FIN segments. In fact, as all reviewers pointed out, most of these misbehaviors are due to the lack of (or incorrect) implementation of SHOULD clauses in several RFCs. Seven out of the eight misbehaviors discussed do not affect correctness, and the eight one manifests only in Solaris and OpenSolaris. The good news is that newer versions of each OS had less misbehaviors than older ones. The bad news is that most operating systems exhibit one or more of these misbehaviors. After describing the misbehaviors, the paper uses TBIT to implement a number of tests to detect whether these misbehaviors appear in Windows, Linux, Mac OSX, FreeBSD, OpenBSD, Solaris, and OpenSolaris. The misbehaviors were first identified in a study of CAIDA TCP traffic traces that the authors conducted in previous work.
Amer This paper presents a study of eight misbehaviors in TCP SACK generation in TCP/IP stacks in commodity operating systems.
Public Review for Misbehaviors in TCP SACK Generation Nasif Ekiz, Abuthahir Habeeb Rahman, and Paul D. Misbehaviors in TCP SACK generation Misbehaviors in TCP SACK generationĮkiz, Nasif Rahman, Abuthahir Habeeb Amer, Paul D.
0 kommentar(er)
