Re: [V3] Thoughts on scope for ript
Justin Uberti <juberti@google.com> Wed, 25 March 2020 16:55 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 8DB1D3A09AB for <v3@ietfa.amsl.com>; Wed, 25 Mar 2020 09:55:44 -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 QTLWQgvP13Ml for <v3@ietfa.amsl.com>; Wed, 25 Mar 2020 09:55:43 -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 96A183A09A4 for <v3@ietf.org>; Wed, 25 Mar 2020 09:55:42 -0700 (PDT)
Received: by mail-vs1-xe2b.google.com with SMTP id o3so1961103vsd.4 for <v3@ietf.org>; Wed, 25 Mar 2020 09:55:42 -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=WyzqTRLggxDJDVnN2gBd/xoFffQq8EDMKy7aVL8hvdU=; b=uOGnwmboigrSxXjJO+MSMOdiONdhXcXyI0Gu0lCEwjtcoSwPXICEVUU+mGLqkuabSc 5MOSWh+j8fKj0KOFZWoUXp1gjtby/ApwktgLcWKift0qLL5Q8/nobSXy/4c4zUKBoWs7 vZPCCu7W9ARASaXeno/CgEaSuZXHzc5whUFixKvHgZx0iA4TTSpdl0f5I/fpC0Q4a3Sz PrTflYhaQOHJSK5KKJ8asQREI0O50kzAmwUp4o4VcIAytfGkAEENaJd9TUCuk8Q9/E4R M4raR0+UcvieoZ3IzELS3+bvo0h/cn2OtzSoACmbVytbxwtfhWUgLZPs73S1sSqwWyop Gwww==
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=WyzqTRLggxDJDVnN2gBd/xoFffQq8EDMKy7aVL8hvdU=; b=ksUu/IZrzA3t0eDnqtRMRgRGG6yGRB4u2UVpgmrnYomctaDpdj6eJE0MY0AHBF5r+4 clLVrbMButwdxCZCF1CQgmdYTyGsIj1BkxIfziQ5ucDl0HdnPe6Jv12nyhFhIGAnE2CS fjPowxZsVUa7t9d43PgI8xbayazWcWmx9+eS1lVqoUIhQR2DmwBxAHmtCdtpSGDz1Ubg af9judWWWIpE/Fei+Iyel9qdEHNUdUOcjk0dkFvFM1r0TobtwPjCERqVwkFo0LBS+Vw0 zr4edXGBVARUfnkEJt4dnlzMLs18rd0Tc8yhA32bTA4vsSds05XRWsjDFuLskpfhfJeX twAQ==
X-Gm-Message-State: ANhLgQ2U81l3HEPOHmkJ3sRVAkL7pCW1WgcFfNIffrF0m666dBlkWfzV PozPeNUpJopiFS3wCi5Eb+hIRAVVTi0ACFkXhnOiWw==
X-Google-Smtp-Source: ADFU+vsWCeLJxC3j15N7wi8R1HgoSNSl6fLT/SGwyqZg4l2gHeGDSo8WXNDo4QIIq5hYNtf/jWDjIYrAVXFYHk8GOOo=
X-Received: by 2002:a67:8844:: with SMTP id k65mr3552716vsd.231.1585155340612; Wed, 25 Mar 2020 09:55:40 -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>
In-Reply-To: <CAKKJt-d-6O1_aP1_7KENQSMYyE5yLhrbSCxec1TEEDB_0ss6=Q@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Wed, 25 Mar 2020 09:55:28 -0700
Message-ID: <CAOJ7v-0SEtMPedQ=Jga5ErTTTeacUjCKTOZd1arzUDKDVXjyoQ@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="000000000000fe1fea05a1b0bc72"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v3/YCSfJD6RLvxRg5dgoPWD9mcPCGE>
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 16:55:45 -0000
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.
- [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