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

Xavier Marjou <xavier.marjou@orange.com> Fri, 25 January 2013 14:46 UTC

Return-Path: <xavier.marjou@gmail.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 267FD21F8682 for <avt@ietfa.amsl.com>; Fri, 25 Jan 2013 06:46:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 B-KumsThD095 for <avt@ietfa.amsl.com>; Fri, 25 Jan 2013 06:46:24 -0800 (PST)
Received: from mail-qc0-f181.google.com (mail-qc0-f181.google.com [209.85.216.181]) by ietfa.amsl.com (Postfix) with ESMTP id 61AA621F86FA for <avt@ietf.org>; Fri, 25 Jan 2013 06:46:24 -0800 (PST)
Received: by mail-qc0-f181.google.com with SMTP id x40so209713qcp.26 for <avt@ietf.org>; Fri, 25 Jan 2013 06:46:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=8qAT14lk5mMSByJp6BBusUfepmcggUjFA23Xygqsz1Q=; b=zriXFbaOZ459I6STGN4rbxMgdiVVNshG9l1QRuEIgmEDrEeWMRV6wkLRb9ejPsnrUN iARTvbsQg98zLefwzLQ/EJURkE6nrc948LTffQaTvppPsuLFUNWFuHU8DIUTMkGjxZNS 8bfvV0xk4eeEfngiyFvTLgfKw+Zav+luN+WNH93oMBXkjw+3OJT9tznWaIwxF4bMfxuS XgqpqTThm23tSVijhHYhswr5PJbyC1Lgi0cyXyri6VvWq5VSZxYuznt8idpCO94UkFWe LpFlF+ZcYt+iEm15VWBMjLOPoIjag6qeRbOx/dSyxSU0dZ7m7ygDk+dsbicytxjVW7Ho rWfw==
MIME-Version: 1.0
X-Received: by 10.224.223.80 with SMTP id ij16mr6002528qab.8.1359125183844; Fri, 25 Jan 2013 06:46:23 -0800 (PST)
Sender: xavier.marjou@gmail.com
Received: by 10.49.63.227 with HTTP; Fri, 25 Jan 2013 06:46:23 -0800 (PST)
In-Reply-To: <CAErhfrzd_rcVi48ezncx8FWt0t18cYtJmW4wiHqqyUOVWkR47A@mail.gmail.com>
References: <CAErhfrzd_rcVi48ezncx8FWt0t18cYtJmW4wiHqqyUOVWkR47A@mail.gmail.com>
Date: Fri, 25 Jan 2013 15:46:23 +0100
X-Google-Sender-Auth: zAU4U9TZTwpHbE5o_Lq8zO91a84
Message-ID: <CAErhfrzfrG=dewc-z-y33Dh5=_RhX6UpAx+FGKjFR28G3+g1NQ@mail.gmail.com>
From: Xavier Marjou <xavier.marjou@orange.com>
To: avt@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
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: Fri, 25 Jan 2013 14:46:28 -0000

Hi,

I also agree that this text proposal is better.

I would even suggest to remove the end of the sentence (i.e. "to
simplify the generation of audio waveforms at a gateway") in order to
make it easier to understand (as we would add " if they use the same
SSRC ..." before).

In other words, I would suggest :
 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.

Cheers,
Xavier

> On 2013-01-16 17:45, Marc Petit-Huguenin wrote:
>> 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.
>>
>
> I think this is much better.
>
> Cheers
>
> Magnus Westerlund