Re: [codec] Liaisons sent to ITU, 3gpp and ISO/IEC

Paul Coverdale <> Wed, 27 July 2011 19:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2462921F859E for <>; Wed, 27 Jul 2011 12:55:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.865
X-Spam-Status: No, score=0.865 tagged_above=-999 required=5 tests=[AWL=2.661, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Cu-9cSktxUK0 for <>; Wed, 27 Jul 2011 12:55:50 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 3F08321F8593 for <>; Wed, 27 Jul 2011 12:55:50 -0700 (PDT)
Received: from BLU0-SMTP66 ([]) by with Microsoft SMTPSVC(6.0.3790.4675); Wed, 27 Jul 2011 12:55:49 -0700
X-Originating-IP: []
X-Originating-Email: []
Message-ID: <BLU0-SMTP662AFD4A13216B7EBF9057D0350@phx.gbl>
Received: from PaulNewPC ([]) by BLU0-SMTP66.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 27 Jul 2011 12:55:47 -0700
From: Paul Coverdale <>
To: <>
References: <>
In-Reply-To: <>
Date: Wed, 27 Jul 2011 15:55:42 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcxMlL3LsqUSi2ItQna/luTVdFR1CQAAbAJw
Content-Language: en-us
X-OriginalArrivalTime: 27 Jul 2011 19:55:47.0707 (UTC) FILETIME=[2DAE44B0:01CC4C97]
Subject: Re: [codec] Liaisons sent to ITU, 3gpp and ISO/IEC
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Codec WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 27 Jul 2011 19:55:51 -0000

If I understand correctly, the latest version is the requirements document
is now -05?


>-----Original Message-----
>From: [] On Behalf
>Of Jonathan Rosenberg
>Sent: Wednesday, July 27, 2011 3:38 PM
>Subject: [codec] Liaisons sent to ITU, 3gpp and ISO/IEC
>This is to let folks know that we've just sent liaison statements to
>ITU, 3gpp and ISO/IEC informing them of our status and inviting comments
>on the Opus codec. The liaison text is the same (except for name of the
>SDO). Here is what was sent:
>The IETF codec work continues to make progress, and we wanted to give
>the ITU an update on our activities.
>The working group has three document deliverables - a requirements
>document, a guidelines document, and the actual codec specification. The
>codec working group has completed its specification of the requirements
>(, and this
>document has been passed to the IESG for consideration as an
>informational document. The codec working group initiated a working
>group last call (WGLC) on the guidelines document
>(  on July 6,
>2011. The WGLC period has ended, and the codec group will now proceed to
>incorporate any final comments and discussion arising from our
>face-to-face meeting at the Quebec City IETF the week of July 25, 2011.
>Work on the codec specification itself has progressed nicely. By working
>collaboratively, the group has combined aspects of CELT and SILK to
>produce Opus (
>Testing has taken place on this combined codec, including numerous
>listening tests, which you can find documented here
>( )  The
>bitstream has been unchanged for several months, and the design team
>believed the codec was complete by June 2011. Consequently, the codec
>group issued a WGLC for the codec on July 8, 2011. The document will
>also be discussed at the IETF meeting the week of July 25, 2011. The
>CODEC working group would like to invite experts from ITU-SG16 to
>provide any comments they might have on the document. The chairs will
>hold the document from being passed to the IESG for a period of 4 weeks,
>commencing today, awaiting any input from SG16 (and from anyone else, of
>It is also important to note that several IPR claims have been made
>against Opus, including one from Qualcomm
>. All but the Qualcomm license declarations grant royalty free access.
>The IETF, as a matter of policy, makes no judgment on the validity of
>patent claims made against its documents. Instead, it relies on
>individual contributors to make their own assessments, and then act on
>them accordingly.
>Jonathan D. Rosenberg, Ph.D.                   SkypeID: jdrosen
>Skype Chief Technology Strategist
>codec mailing list