Transporting the SDP attribute 'dtls-id' in TLS and DTLS
draft-jones-perc-dtls-id-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           P. Jones
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                             N. Ohlmeier
Expires: September 14, 2017                                      Mozilla
                                                          March 13, 2017

        Transporting the SDP attribute 'dtls-id' in TLS and DTLS
                      draft-jones-perc-dtls-id-00

Abstract

   This draft defines a new extension to carry the "dtls-id" value
   defined for use in the Session Description Protocol within TLS and
   DTLS.

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 http://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 September 14, 2017.

Copyright Notice

   Copyright (c) 2017 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
   (http://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.

Jones & Ohlmeier       Expires September 14, 2017               [Page 1]
Internet-Draft           dtls-id in TLS and DTLS              March 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions Used In This Document . . . . . . . . . . . . . .   2
   3.  Endpoint procedures . . . . . . . . . . . . . . . . . . . . .   3
   4.  Media distributor procedures  . . . . . . . . . . . . . . . .   3
   5.  Key distributor procedures  . . . . . . . . . . . . . . . . .   3
   6.  The dtls_id TLS extension . . . . . . . . . . . . . . . . . .   4
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   10. Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The Privacy-Enhanced RTP Conferencing (PERC) working group specified
   a DTLS [RFC6347] tunneling mechanism [I-D.ietf-perc-dtls-tunnel] that
   enables a media distributor to forward DTLS messages between an
   endpoint and a key distributor.  In the process, the media
   distributor is able to securely receive only the hop-by-hop keying
   material, while the endpoints are able to securely receive both end-
   to-end and hob-by-hop keying material.

   An open issue with the current design is how the key distributor can
   determine which one of several conferences an endpoint is attempting
   to join.  The only information that the key distributor receives via
   the DTLS tunnel is the endpoint's certificate.  However, the same
   certificate might be used to join several conferences in parallel,
   thus creating a need for additional information.

   [I-D.ietf-mmusic-dtls-sdp] defines an attribute in SDP [RFC4566]
   called the "dlts-id".  The "dtls-id" presented by the endpoint's in
   SDP will be unique for each DTLS association established using the
   same certificate.  By signaling the certificate fingerprint and
   "dtls-id" in SDP, along with including the same in the DTLS signaling
   sent to the key distributor, it would be possible for the key
   distributor to unambiguously determine which conference key the
   endpoint should receive.

2.  Conventions Used In This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119] when they
Show full document text