IETF Logo Mail Archive

RE: [rohc] RE: Default decompression algorithms

"Dr. Carsten Bormann" <cabo@tzi.org> Tue, 26 February 2002 16:31 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 LAA06478 for <rohc-archive@odin.ietf.org>; Tue, 26 Feb 2002 11:31:09 -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 LAA21575; Tue, 26 Feb 2002 11:28:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21538 for <rohc@optimus.ietf.org>; Tue, 26 Feb 2002 11:28:36 -0500 (EST)
Received: from nmh.informatik.uni-bremen.de (root@nmh.informatik.uni-bremen.de [134.102.224.3]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06368 for <rohc@ietf.org>; Tue, 26 Feb 2002 11:28:32 -0500 (EST)
Received: from cabo3 (root@nmh.informatik.uni-bremen.de [134.102.224.3]) by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with SMTP id g1QGSOC21659; Tue, 26 Feb 2002 17:28:24 +0100 (MET)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>, <zhigang.c.liu@nokia.com>
Cc: <rohc@ietf.org>
Subject: RE: [rohc] RE: Default decompression algorithms
Date: Tue, 26 Feb 2002 17:28:21 +0100
Message-ID: <NFBBJFHGMCFINEMHAMBGAEIGHHAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-reply-to: <3C7BB47C.F03E93FD@ericsson.com>
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

> I also agree with the requirement whereby a decompressor informs
> the compressor of the algorythms that are already uploaded, and
> therefore, don't need to be uploaded again. This is just to
> save bandwidth over the air interface and avoid unneeded uploads.
> I think this is a very valid requirement.

How many algorithms are there going to be in the cache of a typical
decompressor?
What is the cost of supplying this information?
Explain how this computes.

Gruesse, Carsten


_______________________________________________
Rohc mailing list
Rohc@ietf.org
https://www1.ietf.org/mailman/listinfo/rohc

v2.8.7 | Report a Bug | By Email