IETF Logo Mail Archive

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

Ross Finlayson <finlayson@live555.com> Sat, 13 March 2021 03:58 UTC

Return-Path: <finlayson@live555.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 2DB953A1485 for <wish@ietfa.amsl.com>; Fri, 12 Mar 2021 19:58:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 KX74w6yAkxqs for <wish@ietfa.amsl.com>; Fri, 12 Mar 2021 19:58:52 -0800 (PST)
Received: from us.live555.com (us.live555.com [52.8.240.222]) (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 1B6FF3A1484 for <wish@ietf.org>; Fri, 12 Mar 2021 19:58:52 -0800 (PST)
Received: from [127.0.0.1] (localhost.live555.com [IPv6:0:0:0:0:0:0:0:1]) by us.live555.com (8.15.2/8.15.2) with ESMTP id 12D3wGUh073892 for <wish@ietf.org>; Fri, 12 Mar 2021 19:58:51 -0800 (PST) (envelope-from finlayson@live555.com)
From: Ross Finlayson <finlayson@live555.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Fri, 12 Mar 2021 19:58:50 -0800
References: <EA0DDB88-D685-4646-8BC8-D694EA2274D7@live555.com> <CAHgZEq7KOpZhOEXbNr5D3AFN1HktUKky_pw3d7UV9GW4iGxHRw@mail.gmail.com>
To: wish@ietf.org
In-Reply-To: <CAHgZEq7KOpZhOEXbNr5D3AFN1HktUKky_pw3d7UV9GW4iGxHRw@mail.gmail.com>
Message-Id: <2EB890DF-0BA1-442D-9E6E-0F58CA4CB5DF@live555.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wish/I88-11F3LyX-Dii_9TO-3JBQn0o>
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: Sat, 13 Mar 2021 03:58:53 -0000


> On Mar 12, 2021, at 7:41 PM, Alexandre GOUAILLARD <agouaillard@gmail.com> wrote:
> 
> Media management is entirely delegated to the RTCWEB specifications. In particular, the use of ICE, and the use of DTLS-SRTP are mandatory. For clarification, the use of JSEP, SDP, SDP O/A are also all mandatory.

Alex,

I think you may be missing my point.  A WebRTC stream that happens to negotiate COMEDIA transport (with RFC 4571 framing of RTP/RTCP) is still, in my mind, a WebRTC stream.  It would be negotiated the same way as any other WebRTC stream (using JSEP, SDP, O/A).  But the stream itself wouldn’t use datagrams, and thus wouldn’t use ICE (because it wouldn’t need it).  That’s why I described this as being ‘WHIP-light’ - a subset of the WHIP protocol just for this simple class of streams.

Perhaps I have a more expansive view of WebRTC than everyone else, but I consider what I’m describing as being a WebRTC stream; albeit a special case.

	Ross.

v2.23.0 | Report a Bug | By Email