From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bifrost.lang.hm (lang.hm [66.167.227.134]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 3927F3B25E for ; Fri, 6 May 2016 15:14:17 -0400 (EDT) Received: from asgard.lang.hm (asgard.lang.hm [10.0.0.100]) by bifrost.lang.hm (8.13.4/8.13.4/Debian-3) with ESMTP id u46JEDGO015784; Fri, 6 May 2016 12:14:13 -0700 Date: Fri, 6 May 2016 12:14:13 -0700 (PDT) From: David Lang X-X-Sender: dlang@asgard.lang.hm To: Jonathan Morton cc: Stephen Hemminger , cake@lists.bufferbloat.net In-Reply-To: <26BC8860-0485-4052-A8AC-574737B878E6@gmail.com> Message-ID: References: <1462201620.5535.250.camel@edumazet-glaptop3.roam.corp.google.com> <1462205669.5535.254.camel@edumazet-glaptop3.roam.corp.google.com> <2D83E4F6-03DD-4421-AAE0-DD3C6A8AFCE0@gmail.com> <1577AB06-3C14-43D1-92AD-E37CEDCB8E11@gmail.com> <8F329CCB-038C-4EF4-A01D-DB8C093AE6B2@gmx.de> <20160506083114.0730d9f1@xeon-e3> <26BC8860-0485-4052-A8AC-574737B878E6@gmail.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="680960-363802473-1462562053=:1768" Subject: Re: [Cake] Fwd: [Codel] fq_codel_drop vs a udp flood X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2016 19:14:17 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --680960-363802473-1462562053=:1768 Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT On Fri, 6 May 2016, Jonathan Morton wrote: >> On 6 May, 2016, at 21:50, David Lang wrote: >> >> what IP id are you referring to? I don't remember any such field in the packet header. > > It’s the third halfword. half a word is hardly enough to be unique across the Internet, anything that small would lead to lots of attackes that inserted garbage data into threads. looking at the IP header, the minimum size header includes fragment offset, source and destination IP addresses, and I'd bet a lot of money that every fragment of TCP/UDP includes the port numbers as well because there is just not enough into in the 20 byte header to identify what it matches with. and I don't see this field you are talking about. http://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/ip-packet.html David Lang --680960-363802473-1462562053=:1768--