RIST is a streaming protocol which allows unreliable/lossy networks such as the internet to be used for critical streaming applications. Called Reliable Internet Stream Protocol, it uses a light-touch mechanism to request any data that’s lost by the network. As losses are often temporary and sporadic, the chances are that the data will get through the second or, perhaps, third time. For a more in-depth explanation of RIST, check out this talk from Merrick Ackermans
The panel here at the IBC 2019 IP Showcase give an brief definition of RIST and then examine how far they’ve got with the ‘Simple Profile’ of RIST calling out things that are yet to be done. Still on the to-do list are such things as ‘pull’ streams, encryption, simplifying the port structure and embedding control.
Fixed Key encryption comes under the microscope next asking whether there’s a practical threat in terms of finding the key but also in terms of whether there are any side-channel attacks in a ‘non-standard’ encryption. The fixed key encryption has been implemented in line with NIST protocols but, as Kieran highlights, getting enough eyes on the detail is difficult with the specification being created outside of an open forum.
The panels covers the recent interop testing which shows overall positive results and then discusses whether RIST is appropriate for uncompressed video. Already, Kieran points out, Amazon Direct Connect is available in 100s of Gb/s links and so it’s completely possible to do uncompressed to the cloud. RTP is over 20 years old and is being used for much more than ever imagined at the time. As technology develops, use of RIST will also develop.
What are the other uses for RIST? Videoconferencing is one possibility, creating a generally secure link to equipment and ingest into the cloud are the others offered.
The panel fishes by looking to the future. Asking how, for instance, the encoder could react to reduced quality of the link. How much of the all the technology needed should be standardised and what features could be added. Sergio Ammirata suggests opening up the protocol for the bandwidth estimation to be requested by any interested device.
This session, bringing together DVEO, OBS, Zixi and Net Insight finishes with questions from the audience.
This webinar brings together Support Partners and Microsoft to explain the term ‘intelligent cloud’ and how this can help creative teams produce higher quality, more innovative content by augmenting human ingenuity, manage content better and grow audiences while increasing advertising and subscription revenue.
The panel will cover:
– Haivision’s SRT Hub, intelligent media routing and cloud-based workflows
– Highlights from partners such as Avid, Telestream and Wowza.
– New production workflows for remote live production, sports and breaking news.
– Connected production: A process that helps with production collaboration and management, removing traditional information and creative silos which exist today, while driving savings and efficiencies from script to screen.
SRT allows unreliable networks like the Internet be used for reliable, encrypted video contribution. Created by Haivision and now an Open Source technology, the alliance of SRT users continues to grow as the technology continues to develop and add features. This panel, from IBC 2019, is an update on what’s new with SRT and how it’s being used daily in broadcast.
Marc Cymontowski starts with an overview of the new features of SRT, mentioning its active Github repository, pointing to recent advances in the encryption available, upcoming FEC and the beginnings of SMPTE ST 2022-7 like redundancy. He also takes a look at how SRT fares against RTMP, the venerable incumbent technology for contribution of streams over the internet. Official support for RTMP will be coming to an end next year, so there is much interest in what may replace it. Marc makes the case that for the same link, SRT tends to have a latency of a half to a third and also performs better at higher bitrates.
RTP, the Real-Time Transport Protocol, is an important feature when it comes to redundancy. By using RTP’s ability to stamp each packet, the receiver can take two identical RTP streams – say from two separate ISPs and fill in missing packets on one stream from the packets of the other stream. This is a very powerful way of ensuring reliability over the internet so Marc makes the point that using SRT doesn’t stop you using RTP.
Simen Frostad then takes to the stage to explain why Bridge Technologies has added SRT support and how the SRT Hub will be very important step forward. Then it’s Leonardo Chaves’ turn who explains how broadcaster Globo is using SRT to transform its video workflows and reduce OPEX costs to one third satellite costs.
Steve Russell from Red Bee talks about how they use SRT to create new, or lower cost, circuits and services to their customers. They’re able to use the internet not only for contribution from events but also to safely get video in and out of the cloud.
With these use-cases in mind, the panel opens up to thirty minutes of wide ranging technical and non-technical questions.
In the west, RTMP is seen as a dying protocol so the hunt is on for a replacement which can be as widely adopted but keep some of it’s best parts including relatively low latency. SRT is a protocol for Secure, Reliable Transport of streams over the internet so does this have a role to play and how does it work?
Alex Converse from Twitch picks up the gauntlet to dive deep into the workings of SRT to show how it compares to RTMP and specifically how it improves upon it.
RTMP fails in many ways, two to focus on are that the spec has stopped moving forward and it doesn’t work well over problematic networks. So Alex takes a few minutes to explain where SRT has come from, the importance of t being open source and how to get hold of the code and more information.
Now, Alex starts his dive into the detail reminding us about UDP, TS Packets and Ethernet MTUs has he goes down. We look at how SRT data packets are formed which helps explain some of the features and sets us up for a more focussed look.
SRT, as with other, similar protocols which create their resilience by retransmitting missing packets, need to use buffers in order to have chance to send the missing data before it’s needed at the decoder. Alex takes us through how the sender and receiver buffers work to understand the behaviour in different situations.
Fundamental to the whole protocol is packet the packet acknowledgement and negative acknowledgements which feature heavily before we discuss handshaking as we start our ascent from the depths of the protocol. As much as acknowledgements provide the reliability, encryption provides the ‘secure’ in Secure Reliable Transport. We look at the approach taken to encryption and how it relates to current encryption for websites.
Finally Alex answers a number of questions from the audience as he concludes this talk from the San Francisco Video Tech meet up.