[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

iLBC codec legal status



Hello All!
ILBC is a low-bitrate codec used in many OSS and commerciall
applications. However its legal status isn't clear at least for me.

Codec itself distributed in opensource form, but no publically
available tarball available exists. Instead of this, sources of
reference implementation can be accessed as an appendix to RFC 3951:

http://www.ietf.org/rfc/rfc3951.txt

Someone already extracted source from this RFC, and extracted sources
available as 3rd party library in many OSS voip projects, for example:

http://download.savannah.nongnu.org/releases/linphone/1.3.x/source/ilbc-rfc3951.tar.gz

The source has no explicit license but every file in tarball contains
the following header:

=================================
   /******************************************************************

       iLBC Speech Coder ANSI-C Source Code

       iLBC_encode.h

       Copyright (C) The Internet Society (2004).
       All Rights Reserved.

   ******************************************************************/
=================================

The RFC itself contains the following license banner:

=================================
Full Copyright Statement

   Copyright (C) The Internet Society (2004).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the IETF's procedures with respect to rights in IETF Documents can
   be found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at ietf-
   ipr ietf org 

=================================

At the iLBC site ( http://ilbcfreeware.org/ ) they mention that this
codec is FREE (meaning that no fee required), but under the following
license:

http://ilbcfreeware.org/documentation/gips_iLBClicense.pdf

=======================
  ll use of the Original Code (GIPS iLBC , and code provided by GIPS
as part of any related IETF Standard or draft standard) is
subject to the complete Global IP Sound iLBC Public License, IETF
Standard, Limited Commercial Use (the (License"). By
accessing the Original Code You agree to the License terms. PLEASE SEE
THE COMPLETE LICENSE BELOW FOR
ADDITIONAL TERMS. In general:
-     Personal, non-commercial use is generally permitted.
-     Commercialization is permitted with certain limitations; for
example, to ensure that every iLBC decoder can decode
      every iLBC-encoded payload, commercial "Deployment" must comply
with the applicable IETF Standard/draft, and the
      format of the bitstream may not be modified.
-     You are provided no warranty or support, and all liability is disclaimed.
-     You must register this license with GIPS prior to any commercial
Deployment.

=======================

Is it acceptable for inclusion into Fedora? If yes, then what sort of
license is this?
-- 
With best regards!


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]