IETF Logo Mail Archive

Re: [Wish] WG recharter

Sean DuBois <sean@siobud.com> Mon, 17 April 2023 18:40 UTC

Return-Path: <sean@siobud.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 D9F48C151B35 for <wish@ietfa.amsl.com>; Mon, 17 Apr 2023 11:40:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=siobud.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PQo6oIIKwJdq for <wish@ietfa.amsl.com>; Mon, 17 Apr 2023 11:40:11 -0700 (PDT)
Received: from mail.siobud.com (mail.siobud.com [165.227.221.230]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F0F5C14CE5D for <wish@ietf.org>; Mon, 17 Apr 2023 11:40:11 -0700 (PDT)
Date: Mon, 17 Apr 2023 14:40:05 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=siobud.com; s=mail; t=1681756806; bh=7BEX1OkAcmtcacvYHErVPhwzwuz/PbgxTvCSg8XFHjk=; h=From:To:Cc:Subject:References:In-Reply-To; b=ETtSt5gYrAxKboXrsHFNtDjYxJvL1Cc5YZ55hx6yWjAEBZX7oFDc5LtFzvg+NzaP7 RYz1a2Oa1ESzHAYgJ1gN7asSrMPwbSsQAtfrYrZRidTz0GDWY3v58e2DOMSPrvEHnv DR50IB0kiDhZ/fTxYobYCljPJmmKevnzXzirlKxw=
From: Sean DuBois <sean@siobud.com>
To: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Cc: Bernard Aboba <bernard.aboba@gmail.com>, Juliusz Chroboczek <jch@irif.fr>, Sean Turner <sean@sn3rd.com>, WISH List <wish@ietf.org>
Message-ID: <ZD2ShULL37EVl8Th@SeanLaptop>
References: <CA+ag07YGJJ3OGbVWvTyx8azE8rPZxUTx+e1t-8QwDFc46+0jOg@mail.gmail.com> <F830F2A1-940D-40B2-9B37-BA8458E23430@pi.pe> <194B3D5F-D61E-496B-8B6A-74D5BAB78314@sn3rd.com> <CA+ag07aq6XHhGyCLwDFxXeb9vVMdXE5jE=NsvUJNhgr96Gxwpw@mail.gmail.com> <CA+ag07Y424OPOHvW8sGie4VwJfC1JKhE=bC-vsCFWnqc_pmU+Q@mail.gmail.com> <CAOW+2dsPfoNPCO-S8THzMPkT8_pPCyiprB598Od4YjH9nNyiKQ@mail.gmail.com> <CA+ag07Z7+dRqCEqye_rEwSZx4AkKUdeRbONbfDY2ZDQDAd5=kg@mail.gmail.com> <874jpejtvv.wl-jch@irif.fr> <CAOW+2duw_8U7+2K5Yesxcm1bRuCf4EGwp+8P+Y6f0tQfc1mobA@mail.gmail.com> <CA+ag07bms3AXfP7-D0M6dBJKQyNHfc8OAFGNUKO9vSfVqTitEw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CA+ag07bms3AXfP7-D0M6dBJKQyNHfc8OAFGNUKO9vSfVqTitEw@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wish/zswkvd8JHsNAQlkP5-O8MtOKJq0>
Subject: Re: [Wish] WG recharter
X-BeenThere: wish@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 17 Apr 2023 18:40:14 -0000

WebTransport is a Javascript/Browser technology, while WHIP/WHEP isn't.
So things like MSE don't apply right? MSE doesn't exist for my WHIP/WHEP clients.
I am doing everything in Native/Server.

We have the flexibility to define/propose extensions in the future. I
would rather discuss rewind in depth in the future. WHIP+WHEP has
everything I need today to start building things.

On Mon, Apr 17, 2023 at 08:14:07PM +0200, Sergio Garcia Murillo wrote:
> So you are proposing sending CMAF over datachannels for WHEP? Appart of
> being a terrible idea from my point of view (use MoQ intead), there is no
> standard "CMAF over datachannels" media protocol we can reference.
>
> El lun, 17 abr 2023 20:07, Bernard Aboba <bernard.aboba@gmail.com> escribió:
>
> > Juliusz said:
> >
> > "I think that's an important point.  In WHIP, Sergio has been careful to
> > stick to signalling, and defer all other protocol features to existing
> > standards.  That's what makes WHIP so eminently implementable."
> >
> > [BA]  Except that there *are* "eminently implementable" standards, such as
> > CMAF for containerization and MSE API (for rendering).  To prove the point,
> > CMAF is supported in early MoQ drafts and browser clients demos supporting
> > MSE have implemented "rewind".  If WebTransport were swapped out for
> > RTCDataChannel, those same demos would run in Chromium.
> >
> > So the protocols have already been defined and implemented, and running
> > code already exists.  In that sense, the remaining functionality is largely
> > in the realm of "signaling" (e.g. how to request CMAF over RTCDataChannel,
> > or how to request "rewind").
> >
> >
> >
> > On Mon, Apr 17, 2023 at 10:33 AM Juliusz Chroboczek <jch@irif.fr> wrote:
> >
> >> > Regarding the specific DRM and rewind functionalities, there is not a
> >> standard
> >> > way of implementing them that we can reuse here.
> >>
> >> I think that's an important point.  In WHIP, Sergio has been careful to
> >> stick to signalling, and defer all other protocol features to existing
> >> standards.  That's what makes WHIP so eminently implementable.
> >>
> >> -- Juliusz
> >>
> >

> --
> Wish mailing list
> Wish@ietf.org
> https://www.ietf.org/mailman/listinfo/wish

v2.46.0 | Report a Bug | By Email | System Status