Skip to content

Update charter.txt #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update charter.txt #23

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions charter.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,10 +15,11 @@ many extensions into HTTP. The group will limit itself to supporting the
functionality in widespread actual usage today.

The protocol uses HTTP techniques for authentication and authorization
(notably OAuth), and requires hop by hop encryption (i.e., https). The
protocol will also allow for e2e media encryption, although keying is
out of scope, and is expected to be handled by other protocols such as
MLS. This extension will also utilize STIR for callerID.
and requires hop by hop encryption (i.e., https). The protocol will
also specify a technnique for encapsulated e2e encrypted media
Copy link

@bifurcation bifurcation Apr 11, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would propose that E2E encryption of media should be mandatory, just like SRTP is mandatory in WebRTC. It should never be possible for elements in the middle just to grab stuff, without explicit authorization. So something like:

The protocol will carry media in an end-to-end encrypted form in order to prevent access by unauthorized intermediary devices. (Some authorized intermediaries may be provided with keys, depending on the key management protocol.)

packets, and will specify mandatory-to-implement protocol for keying
(likely MLS) and identity (likely STIR passports). This extension will
also utilize STIR for callerID.

This protocol should be implementable in browsers, thick desktop
clients, mobile apps and servers.
Expand Down