netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Baruch Even <baruch@ev-en.org>
To: Jamie Lokier <jamie@shareable.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 12:58:04 +0100	[thread overview]
Message-ID: <4268E6CC.6060703@ev-en.org> (raw)
In-Reply-To: <20050422031510.GA13508@mail.shareable.org>

Jamie Lokier wrote:
> 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.
 >
 > [snipped]

We are trying to get this sorted in the proper way, even as authors the 
issue here is also of dealing with the university bureaucracy so we'd 
prefer to avoid that and the associated paperwork as much as possible.

Is more paperwork/licenses really necessary?

What is it that we need to provide for this contribution to be 
acceptable for the kernel? Specifics please.

David, Can you comment on this and say if what was provided so far is 
sufficient to be accepted and if not what is needed?

Thanks,
Baruch

      reply	other threads:[~2005-04-22 11:58 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
2005-04-22 11:58       ` Baruch Even [this message]

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=4268E6CC.6060703@ev-en.org \
    --to=baruch@ev-en.org \
    --cc=davem@davemloft.net \
    --cc=doug.leith@nuim.ie \
    --cc=jamie@shareable.org \
    --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).