[codec] Spencer Dawkins' No Objection on draft-ietf-codec-opus-update-08: (with COMMENT)

Spencer Dawkins <spencerdawkins.ietf@gmail.com> Tue, 15 August 2017 16:40 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
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 378E812426E; Tue, 15 Aug 2017 09:40:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-codec-opus-update@ietf.org, Tim Terriberry <tterriberry@mozilla.com>, codec-chairs@ietf.org, tterriberry@mozilla.com, codec@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150281524621.21110.4158788012236698670.idtracker@ietfa.amsl.com>
Date: Tue, 15 Aug 2017 09:40:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/codec/OYsNRKlzabaJEtZIQ3fBDfg80q4>
Subject: [codec] Spencer Dawkins' No Objection on draft-ietf-codec-opus-update-08: (with COMMENT)
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 15 Aug 2017 16:40:46 -0000

Spencer Dawkins has entered the following ballot position for
draft-ietf-codec-opus-update-08: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)

Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:


Thanks for producing this specification. I have some questions, but nothing at
Discuss level.

I have no idea what an “extreme bitstream” is. Aren’t they all pretty much 0s
and 1s?

More seriously, it would be nice to know what about the bitstream is extreme.
Googling for ‘opus “extreme bitstream”’ turns up one hit for side effects from
a drug being tested, so that wasn’t much help.

Is there an obvious way that the decoder can know whether audio will be
downmixed outside the decoder? Section 10 thinks decoders can know that,

In the security considerations, why is it highly unlikely that the read-only
table will be placed next to sensitive data? I’m not balloting Discuss on this
because the assertion is nested in a reported vulnerability with no known
exploit, but I am curious.