[AVTCORE] Robert Wilton's No Objection on draft-ietf-avtcore-multi-party-rtt-mix-18: (with COMMENT)

Robert Wilton via Datatracker <noreply@ietf.org> Thu, 20 May 2021 08:50 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: avt@ietf.org
Delivered-To: avt@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AE8EA3A1390; Thu, 20 May 2021 01:50:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Wilton via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-avtcore-multi-party-rtt-mix@ietf.org, avtcore-chairs@ietf.org, avt@ietf.org, bernard.aboba@gmail.com, bernard.aboba@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Robert Wilton <rwilton@cisco.com>
Message-ID: <162150064568.17183.13006538345122561644@ietfa.amsl.com>
Date: Thu, 20 May 2021 01:50:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/nkO49WxM8o5onon9seIsHjd_cIQ>
Subject: [AVTCORE] Robert Wilton's No Objection on draft-ietf-avtcore-multi-party-rtt-mix-18: (with COMMENT)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2021 08:50:46 -0000

Robert Wilton has entered the following ballot position for
draft-ietf-avtcore-multi-party-rtt-mix-18: 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 DISCUSS and COMMENT positions.

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



Thanks for this document.  This document is quite a long way from my core
knowledge base, so I'm not sure whether there is much that I can really add. 
It doesn't seem to have any obvious manageability concerns.

I was initially surprised by the capability exchange mechanism
(offer/exchange), in that if both offeror and receiver could support multiple
options then it is always the the receiver that decides which to use (by only
selecting one).  I think that this is probably fine.  I don't know which
parties generally initiate these exchanges, and whether there is ever a case
where both offeror and receiver support multiple options where it would be
beneficial for the offeror to make the final decision as to which should be
used (e.g., when coordinating between more than two devices).

As one minor nit, I would have preferred to see section 1.2, "Selected solution
and considered alternatives" as an appendix.  I wasn't convinced that it is
core to understanding this document, but I'm happy to leave it to the authors
discretion as to whether they should move it, or leave it where it is.