Negotiating SRTP and RTCP Feedback using the RTP/AVP Profile
draft-ietf-mmusic-opportunistic-negotiation-01

Document Type Active Internet-Draft (mmusic WG)
Last updated 2017-10-16 (latest revision 2017-09-14)
Replaces draft-hutton-mmusic-opportunistic-negotiation
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state WG Document (wg milestone: Dec 2017 - Submit Negotiating S... )
Document shepherd Bo Burman
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to Bo Burman <bo.burman@ericsson.com>
Network Working Group                                          A. Hutton
Internet-Draft                                              Unify / Atos
Updates: 4568,4585 (if approved)                               R. Jesske
Intended status: Standards Track                        Deutsche Telekom
Expires: March 18, 2018                                      A. Johnston
                                                        Rowan University
                                                            G. Salgueiro
                                                                   Cisco
                                                                B. Aboba
                                                               Microsoft
                                                      September 14, 2017

      Negotiating SRTP and RTCP Feedback using the RTP/AVP Profile
             draft-ietf-mmusic-opportunistic-negotiation-01

Abstract

   This document describes how the use of the Secure Real-time transport
   protocol (SRTP) [RFC3711]. can be negotiated using the RTP/AVP (Audio
   Video Profile) defined in [RFC3551].  Such a mechanism is used to
   provide a means for encrypted media to be used in environments where
   support for encryption is not known in advance, and not required.
   The same mechanism is also applied to negotiation of the Extended RTP
   Profile for Real-time Transport Control Protocol Based Feedback (RTP/
   AVPF) [RFC4585].

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 March 18, 2018.

Hutton, et al.           Expires March 18, 2018                 [Page 1]
Internet-Draft          Negotiating RTP Profiles          September 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
   (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
   2.  Normative Language  . . . . . . . . . . . . . . . . . . . . .   3
   3.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Use of RTP/AVP profile with SRTP  . . . . . . . . . . . . . .   3
   5.  Use of RTP/AVP profile with RTCP Feedback . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Opportunistic Security [RFC7435] is an approach to security that
   defines a third mode for security between "cleartext" and
   "comprehensive protection" that allows encryption and authentication
   to be used if supported but will not result in failures if it is not
   supported.  In terms of secure media, cleartext is RTP [RFC3550]
   media which is negotiated with the RTP/AVP (Audio Video Profile)
   profile defined [RFC3551].  Comprehensive protection is Secure RTP
   [RFC3711], negotiated with a secure profile, such as RTP/SAVP or RTP/
   SAVPF [RFC5124].

   [I-D.ietf-sipbrandy-osrtp] describes how Secure Real-time transport
   protocol (SRTP) can be negotiated opportunistically.

   [RFC4568] however requires that SRTP is only negotiated using the
   RTP/SAVP profile [RFC3711] or the RTP/SAVPF profile [RFC5124].  This
Show full document text