Bug#664606: additional information
I noticed this site: http://www.webrtc.org/ilbc-freeware However I cannot find any license statement that applies to the iLBC reference implementation. Maybe you could use the iLBC implementation from WebRTC instead? It seems quite heavily modified from the reference implementation though. It is here: https://code.google.com/p/webrtc/source/browse/trunk/src/modules/audio_coding/codecs/ilbc/ Just some additional information. It seems likely that this problem can be resolved by putting some additional information in debian/copyright. /Simon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664606: additional information
Some even further information, as I seen that others have identified the problem, see for example: http://yate.null.ro/mantis/view.php?id=295 There exists a libilbc library with a clear license here: https://github.com/dekkers/libilbc It is labeled as a drop-in replacement for the non-free code in RFC 3591. /Simon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664606: additional information
On Mon, 19 Mar 2012 21:32:09 Simon Josefsson wrote: I noticed this site: http://www.webrtc.org/ilbc-freeware Simon, In 2006 you filed the same bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393402 Since then we have _not_ shipped ilbc in Debian, until this year when Google purchased iLBC from GlobalIP solutions and re-licensed. We should perhaps include something in the debian/copyright saying this is now free. Mark signature.asc Description: This is a digitally signed message part.
Bug#664606: additional information
Faidon Liambotis parav...@debian.org writes: On 03/19/12 13:28, Simon Josefsson wrote: Some even further information, as I seen that others have identified the problem, see for example: http://yate.null.ro/mantis/view.php?id=295 There exists a libilbc library with a clear license here: https://github.com/dekkers/libilbc It is labeled as a drop-in replacement for the non-free code in RFC 3591. The iLBC code in RFC 3591 was freed when the company that original authored it (GIPS) was acquired by Google. See e.g. https://datatracker.ietf.org/ipr/1649/ Hi! That is only the patent license, right? I don't see anything about the copyright and license of the code. There are multiple people who have extracted this code from the RFC and either included it as-is in their source trees or created libraries out of it. Under what license? I didn't check the one you pointed at, but I'm fairly sure it'll be the exact same code. No, it uses the code from WebRTC which appears to be different from the code in the RFC. The best solution (but I'm not speaking as a maintainer, since I haven't been doing that for the VoIP team for quite some time) would be to package one of these libraries and port all the software the uses it to use that. Licensing-wise it won't make a big difference (besides a proper debian/copyright), but it'll help to reduce code duplication and security response. That sounds like a good idea. /Simon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664606: additional information
On 03/19/12 13:28, Simon Josefsson wrote: Some even further information, as I seen that others have identified the problem, see for example: http://yate.null.ro/mantis/view.php?id=295 There exists a libilbc library with a clear license here: https://github.com/dekkers/libilbc It is labeled as a drop-in replacement for the non-free code in RFC 3591. The iLBC code in RFC 3591 was freed when the company that original authored it (GIPS) was acquired by Google. See e.g. https://datatracker.ietf.org/ipr/1649/ There are multiple people who have extracted this code from the RFC and either included it as-is in their source trees or created libraries out of it. I didn't check the one you pointed at, but I'm fairly sure it'll be the exact same code. The best solution (but I'm not speaking as a maintainer, since I haven't been doing that for the VoIP team for quite some time) would be to package one of these libraries and port all the software the uses it to use that. Licensing-wise it won't make a big difference (besides a proper debian/copyright), but it'll help to reduce code duplication and security response. Best regards, Faidon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664606: additional information
Mark Purcell m...@purcell.id.au writes: On Mon, 19 Mar 2012 21:32:09 Simon Josefsson wrote: I noticed this site: http://www.webrtc.org/ilbc-freeware Simon, In 2006 you filed the same bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393402 Since then we have _not_ shipped ilbc in Debian, Hi Mark. Thanks for taking care of that, btw! until this year when Google purchased iLBC from GlobalIP solutions and re-licensed. Do you have a pointer to this re-licensing? With text that affects the code license. I have so far only seen: 1) A statement about freeing the patent license 2) The WebRTC project under a BSD-like license with a iLBC implementation However the code in Asterisk/H323plus is using the code from the RFC which is still non-free unless we can point to something saying anything else. We should perhaps include something in the debian/copyright saying this is now free. Right. I checked the WebRTC svn repo, and the iLBC stuff was added in revision 4 but it is not the RFC code but modified. Thanks, /Simon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
