Completely Encrypting RTP Header Extensions and Contributing Sources
draft-uberti-avtcore-cryptex-01
| Document | Type |
Replaced Internet-Draft
(avtcore WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Justin Uberti , Cullen Fluffy Jennings | ||
| Last updated | 2021-01-03 (Latest revision 2020-11-02) | ||
| Replaced by | draft-ietf-avtcore-cryptex | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-avtcore-cryptex | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
While the Secure Real-time Transport Protocol (SRTP) provides confidentiality for the contents of a media packet, a significant amount of metadata is left unprotected, including RTP header extensions and contributing sources (CSRCs). However, this data can be moderately sensitive in many applications. While there have been previous attempts to protect this data, they have had limited deployment, due to complexity as well as technical limitations. This document proposes a new mechanism to completely encrypt header extensions and CSRCs as well a simpler signaling mechanism intended to facilitate deployment.
Authors
Justin Uberti
Cullen Fluffy Jennings
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)