From f97dfa0bd1ba72fb0303377dbb40a7fe22717282 Mon Sep 17 00:00:00 2001 From: Sergio Garcia Murillo Date: Thu, 21 Oct 2021 15:47:10 +0200 Subject: [PATCH] Typo /mechanishm/mechanism --- draft-ietf-wish-whip.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-wish-whip.md b/draft-ietf-wish-whip.md index 32bb898..5665f9b 100644 --- a/draft-ietf-wish-whip.md +++ b/draft-ietf-wish-whip.md @@ -49,7 +49,7 @@ This document proposes a simple HTTP based protocol that will allow WebRTC based # Introduction -RTCWEB standardized JSEP ({{!RFC8829}}), a mechanishm used to control the setup, management, and teardown of a multimedia session, how to apply it using the SDP Offer/Answer model and all the formats for the data sent over the wire (media, codec, encryption, ...). Also, WebRTC intentionally does not specify a signaling transport protocol at application level. This flexibility has allowed the implementation of a wide range of services. However, those services are typically standalone silos which don't require interoperability with other services or leverage the existence of tools that can communicate with them. +RTCWEB standardized JSEP ({{!RFC8829}}), a mechanism used to control the setup, management, and teardown of a multimedia session, how to apply it using the SDP Offer/Answer model and all the formats for the data sent over the wire (media, codec, encryption, ...). Also, WebRTC intentionally does not specify a signaling transport protocol at application level. This flexibility has allowed the implementation of a wide range of services. However, those services are typically standalone silos which don't require interoperability with other services or leverage the existence of tools that can communicate with them. In the broadcasting/streaming world, the usage of hardware encoders that make it very simple to plug in (SDI) cables carrying raw media, encode it in place, and push it to any streaming service or CDN ingest is already ubiquitous. It is the adoption of a custom signaling transport protocol for each WebRTC service has hindered broader adoption as an ingestion protocol.