From: Jamie Lokier <jamie@shareable.org>
To: Baruch Even <baruch@ev-en.org>
Cc: Stephen Hemminger <shemminger@osdl.org>,
"David S.Miller" <davem@davemloft.net>,
linux-net@vger.kernel.org, netdev@oss.sgi.com,
Douglas Leith <doug.leith@nuim.ie>
Subject: Re: [RFC INTRO 0/5] H-TCP congestion control
Date: Fri, 22 Apr 2005 04:15:10 +0100 [thread overview]
Message-ID: <20050422031510.GA13508@mail.shareable.org> (raw)
In-Reply-To: <426849C2.7000409@ev-en.org>
Baruch Even wrote:
> >>This patch is covered by a pending patent, a license is being worked on to
> >>enable the inclusion in Linux. Comments and suggestions on this are also
> >>solicited.
> >
> >
> >Has this changed?
>
> This has changed now. The code is now released under the GNU GPL v2,
> according to what I was told this effectively implies that any patent
> right that the university will have regarding this technology is
> effectively licensed for use with this code.
>
> Please let me know if there is anything else that we need to do to let
> the review and possible inclusion of our contribution to proceed.
The patents must be licensed for _all_ GPL v2 implementations of that
algorithm, not just in this specific code. (And it would be
friendlier if you granted a patent license for GPL v2 and later).
That's because it's necessary for derivative works to have the patent
license too, and derivative works includes taking the code and totally
rewriting it for a different operating system or a different
application.
Otherwise, section 7 of the GPL kicks in, and although you the authors
could distribute the code, nobody could _redistribute_ it because they
couldn't satisfy the requirements of section 7.
Also, just because you, the authors, are distributing the code under
GPLv2, that doesn't automatically grant a patent license (unless
that's the university's policy). The GPL does _not_ state that you
grant patent licenses by distributing the program. Rather, it
_forbids_ redistributing the code if a patent license does not permit
royalty-free distribution by all those who receive copies directly or
indirectly, and that's the situation in the absence of a patent
license being granted. You, as the authors, are exempt simply by
being the copyright holders and therefore not bound by the GPL terms
applying to your own code.
-- Jamie
next prev parent reply other threads:[~2005-04-22 3:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 16:07 [RFC INTRO 0/5] H-TCP congestion control Baruch Even
2005-03-11 16:08 ` [RFC PATCH 1/5] Implement H-TCP congestion control algorithm Baruch Even
2005-03-11 16:09 ` [RFC PATCH 2/5] Adjust alpha according to a function defined in HTCP Baruch Even
2005-03-11 16:10 ` [RFC PATCH 3/5] Adjust alpha to 2*(1-beta) Baruch Even
2005-03-11 16:11 ` [RFC PATCH 4/5] Adjust alpha according to RTT timing Baruch Even
2005-03-11 16:12 ` [RFC PATCH 5/5] Switch in/out of beta=minrtt/maxrtt by bandwidth Baruch Even
2005-03-11 17:42 ` [RFC INTRO 0/5] H-TCP congestion control Stephen Hemminger
2005-03-11 18:38 ` Baruch Even
2005-03-12 4:13 ` David S. Miller
2005-04-22 0:48 ` Baruch Even
2005-04-22 3:15 ` Jamie Lokier [this message]
2005-04-22 11:58 ` Baruch Even
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050422031510.GA13508@mail.shareable.org \
--to=jamie@shareable.org \
--cc=baruch@ev-en.org \
--cc=davem@davemloft.net \
--cc=doug.leith@nuim.ie \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
/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;
as well as URLs for NNTP newsgroup(s).