Re: [dispatch] WHIP - WebRTC HTTP ingestion protocol

Alexandre GOUAILLARD <agouaillard@gmail.com> Tue, 01 December 2020 22:36 UTC

Return-Path: <agouaillard@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A47DE3A08FA for <dispatch@ietfa.amsl.com>; Tue, 1 Dec 2020 14:36:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 hggiKFB5W8p4 for <dispatch@ietfa.amsl.com>; Tue, 1 Dec 2020 14:36:34 -0800 (PST)
Received: from mail-pl1-x636.google.com (mail-pl1-x636.google.com [IPv6:2607:f8b0:4864:20::636]) (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 54F763A0913 for <dispatch@ietf.org>; Tue, 1 Dec 2020 14:36:34 -0800 (PST)
Received: by mail-pl1-x636.google.com with SMTP id p6so2036361plr.7 for <dispatch@ietf.org>; Tue, 01 Dec 2020 14:36:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=V8rTmSCEg22tPt2J7YlzlfVBvxuD76Rs0bt4q5S/lA4=; b=YmCr6HVRsKd9+yKgczEBQNCPWbEaXey7UW6JTWJqQdtqpEisOdxoThKOMPvkdxsSk8 i7m7ecVS4onivn32cDXH3GcOjNd6HVmZNNekaw4NWPTEGvMIrsWs82d0J06mCfJp4DfB tChRDdGbzCuRfgg0xWp1imWYIp9TeTd7CkOX4iu3gWfY8hpOSnAAiAtP8nDk5m4Lcf7i nn2fGz9XQtkZURC5FMv20dMz/1y+nCbJ3hmqFbp4tFyQCfzrJBuHMrmqz30d/BwQHHwe hrFkzeHKCmL7C9rAxdiI58c86YucmFAOo+5Er8FMj+3U7jEbv4UAH/EiQpjNWYl4Dtfv KuxA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=V8rTmSCEg22tPt2J7YlzlfVBvxuD76Rs0bt4q5S/lA4=; b=WAzqpBELz0tAnb1VZhMX1CXXuz2q42LQIkUd/0TYMosZt07Ft3wOPRFMAuWvkwdZnb ZYDZq537SZkc8jeNL6ARolGjDpEaobOkya3A8jTJPnoxoHmCpT80BAbO4HBpClqI+MgJ u8BhJghimwQiD3n2t+Y7AkDJ+/jht6Md4vEZnwgxlA08BS+BRF1y8YC7BrxbVRRqCV5V tKgM5lvPAHLovFSwWVJ+ETKVxVBKfw7zm1TpDK9kIAT3ZiSHNhXjC1akYum7dgY335Fq mRjbteKre/ngsRKzzKi7dB4Klt2luemhSO8R6sC+s4fKC4Zw6qaXxtXUm14rUUbmqvZa 1CSg==
X-Gm-Message-State: AOAM533xRlBMZV3JdjVrahxNDYI5biiQxtbgKrOOzTHTVLqXanxDLXLD f0s1jOHwLVizHUwKOvT1750=
X-Google-Smtp-Source: ABdhPJyIvm5BIpqMsDMA8NR6iJSLaruxrlSxmbpr0qPa4P+BsYx7Xs+NmQGBUUySIQHYrrvxEka5EQ==
X-Received: by 2002:a17:90a:2e8c:: with SMTP id r12mr4968879pjd.101.1606862193836; Tue, 01 Dec 2020 14:36:33 -0800 (PST)
Received: from [192.168.86.61] ([103.6.150.161]) by smtp.gmail.com with ESMTPSA id b17sm746978pfi.61.2020.12.01.14.36.30 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 01 Dec 2020 14:36:30 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Alexandre GOUAILLARD <agouaillard@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Wed, 02 Dec 2020 06:36:28 +0800
Message-Id: <9D4628CB-20A0-4B50-92FE-1F6DD6E39C65@gmail.com>
References: <f9833842-b567-f159-cf10-378e485a5cc8@gmail.com>
Cc: Adam Roach <adam@nostrum.com>, Ben Campbell <ben@nostrum.com>, dispatch@ietf.org, Alex Gouaillard <dralex@millicast.com>
In-Reply-To: <f9833842-b567-f159-cf10-378e485a5cc8@gmail.com>
To: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
X-Mailer: iPhone Mail (18B92)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/kFC_G_RAWxA58fx2PyAl6tkYNDM>
Subject: Re: [dispatch] WHIP - WebRTC HTTP ingestion protocol
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Dec 2020 22:36:36 -0000

+1 with Sergio

Sent from my iPhone

> On 2 Dec 2020, at 05:40, Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> wrote:
> 
> On 30/11/2020 18:56, Adam Roach wrote:
>> 
>> Having read through the proposal and watched the corresponding segment of the DISPATCH meeting from two weeks ago, I think that having something like this standardized would be very useful, both for the handful of broadcasting tools that exist as well as for the various WebRTC broadcast networks that are being deployed.
>> 
>> So I definitely think we should pursue this work in the IETF.
>> 
>> It's a little less clear to me whether we want to slot this into something like MMUSIC or to create a short-lived working group. I'm leaning towards the second, for a couple of reasons. First, I found Ted's comments at the DISPATCH meeting to be kind of illuminating as far as the kinds of additional work that might be necessary (and I have my own list of things that might need some refinement, like negotiation of authentication mechanisms); and that nudges the effort into a "maybe a little larger than just one work item in a long-standing working group." More importantly, this work straddles the real-time media and web disciplines, and I'd like to make sure we have people from the latter group putting eyes on it. I seriously doubt we can get HTTP experts showing up at MMUSIC, but there's at least a fair chance that we might get them interested in a lower-volume mailing list such as a dedicated WHIP WG.
>> 
>> I think this mirrors, for the most part, the tentative conclusion that came out of the DISPATCH discussion earlier this month. If we decide to take this path of creating a short-lived WG, I'm happy to help craft a charter and plan to be actively involved in the technical work.
>> 
> I agree with you, a dedicated small/short lived WG would be the best way to have right people involved and focused. Also, your collaboration is really appreciated, looking forward to start working on it.
> 
> Best regards
> 
> Sergio
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch