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

Jean-Marc Valin <jmvalin@jmvalin.ca> Mon, 24 October 2016 21:28 UTC

Return-Path: <jmvalin@jmvalin.ca>
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 <codec@ietfa.amsl.com>; 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 <codec@ietfa.amsl.com>; 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 <codec@ietf.org>; Mon, 24 Oct 2016 14:28:21 -0700 (PDT)
Received: by mail-qt0-x22d.google.com with SMTP id g49so4232927qtc.6 for <codec@ietf.org>; 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)" <mzanaty@cisco.com>, "codec@ietf.org" <codec@ietf.org>
References: <147275540488.32075.5908406792224056353.idtracker@ietfa.amsl.com> <fe060bab-0e31-ccfb-ce7e-a683beb6d445@jmvalin.ca> <D426B856.6580D%mzanaty@cisco.com>
From: Jean-Marc Valin <jmvalin@jmvalin.ca>
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: <D426B856.6580D%mzanaty@cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/codec/ZqWVU3KYNEC0kQNWyN03LBUmFss>
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: 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 <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
>