Encrypted Key Transport for DTLS and Secure RTP
draft-ietf-perc-srtp-ekt-diet-10

Document Type Active Internet-Draft (perc WG)
Last updated 2019-09-02 (latest revision 2019-07-08)
Replaces draft-jennings-perc-srtp-ekt-diet
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Suhas Nandakumar
Shepherd write-up Show (last changed 2018-07-15)
IESG IESG state IESG Evaluation::AD Followup
Consensus Boilerplate Yes
Telechat date
Has 2 DISCUSSes. Needs 3 more YES or NO OBJECTION positions to pass.
Responsible AD Alexey Melnikov
Send notices to Suhas Nandakumar <suhasietf@gmail.com>
IANA IANA review state IANA OK - Actions Needed
Network Working Group                                        C. Jennings
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                             J. Mattsson
Expires: January 9, 2020                                     Ericsson AB
                                                               D. McGrew
                                                           Cisco Systems
                                                                 D. Wing

                                                            F. Andreason
                                                           Cisco Systems
                                                            July 8, 2019

            Encrypted Key Transport for DTLS and Secure RTP
                    draft-ietf-perc-srtp-ekt-diet-10

Abstract

   Encrypted Key Transport (EKT) is an extension to DTLS (Datagram
   Transport Layer Security) and Secure Real-time Transport Protocol
   (SRTP) that provides for the secure transport of SRTP master keys,
   rollover counters, and other information within SRTP.  This facility
   enables SRTP for decentralized conferences by distributing a common
   key to all of the conference endpoints.

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."

   This Internet-Draft will expire on January 9, 2020.

Copyright Notice

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

Jennings, et al.         Expires January 9, 2020                [Page 1]
Internet-Draft                  EKT SRTP                       July 2019

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Conventions Used In This Document . . . . . . . . . . . . . .   4
   4.  Encrypted Key Transport . . . . . . . . . . . . . . . . . . .   4
     4.1.  EKTField Formats  . . . . . . . . . . . . . . . . . . . .   5
     4.2.  SPIs and EKT Parameter Sets . . . . . . . . . . . . . . .   8
     4.3.  Packet Processing and State Machine . . . . . . . . . . .   8
       4.3.1.  Outbound Processing . . . . . . . . . . . . . . . . .   8
       4.3.2.  Inbound Processing  . . . . . . . . . . . . . . . . .  10
     4.4.  Ciphers . . . . . . . . . . . . . . . . . . . . . . . . .  12
       4.4.1.  AES Key Wrap  . . . . . . . . . . . . . . . . . . . .  12
       4.4.2.  Defining New EKT Ciphers  . . . . . . . . . . . . . .  13
     4.5.  Synchronizing Operation . . . . . . . . . . . . . . . . .  13
     4.6.  Timing and Reliability Consideration  . . . . . . . . . .  13
   5.  Use of EKT with DTLS-SRTP . . . . . . . . . . . . . . . . . .  14
     5.1.  DTLS-SRTP Recap . . . . . . . . . . . . . . . . . . . . .  15
     5.2.  SRTP EKT Key Transport Extensions to DTLS-SRTP  . . . . .  15
       5.2.1.  Negotiating an EKTCipher  . . . . . . . . . . . . . .  17
       5.2.2.  Establishing an EKT Key . . . . . . . . . . . . . . .  17
     5.3.  Offer/Answer Considerations . . . . . . . . . . . . . . .  19
     5.4.  Sending the DTLS EKTKey Reliably  . . . . . . . . . . . .  19
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  19
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  21
     7.1.  EKT Message Types . . . . . . . . . . . . . . . . . . . .  21
     7.2.  EKT Ciphers . . . . . . . . . . . . . . . . . . . . . . .  21
     7.3.  TLS Extensions  . . . . . . . . . . . . . . . . . . . . .  22
     7.4.  TLS Handshake Type  . . . . . . . . . . . . . . . . . . .  22
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  23
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  23
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  23
Show full document text