[Wish] Magnus Westerlund's No Objection on charter-ietf-wish-00-01: (with COMMENT)

Magnus Westerlund via Datatracker <noreply@ietf.org> Thu, 21 January 2021 13:43 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: wish@ietf.org
Delivered-To: wish@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5820B3A0BC5; Thu, 21 Jan 2021 05:43:35 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Magnus Westerlund via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: wish-chairs@ietf.org, wish@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <161123661527.29515.3808895890497585933@ietfa.amsl.com>
Date: Thu, 21 Jan 2021 05:43:35 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/wish/ppEKMvoSX0sAFuYpajIf-iDDEio>
Subject: [Wish] Magnus Westerlund's No Objection on charter-ietf-wish-00-01: (with COMMENT)
X-BeenThere: wish@ietf.org
X-Mailman-Version: 2.1.29
List-Id: WebRTC Ingest Signaling over HTTPS <wish.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wish>, <mailto:wish-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wish/>
List-Post: <mailto:wish@ietf.org>
List-Help: <mailto:wish-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wish>, <mailto:wish-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2021 13:43:35 -0000

Magnus Westerlund has entered the following ballot position for
charter-ietf-wish-00-01: 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.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-wish/



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

I am on the verge of a block here.

So the goal is to establish a one-way media over an WebRTC peer connection
between a media producer and a consumer. What isn't clear in this work is who
is the intended initiator to this communication. After having looked in
draft-imurillo-whip it appears the intention is for the media producer (or its
controller) to initiate the HTTP connection to a consumer (or its controller).
Where the necessary configuration is established.

I assume based on signalling the media flow could be reversed so the consumer
initates the media establishment, but that is also not clear. Clarifying the
high level functionality here in the charter might avoid the need for
specifically commenting on screens. Because that would basically work if the
consumer can be the initiator and request media to it.

The other aspect that I realize is missing is the scope of capability
negotiation here and preference indication. Defining this from a WebRTC API
perspective might be possible but is not clear. What is needed here? What is
assumed about third parties creating media profiles for this type of devices?