RE: [rohc] Default decompression algorithms

"Abbie Barbir"<abbieb@nortelnetworks.com> Thu, 21 February 2002 18:35 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28495 for <rohc-archive@odin.ietf.org>; Thu, 21 Feb 2002 13:35:15 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA18232; Thu, 21 Feb 2002 13:32:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA18193 for <rohc@optimus.ietf.org>; Thu, 21 Feb 2002 13:31:58 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28366 for <rohc@ietf.org>; Thu, 21 Feb 2002 13:31:55 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57]) by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g1LIVOM18975; Thu, 21 Feb 2002 13:31:24 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7]) by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g1LIVM325419; Thu, 21 Feb 2002 13:31:23 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) id <FAMDS23Q>; Thu, 21 Feb 2002 13:31:24 -0500
Message-ID: <87609AFB433BD5118D5E0002A52CD754015D5C0C@zcard0k6.ca.nortel.com>
From: "Abbie Barbir"<abbieb@nortelnetworks.com>
To: "Price, Richard" <richard.price@roke.co.uk>, "'Lars-Erik Jonsson (EPL)'" <Lars-Erik.Jonsson@epl.ericsson.se>, "Conroy, Lawrence (SMTP)" <lwc@roke.co.uk>
Cc: rohc@ietf.org
Subject: RE: [rohc] Default decompression algorithms
Date: Thu, 21 Feb 2002 13:31:22 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1BB05.F61534A0"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

Richard,

Thanks for the responce.
I am aware of what the compressor need to do. However, your remark states

"the compressor downloads a new algorithm to the decompressor when it 
judges the overall performance to be better than using one of the existing 
algorithms"

>From an implementation point of view, 
1. are you saying that the compressor must/should keep a list that relates
 a device's algorithm with the compression ratio etc that it could achieve?
2. Or the compressor will first attempt to compress using the algorithm that
is avilable at the decompressor and then it realize that i can get better
compression if this xyz algorithm is used, so what will do 
  - try to remember that for the next message
  - decide to go ahead with this message and then download a new algorithm 
    to the UDVM

Definitly other options could be used. The point here, is that the above
statement
can be hard to implement in the field.

abbie


> -----Original Message-----
> From: Price, Richard [mailto:richard.price@roke.co.uk]
> Sent: Thursday, February 21, 2002 12:57 PM
> To: Barbir, Abbie [CAR:1A00:EXCH]; 'Lars-Erik Jonsson (EPL)'; Conroy,
> Lawrence (SMTP)
> Cc: rohc@ietf.org
> Subject: RE: [rohc] Default decompression algorithms
> 
> 
> ------------------- SNIP SNIP 
> > Making one or more of these well-known algorithms mandatory at the 
> > decompressor doesn't contradict the UDVM approach because 
> the decision on 
> > which algorithm to use (or whether to download a new one) 
> is still made by 
> > the compressor. So we have a "win-win" situation; the 
> compressor downloads 
> > a new algorithm to the decompressor when it judges the 
> overall performance 
> > to be better than using one of the existing algorithms. 
> > 
> -------------- 
> > Can you suggest how this would be done (implemented) from 
> the compressor end. 
> > abbie
> 
> Hi,
> 
> There are quite a few issues that the compressor will need to 
> consider when
> judging overall performance, including some or all of the 
> following metrics:
> 
> 1   Compression ratio
> 
> 2   Processing efficiency
> 
> 3   Memory efficiency
> 
> 4   Implementation effort
> 
> 5   IPR considerations
> 
> The IPR considerations are particularly important, since 
> encumbered algorithms
> tend to substantially outperform unencumbered algorithms in 
> terms of metrics
> 1, 2, and 3.
> 
> So if a compressor has licensed the bytecode for an 
> encumbered algorithm, it
> is usually preferable to download this bytecode to a 
> decompressor that does
> not support the encumbered algorithm, rather than picking one 
> of the weaker
> unencumbered algorithms already available at the decompressor.
> 
> Regards,
> 
> Richard Price
>