Re: [MMUSIC] Telephone-event and multiple clock rates

Adam Roach <adam@nostrum.com> Fri, 24 January 2014 15:59 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14FDB1A001E for <mmusic@ietfa.amsl.com>; Fri, 24 Jan 2014 07:59:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level:
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=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 d03gGJqKnE39 for <mmusic@ietfa.amsl.com>; Fri, 24 Jan 2014 07:59:49 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id AC97E1A0010 for <mmusic@ietf.org>; Fri, 24 Jan 2014 07:59:49 -0800 (PST)
Received: from orochi-2.roach.at (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0OFxjHO074121 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 24 Jan 2014 09:59:45 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <52E28DEB.1040100@nostrum.com>
Date: Fri, 24 Jan 2014 09:59:39 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, "Stach, Thomas" <thomas.stach@unify.com>
References: <52E178F6.70009@nostrum.com> <F81CEE99482EFE438DAE2A652361EE1217A2E16D@MCHP04MSX.global-ad.net> <52E24090.1030608@ericsson.com>
In-Reply-To: <52E24090.1030608@ericsson.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 99.152.145.110 is authenticated by a trusted mechanism)
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Telephone-event and multiple clock rates
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 15:59:51 -0000

On 1/24/14 04:29, Magnus Westerlund wrote:
> My understanding for the reasoning behind this definition in the RFC is
> due to that the events is supposed to be connected to the same time-line
> as the audio. Thus it ended up using the same SSRC. To avoid timestamp
> rate switching which we know has issues
> (https://datatracker.ietf.org/doc/draft-ietf-avtext-multiple-clock-rates/)
> it was mandated to provide one PT for each rate negotiated for the audio
> payload types.

To make sure I understand what you're saying correctly: you are 
asserting that having four different clock rates for voice codecs 
requires us to use four different PTs for telephone-event if we're going 
to have them on the same SSRC. Is that correct?

/a