[codec] Joel Jaeggli's No Objection on draft-ietf-codec-oggopus-13: (with COMMENT)

"Joel Jaeggli" <joelja@bogus.com> Tue, 16 February 2016 17:00 UTC

Return-Path: <joelja@bogus.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 D65491B2FBE; Tue, 16 Feb 2016 09:00:16 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Jaeggli <joelja@bogus.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.14.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160216170016.13734.77381.idtracker@ietfa.amsl.com>
Date: Tue, 16 Feb 2016 09:00:16 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/codec/4JwjK1napNGAR6SM9hjKjsdcidg>
Cc: codec-chairs@ietf.org, codec@ietf.org, draft-ietf-codec-oggopus@ietf.org
Subject: [codec] Joel Jaeggli's No Objection on draft-ietf-codec-oggopus-13: (with COMMENT)
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.15
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, 16 Feb 2016 17:00:17 -0000

Joel Jaeggli has entered the following ballot position for
draft-ietf-codec-oggopus-13: 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:
https://datatracker.ietf.org/doc/draft-ietf-codec-oggopus/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Scott Bradner performed the OPSdir review.

There was an ask for a paragraph covering the following

That said, I wonder if it would be possible to as a OAM-like ability to
support "in-band" condition information - for example by adding an OAM
channel to the channel mapping function (i.e. the "Opus Channel Mapping
Families" registry) where the definition would be that the channel is for
the use of OAM services and is otherwise passed unmodified.  Having the
ability to have real time "what the customer is seeing" RTCP like, but
with more expansion abilities, feedback could be quite helpful
operations-wise

which has not yet come to conclusion.