Re: [rohc] Feedback formats

Carl Knutsson <carl.knutsson@effnet.com> Thu, 16 July 2009 13:10 UTC

Return-Path: <carl.knutsson@effnet.com>
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7622628C110 for <rohc@core3.amsl.com>; Thu, 16 Jul 2009 06:10:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.171
X-Spam-Level:
X-Spam-Status: No, score=-3.171 tagged_above=-999 required=5 tests=[AWL=-0.428, BAYES_00=-2.599, CN_BODY_46=0.256, J_CHICKENPOX_22=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MSrZVIDLA9dY for <rohc@core3.amsl.com>; Thu, 16 Jul 2009 06:10:26 -0700 (PDT)
Received: from lists.levonline.com (lists.levonline.com [217.70.33.37]) by core3.amsl.com (Postfix) with ESMTP id E15DE3A6D08 for <rohc@ietf.org>; Thu, 16 Jul 2009 06:10:25 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by lists.levonline.com (Postfix) with ESMTP id F10EF29C4AD; Thu, 16 Jul 2009 15:09:15 +0200 (CEST)
X-Virus-Scanned: By http://levonline.com - free virus scanning for all customers
Received: from lists.levonline.com ([127.0.0.1]) by localhost (lists.levonline.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vo4K3MVKUbnW; Thu, 16 Jul 2009 15:09:13 +0200 (CEST)
Received: from truck3.fordonnet.levonline.com (gw-uu-virtual.levonline.com [217.70.32.2]) by lists.levonline.com (Postfix) with ESMTP id 1D60F29C03C; Thu, 16 Jul 2009 15:09:13 +0200 (CEST)
Received: from [192.168.101.28] (c-6a0471d5.04-205-6c756c1.cust.bredbandsbolaget.se [213.113.4.106]) (authenticated bits=0) by truck3.fordonnet.levonline.com (8.12.11.20060308/8.12.11) with ESMTP id n6GD9Bvj020912 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Jul 2009 15:09:12 +0200
Message-ID: <4A5F26AD.2020706@effnet.com>
Date: Thu, 16 Jul 2009 15:10:05 +0200
From: Carl Knutsson <carl.knutsson@effnet.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090608)
MIME-Version: 1.0
To: Klaus Warnke <klaus.warnke@acticom.de>
References: <OFFE3A0258.C241EF00-ON482575F4.0009FFD2-482575F5.00315EB2@zte.com.cn> <4A5EFAD3.900@acticom.de>
In-Reply-To: <4A5EFAD3.900@acticom.de>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Cc: rohc@ietf.org, cai.wei2@zte.com.cn
Subject: Re: [rohc] Feedback formats
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jul 2009 13:10:27 -0000

Klaus, Cai,

Using the "short cut" as Klaus describes below is not really allowed in
RFC3095. Section 5.6.1 is quite clear that all feedback during a mode
transition must carry a CRC option. The mode parameter must also be set
to O to transfer from U-mode to O-mode. FEEDBACK-1 doesn't have a mode
field and cannot carry feedback options.

Klaus, I guess you refer to the last paragraph of section 5.6.2. It
should not be interpreted by its own. I agree that the wording is a bit
unfortunate, but I can still not see how it can be interpret it this
way. FEEDBACK-1 cannot be used for mode transfer between U-mode and
O-mode. The compressor simply don't have the information to which mode
to transfer to.


Cheers,

/Calle


Klaus Warnke wrote:
> Hello cai,
> 
> I'm not completely sure what your mean.
> 
> First, there is a "short cut" to switch from U to O
> mode (5.6.2.). In this case, a feedback-1 is sufficient, because
> the receiving of any feedback shows to compressor that a feedback
> channel is available and this is the precondition for bidirectional
> optimistic mode.
> 
> Ideally the mode transition should be profile independent. But for the
> IR/IR-DYN packet it isn't due to a design flaw. Only the dynamic chain
> of the RTP Header contains the 'M' (5.7.7.6.) flag to transmit a
> compression mode. For the other profiles you must use a extension-3.
> 
> Hope that helps.
> 
> If not, could you please explain the problem more detailed?
> 
> br
> Klaus Warnke
> 
> 
> cai.wei2@zte.com.cn wrote:
>> RFC 3095 describes that when mode transitions, any feedback should be
>> sent with mode transition parameter;
>>
>> at the same time, the feedback logic of decompressor in U/O/R mode
>> also send feedback with mode parameter.
>>
>> there is a doubt that which case we could use feedback-1 in profile RTP?
>>
>> Thanks
>> 	
>> *caiwei 167981*
>> LTE Development Department | LTE¿ª·¢²¿
>> 	*Product Marketing System *
>> *²úÆ·Êг¡Ìåϵ*
>> D3-06, ZTE Corp., No.10 South Tangyan Rd.,
>> Hi-tech Industrial Development Zone, Xi'an,
>> P.R.China, 710065
>> Tel:+86-29-88724112, 15801916689
>> Email:167981@zte.com.cn
>>
>>
>>
>>
>> --------------------------------------------------------
>> ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
>> This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
>> This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
>>   
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Rohc mailing list
>> Rohc@ietf.org
>> https://www.ietf.org/mailman/listinfo/rohc
>>   
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www.ietf.org/mailman/listinfo/rohc