IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Thu, 02 December 2004 23:25 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 SAA13708 for <rohc-web-archive@ietf.org>; Thu, 2 Dec 2004 18:25:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ca0PX-0002Jr-8o for rohc-web-archive@ietf.org; Thu, 02 Dec 2004 18:30:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZvUN-0004QI-1M; Thu, 02 Dec 2004 13:15:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZuIJ-0000Cd-SB for rohc@megatron.ietf.org; Thu, 02 Dec 2004 11:59:04 -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 LAA08657 for <rohc@ietf.org>; Thu, 2 Dec 2004 11:59:01 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4] helo=informatik.uni-bremen.de) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZuNr-00011q-MH for rohc@ietf.org; Thu, 02 Dec 2004 12:04:49 -0500
Received: from [IPv6:::1] (imh [134.102.224.4]) by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id iB2GwkZ4012619; Thu, 2 Dec 2004 17:58:47 +0100 (MET)
In-Reply-To: <41AF25BE.2090203@effnet.com>
References: <A943FD84BD9ED41193460008C7918050072E99B5@ESEALNT419.al.sw.ericsson.se> <41AF25BE.2090203@effnet.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <6E745528-4483-11D9-951E-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] The discussion on slope(s)
Date: Thu, 02 Dec 2004 17:58:46 +0100
To: Kristofer Sandlund <kristofer.sandlund@effnet.com>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: rohc@ietf.org, Carsten Bormann <cabo@tzi.org>, "'zhigang.c.liu@nokia.com'" <zhigang.c.liu@nokia.com>, "Ghyslain Pelletier (LU/EAB)" <ghyslain.pelletier@ericsson.com>, "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
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: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit

> the slope itself would not be covered by a CRC

Kristofer,

what do you mean by this?

If we assume the msg934 model for slopes 
(http://www1.ietf.org/mail-archive/web/rohc/old-archive/msg00934.html), 
the slope is established from CRC-protected packets only.
(Since ACKs can get lost, there is still some uncertainty what slope is 
actually established, so the compressor has to be careful about what it 
has sent, but this is a detail.)

Of course, the slope itself indeed is not protected.
Also, of course, CRC-protected packets still have a non-zero 
probability of bit errors being uncaught.

Gruesse, Carsten


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

v2.23.0 | Report a Bug | By Email