[AVTCORE] RFC 6904 on Encryption of Header Extensions in the Secure Real-time Transport Protocol (SRTP)

rfc-editor@rfc-editor.org Thu, 18 April 2013 16:58 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 7870321F90B4; Thu, 18 Apr 2013 09:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.115
X-Spam-Status: No, score=-102.115 tagged_above=-999 required=5 tests=[AWL=-0.115, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id pyplVzaJj7uI; Thu, 18 Apr 2013 09:58:48 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 1702821F90AC; Thu, 18 Apr 2013 09:58:48 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id EB792B1E002; Thu, 18 Apr 2013 09:57:42 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130418165742.EB792B1E002@rfc-editor.org>
Date: Thu, 18 Apr 2013 09:57:42 -0700
Cc: avt@ietf.org, rfc-editor@rfc-editor.org
Subject: [AVTCORE] RFC 6904 on Encryption of Header Extensions in the Secure Real-time Transport Protocol (SRTP)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Apr 2013 16:58:48 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 6904

        Title:      Encryption of Header Extensions in 
                    the Secure Real-time Transport Protocol (SRTP) 
        Author:     J. Lennox
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2013
        Mailbox:    jonathan@vidyo.com
        Pages:      15
        Characters: 33486
        Updates:    RFC 3711

        I-D Tag:    draft-ietf-avtcore-srtp-encrypted-header-ext-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6904.txt

The Secure Real-time Transport Protocol (SRTP) provides
authentication, but not encryption, of the headers of Real-time
Transport Protocol (RTP) packets.  However, RTP header extensions may
carry sensitive information for which participants in multimedia
sessions want confidentiality.  This document provides a mechanism,
extending the mechanisms of SRTP, to selectively encrypt RTP header
extensions in SRTP.

This document updates RFC 3711, the Secure Real-time Transport
Protocol specification, to require that all future SRTP encryption
transforms specify how RTP header extensions are to be encrypted.

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC