Re: [Wish] draft charter

Adam Roach <adam@nostrum.com> Fri, 18 December 2020 21:22 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: wish@ietfa.amsl.com
Delivered-To: wish@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51DCB3A0475; Fri, 18 Dec 2020 13:22:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.281
X-Spam-Level:
X-Spam-Status: No, score=-1.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.399, NICE_REPLY_A=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 YXqRIs2nfYcD; Fri, 18 Dec 2020 13:22:08 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 AE8413A0489; Fri, 18 Dec 2020 13:22:08 -0800 (PST)
Received: from Zephyrus.local (76-218-40-253.lightspeed.dllstx.sbcglobal.net [76.218.40.253]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 0BILM3th061577 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 18 Dec 2020 15:22:04 -0600 (CST) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1608326525; bh=1dEux5W4QaLM7wWkzXuHjBa0VMtZYLkSVhPRvN6aqbE=; h=Subject:To:References:From:Date:In-Reply-To; b=ON1U4ADDFmdIZ7YIUg/Inrxsmo6xxy+LsCIBkgmqR+awz21VC41F9qBqP2kj4p5CK hNT9Yp9THB8mCHEp2wmE2FijMzuYheqoECwzfcOmXqL9+7oBhAFiy2/cdD/USrqyoG nSueFze6CXVIn2ygivX+QXNDheWjORtr2B56fTnM=
X-Authentication-Warning: raven.nostrum.com: Host 76-218-40-253.lightspeed.dllstx.sbcglobal.net [76.218.40.253] claimed to be Zephyrus.local
To: "Charles Eckel (eckelcu)" <eckelcu=40cisco.com@dmarc.ietf.org>, "wish@ietf.org" <wish@ietf.org>
References: <2BA16BAF-CC1D-41B1-887C-99AF82372B94@cisco.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <6da57174-d574-4b1a-5185-f1e4c1306a7d@nostrum.com>
Date: Fri, 18 Dec 2020 15:21:58 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.11.0
MIME-Version: 1.0
In-Reply-To: <2BA16BAF-CC1D-41B1-887C-99AF82372B94@cisco.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/wish/fAoeq1UapJ6k3-lKbQ0NcLfh2cs>
Subject: Re: [Wish] draft charter
X-BeenThere: wish@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Fri, 18 Dec 2020 21:22:11 -0000

On 12/11/20 13:24, Charles Eckel (eckelcu) wrote:
> I had a look at the draft charter at https://datatracker.ietf.org/doc/charter-ietf-wish/.
> Overall, it looks pretty good to me, but I do have a couple questions.
>
> 1) Is the intent that any WebRTC server, and any WebRTC client, be able to use this protocol to establish a one way media session to forward its own view of the WebRTC media streams, with or without any alteration, to a broadcast network?


Server-to-server isn't really in scope, although a server taking media 
that it is receiving and setting up a rebroadcast for it using WISH is 
certainly possible.


> 2) I understood from the dispatch session, the time frame for this work to complete is expected to be relatively short. It would be helpful to see milestones with anticipated dates for completion.


Definitely a good point! Notionally, this is your typical "as long as it 
takes but not any longer" desideratum, but we should have goals. I'd 
love to see a single milestone that is "submit WISH document to IESG for 
publication" with a date sometime in 2021. I know this is aggressive, 
but I'm using MARTINI as my idealized model, and we managed to go from 
first draft to publication requested in 13 months.

/a