Revise Abstract and Introduction #72
Conversation
draft-omara-sframe.md
Outdated
|
|
||
| This document proposes a new end-to-end encryption mechanism known as SFrame, specifically designed to work in group conference calls with SFUs. | ||
| This document proposes a new end-to-end encryption mechanism known as SFrame, specifically designed to work in group conference calls with SFUs. SFrame is a general encryption framing that can be used to protect payloads sent over SRTP | ||
|
|
||
| ~~~~~ |
There was a problem hiding this comment.
Here's a scary experiment:
| ~~~~~ | |
| ~~~ aasvg |
There was a problem hiding this comment.
What is this supposed to do? Auto-generate SVG from ASCII art?
|
Needs rebasing. I am not sure what the changes should look like, @bifurcation , can you do the rebasing? |
|
|
||
| The proposed mechanism differs from the Secure Real-Time Protocol (SRTP) in that | ||
| it is independent of RTP (thus compatible with non-RTP media transport) and can | ||
| be applied to whole media frames in order to be more bandwidth efficient. |
There was a problem hiding this comment.
This one is 80 char wrapped, not the other section.
We should probably try to be consistent.
There was a problem hiding this comment.
Updated the sections affected by this PR. I can do a global 80-char-wrap PR once the current queue drains.
|
|
||
| --- middle | ||
|
|
||
|
|
||
| # Introduction | ||
| Modern multi-party video call systems use Selective Forwarding Unit (SFU) servers to efficiently route RTP streams to call endpoints based on factors such as available bandwidth, desired video size, codec support, and other factors. In order for the SFU to work properly though, it needs to be able to access RTP metadata and RTCP feedback messages, which is not possible if all RTP/RTCP traffic is end-to-end encrypted. |
There was a problem hiding this comment.
Do we need to spell out SFU since we already clarified what this is in the abstract?
There was a problem hiding this comment.
Seems like it doesn't hurt, and might improve clarity if someone skips the abstract.
Co-authored-by: youennf <youennf@users.noreply.github.com>
No description provided.