From: Dave Taht <dave.taht@gmail.com>
To: Battle of the Mesh Mailing List <battlemesh@ml.ninux.org>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] fighting some mesh related patents?
Date: Fri, 21 Jun 2013 11:53:02 -0700 [thread overview]
Message-ID: <CAA93jw6wM=vmB=vBawaXWZMHVnFgT53dN_g75SsLCnc=fx4iVQ@mail.gmail.com> (raw)
I don't read patents as a rule...
... but I was just informed that the eff is attempting to engage with
defeating 3 overbroad mesh related - and newly filed - patents. So if
anyone has any prior art that can help here, here's a link to what the
EFF is up to:
https://www.eff.org/deeplinks/2013/06/mesh-networking-good-overbroad-patents-bad
Beating patent #7035281 took 3 years, and far more of my time than I
wanted to give it, and millions of dollars (thankfully not mine). I
strongly feel I've done enough time in that barrel. (I get nervous
today even reading a paper on a technology that was ultimately
patented, and we tried really hard to make sure codel went out the
door unpatented and unpatentable. Lawyers scare me)
I have been meaning to write up the successful conclusion to that
7035281 story (
http://the-edge.blogspot.com/2010/10/who-invented-embedded-linux-based.html
before the lawyers read slashot ) since litigation was completed a
year or so back, but at the prospect of sorting through a 12 foot high
stack of documents and the judge's basis for the decision is too
depressing.
I AM encouraged that the US patent system has this newfangled
pre-review process and if anyone has a suggestion as to what I can and
can't legally read in the US anymore without inducing liabilities I'd
love to know.
In the meantime perhaps there's prior art in the mesh community to
help out the EFF. (please contact them directly). My fear is that much
of the work has taken place outside of the US, and in forms that the
patent office doesn't consider as useful prior art.
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
reply other threads:[~2013-06-21 18:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6wM=vmB=vBawaXWZMHVnFgT53dN_g75SsLCnc=fx4iVQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=battlemesh@ml.ninux.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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