Re: [AVT] RFC3558 header-free packet format question

Qiaobing Xie <Qiaobing.Xie@motorola.com> Fri, 17 September 2004 10:42 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 GAA24017 for <avt-archive@ietf.org>; Fri, 17 Sep 2004 06:42:33 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C8GHg-00064M-M5 for avt-archive@ietf.org; Fri, 17 Sep 2004 06:48:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C8GAG-0005T4-N2; Fri, 17 Sep 2004 06:40:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C8G7x-0004wQ-3Z for avt@megatron.ietf.org; Fri, 17 Sep 2004 06:38:05 -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 GAA23774 for <avt@ietf.org>; Fri, 17 Sep 2004 06:38:02 -0400 (EDT)
Received: from ftpbox.mot.com ([129.188.136.101]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C8GDF-0005yJ-4p for avt@ietf.org; Fri, 17 Sep 2004 06:43:47 -0400
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231]) by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id i8HAbkZ0013413; Fri, 17 Sep 2004 03:37:47 -0700 (MST)
Received: from motorola.com ([163.14.20.39]) by az33exr01.mot.com (Motorola/az33exr01) with ESMTP id i8HATh1d003428; Fri, 17 Sep 2004 05:29:44 -0500
Message-ID: <414ABEDD.3040309@motorola.com>
Date: Fri, 17 Sep 2004 18:39:25 +0800
From: Qiaobing Xie <Qiaobing.Xie@motorola.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
Subject: Re: [AVT] RFC3558 header-free packet format question
References: <A943FD84BD9ED41193460008C7918050072E973D@ESEALNT419.al.sw.ericsson.se>
In-Reply-To: <A943FD84BD9ED41193460008C7918050072E973D@ESEALNT419.al.sw.ericsson.se>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit
Cc: adamli@icsl.ucla.edu, AVT List <avt@ietf.org>
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: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: 7bit

Hi, Lars-Erik/Magnus,

Thank you both for the explanation. Yes, it makes sense now. Does the intended 
ROHC-LLA/CDMA2000 operation (as described by both of you) must require the 
one-frame-per-packet limitation on the header-free format? This is not obvious to me at least.

regards,
-Qiaobing

Lars-Erik Jonsson (LU/EAB) wrote:

> Qiaobing,
> 
> The header-free format was included to make no-overhead-over-the-air
> possible, then obviously assuming IP/UDP/RTP header compression on
> the wireless link. By using RFC 3242, the header overhead can be
> totally eliminated under certain conditions, thus one frame per RTP
> packet can make much sense.
> 
> Cheers,
> /L-E
> 
> 
> 
>>-----Original Message-----
>>From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org]On Behalf Of
>>Qiaobing Xie
>>Sent: den 17 september 2004 05:51
>>To: AVT List
>>Cc: adamli@icsl.ucla.edu
>>Subject: [AVT] RFC3558 header-free packet format question
>>
>>
>>Hi, Adam,
>>
>>The text in section 4.2 of RFC3558 **seems** to indicate that 
>>only ONE speech frame is 
>>allowed per RTP packet when header-free format is used. This 
>>seems to be overly limiting and 
>>may severely hinder the usage of this payload format (e.g., I 
>>don't think any over-the-air 
>>link can afford to use one frame per RTP packet arrangement, 
>>and if over-the-air link can 
>>not use header-free format, what would be its purpose?). One 
>>would think that as long as the 
>>same codec rate (hence the layout and size) is in use, more 
>>than one frame should be able to 
>>be unambiguously carried in a header-free RTP packet.
>>
>>Maybe I missed something.
>>
>>regards,
>>-Qiaobing
>>
>>
>>_______________________________________________
>>Audio/Video Transport Working Group
>>avt@ietf.org
>>https://www1.ietf.org/mailman/listinfo/avt
>>
> 
> 


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