From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw0-f52.google.com (mail-yw0-f52.google.com [209.85.213.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id BCC8A202224 for ; Wed, 11 Jul 2012 09:56:36 -0700 (PDT) Received: by yhpp61 with SMTP id p61so1669298yhp.11 for ; Wed, 11 Jul 2012 09:56:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=rgEx2a6MpcS7l1jdmbcwCZ2wiUMn0vaTGCo7g0beG0I=; b=XzGPuDS37AIJM6aRBp79fYC3WWXUsUjyNFuVYER6VJB367rPevGp824VeD2/BSVoEU a65lyakv+yzLyN9x8VzrfxheAAV+9rHN2NkiuOzfpK9OdeDGBJLDZujDLy8rXCiq9rYE EIpmDhkLBrDwN08N4IyuBrptbs9MHKylYvR0G9ZjpSNM9cnRyUSyoXvJa0ykiI9a4arm NFr5yMidLixy5oGuXE1K5waypvlrOLtetHEaIsH8CyvUp6EG3R/LtXF/IwiJAP5mBIEZ LxTHrXdFsXdJTyyfteTbILfNY9RE2vovpthD3XAK8Rr1H5tPsT4Tla6a4cIBE6Tg0kej C1xA== MIME-Version: 1.0 Received: by 10.42.87.75 with SMTP id x11mr25787643icl.25.1342025795427; Wed, 11 Jul 2012 09:56:35 -0700 (PDT) Received: by 10.64.31.106 with HTTP; Wed, 11 Jul 2012 09:56:35 -0700 (PDT) X-Originating-IP: [77.65.42.82] In-Reply-To: References: Date: Wed, 11 Jul 2012 18:56:35 +0200 Message-ID: From: Maciej Soltysiak To: Dave Taht Content-Type: multipart/alternative; boundary=bcaec539650cd0de8f04c490ba37 X-Gm-Message-State: ALoCoQnumJT1z13UKABfj6Rn5dm5TxJ64O1G5jrNfd0sZQL+VteFx9PDmUYl7iCkGTotNNRVkDJO Cc: bloat-announce@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net, bloat Subject: Re: [Cerowrt-devel] Cerowrt 3.3.8-10 is released X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2012 16:56:37 -0000 --bcaec539650cd0de8f04c490ba37 Content-Type: text/plain; charset=UTF-8 Hi Dave, Thanks for a good, lengthy update. I wish you pleasant time travelling. One question on ECN though. On Tue, Jul 10, 2012 at 3:43 AM, Dave Taht wrote: > - ECN dropping - after several high level conversations with many > people smarter than me, I decided that dropping ECN packets at a > certain point made sense. So did everyone else. The "certain point" > remains puzzling to all, and > rather than continue to waste time on it in cero I decided to play > with models instead, and frankly, hope that someone else comes up with > some sane way to combine ECN and codel sojourn time. So if we're dropping ECN packets and not of trying to allow them through to communicate congestion am I better of enabling ECN on clients on my network or not? Regards, Maciej --bcaec539650cd0de8f04c490ba37 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Dave,
=C2=A0
Thanks for a good, lengthy update. I wish you pleasant time travelling= .
=C2=A0
One question on ECN though.

On Tue, Jul 10, 2012 at 3:43 AM, Da= ve Taht <dave.taht@gmail.com> wrote:
- ECN dropping - after several high l= evel conversations with many
people smarter than me, I decided that drop= ping ECN packets at a
certain point made sense. So did everyone else. The "certain point&quo= t;
remains puzzling to all, and
rather than continue to waste time on= it in cero I decided to play
with models instead, and frankly, hope tha= t someone else comes up with
some sane way to combine ECN and codel sojourn time.
So if we're dropping ECN packets and not of trying to allow them t= hrough to communicate congestion am I better of enabling ECN on clients on = my network or not?
=C2=A0
Regards,
Maciej
--bcaec539650cd0de8f04c490ba37--