RE: [rohc] default algorithm, redux
"Surtees, Abigail" <abigail.surtees@roke.co.uk> Mon, 18 February 2002 11:46 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 GAA00573
for <rohc-archive@odin.ietf.org>; Mon, 18 Feb 2002 06:46: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 GAA15312;
Mon, 18 Feb 2002 06:41:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA15281
for <rohc@optimus.ietf.org>; Mon, 18 Feb 2002 06:41:57 -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 GAA00526
for <rohc@ietf.org>; Mon, 18 Feb 2002 06:41:52 -0500 (EST)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19)
id <1S9WNHHW>; Mon, 18 Feb 2002 11:40:30 -0000
Message-ID: <76C92FBBFB58D411AE760090271ED418033555EF@rsys002a.roke.co.uk>
From: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
To: "'hans.hannu@epl.ericsson.se'" <hans.hannu@epl.ericsson.se>,
"'rohc@ietf.org'" <rohc@ietf.org>
Subject: RE: [rohc] default algorithm, redux
Date: Mon, 18 Feb 2002 11:40:29 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
boundary="------------InterScan_NT_MIME_Boundary"
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
Hans, Thanks for these clarifications. For completeness here are the results for the same files with no dynamic compression and no sharing - just each file compressed independently of everything else. message static dynamic forward direction 1 587 502 4 457 395 6 434 377 7 216 200 9 249 232 12 227 213 reverse direction 2 223 210 3 685 576 5 227 214 8 266 245 10 216 203 11 239 225 Best Regards, Abbie > I think we have been talking (again) about different things. > What I meant with dynamic compression, regardless of the compression > algorithm used, is that: > (Referring to an old expired draft SigComp -02) > > "5.3. Dynamic compression > A compressing entity MAY choose to use previously sent messages in > the compression process in an attempt to improve the compression > efficiency. This is referred to as dynamic compression." > > "5.4. Shared compression > > Shared compression is referred to the case when a > compressor 'A' make > use of decompressed messages received by the decompressor > located at > the same SigComp entity. These decompressed messages MUST originate > from the corresponding SigComp entity, which decompressor is > controlled by compressor 'A'." > > So, the figures you present in this mail, would be with the above > definition, compressed using "dynamic" compression, and in > your previous > mail, both "shared" and "dynamic" compression were used. > > BR > /Hans H > >
- RE: [rohc] default algorithm, redux Surtees, Abigail