From nobody Fri Oct 14 13:39:10 2016 Return-Path: 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 ; 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 ; 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 ; 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: =?us-ascii?q?A0BtAQC8QQFY/4wNJK1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgzwBAQEBAR1XfAeNLZcFlDiCCB0LhXoCghg4FAECAQEBAQEBAV4nhGE?= =?us-ascii?q?BAQEEAQEBNzQXBAIBCBEDAQIfECcLHQgCBAESiFIOww0BAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEghj2EVYomBZoGAYYniViBbk6EGYkghxCFaYN+AR42GzeCehyBU3KHNYE?= =?us-ascii?q?AAQEB?= 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)" To: Jean-Marc Valin , "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: References: <147275540488.32075.5908406792224056353.idtracker@ietfa.amsl.com> In-Reply-To: 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: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 on behalf of Jean-Marc Valin Date: Thursday, September 1, 2016 at 4:13 PM To: "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=3Ddraft-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 From nobody Tue Oct 18 16:13:44 2016 Return-Path: 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 5A1CE129417 for ; Tue, 11 Oct 2016 18:25:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.598 X-Spam-Level: X-Spam-Status: No, score=-105.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no 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 4YPx_zCniIEQ for ; Tue, 11 Oct 2016 18:25:26 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DBB61296B3 for ; Tue, 11 Oct 2016 18:25:26 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 77898B8002B; Tue, 11 Oct 2016 18:25:26 -0700 (PDT) To: jmvalin@jmvalin.ca, koenvos74@gmail.com, tterriberry@mozilla.com, ben@nostrum.com, alissa@cooperw.in, aamelnikov@fastmail.fm, tterriberry@mozilla.com, mzanaty@cisco.com X-PHP-Originating-Script: 30:errata_mail_lib.php From: RFC Errata System Message-Id: <20161012012526.77898B8002B@rfc-editor.org> Date: Tue, 11 Oct 2016 18:25:26 -0700 (PDT) Archived-At: X-Mailman-Approved-At: Tue, 18 Oct 2016 16:13:43 -0700 Cc: 0f1ac5@gmail.com, codec@ietf.org, rfc-editor@rfc-editor.org Subject: [codec] [Editorial Errata Reported] RFC6716 (4829) X-BeenThere: codec@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Codec WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Oct 2016 01:25:28 -0000 The following errata report has been submitted for RFC6716, "Definition of the Opus Audio Codec". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=6716&eid=4829 -------------------------------------- Type: Editorial Reported by: flacs <0f1ac5@gmail.com> Section: GLOBAL Original Text ------------- Coeffieients Corrected Text -------------- Coefficients Notes ----- Just a small typo in the Table of Contents. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC6716 (draft-ietf-codec-opus-16) -------------------------------------- Title : Definition of the Opus Audio Codec Publication Date : September 2012 Author(s) : JM. Valin, K. Vos, T. Terriberry Category : PROPOSED STANDARD Source : Internet Wideband Audio Codec RAI Area : Real-time Applications and Infrastructure Stream : IETF Verifying Party : IESG From nobody Fri Oct 21 00:51:50 2016 Return-Path: X-Original-To: codec@ietf.org Delivered-To: codec@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B8D012946B; Fri, 21 Oct 2016 00:51:46 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.35.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147703630617.23721.2842157119517513885.idtracker@ietfa.amsl.com> Date: Fri, 21 Oct 2016 00:51:46 -0700 Archived-At: Cc: codec@ietf.org Subject: [codec] I-D Action: draft-ietf-codec-opus-update-04.txt X-BeenThere: codec@ietf.org X-Mailman-Version: 2.1.17 List-Id: Codec WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Oct 2016 07:51:46 -0000 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-04.txt Pages : 10 Date : 2016-10-21 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-04 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-codec-opus-update-04 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/ From nobody Mon Oct 24 14:01:08 2016 Return-Path: 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 7585F129861 for ; Mon, 24 Oct 2016 14:01:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=jmvalin-ca.20150623.gappssmtp.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 euhgEPu-MhMK for ; Mon, 24 Oct 2016 14:01:04 -0700 (PDT) Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC3B312945D for ; Mon, 24 Oct 2016 14:01:04 -0700 (PDT) Received: by mail-qt0-x22f.google.com with SMTP id s49so133893889qta.0 for ; Mon, 24 Oct 2016 14:01:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jmvalin-ca.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=29jmPQd3DGAIjQkM+8EiGokF6B4bDvI7DKVVE9eJwnk=; b=osyyA1CxnCNsNMr7keU68GdtDJg7sg7I6yl5wFr6wb6wjbJVajT2fCZxALDD3VFIvX kBkW5+WuXiHkUYeUtE/pmPe0wPsbtZ7pFduOrjORnqlBstn1aY+UX16eL56tgK3JsvCC t6SPrDXO0HTdbVsb1zbmYDEnTf98gitVZpCh7wGpBsZdYfQCcspJoRKT3GmOgWKrriHI Fu/saH0qrg5xdsmlBVGNW03GpniTMMcHFNsCFuYzvsje8uaU68BXEMeesotz0AedsvEV XZS5M37xLMGHpfDvV30ZJ/c1fh/Wuwxon/WnqqWwD89McfoG7tRU3T3tha8PjZT4kuAf PKyw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=29jmPQd3DGAIjQkM+8EiGokF6B4bDvI7DKVVE9eJwnk=; b=G8cv6hTQ2PBLYgzNK3LKt5Tzqq+nqjSyO6XvgkfMnvNZQ7nVJQJ+bPcnvoooEjtTlO 8c3D8atlRkrLCUOdFtBjztzFqzKN7wDWmOZSGdtx4DTQ5coLOqinCT6CTqSAUiEYw6Uq E7/t8rAjH8XjDqeG0oo2n7fdDbuH7plQg74NaymIcssS437DBBEXTThOhQYJrXGKC5W8 1143oLWQqdUD73Ravrai5HHSWJPT0LN9407u4829c9EB5aUr2I2VOz9JYUSIePsClRXd I9/8StXV7cvcVdzZMOjD7ANkzk3Kw9ZJ1wcQ0jGyRBTOgXqwESVxM09oEPhH1aNCmPU9 iRVA== X-Gm-Message-State: ABUngvcKmRy/2cKpaq6GXZwLxRIATIRqUJqRAKLNWawCCLiCdRy3uAFe6WnWQAo3jyYang== X-Received: by 10.237.47.194 with SMTP id m60mr16743453qtd.55.1477342863477; Mon, 24 Oct 2016 14:01:03 -0700 (PDT) Received: from panoramix.jmvalin.ca ([24.225.136.155]) by smtp.gmail.com with ESMTPSA id p28sm10698331qtb.2.2016.10.24.14.01.02 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 24 Oct 2016 14:01:02 -0700 (PDT) To: codec@ietf.org References: <147703630617.23721.2842157119517513885.idtracker@ietfa.amsl.com> From: Jean-Marc Valin Message-ID: <8703999f-618c-1d4a-6bcc-83f668c1ed75@jmvalin.ca> Date: Mon, 24 Oct 2016 17:01:01 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <147703630617.23721.2842157119517513885.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [codec] I-D Action: draft-ietf-codec-opus-update-04.txt X-BeenThere: codec@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Codec WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2016 21:01:06 -0000 Hi, The only change in this new version is the addition of a cap on the band energy. While it's technically not required to properly decode any of the test vectors, it avoids causing the decoder to output NaNs on extreme (invalid) bit-streams. I'm not aware of any other issues in the spec that needs fixing at this point. Cheers, Jean-Marc On 21/10/16 03:51 AM, internet-drafts@ietf.org wrote: > > 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-04.txt > Pages : 10 > Date : 2016-10-21 > > 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-04 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-codec-opus-update-04 > > > 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 > From nobody Mon Oct 24 14:28:26 2016 Return-Path: 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 4D83B129A00 for ; Mon, 24 Oct 2016 14:28:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=jmvalin-ca.20150623.gappssmtp.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 z842f6hN1-b8 for ; Mon, 24 Oct 2016 14:28:22 -0700 (PDT) Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D40601299FE for ; Mon, 24 Oct 2016 14:28:21 -0700 (PDT) Received: by mail-qt0-x22d.google.com with SMTP id g49so4232927qtc.6 for ; Mon, 24 Oct 2016 14:28:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jmvalin-ca.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=SyyE/Ox839ZOZvoRg+A2lnf0p2Baf6rJLu9gXo6qQ7I=; b=akikQjLyGaGgOgtO9nFxoDWyux9N88LTpH44BPRHb8zYVAi7jxqLvA3WYqp8KaT+H3 4W1TlFq0Em8VhKHRAApWP3bpLaF2ceJeM2oD/IN33S6egM1co7hp/GE/544ojmmGEL9g +iFC67+kEkkAUXSlIMzIs+oKo0JTWEipIgFNBgXZ+GvgwaBYAjqPiVMDZ3iWK7qbrKxL r2IwNlbi9LjyY5fHzF4M6YrpeLi1hXIV0kqI2dCfC9brw6qscrFp2HlrwAy9SVJPde3A CGSFUZKss8AzMvuqzRaZ/i1aeICpY9LfhvnHRNxdkSDkCZD2yZq/viP/OwT7yxRDcydy wmyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=SyyE/Ox839ZOZvoRg+A2lnf0p2Baf6rJLu9gXo6qQ7I=; b=BgNoBip4QYG6tLyvKO8BA3e9Dp0TIQEXdoOLVsFepMwCMlAtrIVuLfIOk5PYCpsjT2 SOcNhT5h7zgsqdqtoyinzow1xPrS2U/5wxYu4WE9yTJJMngUubqgTVVrajLYJEhQhbLf EOUozPdH6EY+PZkbSoigSY4/TmIZU6GEQAwfSg0/+BUOKajjsYpX/XjPlkcZOknEn1aJ noivDBn5ZU20EWO1KUsJx2y/51ciO82dyrbvlnq7qIUNxzJAJieAOj8/MxABeWxTIBcb XH/PSt2OeAuG76n6CVHeusyXI01lubBwMQxPFGORdlD6PIMj5t2x3HzhRpJ3MOOL96T6 jVwA== X-Gm-Message-State: ABUngve+SHonOivE5PcwPn2nm2Z6CApAbDbYOY8MHi2b5bB6QuWhsNcsKIZBhzH/i1t4yA== X-Received: by 10.200.36.202 with SMTP id t10mr16852094qtt.85.1477344500741; Mon, 24 Oct 2016 14:28:20 -0700 (PDT) Received: from panoramix.jmvalin.ca ([24.225.136.155]) by smtp.gmail.com with ESMTPSA id p22sm9389640qka.43.2016.10.24.14.28.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 24 Oct 2016 14:28:19 -0700 (PDT) To: "Mo Zanaty (mzanaty)" , "codec@ietf.org" References: <147275540488.32075.5908406792224056353.idtracker@ietfa.amsl.com> From: Jean-Marc Valin Message-ID: <3a2b1129-8b3f-c9d9-0b19-4b17301b651b@jmvalin.ca> Date: Mon, 24 Oct 2016 17:28:19 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2016 21:28:24 -0000 Hi Mo, On 14/10/16 04:39 PM, Mo Zanaty (mzanaty) wrote: > 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. Well, I think at this point the opus-codec.org encoder is significantly better than the one in RFC6716. It seems weird to say "using the RFC 6716 encoder is NOT RECOMMENDED" without having the IETF itself distribute a better implementation. Cheers, Jean-Marc > Mo (as individual contributor) > > -----Original Message----- > From: codec on behalf of Jean-Marc Valin > > Date: Thursday, September 1, 2016 at 4:13 PM > To: "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 > From nobody Tue Oct 25 16:26:30 2016 Return-Path: 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 0041212944C for ; Tue, 25 Oct 2016 16:26:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.331 X-Spam-Level: X-Spam-Status: No, score=-2.331 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.431] autolearn=ham autolearn_force=no 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 o0KvPt9tEV-g for ; Tue, 25 Oct 2016 16:26:10 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38C6412956F for ; Tue, 25 Oct 2016 16:26:10 -0700 (PDT) Received: from [10.10.1.4] ([162.216.46.158]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u9PNQ3Sg039754 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 25 Oct 2016 18:26:04 -0500 (CDT) (envelope-from ben@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host [162.216.46.158] claimed to be [10.10.1.4] From: "Ben Campbell" To: "Jean-Marc Valin" Date: Tue, 25 Oct 2016 16:26:02 -0700 Message-ID: In-Reply-To: <3a2b1129-8b3f-c9d9-0b19-4b17301b651b@jmvalin.ca> References: <147275540488.32075.5908406792224056353.idtracker@ietfa.amsl.com> <3a2b1129-8b3f-c9d9-0b19-4b17301b651b@jmvalin.ca> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Mailer: MailMate (1.9.5r5263) Archived-At: Cc: "codec@ietf.org" Subject: Re: [codec] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2016 23:26:16 -0000 (as individual) On 24 Oct 2016, at 14:28, Jean-Marc Valin wrote: > Hi Mo, > > On 14/10/16 04:39 PM, Mo Zanaty (mzanaty) wrote: >> 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. > > Well, I think at this point the opus-codec.org encoder is > significantly > better than the one in RFC6716. It seems weird to say "using the RFC > 6716 encoder is NOT RECOMMENDED" without having the IETF itself > distribute a better implementation. The issue is, the IETF is not normally in the business of specifying implementations. RFC6716 is a bit weird, because the code specifies the bitstream. But IMO, the code is only normative in that sense; that is, there is no normative requirement to use that code as long as you generate the same bitstream. Ben. > > Cheers, > > Jean-Marc > >> Mo (as individual contributor) >> >> -----Original Message----- >> From: codec on behalf of Jean-Marc Valin >> >> Date: Thursday, September 1, 2016 at 4:13 PM >> To: "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 >> > > _______________________________________________ > codec mailing list > codec@ietf.org > https://www.ietf.org/mailman/listinfo/codec