[rohc] RE: Default decompression algorithms

"Price, Richard" <richard.price@roke.co.uk> Thu, 21 February 2002 17:47 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 MAA26214 for <rohc-archive@odin.ietf.org>; Thu, 21 Feb 2002 12:47:53 -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 MAA14311; Thu, 21 Feb 2002 12:44:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA14280 for <rohc@optimus.ietf.org>; Thu, 21 Feb 2002 12:44:31 -0500 (EST)
Received: from rsys000a.roke.co.uk (rsys000a.roke.co.uk [193.118.201.102]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA26104 for <rohc@ietf.org>; Thu, 21 Feb 2002 12:44:28 -0500 (EST)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19) id <1S9WNNRA>; Thu, 21 Feb 2002 17:43:19 -0000
Message-ID: <76C92FBBFB58D411AE760090271ED4186F9FD3@rsys002a.roke.co.uk>
From: "Price, Richard" <richard.price@roke.co.uk>
To: "'Lars-Erik Jonsson (EPL)'" <Lars-Erik.Jonsson@epl.ericsson.se>
Cc: rohc@ietf.org
Date: Thu, 21 Feb 2002 17:43:18 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed; boundary="------------InterScan_NT_MIME_Boundary"
Subject: [rohc] RE: Default decompression algorithms
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

> > So for the wireless environment 3GPP will be
> > able to choose their own list of mandatory and optional algorithms.
> 
> Yes, they use to do it that way, but why should WE make any algorithm
> mandatory at the decompressor.

We shouldn't - in my opinion it would be a mistake for the ROHC Working
Group to do more than standardise the algorithms themselves. The final
decision on whether algorithms are mandatory or optional should be made
in the context of a particular application.

The ability to make certain algorithms mandatory is available "for free"
as part of the secure state reference mechanism, so no additional
standardisation is required on our part.

> As you say yourself, the decompressor can announce what resources it has,
> and the compressor decides what to use based on that, but the decompressor
> does not have to announce any available algorithms. If it does not, the
> compressor just do not have any other choice than to download its own
> algorithm.

We should leave the decision as to whether or not mandatory algorithms are
required to particular applications (e.g. 3GPP can decide this for SIP in
the mobile environment).

> > I would be very happy to include both approaches in the SigComp
> > solution and leave the decision on which to use to the compressor.
> 
> Simple and well defined solutions with few options are usually
> preferable when making standards, at least in the IETF. 

With the UDVM approach the SigComp solution can certainly be simple and
well-defined, but few options is one thing that we won't have! A compressor
with the ability to download bytecode already has complete flexibility to
choose any algorithm it likes; in my opinion this is a strength of SigComp
rather than a weakness.

The ability to announce a list of supported algorithms at the decompressor
does not introduce more flexibility but instead just saves downloading the
chosen algorithm when it is already available at the decompressor.

Regards,

Richard