From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 03ADA3CB3F for ; Thu, 8 Feb 2018 16:53:47 -0500 (EST) Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 346EE200A3; Thu, 8 Feb 2018 17:00:25 -0500 (EST) Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 2C98B806C2; Thu, 8 Feb 2018 16:53:47 -0500 (EST) From: Michael Richardson To: Dave Taht cc: bloat In-Reply-To: References: X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Subject: Re: [Bloat] vendor status-s for bufferbloat solutions X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Feb 2018 21:53:48 -0000 --=-=-= Content-Type: text/plain Dave Taht wrote: > It would be nice to have a set of official statements from vendors > regarding their bufferbloat solutions vis a vis the various RFCs > (notably rfc8290) before the ietf blog entry goes out. Years ago, I was trying to get ISOC's Deploy360 folks to help with doing this. > My interchange with the tomahawk 3 guy was fruitless. Apple's kind > of exited the router market. Cable manufacturers are obligated to > implement docsis-pie in 3.1. Microsoft has made a big push recently to > modernize their TCPs. A bunch of router makers did embrace fq_codel > (calling it various things like streamboost, adaptive qos, etc), and a > few calling it what it is notably evenroute, and ubnt in their > edgerouter products, sophos, all of lede/openwrt/asuswrt/etc... but > I'm still unaware of any implementations on ONTs, CMTSes, DSLAMs, DSL > firmwares, MOCA... > What I kind of envision is everybody here annoying their favorite > forums for their favorite product and asking what of the outputs of > the ietf aqm working group they planned to implement. Yeah... So I went through IETF types and through sales channels at one point, and despite knowing that companies in questions were working on solutions, nobody knew anything. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | network architect [ ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlp8xuoACgkQgItw+93Q 3WVpFQf/efN0eQQD3qmeK6tP+o3IpDbMYJQ6sx1eo0bWlLVrBzyCu9k9ZiOkc18o hk8ApqenTbxSQZQCv6fr+lgxzDAmls+gOXJYbcmNKMp+qetTp7EyTfV4h9Au+dnu xC/ZR/Vo3wb4P1M4r8R/HPQnJzFE2gykHIwO3H9ZxevVLMetlLJGecZL80MgUdle yLjtPYXmBMr1xjUeSWq7cGqzP8+9rmAHf7byT/3+RW+etpmB+oGfaGVwf64Z/A1K 75h6fvusrO5CclG35PjUm3cjvFmmsfaMSBNCbvr5LR9gSIumMlJpopaV8Hmvucoz WuovJJRLWUkml9ucUe9lSaPgxRpSbg== =+mzn -----END PGP SIGNATURE----- --=-=-=--