IETF Logo Mail Archive

Re: [codec] Fwd: I-D Action: draft-ietf-codec-opus-update-03.txt

"Mo Zanaty (mzanaty)" <mzanaty@cisco.com> Fri, 14 October 2016 20:39 UTC

Return-Path: <mzanaty@cisco.com>
X-Original-To: codec@ietfa.amsl.com
Delivered-To: codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF5B712957F for <codec@ietfa.amsl.com>; Fri, 14 Oct 2016 13:39:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.517
X-Spam-Level:
X-Spam-Status: No, score=-17.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.996, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tAsrSLI8Z3HJ for <codec@ietfa.amsl.com>; Fri, 14 Oct 2016 13:39:06 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A08CB129578 for <codec@ietf.org>; Fri, 14 Oct 2016 13:39:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3467; q=dns/txt; s=iport; t=1476477546; x=1477687146; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=RpsKm83wc/PB70UimMeOOO9LkrbbiYPP47Z2zruDhGc=; b=mSMRJUs8yMyoP90Aml0yJqkBSQ/1U5JXgrGi8wPP3bG9CQk9TP694bz3 eD6nQc8gFpQGiG4tvIYFXoJa/zCKlik3U11WXbca0/yPO5a4bDqWUG5Br Koc6AQXfU8XM2fpV9eqyyaWnFzIWYfh29hJgx8Byb37QsXAmwWekS+Z8t 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BtAQC8QQFY/4wNJK1cGgEBAQECAQEBAQgBAQEBgzwBAQEBAR1XfAeNLZcFlDiCCB0LhXoCghg4FAECAQEBAQEBAV4nhGEBAQEEAQEBNzQXBAIBCBEDAQIfECcLHQgCBAESiFIOww0BAQEBAQEBAQEBAQEBAQEBAQEghj2EVYomBZoGAYYniViBbk6EGYkghxCFaYN+AR42GzeCehyBU3KHNYEAAQEB
X-IronPort-AV: E=Sophos;i="5.31,346,1473120000"; d="scan'208";a="334401755"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 14 Oct 2016 20:39:05 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id u9EKd5EG023848 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 14 Oct 2016 20:39:05 GMT
Received: from xch-aln-005.cisco.com (173.36.7.15) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 14 Oct 2016 15:39:05 -0500
Received: from xch-aln-005.cisco.com ([173.36.7.15]) by XCH-ALN-005.cisco.com ([173.36.7.15]) with mapi id 15.00.1210.000; Fri, 14 Oct 2016 15:39:05 -0500
From: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
To: Jean-Marc Valin <jmvalin@jmvalin.ca>, "codec@ietf.org" <codec@ietf.org>
Thread-Topic: [codec] Fwd: I-D Action: draft-ietf-codec-opus-update-03.txt
Thread-Index: AQHSJlsBw5gLSVZzLE6At05vOW2i+Q==
Date: Fri, 14 Oct 2016 20:39:05 +0000
Message-ID: <D426B856.6580D%mzanaty@cisco.com>
References: <147275540488.32075.5908406792224056353.idtracker@ietfa.amsl.com> <fe060bab-0e31-ccfb-ce7e-a683beb6d445@jmvalin.ca>
In-Reply-To: <fe060bab-0e31-ccfb-ce7e-a683beb6d445@jmvalin.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.8.160830
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.226.203]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A7E74C1219C18D4B917F39851CD29869@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/codec/NnleFeXp-HItz-FW36xBljfwf7s>
Subject: Re: [codec] Fwd: I-D Action: draft-ietf-codec-opus-update-03.txt
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Fri, 14 Oct 2016 20:39:09 -0000

I would like to propose another option.

4) Add an informational note in the update draft that the codebase on
opus-codec.org has diverged, and may continue to diverge, from the code in
RFC 6716, without breaking normative bitstream compatibility.

This option seems sufficient and lightweight.

Mo (as individual contributor)

-----Original Message-----
From: codec <codec-bounces@ietf.org> on behalf of Jean-Marc Valin
<jmvalin@jmvalin.ca>
Date: Thursday, September 1, 2016 at 4:13 PM
To: "codec@ietf.org" <codec@ietf.org>
Subject: [codec] Fwd:  I-D Action: draft-ietf-codec-opus-update-03.txt

Hi,

I just uploaded a new version of the Opus draft. It adds fixes for two
decoder integer wrap-around issues discovered through fuzzing. None of
them is particularly frightening, but they still needed to be fixed. At
this point, I do not expect more fixes to this document -- please let me
know if you think I missed something.

I'm also realizing just how much the "current" codebase on
opus-codec.org has come to differ from the code in RFC6716. This
includes many many fixes and improvements to the encoder and fixed-point
decoder. Since they are not normative bitstream changes, they are not
included in this update draft. I think it would be nice to update the
IETF "reference implementation" of Opus to reflect the improvements.
That being said, I'm not sure what's the best way to do that. I can
think of several options:

1) An (informational?) RFC with updated based64 tarball containing the
newest version
2) A tarball of the new version uploaded as meeting material like the
original testvectors (where would we link to it?)
3) Somehow mirroring the opus-coder.org downloads on the IETF website

There's probably other options too. Any thoughts?

Cheers,

	Jean-Marc


-------- Forwarded Message --------
Subject: [codec] I-D Action: draft-ietf-codec-opus-update-03.txt
Date: Thu, 01 Sep 2016 11:43:24 -0700
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
CC: codec@ietf.org


A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Internet Wideband Audio Codec of the IETF.

        Title           : Updates to the Opus Audio Codec
        Authors         : Jean-Marc Valin
                          Koen Vos
	Filename        : draft-ietf-codec-opus-update-03.txt
	Pages           : 9
	Date            : 2016-09-01

Abstract:
   This document addresses minor issues that were found in the
   specification of the Opus audio codec in RFC 6716 [RFC6716].


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-codec-opus-update/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-codec-opus-update-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-codec-opus-update-03


Please note that it may take a couple of minutes from the time of
submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
codec mailing list
codec@ietf.org
https://www.ietf.org/mailman/listinfo/codec

_______________________________________________
codec mailing list
codec@ietf.org
https://www.ietf.org/mailman/listinfo/codec

v2.46.0 | Report a Bug | By Email | System Status