From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mout.perfora.net", Issuer "Thawte SSL CA" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 36D2D21F529 for ; Sat, 23 Aug 2014 11:16:37 -0700 (PDT) Received: from J4 (175.sub-70-192-9.myvzw.com [70.192.9.175]) by mrelay.perfora.net (node=mreueus003) with ESMTP (Nemesis) id 0MSc3W-1WvvWg211o-00RZr4; Sat, 23 Aug 2014 20:16:36 +0200 From: "Jerry Jongerius" To: Date: Sat, 23 Aug 2014 14:16:48 -0400 Message-ID: <000001cfbefe$69194c70$3b4be550$@duckware.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac++/TegXjuC8IrxQVm08Xz1mNtBdA== Content-Language: en-us X-Provags-ID: V02:K0:cEhnPTk+uGaHRPTon+SfABtVvY6beBEQzRRsdgbLSur BvWHCD+v6rIUAgET+uIICOkWn6Dc5yOla27OXk0VYJpuvuW8TF gi8DKcl8k2OpY4r2hQOd85uBUt/JjMVmVK/5ix7lb065YKUh/p 6E5f6xWtYa5LBZKiJVrJ0BQb/iRoM+h/QpuudGfJ8p4lzvU0SF mMsMYF+Nr/pPqSlDmQwWbY2iFRMSloZ13kq0vOsfFVGRnJy7JG P4weQYCiGRLx0qVRugnTWMaOXwP9U2T3TZKL9bQ0SA8HsDIpbY HVl/inFSW7AzbV+/HyXhsLqgloCjpk8wUybjuFxJf5HC87bTq1 eGE/qxMu22lYuYKk86acbPmn3vMjOxbhVuBBOCQWm X-UI-Out-Filterresults: notjunk:1; Subject: [Bloat] The Dark Problem with AQM in the Internet? X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Aug 2014 18:16:37 -0000 Request for comments on: www.duckware.com/darkaqm The bottom line: How do you know which AQM device in a network intentionally drops a packet, without cooperation from AQM? Or is this in AQM somewhere and I just missed it?