From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id DA9F021F8F9 for ; Fri, 30 Oct 2015 05:40:15 -0700 (PDT) Received: from u-089-d061.biologie.uni-tuebingen.de ([134.2.89.61]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0MePYV-1a7lv10oAh-00QCfQ; Fri, 30 Oct 2015 13:40:12 +0100 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Sebastian Moeller In-Reply-To: Date: Fri, 30 Oct 2015 13:40:12 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <87887DDA-5602-4A2F-9212-77E7214BA706@gmx.de> References: <5A86B264-B957-41D2-9E4C-D1F9C525A99F@gmx.de> To: =?windows-1252?Q?Dave_T=E4ht?= , cake@lists.bufferbloat.net X-Mailer: Apple Mail (2.1878.6) X-Provags-ID: V03:K0:5PcNNgsS1efHZqxQjmCDVS9NT+aCzSO7bxLUUaD9PiCW3Ufz2JH oWRpElG15hREXtchoxpDUjeA5PGvIIHmSHY+SGO2Y1yIdeVMIRkSxP/Dzlv7W0Og+YlyRhO bSJq3ihHeWMCROFXGCWAoahonqhBXoXFoURnb3frXbNbgNfo55V/goxATHKST4XTuLArRZV 4uvhJbX5D7kQ9/DI7gw7w== X-UI-Out-Filterresults: notjunk:1;V01:K0:qHFjo4FwjDw=:q00cA6y1q3e9FHhvywW26u MmFg1YO1K4KK3Ixd5Ju8Y3FjhRuRqYDpoMRpYurYinPAT6uP81GR0JBj6wYHTMqVwG6t3v3ET 3oEGxAl7R7MKb7EfQIFEzLenMnR9U/hG5cc5HjQHoqejA+WVh5YPGuUWwG8Ic7AuV2y/2Dz/W 5gG2h7iqoafqn7zgzuZh4msdqrWMo83DTFFBeJG0Ym19lW2dFf/x7Z87VCU60HrUz6AvadvqU QMTUxfEa/k/lKkA64RGC5tbGhmzzrAnnTOhWX06amlq8piUAVcKoMHt0OTRta/YRrtSrOro5S 9P2awlRLfh4+HQaLALxjDfoL1jATTZBNDBunGpAfkCy2TorjWzL2oRTQkll2sX6NrjhFrHKlX VcLp5MH7Atum1o+KFoQv4SVgPXROk3VC5UobRBOkev8uyc98RXgStTx0D3nEOr7F4DZ3MI1bn DdIeBv3xkyvTXFTeF0qAgVz5yhHPQHKU7dRHmm1B3V1A8Pg/2OYtXZ6EY04UxnKIomfuFGhDG 49/BMvOcqPJtltuU4OF3pa72E6kIbSgoUCqzDLRoZD6C5gQO26zPCs36W0620uGVBYvQB3uyE 7jkXP5inVFmu/MXhy1WruSVVLzfXo1tNuRxxkJoCWASs6YK48D4UFXpq6Hdw5K3jUBzNC2+oW lMtZw8WmeZCGIEIHGjLIBbZLgglTvsnjWOkBJpcd0nB26QAbiIPTTczJG26w/7RGsxTIewiCp JjZVqAjXbQpRpRijctwDuhNoFyDSNmhGGJQhFjEZxFSglj2JlPyei/6I9At7EyhwkJ09Cvc/X 1xJs6wu Subject: Re: [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:40:38 -0000 On Oct 30, 2015, at 13:35 , Dave Taht wrote: > publicly please for as many emails as possible. Argh, my old nemesis again Reply instead of Reply-All, sorry. It = will sink in but habit change slowly (which for good habits is a boon) >=20 > I will answer with that "diffserv support is totally new - wg's barely > concluded=94 Good point. But that also allows us to come up with something = completely new instead of modeling after older stuff that always kept = some legacy compatibility in mind. None of the existing schemes make too = much sense in a home network I believe, potentiay a wrong believe ;) Best Regards Sebastian >=20 >=20 > On Fri, Oct 30, 2015 at 8:29 AM, Sebastian Moeller = wrote: >> Hi Dave, >>=20 >>=20 >> On Oct 30, 2015, at 13:13 , Dave Taht wrote: >>=20 >>> I am still way behind on email, only reading things peripherally, = and >>> trying to keep to one subject per mail. >>>=20 >>> 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". >>>=20 >>> It was my hope, instead, that with ease we could add new models for >>> how to handle diffserv handling along existing htb based schemes. >>>=20 >>> I have long pursued every isp that I have contact with to talk about >>> their stuff, and none have responded. >>>=20 >>> We have not even tried to address vlans, for example... and probably = should. >>>=20 >>> 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. >>=20 >> Now I am puzzled, if that is our prediction we actrually = should go and make the diffserv scheme configurable in cake, but then = the discussion whether to expose target and limit are somewhat moot = given how much ABI we will be committing to ;) >>=20 >> Best Regards >> Sebastian >>=20 >>=20 >>>=20 >>> Dave T=E4ht >>> 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 >>> _______________________________________________ >>> Cake mailing list >>> Cake@lists.bufferbloat.net >>> https://lists.bufferbloat.net/listinfo/cake >>=20