IETF Logo Mail Archive

Re: [AVTCORE] I-D Action: draft-ietf-avtcore-srtp-encrypted-header-ext-03.txt

Jonathan Lennox <jonathan@vidyo.com> Mon, 22 October 2012 22:33 UTC

Return-Path: <jonathan@vidyo.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C741921F8566 for <avt@ietfa.amsl.com>; Mon, 22 Oct 2012 15:33:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level:
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zy4d2eBYH7Pv for <avt@ietfa.amsl.com>; Mon, 22 Oct 2012 15:33:26 -0700 (PDT)
Received: from mxout.myoutlookonline.com (mxout.myoutlookonline.com [64.95.72.241]) by ietfa.amsl.com (Postfix) with ESMTP id 3E50921F8203 for <avt@ietf.org>; Mon, 22 Oct 2012 15:33:26 -0700 (PDT)
Received: from mxout.myoutlookonline.com (localhost [127.0.0.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id 979D68BEBF0 for <avt@ietf.org>; Mon, 22 Oct 2012 18:33:25 -0400 (EDT)
X-Virus-Scanned: by SpamTitan at mail.lan
Received: from HUB012.mail.lan (unknown [10.110.2.1]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mxout.myoutlookonline.com (Postfix) with ESMTPS id 522FB8BEB1F for <avt@ietf.org>; Mon, 22 Oct 2012 18:33:25 -0400 (EDT)
Received: from BE235.mail.lan ([10.110.32.235]) by HUB012.mail.lan ([10.110.17.12]) with mapi; Mon, 22 Oct 2012 18:33:21 -0400
From: Jonathan Lennox <jonathan@vidyo.com>
To: IETF AVTCore WG <avt@ietf.org>
Date: Mon, 22 Oct 2012 18:33:24 -0400
Thread-Topic: [AVTCORE] I-D Action: draft-ietf-avtcore-srtp-encrypted-header-ext-03.txt
Thread-Index: Ac2wpT3O0erfF/fJSGKmGz/3OWJP6g==
Message-ID: <AC937D9D-43FD-477A-B552-2D0C6D14F059@vidyo.com>
References: <20121022222715.28412.59035.idtracker@ietfa.amsl.com>
In-Reply-To: <20121022222715.28412.59035.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-srtp-encrypted-header-ext-03.txt
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: Mon, 22 Oct 2012 22:33:26 -0000

This version incorporates the changes suggested to the draft by David McGrew during the second WGLC.  All known outstanding comments have now been resolved.

On Oct 22, 2012, at 6:27 PM, <internet-drafts@ietf.org> wrote:

> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Audio/Video Transport Core Maintenance Working Group of the IETF.
> 
> 	Title           : Encryption of Header Extensions in the Secure Real-Time Transport Protocol (SRTP)
> 	Author(s)       : Jonathan Lennox
> 	Filename        : draft-ietf-avtcore-srtp-encrypted-header-ext-03.txt
> 	Pages           : 15
> 	Date            : 2012-10-22
> 
> Abstract:
>   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 SRTP encryption
>   transforms specify how RTP header extensions are to be encrypted.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-avtcore-srtp-encrypted-header-ext
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-avtcore-srtp-encrypted-header-ext-03
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-srtp-encrypted-header-ext-03
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
> 

--
Jonathan Lennox
jonathan@vidyo.com

v2.23.0 | Report a Bug | By Email