Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Options for Securing RTP Sessions (RFC7201)

IP.com Disclosure Number: IPCOM000236249D
Original Publication Date: 2014-Apr-01
Included in the Prior Art Database: 2014-Apr-16
Document File: 74 page(s) / 92K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Westerlund: AUTHOR [+2]

Abstract

The Real-time Transport Protocol (RTP) [RFC3550] is widely used in a large variety of multimedia applications, including Voice over IP (VoIP), centralized multimedia conferencing, sensor data transport, and Internet television (IPTV) services. These applications can range from point-to-point phone calls, through centralized group teleconferences, to large-scale television distribution services. The types of media can vary significantly, as can the signaling methods used to establish the RTP sessions.

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

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

                    Options for Securing RTP Sessions

Abstract

   The Real-time Transport Protocol (RTP) is used in a large number of    different application domains and environments.  This heterogeneity    implies that different security mechanisms are needed to provide    services such as confidentiality, integrity, and source    authentication of RTP and RTP Control Protocol (RTCP) packets    suitable for the various environments.  The range of solutions makes    it difficult for RTP-based application developers to pick the most    suitable mechanism.  This document provides an overview of a number    of security solutions for RTP and gives guidance for developers on    how to choose the appropriate security mechanism.

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/rfc7201.

 Westerlund & Perkins          Informational                     [Page 1]
 RFC 7201            Options for Securing RTP Sessions         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.

Westerlund & ...