Re: [AVTCORE] [Technical Errata Reported] RFC4733 (3451)
"Art Allison" <AAllison@nab.org> Wed, 16 January 2013 17:13 UTC
Return-Path: <aallison@nab.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 E421E21F86D3 for <avt@ietfa.amsl.com>; Wed, 16 Jan 2013 09:13:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 7ku--Yh9uuMM for <avt@ietfa.amsl.com>; Wed, 16 Jan 2013 09:13:40 -0800 (PST)
Received: from p01c11o148.mxlogic.net (p01c11o148.mxlogic.net [208.65.144.71]) by ietfa.amsl.com (Postfix) with ESMTP id 20A6C21F8AB0 for <avt@ietf.org>; Wed, 16 Jan 2013 09:13:39 -0800 (PST)
Received: from unknown [208.97.234.91] (EHLO NABSREX027324.NAB.ORG) by p01c11o148.mxlogic.net(mxl_mta-6.16.0-0) with ESMTP id 2cfd6f05.0.98453.00-268.251101.p01c11o148.mxlogic.net (envelope-from <aallison@nab.org>); Wed, 16 Jan 2013 10:13:39 -0700 (MST)
X-MXL-Hash: 50f6dfc32d64ee39-f5af40bd637e7248d70791c627325919d62f6d57
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 16 Jan 2013 12:13:27 -0500
Message-ID: <71C9EC0544D1F64D8B7D91EDCC6220200D087451@NABSREX027324.NAB.ORG>
In-Reply-To: <50F6D929.2090406@acm.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [AVTCORE] [Technical Errata Reported] RFC4733 (3451)
Thread-Index: Ac30CNxktEZf+l30QnafUCDZtoWumgAAyILw
References: <20130111132451.A8C86B1E002@rfc-editor.org><50F589BB.5010709@ericsson.com> <50F6D929.2090406@acm.org>
From: Art Allison <AAllison@nab.org>
To: avt@ietf.org
X-AnalysisOut: [v=2.0 cv=FrOyCRXq c=1 sm=1 a=tFGTPFZixTZ3yCXJchW01Q==:17 a]
X-AnalysisOut: [=oHOBHFV2aHAA:10 a=BvPfnLs-15kA:10 a=BLceEmwcHowA:10 a=8nJ]
X-AnalysisOut: [EP1OIZ-IA:10 a=g0FpLpFZAAAA:8 a=6CjRojJJfT0A:10 a=48vgC7mU]
X-AnalysisOut: [AAAA:8 a=BqEg4_3jAAAA:8 a=z9tbli-vAAAA:8 a=jvcXq-UlAAAA:8 ]
X-AnalysisOut: [a=jU4qhlNgAAAA:8 a=MPIb9N_B8eXkAx9-8lkA:9 a=wPNLvfGTeEIA:1]
X-AnalysisOut: [0 a=8SgyfJxrfqYA:10 a=-9UqKSle32gA:10 a=nxvUgxnZw2cA:10 a=]
X-AnalysisOut: [mhd2NDuUijAA:10 a=Qd0007q6B0YA:10 a=lZB815dzVvQA:10 a=oAXR]
X-AnalysisOut: [_kdF8uMA:10 a=scxRXJgP-wcA:10 a=VE3WPqR0TXrV6GPW:21 a=3F7W]
X-AnalysisOut: [V4hvX-Hx_Bg-:21]
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <aallison@nab.org>
X-SOURCE-IP: [208.97.234.91]
Subject: Re: [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: Wed, 16 Jan 2013 17:13:41 -0000
It seems to me that the conditional mandatory sentence is clearer if the (informative) reason is separated to prevent any misread of the 'MUST' as appling only to streams that pass through a gateway. As in RTR: " Named telephone events are carried as part of the audio stream and if they use the same SSRC (therefore the same timing and sequence number space), they MUST use the same timestamp clock rate as the regular audio channel. Note: One benefit of this requirement is simplification of the generation of audio waveforms at a gateway." Regards, Art Art Allison Senior Director Advanced Engineering, Technology National Association of Broadcasters 1771 N Street NW Washington, DC 20036 Phone 202 429 5418 Fax 202 775 4981 www.nab.org Advocacy Education Innovation -----Original Message----- From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Marc Petit-Huguenin Sent: Wednesday, January 16, 2013 11:45 AM To: Magnus Westerlund Cc: avt@ietf.org Subject: Re: [AVTCORE] [Technical Errata Reported] RFC4733 (3451) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 01/15/2013 08:54 AM, Magnus Westerlund wrote: > Hi, > > (As Individual) > > Are we certain that the RTP payload format will never be sent over two > different but linked SSRCs to the original audio. There is such a use > case (See RFC 3388) where DTMF and original audio are sent in two > different RTP sessions and thus with different SSRCs (although, they > could have the same number for binding reasons). I fear the proposed > corrected text is to restrictive. Right. I propose this: Named telephone events are carried as part of the audio stream and if they use the same SSRC (therefore the same timing and sequence number space), they MUST use the same timestamp clock rate as the regular audio channel to simplify the generation of audio waveforms at a gateway. > > Cheers > > Magnus > > On 2013-01-11 14:24, RFC Errata System wrote: >> >> 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 >> _______________________________________________ Audio/Video Transport >> Core Maintenance avt@ietf.org >> https://www.ietf.org/mailman/listinfo/avt >> > > - -- Marc Petit-Huguenin Email: marc@petit-huguenin.org Blog: http://blog.marc.petit-huguenin.org Profile: http://www.linkedin.com/in/petithug -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQ9tkkAAoJECnERZXWan7E3koP/0AqEe+Iuy8RLOmU0jls4+fv kMZdDsuI6MtHiAUhOZ+DLuKww5pt6ubskiILud6GlqQPwFf3kEAzYXeYJUmX7bJ5 r4BSqkKwQsIf1OUR6V4a0jpy3Ydy6FJNqe0CS8dQPrD4otLnT6AjFW/StZVbhBzT wdmj3gfS4YQY9FkI3eHQxXEIAsqT53iuI5m6x9+5BFMU47M5Xh4WM49RdHwZP0uO Mqo3CYjBe7I1bBo7y9V+uaddQj+nW5MeNoAbXl9hKZCtZOL2TRq8M2OQpVqnDsNx LmPtxcSud9fW07GxWlmJgQBiV2C+LVj4TSjXeIvZozwceRIg304yLpJLfe4hkulK /Qahsz1VIGXR2ddacdYTIZtPCP+uRbpFal+zoTlbscdRTlrx5xgpvY/x2saqj79m 31QJ6WrN1cRW7fJU3i6NQvM+UB0+v3PVnu4WpNaa5o+yoVU1UItKXDlFTh+hUbjQ sfKFbcsZcJERCHH4Wc58zCbj5/O2iXbwPzmnfe5seFrxxxO5U+RNu/yZO0GwWmAo qx/V2Z0VoSgVHip0LbtgJeTkIOt3V791sFZt61H1D2sbofTvhdLrAsrRvaqPuGId C3tX6YBEhrBk19rzDMQmInXHCf1wL17wc6Oojy8Lt/oCO9rLVCTvOcNPK5TDG1qc fagpbtxylCBGa1T/6UNy =FMtx -----END PGP SIGNATURE----- _______________________________________________ Audio/Video Transport Core Maintenance avt@ietf.org https://www.ietf.org/mailman/listinfo/avt
- [AVTCORE] [Technical Errata Reported] RFC4733 (34… RFC Errata System
- Re: [AVTCORE] [Technical Errata Reported] RFC4733… Tom Taylor
- Re: [AVTCORE] [Technical Errata Reported] RFC4733… Art Allison
- Re: [AVTCORE] [Technical Errata Reported] RFC4733… Magnus Westerlund
- Re: [AVTCORE] [Technical Errata Reported] RFC4733… Marc Petit-Huguenin
- Re: [AVTCORE] [Technical Errata Reported] RFC4733… Marc Petit-Huguenin
- Re: [AVTCORE] [Technical Errata Reported] RFC4733… Magnus Westerlund
- Re: [AVTCORE] [Technical Errata Reported] RFC4733… Art Allison
- Re: [AVTCORE] [Technical Errata Reported] RFC4733… Xavier Marjou