Re: [V3] Thoughts on scope for ript

Spencer Dawkins at IETF <> Wed, 25 March 2020 16:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 49B493A0BCF for <>; Wed, 25 Mar 2020 09:28:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 8BZGL-23-_ke for <>; Wed, 25 Mar 2020 09:28:20 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::135]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 332033A085C for <>; Wed, 25 Mar 2020 09:28:20 -0700 (PDT)
Received: by with SMTP id n20so2299780lfl.10 for <>; Wed, 25 Mar 2020 09:28:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KAuACdV8vgd+R96U83ycLJxsAYqsbt9bCqLD80q68OU=; b=CFhFRgNKjk0MvnILrelSJ7nuBseGaLnDABRyJk4F7PklAVFW8dtJZBmdSoowHe8wXd wbxqcdpHmgPRVrTpMalFtS6CeMJcjHRLDrLF+z1AbhBWzTs2AO8BaG03VbyvDuXjGHlj K0ZMu3k5yaeopfm+4c2C11e3d79fKENbTVfv2GGy/MJ08vS6MDxFDkPF5m71/uWkmYMA n3oW2MH2DLuPU47Z3hWeLsWx+nC98iTnVPteiGkyZCGQ3oSN1hn7xHp9q9ecyjK6nKF6 HTOqzInQwuxYdXA1hOwiFgNb63wVELhM5YfxLkZPkcLZB8Pm/h5ChDyIB/C01Il0o7NF OnIA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KAuACdV8vgd+R96U83ycLJxsAYqsbt9bCqLD80q68OU=; b=C2q/FN1eovM9nOLHw1eC3dIhBBGt0+lCf4VkeacXttOTGgEq41x3e3KrJQGizqGWWd pTGwZvNdPwCSfT45ufS5p8DG3emGNoJCDo2sBXnizqvI7bSoQ7cwpHGLqMnHFGK8V9Wx f9PEYzP7nhNJc0vRNt3PBCMiUg4Hli5K3LZ4GfMTWxaO6j+bI/wlAikwWmL0UtpsSwJ8 7NRVnEquhEsXVMTUiDWQZDGz9F+mBN+B29z2/tgnCsy+MoGUQXv1keAAJ1u78hlKMBga YVCu2S0+DJofi7mgcfrmLTgAFaBXHhEZiT90lCd08QvB3h8eGzqtejVImAreBp+iryn6 k36A==
X-Gm-Message-State: ANhLgQ0h6pi99zoMqgpkga+nn+yTVFyzhuE9jqgKSSLZWC423vQOx+ut xbWIdmblrk4QIdsEAf5kVr60bZq6AUQOniSeVU4=
X-Google-Smtp-Source: ADFU+vtfBHeEDGwkNAJ+6A1xJNHzy930ohrcyaLHK2g0uyFGpNx+s9+QKGvt7KTUi+Eg9pDYt/uQEOXStaNl2nyC8ZI=
X-Received: by 2002:ac2:4433:: with SMTP id w19mr2834857lfl.53.1585153697006; Wed, 25 Mar 2020 09:28:17 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <>
In-Reply-To: <>
From: Spencer Dawkins at IETF <>
Date: Wed, 25 Mar 2020 11:27:51 -0500
Message-ID: <>
To: Victor Vasiliev <>
Cc: Justin Uberti <>, Jonathan Rosenberg <>, "" <>
Content-Type: multipart/alternative; boundary="00000000000006474b05a1b05b85"
Archived-At: <>
Subject: Re: [V3] Thoughts on scope for ript
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 25 Mar 2020 16:28:23 -0000

This is interesting ...

On Wed, Mar 25, 2020 at 10:31 AM Victor Vasiliev <vasilvv=> 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?