Completely Encrypting RTP Header Extensions and Contributing Sources
draft-ietf-avtcore-cryptex-00

Document Type Active Internet-Draft (avtcore WG)
Authors Justin Uberti  , Cullen Jennings  , Sergio Garcia Murillo 
Last updated 2021-02-08 (latest revision 2021-01-28)
Replaces draft-uberti-avtcore-cryptex
Stream Internent Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
On Agenda avtcore at IETF-110
Document shepherd Bernard Aboba
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to bernard.aboba@gmail.com
AVTCORE                                                        J. Uberti
Internet-Draft                                                    Google
Intended status: Standards Track                             C. Jennings
Expires: 1 August 2021                                             Cisco
                                                       S. Garcia Murillo
                                                                   CoSMo
                                                         28 January 2021

  Completely Encrypting RTP Header Extensions and Contributing Sources
                     draft-ietf-avtcore-cryptex-00

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.

Discussion Venues

   This note is to be removed before publishing as an RFC.

   Source for this draft and an issue tracker can be found at
   https://github.com/juberti/cryptex.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Uberti, et al.            Expires 1 August 2021                 [Page 1]
Internet-Draft  Completely Encrypting RTP Header Extensi    January 2021

   This Internet-Draft will expire on 1 August 2021.

Copyright Notice

   Copyright (c) 2021 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Simplified BSD License text
   as described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Problem Statement . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Previous Solutions  . . . . . . . . . . . . . . . . . . .   3
     1.3.  Goals . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Design  . . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Signaling . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  RTP Header Processing . . . . . . . . . . . . . . . . . . . .   5
     5.1.  Sending . . . . . . . . . . . . . . . . . . . . . . . . .   6
     5.2.  Receiving . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Encryption and Decryption . . . . . . . . . . . . . . . . . .   7
     6.1.  Packet Structure  . . . . . . . . . . . . . . . . . . . .   7
     6.2.  Encryption Procedure  . . . . . . . . . . . . . . . . . .   8
     6.3.  Decryption Procedure  . . . . . . . . . . . . . . . . . .   8
   7.  Backwards Compatibility . . . . . . . . . . . . . . . . . . .   8
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     11.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

Uberti, et al.            Expires 1 August 2021                 [Page 2]
Internet-Draft  Completely Encrypting RTP Header Extensi    January 2021

1.1.  Problem Statement

   The Secure Real-time Transport Protocol [RFC3711] mechanism provides
   message authentication for the entire RTP packet, but only encrypts
Show full document text