From owner-freebsd-security Tue Jul 10 2:39:43 2001 Delivered-To: freebsd-security@freebsd.org Received: from caligula.anu.edu.au (caligula.anu.edu.au [150.203.224.42]) by hub.freebsd.org (Postfix) with ESMTP id DFDA937B435 for ; Tue, 10 Jul 2001 02:39:05 -0700 (PDT) (envelope-from avalon@caligula.anu.edu.au) Received: (from avalon@localhost) by caligula.anu.edu.au (8.9.3/8.9.3) id TAA13064; Tue, 10 Jul 2001 19:38:59 +1000 (EST) From: Darren Reed Message-Id: <200107100938.TAA13064@caligula.anu.edu.au> Subject: Re: FW: Small TCP packets == very large overhead == DoS? To: crist.clark@globalstar.com (Crist Clark) Date: Tue, 10 Jul 2001 19:38:59 +1000 (Australia/ACT) Cc: freebsd-security@FreeBSD.ORG In-Reply-To: <3B4A53D7.287F47AF@globalstar.com> from "Crist Clark" at Jul 09, 2001 06:01:11 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In some mail from Crist Clark, sie said: > > The TCP segment is everything in the IP payload. An SYN segment is a > TCP segment, but it carries no data and has a segment length of one (whee!). > I can see that clearly in the RFC, and I think we all cab agree on that. > However, I think that a SYN segment, which is all header, has a size greater > than one. It looks more like 24-or-so bytes typically... or maybe it does not. > I am looking for where (if anywhere) the specification comes out and says > that segment "size" is the same as "length." Why isn't the MSS called the MSL > after the RFC has gone to such pains to define "length?" Why can't a SYN segment be a TCP segment of length 0 ? (with one phantom byte) Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message