Re: [V3] Thoughts on scope for ript
Justin Uberti <juberti@google.com> Wed, 25 March 2020 19:31 UTC
Return-Path: <juberti@google.com>
X-Original-To: v3@ietfa.amsl.com
Delivered-To: v3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95DF63A0B9B for <v3@ietfa.amsl.com>; Wed, 25 Mar 2020 12:31:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level:
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 UaMdIErf-U0Y for <v3@ietfa.amsl.com>; Wed, 25 Mar 2020 12:31:52 -0700 (PDT)
Received: from mail-vs1-xe2b.google.com (mail-vs1-xe2b.google.com [IPv6:2607:f8b0:4864:20::e2b]) (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 C83073A0BE1 for <v3@ietf.org>; Wed, 25 Mar 2020 12:31:50 -0700 (PDT)
Received: by mail-vs1-xe2b.google.com with SMTP id x82so2282031vsc.12 for <v3@ietf.org>; Wed, 25 Mar 2020 12:31:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3jAXsE4yaYOjzH1nl6Kua0rZMPSbLcVOmRjHKNXddYk=; b=QY5V3a2sZSUOV3keBlLQaHmHhG/C2yEgSIHkmqOXZLzOaCIKYGSc+dkYb7wainZNNM hwvuY+HTC7Me6UNY7lrxn9p+DTF5LzglIjpjUUJt92liSW5FXaqhx5wzCMKHAHKqrSvG D7HQllaGcPkBX+dfT0iqcG8HDK8z5UezlOMhYU5nEEMJ+YGm9LZUg8dI+KQ4PkUGIn+1 Ph+u8xKqXmVsu46lK+uWtH5A6ok1iR+rkqXj02esbP0Ne1y2PI0pH/Fe5KKQa22Pi2oz Tbb94y6Vz+8OOZAQqdug5tofnnaSbAJWXMOwWPVgA6PrHeUg+VTGEOVo4X7SBXmYaAnH F6zg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3jAXsE4yaYOjzH1nl6Kua0rZMPSbLcVOmRjHKNXddYk=; b=mfdqmyrnt2phPg9iMSlMMw2R3Tywl7ftP6I37hKrKm80SKdWpeJ3IIJeKFN7TyZGRB QDXcYs4Wqqxt+aeYiTlLsAZw+c5sN3/gtb6opFojkmhDwewr9r+czT1FudM+B6aBIvUS qL2h6TWPFa1B4rcldSLYCOq0aLJpJl/fKtKezEWqtVbTr2o66sa/86NcfujGu8v97rXV 3vMvShDmgpw9FEN8MLDGWAY1PiGdCk55kAAEvyxkESYIz99XWNGxxO2l7DaE3xmOqQdZ aFsVtx2Yr1+Pymqf8dYNtbow0DjrKfekAF47YX9Vdwmb5iqdsP7F54JfAFreLSZtsjy0 rawQ==
X-Gm-Message-State: ANhLgQ14/99XXlnGuXNnWn48qAquKHagBbdom1fZHuef94N0QxFuR1iJ XfgoUOPqvjRtclz+fnEuaJARh7zUmfa59vOpMRvQSA==
X-Google-Smtp-Source: ADFU+vsQOGgOcp+mEHnID8DJNJ/QIe67gWGPjsTIBukk1X2W7wpDV/JmN8GbqIvXLzKysyapIFlkuIw6DTS2+78eGek=
X-Received: by 2002:a67:2f83:: with SMTP id v125mr4000294vsv.100.1585164709068; Wed, 25 Mar 2020 12:31:49 -0700 (PDT)
MIME-Version: 1.0
References: <BYAPR06MB4391FBC64E195E87003061B8FBF00@BYAPR06MB4391.namprd06.prod.outlook.com> <CAOJ7v-0MP4p=tpzgNJu1Mxgt8cv4PL01PbQWhTzN6bYSQR9Yuw@mail.gmail.com> <CAAZdMadmEuZz4T6t6BP_=ZMUrducE4g-qwYHpeiB8Ho8SEKCsQ@mail.gmail.com> <CAKKJt-d-6O1_aP1_7KENQSMYyE5yLhrbSCxec1TEEDB_0ss6=Q@mail.gmail.com> <CAOJ7v-0SEtMPedQ=Jga5ErTTTeacUjCKTOZd1arzUDKDVXjyoQ@mail.gmail.com> <CAKKJt-cZ+oxysgsyoGVQyV_z3GALT9uEYcwia5qLONjw1Oc2Rg@mail.gmail.com>
In-Reply-To: <CAKKJt-cZ+oxysgsyoGVQyV_z3GALT9uEYcwia5qLONjw1Oc2Rg@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Wed, 25 Mar 2020 12:31:37 -0700
Message-ID: <CAOJ7v-230-EskWz0abxcmTEpz4jf7xuVjOeVYeuxbEA3p2pr2Q@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Victor Vasiliev <vasilvv@google.com>, Jonathan Rosenberg <jdrosen@five9.com>, "v3@ietf.org" <v3@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000658b8005a1b2eba7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v3/hgHCJlpWOMrkNrxN87993pF_4FU>
Subject: Re: [V3] Thoughts on scope for ript
X-BeenThere: v3@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <v3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v3>, <mailto:v3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v3/>
List-Post: <mailto:v3@ietf.org>
List-Help: <mailto:v3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v3>, <mailto:v3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Mar 2020 19:31:54 -0000
On Wed, Mar 25, 2020 at 12:26 PM Spencer Dawkins at IETF < spencerdawkins.ietf@gmail.com> wrote: > Replying to Justin, after reading Victor's reply - thank you both for > replying ... > > On Wed, Mar 25, 2020 at 11:55 AM Justin Uberti <juberti@google.com> wrote: > >> >> >> On Wed, Mar 25, 2020 at 9:28 AM Spencer Dawkins at IETF < >> spencerdawkins.ietf@gmail.com> wrote: >> >>> This is interesting ... >>> >>> On Wed, Mar 25, 2020 at 10:31 AM Victor Vasiliev <vasilvv= >>> 40google.com@dmarc.ietf.org> wrote: >>> >>>> I would like to second Justin's point here about the value of a >>>> client-server RTP streaming by itself (e-f, though in-band c-d are also >>>> valuable). There's a lot of value in the world where I can take an HTTP >>>> URL to some endpoint in the cloud and give it to, say, an IoT camera device >>>> to use as a realtime media sink, or pass it to an off-the-shelf streaming >>>> library to show a realtime media source on screen. >>>> >>> >>> I know most of my own concerns about RIPT media have started out with >>> "this won't be as good as RTP for media", but what I've been getting from >>> RIPT discussions is, that may not matter as much as I expected. >>> >>> For a use case like Victor's, great media quality would be great, but >>> good enough media quality may be ... good enough. >>> >>> Am I putting words in the mouths of the proponents? >>> >>> Some applications may tolerate somewhat lower quality in fallback >> scenarios, but I think we should be aiming for RTP performance with HTTP >> ease of deployment. >> > > I was actually hoping that wasn't the case, because ISTM that the question > whether RTP performance over HTTP is possible/likely is going to suck up a > LOT of the discussion time during the BOF ... > To Eric's point, "H3 is not widely deployed yet, and so we should think about how we want things to look". I think it's entirely possible to achieve RTP performance over H3, and hopefully also have a reasonable fallback when only H2 is available.
- [V3] Thoughts on scope for ript Jonathan Rosenberg
- Re: [V3] Thoughts on scope for ript Eric Rescorla
- Re: [V3] Thoughts on scope for ript Justin Uberti
- Re: [V3] Thoughts on scope for ript Anthony Minessale
- Re: [V3] Thoughts on scope for ript Justin Uberti
- Re: [V3] Thoughts on scope for ript Anthony Minessale
- Re: [V3] Thoughts on scope for ript Victor Vasiliev
- Re: [V3] Thoughts on scope for ript Spencer Dawkins at IETF
- Re: [V3] Thoughts on scope for ript Anthony Minessale
- Re: [V3] Thoughts on scope for ript Justin Uberti
- Re: [V3] Thoughts on scope for ript Spencer Dawkins at IETF
- Re: [V3] Thoughts on scope for ript Justin Uberti
- Re: [V3] Thoughts on scope for ript Stephan Wenger
- Re: [V3] Thoughts on scope for ript Justin Uberti
- Re: [V3] Thoughts on scope for ript Eric Rescorla
- Re: [V3] Thoughts on scope for ript Justin Uberti