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

[[e-mail]]

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: [e-mail] [mailto:[e-mail]]On Behalf Of
> ext Lars-Erik Jonsson (LU/EAB)
> Sent: 25 November, 2004 05:08 AM
> To: '[e-mail]'
> 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: [e-mail]                      /"\
> Phone: [phone]                                      \ /
> Fax: [phone]               ASCII Ribbon Campaign      X
> Home: [phone]           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
> [e-mail]
> https://www1.ietf.org/mailman/listinfo/rohc
> 

_______________________________________________
Rohc mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/rohc