IETF Logo Mail Archive

Re: [Wish] WHIP should also allow *media* to be sent over the HTTPS connection

Juliusz Chroboczek <jch@irif.fr> Sun, 14 March 2021 17:19 UTC

Return-Path: <jch@irif.fr>
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 AB21B3A0BC7 for <wish@ietfa.amsl.com>; Sun, 14 Mar 2021 10:19:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 pZVV32e4Zhk3 for <wish@ietfa.amsl.com>; Sun, 14 Mar 2021 10:19:54 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5202E3A0BC2 for <wish@ietf.org>; Sun, 14 Mar 2021 10:19:54 -0700 (PDT)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/82085) with ESMTP id 12EHJmJQ024852; Sun, 14 Mar 2021 18:19:48 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 64BE314454; Sun, 14 Mar 2021 18:19:48 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id vVIEUTEKhcIF; Sun, 14 Mar 2021 18:19:47 +0100 (CET)
Received: from pirx.irif.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 55FB014450; Sun, 14 Mar 2021 18:19:46 +0100 (CET)
Date: Sun, 14 Mar 2021 18:19:45 +0100
Message-ID: <87ft0xmz4e.wl-jch@irif.fr>
From: Juliusz Chroboczek <jch@irif.fr>
To: Tim Panton <tim@pi.pe>
Cc: Ross Finlayson <finlayson@live555.com>, wish@ietf.org
In-Reply-To: <35AF83F2-C219-42E7-8A53-5292B8E748B8@pi.pe>
References: <2EB890DF-0BA1-442D-9E6E-0F58CA4CB5DF@live555.com> <35AF83F2-C219-42E7-8A53-5292B8E748B8@pi.pe>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.1 Mule/6.0
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sun, 14 Mar 2021 18:19:48 +0100 (CET)
X-Miltered: at korolev with ID 604E45B4.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 604E45B4.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@irif.fr>
X-j-chkmail-Score: MSGID : 604E45B4.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/wish/GEWtrVtXq5vlyYRCFiR9IW6UAfg>
Subject: Re: [Wish] WHIP should also allow *media* to be sent over the HTTPS connection
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: Sun, 14 Mar 2021 17:19:57 -0000

> Unless I am mistaken it will take quite a lot of work to engineer this
> into the webRTC stack on a browser.

I'm confused again, sorry if I'm being dense.  If the media source is
a browser, then it presumably already implements the full WebRTC stack?
Why is a reduced complexity protocol required in that case?

v2.23.0 | Report a Bug | By Email