Multiplexing Scheme Updates for Secure Real-time Transport Protocol (SRTP) Extension for Datagram Transport Layer Security (DTLS)
draft-ietf-avtcore-rfc5764-mux-fixes-10

The information below is for an old version of the document
Document Type Active Internet-Draft (avtcore WG)
Authors Marc Petit-Huguenin  , Gonzalo Salgueiro 
Last updated 2016-09-01 (latest revision 2016-07-05)
Replaces draft-petithuguenin-avtcore-rfc5764-mux-fixes
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Magnus Westerlund
Shepherd write-up Show (last changed 2016-07-06)
IESG IESG state Approved-announcement to be sent
Consensus Boilerplate Yes
Telechat date
Responsible AD Ben Campbell
Send notices to (None)
IANA IANA review state IANA OK - Actions Needed
AVTCORE                                                M. Petit-Huguenin
Internet-Draft                                        Impedance Mismatch
Updates: 5764 (if approved)                                 G. Salgueiro
Intended status: Standards Track                           Cisco Systems
Expires: January 6, 2017                                    July 5, 2016

  Multiplexing Scheme Updates for Secure Real-time Transport Protocol
     (SRTP) Extension for Datagram Transport Layer Security (DTLS)
                draft-ietf-avtcore-rfc5764-mux-fixes-10

Abstract

   This document defines how Datagram Transport Layer Security (DTLS),
   Real-time Transport Protocol (RTP), RTP Control Protocol (RTCP),
   Session Traversal Utilities for NAT (STUN), Traversal Using Relays
   around NAT (TURN), and ZRTP packets are multiplexed on a single
   receiving socket.  It overrides the guidance from RFC 5764 ("SRTP
   Extension for DTLS"), which suffered from four issues described and
   fixed in this document.

   This document updates RFC 5764.

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 January 6, 2017.

Copyright Notice

   Copyright (c) 2016 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

Petit-Huguenin & SalgueirExpires January 6, 2017                [Page 1]
Internet-Draft             RFC 5764 Mux Fixes                  July 2016

   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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Implicit Allocation of Codepoints for New STUN Methods  . . .   4
   4.  Multiplexing of ZRTP  . . . . . . . . . . . . . . . . . . . .   5
   5.  Implicit Allocation of New Codepoints for TLS ContentTypes  .   5
   6.  Multiplexing of TURN Channels . . . . . . . . . . . . . . . .   6
   7.  RFC 5764 Updates  . . . . . . . . . . . . . . . . . . . . . .   8
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
     9.1.  STUN Methods  . . . . . . . . . . . . . . . . . . . . . .   9
     9.2.  TLS ContentType . . . . . . . . . . . . . . . . . . . . .  10
     9.3.  Traversal Using Relays around NAT (TURN) Channel Numbers   10
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     11.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Appendix A.  Release notes  . . . . . . . . . . . . . . . . . . .  12
     A.1.  Modifications between draft-ietf-avtcore-rfc5764-mux-
           fixes-10 and draft-ietf-avtcore-rfc5764-mux-fixes-09  . .  12
     A.2.  Modifications between draft-ietf-avtcore-rfc5764-mux-
           fixes-09 and draft-ietf-avtcore-rfc5764-mux-fixes-08  . .  13
     A.3.  Modifications between draft-ietf-avtcore-rfc5764-mux-
           fixes-08 and draft-ietf-avtcore-rfc5764-mux-fixes-07  . .  13
Show full document text