From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) (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 59B9F21F8F9 for ; Fri, 30 Oct 2015 05:13:47 -0700 (PDT) Received: by obbwb3 with SMTP id wb3so42469138obb.0 for ; Fri, 30 Oct 2015 05:13:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=tfAzfzDU7qLQKz8xIoZuC/R+mWquupK4VIvpSsqM8ak=; b=0m08tZ1JfqepIYwjYnExTgqA8OcC1K28CWyjEsFHxQHzxse/nl/qDHC1+doxjD9G4r VonKrUNXVzvf38IUCpS2lgb6DGC4dqQc5oUtrJm6UVHHY11Pw8rGvMMAUintfyGZMFrj lH1GkEk6kP+cKlEmcsVWL0/+mdCEqLJHSU7EvcR60iqP4IU6IgjtKBuBiztaT5OaZI9l nSYvShBPwzlV1Y5lwrBiPWQ2GRULZaxjyiz26D5Gi5QyVBdXxHxbHGFnGXNPVez9qLaf vCqusJtRr64fsiUEBCMLhy/YRrkIM0y/UWOsw0dOwmO+nPD+jVOZLJC29HcZvQP0Sw7s haaw== MIME-Version: 1.0 X-Received: by 10.182.108.129 with SMTP id hk1mr5269390obb.25.1446207227237; Fri, 30 Oct 2015 05:13:47 -0700 (PDT) Received: by 10.202.61.133 with HTTP; Fri, 30 Oct 2015 05:13:47 -0700 (PDT) Date: Fri, 30 Oct 2015 08:13:47 -0400 Message-ID: From: Dave Taht To: cake@lists.bufferbloat.net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [Cake] diffserv in cake X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.13 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, 30 Oct 2015 12:14:10 -0000 I am still way behind on email, only reading things peripherally, and trying to keep to one subject per mail. I have never thought the schemes we currently have in cake for diffserv will survive exposure to what ISPs and other users consider the "real world". It was my hope, instead, that with ease we could add new models for how to handle diffserv handling along existing htb based schemes. I have long pursued every isp that I have contact with to talk about their stuff, and none have responded. We have not even tried to address vlans, for example... and probably should= . However the API lets us add new models easily, and I am thus, certain, no matter what we deliver, that some big user will diss us as to what we got wrong, fix it internally, and end up with a conflicting api for whatever they deploy, and diss us for not intuiting their needs well enough. I'm prepared to live with that. Dave T=C3=A4ht I just invested five years of my life to making wifi better. And, now... the FCC wants to make my work, illegal for people to install. https://www.gofundme.com/savewifi