Re: [AVTCORE] Fwd: [Technical Errata Reported] RFC5764 (4788)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 20 September 2016 22:00 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 CF9A012B14D; Tue, 20 Sep 2016 15:00:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.617
X-Spam-Level:
X-Spam-Status: No, score=-6.617 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id efucjNtv9HqW; Tue, 20 Sep 2016 15:00:45 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03E8612B308; Tue, 20 Sep 2016 15:00:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id B8CB1BE74; Tue, 20 Sep 2016 23:00:43 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wzV5GjRGgX3X; Tue, 20 Sep 2016 23:00:35 +0100 (IST)
Received: from [192.168.60.59] (unknown [62.237.32.34]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 3DAA8BE5B; Tue, 20 Sep 2016 23:00:34 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1474408835; bh=9I2Yr5Hdo9Pg3trfJo28Vs/KrArkP/cIgPlEtE/h88g=; h=Subject:To:References:From:Date:In-Reply-To:From; b=wBVYtMJqkMIpeyqJpjgtHAz9wKcjQqvqzLGIhQ1H4rFLZAaIvEPqOncJ6/BaYCNib 5LiiIaj8eoTVGnDfavq17wTiObTdTO/U8xVZww+jXY/u/0Oq8CnPhiVaLAGpyGDDNb tymzMk2CEtz+Og++ekq0iDMnX8anV20Wn9lJwD+s=
To: Ben Campbell <ben@nostrum.com>, IETF AVTCore WG <avt@ietf.org>, sec-ads@ietf.org
References: <20160830132557.B863DB80D13@rfc-editor.org> <E55D9EC6-B3AA-4C64-BA87-26108446788C@nostrum.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <d6f300f8-32fe-f521-d9c5-3443ed4d10ce@cs.tcd.ie>
Date: Tue, 20 Sep 2016 23:00:33 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <E55D9EC6-B3AA-4C64-BA87-26108446788C@nostrum.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms060509000108010809050504"
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/3Hm3OEZU2emO3kTTUUydVY7UtCo>
Subject: Re: [AVTCORE] Fwd: [Technical Errata Reported] RFC5764 (4788)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 20 Sep 2016 22:00:48 -0000


On 20/09/16 22:57, Ben Campbell wrote:
> Hi avtcore and security ADs:
> 
> Does anyone object to this erratum? It seems pretty straightforward (if
> borderline on the "does this represent the original intent" spectrum.)

No objection from me if it makes interop better. I've
no idea whether or not that's the case, so happy with
to go with whatever the WG list conclude.

S

> 
> Thanks!
> 
> Ben.
> 
> Forwarded message:
> 
>> From: RFC Errata System <rfc-editor@rfc-editor.org>
>> To: mcgrew@cisco.com, ekr@rtfm.com, ben@nostrum.com,
>> alissa@cooperw.in, aamelnikov@fastmail.fm,
>> keith.drage@alcatel-lucent.com, roni.even@mail01.huawei.com
>> Cc: ekr@rtfm.com, avt@ietf.org, rfc-editor@rfc-editor.org
>> Subject: [Technical Errata Reported] RFC5764 (4788)
>> Date: Tue, 30 Aug 2016 06:25:57 -0700 (PDT)
>>
>> The following errata report has been submitted for RFC5764,
>> "Datagram Transport Layer Security (DTLS) Extension to Establish Keys
>> for the Secure Real-time Transport Protocol (SRTP)".
>>
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=5764&eid=4788
>>
>> --------------------------------------
>> Type: Technical
>> Reported by: Eric Rescorla <ekr@rtfm.com>
>>
>> Section: 5.3
>>
>> Original Text
>> -------------
>> Section 4.2 says:
>>    which are assigned as shown below.  The per-association context value
>>    is empty.
>>
>> Corrected Text
>> --------------
>>    which are assigned as shown below.  No per-association context value
>>    is used.
>>
>> Notes
>> -----
>> This code is somewhat ambiguous, though the better interpretation is
>> probably that you should use a zero-length context (arm 2 of
>> https://tools.ietf.org/html/rfc5705#section-4). However, real
>> implementations do not seem to use the exporter value, so we need to
>> resolve this in that direction.
>>
>> Instructions:
>> -------------
>> This erratum is currently posted as "Reported". If necessary, please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party (IESG)
>> can log in to change the status and edit the report, if necessary.
>>
>> --------------------------------------
>> RFC5764 (draft-ietf-avt-dtls-srtp-07)
>> --------------------------------------
>> Title               : Datagram Transport Layer Security (DTLS)
>> Extension to Establish Keys for the Secure Real-time Transport
>> Protocol (SRTP)
>> Publication Date    : May 2010
>> Author(s)           : D. McGrew, E. Rescorla
>> Category            : PROPOSED STANDARD
>> Source              : Audio/Video Transport
>> Area                : Real-time Applications and Infrastructure
>> Stream              : IETF
>> Verifying Party     : IESG
>>