From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vc0-x22f.google.com (mail-vc0-x22f.google.com [IPv6:2607:f8b0:400c:c03::22f]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id ADC7B21F299 for ; Sat, 23 Aug 2014 12:30:30 -0700 (PDT) Received: by mail-vc0-f175.google.com with SMTP id ik5so13412841vcb.6 for ; Sat, 23 Aug 2014 12:30:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=X/onhTnFifrAWNsi+gvkviwCVYQAxk+dCA/46i0baEQ=; b=pMzdLsHeDb5UJPLydjczvkuSSCG+hxnKVzWCYNgerWO9+SpPATdW3RR1Ax5XXkKFSw Oy7bdrxXnMOVa1epI5lSNOth5KNPX9jIAxpkUXCXmkPgkdtBH37HlhC4F8d0w+44vhjA oNXzO8qU8KG39kYXhhrrqalaC9APrFlg63l6nv+sEaYiyWyFI+KQhgu+usbdXnM8ouHk oHVAfzSrr5DyNgMdLvpfVEgCyNih5F954fAFnh2xjchGeWJu2Bb6lsLIsf2ygfaVihLu Le7c+DGtfgEYdr/Nszi1DY48QonNpHerfOrNhVBRQGckYpPJZ0IVfy9bm21ZYyR2hBTX 5xAQ== MIME-Version: 1.0 X-Received: by 10.52.119.229 with SMTP id kx5mr688093vdb.40.1408822229499; Sat, 23 Aug 2014 12:30:29 -0700 (PDT) Received: by 10.53.8.39 with HTTP; Sat, 23 Aug 2014 12:30:29 -0700 (PDT) Received: by 10.53.8.39 with HTTP; Sat, 23 Aug 2014 12:30:29 -0700 (PDT) In-Reply-To: <000001cfbefe$69194c70$3b4be550$@duckware.com> References: <000001cfbefe$69194c70$3b4be550$@duckware.com> Date: Sat, 23 Aug 2014 22:30:29 +0300 Message-ID: From: Jonathan Morton To: Jerry Jongerius Content-Type: multipart/alternative; boundary=047d7bdc99aa8a86f8050150fc71 Cc: bloat Subject: Re: [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 19:30:31 -0000 --047d7bdc99aa8a86f8050150fc71 Content-Type: text/plain; charset=UTF-8 There is no such indication, unless you examine the packets before and after each potential point. But you don't generally need one. It is enough to know that congestion exists somewhere on the path. - Jonathan Morton On 23 Aug 2014 21:17, "Jerry Jongerius" wrote: > 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? > > > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat > --047d7bdc99aa8a86f8050150fc71 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

There is no such indication, unless you examine the packets = before and after each potential point. But you don't generally need one= . It is enough to know that congestion exists somewhere on the path.

- Jonathan Morton

On 23 Aug 2014 21:17, "Jerry Jongerius"= ; <jerryj@duckware.com> wr= ote:
Request for comments on: www.duckware.com/darkaqm

The bottom line: How do you know which AQM device in a network intentionall= y
drops a packet, without cooperation from AQM?

Or is this in AQM somewhere and I just missed it?


_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net<= /a>
= https://lists.bufferbloat.net/listinfo/bloat
--047d7bdc99aa8a86f8050150fc71--