[AVTCORE] [Editorial Errata Reported] RFC5764 (4873)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 30 November 2016 15:27 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 9AE241294F1 for <avt@ietfa.amsl.com>; Wed, 30 Nov 2016 07:27:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.699
X-Spam-Level:
X-Spam-Status: No, score=-105.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
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 unE6nb8F4QKj for <avt@ietfa.amsl.com>; Wed, 30 Nov 2016 07:27:26 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB4701295B7 for <avt@ietf.org>; Wed, 30 Nov 2016 07:25:39 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id CE9B6B80902; Wed, 30 Nov 2016 07:25:39 -0800 (PST)
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
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20161130152539.CE9B6B80902@rfc-editor.org>
Date: Wed, 30 Nov 2016 07:25:39 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/Sc1fRHdSh9PDAm4PeMxl2lfwrz0>
X-Mailman-Approved-At: Thu, 01 Dec 2016 02:05:16 -0800
Cc: rfc-editor@rfc-editor.org, peter@lekensteyn.nl, avt@ietf.org
Subject: [AVTCORE] [Editorial Errata Reported] RFC5764 (4873)
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: Wed, 30 Nov 2016 15:27:28 -0000

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=4873

--------------------------------------
Type: Editorial
Reported by: Peter Wu <peter@lekensteyn.nl>

Section: 5.1.1

Original Text
-------------
When the mechanism described in this document is in
effect, this is modified so that data written by upper-level protocol
clients of DTLS is assumed to be RTP/RTP and is encrypted using SRTP
rather than the standard TLS record encoding.

Corrected Text
--------------
When the mechanism described in this document is in
effect, this is modified so that data written by upper-level protocol
clients of DTLS is assumed to be RTP/RTCP and is encrypted using SRTP
rather than the standard TLS record encoding.

Notes
-----
Section 5.1 notes that RTP or RTCP can be sent over the channel, so "RTP/RTP" should be "RTP/RTCP".

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  
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