RE: [rohc] RE: Default decompression algorithms

"Dr. Carsten Bormann" <cabo@tzi.org> Fri, 22 February 2002 08: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 DAA24414 for <rohc-archive@odin.ietf.org>; Fri, 22 Feb 2002 03:31:48 -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 DAA04192; Fri, 22 Feb 2002 03:24:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA04160 for <rohc@ns.ietf.org>; Fri, 22 Feb 2002 03:24:20 -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 DAA24265 for <rohc@ietf.org>; Fri, 22 Feb 2002 03:24:17 -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 g1M8O4C10925; Fri, 22 Feb 2002 09:24:05 +0100 (MET)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: "Lars-Erik Jonsson \(EPL\)" <Lars-Erik.Jonsson@epl.ericsson.se>, "'Price, Richard'" <richard.price@roke.co.uk>
Cc: <rohc@ietf.org>
Subject: RE: [rohc] RE: Default decompression algorithms
Date: Fri, 22 Feb 2002 09:24:04 +0100
Message-ID: <NFBBJFHGMCFINEMHAMBGOEHFHHAA.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)
In-Reply-To: <A943FD84BD9ED41193460008C791805003E31E1A@ESEALNT419.al.sw.ericsson.se>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
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

One question about the compression algorithm negotiation:
Given that there are algorithms that take on the order of 50 bytes to send
over, why is it a win to spend maybe 100 bytes of overhead and a round trip
to negotiate that away?

Gruesse, Carsten


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