[AVT] VMR-WB RTP Payload and Storage Formats

sassan.ahmadi@nokia.com Mon, 04 October 2004 18:17 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00282 for <avt-archive@ietf.org>; Mon, 4 Oct 2004 14:17:44 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEXYG-0004hT-Ep for avt-archive@ietf.org; Mon, 04 Oct 2004 14:27:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEXNP-0000dm-3i; Mon, 04 Oct 2004 14:15:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEXGw-0007fZ-PO for avt@megatron.ietf.org; Mon, 04 Oct 2004 14:09:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29446 for <avt@ietf.org>; Mon, 4 Oct 2004 14:09:17 -0400 (EDT)
From: sassan.ahmadi@nokia.com
Received: from mgw-x3.nokia.com ([131.228.20.26]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEXQ3-000317-Op for avt@ietf.org; Mon, 04 Oct 2004 14:18:45 -0400
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120]) by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i94I97a13446; Mon, 4 Oct 2004 21:09:07 +0300 (EET DST)
X-Scanned: Mon, 4 Oct 2004 21:08:58 +0300 Nokia Message Protector V1.3.31 2004060815 - RELEASE
Received: (from root@localhost) by esdks001.ntc.nokia.com (8.12.9/8.12.9) id i94I8wsh026430; Mon, 4 Oct 2004 21:08:58 +0300
Received: from mgw-int2.ntc.nokia.com (172.21.143.97) by esdks001.ntc.nokia.com 00aS8JKm; Mon, 04 Oct 2004 21:08:56 EEST
Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com [10.241.35.122]) by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i94I8lS16787; Mon, 4 Oct 2004 21:08:47 +0300 (EET DST)
Received: from sdebe002.NOE.Nokia.com ([172.19.201.138]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Mon, 4 Oct 2004 13:08:44 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 04 Oct 2004 11:08:38 -0700
Message-ID: <0B08EA1BF5F6304992CDC985EE02209E02A7437B@sdebe002.americas.nokia.com>
Thread-Topic: [AVT] RE: <draft-ietf-avt-rtp-vmr-wb-03.txt>: sampling rate
Thread-Index: AcSpyYv3zQG44iCcSni7uLr/xYEriQAbbA2g
X-Priority: 1
Priority: Urgent
Importance: high
To: csp@csperkins.org
X-OriginalArrivalTime: 04 Oct 2004 18:08:44.0092 (UTC) FILETIME=[2F9027C0:01C4AA3D]
X-Spam-Score: 1.6 (+)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: quoted-printable
Cc: magnus.westerlund@ericsson.com, avt@ietf.org
Subject: [AVT] VMR-WB RTP Payload and Storage Formats
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: quoted-printable

Dear Colin,

I am getting frustrated with the situation regarding the VMR-WB I-D.

When this I-D was about to be accepted for the WGLC, a comment on the relationship between the sampling rate and RTP clock rate has put this I-D in an ambiguous status.

In the one hand, based on the distinctive capability of VMR-WB, there are people who want to use a fixed RTP clock rate of 16000 Hz to enable processing/injection of the 8000 Hz sampled media. Note that 8000 and 16000 Hz sampled media have identical VMR-WB output frames. I believe there is technically nothing wrong and revision -04 of the I-D appropriately addresses this concern.

On the other hand, you persist on your opinion that RTP clock rate must be identical to the input media sampling rate regardless of the codec capabilities.

The following excerpt from Section 4.1 of RFC 3551 (line 434)

"...
   The RTP clock rate used for generating the RTP timestamp is
   independent of the number of channels and the encoding; it usually
   equals the number of sampling periods per second.  For N-channel
   encodings, each sampling period (say, 1/8,000 of a second) generates
   N samples.  (This terminology is standard, but somewhat confusing, as
   the total number of samples generated per second is then the sampling
   rate times the channel count.)
..."

indicates that (there is no normative language here) the RTP clock rate "usually" equals the input media sampling rate and that it is independent of the encoding.

Also the following excerpt from Section 6.4.4 of RFC 3550 (line 2391)

"...
   Since that timestamp is
   independent of the clock rate for the data encoding, it is possible
   to implement encoding- and profile-independent quality monitors.
..."

Therefore, you have no technical ground to assert that RTP clock rate MUST be equal to input media sampling frequency.

Please think of VMR-WB as a dual-rate system where both 8000 and 16000 Hz sampled media are supported and that decoding can proceed without knowing the input media sampling frequency.

Please remember that initially I resisted this idea; however, after considering all aspects of the requested change, I came to realize that it is technically sound.

I do want a resolution for this matter. This is definitely jeopardizing and delaying the deployment of VMR-WB codec and its prospective applications. Please do not expect that the other parties to back off from their position. We must resolve this issue.

Your understanding and consideration are appreciated in advance.

Regards

-Sassan Ahmadi



_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt