From: Dave Taht <dave.taht@gmail.com>
To: "aqm@ietf.org" <aqm@ietf.org>
Cc: Vishal Misra <misra@cs.columbia.edu>,
bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] the cisco pie patent and IETF IPR filing
Date: Tue, 3 Mar 2015 22:07:43 -0800 [thread overview]
Message-ID: <CAA93jw4zZXGn_z2_dBBMsKN-XdwP88Wt-ChvfWJgCtp=J+i0rg@mail.gmail.com> (raw)
Two items:
A) The IETF IPR filing http://datatracker.ietf.org/ipr/2187/ points
to the wrong patent: 13/874,500. A google search for that patent
number brings up http://www.google.com/patents/US20130239255"
It is ironically relevant to the discussions at hand, as that one concerns:
Abstract:
"Provided are methods of increasing the tolerance of a plant to
abiotic stresses and/or increasing the biomass and/or increasing the
yield of a plant by expressing within the plant an exogenous
polynucleotide homologous to SEQ ID NO:13."
... As I consider myself a near-vegetable, and am 40 pounds heavier,
and not responding particularly well to antibiotics, after
participating for the past several years on all the ietf mailing lists
I just got off of. I am sure that upon acceptance of pie in the ietf,
that making that particular patent more generally available for all to
use would probably have similar effects on others.
The correct patent number for PIE, 13/874,600, is here:
http://www.google.com/patents/US20140328175
I would appreciate that the IPR filing be corrected.
In the meantime, here's some more great NSFW george carlin routines!
https://www.youtube.com/watch?v=tVlkxrNlp10
B) Vishal Misra (author of PI) gave me pointers to his PI papers
recently (and he had NO idea at all his work was used for pie! - he
got his marketing department to issue a press release about it:
http://engineering.umass.edu/news/got-bufferbloat-umass-amherst-research-behind-fix
)
I usually have a pretty strict policy about never reading patents, but
I read all those papers [1], and both! patents above. I had not fully
realized that the PI-AQM work went as far back as 2001. The PI update
equation and the PIE update equation, look pretty darn similar, just
the meanings of two variables, changed.
C) I am kind of curious if any working code for the original PI
algorithm exists for linux?
D) oh, never mind, I will blog about the rest one day.
[1] still prefer fq_codel.
--
Dave Täht
Let's make wifi fast, less jittery and reliable again!
https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
next reply other threads:[~2015-03-04 6:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 6:07 Dave Taht [this message]
[not found] ` <D11CA814.D0B3%ropan@cisco.com>
2015-03-04 23:37 ` [Bloat] [aqm] " Dave Taht
[not found] ` <473265656416337848@unknownmsgid>
[not found] ` <D11C0740.3B84%kk@cs.ucr.edu>
2015-03-04 9:42 ` David Lang
2015-03-05 13:58 ` [Bloat] " Dave Taht
2015-03-06 19:46 ` Vishal Misra
[not found] ` <4077D77B-6C1A-47DF-989C-76B4B99AF863@icloud.com>
2015-04-09 19:24 ` [Bloat] [aqm] " Dave Taht
2015-04-09 19:27 ` Steinar H. Gunderson
2015-04-09 19:45 ` Dave Taht
2015-04-09 19:28 ` Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw4zZXGn_z2_dBBMsKN-XdwP88Wt-ChvfWJgCtp=J+i0rg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=misra@cs.columbia.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox