Re: [codec] WG Review: Internet Wideband Audio Codec (codec)

Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca> Mon, 11 January 2010 18:23 UTC

Return-Path: <Jean-Marc.Valin@USherbrooke.ca>
X-Original-To: codec@core3.amsl.com
Delivered-To: codec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C4C013A67AE; Mon, 11 Jan 2010 10:23:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0tyx3MATPZ1B; Mon, 11 Jan 2010 10:23:36 -0800 (PST)
Received: from smtpi5.usherbrooke.ca (smtpi5.USherbrooke.ca [132.210.236.1]) by core3.amsl.com (Postfix) with ESMTP id B758B3A67B5; Mon, 11 Jan 2010 10:23:36 -0800 (PST)
Received: from localhost (www03.USherbrooke.ca [132.210.244.10]) by smtpi5.usherbrooke.ca (8.13.8/8.13.8) with ESMTP id o0BIMvJ0003206; Mon, 11 Jan 2010 13:22:57 -0500
Received: from mail.octasic.com (mail.octasic.com [70.54.254.106]) by www.usherbrooke.ca (IMP) with HTTP for <valj1901@courriel-fec.usherbrooke.ca>; Mon, 11 Jan 2010 13:22:57 -0500
Message-ID: <1263234177.4b4b6c81b3dad@www.usherbrooke.ca>
Date: Mon, 11 Jan 2010 13:22:57 -0500
From: Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca>
To: Stephan Wenger <stewe@stewe.org>
References: <C770BF68.1EA6B%stewe@stewe.org>
In-Reply-To: <C770BF68.1EA6B%stewe@stewe.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.6
X-Originating-IP: 70.54.254.106
X-UdeS-MailScanner-Information: Veuillez consulter le http://www.usherbrooke.ca/vers/virus-courriel
X-MailScanner-ID: o0BIMvJ0003206
X-UdeS-MailScanner: Aucun code suspect détecté
X-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (not cached, score=-7.499, requis 5, autolearn=not spam, BAYES_00 -2.60, RDNS_NONE 0.10, UDES_MONBUREAU01 -5.00)
X-UdeS-MailScanner-From: jean-marc.valin@usherbrooke.ca
Cc: codec@ietf.org, ietf@ietf.org, iesg@ietf.org
Subject: Re: [codec] WG Review: Internet Wideband Audio Codec (codec)
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Should the IETF standardize wideband Internet codec\(s\)? " <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codec>
List-Post: <mailto:codec@ietf.org>
List-Help: <mailto:codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2010 18:23:37 -0000

Sorry, my "has been shown" statement was about "making something much better
than G.722/G.711". The IPR part is something that would need to be discussed
within a future WG (subject to BCP79 and all).

   Jean-Marc

Quoting Stephan Wenger <stewe@stewe.org>:

> Hi Jean-Marc,
>
> I don't think anything "has been shown", with respect to IPR and RF
> properties of the current input proposal documents.  And I don't believe
> anything conclusive will be shown, ever.  At best, arguably, nothing
> substantial has been shown against an RF claim of the input proposals.
> Arguably", because the Skype assurance in
> https://datatracker.ietf.org/ipr/1164/ is hardly a strongly worded, binding,
> non-assert or license.
>
> Theoretically, even the 23 year timeframe (of publication of G.722) does not
> (yet) provide full certainty under US law against patent encumbrances;
> though the position of a G.722 user is probably very strong now.  Look up
> "prosecution laches" if you want to know how I came to these conclusions.
>
> I completely agree that we should not exclusively rely on 20 year old
> technologies on a mission to "make the Internet work better", not even on
> the grounds of patent fears.  Expect me to use this argument occasionally
> :-)
>
> Stephan
>
>
> On 1/11/10 7:32 AM, "Jean-Marc Valin" <Jean-Marc.Valin@USherbrooke.ca>
> wrote:
>
> > Hi,
> >
> > Regardless of the exact status of the PLC IPR, I don't think it would be a
> > good
> > idea to just say that "the Internet should just follow ITU-T standards with
> a
> > 20-year lag". As it has been already shown with the codec proposals
> received
> > to
> > date, it should be possible to create RF codecs that are *much* better than
> > G.722 and G.711.
> >
> >    Jean-Marc
> >
> > Quoting Steve Underwood <steveu@coppice.org>:
> >
> >> On 01/11/2010 11:00 PM, Christian Hoene wrote:
> >>> Dear Herve Taddei,
> >>>
> >>>
> >>>> Besides, I don't think you would have any trouble to propose at ITU-T
> some
> >>>> new appendices to G.711 and G.722 that could fit your goals. An appendix
> >> is
> >>>> non normative (a bit like the informative reference to G.711 PLC in
> iLBC).
> >>>> By the way, if I am not wrong, some basic ITU-T G.722 PLCs are RF.
> >>>>
> >>> This was my understanding, too.
> >>>
> >> The G.722 spec is 23 years old, so it would be difficult for any of the
> >> patents on that spec to still be valid. The ITU patent database does
> >> list US patent 5528629 as related to G.722, but I assume this is an
> >> error. The patent dates from so long after G.722 came out, and its
> >> contents do not appear relevant to G.722. However, the recent additions
> >> for PLC are:
> >>
> >>      G.722 (1988) App IV - Broadcom has claims
> >>      G.722 Appendix III - Broadcom has claims
> >>      G.722 Appendix IV - France Telecom has claims.
> >>
> >> Have you seen any clear statements that those patents may be used
> >> royalty free?
> >>
> >> Steve
> >>
> >> _______________________________________________
> >> codec mailing list
> >> codec@ietf.org
> >> https://www.ietf.org/mailman/listinfo/codec
> >>
> >>
> >
> >
> >
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>