Browse Prior Art Database

Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution (RFC7202)

IP.com Disclosure Number: IPCOM000236250D
Publication Date: 2014-Apr-15
Document File: 20 page(s) / 23K

Publishing Venue

The IP.com Prior Art Database

Related People

C. Perkins: AUTHOR [+2]

Abstract

The Real-time Transport Protocol (RTP) [RFC3550] is widely used for voice over IP, Internet television, video conferencing, and other real-time and streaming media applications. Despite this use, the basic RTP specification provides only limited options for media security and defines no standard key exchange mechanism. Rather, a number of extensions are defined that can provide confidentiality and authentication of RTP media streams and RTP Control Protocol (RTCP) messages. Other mechanisms define key exchange protocols. This memo outlines why it is appropriate that multiple extension mechanisms are defined rather than mandating a single security and keying mechanism for all users of RTP.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 12% of the total text.

Internet Engineering Task Force (IETF)                        C. Perkins Request for Comments: 7202                         University of Glasgow Category: Informational                                    M. Westerlund ISSN: 2070-1721                                                 Ericsson                                                               April 2014

                       Securing the RTP Framework:        Why RTP Does Not Mandate a Single Media Security Solution

Abstract

   This memo discusses the problem of securing real-time multimedia    sessions.  It also explains why the Real-time Transport Protocol    (RTP) and the associated RTP Control Protocol (RTCP) do not mandate a    single media security mechanism.  This is relevant for designers and    reviewers of future RTP extensions to ensure that appropriate    security mechanisms are mandated and that any such mechanisms are    specified in a manner that conforms with the RTP architecture.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7202.

 Perkins & Westerlund          Informational                     [Page 1]
 RFC 7202               Securing the RTP Framework             April 2014

 Copyright Notice

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2    2.  RTP Applications and Dep...