Document Action: 'Options for Securing RTP Sessions' to Informational RFC (draft-ietf-avtcore-rtp-security-options-10.txt)

The IESG <> Thu, 23 January 2014 17:15 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id ADD9F1A0041; Thu, 23 Jan 2014 09:15:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id MPtbn_wGarpB; Thu, 23 Jan 2014 09:15:27 -0800 (PST)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 204011A00A1; Thu, 23 Jan 2014 09:15:25 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Document Action: 'Options for Securing RTP Sessions' to Informational RFC (draft-ietf-avtcore-rtp-security-options-10.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Thu, 23 Jan 2014 09:15:25 -0800
Cc: avtcore chair <>, avtcore mailing list <>, RFC Editor <>
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 23 Jan 2014 17:15:29 -0000

The IESG has approved the following document:
- 'Options for Securing RTP Sessions'
  (draft-ietf-avtcore-rtp-security-options-10.txt) as Informational RFC

This document is the product of the Audio/Video Transport Core
Maintenance Working Group.

The IESG contact persons are Richard Barnes and Gonzalo Camarillo.

A URL of this Internet Draft is:

Technical Summary

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

Working Group Summary

This document complements draft-ietf-avt-srtp-not-mandatory providing information about security options. It was reviewed by the WG members and the WG security experts and there are no issues from the WG that is worth noting.

Document Quality

This document is an overview document and I would like to mention that Dan Wing and Alan Johnston did a review and made helpful comments that helped with the quality of the document.


Document Shepherd is Roni Even and the responsible AD is Richard Barnes.