Re: [dispatch] Virtual IETF107 - SRT draft is available
Colin Perkins <csp@csperkins.org> Fri, 20 March 2020 12:16 UTC
Return-Path: <csp@csperkins.org>
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 CFD583A08E4 for <dispatch@ietfa.amsl.com>; Fri, 20 Mar 2020 05:16:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 KcUBkYCMsh8w for <dispatch@ietfa.amsl.com>; Fri, 20 Mar 2020 05:16:04 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0590D3A07F9 for <dispatch@ietf.org>; Fri, 20 Mar 2020 05:16:04 -0700 (PDT)
Received: from [81.187.2.149] (port=43654 helo=[192.168.0.66]) by haggis.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from <csp@csperkins.org>) id 1jFGZE-0005mL-87; Fri, 20 Mar 2020 12:16:00 +0000
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <F97AADA9-817E-4D3D-B6AF-BEC145359851@mnot.net>
Date: Fri, 20 Mar 2020 12:15:57 +0000
Cc: "Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com>, "dispatch@ietf.org" <dispatch@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F3D6E154-F47C-41C6-B6EB-A448B86E1D99@csperkins.org>
References: <A928C153-0E0B-41E6-8A7E-2752D8137408@nbcuni.com> <F97AADA9-817E-4D3D-B6AF-BEC145359851@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.3445.104.11)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/i5avCs7hl3oZt4Nhs1esqzP09-s>
Subject: Re: [dispatch] Virtual IETF107 - SRT draft is available
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: Fri, 20 Mar 2020 12:16:07 -0000
> On 19 Mar 2020, at 00:22, Mark Nottingham <mnot@mnot.net> wrote: > On 19 Mar 2020, at 8:26 am, Deen, Glenn (NBCUniversal) <Glenn.Deen@nbcuni.com> wrote: >> >> * why would anyone choose to do this as opposed to something like QUIC? QUIC provides certain security properties, whereas I have very little confidence in the claimed security properties of this protocol. >> >> [GD] SRT has reliable delivery features that are needed for media distribution and are not part of QUIC and wouldn't be likely to be added to QUIC. So QUIC isn't a replacement for SRT, though it is entirely possible that at some point SRT may be run over QUIC. >> >> [GD] SRT has features that meet media specific needs. For example consider the need to reliably deliver a live sporting event quickly from the stadium to the distribution carriers such as your local TV station or cable company or streaming operator. It's used when the media stream MUST arrive at the studio and can't tolerate retrains. It's not only for live events but such events are a great use-case for the Reliable aspects of SRT. > > QUIC has reliable delivery of streams by default, and the WG has just adopted <https://tools.ietf.org/html/draft-ietf-quic-datagram-00> for unreliable delivery. Is there any feature of SRT that can't be built on top of those primitives? Or on top of Secure RTP and RTSP, which seem to occupy a very similar space to SRT. -- Colin Perkins https://csperkins.org/
- [dispatch] Virtual IETF107 - SRT draft is availab… 김준웅님(JOONWOONG.KIM)
- Re: [dispatch] Virtual IETF107 - SRT draft is ava… Ben Campbell
- Re: [dispatch] Virtual IETF107 - SRT draft is ava… Deen, Glenn (NBCUniversal)
- Re: [dispatch] Virtual IETF107 - SRT draft is ava… Eric Rescorla
- Re: [dispatch] Virtual IETF107 - SRT draft is ava… Eric Rescorla
- Re: [dispatch] Virtual IETF107 - SRT draft is ava… Martin Thomson
- Re: [dispatch] Virtual IETF107 - SRT draft is ava… Deen, Glenn (NBCUniversal)
- Re: [dispatch] Virtual IETF107 - SRT draft is ava… Spencer Dawkins at IETF
- Re: [dispatch] Virtual IETF107 - SRT draft is ava… Mark Nottingham
- Re: [dispatch] Virtual IETF107 - SRT draft is ava… Alexandre GOUAILLARD
- Re: [dispatch] Virtual IETF107 - SRT draft is ava… Eric Rescorla
- Re: [dispatch] Virtual IETF107 - SRT draft is ava… 김준웅님(JOONWOONG.KIM)
- Re: [dispatch] Virtual IETF107 - SRT draft is ava… 김준웅님(JOONWOONG.KIM)
- Re: [dispatch] Virtual IETF107 - SRT draft is ava… Mark Nottingham
- Re: [dispatch] Virtual IETF107 - SRT draft is ava… 김준웅님(JOONWOONG.KIM)
- Re: [dispatch] Virtual IETF107 - SRT draft is ava… Colin Perkins
- Re: [dispatch] Virtual IETF107 - SRT draft is ava… Maxim Sharabayko
- Re: [dispatch] Virtual IETF107 - SRT draft is ava… Patrick McManus