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

zhigang.c.liu@nokia.com Tue, 30 November 2004 17:39 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 MAA12125 for <rohc-web-archive@ietf.org>; Tue, 30 Nov 2004 12:39:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZC3i-0001br-NM for rohc-web-archive@ietf.org; Tue, 30 Nov 2004 12:45:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZBpO-00074i-CG; Tue, 30 Nov 2004 12:30:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZBbc-0001c5-TW for rohc@megatron.ietf.org; Tue, 30 Nov 2004 12:16:03 -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 MAA08491 for <rohc@ietf.org>; Tue, 30 Nov 2004 12:15:58 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZBgl-0000p7-N2 for rohc@ietf.org; Tue, 30 Nov 2004 12:21:20 -0500
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id iAUHFov13171; Tue, 30 Nov 2004 19:15:51 +0200 (EET)
X-Scanned: Tue, 30 Nov 2004 19:15:25 +0200 Nokia Message Protector V1.3.31 2004060815 - RELEASE
Received: (from root@localhost) by esdks002.ntc.nokia.com (8.12.9/8.12.9) id iAUHFPXj015332; Tue, 30 Nov 2004 19:15:25 +0200
Received: from mgw-int2.ntc.nokia.com (172.21.143.97) by esdks002.ntc.nokia.com 006K1Vl2; Tue, 30 Nov 2004 19:15:22 EET
Received: from daebh001.NOE.Nokia.com (daebh001.americas.nokia.com [10.241.35.121]) by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id iAUGfBS27870; Tue, 30 Nov 2004 18:41:11 +0200 (EET)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Tue, 30 Nov 2004 10:41:06 -0600
content-class: urn:content-classes:message
Subject: RE: [rohc] The discussion on slope(s)
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Tue, 30 Nov 2004 11:41:05 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B82891AE@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] The discussion on slope(s)
Thread-Index: AcTW0mvGQ9z6scU1QPub8FCYQCgsIgAHrGwQ
To: ghyslain.pelletier@ericsson.com, lars-erik.jonsson@ericsson.com, rohc@ietf.org
X-OriginalArrivalTime: 30 Nov 2004 16:41:06.0978 (UTC) FILETIME=[639FF820:01C4D6FB]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 25eb6223a37c19d53ede858176b14339
Content-Transfer-Encoding: quoted-printable
Cc: cabo@tzi.org
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.3 (/)
X-Scan-Signature: 995b2e24d23b953c94bac5288c432399
Content-Transfer-Encoding: quoted-printable

Ghyslian,

> > 1) This seemed to be the conclusion back in March/April, after 
> > a long and good discussion among many people.
> 
> I certainly don't recall such an homogeneous conclusion.
> I think many gave up the discussion because it started
> being venomous.

I don't know why you call the discussion venomous. I have proposed
and most people have been sticking to the technical substance. 
The discussion stopped because there were no more counter
arguments against learned slope. 

> > 3) Technically, the need of implicit slopes have been well explained
> 
> To clarify this, there is no _need_ for this, the current 
> 3095 not having implicit slopes works well. So it is not something that is 
> missing in the specification and that should now be added.

I'd suggest you to read the examples and comment directly on them.

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.

> > 5) Many other issues have already been clarified in 
> > March/April discussion:
> > - The learned slope *was* part of RFC 3095, as agreed among authors:
> > http://www1.ietf.org/mail-archive/web/rohc/current/msg02078.html
> 
> How can you refer to your own mail to state that authors agreed?
> I have definitely heard the opposite from other authors, and I hope
> they will contribute to this thread.

My email has references to earlier email discussions between Mikael 
and me. It demonstrates that learned slope was agreed upon when we were 
writing up the encoding of 3095. We didn't hear disagreement at that
time on the mailing list, including those from other 3095 authors.

BR, Zhigang

> Best regards,
> 
> /Ghyslain
> 
> 
> 
> > -----Original Message-----
> > From: rohc-bounces@ietf.org 
> [mailto:rohc-bounces@ietf.org]On Behalf Of
> > zhigang.c.liu@nokia.com
> > Sent: den 29 november 2004 19:18
> > To: Lars-Erik Jonsson (LU/EAB); rohc@ietf.org
> > Subject: RE: [rohc] The discussion on slope(s)
> > 
> > 
> > Lars-Erik and Others,
> > 
> > I'd like to propose to keep the implicit (or learned) slopes 
> > in 3095 and clarify it in the implementer's guide. It's not
> > a waste of time.
> > 
> > 1) This seemed to be the conclusion back in March/April, after 
> > a long and good discussion among many people.
> > 
> > 2) Resource limitation should not be a problem (if it has been). 
> > I can volunteer to write the clarification text in the 
> > implementer's guide. And I believe there are other people on
> > this list wanting to contribute.
> > 
> > 3) Technically, the need of implicit slopes have been well explained
> > with many examples. The last email on that was between Pawel and me:
> > http://www1.ietf.org/mail-archive/web/rohc/current/msg02138.html.
> > Kamal also agreed with me.
> > http://www1.ietf.org/mail-archive/web/rohc/current/msg02100.html
> > After that, I don't see any emails of counter argument. 
> > 
> > 4) The confusion was not only about implicit slope. It is also
> > about the fundamental encoding of 3095, such as the separation 
> > between scale and compression of scaled TS, the difference between 
> > TS_STRIDE and slope. They should be clarified in the implementer's
> > guide. (I remember I have answered almost every question on the
> > list back in March/April.)
> > 
> > 5) Many other issues have already been clarified in 
> > March/April discussion:
> > - The learned slope *was* part of RFC 3095, as agreed among authors:
> > http://www1.ietf.org/mail-archive/web/rohc/current/msg02078.html
> > - TS can be compressed after scaling or can be compressed 
> > without scaling:
> > http://www1.ietf.org/mail-archive/web/rohc/current/msg02077.html
> > - Why different interpretations didn't catch fire during 
> > inter-op tests?
> > http://www1.ietf.org/mail-archive/web/rohc/current/msg02122.html
> > 
> > BR, Zhigang
> > 
> > > -----Original Message-----
> > > From: rohc-bounces@ietf.org 
> > [mailto:rohc-bounces@ietf.org]On Behalf Of
> > > ext Lars-Erik Jonsson (LU/EAB)
> > > Sent: 25 November, 2004 05:08 AM
> > > To: 'rohc@ietf.org'
> > > Subject: [rohc] The discussion on slope(s)
> > > 
> > > 
> > > ROHCers,
> > > 
> > > In Washington DC, we had a discussion about the 3095 slope
> > > problem, which still is an open issue for the implementer's
> > > guide to clarify, if we want to ensure interoperability. My
> > > initial opinion was that the previous discussions on the list
> > > indicated we would have to do a careful study of this to be
> > > able to get consensus, and write a draft explaining both
> > > operations (with and without implicit slopes). However, the
> > > sense of the room I got was that we should not waste too
> > > much effort on this, but actually declare implicit slopes as 
> > > not to be part of 3095, and in the implementer's guide just
> > > point out the text parts of 3095 that caused this confusion
> > > and clarify accordingly. Although I personally agree with
> > > this approach and believe it is the only reasonable way to
> > > go, I will not propose any text for the implementer's guide
> > > before there is consensus to go with the proposed approach.
> > > 
> > > Therefore, I ask for opinions on this, more or less
> > > elaborated. See it as a HUM, with possibility to provide
> > > more details. 
> > > 
> > > To find the previous ROHC list discussion on slopes, please
> > > refer to the archives from March 17 to April 16 this year.
> > > 
> > > This is currently the only open issue for the implementer's
> > > guide and I need your help to get this resolved.
> > > 
> > > Thanks!
> > > /L-E
> > > 
> > > -----------------------------------
> > > Lars-Erik Jonsson, M.Sc.
> > > Senior Research Engineer
> > > Wireless IP Optimizations
> > > AWARE - Advanced Wireless Algorithm Research
> > > Ericsson Research, Corporate Unit
> > > Ericsson AB
> > > Box 920, S-971 28 LuleƄ, Sweden
> > > E-mail: lars-erik.jonsson@ericsson.com                      /"\
> > > Phone: +46 8 404 29 61                                      \ /
> > > Fax: +46 920 996 21               ASCII Ribbon Campaign      X
> > > Home: +46 920 999 57           against HTML email & vCards  / \
> > > 
> > > My opinions are my personal opinions and should not be considered
> > > as the opinions of my employer, if not explicitly stated.
> > > 
> > > _______________________________________________
> > > Rohc mailing list
> > > Rohc@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/rohc
> > > 
> > 
> > _______________________________________________
> > Rohc mailing list
> > Rohc@ietf.org
> > https://www1.ietf.org/mailman/listinfo/rohc
> > 
> 

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