From: Greg KH <greg@kroah.com>
To: Baruch Even <baruch@ev-en.org>
Cc: netdev@oss.sgi.com, Douglas Leith <doug.leith@nuim.ie>,
"David S.Miller" <davem@davemloft.net>
Subject: Re: [TCP 0/4] H-TCP patches on top of Stephens cc framework
Date: Fri, 6 May 2005 11:09:06 -0700 [thread overview]
Message-ID: <20050506180906.GA21461@kroah.com> (raw)
In-Reply-To: <20050506173729.20140.93205.37072@galon.ev-en.org>
On Fri, May 06, 2005 at 08:37:29PM +0300, Baruch Even wrote:
> This is a first post of the H-TCP framework on top of Stephens congestion
> control framework. Hopefully the use of the framework will make it easier to
> understand the logic of the H-TCP algorithm. It definitely helped me :-)
>
> The code is licensed under the GNU GPL v2, and according to that we know this
> gives an implicit patent license to users of this code. An explicit licensing
> to OSDL for the purpose of sub-licensing is in the works to alleviate any fear.
Why would OSDL have anything to do with "sub-licensing" a patent, unless
they want to make money off of it? Why not do what other companies have
done with GPL granted patents instead?
thanks,
greg k-h
next prev parent reply other threads:[~2005-05-06 18:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 17:37 [TCP 0/4] H-TCP patches on top of Stephens cc framework Baruch Even
2005-05-06 17:38 ` [PATCH TCP 1/4] Add undo callback to " Baruch Even
2005-05-06 17:39 ` [PATCH TCP 2/4] Implement H-TCP congestion control algorithm Baruch Even
2005-05-06 17:40 ` [PATCH TCP 3/4] Adjust alpha according to RTT timing Baruch Even
2005-05-06 17:41 ` [PATCH TCP 4/4] Switch out when bandwidth changes abruptly Baruch Even
2005-05-06 18:09 ` Greg KH [this message]
2005-05-09 23:22 ` [RFC] TCP congestion infrastructure Stephen Hemminger
2005-05-10 0:17 ` David S. Miller
2005-05-10 16:13 ` Stephen Hemminger
2005-05-10 14:06 ` Baruch Even
2005-05-10 14:31 ` Baruch Even
2005-05-10 16:11 ` Stephen Hemminger
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=20050506180906.GA21461@kroah.com \
--to=greg@kroah.com \
--cc=baruch@ev-en.org \
--cc=davem@davemloft.net \
--cc=doug.leith@nuim.ie \
--cc=netdev@oss.sgi.com \
/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).