Re: [V3] Thoughts on scope for ript

Anthony Minessale <> Wed, 25 March 2020 16:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 27CC03A0A45 for <>; Wed, 25 Mar 2020 09:54:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Status: No, score=-1.988 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, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id YPRzX-EqU0ca for <>; Wed, 25 Mar 2020 09:54:11 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::a31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 012F03A0A03 for <>; Wed, 25 Mar 2020 09:54:10 -0700 (PDT)
Received: by with SMTP id o124so867234vkc.4 for <>; Wed, 25 Mar 2020 09:54:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Iteuc/uJw4uyL4d7vyBpvfJ5gU2LNPL6t4Vn1PsW8S8=; b=YsuBO22n42VCYQbRJbxlEDjQfD9uq7ynIBs2kGQxdqPJAf6AxKVGyTqTnQa2jbmGfw qqo13X1oV/v345CoHSVT6W9/JxbM2KgGnC7PXuCe0iWCG8Ayt+mWhLt3FrnnEhByNkdk iaDgoprBAuARAU0W1QO+MO1xqHkXTkLHroet8=
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=Iteuc/uJw4uyL4d7vyBpvfJ5gU2LNPL6t4Vn1PsW8S8=; b=bAgJahVgyg+yoMPtiOlQLAqoYBfYg0ScY5d6elp+kgTiejaUtj9y1fiND+vmJo0du4 9XQVyNJbIYf06c+R5K1yz8A1S6JEDlazKFSQnUo11R8yPvoqe74lJ3fUTJnsLM2UKFaK NWova1MrVSQ8yemGXRgx0/JLE4ybM63BuPoSG1pHKsyXkpI1aogh/gkicMbUlgCVJbSk 0QJEz2tnctu8ZN61r5w4hvomU2Wv82XPnDkj3gtVYeqp3tZojHu7ieJoKE6Jrb1rq+Da 3S4azOb/Qm0wpLV7TcbyIr+zNeDUKCTqmNZyUciiTMsad0ZuEtE9oOPPm0Jj93IWEgwR yOPA==
X-Gm-Message-State: ANhLgQ0GRGdX0Ijy1tbL7rFJ6dcjeoUHLWswxt8XRhSsshSCkByAlKlr nZXDzXdpWGG0kXOSMURaaidXnjUVnZnI0vNNtH0ZPA==
X-Google-Smtp-Source: ADFU+vshLdD4sF31mmSC8UTH7cMY3cnz/kMd7r5DHrGIrfJ9KJZ1zhjTfEaaNRsHAfMyxIkSPhDY9yUdtZf2x65ZGsI=
X-Received: by 2002:a1f:2c4b:: with SMTP id s72mr3280889vks.93.1585155249268; Wed, 25 Mar 2020 09:54:09 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <> <>
In-Reply-To: <>
From: Anthony Minessale <>
Date: Wed, 25 Mar 2020 11:53:57 -0500
Message-ID: <>
To: Spencer Dawkins at IETF <>
Cc: Victor Vasiliev <>, "" <>, Jonathan Rosenberg <>, Justin Uberti <>
Content-Type: multipart/related; boundary="0000000000008c9e2205a1b0b757"
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:54:14 -0000

On Wed, Mar 25, 2020 at 11:28 AM Spencer Dawkins at IETF <> wrote:

> 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?
Being "as good as RTP" is relative and so is "quality" There is quality
like how it sounds and quality like (how many packets did I get that I am
supposed to be getting and are they on time, are they dejittered and are
they dropped when they are too old)
If the media signal is in good shape then the second type makes all the
difference in preserving that.

One thing about RTP that is helpful but often not taken advantage of is
that you can pass it through as is even out of order and messed up and the
final thing to receive the stream can put things back together.
If something in the middle just cleanses it and rewrites all the timestamps
you get a permanently messed-up stream that can never be fixed.
Sometimes you want to dejitter and rewrite the packets when you know the
next hop has no way to do it but otherwise usually only when you are the
final terminating leg.

Everything RTP can do to make sure you have these features should be
duplicated or maybe an encapsulation mode to just carry old school RTP as a
payload so 2 aincent devices can still exchange RTP across a RIPT-wormhole.

> Best,
> Spencer
> --
> V3 mailing list


Anthony Minessale  | Founder and CEO

SignalWire: *228 Hamilton Ave 3rd Floor, Palo Alto, CA 94303

* <>* <>


Phone: 262-309-8501

Website: <>