RE: [rohc] The discussion on slope(s)

"Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com> Fri, 03 December 2004 18:36 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17118 for <rohc-web-archive@ietf.org>; Fri, 3 Dec 2004 13:36:43 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaINw-0007Hu-Vx for rohc-web-archive@ietf.org; Fri, 03 Dec 2004 13:42:45 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CaFKI-0005Fp-Q3; Fri, 03 Dec 2004 10:26:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CaEz0-00041g-4Y for rohc@megatron.ietf.org; Fri, 03 Dec 2004 10:04:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12648 for <rohc@ietf.org>; Fri, 3 Dec 2004 10:04:28 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaF4j-0005VY-SQ for rohc@ietf.org; Fri, 03 Dec 2004 10:10:27 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119]) by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id iB3F4RvD025515 for <rohc@ietf.org>; Fri, 3 Dec 2004 16:04:27 +0100 (MET)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Fri, 3 Dec 2004 16:04:25 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72) id <XVCVQNM8>; Fri, 3 Dec 2004 16:04:25 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E99CD@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Subject: RE: [rohc] The discussion on slope(s)
Date: Fri, 03 Dec 2004 16:04:20 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain; charset="iso-8859-1"
X-OriginalArrivalTime: 03 Dec 2004 15:04:25.0608 (UTC) FILETIME=[60FA6880:01C4D949]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25

> > > Well, zero is not exactly prohibited, but then you couldn't 
> > > send any other value than TS_OFFSET, which wouldn't be too useful.
> 
> It is true that with a TS_STRIDE of 0, one would not be able to
> scale the TS value when it actually have to be sent, but I would
> not say TS_OFFSET=0 is useless, as one would be able to omit the
> TS in consecutive packets with constant TS.

Of course, I meant "I would not say TS_STRIDE=0 is useless"

/L-E

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