Re: [AVTCORE] header extensions and draft-ietf-avtcore-srtp-aes-gcm-04.txt

Jonathan Lennox <jonathan@vidyo.com> Fri, 19 April 2013 15:59 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 0F25221F86D8 for <avt@ietfa.amsl.com>; Fri, 19 Apr 2013 08:59:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gK4x1bs2u+Wo for <avt@ietfa.amsl.com>; Fri, 19 Apr 2013 08:59:14 -0700 (PDT)
Received: from mxout.myoutlookonline.com (mxout.myoutlookonline.com [64.95.72.252]) by ietfa.amsl.com (Postfix) with ESMTP id 088CF21F962D for <avt@ietf.org>; Fri, 19 Apr 2013 08:59:12 -0700 (PDT)
Received: from mxout.myoutlookonline.com (localhost [127.0.0.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id C2070416939 for <avt@ietf.org>; Fri, 19 Apr 2013 11:59:01 -0400 (EDT)
X-Virus-Scanned: by SpamTitan at mail.lan
Received: from HUB022.mail.lan (unknown [10.110.2.1]) by mxout.myoutlookonline.com (Postfix) with ESMTP id 9193C416B66 for <avt@ietf.org>; Fri, 19 Apr 2013 11:59:00 -0400 (EDT)
Received: from BE235.mail.lan ([10.110.32.235]) by HUB022.mail.lan ([10.110.17.22]) with mapi; Fri, 19 Apr 2013 11:57:53 -0400
From: Jonathan Lennox <jonathan@vidyo.com>
To: IETF AVTCore WG <avt@ietf.org>
Date: Fri, 19 Apr 2013 11:58:59 -0400
Thread-Topic: header extensions and draft-ietf-avtcore-srtp-aes-gcm-04.txt
Thread-Index: Ac49FsMyIepl6QzoSuCQQ+PEUtZgtg==
Message-ID: <1F2A6816-DDB9-4964-AD82-5F9EC2A2957D@vidyo.com>
References: <20130204181454.8284.73608.idtracker@ietfa.amsl.com> <461FB470-9F33-4B72-BDCC-402E44208789@vidyo.com> <3C4AAD4B5304AB44A6BA85173B4675CA69669890@MSMR-GH1-UEA03.corp.nsa.gov> <F46785E4-8447-44CB-B169-E64F25665274@vidyo.com> <3C4AAD4B5304AB44A6BA85173B4675CA6AA9DCC8@MSMR-GH1-UEA03.corp.nsa.gov>
In-Reply-To: <3C4AAD4B5304AB44A6BA85173B4675CA6AA9DCC8@MSMR-GH1-UEA03.corp.nsa.gov>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [AVTCORE] header extensions and draft-ietf-avtcore-srtp-aes-gcm-04.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, 19 Apr 2013 15:59:16 -0000

To note, the changes in srtp-aes-gcm-05 describing the use of header extension encryption look good to me.

The RFC for header extension encryption has now been published, as RFC 6904.  The next rev of srtp-aes-gcm (whenever that is) should update that in its references.

--
Jonathan Lennox
jonathan@vidyo.com