The legal answer is “read the IPR disclosure at the IETF” and “read the copy write notice in the code”.  

I think that you will like what you find, though……. The broad intent is to fix the bloat problem in as many places as possible.

Bill VerSteeg

From: bloat-bounces@lists.bufferbloat.net [mailto:bloat-bounces@lists.bufferbloat.net] On Behalf Of Simon Barber
Sent: Friday, June 05, 2015 8:03 PM
To: Hironori Okano -X (hokano - AAP3 INC at Cisco); bloat@lists.bufferbloat.net; aqm@ietf.org
Cc: Rong Pan (ropan); Preethi Natarajan (prenatar)
Subject: Re: [Bloat] FQ-PIE kernel module implementation

Very cool. Does this mean that Cisco are not planning on enforcing any IP rights over PIE?

Simon

On 6/4/2015 3:06 PM, Hironori Okano -X (hokano - AAP3 INC at Cisco) wrote:

Hi all,

I’m Hironori Okano and Fred’s intern. 

I’d like to let you know that I have implemented FQ-PIE as a linux kernel module “fq-pie" and iproute2 for fq-pie.

This was done in collaboration with others at Cisco including Fred Baker, Rong Pan, Bill Ver Steeg, and Preethi Natarajan.

The source codes are in my github repository. I attached patch file “fq-pie_patch.tar.gz” to this email also.

I’m using the latest linux kernel (git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git)

fq-pie kernel module

https://github.com/hironoriokano/fq-pie.git

iproute2 for fq-pie

https://github.com/hironoriokano/iproute2_fq-pie.git

If you have any comments, please reach out to me.

Best regards,

Hironori Okano

hokano@cisco.com

_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat