[AVTCORE] [Technical Errata Reported] RFC4733 (3451)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 11 January 2013 13:35 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 2CBD821F8942 for <avt@ietfa.amsl.com>; Fri, 11 Jan 2013 05:35:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.451
X-Spam-Level:
X-Spam-Status: No, score=-102.451 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 8lHGidiXGh0Y for <avt@ietfa.amsl.com>; Fri, 11 Jan 2013 05:35:21 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id A71B921F892A for <avt@ietf.org>; Fri, 11 Jan 2013 05:35:21 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id A8C86B1E002; Fri, 11 Jan 2013 05:24:51 -0800 (PST)
To: schulzrinne@cs.columbia.edu, taylor@nortel.com, gonzalo.camarillo@ericsson.com, rjsparks@nostrum.com, keith.drage@alcatel-lucent.com, even.roni@huawei.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20130111132451.A8C86B1E002@rfc-editor.org>
Date: Fri, 11 Jan 2013 05:24:51 -0800
Cc: xavier.marjou@orange.com, avt@ietf.org, rfc-editor@rfc-editor.org
Subject: [AVTCORE] [Technical Errata Reported] RFC4733 (3451)
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, 11 Jan 2013 13:35:22 -0000

The following errata report has been submitted for RFC4733,
"RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=4733&eid=3451

--------------------------------------
Type: Technical
Reported by: Xavier Marjou <xavier.marjou@orange.com>

Section: 2.1

Original Text
-------------
Named telephone events are carried as part of the audio stream and
MUST use the same sequence number and timestamp base as the regular
audio channel to simplify the generation of audio waveforms at a 
gateway.

Corrected Text
--------------
Named telephone events are carried as part of the audio stream and
MUST use the same SSRC (therefore the same timing and sequence
number space) and the same timestamp clock rate as the regular
audio channel to simplify the generation of audio waveforms at a
gateway.

Notes
-----
RFC4733 was written in a way to avoid the multiple clock-rate problem by mandating the use of the same SSRC for DTMF and audio. However it's not explicitly written, which brings an ambiguity. It was commented that RFC4733 needs to be updated. (c.f. http://tools.ietf.org/wg/avtext/minutes?item=minutes-85-avtext.html)

Instructions:
-------------
This errata 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. 

--------------------------------------
RFC4733 (draft-ietf-avt-rfc2833bis-15)
--------------------------------------
Title               : RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals
Publication Date    : December 2006
Author(s)           : H. Schulzrinne, T. Taylor
Category            : PROPOSED STANDARD
Source              : Audio/Video Transport
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG