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

Carsten Bormann <cabo@tzi.org> Wed, 01 December 2004 02:54 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 VAA16752 for <rohc-web-archive@ietf.org>; Tue, 30 Nov 2004 21:54:10 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZKiO-00037X-Ua for rohc-web-archive@ietf.org; Tue, 30 Nov 2004 21:59:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZKZH-00070m-HG; Tue, 30 Nov 2004 21:50:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZKYW-0006Yj-7u for rohc@megatron.ietf.org; Tue, 30 Nov 2004 21:49:24 -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 VAA16023 for <rohc@ietf.org>; Tue, 30 Nov 2004 21:49:22 -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 1CZKdk-0002ye-Jz for rohc@ietf.org; Tue, 30 Nov 2004 21:54: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 iB12nCO7002454; Wed, 1 Dec 2004 03:49:14 +0100 (MET)
In-Reply-To: <7B5AF06E216CB74DA8A5960A3181B5B82891AE@ajebe001.americas.nokia.com>
References: <7B5AF06E216CB74DA8A5960A3181B5B82891AE@ajebe001.americas.nokia.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <946FF734-4343-11D9-82C1-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] The discussion on slope(s)
Date: Wed, 01 Dec 2004 03:49:11 +0100
To: zhigang.c.liu@nokia.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: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, rohc@ietf.org, lars-erik.jonsson@ericsson.com, ghyslain.pelletier@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: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit

> It's clear that different people have different interpretations
> of what is "current 3095". Some people implemented learned slope
> while others didn't. However, learned slope is not something new.
> It has been discussed and agreed when we wrote up RFC 3095 (see
> below). Unfortunately, it was not written clearly enough.

Zhigang,

as far as I understand the current discussion, it is not about whether 
3095 is clear about dynamic slopes (it clearly isn't) -- it is about 
whether dynamic slopes made it into 3095 at all.
We have discussed many mechanisms during the development of 3095, not 
all of which made it into the specification.

Let me give an example for a good argument that dynamic slopes are not 
in 3095.
Consider section 6.5.
This section was intended as the basis for future documents describing 
context transfer, so it lists all the state that a compressor/a 
decompressor needs to maintain.
Dynamic slopes are not among this state.

Gruesse, Carsten


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