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

Jonathan Lennox <jonathan@vidyo.com> Fri, 08 February 2013 17:23 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 A1ECA21F8A64 for <avt@ietfa.amsl.com>; Fri, 8 Feb 2013 09:23:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.41
X-Spam-Level:
X-Spam-Status: No, score=-2.41 tagged_above=-999 required=5 tests=[AWL=0.189, 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 vrVskC0NCGMI for <avt@ietfa.amsl.com>; Fri, 8 Feb 2013 09:23:59 -0800 (PST)
Received: from mxout.myoutlookonline.com (mxout.myoutlookonline.com [64.95.72.241]) by ietfa.amsl.com (Postfix) with ESMTP id 2143221F8A5F for <avt@ietf.org>; Fri, 8 Feb 2013 09:23:59 -0800 (PST)
Received: from mxout.myoutlookonline.com (localhost [127.0.0.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id D6ACF41699C for <avt@ietf.org>; Fri, 8 Feb 2013 06:27:03 -0500 (EST)
X-Virus-Scanned: by SpamTitan at mail.lan
Received: from HUB016.mail.lan (unknown [10.110.2.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id 83B8041695D for <avt@ietf.org>; Fri, 8 Feb 2013 06:26:56 -0500 (EST)
Received: from BE235.mail.lan ([10.110.32.235]) by HUB016.mail.lan ([10.110.17.16]) with mapi; Fri, 8 Feb 2013 12:23:51 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: IETF AVTCore WG <avt@ietf.org>
Date: Fri, 08 Feb 2013 12:23:50 -0500
Thread-Topic: [AVTCORE] I-D Action: draft-ietf-avtcore-srtp-encrypted-header-ext-05.txt
Thread-Index: Ac4GIQ9bq9AVGSrnRGSY9c8JrUO7Kg==
Message-ID: <579E797D-9A53-4439-AF4B-D945A9C407CE@vidyo.com>
References: <20130208171514.13325.16330.idtracker@ietfa.amsl.com>
In-Reply-To: <20130208171514.13325.16330.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-05.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: Fri, 08 Feb 2013 17:23:59 -0000

Hello, all --

This version of the srtp-encrypted-header-ext draft addresses issues brought up in IESG review: https://datatracker.ietf.org/doc/draft-ietf-avtcore-srtp-encrypted-header-ext/ballot/ .

There are no protocol changes.  The only significant normative change is to make it clear that offering both encrypted and unencrypted forms of the same header extension is only for backward compatibility: you MUST NOT ever negotiate to use, or actually send, both encrypted and unencrypted forms of the same header extension.

See the diff for the full list of changes.

On Feb 8, 2013, at 12:15 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-05.txt
> 	Pages           : 17
> 	Date            : 2013-02-08
> 
> 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 future 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-05
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-srtp-encrypted-header-ext-05
> 
> 
> 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