Re: [codec] WG: [87all] IETF 87 Technical Plenary Experiment

"Christian Hoene" <> Mon, 22 July 2013 21:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7103B11E80D3 for <>; Mon, 22 Jul 2013 14:10:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.664
X-Spam-Status: No, score=-1.664 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_19=0.6]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id oJikHfWhs0G2 for <>; Mon, 22 Jul 2013 14:10:50 -0700 (PDT)
Received: from ( []) by (Postfix) with SMTP id E36C311E8145 for <>; Mon, 22 Jul 2013 14:10:49 -0700 (PDT)
Received: (qmail 31475 invoked by uid 0); 22 Jul 2013 21:10:24 -0000
Received: from unknown (HELO ( by with SMTP; 22 Jul 2013 21:10:24 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;; s=default; h=Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:Cc:To:From; bh=zkWsn+zfZUDdE2NI0EBJR4DlsDEc/28nYHb/JX7nEH8=; b=H7JodxZ22pFc2xg8CVSkdPttUvRBStJWfA4xDtJiVcX10ftMbls7GNPQhYbbdG5PM4H+G0OsQvY6j2cfT3nKTR2A8szkrz88c6VkZErK2ImerFHcxwg5nhBWLvSso6bv;
Received: from [] (port=49731 helo=samsung7PC) by with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.80) (envelope-from <>) id 1V1NN9-0003KG-Jj; Mon, 22 Jul 2013 15:10:24 -0600
From: "Christian Hoene" <>
To: "'Christian Hoene'" <>, <>
References: <> <> <005901ce871a$fe569670$fb03c350$>
In-Reply-To: <005901ce871a$fe569670$fb03c350$>
Date: Mon, 22 Jul 2013 23:10:25 +0200
Message-ID: <002901ce871f$e3ee8a40$abcb9ec0$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_002A_01CE8730.A779F250"
X-Mailer: Microsoft Outlook 14.0
thread-index: AQGDWZZoVivfV8W0ZMjljpwueGLImQFtquHEAqZ09C4BAejRrQ==
Content-Language: de
X-Identified-User: {} {sentby:smtp auth authed with}
Subject: Re: [codec] WG: [87all] IETF 87 Technical Plenary Experiment
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: Mon, 22 Jul 2013 21:10:55 -0000

Hi Guys,


for the technical plenary, it would be useful to present at least some of
the test results made my third parties, such as Google.


For course, we have also some thousands of mushra results in an excel  that
just wait to be added to the opus-quality-draft. We will send them to the
mailing list as an input.


With best regards,


Christian Hoene







Von: [] Im Auftrag von
Christian Hoene
Gesendet: Montag, 22. Juli 2013 22:35
Betreff: [codec] WG: [87all] IETF 87 Technical Plenary Experiment


-------- Original-Nachricht -------- 


[87all] IETF 87 Technical Plenary Experiment


Mon, 22 Jul 2013 13:15:23 -0700


IAB Chair  <> <>

Antwort an:



The OPUS codec, defined in RFC 6716, can scale from low bit-rate 
narrowband speech to very high quality stereo music, making it suitable 
for a wide range of audio applications. The IETF 87 Technical Plenary 
session will cover the past and future of Opus as well as the lessons 
learned from the standardization process that could apply to future IETF 
To provide additional materials relating to the plenary topic, the IAB 
has created a wiki. If you have material relevant to the plenary topic 
(such as papers or test data relating to OPUS), please contribute it to 
the wiki, either by editing it yourself, or sending it to the IAB 
<iab at>.
Also, during the IETF 87 Technical Plenary, the MeetEcho team will be 
running an experiment to enable remote participation in the Technical 
Plenary using the OPUS codec.  Information on how to access on the 
Remote Participation experiment is also available on the IAB wiki page:
On behalf of the IAB,
  Russ Housley
  IAB Chair
87all mailing list