Date: Tue, 08 Mar 2005 00:17:14 +0900 (JST) From: Noritoshi Demizu <demizu@dd.iij4u.or.jp> To: freebsd-net@freebsd.org Subject: Why TCP_MAX_SACK == 3 ? Message-ID: <20050308.001714.41652371.Noritoshi@Demizu.ORG>
next in thread | raw e-mail | index | archive | help
In netinet/tcp.h, TCP_MAX_SACK is defined as follows. #define TCP_MAX_SACK 3 /* MAX # SACKs sent in any segment */ Shouldn't it be 4? If a peer node does not use TCP timestamps option, four SACK blocks can be sent. For example, if my memory serves correctly, Microsoft Windows does not use TCP timestamps option by default. By the way, currently, both window scale option and timestamps option are controled by one sysctl variable: net.inet.tcp.rfc1323. Wouldn't it be nice if each option had its own sysctl variable? Regards, Noritoshi Demizu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050308.001714.41652371.Noritoshi>