From mailman-bounces@ietf.org  Wed Dec  1 06:48:59 2004
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 GAA18086
	for <rohc-web-archive@ietf.org>; Wed, 1 Dec 2004 06:48:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZT42-0006Sx-TR
	for rohc-web-archive@ietf.org; Wed, 01 Dec 2004 06:54:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZS7G-0000g0-47
	for rohc-web-archive@ietf.org; Wed, 01 Dec 2004 05:53:46 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: rohc-web-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.7892.1101897175.3553.mailman@lists.ietf.org>
Date: Wed, 01 Dec 2004 05:32:55 -0500
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

**********************************************************************

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for rohc-web-archive@ietf.org:

List                                     Password // URL
----                                     --------  
rohc@ietf.org                            umDk      
https://www1.ietf.org/mailman/options/rohc/rohc-web-archive%40ietf.org


From rohc-bounces@ietf.org  Wed Dec  1 18:20:04 2004
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 SAA08959
	for <rohc-web-archive@ietf.org>; Wed, 1 Dec 2004 18:20:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZdqw-0008LP-0o
	for rohc-web-archive@ietf.org; Wed, 01 Dec 2004 18:25:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZdbz-0003J7-7L; Wed, 01 Dec 2004 18:10:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZdPc-0001OE-GE
	for rohc@megatron.ietf.org; Wed, 01 Dec 2004 17:57:28 -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 RAA06037
	for <rohc@ietf.org>; Wed, 1 Dec 2004 17:57:26 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZdV0-0007hr-QF
	for rohc@ietf.org; Wed, 01 Dec 2004 18:03:04 -0500
Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iB1MvIS24887; Thu, 2 Dec 2004 00:57:19 +0200 (EET)
X-Scanned: Thu, 2 Dec 2004 00:57:01 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id iB1Mv19U008055;
	Thu, 2 Dec 2004 00:57:01 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks003.ntc.nokia.com 00Ecfzss; Thu, 02 Dec 2004 00:56:58 EET
Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com
	[10.241.35.122])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iB1Muua12876; Thu, 2 Dec 2004 00:56:56 +0200 (EET)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by
	daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 1 Dec 2004 16:56:55 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] The discussion on slope(s)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Wed, 1 Dec 2004 17:56:54 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B82891B2@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] The discussion on slope(s)
Thread-Index: AcTXUUtcZI8FY3bkR9Ot1cLiC+517AAeVDIQ
To: <cabo@tzi.org>
X-OriginalArrivalTime: 01 Dec 2004 22:56:55.0004 (UTC)
	FILETIME=[0DB571C0:01C4D7F9]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: quoted-printable
Cc: 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.3 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: quoted-printable

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

Carsten,

That is because dynamic slopes were not considered worthwhile=20
to transfer. The benefit of transferring dynamic slopes is
to stay in SO state during context transfer. However it's
complicated because the compressor may not be in SO state=20
at the beginning or in the middle of a context transfer.

Of course, the point is debatable. But we really haven't
had a chance to discuss. I was one of the proponents of=20
context transfer, but many other authors opposed the idea of=20
context transfer at that time. As a result, context relocation=20
is not mentioned by 3095 at all, and there has been no serious=20
discussion/work on context relocation in ROHC.

In 3GPP, however, ROHC context relocation has been discussed and
adopted in TS 25.331 (I remember it's optional). There, SYN_SLOPE_TS
(the last synchronized slope of TS) was defined as an optional
parameter in context transfer.

I think it's fair to also look at the arguments that dynamic
(or learned or implicit) slopes are in 3095. I have given some
back in March/April. Below is one of them. If I have to summarize
in one sentence, the argument is that if dynamic slopes are not
in 3095, many text (some are essential to encoding) wouldn't=20
make sense without twisting hard the meaning of words.
http://www1.ietf.org/mail-archive/web/rohc/current/msg02101.html

BR, Zhigang





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


From rohc-bounces@ietf.org  Wed Dec  1 18:47:21 2004
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 SAA11582
	for <rohc-web-archive@ietf.org>; Wed, 1 Dec 2004 18:47:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZeHL-0000ff-BR
	for rohc-web-archive@ietf.org; Wed, 01 Dec 2004 18:52:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZdna-0001QS-F6; Wed, 01 Dec 2004 18:22:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZdkm-0005fb-BI; Wed, 01 Dec 2004 18:19:20 -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 SAA08859;
	Wed, 1 Dec 2004 18:19:18 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZdqB-0008KJ-Vh; Wed, 01 Dec 2004 18:24:56 -0500
Received: from apache by megatron.ietf.org with local (Exim 4.32)
	id 1CZdbf-0002z4-GB; Wed, 01 Dec 2004 18:09:55 -0500
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1CZdbf-0002z4-GB@megatron.ietf.org>
Date: Wed, 01 Dec 2004 18:09:55 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: rohc@ietf.org
Subject: [rohc] Last Call: 'A Negative Acknowledgement Mechanism for
 Signaling Compression' to Proposed Standard 
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org
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: 856eb5f76e7a34990d1d457d8e8e5b7f

The IESG has received a request from the Robust Header Compression WG to 
consider the following document:

- 'A Negative Acknowledgement Mechanism for Signaling Compression '
   <draft-ietf-rohc-sigcomp-nack-02.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2004-12-15.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-rohc-sigcomp-nack-02.txt


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


From rohc-bounces@ietf.org  Thu Dec  2 06:13:15 2004
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 GAA29789
	for <rohc-web-archive@ietf.org>; Thu, 2 Dec 2004 06:13:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZoz4-0006v3-2r
	for rohc-web-archive@ietf.org; Thu, 02 Dec 2004 06:19:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZofx-0000Jk-UB; Thu, 02 Dec 2004 05:59:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZmrK-0003v2-04
	for rohc@megatron.ietf.org; Thu, 02 Dec 2004 04:02:42 -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 EAA21480
	for <rohc@ietf.org>; Thu, 2 Dec 2004 04:02:40 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZmwo-0004N0-GI
	for rohc@ietf.org; Thu, 02 Dec 2004 04:08:23 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iB292ZR2021243 for <rohc@ietf.org>; Thu, 2 Dec 2004 10:02:35 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 2 Dec 2004 10:02:35 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <XVCVD0D9>; Thu, 2 Dec 2004 10:02:26 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E99B5@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'zhigang.c.liu@nokia.com'" <zhigang.c.liu@nokia.com>, cabo@tzi.org
Subject: RE: [rohc] The discussion on slope(s)
Date: Thu, 2 Dec 2004 10:00:37 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 02 Dec 2004 09:02:35.0253 (UTC)
	FILETIME=[AA2F6250:01C4D84D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: rohc@ietf.org,
        "Ghyslain Pelletier \(LU/EAB\)" <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: d185fa790257f526fedfd5d01ed9c976

Folks,

Unfortunately, it seems like I was wrong when I hoped we would be
able to easily close this issue, I got over-optimistic by the
sense of the room at the Washington DC meeting. The discussions
in March/April died with no conclusion and all involved parties
got tired of repeating the same arguments over and over again
without getting any closer to an agreement. Since then, I have
also had the feeling that this will require a detailed analysis
of the slope/non-slope algorithms, to be able to answer the
questions I earlier outlined, which is the way I still think we
will have to go to get closure on the issue:
http://www1.ietf.org/mail-archive/web/rohc/current/msg02085.html
However, it seems like this requires that someone seriously looks
at this problem from both perspectives so that everyone can see
what we have to decide upon. This will be resource-demanding, 
while I do not think it will be very tricky to write the final
clarifying text in the implementer's guide. As always, it is the
preparation work that takes time. I expressed this feeling both
in San Diego and in Washington, and although the response in
Washington was that we should not make this to complicated but
just get rid of slopes, I am still pretty sure after last weeks
mails on the list that we will have to spend some effort on this.

Personally, I am still sure there is no need for a learned slope,
and I can not see why we should expand the 3095 text and logic
to capture it, when something like it is only mentioned (but not
even close to defined) at a few places in 3095. However, that is
my opinion and others disagree, so I am afraid we might have to
do the detailed analysis before we will be able to get (at least
a rough) consensus on this.

However, I would like to make a few observations on what makes
me so confident in what is the "right" solution, apart from my
own opinion on the technical problem.

There are only two implementers whose implementations have made
it to all interop meetings, and who have thus learned ROHC RTP
from the specification, implemented it, got it to interoperate,
and also discussed/tested the TS encoding at an interop meeting
to get a clear opinion on the slope question. Their opinions
have been expressed in this ongoing mail thread:

Vick:
http://www1.ietf.org/mail-archive/web/rohc/current/msg02097.html

Kristofer:
http://www1.ietf.org/mail-archive/web/rohc/current/msg02033.html
http://www1.ietf.org/mail-archive/web/rohc/current/msg02062.html
http://www1.ietf.org/mail-archive/web/rohc/current/msg02071.html
http://www1.ietf.org/mail-archive/web/rohc/current/msg02081.html
(the last one included questions to Zhigang, which were ignored)

Finally, I would like to send a direct appeal to Zhigang, as a
comment on yesterday's mail on this subject:

> ZL:
> I think it's fair to also look at the arguments that dynamic
> (or learned or implicit) slopes are in 3095. I have given some
> back in March/April. Below is one of them. If I have to summarize
> in one sentence, the argument is that if dynamic slopes are not
> in 3095, many text (some are essential to encoding) wouldn't 
> make sense without twisting hard the meaning of words.
> http://www1.ietf.org/mail-archive/web/rohc/current/msg02101.html

Can you then list these parts, please cut and paste the sentences
in an e-mail, do not use references. A previous proposal for what
to clarify in the implementer's guide to get rid of the confusing
slope wordings can be found at:
http://www1.ietf.org/mail-archive/web/rohc/current/msg02089.html
The attempts to clarify the slope concept and actually define it
have been much more complicated, which I also think is necessary
if we go that way.

BR
/L-E

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


From rohc-bounces@ietf.org  Thu Dec  2 06:15:15 2004
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 GAA00045
	for <rohc-web-archive@ietf.org>; Thu, 2 Dec 2004 06:15:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZp0n-0006yd-Us
	for rohc-web-archive@ietf.org; Thu, 02 Dec 2004 06:21:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZogA-0000SE-I3; Thu, 02 Dec 2004 05:59:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZn04-0005Xe-DG
	for rohc@megatron.ietf.org; Thu, 02 Dec 2004 04:11:44 -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 EAA22083
	for <rohc@ietf.org>; Thu, 2 Dec 2004 04:11:42 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZn5Y-0004WL-07
	for rohc@ietf.org; Thu, 02 Dec 2004 04:17:25 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iB29Bfh5004747
	for <rohc@ietf.org>; Thu, 2 Dec 2004 10:11:41 +0100 (MET)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 2 Dec 2004 10:11:41 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <XVCV1BJ7>; Thu, 2 Dec 2004 10:11:36 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E99B6@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Thu, 2 Dec 2004 10:10:57 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-OriginalArrivalTime: 02 Dec 2004 09:11:41.0489 (UTC)
	FILETIME=[EFC46210:01C4D84E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: quoted-printable
Subject: [rohc] MINE header compression clarification?
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: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: quoted-printable

ROHCers,

Since I have received several questions on how the MINE header
is to be compressed (as it is listed as a compressible header
but not further discussed in the same way as the other extension
headers listed), I would like to add the following line at the
end of section 5.6 of the implementer's guide:

"It should further be noted that for the Minimal Encapsulation
(MINE) header, there is no explicit discussion of how to
compress it, as the header is either sent uncompressed or
fully compressed away."

Any comments on this?
/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=E5, 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


From rohc-bounces@ietf.org  Thu Dec  2 12:37:41 2004
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 MAA13336
	for <rohc-web-archive@ietf.org>; Thu, 2 Dec 2004 12:37:41 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZuzJ-0002SD-SK
	for rohc-web-archive@ietf.org; Thu, 02 Dec 2004 12:43:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZquf-0000IW-Qy; Thu, 02 Dec 2004 08:22:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZqEi-0005oJ-H8
	for rohc@megatron.ietf.org; Thu, 02 Dec 2004 07:39: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 HAA09625
	for <rohc@ietf.org>; Thu, 2 Dec 2004 07:39:03 -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 1CZqKF-0000wx-2x
	for rohc@ietf.org; Thu, 02 Dec 2004 07:44:47 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iB2CctiU000010; Thu, 2 Dec 2004 13:38:57 +0100 (MET)
In-Reply-To: <A943FD84BD9ED41193460008C7918050072E99B6@ESEALNT419.al.sw.ericsson.se>
References: <A943FD84BD9ED41193460008C7918050072E99B6@ESEALNT419.al.sw.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <21AAF025-445F-11D9-82C1-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] MINE header compression clarification?
Date: Thu, 2 Dec 2004 13:38:56 +0100
To: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.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: 30ac594df0e66ffa5a93eb4c48bcb014
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, "'rohc@ietf.org'" <rohc@ietf.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.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit

> "It should further be noted that for the Minimal Encapsulation
> (MINE) header, there is no explicit discussion of how to
> compress it, as the header is either sent uncompressed or
> fully compressed away."

Sounds good to me (this certainly was the intention).

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Thu Dec  2 15:06:58 2004
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 PAA22976
	for <rohc-web-archive@ietf.org>; Thu, 2 Dec 2004 15:06:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZxJl-0005dL-M8
	for rohc-web-archive@ietf.org; Thu, 02 Dec 2004 15:12:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZutZ-0002KA-0K; Thu, 02 Dec 2004 12:37:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZqlA-0002Ue-9n
	for rohc@megatron.ietf.org; Thu, 02 Dec 2004 08:12:36 -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 IAA12875
	for <rohc@ietf.org>; Thu, 2 Dec 2004 08:12:34 -0500 (EST)
Received: from rproxy.gmail.com ([64.233.170.204])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZqqg-0001tU-DO
	for rohc@ietf.org; Thu, 02 Dec 2004 08:18:19 -0500
Received: by rproxy.gmail.com with SMTP id a36so797608rnf
	for <rohc@ietf.org>; Thu, 02 Dec 2004 05:12:34 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding;
	b=TyI2wjCY6bDTFeNqp34k7TLANnGylOiTvIFpFPV8dWs+Q01l0J6gylIpfFtqIL3XHzOCtgsD/xJyTmc4eijEzBy9KjXnE7fQYM35u2fIkv1DguWh1U7VuxYIIuHwqEVfmzqXTCC5p5AMFcd6qLlNbXTti5ENzGyKBQzqZMxw++4=
Received: by 10.38.77.6 with SMTP id z6mr779869rna;
	Thu, 02 Dec 2004 05:12:34 -0800 (PST)
Received: by 10.38.83.41 with HTTP; Thu, 2 Dec 2004 05:12:34 -0800 (PST)
Message-ID: <1bd254fc0412020512640add34@mail.gmail.com>
Date: Thu, 2 Dec 2004 18:42:34 +0530
From: chitrak gupta <mailfromchitrak@gmail.com>
To: rohc@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Content-Transfer-Encoding: 7bit
Subject: [rohc] Deflate Byte Code with Dictionary
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: chitrak gupta <mailfromchitrak@gmail.com>
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: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit

Hi all,

Can anyone provide me with a Deflate bytecode which uses a Static
dictionary for SIGCOMP. It will be  much helpful if anyone can provide
a test data to test the ByteCode using a UDVM implementation.

Thanks in advance
Chitrak Gupta.

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


From rohc-bounces@ietf.org  Thu Dec  2 16:42:21 2004
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 QAA02051
	for <rohc-web-archive@ietf.org>; Thu, 2 Dec 2004 16:42:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZyo6-0007sx-Iy
	for rohc-web-archive@ietf.org; Thu, 02 Dec 2004 16:48:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZuxO-00067L-KG; Thu, 02 Dec 2004 12:41:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZroA-00073K-EU
	for rohc@megatron.ietf.org; Thu, 02 Dec 2004 09:19:46 -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 JAA20582
	for <rohc@ietf.org>; Thu, 2 Dec 2004 09:19:44 -0500 (EST)
Received: from [194.237.235.30] (helo=effnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZrth-0004Nw-95
	for rohc@ietf.org; Thu, 02 Dec 2004 09:25:30 -0500
Received: from effnet.com (c-b97c71d5.04-205-6c756c1.cust.bredbandsbolaget.se
	[213.113.124.178]) (authenticated bits=0)
	by effnet.com (8.12.3/8.12.3) with ESMTP id iB2DIdLh012222
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Thu, 2 Dec 2004 14:18:40 +0100
Message-ID: <41AF25BE.2090203@effnet.com>
Date: Thu, 02 Dec 2004 15:25:02 +0100
From: Kristofer Sandlund <kristofer.sandlund@effnet.com>
Organization: Effnet
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
Subject: Re: [rohc] The discussion on slope(s)
References: <A943FD84BD9ED41193460008C7918050072E99B5@ESEALNT419.al.sw.ericsson.se>
In-Reply-To: <A943FD84BD9ED41193460008C7918050072E99B5@ESEALNT419.al.sw.ericsson.se>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit
Cc: rohc@ietf.org, cabo@tzi.org,
        "'zhigang.c.liu@nokia.com'" <zhigang.c.liu@nokia.com>,
        "Ghyslain Pelletier \(LU/EAB\)" <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.1 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit

Hi all,

as I've stated before, I don't think slope is defined in 3095, and to me that 
would be good-enough for closing this issue. But since we do not have consensus, 
let's present some problems with accepting this scheme.

The slope scheme has (at least) one patological worst case where it simply 
destroys the entire compression. (if I have managed to understand how it was 
meant to work, that is).

- Let's say we're operating in R-mode.
- The slope will only be used for decompression when packets without any TS bits 
are sent (R-0, R-0-CRC).
- The slope gets out of synch between compressor and decompressor (bit errors 
will be able to do this, especially since the slope itself would not be covered 
by a CRC). For example, let's say we got hc_slope=0, dc_slope=1. Note that the 
compressor will only see ACKs in order to update slope, it will not know _what_ 
slope value is being ACKed in the case where the decompressor gets it wrong.
- The traffic sent is video where you'd have TS: X, X, X, X, X+1, X+1, X+1, X+1 
(4 packets per video frame).
- What the compressor is likely to send will be something like UOR-2-TS, R-0, 
R-0, R-0, UOR-2-TS, R-0, R-0, R-0 (assuming immediate ACK).
   Note: From what I understand of the pRTT algorithm in 3095, it is enough to 
ACK the type 2 packets, so there is nothing in the spec to guarantee that ANY 
R-0-CRC packets will be sent.
- So, when the UOR-2-TS packets are decompressed, slope will not be used and the 
decompressor sends out an ACK which makes the compressor go back to SO state 
immediately (send R-0 packets again).
- When the R-0 packets are received, they will be erroneously decompressed due 
to the slope mismatch, but this will NOT BE DETECTED by the decompressor since 
there is no CRC on these packets (the packet with a bad timestamp value gets 
delivered out into the network). The only way a slope mismatch can be detected 
is through the reception of a R-0-CRC packet. And in this patological worst case 
stream the compressor will never produce such a packet.

So, the conclusion of this example is that all packets will be decompressed and 
delivered to the network, but 75% of them will have a bad timestamp (video 
frames spread out into a larger number of packets will get even worse figures). 
And, the decompressor will never even detect that it is doing this. Of course, 
this is a worst case situation, but I cannot see that it is _impossible_. To me, 
this situation is unacceptable and if this has even one chance in a million to 
occur, it is enough for me to say that we should not accept this scheme even if 
it had been defined in the spec.
And, if there is one worst case by just doing a quick theoretical analysis, 
there is a large chance that interop testing this will provide other near-worst 
cases (if running losses and/or BER). I also doubt that it is possible to 
specify the slope-updating mechanism well enough to get it to fully interoperate 
under lossy conditions (since the update is implicit and not crc-covered).

/Kristofer Sandlund, Effnet AB

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


From rohc-bounces@ietf.org  Thu Dec  2 17:08:28 2004
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 RAA04488
	for <rohc-web-archive@ietf.org>; Thu, 2 Dec 2004 17:08:28 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZzDO-0000F5-ID
	for rohc-web-archive@ietf.org; Thu, 02 Dec 2004 17:14:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZuyC-0006lo-NY; Thu, 02 Dec 2004 12:42:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZsI0-00019a-F4
	for rohc@megatron.ietf.org; Thu, 02 Dec 2004 09:50:36 -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 JAA23660
	for <rohc@ietf.org>; Thu, 2 Dec 2004 09:50:34 -0500 (EST)
Received: from [194.237.235.30] (helo=effnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZsNY-00050m-4z
	for rohc@ietf.org; Thu, 02 Dec 2004 09:56:20 -0500
Received: from effnet.com (c-b97c71d5.04-205-6c756c1.cust.bredbandsbolaget.se
	[213.113.124.178]) (authenticated bits=0)
	by effnet.com (8.12.3/8.12.3) with ESMTP id iB2DnSLh012309
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Thu, 2 Dec 2004 14:49:29 +0100
Message-ID: <41AF2CF7.2030403@effnet.com>
Date: Thu, 02 Dec 2004 15:55:51 +0100
From: Kristofer Sandlund <kristofer.sandlund@effnet.com>
Organization: Effnet
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Ghyslain Pelletier (LU/EAB)" <ghyslain.pelletier@ericsson.com>
Subject: Re: [rohc] ROHC-TCP, ack number compression
References: <A943FD84BD9ED41193460008C79180500C57065F@ESEALNT419.al.sw.ericsson.se>
In-Reply-To: <A943FD84BD9ED41193460008C79180500C57065F@ESEALNT419.al.sw.ericsson.se>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Content-Transfer-Encoding: 7bit
Cc: "'West, Mark'" <mark.a.west@roke.co.uk>, Carsten Bormann <cabo@tzi.org>,
        "'rohc@ietf.org'" <rohc@ietf.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.1 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Content-Transfer-Encoding: 7bit

Ok, to re-awaken the discussion on ack numbers in ROHC-TCP, I thought I'd list 
the options we have.

- The implicit ACK number scaling in bidirectional deployments seems to only 
have the support from Mark, while myself, Lars-Erik, Ghyslain and Carsten have 
doubts about the complexity required (Mark, if you want to keep this, please 
explain IN DETAIL how you want it to work). I think we should leave this out of 
the spec. (if I have misjudged the opinions of anyone or if someone else finds 
this to be compelling, please yell out before we scrap it)

This leaves us with (at least) the following different roads for this:
a) Only send unscaled ACK numbers. Not very optimal, will often have to send 
about one byte extra compared to a scaled scheme. Simple and clearly interoperable.
b) Explicit scaling (ack_stride, 16 bit value) by letting the compressor send 
over a scaling value in a compressed packet (for example, this value could be 
transmitted in the dynamic chain and co_common, but nowhere else). How this 
value is inferred by the compressor would be an implementation detail, so that 
it can use the reverse-directional stream, it could look at the traffic or it 
could use some proprietory out-of-band signalling etc. In this scheme, only one 
scaling value is legal at any one time and if the ack number change rate is very 
variable, then either we need a frequent update of the stride or we have to send 
unscaled values until the same stride "comes back". Not being a TCP expert, I 
can't really say how much gain/loss this would be in the end, but I think it 
seems worth considering.
Also, if we go for this strategy we need to decide how to handle it at context 
replication (always, never or optional).
c) optional feedback option sending the ack_stride (the sending entity's 
decompressor could take this value from the co-located compressor). This is like 
the bidirectional stuff but it is "explicit and optional" instead of "implicit 
and mandatory". Downsides are the delay before this can be used and also this 
will probably lead to some sliding window of scaling values so that 
compressor/decompressor keep in synch. I'm not for such a solution, since it 
seems complex and slightly evil.

I could consider option b), but as I stated, I cannot really estimate the gain, 
so possibly a) is good enough.

So, what should we do? Opinions welcome.

/Kristofer Sandlund, Effnet AB

Ghyslain Pelletier (LU/EAB) wrote:
> Hi all,
> 
> At first I thought it could be good to consider some kind of bidirectional compression, and thanks for information that was sent regarding this.
> 
> However, it now seems to me that this thread is converging towards keeping ack compression as it is.
> After reading the thread carefully, this is at least what I am in favor of right now.
> 
> I.e. let's keep 'vanilla' ack compression as it currently is.
> 
> /Ghyslain
> 
> 
>>-----Original Message-----
>>From: rohc-bounces@ietf.org [mailto:rohc-bounces@ietf.org]On Behalf Of
>>West, Mark
>>Sent: den 23 november 2004 01:37
>>To: Carsten Bormann
>>Cc: 'rohc@ietf.org'; Kristofer Sandlund; Lars-Erik Jonsson (LU/EAB)
>>Subject: Re: [rohc] ROHC-TCP, ack number compression
>>
>>
>>
>>
>>>>And I don't think it's a complex 'negotiation': the 
>>
>>compressor *does*
>>
>>>>need
>>>>to signal that it is storing ack numbers
>>>
>>>Also, we need some way to bind the forward and reverse channels, as
>>>well as the CIDs.
>>
>>True -- something that I had managed to ignore... :-)
>>
>>
>>>This may be interesting on some channels.
>>>(There was a reason we did the state ID dance for SigComp...)
>>>
>>
>>Good point: I'd managed to overlook flow separation issues 
>>(for example).
>>But do you really think that this is as messy as SigComp..?  We have a
>>little more control over the endpoints.  And so I don't think that the
>>SigComp state model is directly applicable.  (But I've still 
>>probably been
>>guilty of over simplifying...)
>>
>>Cheers,
>>
>>Mark.
>>
>>_______________________________________________
>>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

-- 
()  ascii ribbon campaign - against html mail
/\                        - against microsoft attachments


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


From rohc-bounces@ietf.org  Thu Dec  2 17:19:11 2004
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 RAA05377
	for <rohc-web-archive@ietf.org>; Thu, 2 Dec 2004 17:19:11 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZzNm-0000VE-6I
	for rohc-web-archive@ietf.org; Thu, 02 Dec 2004 17:25:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZywF-0001Hz-Li; Thu, 02 Dec 2004 16:56:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZxlA-0002Jb-GZ
	for rohc@megatron.ietf.org; Thu, 02 Dec 2004 15:41: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 PAA27890
	for <rohc@ietf.org>; Thu, 2 Dec 2004 15:41:02 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZxqk-0006Wa-9f
	for rohc@ietf.org; Thu, 02 Dec 2004 15:46:51 -0500
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iB2KeoS07969; Thu, 2 Dec 2004 22:40:50 +0200 (EET)
X-Scanned: Thu, 2 Dec 2004 22:40:01 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id iB2Ke10H015373;
	Thu, 2 Dec 2004 22:40:01 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 00sKI2aD; Thu, 02 Dec 2004 22:39:59 EET
Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com
	[10.241.35.122])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iB2Kdqa22469; Thu, 2 Dec 2004 22:39:52 +0200 (EET)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by
	daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Thu, 2 Dec 2004 14:38:06 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] The discussion on slope(s)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Thu, 2 Dec 2004 15:38:05 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B82891B6@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] The discussion on slope(s)
Thread-Index: AcTYTmX+BasxjL9OQtaDUqRk7EpqDgAO/3/w
To: <lars-erik.jonsson@ericsson.com>, <cabo@tzi.org>
X-OriginalArrivalTime: 02 Dec 2004 20:38:06.0977 (UTC)
	FILETIME=[D43B1F10:01C4D8AE]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Content-Transfer-Encoding: quoted-printable
Cc: rohc@ietf.org, 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.3 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Content-Transfer-Encoding: quoted-printable

Lars-Erik and Others,

> which is the way I still think we
> will have to go to get closure on the issue:
> http://www1.ietf.org/mail-archive/web/rohc/current/msg02085.html

I think I've answered - from my perspective - most of the questions
asked in the above email.

> 1) What was discussed during the development of 3095 in 1999-2000?

I've provided emails on ROHC mailing list where Mickael and I discussed
about the synchronization of the slope. The conclusion was that =
compression
starts with default-slope and then use "learned slope" if default-slope
is not good. Video example was discussed as one reason for that. It
was also clear that slope is a separate concept from TS_STRIDE, which
is a scale factor.

2) What was 3095 intended to say, back in 2000?

Above was what 3095 intended to say, in my opinion.

3) What is 3095 really saying?

As result of above and other discussions:

- Section 3.4 describe the function from SN to other fields X.
- Section 4.3.1.3 describes the function SN->X and SO state.
- Section 4.5.3 defines the scaling of TS before compression.
Note: scaling and thus TS_STRIDE is optional. While WLSB is
not. Neither is SO state. It should be self-evident that
TS_STRIDE is not the slope.
- Section 5.2.7 describes the function SN->X and packet types/formats.
- Section 5.5.1.2 describes the slope (yes, it should be put in
earlier sections. See below.)
- Section 5.7 defines the value of default-slope.

>From what I heard, there are two major sources of confusions about this:
- The definition of TS_STRIDE is section 2. It's not accurate and
makes people think TS_STRIDE is the slope. But it is isn't. It's
probably caused by glitch between different authors.
- The text on slope is in R-mode section. I don't know what exactly
happened. But following are probably some of the factors:
1) Because of work distribution, people knowing most about a technical
subject didn't get a chance to write the corresponding section.
2) We were under time-pressure. Not everyone reviewed rigorously
or cross checked every aspect of 3095.
3) 3095 was so long that making it shorter became one of the goals.
Unfortunately, some clarification text (e.g. those proposed during
email discussions) were left out in the final version. In retrospect,=20
they would help to avoid confusions.

4) How can 3095 be interpreted?

See above.

5) Now 2004, which solution do we think makes most sense, technically?

I'm a bit confused, and this is the difficulty I have. What is the
question in this discussion: a) learned slope or even slope doesn't
ever exist in 3095? b) even if it exists, we can re-evaluate and=20
decide to remove it (what is implied above)?

Anyway, I've given my opinions on both.

6) Now 2004, which solution would make most sense if we consider 3)?

See above.

7) How do we realize 6) in the implementers guide to ensure =
interoperability?

I think we haven't reached this yet.

> This will be resource-demanding,=20

Yes, it is. But this is a serious issue and we need to resolve it.
I've been devoting my time to read, reply, explain, give examples.=20
It's fair to say people with interest should try the same.

> There are only two implementers whose implementations have made
> it to all interop meetings,=20

Vick and Kristofer's work is certainly valuable to ROHC. I used to
do lots of coding so I understand how important it is. There are=20
also other implementers that didn't make all the interop meetings=20
due to various reasons. I know that the implementation team in
Nokia implemented learned slope. Unfortunately, as I explained earlier,=20
the interop tests didn't reveal the different understandings (
the test cases were not comprehensive enough).

Also, Pawel (who started the discussion) and Kamal seem to agree
with me. I don't know if they have done some implementation. But
their opinions are derived from reading of 3095 and discussions
in March/April.

> http://www1.ietf.org/mail-archive/web/rohc/current/msg02081.html
> (the last one included questions to Zhigang, which were ignored)

I probably missed Kristofer's email. It's not easy for me to
read/reply so many emails although I tried. I'll reply him in=20
a separate email.
=20
> Finally, I would like to send a direct appeal to Zhigang, as a
> comment on yesterday's mail on this subject:
>=20
> > ZL:
> > I think it's fair to also look at the arguments that dynamic
> > (or learned or implicit) slopes are in 3095. I have given some
> > back in March/April. Below is one of them. If I have to summarize
> > in one sentence, the argument is that if dynamic slopes are not
> > in 3095, many text (some are essential to encoding) wouldn't=20
> > make sense without twisting hard the meaning of words.
> > http://www1.ietf.org/mail-archive/web/rohc/current/msg02101.html
>=20
> Can you then list these parts, please cut and paste the sentences
> in an e-mail, do not use references.=20

I thought providing a link is a better way than resending the same
email. But I'll do it as you wish.

BR, Zhigang

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


From rohc-bounces@ietf.org  Thu Dec  2 17:48:33 2004
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 RAA09426
	for <rohc-web-archive@ietf.org>; Thu, 2 Dec 2004 17:48:33 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZzqC-0001SP-OJ
	for rohc-web-archive@ietf.org; Thu, 02 Dec 2004 17:54:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZyxl-0001lX-7q; Thu, 02 Dec 2004 16:58:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZy6Z-00037l-0A
	for rohc@megatron.ietf.org; Thu, 02 Dec 2004 16:03:11 -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 QAA29308
	for <rohc@ietf.org>; Thu, 2 Dec 2004 16:03:08 -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 1CZyC9-000767-WD
	for rohc@ietf.org; Thu, 02 Dec 2004 16:08:58 -0500
Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iB2L2vv23326; Thu, 2 Dec 2004 23:02:59 +0200 (EET)
X-Scanned: Thu, 2 Dec 2004 23:02:28 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id iB2L2S1b030395;
	Thu, 2 Dec 2004 23:02:28 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks003.ntc.nokia.com 00FoScs1; Thu, 02 Dec 2004 23:02:26 EET
Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com
	[10.241.35.122])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iB2L1Ja17228; Thu, 2 Dec 2004 23:01:19 +0200 (EET)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by
	daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Thu, 2 Dec 2004 14:59:27 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] The discussion on slope(s)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Thu, 2 Dec 2004 15:54:23 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B82891B7@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] The discussion on slope(s)
Thread-Index: AcTYTmX+BasxjL9OQtaDUqRk7EpqDgAYIFQw
To: <lars-erik.jonsson@ericsson.com>, <cabo@tzi.org>
X-OriginalArrivalTime: 02 Dec 2004 20:59:27.0213 (UTC)
	FILETIME=[CF4FA1D0:01C4D8B1]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Content-Transfer-Encoding: quoted-printable
Cc: rohc@ietf.org, 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.3 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Content-Transfer-Encoding: quoted-printable

Hello Folks,

As Lars-Erik asked, below is the clarification text I proposed
back in April, based on my own interpretation of text in 3095=20
written by myself. I also included some examples to show exactly=20
how encoding/decoding works. Those were actually discussed
when we developed 3095. But it's good to give them again to
show enough technical details.

Again, the clarification may be too verbose. My intention is to=20
make it as clear as possible.

As always, comments and questions are welcome.

Br, Zhigang

------------------------------------------------------------
As it is described in section 4.5.3 and other places in RFC
3095, TS_STRIDE is the factor by which an RTP Timestamp is
downscaled before compression. Obviously, it cannot be 0 (zero).

The wording of TS_STRIDE definition in section 2 is confusing
and may be incorrectly interpreted as TS_STRIDE is always equal
to the increase in TS value between two RTP packets with
consecutive sequence number. This is not the intent of the
specification. It is the compressor that decides whether TS=20
scaling should be used and if yes, what is the best value of=20
TS_STRIDE. See section 4.5.3 for information. How this is done=20
is an implementation issue. However, an implementation must follow=20
section 4.5.3, 4.5.6 and 5.7 on how to initialize, encode, and=20
synchronize TS_STRIDE between the compressor and decompressor.

Note: TS_STRIDE is not the same as slope described in section=20
5.5.1.2 and 5.7. Here, slope has the general meaning in mathematics.
Namely, slope(X) equals the change of a non-SN field X between
two packets divided by the change of SN field between the same
two packets. It is one of the two parameters (the other one
being offset) that define a linear function from SN to field X.
The concept can also be visualized as a line, with SN being
the horizontal coordinate and the field X being the vertical=20
coordinate. For TS, this applies regardless whether it is scaled=20
or not. In case the TS is scaled, the linear function (or equivalently
its slope and offset) is from SN to the TS_SCALED.

Note: it should be clear from section 4.5.3 that when scale is
used for TS, two steps are involved: 1) downscale of the=20
original TS to TS_SCALED; and 2) compression of TS_SCALED.
The decompressor follows the reverse procedure with two steps.
Following are two examples to further illustrate this.

Example 1 (audio stream with TS_STRIDE =3D 160):

            <------ String 1 ------>    <-- String 2 --->
SN           11  12  13  14 ...   60    61    62    63 ...
TS          200 360 420 580 ... 8040 16040 16200 16360 ...=20
TS_SCALED     1   2   3   4 ...   50   100   101   102 ...
TS_OFFSET    40  40  40  40       40    40    40    40 ...
slope       <--------  1 ---------->    <----- 1 ------->
offset      <-------- (-10)-------->    <----- (39) ---->

Example 2 (video stream with TS_STRIDE =3D 3000):

            <------ String 1 ------>  <-- String 2 --->
SN            11   12   13 ...    25   26   27   28 ...
TS          4000 4000 4000 ...  4000 7000 7000 7000 ...=20
TS_SCALED      1    1    1 ...     1    2    2    2 ...
TS_OFFSET   1000 1000 1000 ...  1000 1000 1000 1000 ...=20
slope       <--------  0 ---------->  <----- 0 ------->
offset      <--------- 1 ---------->  <----- 2 ------->

Note: the default-slope(X) specified in section 5.7 is to be used=20
by the compressor and decompressor to initialize the slope of the=20
linear function from SN to field X. This is an optimization to=20
save synchronization overhead at the beginning of an RTP packet=20
stream. Namely, if the actual slope of X in the first string matches=20
the default-slope(X), the compressor can enter SO state and send=20
Type 0 packets once it is confident that one - instead of two in=20
the normal case - packet carrying field(X) has been correctly=20
decompressed by the decompressor. This is enough for the decompressor
to determine the other parameter, i.e. offset, for the linear function
from SN to X. After the fist string, the decompressor will update the
linear function from SN to X depending on how many packets carrying
field(X) have been correctly decompressed. If the number is 1,
the decompressor will assume the new slope(X) =3D previously established
slope(X), and the update offset(X) based on field(X) received. If the=20
number is 2, the decompressor will update both slope(X) and offset(X).
Note that the decompressor always uses the latest received packet(s)
to update the function.

For instance, in Example 1 above, the compressor can enter SO state once
it is confident that one packet carrying TS has been correctly =
decompressed=20
by the decompressor. This is because the actual slope of TS (after =
scaling)
equals the default-slope. Of course, the TS_STRIDE =3D 3000 must be=20
synchronized also, which can be done within the same packet.=20

Example 2 is different. The actual slope (=3D 0) of scaled TS does not =
equal
the default-slope (=3D 1). Therefore, during the first string of the =
packet=20
stream, the compressor has to ensure that two packets carrying TS info
have been correctly decompressed by the decompressor. This allows the
decompressor to establish both the slope and offset for function from
SN to scaled TS. However, for subsequent strings, only one correctly
decompressed packet is needed since slope =3D 0 has already been =
established
and thus can be reused.
--------------------------------------------------------------------

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


From rohc-bounces@ietf.org  Thu Dec  2 18:24:00 2004
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 SAA13597
	for <rohc-web-archive@ietf.org>; Thu, 2 Dec 2004 18:24:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ca0OT-0002J5-A1
	for rohc-web-archive@ietf.org; Thu, 02 Dec 2004 18:29:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZyyj-0001ye-GK; Thu, 02 Dec 2004 16:59:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZyT5-00040g-TV
	for rohc@megatron.ietf.org; Thu, 02 Dec 2004 16:26:27 -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 QAA00817
	for <rohc@ietf.org>; Thu, 2 Dec 2004 16:26:25 -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 1CZyYe-0007aB-91
	for rohc@ietf.org; Thu, 02 Dec 2004 16:32:15 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iB2LQDvL022452; Thu, 2 Dec 2004 22:26:14 +0100 (MET)
In-Reply-To: <7B5AF06E216CB74DA8A5960A3181B5B82891B7@ajebe001.americas.nokia.com>
References: <7B5AF06E216CB74DA8A5960A3181B5B82891B7@ajebe001.americas.nokia.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <CB699B02-44A8-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, 2 Dec 2004 22:26:14 +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: 287c806b254c6353fcb09ee0e53bbc5e
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, rohc@ietf.org,
        ghyslain.pelletier@ericsson.com, 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: 36c793b20164cfe75332aa66ddb21196
Content-Transfer-Encoding: 7bit

> As it is described in section 4.5.3 and other places in RFC
> 3095, TS_STRIDE is the factor by which an RTP Timestamp is
> downscaled before compression. Obviously, it cannot be 0 (zero).

Well, zero is not exactly prohibited, but then you couldn't send any 
other value than TS_OFFSET, which wouldn't be too useful.

> The wording of TS_STRIDE definition in section 2 is confusing
> and may be incorrectly interpreted as TS_STRIDE is always equal
> to the increase in TS value between two RTP packets with
> consecutive sequence number. This is not the intent of the
> specification. It is the compressor that decides whether TS
> scaling should be used and if yes, what is the best value of
> TS_STRIDE. See section 4.5.3 for information. How this is done
> is an implementation issue. However, an implementation must follow
> section 4.5.3, 4.5.6 and 5.7 on how to initialize, encode, and
> synchronize TS_STRIDE between the compressor and decompressor.

I hope we are all in agreement about this.

> Note: TS_STRIDE is not the same as slope described in section
> 5.5.1.2 and 5.7. Here, slope has the general meaning in mathematics.
> Namely, slope(X) equals the change of a non-SN field X between
> two packets divided by the change of SN field between the same
> two packets. It is one of the two parameters (the other one
> being offset) that define a linear function from SN to field X.
> The concept can also be visualized as a line, with SN being
> the horizontal coordinate and the field X being the vertical
> coordinate. For TS, this applies regardless whether it is scaled
> or not. In case the TS is scaled, the linear function (or equivalently
> its slope and offset) is from SN to the TS_SCALED.

This is the msg934 dynamic slope.

In 3095, some of this shines through in the description of R-mode, but 
in no other place.

I believe we are split between:
-- This is a mistake in the R-mode text
-- msg934 slopes only apply to R-mode (one quite logical conclusion 
from the text of 3095)
-- msg934 slopes apply to all headers that do not send a timestamp.

In the latter two cases some text from msg934 or equivalent would need 
to be retrofitted to the standard.

> Note: it should be clear from section 4.5.3 that when scale is
> used for TS, two steps are involved: 1) downscale of the
> original TS to TS_SCALED; and 2) compression of TS_SCALED.

Again, I hope we all agree on this part.

> The decompressor follows the reverse procedure with two steps.
> Following are two examples to further illustrate this.
>
> Example 1 (audio stream with TS_STRIDE = 160):
>
>             <------ String 1 ------>    <-- String 2 --->
> SN           11  12  13  14 ...   60    61    62    63 ...
> TS          200 360 420 580 ... 8040 16040 16200 16360 ...
> TS_SCALED     1   2   3   4 ...   50   100   101   102 ...
> TS_OFFSET    40  40  40  40       40    40    40    40 ...
> slope       <--------  1 ---------->    <----- 1 ------->
> offset      <-------- (-10)-------->    <----- (39) ---->

The problem with this picture is that it does not identify which of the 
packets are context-updating.
The way I read msg934, the intention of this proposal was to only 
compute slope from the points created by CRC-checked packets.

> Example 2 (video stream with TS_STRIDE = 3000):
>
>             <------ String 1 ------>  <-- String 2 --->
> SN            11   12   13 ...    25   26   27   28 ...
> TS          4000 4000 4000 ...  4000 7000 7000 7000 ...
> TS_SCALED      1    1    1 ...     1    2    2    2 ...
> TS_OFFSET   1000 1000 1000 ...  1000 1000 1000 1000 ...
> slope       <--------  0 ---------->  <----- 0 ------->
> offset      <--------- 1 ---------->  <----- 2 ------->
>
> Note: the default-slope(X) specified in section 5.7 is to be used
> by the compressor and decompressor to initialize the slope of the
> linear function from SN to field X. This is an optimization to
> save synchronization overhead at the beginning of an RTP packet
> stream. Namely, if the actual slope of X in the first string matches
> the default-slope(X), the compressor can enter SO state and send
> Type 0 packets once it is confident that one - instead of two in
> the normal case - packet carrying field(X) has been correctly
> decompressed by the decompressor. This is enough for the decompressor
> to determine the other parameter, i.e. offset, for the linear function
> from SN to X. After the fist string, the decompressor will update the
> linear function from SN to X depending on how many packets carrying
> field(X) have been correctly decompressed.

I'm not sure I understand this sentence.

After SN-60 and SN-61 (assuming both are context-updating), the msg934 
slope is 50.
(If SN-60 is not context-updating and SN-59 and SN-61 are 
context-updating, the slope is 25.
If neither SN-59 nor SN-60 is context-updating and SN-58 and SN-61 are 
context-updating, there is no msg934 slope and you cannot send -0 
headers if you assume msg934.)
Since you don't really know which of these actually arrived (even in 
R-mode, you must wait for the ACKs to arrive, and some these might even 
be lost), it will take a while before it is one again.
This is one of the reasons I'm not a great fan of msg934 slopes.

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Thu Dec  2 18:25:04 2004
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, 2 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


From rohc-bounces@ietf.org  Thu Dec  2 21:44:38 2004
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 VAA29912
	for <rohc-web-archive@ietf.org>; Thu, 2 Dec 2004 21:44:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ca3Wg-0006rY-9R
	for rohc-web-archive@ietf.org; Thu, 02 Dec 2004 21:50:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ca0SA-0004m6-3m; Thu, 02 Dec 2004 18:33:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZzL2-0006MR-PG
	for rohc@megatron.ietf.org; Thu, 02 Dec 2004 17:22:12 -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 RAA06058
	for <rohc@ietf.org>; Thu, 2 Dec 2004 17:22:10 -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 1CZzQe-0000e9-HX
	for rohc@ietf.org; Thu, 02 Dec 2004 17:28:01 -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
	iB2MM2v02552; Fri, 3 Dec 2004 00:22:04 +0200 (EET)
X-Scanned: Fri, 3 Dec 2004 00:19:22 +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 iB2MJM8N001702;
	Fri, 3 Dec 2004 00:19:22 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks002.ntc.nokia.com 00GtXMgf; Fri, 03 Dec 2004 00:19:21 EET
Received: from daebh001.NOE.Nokia.com (daebh001.americas.nokia.com
	[10.241.35.121])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iB2MJEa03729; Fri, 3 Dec 2004 00:19:14 +0200 (EET)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by
	daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Thu, 2 Dec 2004 16:18:14 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] The discussion on slope(s)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Thu, 2 Dec 2004 17:18:12 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B82891B8@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] The discussion on slope(s)
Thread-Index: AcTYTmX+BasxjL9OQtaDUqRk7EpqDgAY0Www
To: <kristofer.sandlund@effnet.com>
X-OriginalArrivalTime: 02 Dec 2004 22:18:14.0592 (UTC)
	FILETIME=[D10C6C00:01C4D8BC]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: quoted-printable
Cc: cabo@tzi.org, rohc@ietf.org, 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.3 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: quoted-printable

> http://www1.ietf.org/mail-archive/web/rohc/current/msg02081.html
> (the last one included questions to Zhigang, which were ignored)

Kristofer,

Lars-Erik pointed out that I didn't reply to your questions
(copied below) in the above email. Sorry about that. I probably=20
missed them. Handing that many emails were not easy for me.

Short answers: section 4.5.3 is correct. The definition of
TS_STRIDE in section 2 is wrong.

Long answers. ROHC works at RTP packet level. That's for sure.
What section 4.5.3 says is that for video, you can still
scale the TS by TS_STRIDE (see example below). The mentioning=20
of "frame delta" is to explain why and give reminder about
the special "ladder" characteristics of TS in video.

            <------ String 1 ------>  <-- String 2 --->
SN            11   12   13 ...    25   26   27   28 ...
TS          4000 4000 4000 ...  4000 7000 7000 7000 ...=20
TS_SCALED      1    1    1 ...     1    2    2    2 ...
TS_OFFSET   1000 1000 1000 ...  1000 1000 1000 1000 ...=20
slope       <--------  0 ---------->  <----- 0 ------->
offset      <--------- 1 ---------->  <----- 2 ------->

RE the definition of TS_STRIDE, it was probably written
with audio context - the most important application of
ROHC. But it's not generic enough to cover video.

Another note: TS scaling is optional. Of course, scaling=20
by a factor of 1 is equivalent to no scaling.

BR, Zhigang

--------------------------------------------------------------------
Ok, now I see one reason that we both base ourselves on the spec but =
reach opposite conclusions.
This example in 4.5.3 actually explains your thinking:

In the case of video, there is usually a TS_STRIDE as well when the
video frame level is considered. The sample rate for most video
codecs is 90 kHz. If the video frame rate is fixed, say, to 30
frames/second, the TS will increase by n * 3000 (=3D n * 90000 / 30)
between video frames. Note that a video frame is often divided into
several RTP packets to increase robustness against packet loss. In
this case several RTP packets will carry the same TS.

That is a contradiction of 2.0:

Timestamp stride

The timestamp stride (TS_STRIDE) is the expected increase in the
timestamp value between two RTP packets with consecutive sequence
numbers.

4.5.3 talks about stride as the "frame delta" and 2.0 as the "packet =
delta".
So yes, if 4.5.3 "overrides" 2.0 then you're right that the stride =
cannot be 0, and then I can see why you think I'm silly to say we must =
define modulus 0. But if 2.0 overriders 4.5.3, then I still think I'm =
right.
That's one quite fundamental difference.

So, one is wrong. Which one?
-----------------------------------------------------------------

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


From rohc-bounces@ietf.org  Thu Dec  2 22:10:41 2004
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 WAA02536
	for <rohc-web-archive@ietf.org>; Thu, 2 Dec 2004 22:10:41 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ca3vt-0007c3-Ep
	for rohc-web-archive@ietf.org; Thu, 02 Dec 2004 22:16:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ca0bX-0006tq-R4; Thu, 02 Dec 2004 18:43:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ca08B-0005xY-BZ
	for rohc@megatron.ietf.org; Thu, 02 Dec 2004 18:12:59 -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 SAA12120
	for <rohc@ietf.org>; Thu, 2 Dec 2004 18:12:56 -0500 (EST)
Received: from mother.ludd.ltu.se ([130.240.16.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ca0Dn-000227-E6
	for rohc@ietf.org; Thu, 02 Dec 2004 18:18:48 -0500
Received: from jymden (jymden.campus.luth.se [130.240.198.36])
	by mother.ludd.ltu.se (8.12.10+Sun/8.12.10) with SMTP id iB2NCmtx011601;
	Fri, 3 Dec 2004 00:12:52 +0100 (MET)
Message-ID: <00de01c4d8c4$dfb6df30$24c6f082@jymden>
From: "Lars-Erik Jonsson" <larsman@home.se>
To: <zhigang.c.liu@nokia.com>, <lars-erik.jonsson@ericsson.com>,
        <cabo@tzi.org>
References: <7B5AF06E216CB74DA8A5960A3181B5B82891B6@ajebe001.americas.nokia.com>
Subject: Re: [rohc] The discussion on slope(s)
Date: Fri, 3 Dec 2004 00:15:52 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit
Cc: rohc@ietf.org, 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: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit

> > http://www1.ietf.org/mail-archive/web/rohc/current/msg02081.html
> > (the last one included questions to Zhigang, which were ignored)
>
> I probably missed Kristofer's email. 

Well, you answered, but not to the questions he asked.
 
> > Finally, I would like to send a direct appeal to Zhigang, as a
> > comment on yesterday's mail on this subject:
> > 
> > > ZL:
> > > I think it's fair to also look at the arguments that dynamic
> > > (or learned or implicit) slopes are in 3095. I have given some
> > > back in March/April. Below is one of them. If I have to summarize
> > > in one sentence, the argument is that if dynamic slopes are not
> > > in 3095, many text (some are essential to encoding) wouldn't 
> > > make sense without twisting hard the meaning of words.
> > > http://www1.ietf.org/mail-archive/web/rohc/current/msg02101.html
> >
> > Can you then list these parts, please cut and paste the sentences
> > in an e-mail, do not use references. 
>
> I thought providing a link is a better way than resending the same
> email. But I'll do it as you wish.

I did not ask for the same "clarification" you had already provided
for the slope approach, but rather for all these text parts of 3095
that you say would have to be twisted hard if there was no slope.

/L-E


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


From rohc-bounces@ietf.org  Fri Dec  3 00:59:58 2004
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 AAA14605
	for <rohc-web-archive@ietf.org>; Fri, 3 Dec 2004 00:59:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ca6Zm-0002cF-4Q
	for rohc-web-archive@ietf.org; Fri, 03 Dec 2004 01:05:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ca3uL-0008KV-Eo; Thu, 02 Dec 2004 22:14:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ca1b1-0004nL-S3
	for rohc@megatron.ietf.org; Thu, 02 Dec 2004 19:46:51 -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 TAA20813
	for <rohc@ietf.org>; Thu, 2 Dec 2004 19:46:48 -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 1Ca1ge-0004Go-TH
	for rohc@ietf.org; Thu, 02 Dec 2004 19:52:41 -0500
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iB30kgv00765; Fri, 3 Dec 2004 02:46:43 +0200 (EET)
X-Scanned: Fri, 3 Dec 2004 02:45:57 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id iB30jveY015390;
	Fri, 3 Dec 2004 02:45:57 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 00I7jcDU; Fri, 03 Dec 2004 02:45:56 EET
Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com
	[10.241.35.122])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iB30jsa10064; Fri, 3 Dec 2004 02:45:54 +0200 (EET)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by
	daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Thu, 2 Dec 2004 18:45:53 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] The discussion on slope(s)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Thu, 2 Dec 2004 19:45:52 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B82891BA@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] The discussion on slope(s)
Thread-Index: AcTYtfwk9gc50plbQpGSrLaJQS9/9QACTxgQ
To: <cabo@tzi.org>
X-OriginalArrivalTime: 03 Dec 2004 00:45:53.0945 (UTC)
	FILETIME=[71A26890:01C4D8D1]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Content-Transfer-Encoding: quoted-printable
Cc: rohc@ietf.org, ghyslain.pelletier@ericsson.com,
        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.3 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Content-Transfer-Encoding: quoted-printable

Carsten,

> > As it is described in section 4.5.3 and other places in RFC
> > 3095, TS_STRIDE is the factor by which an RTP Timestamp is
> > downscaled before compression. Obviously, it cannot be 0 (zero).
>=20
> Well, zero is not exactly prohibited, but then you couldn't send any=20
> other value than TS_OFFSET, which wouldn't be too useful.

A zero TS_STRIDE would also make section 4.5.3 look weird. For example,=20
"it compresses the downscaled values: TS_SCALED =3D TS / TS_STRIDE."

> > Example 1 (audio stream with TS_STRIDE =3D 160):
> >
> >             <------ String 1 ------>    <-- String 2 --->
> > SN           11  12  13  14 ...   60    61    62    63 ...
> > TS          200 360 420 580 ... 8040 16040 16200 16360 ...
> > TS_SCALED     1   2   3   4 ...   50   100   101   102 ...
> > TS_OFFSET    40  40  40  40       40    40    40    40 ...
> > slope       <--------  1 ---------->    <----- 1 ------->
> > offset      <-------- (-10)-------->    <----- (39) ---->
>=20
> The problem with this picture is that it does not identify=20
> which of the packets are context-updating.
> The way I read msg934, the intention of this proposal was to only=20
> compute slope from the points created by CRC-checked packets.

Yes. I re-draw the picture below to make it clear. Also, I corrected
a typo (TS in packet 13). Of course, there are many different scenarios
of context-updating packets or ACKs of them being lost (see below)
I can provide additional examples with detail if needed.

             <------- String 1 -------->    <----- String 2 ------->
SN           11  12  13  14  15 ...   60    61    62    63    64 ...
Ctxt-Update   x   x   x                      x     x     x
TS          200 360 520 680 840 ... 8040 16040 16200 16360 16520 ...
TS_SCALED     1   2   3   4   5 ...   50   100   101   102   103 ...
TS_OFFSET    40  40  40  40  40 ...   40    40    40    40    40 ...
slope       <-----------  1 ----------->    <---------- 1 --------->
offset      <----------- (-10)--------->    <--------- (39) ------->


> > After the fist string, the decompressor will update the
> > linear function from SN to X depending on how many packets carrying
> > field(X) have been correctly decompressed.
>=20
> I'm not sure I understand this sentence.
>
> After SN-60 and SN-61 (assuming both are context-updating),=20
> the msg934 slope is 50.

In the above example, the compressor wouldn't send SN-60 as
context-updating (CU) packet, since its TS_SCALED still conforms=20
to the linear pattern. The compressor would send SN-61 as CU
since it's the one that breaks TS_SCALED pattern. For packets=20
after SN-61, the compressor can have different options as follows
(basically text in section 5.5.1.2 of 3095):
1) Send all of them as CU until receiving two ACKs.
2) Send some of them as CU while others non-CU, until receiving two =
ACKs.
3) In this example, since the slope(String 1) =3D slope(String 2),
the compressor can be "lazy" by doing either 1 or 2, but just waiting=20
for one ACK before sending -0 packets.

Now the decompressor side:
- When it receives the first CU after -0 packets, it knows a
new string begins.
- If it received and ACKed only one CU before receiving another -0=20
packet, it knows compressor is in case 3 above, which means
slope(String 2) =3D slope(String 1). It decompress -0 accordingly.
- Else, the decompressor knows the compressor is in case 1 or 2.=20
Calculate the slope using the last two CUs that have been ACKed.

> Since you don't really know which of these actually arrived (even in=20
> R-mode, you must wait for the ACKs to arrive, and some these=20
> might even  be lost),=20
> it will take a while before it is one again.
> This is one of the reasons I'm not a great fan of msg934 slopes.

But msg934 slope does not add much delay, since at least one CU packet=20
is needed anyway to synchronize the offset.

a) if the slope of TS_SCALED is always equal to the default-slope,=20
then msg934 slope also means one CU is needed. Same result.

b) Else, the new slope has to communicated to the decompressor.
Now, if we follow msg934, two CUs are needed. For R-mode, it means
RTT + another ACK (say compressor takes option 1). For UO-mode,=20
it means L+1 CU packets need to be sent. The difference is just=20
one packet.

Furthermore, for case b), I still need to see how exactly it would work=20
without msg934.=20

BR, Zhigang


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


From rohc-bounces@ietf.org  Fri Dec  3 05:38:07 2004
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 FAA20144
	for <rohc-web-archive@ietf.org>; Fri, 3 Dec 2004 05:38:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaAuw-0008AN-LS
	for rohc-web-archive@ietf.org; Fri, 03 Dec 2004 05:44:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ca9M6-000497-8m; Fri, 03 Dec 2004 04:03:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ca7tO-00005O-Do
	for rohc@megatron.ietf.org; Fri, 03 Dec 2004 02:30:14 -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 CAA05501
	for <rohc@ietf.org>; Fri, 3 Dec 2004 02:30:13 -0500 (EST)
Received: from [194.237.235.30] (helo=effnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ca7z4-0004NG-Aq
	for rohc@ietf.org; Fri, 03 Dec 2004 02:36:07 -0500
Received: from effnet.com (c-b97c71d5.04-205-6c756c1.cust.bredbandsbolaget.se
	[213.113.124.178]) (authenticated bits=0)
	by effnet.com (8.12.3/8.12.3) with ESMTP id iB36T1Lh015045
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Fri, 3 Dec 2004 07:29:02 +0100
Message-ID: <41B01747.6050801@effnet.com>
Date: Fri, 03 Dec 2004 08:35:35 +0100
From: Kristofer Sandlund <kristofer.sandlund@effnet.com>
Organization: Effnet
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] The discussion on slope(s)
References: <A943FD84BD9ED41193460008C7918050072E99B5@ESEALNT419.al.sw.ericsson.se>
	<41AF25BE.2090203@effnet.com>
	<6E745528-4483-11D9-951E-000A95DC4DB6@tzi.org>
In-Reply-To: <6E745528-4483-11D9-951E-000A95DC4DB6@tzi.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: rohc@ietf.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.1 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit



Carsten Bormann wrote:
>> 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.)
> 

Yes, of course the update packet itself has a CRC. But the slope value is not 
transmitted, it is inferred based on timestamp history so it is not covered by 
that CRC. So, maybe I should have spelled that out, but I figured that should 
have been clear from earlier discussions.

> 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.

Exactly what I meant.

/Kristofer

> 
> Gruesse, Carsten

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


From rohc-bounces@ietf.org  Fri Dec  3 13:11:53 2004
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 NAA12045
	for <rohc-web-archive@ietf.org>; Fri, 3 Dec 2004 13:11:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaHzv-0005kz-5d
	for rohc-web-archive@ietf.org; Fri, 03 Dec 2004 13:17:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaDRn-0001vh-6R; Fri, 03 Dec 2004 08:26:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaCYW-0003uj-5E
	for rohc@megatron.ietf.org; Fri, 03 Dec 2004 07:29:00 -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 HAA28751
	for <rohc@ietf.org>; Fri, 3 Dec 2004 07:28:59 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaCeA-0001r9-Ge
	for rohc@ietf.org; Fri, 03 Dec 2004 07:34:56 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iB3CSrh5013451
	for <rohc@ietf.org>; Fri, 3 Dec 2004 13:28:53 +0100 (MET)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 3 Dec 2004 13:28:52 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <XVCVPBLR>; Fri, 3 Dec 2004 13:28:52 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E99C2@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'Kristofer Sandlund'" <kristofer.sandlund@effnet.com>,
        "Ghyslain Pelletier (LU/EAB)" <ghyslain.pelletier@ericsson.com>
Subject: RE: [rohc] ROHC-TCP, ack number compression
Date: Fri, 3 Dec 2004 13:28:46 +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 12:28:52.0821 (UTC)
	FILETIME=[A6342050:01C4D933]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: "'West, Mark'" <mark.a.west@roke.co.uk>, Carsten Bormann <cabo@tzi.org>,
        "'rohc@ietf.org'" <rohc@ietf.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.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32

Kristofer,

You've given an excellent summary of this issue.

> I could consider option b), but as I stated, I cannot really 
> estimate the gain, so possibly a) is good enough.

I agree with you that option b) sound like a workable approach,
but I am also unsure about the potential gain. We could of
course include it in any case, as it does not hurt anything
but introducing an additional control parameter that might not
be used. However, personally I would go for the simplest
possible approach a), as I do not see the big gain from adding
an additional mechanism, and I think we should aim at finalizing
ROHC-TCP THIS YEAR (yes, 2004).

If others promote b), I'll accept that, as long as we decide and
move on.

/L-E

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


From rohc-bounces@ietf.org  Fri Dec  3 13:20:31 2004
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 NAA14347
	for <rohc-web-archive@ietf.org>; Fri, 3 Dec 2004 13:20:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaI8G-0006R1-Hh
	for rohc-web-archive@ietf.org; Fri, 03 Dec 2004 13:26:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaEaW-0004lq-FJ; Fri, 03 Dec 2004 09:39:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaDnp-0006EX-3m
	for rohc@megatron.ietf.org; Fri, 03 Dec 2004 08:48:53 -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 IAA04250
	for <rohc@ietf.org>; Fri, 3 Dec 2004 08:48:51 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaDtZ-0003fd-4c
	for rohc@ietf.org; Fri, 03 Dec 2004 08:54:49 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iB3Dmph5002582
	for <rohc@ietf.org>; Fri, 3 Dec 2004 14:48:51 +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 14:48:50 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <XVCVPWHG>; Fri, 3 Dec 2004 14:48:50 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E99C4@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: rohc@ietf.org
Subject: RE: [rohc] The discussion on slope(s)
Date: Fri, 3 Dec 2004 14:48:44 +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 13:48:50.0777 (UTC)
	FILETIME=[D2021C90:01C4D93E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
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: 5a9a1bd6c2d06a21d748b7d0070ddcb8

> > > As it is described in section 4.5.3 and other places in RFC
> > > 3095, TS_STRIDE is the factor by which an RTP Timestamp is
> > > downscaled before compression. Obviously, it cannot be 0 (zero).
> > 
> > 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.

> A zero TS_STRIDE would also make section 4.5.3 look weird. 
> For example, "it compresses the downscaled values:
> TS_SCALED = TS / TS_STRIDE."

Yes, this formula should be replaced by the actual scaling
formula: TS = TS_SCALED * TS_STRIDE + TS_OFFSET

The TS_SCALED = TS / TS_STRIDE formula is not really good in any
case, since with an undefined "/", it could be interpretred as if
it generates a TS_SCALED that is not necessarily an integer number.  


> > > After the fist string, the decompressor will update the
> > > linear function from SN to X depending on how many 
> > > packets carrying field(X) have been correctly decompressed.
> > 
> > I'm not sure I understand this sentence.
> >
> > After SN-60 and SN-61 (assuming both are context-updating), 
> > the msg934 slope is 50.
> 
> In the above example, the compressor wouldn't send SN-60 as
> context-updating (CU) packet, since its TS_SCALED still conforms 
> to the linear pattern. 

So, you mean that you would have to force the compressor not to
send updating packets to avoid the slope being accidentially
updated? There are other reasons for sending updating packets
than to establish an implicit slope, the periodic R-0-CRC for
SN update, for example.

I still miss the full logic for how a new slope is established at
the decompressor, as well as all the rules the compressor will
have to follow to ensure it makes the correct assumptions for
which slope is established at the decompressor, and (maybe most
important) how the compressor ensures it does not accidentially
makes the decompressor update the slope. A complete picture for
all modes would be very interesting (or maybe terrifying) to see.

/L-E

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


From rohc-bounces@ietf.org  Fri Dec  3 13:35:15 2004
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 NAA16917
	for <rohc-web-archive@ietf.org>; Fri, 3 Dec 2004 13:35:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaIMX-0007E5-Vo
	for rohc-web-archive@ietf.org; Fri, 03 Dec 2004 13:41:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaFIs-0004iG-8E; Fri, 03 Dec 2004 10:25:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaEnA-00079r-Us
	for rohc@megatron.ietf.org; Fri, 03 Dec 2004 09:52:17 -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 JAA11745
	for <rohc@ietf.org>; Fri, 3 Dec 2004 09:52:15 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaEsu-0005IH-DD
	for rohc@ietf.org; Fri, 03 Dec 2004 09:58:14 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iB3EqDh5017663
	for <rohc@ietf.org>; Fri, 3 Dec 2004 15:52:13 +0100 (MET)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 3 Dec 2004 15:52:13 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <XVCVQKBB>; Fri, 3 Dec 2004 15:52:13 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E99C9@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'zhigang.c.liu@nokia.com'" <zhigang.c.liu@nokia.com>, cabo@tzi.org
Subject: RE: [rohc] The discussion on slope(s)
Date: Fri, 3 Dec 2004 15:52:09 +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 14:52:13.0574 (UTC)
	FILETIME=[ACA6E260:01C4D947]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Cc: rohc@ietf.org,
        "Ghyslain Pelletier \(LU/EAB\)" <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: b132cb3ed2d4be2017585bf6859e1ede

> > 1) What was discussed during the development of 3095 in 1999-2000?
> 
> I've provided emails on ROHC mailing list where Mickael and I 
> discussed about the synchronization of the slope. The conclusion
> was  that compression starts with default-slope and then use
> "learned slope" if default-slope is not good. Video example
> was discussed as one reason for that. It was also clear that
> slope is a separate concept from TS_STRIDE, which is a scale
> factor.

Yes, a few e-mails were found that discussed this conceptually,
but, as also reflected in RFC 3095, all the details needed to
potentially get this to work was not at all nailed down. What can
be found in the archives does not make it clear what the actual
outcome was, as is also reflected in 3095 where "slope-ing" was
never really defined.


> 2) What was 3095 intended to say, back in 2000?
> 
> Above was what 3095 intended to say, in my opinion.

My conclusion is that there was no consistent consensus on
this issue, and the details were never worked out.


> 3) What is 3095 really saying?
> 
> As result of above and other discussions:
> 
> - Section 3.4 describe the function from SN to other fields X.

Yes, and scaling forms the SN-to-TS function through TS_STRIDE
(explicit) and TS_OFFSET (implicit). No mentioning of any 
implicitly learned slope.

> - Section 4.3.1.3 describes the function SN->X and SO state.

Yes, the "other fields based on SN"-principle is mentioned here,
but nothing about any implicitly learned slope.

> - Section 4.5.3 defines the scaling of TS before compression.
> Note: scaling and thus TS_STRIDE is optional. While WLSB is
> not. Neither is SO state. It should be self-evident that
> TS_STRIDE is not the slope.

If there is no function defined, there is no function, that's it.
No mentioning of implicitly learned slopes here either.

> - Section 5.2.7 describes the function SN->X and packet types/formats.

There is nothing here that talks about implicitly learned slopes.
E.g. the Packet type 2 text rather indicates that functions are
established explicitly, e.g. with UOR-2.

> - Section 5.5.1.2 describes the slope

This is the only place where slope is actually mentioned, and this
is an R-mode section only. This is the only part one can interpret
as if there was a generally applicable slope concept, but nothing
talks about implicit methods to establish parameters. One can rather
interpret this as a way to generally describe functions like the
TS scaling method, which is the only method that is defined to
use an implicitly established parameter.

> - Section 5.7 defines the value of default-slope.

Yes, and without any definition of either slope or default_slope,
this just creates confusion.
 

> 4) How can 3095 be interpreted?

As you use to say, "I get speechless". Do you really mean that
you think the text pieces in 3095 defines implicitly learned
slopes and all the principles needed to get this to work and
interoperate?


> 5) Now 2004, which solution do we think makes most sense, technically?
> 
> I'm a bit confused, and this is the difficulty I have. What is the
> question in this discussion: a) learned slope or even slope doesn't
> ever exist in 3095? b) even if it exists, we can re-evaluate and 
> decide to remove it (what is implied above)?

What is implied is that whatever we do, we must ensure we have 
an understanding of the alternatives we are discussing. It is clear
that the RFC is ambiguous and in practice impossible to create
interoperable implementations from. Considering that what is actually
in the RFC is the basis we will build on, not the ideas from some
authors that were never nailed down and thus not captured in the RFC,
what we technically think about the alternatives today and their
relation to what is described in 3095 will indeed be very important
when deciding on what elaboration/clarification to provide to
implementers.


> 6) Now 2004, which solution would make most sense if we consider 3)?
> 
> See above.

Considering the complexity of the implicitly learned slope mechanism,
the fact that it does not at all exist in 3095, it seems like most
people agree it is not what we should now add to 3095 profiles.
 

> 7) How do we realize 6) in the implementers guide to ensure 
> interoperability?
> 
> I think we haven't reached this yet.

Agree, but we seem to be going towards defining two different
proposals, and that might help in deciding upon 6).

/L-E

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


From rohc-bounces@ietf.org  Fri Dec  3 13:36:43 2004
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, 3 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


From rohc-bounces@ietf.org  Fri Dec  3 14:28:02 2004
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 OAA24850
	for <rohc-web-archive@ietf.org>; Fri, 3 Dec 2004 14:28:01 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaJBp-0001E1-HT
	for rohc-web-archive@ietf.org; Fri, 03 Dec 2004 14:34:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaIMb-0002bO-KG; Fri, 03 Dec 2004 13:41:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaGAo-000702-85
	for rohc@megatron.ietf.org; Fri, 03 Dec 2004 11:20:46 -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 LAA21501
	for <rohc@ietf.org>; Fri, 3 Dec 2004 11:20:44 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaGGY-0007Xf-9u
	for rohc@ietf.org; Fri, 03 Dec 2004 11:26:43 -0500
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iB3GKUb17708; Fri, 3 Dec 2004 18:20:31 +0200 (EET)
X-Scanned: Fri, 3 Dec 2004 18:20:55 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks001.ntc.nokia.com (8.12.9/8.12.9) id iB3GKtVu008990;
	Fri, 3 Dec 2004 18:20:55 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks001.ntc.nokia.com 004DYxam; Fri, 03 Dec 2004 18:20:55 EET
Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com
	[10.241.35.122])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iB3GGua22908; Fri, 3 Dec 2004 18:16:56 +0200 (EET)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by
	daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Fri, 3 Dec 2004 10:16:28 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] The discussion on slope(s)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Fri, 3 Dec 2004 11:16:27 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B82891BB@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] The discussion on slope(s)
Thread-Index: AcTYxuLHvMupq0MBRHqP/j72iV0rHQAiBDEg
To: <larsman@home.se>, <cabo@tzi.org>, <kristofer.sandlund@effnet.com>
X-OriginalArrivalTime: 03 Dec 2004 16:16:28.0615 (UTC)
	FILETIME=[71B0ED70:01C4D953]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: quoted-printable
Cc: rohc@ietf.org, 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.3 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: quoted-printable

> > > http://www1.ietf.org/mail-archive/web/rohc/current/msg02081.html
> > > (the last one included questions to Zhigang, which were ignored)
> >
> > I probably missed Kristofer's email.=20
>=20
> Well, you answered, but not to the questions he asked.

Lars-Erik,

Which questions I didn't answer?

BR, Zhigang

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


From rohc-bounces@ietf.org  Fri Dec  3 14:30:21 2004
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 OAA25398
	for <rohc-web-archive@ietf.org>; Fri, 3 Dec 2004 14:30:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaJE6-0001MH-6h
	for rohc-web-archive@ietf.org; Fri, 03 Dec 2004 14:36:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaIXl-0007Rc-2i; Fri, 03 Dec 2004 13:52:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaGYy-0002Si-Lq
	for rohc@megatron.ietf.org; Fri, 03 Dec 2004 11:45:44 -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 LAA23918
	for <rohc@ietf.org>; Fri, 3 Dec 2004 11:45:42 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaGek-0008GI-9d
	for rohc@ietf.org; Fri, 03 Dec 2004 11:51:42 -0500
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iB3GjXb16601; Fri, 3 Dec 2004 18:45:34 +0200 (EET)
X-Scanned: Fri, 3 Dec 2004 18:49:03 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks001.ntc.nokia.com (8.12.9/8.12.9) id iB3Gn31o032292;
	Fri, 3 Dec 2004 18:49:03 +0200
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks001.ntc.nokia.com 00WetcOV; Fri, 03 Dec 2004 18:49:01 EET
Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com
	[10.241.35.122])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iB3Gj3S18835; Fri, 3 Dec 2004 18:45:04 +0200 (EET)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by
	daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Fri, 3 Dec 2004 10:45:02 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] The discussion on slope(s)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Fri, 3 Dec 2004 11:45:01 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B82891BC@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] The discussion on slope(s)
Thread-Index: AcTZR+DnrKiz11MWTReMC9D306Sg9QADG/Cg
To: <lars-erik.jonsson@ericsson.com>, <cabo@tzi.org>
X-OriginalArrivalTime: 03 Dec 2004 16:45:02.0975 (UTC)
	FILETIME=[6F8780F0:01C4D957]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Content-Transfer-Encoding: quoted-printable
Cc: rohc@ietf.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: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: quoted-printable

Lars-Erik,

Could you walk me through the two examples I gave in my email below,
and tell me exactly how ROHC should work in your opinion, step-by-step?

http://www1.ietf.org/mail-archive/web/rohc/current/msg02101.html

BR, Zhigang

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


From rohc-bounces@ietf.org  Fri Dec  3 15:05:59 2004
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 PAA00818
	for <rohc-web-archive@ietf.org>; Fri, 3 Dec 2004 15:05:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaJmZ-0002yr-V6
	for rohc-web-archive@ietf.org; Fri, 03 Dec 2004 15:12:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaJPo-00089U-VV; Fri, 03 Dec 2004 14:48:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaIuF-0003H9-Nu
	for rohc@megatron.ietf.org; Fri, 03 Dec 2004 14:15:51 -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 OAA23180
	for <rohc@ietf.org>; Fri, 3 Dec 2004 14:15:50 -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 1CaJ01-0000iI-Rh
	for rohc@ietf.org; Fri, 03 Dec 2004 14:21:51 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iB3JFcAm004270; Fri, 3 Dec 2004 20:15:39 +0100 (MET)
In-Reply-To: <A943FD84BD9ED41193460008C7918050072E99C9@ESEALNT419.al.sw.ericsson.se>
References: <A943FD84BD9ED41193460008C7918050072E99C9@ESEALNT419.al.sw.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <B7E6C657-455F-11D9-951E-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] The discussion on slope(s)
Date: Fri, 3 Dec 2004 20:15:39 +0100
To: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.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: 08170828343bcf1325e4a0fb4584481c
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>
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: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit

> My conclusion is that there was no consistent consensus on
> this issue, and the details were never worked out.

I still think it is worthwhile to spend some time on this list to 
figure out what slope *could* have been if we had done the work in 
2000.
 From what I've seen so far I'm not even convinced it would have been a 
win.

So, please let's continue the discussion about Zhigang's example and 
flesh it out with things like actual header types for each of the 
modes.

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Fri Dec  3 15:57:55 2004
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 PAA05827
	for <rohc-web-archive@ietf.org>; Fri, 3 Dec 2004 15:57:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaKap-0004lp-Sp
	for rohc-web-archive@ietf.org; Fri, 03 Dec 2004 16:03:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaKN1-0007r9-JN; Fri, 03 Dec 2004 15:49:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaKFu-00056U-AQ
	for rohc@megatron.ietf.org; Fri, 03 Dec 2004 15:42:18 -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 PAA04790
	for <rohc@ietf.org>; Fri, 3 Dec 2004 15:42:16 -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 1CaKLh-0004Gv-Rp
	for rohc@ietf.org; Fri, 03 Dec 2004 15:48:18 -0500
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iB3Kg8v24944; Fri, 3 Dec 2004 22:42:09 +0200 (EET)
X-Scanned: Fri, 3 Dec 2004 22:39:18 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id iB3KdI3V018946;
	Fri, 3 Dec 2004 22:39:18 +0200
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks004.ntc.nokia.com 00ZOJ7ur; Fri, 03 Dec 2004 22:39:17 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
	iB3KdBS20987; Fri, 3 Dec 2004 22:39: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); 
	Fri, 3 Dec 2004 14:39:09 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] The discussion on slope(s)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Fri, 3 Dec 2004 15:39:08 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B82891BE@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] The discussion on slope(s)
Thread-Index: AcTZJIO7pp4qNpI6R4OisGKMn261JgAOV1tg
To: <kristofer.sandlund@effnet.com>, <cabo@tzi.org>
X-OriginalArrivalTime: 03 Dec 2004 20:39:09.0269 (UTC)
	FILETIME=[23C5E050:01C4D978]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: quoted-printable
Cc: rohc@ietf.org, ghyslain.pelletier@ericsson.com,
        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.3 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: quoted-printable

> Yes, of course the update packet itself has a CRC. But the slope value =
is not=20
> transmitted, it is inferred based on timestamp history so it is not =
covered by=20
> that CRC.=20

Kristofer,

An undetected error in an update packet can cause the decompressor=20
to derive an incorrect slope. But the problem is the undetected error,=20
not the slope. That is because the same error can happen in any
transmitted header fields and parameters (e.g. SN, TS, TS_STRIDE)
that will cause context damage and error propagation.

To expand this. When TS breaks its change pattern (i.e. the function=20
TS =3D SN * slope + offset), at least one update packet needs to be =
sent.=20
(Actually, if new slope is same as default-slope, one update packet is=20
enough.) If an undetected error happens in SN or TS of that packet, the=20
function will be incorrect, no matter how you establish slope on the=20
decompressor side.

The issue of undetected (or residual) errors has been discussed heavily
when we developed 3095. Actually, that is one of the core issues.
Text in section 2, 4.6, 4.7 covers the subject.

Also, I'm a bit curious: have you implemented R-mode? If yes, how =
section=20
5.5.1.2 of 3095 was implemented?

BR, Zhigang


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


From rohc-bounces@ietf.org  Fri Dec  3 18:25:33 2004
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 SAA19801
	for <rohc-web-archive@ietf.org>; Fri, 3 Dec 2004 18:25:33 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaMtk-0000Yj-TX
	for rohc-web-archive@ietf.org; Fri, 03 Dec 2004 18:31:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaMjx-0005uy-8H; Fri, 03 Dec 2004 18:21:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaMPb-0006zt-2T
	for rohc@megatron.ietf.org; Fri, 03 Dec 2004 18:00:27 -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 SAA17087
	for <rohc@ietf.org>; Fri, 3 Dec 2004 18:00:24 -0500 (EST)
Received: from mother.ludd.ltu.se ([130.240.16.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaMVP-0008Rs-LE
	for rohc@ietf.org; Fri, 03 Dec 2004 18:06:28 -0500
Received: from jymden (jymden.campus.luth.se [130.240.198.36])
	by mother.ludd.ltu.se (8.12.10+Sun/8.12.10) with SMTP id iB3N0Etx011394;
	Sat, 4 Dec 2004 00:00:18 +0100 (MET)
Message-ID: <005b01c4d98c$5b405c90$24c6f082@jymden>
From: "Lars-Erik Jonsson" <larsman@home.se>
To: "Carsten Bormann" <cabo@tzi.org>,
        "Lars-Erik Jonsson \(LU/EAB\)" <lars-erik.jonsson@ericsson.com>
References: <A943FD84BD9ED41193460008C7918050072E99C9@ESEALNT419.al.sw.ericsson.se>
	<B7E6C657-455F-11D9-951E-000A95DC4DB6@tzi.org>
Subject: Re: [rohc] The discussion on slope(s)
Date: Sat, 4 Dec 2004 00:03:48 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, rohc@ietf.org,
        "Ghyslain Pelletier \(LU/EAB\)" <ghyslain.pelletier@ericsson.com>,
        zhigang.c.liu@nokia.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: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit

Feel free to try to figure out how to get a scheme with an implicitly
learned slope robust and interoperable. Personally, I think this is a
concept that just creates troubles, but if someone can really define it
unambiguously and prove it will work, I will for sure take a look at it.

/L-E


----- Original Message -----
From: "Carsten Bormann" <cabo@tzi.org>
To: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
Cc: <rohc@ietf.org>; "Carsten Bormann" <cabo@tzi.org>;
<zhigang.c.liu@nokia.com>; "Ghyslain Pelletier (LU/EAB)"
<ghyslain.pelletier@ericsson.com>
Sent: Friday, December 03, 2004 8:15 PM
Subject: Re: [rohc] The discussion on slope(s)


> > My conclusion is that there was no consistent consensus on
> > this issue, and the details were never worked out.
>
> I still think it is worthwhile to spend some time on this list to
> figure out what slope *could* have been if we had done the work in
> 2000.
>  From what I've seen so far I'm not even convinced it would have been a
> win.
>
> So, please let's continue the discussion about Zhigang's example and
> flesh it out with things like actual header types for each of the
> modes.
>
> Gruesse, Carsten
>
>
> _______________________________________________
> 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


From rohc-bounces@ietf.org  Sun Dec  5 07:01:34 2004
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 HAA00226
	for <rohc-web-archive@ietf.org>; Sun, 5 Dec 2004 07:01:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CavBG-00057w-2f
	for rohc-web-archive@ietf.org; Sun, 05 Dec 2004 07:07:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cav40-0004lh-Od; Sun, 05 Dec 2004 07:00:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cauz5-0003xg-S1
	for rohc@megatron.ietf.org; Sun, 05 Dec 2004 06:55: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 GAA29942
	for <rohc@ietf.org>; Sun, 5 Dec 2004 06:55:21 -0500 (EST)
Received: from [194.237.235.30] (helo=effnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cav5D-00051E-UJ
	for rohc@ietf.org; Sun, 05 Dec 2004 07:01:44 -0500
Received: from [172.16.0.35] (c83-176-200-103.cust.tele2.se [83.176.200.103])
	(authenticated bits=0)
	by effnet.com (8.12.3/8.12.3) with ESMTP id iB5AsDLh026553
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sun, 5 Dec 2004 11:54:21 +0100
Message-ID: <41B2F702.2090803@effnet.com>
Date: Sun, 05 Dec 2004 12:54:42 +0100
From: Kristofer Sandlund <kristofer.sandlund@effnet.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041115
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: zhigang.c.liu@nokia.com
Subject: Re: [rohc] The discussion on slope(s)
References: <7B5AF06E216CB74DA8A5960A3181B5B82891BE@ajebe001.americas.nokia.com>
In-Reply-To: <7B5AF06E216CB74DA8A5960A3181B5B82891BE@ajebe001.americas.nokia.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: 7bit
Cc: cabo@tzi.org, rohc@ietf.org, ghyslain.pelletier@ericsson.com,
        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: 0fa76816851382eb71b0a882ccdc29ac
Content-Transfer-Encoding: 7bit

Hi Zhigang,

comments inline.

zhigang.c.liu@nokia.com wrote:
>>Yes, of course the update packet itself has a CRC. But the slope value is not 
>>transmitted, it is inferred based on timestamp history so it is not covered by 
>>that CRC. 
> 
> 
> Kristofer,
> 
> An undetected error in an update packet can cause the decompressor 
> to derive an incorrect slope. But the problem is the undetected error, 
> not the slope. That is because the same error can happen in any
> transmitted header fields and parameters (e.g. SN, TS, TS_STRIDE)
> that will cause context damage and error propagation.
> 

In the worst-case example I provided earlier, the problem I was trying 
to point out was NOT the fact that the context _can_ get damaged, which 
I agree can happen at any time because of any field. The problem I was 
pointing out that we get context damage that will NEVER be detected on 
such a stream as I showed. In U/O-mode, context damage will be picked up 
quickly since all packets have a CRC, and in "normal" R-mode, almost as 
quickly (as soon as some context-updating packets arrive). This is what 
sets slope apart from explicit fields. So, my problem with slope is that 
when it is set (in a CRC-carrying packet) it is not used for this 
specific packet (therfore, the setting of the slope is not verified). In 
R-mode, the first time it will be used will (usually) be for a packet 
without a CRC, meaning that the slope itself might actually _never_ be 
verified. The only saviour is the R-0-CRC and there is nothing in the 
spec mandating sending of this specific packet type since a UOR2 could 
be used instead (in the worst-case stream, the compressor HAS to use 
UOR-2s).

Could you please comment on the worst-case mail, since to me this is a 
huge problem. You could (theoretically at least) have a video stream 
running for days in a row, without detecting that the context is damaged.

Also, the second-biggest problem to me is the actual updating of the 
slope (both in U/O and R-mode) and so far, the examples you have 
provided have only dealt with situations where the slope has already 
been set. It would be interesting to see some of this as well.

> To expand this. When TS breaks its change pattern (i.e. the function 
> TS = SN * slope + offset), at least one update packet needs to be sent. 
> (Actually, if new slope is same as default-slope, one update packet is 
> enough.) If an undetected error happens in SN or TS of that packet, the 
> function will be incorrect, no matter how you establish slope on the 
> decompressor side.
> 
> The issue of undetected (or residual) errors has been discussed heavily
> when we developed 3095. Actually, that is one of the core issues.
> Text in section 2, 4.6, 4.7 covers the subject.
>

See my reply above why I think these are two different problems.

> Also, I'm a bit curious: have you implemented R-mode? If yes, how section 
> 5.5.1.2 of 3095 was implemented?
> 

Yes, we have implemented R-mode. But we felt the same as multiple other 
implementers, that the "slope' part of that section was a leftover from 
something that did not make it into the spec since it is not really 
specified and therefore a "bug".

/Kristofer Sandlund, Effnet AB

> BR, Zhigang
> 

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


From rohc-bounces@ietf.org  Mon Dec  6 04:01:04 2004
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 EAA14878
	for <rohc-web-archive@ietf.org>; Mon, 6 Dec 2004 04:01:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbEq8-0005ER-JQ
	for rohc-web-archive@ietf.org; Mon, 06 Dec 2004 04:07:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbEip-00064q-6Z; Mon, 06 Dec 2004 03:59:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbEdu-0005VF-6r
	for rohc@megatron.ietf.org; Mon, 06 Dec 2004 03:54:50 -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 DAA14550
	for <rohc@ietf.org>; Mon, 6 Dec 2004 03:54:48 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbEkE-00050r-6p
	for rohc@ietf.org; Mon, 06 Dec 2004 04:01:22 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iB68smh5009520
	for <rohc@ietf.org>; Mon, 6 Dec 2004 09:54:48 +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); 
	Mon, 6 Dec 2004 09:54:48 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <XVCV766A>; Mon, 6 Dec 2004 09:54:48 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E99D7@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'zhigang.c.liu@nokia.com'" <zhigang.c.liu@nokia.com>, cabo@tzi.org
Subject: RE: [rohc] The discussion on slope(s)
Date: Mon, 6 Dec 2004 09:54:46 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 06 Dec 2004 08:54:48.0256 (UTC)
	FILETIME=[3D7C4C00:01C4DB71]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: rohc@ietf.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.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002

Example 1 (audio stream with TS_STRIDE = 160):

            <------ String 1 ------>    <-- String 2 --->
SN           11  12  13  14 ...   60    61    62    63 ...
TS          200 360 420 580 ... 8040 16040 16200 16360 ... 
TS_SCALED     1   2   3   4 ...   50   100   101   102 ...
TS_OFFSET    40  40  40  40       40    40    40    40 ...


Example 2 (video stream with TS_STRIDE = 0):

            <------ String 1 ------>  <-- String 2 --->
SN            11   12   13 ...    25   26   27   28   29   30 ...
TS          4000 4000 4000 ...  4000 7000 7000 7000 7000 7000 ... 
TS_SCALED      -    -    - ...     -    -    -    -    -    - ...
TS(unsc. LSB)  -    -    - ...     - 7000 7000 7000    -    - ...
TS_OFFSET   4000 4000 4000 ...  4000 7000 7000 7000 7000 7000 ... 



> -----Original Message-----
> From: rohc-bounces@ietf.org [mailto:rohc-bounces@ietf.org]On Behalf Of
> zhigang.c.liu@nokia.com
> Sent: den 3 december 2004 17:45
> To: Lars-Erik Jonsson (LU/EAB); cabo@tzi.org
> Cc: rohc@ietf.org
> Subject: RE: [rohc] The discussion on slope(s)
> 
> 
> Lars-Erik,
> 
> Could you walk me through the two examples I gave in my email below,
> and tell me exactly how ROHC should work in your opinion, 
> step-by-step?
> 
> http://www1.ietf.org/mail-archive/web/rohc/current/msg02101.html
> 
> BR, Zhigang
> 
> _______________________________________________
> 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


From rohc-bounces@ietf.org  Tue Dec  7 04:52:04 2004
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 EAA07090
	for <rohc-web-archive@ietf.org>; Tue, 7 Dec 2004 04:52:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cbc7Q-0006dH-1C
	for rohc-web-archive@ietf.org; Tue, 07 Dec 2004 04:58:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cbbq8-0001Ts-01; Tue, 07 Dec 2004 04:41:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbbiQ-0005h1-7T
	for rohc@megatron.ietf.org; Tue, 07 Dec 2004 04:33:02 -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 EAA05924
	for <rohc@ietf.org>; Tue, 7 Dec 2004 04:33:00 -0500 (EST)
Received: from [194.237.235.30] (helo=effnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cbbox-0006HP-38
	for rohc@ietf.org; Tue, 07 Dec 2004 04:39:47 -0500
Received: from effnet.com (c-b97c71d5.04-205-6c756c1.cust.bredbandsbolaget.se
	[213.113.124.178]) (authenticated bits=0)
	by effnet.com (8.12.3/8.12.3) with ESMTP id iB78VvLh000521
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Tue, 7 Dec 2004 09:31:58 +0100
Message-ID: <41B578E7.4050403@effnet.com>
Date: Tue, 07 Dec 2004 10:33:27 +0100
From: Kristofer Sandlund <kristofer.sandlund@effnet.com>
Organization: Effnet
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ghyslain Pelletier <Ghyslain.Pelletier@ericsson.com>, rohc@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Content-Transfer-Encoding: 7bit
Subject: [rohc] Comments on tcp-08
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.1 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Content-Transfer-Encoding: 7bit

Hi!

Have collected a few minor comments on draft-ietf-rohc-tcp-08.txt.

- General comments:
     The structure is a bit strange right now, I think that the list compression 
section (4.6) should move to somewhere inside section 6, since it is closely 
related to TCP itself. Now, it appears before the basic things such as the state 
machine operations have been defined.
     Also, I think I'd prefer to move section 6.8 to being before all the 
ROHC-FN-code, so that the FN definitions are put last in the document.

- 5.2.7
      In NC state:

         The decompressor SHOULD send a STATIC-NACK if a packet of a type
         other than IR is received, or if an IR packet has failed the CRC
         check.

     I think that either, the rate limiting text below this should be moved up, 
or this text should refer that text for clarify. As it is now, one can easily 
read that one SHOULD send feedback for each failed packet and then one reads the 
rate limiting text which kind of contradicts this. So maybe something like this 
would improve readability:

         The decompressor SHOULD send a STATIC-NACK (subject to the feedback
         rate limiting considerations below/above/somewhere) if a packet of
         a type other than IR is received, or if an IR packet has failed the CRC
         check.

     Similar reference for SC and FC state might also help.
     Also:

      In FC state:

         The decompressor SHOULD send a NACK when decompression of any
         packet type fails and if context damage is assumed (see also
         section 5.2.3).

     This text seems a bit hard to interpret. Maybe it would be better to write:

         When context damage is assumed and the decompression of any
         compressed packet fails, the decompressor SHOULD send a NACK (see also
         section 5.2.3).

     Because that's the intention, right?

- 6.5 "ends with the static part of a TCP packet" -> "packet" is not a good word 
here. Maybe "ends with a TCP replication item" or maybe even "ends with a TCP 
static chain item". Now sure.

- 6.6 "30 packet formats" - not that many in there right now. Maybe remove this 
sentence altogether.

- 6.6.2 The coding of small CIDs in the "Base CID" field is not obvious, since 
in other CID fields, the small CID is encoded as an add-CID with 0xe<value>, but 
here I guess it should be 0x0<value> instead. Maybe draw something like:

    +---+---+---+---+---+---+---+---+
    :      0        | Base CID Small: 1 octet, if small CID and B=1
    +---+---+---+---+---+---+---+---+
    :                               :
    /        Base CID Large         / 1-2 octets, if large CIDs and B=1
    :                               :
    +---+---+---+---+---+---+---+---+

- 6.6.3 "variable number of bits" (base header field). Since this will always be 
a multiple of 8 bits, it might be better to say "variable number of octets".

- 6.7 The two constants defined are not used any longer so they should be 
removed and also the sentence above them.

- 6.8.2 Some references to 3095 are for the wrong section:
	"section 5.7.6.6" should be "section 5.7.6.7" (CLOCK option)
	"section 5.7.6.7" should be "section 5.7.6.8" (JITTER option)


BR,
	Kristofer Sandlund, Effnet AB

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


From zyfkhne@yahoo.com  Tue Dec  7 09:37:11 2004
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 JAA06620;
	Tue, 7 Dec 2004 09:37:11 -0500 (EST)
Received: from [211.162.140.125] (helo=132.151.6.1)
	by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1CbgZE-00053o-Nz; Tue, 07 Dec 2004 09:44:01 -0500
Received: from indicant [206.52.100.232] (helo=dungeon.apatite.dearriba.com)
	by smtp2.cistron.nl with esmtp (revel 3.35 #1 (disjunct))
	id 789LFL-0052PT-42
Message-ID: <35194093144732.R37481@granular.noc.affront.gr>
Sender: freeradius-devel-zyfkhne@yahoo.com
X-Mailman-Version: 2.0.1
Date: Tue, 07 Dec 2004 10:26:07 -0400
From: "Rowena Rosen" <zyfkhne@yahoo.com>
To: rmt-request@ietf.org
Subject:  Sa-ve 70% of Regular Pr|ce Rmt-request
X-Spam-Score: 8.7 (++++++++)
X-Spam-Flag: YES
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab


The L0west price of all med's is here. 

 V1a'gra - $199.95 (60 pil|s)
 Va|ium -	$259.95 (100 pil|s)
 Cia|is -	$189.95 (30 pi||s)
 Xa'nax - $233.95 (100 pi|ls)
and many m0reeee.....

We are the bes't available nowadays

http://missedalesson.com/2/sale/?wid=200007








This is 1 -time mailing. N0-re m0val are re'qui-red
ylfpaSolGVQj10oHAhqjMb154fWmApBRYar3VRo4sOVBj5UNvXUI7i4


From rohc-bounces@ietf.org  Tue Dec  7 19:05:05 2004
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 TAA17885
	for <rohc-web-archive@ietf.org>; Tue, 7 Dec 2004 19:05:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbpR2-00055t-Q0
	for rohc-web-archive@ietf.org; Tue, 07 Dec 2004 19:12:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cbozz-0005wO-GO; Tue, 07 Dec 2004 18:44:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbotE-00030f-1M
	for rohc@megatron.ietf.org; Tue, 07 Dec 2004 18:37: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 SAA15085
	for <rohc@ietf.org>; Tue, 7 Dec 2004 18:37:01 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cbozs-0004Q9-HL
	for rohc@ietf.org; Tue, 07 Dec 2004 18:43:57 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <YHL6R2RH>; Tue, 7 Dec 2004 23:38:11 -0000
Received: from mjw-pc.roke.co.uk ([193.118.194.159]) by rsys002a.roke.co.uk
	with SMTP (Microsoft Exchange Internet Mail Service Version
	5.5.2657.72) id YF4R0WM8; Tue, 7 Dec 2004 23:38:15 -0000
From: "West, Mark" <mark.a.west@roke.co.uk>
To: Kristofer Sandlund <kristofer.sandlund@effnet.com>
Date: Tue, 7 Dec 2004 23:36:18 +0000 (GMT)
X-X-Sender: maw@mjw-pc.roke.co.uk
Subject: Re: [rohc] ROHC-TCP, ack number compression
In-Reply-To: <41AF2CF7.2030403@effnet.com>
Message-ID: <Pine.LNX.4.44.0412072316480.22606-100000@mjw-pc.roke.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Cc: Carsten Bormann <cabo@tzi.org>, "'rohc@ietf.org'" <rohc@ietf.org>,
        "Ghyslain Pelletier \(LU/EAB\)" <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: 5ebbf074524e58e662bc8209a6235027


Hi all,

Apologies for the 'usual' delayed-ACK...

Comments in-line.

Cheers,

Mark.

>
> - The implicit ACK number scaling in bidirectional deployments seems to only
> have the support from Mark, while myself, Lars-Erik, Ghyslain and Carsten have
> doubts about the complexity required (Mark, if you want to keep this, please
> explain IN DETAIL how you want it to work). I think we should leave this out of
> the spec. (if I have misjudged the opinions of anyone or if someone else finds
> this to be compelling, please yell out before we scrap it)
>

I'm assuming that this is referring to the proposal to use sequence
numbers in one direction to infer acks in the reverse direction?  (it's
just that I wouldn't call this scaling, but that's being picky!)

Well, I cannot deny that I'm still rather attached to the idea of this
scheme -- it just seems like a really nice idea from the TCP perspective.
Also, for a more applicable argument, it's going to have most effect on
'pure ACK' packets which are, in fact, 'pure overhead'.  So, arguably,
these are a good target to try and squeeze harder...

However I also cannot deny that there are a number of issues to be ironed
out and corner cases to be thought through.  Having said which, I still
believe that it is possible to specify it in a reasonable and manageable
way.

If anyone actually thinks that it would be useful for me to write a more
detailed description, for discussion, then I'm quite happy to do that.
However, I get a fairly strong sense that it wouldn't be worth the effort;
certainly nobody has indicated any interest following this mail.  In which
case, I bow to the majority view...

> This leaves us with (at least) the following different roads for this:
> a) Only send unscaled ACK numbers. Not very optimal, will often have to send
> about one byte extra compared to a scaled scheme. Simple and clearly interoperable.

> b) Explicit scaling (ack_stride, 16 bit value) by letting the compressor send
> over a scaling value in a compressed packet (for example, this value could be
> transmitted in the dynamic chain and co_common, but nowhere else). How this
> value is inferred by the compressor would be an implementation detail, so that
> it can use the reverse-directional stream, it could look at the traffic or it
> could use some proprietory out-of-band signalling etc. In this scheme, only one
> scaling value is legal at any one time and if the ack number change rate is very
> variable, then either we need a frequent update of the stride or we have to send
> unscaled values until the same stride "comes back". Not being a TCP expert, I
> can't really say how much gain/loss this would be in the end, but I think it
> seems worth considering.
> Also, if we go for this strategy we need to decide how to handle it at context
> replication (always, never or optional).

I'm really not sure how much benefit you'd actually get in this case (in
terms of overall average compressed header size).  There are definitely
going to be cases where large gains can be made: some flows will have long
runs of 2 x MSS intervals in the ack flow.  This will work just as well as
deriving acks from seqno, in that case.

However, in many other cases you will be faced with the 'how long will
this persist / is it worth setting the scaling now / when will I have to
change it back' trade-off.  Ok, there's scope for clever compressors to do
better; but if it's too complex, who will bother?

Carsten's observation suggests that this might typically be able to save a
few bits per header, but how often do you have to send the 16-bit
ack_stride (+ the base-size of the header to carry that information).

> c) optional feedback option sending the ack_stride (the sending entity's
> decompressor could take this value from the co-located compressor). This is like
> the bidirectional stuff but it is "explicit and optional" instead of "implicit
> and mandatory". Downsides are the delay before this can be used and also this
> will probably lead to some sliding window of scaling values so that
> compressor/decompressor keep in synch. I'm not for such a solution, since it
> seems complex and slightly evil.
>

Surely this case is more the remote end-point being able to 'suggest' (in
a feedback option) suitable value(s) for scaling, as defined in (b)?  In
other words, I see this as suggesting a refinement to (b) rather than a
separate scheme.  (I agree with 'complex and slightly evil' as an
assessment of this scheme on its own...)

> I could consider option b), but as I stated, I cannot really estimate the gain,
> so possibly a) is good enough.
>

I would consider (b), too.

I suppose that I have difficulty accepting the statement "(a) is good
enough" when there are clearly ways of achieving better compression than
this.  Although I freely accept that the trade-off of complexity vs.
saving is not obvious.

If we're going to take *that* strong a line on complexity, then (a) is the
only way to go, of course.  And we probably ought to take a good hard look
at the draft to make sure that it's really as simple as we think/hope.

Cheers,

Mark.


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


From rohc-bounces@ietf.org  Tue Dec  7 20:11:58 2004
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 UAA25040
	for <rohc-web-archive@ietf.org>; Tue, 7 Dec 2004 20:11:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbqTl-0006gI-Gn
	for rohc-web-archive@ietf.org; Tue, 07 Dec 2004 20:18:53 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbqJU-0004vx-Sf; Tue, 07 Dec 2004 20:08:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbqIQ-0004iu-LQ
	for rohc@megatron.ietf.org; Tue, 07 Dec 2004 20:07:10 -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 UAA24483
	for <rohc@ietf.org>; Tue, 7 Dec 2004 20:07:09 -0500 (EST)
Received: from mproxy.gmail.com ([216.239.56.250])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbqP4-0006YV-VF
	for rohc@ietf.org; Tue, 07 Dec 2004 20:14:04 -0500
Received: by mproxy.gmail.com with SMTP id q44so124154cwc
	for <rohc@ietf.org>; Tue, 07 Dec 2004 17:07:06 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=dpZFaJr0R7p6h/z92bpNt0iiYDEprqElPB7e2/1b0Lf3rRcjnzaXPhxqpw8Rcf3MVvP81lKzjYKlvzveCIuxvjv5EIHi42mQ713f0VKKvFzbYmInZm6O8B9EHRmUyciXnjnu8SZI2wx+0+VJiWm5Do+r2A5RbavLMu66IgdUbB4=
Received: by 10.11.99.55 with SMTP id w55mr490948cwb;
	Tue, 07 Dec 2004 17:07:06 -0800 (PST)
Received: by 10.11.116.73 with HTTP; Tue, 7 Dec 2004 17:07:06 -0800 (PST)
Message-ID: <db95d40c0412071707b0c2e1b@mail.gmail.com>
Date: Wed, 8 Dec 2004 01:07:06 +0000
From: Pedro Fortuna <pedro.fortuna@gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] Re: Review of draft-bormann-rohc-over-802-00.txt
In-Reply-To: <550877E8-420B-11D9-82C1-000A95DC4DB6@tzi.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_480_15606254.1102468026652"
References: <3F2E01E1D7B04F4EBEC92D3FA324D8803857FC@rsys004a.roke.co.uk>
	<550877E8-420B-11D9-82C1-000A95DC4DB6@tzi.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 441f623df000f14368137198649cb083
Cc: "rohc@ietf.org" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Pedro Fortuna <pedro.fortuna@gmail.com>
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: b5216aa5b0df24d46eaed76d4f65aa31

------=_Part_480_15606254.1102468026652
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Dear Carsten,

I've carefully read the draft but there an issue regarding section 5
(encapsulation proposal) that I didn't quite understood.
Let's say that we come to the conclusion that 802.3 LLC+SNAP
encapsulation is the best one for addressing the padding problem. With
this in mind, let's analyze the following example scenarios (see
attached gif):

Scenario 1
|  PC1 |=3D=3D=3D=3D802.3=3D=3D=3D=3D=3D=3D|  802.3/802.11 bridge |~~~~802.=
11~~~~|  PC2  |

PC1 sends RoHC packets encapsulated with 802.3 LLC+SNAP. The packets
arrive to the bridge where padding, if any, is stripped by the bridge
and the RoHC payload is then sent to PC2 encapsulated in 802.11 data
frames. This scenario works because we can make PC1 send packets with
the Ethernet encapsulation of our choice (i.e. 802.3 LLC+SNAP).

Scenario 2
|  PC1 |~~802.11~~| 802.11/802.3 bridge|=3D=3D802.3=3D=3D|802.3/802.11
bridge|~~802.11~~| PC2 |

Now we have two PC's connected to 2 different AP's, interconnected by
an 802.3 link. In this scenario PC1 sends RoHC packets encapsulated
with 802.3 LLC+SNAP. The packets arrive to the bridge with no padding
(since it is 802.11), then the bridge chooses one encapsulation type
and adds padding if necessary. Imagine that a set of particular
packets are small enough to need padding when crossing the 802.3 link.
In this case, if the AP chooses to use DIX Frames, then the second AP
will not be able to tell that the packet has padding (due to the fact
that we aren't carrying IP packets in the Ethernet frame's payload).
If this thought is correct, the padding will be transported in the
second 802.11 link, falling in the problem we are trying to resolve.
I made the following test: PC1 connected by a 802.11 link to one AP,
connected by 802.3 to a second PC. I sent a 0 byte ping packet sent
from PC1 to PC2, and after sniffing it in PC2, I got a DIX frame
(source MAC=3DPC1 mac,dest MAC=3DPC2). Is this a general AP behavior (i.e.
choosing DIX framing) ?
In this scenario the problem of padding isn't resolved because we
can't force bridges to use the Ethernet encapsulation of our choice
_WITHOUT_ changing the bridges software/firmware or some kind of
reconfiguration (if the bridge allows such reconfiguration).

So, unless I'm missing some major point, choosing an encapsulation
isn't enough. If that is the case, please fill me in on the pieces of
the puzzle that I'm missing.

Best Regards,
Pedro Fortuna
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Pedro Fortuna <pfortuna_at_dei.isep.ipp.pt>, <pedro.fortuna_at_gmail.com>
Computer Engineering Department, ISEP-IPP
Polytechnic Institute of Porto
Rua Dr. Ant=F3nio Bernardino de Almeida 431
P-4200-072 Porto - PORTUGAL
www: http://www.dei.isep.ipp.pt/~pfortuna/
Office Phone: +351 22 8340500 Ext. 1775
Fax: +351 228321159

------=_Part_480_15606254.1102468026652
Content-Type: image/gif; name="scenarios.gif"
Content-Disposition: attachment; filename="scenarios.gif"
Content-Transfer-Encoding: base64

R0lGODlhwgIyAXAAACwAAAAAwgIyAYcAAAAEBAQICAgMDAwMDBAMEBAQEBAQEBQUFBQUFBgYGBgc
HBwcHCAgICAgICQkJCQoKCgsLCwsLDAwMDA0NDQ0NDg0ODg4ODg4ODw4PDw8PDxAQEBEREREREhI
SEhITEz/AABMTExQUFD/CAhQVVlVWV1ZWVlZWV1ZXWHWKChhYWFhYWVlZWn/JCRlaW1paWlpbXFt
bXGhWVlxcXF1dXV1dXn/PDx5eXl5eYGBeXl5fYF9fX3/SEiBhYn/UFCFhYWFiY2NjY3/YWGRkZGV
lZWVmZ3/cXGZnaGdnZ3/dXWhoaH/fX2hpaqlpaX/hYWurq6usrqysrL/lZW2trb/oaG6vsa+vr7G
xsb/srLGytL/trbOzs7K0tr/vr7S1t7W1tba2tr/zs7e3t7e4ur/2trm5ub/3t7/5ubq7vbu7u7y
8vL/8vL29vb/9vb///8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAI/wDdCBxI
sKDBgwgTKlzIsKHDhxAjSpxIsaLFixgzatzIsaPHjyBDihxJsqTJkyhTqlzJsqXLlzBjypxJs6bN
mzhz6tzJs6fPn0CDCh1KtKjRo0iTKl3KtKnTp1CjSp1KtarVq1izat0aVIkIDWB/lKlp5ccPNRZV
aCDCta3bt3DjxtQAoK7dB1to/qibl6KVuj/kCh5MuLBhhnsBiDArou4DmkTAgqEY5QHgw5gza95c
la4Ggir4Ji0T2m5gzqhTq169k+4DKwOtWOkrkMiD2w9oELR9W0OUgZFFqFGBW8lAMCJw5x6oVgWN
20Qia5gsMIoG3CrGHkxc+jTr7+DDi/8PmRiABhqwC5a+XVeFQBqOLQMw7mbvg+vyAVC3jPuyG9d2
lSWaG0rc5Rh1Bf0gwmz+jefggxBGmFBjdgHwgHsC/QUAhqVtUYZlHFooUGIajEXEZZXh5YYaln32
X10ibMFWYnl9aB5sJ5qn0BYNSujjj0Cq5lV+OroB3wPaqUFEXiciKZCNxiWWnhuWeXecZwK5pl19
okk5EHz6JcQjAFYGaeaZaMplxXN1seXaQaWBBdZlNA5U5ZOR5efimwPVyadAY7KF0JhlpmnooYgu
pcYPNPw20BYtvviYQRTKKeeMA1JJphtg8KfBD1hKSpCfIj7appg9JqrqqqzyZKMIBLH/qOORWy4m
oJMG1SnQnY09gNaLexY5omi09pmpQYS2quyyzMZEoQqTbUEXAGxpiCGYSoDR3oi3waarpoHxKWuw
Lg4LQF4aaoCWFZGiummz8MYrL0idGlhXuRSyV2Sc07r47Z1xEsdflsJyea5A68mnoruFzuvwwxAz
hFx+FxbEpoUYvqdwxj/cRtttpyWHcYqTJQdrnx6j7JgICA4KcsQwxyxzQVts0TLNtOEsURk5TwSG
hzMHLfTQRBdt9NFIJ6300kw37fTTUEct9dRUV2311VhnrfXWXHft9ddghy322GSXbfbZaKet9tps
t+3223DHLffcdNdt991456333nz3/+3334AHLvjghBdu+OGIJ6744ow37vjjkEcu+eSUV2755Zhn
rvnmnHfu+eeghy766KSXbvrpqKeu+rIxVOj667DHLvvssIcgsxgF0K777rz37vvvvEvQdAjAF198
DBBrAAUazDfv/PPQRy/99NNzwcBJEz9wcob4WclbxQdJe1vGBYmw/aMLI2R+TFZoQP378Mcv//z0
1+88ADZ1fBt9tfXmqBtlSM59/ncQFvXMDexy2QHXJ6b0kYQBXLCfBOsHhXLNS3kTzGD8rHeS+2yh
fS76kApk9K4TLQmEBhHhFipDvoGAxSBgmI5CXgiT9mnwhjjMof3wpxdqbWEvjirQkv9Ckx6w1AyI
CFEDXXoGqUkh62DqaSHNoFgSCOrwimioYPKWh8UccrAk7NLOXyajFpTtKmN/6dlzBqIEJxKEhhGB
o0ts2MU62jGDPJyJBjKmgZOdZyDra+OW5MhG9uRMf24kCI8OyJBFnsSKd8ygFh+GwUhO8IskCWN1
wvQA7zhSNqY64JbaeBBCckqGRFCBdQaYJRdJS1AqoaMlZ0nL5+VRJnt0Iaw+RJuOrQiW/7GgnX7g
SED5xpfhoyJzMBQjgWGomDQQjkggWcv5TdJhlaym/DBJErBYgYW7spIDEZZIRbZRNwYxpSM7poHZ
XKeVboCUFE8iS23as463jElliEn/nGhRMYEF+VDDAKVMbg2qoMHcVSdJGBhHEoeRHKHmPal3zQty
caLU4+ZI2oib9DiwkwUpEP8MghsCulCY8TzYXqjjSCMupyX1bF4RdAAELzxvpkV4nheAoIOcTg+n
1MvCB6IHBR3oIAvPy4JRbeq8mdb0fVkAQvSYcFFb1kQNAgQfpBRZUFNy9YDIfOIBaai9k6Z0C2qB
aEQjiFGKohRe2Wxr9DQaEpHWBgCweQ1BHjDSAqFTIfCZklmnmJewUikv+ClnSmKKBgs4wLEOqALz
vODYyjaPCY+FrGShV1kHOICp0NMBCqCHAgBYwAIA8CkaYGBax/qUspl1gGqjd1ro/1XBATqQXj5h
Aha0lKGP8XQjpLakRBmiCqyKPWs6XQTSEX2GR3QZaUgkKtfnVVReca2u8+gKEuDayT3NBWD6QiPd
hIDvjShdpxtVRJeODdQkMQVCZJn3AQswDwX2RcNtc4sGB4yWvvl1Hn6bZ4Gh0na2aMgCAKSKBh04
YLKyve+D0VDf5jkYtM7LAmoDzDzMAoC/0NutS3iEIEEWk0BOhNRbCZur5J54sOEFVUr36KsHslW7
1l0xs7KLYzRw9yO5NOsfM4Qr4ph0VH/9z/ngyWLDsvczHbsZSmI6YOY5mHkRZh4MHpyF+Vp5ws6j
afNgwGHngVmmYK4CACR75eZF2P8CIFbzZp0nX/xyGAUO2DKIrTqT4YaSSlNaY3DnKdYWH3SszPWO
jBfJIkKvtcc53iKkt3u9khDnV5CaUY3dUEYjjVM9m/5LedWp0vUidk86zqT7murlAut3zc2Tb/Tw
TL0xWOC/1i0zGrzgAAbTurEcxi30igAApD6PqsAOs02FHT0Rt0SgzJkUA6nkHhE65MUGTSaiw9mn
5x4sCgA4ckeo2+PrxovHOP6xR4rLqPuc9AfEgc2H7mOpaC0sLM+Z53UsNR317vXUAunUe0fC2C1b
Vr+fbd5tMYzwPWfYsQYmrcOZV4TYbvbWzsP481w9vdpCj9khrsleVKAgvgZce6D/qnFo+M3MJWO7
Pi42j6XcQ1ZFe7svl57mjSdtbrhWFdLq/khwgGmkPVJnUWZJ+llWtPTa9LG8tVG6WdSwqHVZaenR
Ac7ARRJTKPhXB1uGAcKdJ2eyOyDi0BsD2P0bPS87j7Jw1gHH4ZzxMjt2DNTz+PNAzmeaWEEtNGgZ
GAD/KyJI/QeCynqsmk6QsiTx8GxR/A+mZAW2VP1Jk9f5pJvX82ahW7tBh1dMNY4GYmdBzcYe+2XZ
Dj/TJ/XMzfv1rnvdWLTTnXkatgDDOavr/k6cec4uGrlx3Pkd/7zHoW9WTB3ABDMfFdZflikAcA09
hvMdDUBAO4HFTmD7VtjN/L1t/+953/bfoyH4RBu+dou/rM9XN/nMWj73Z59TkH+f2Aje+/yhAICf
WyD/yeZmoyVruAdrt0V9edd719c86Dc06ldd7Kcs7hd7p1WBOsBwQFBZKLB7XqB9GVVpMBNTW7Y8
sPVly0NszcdrKFAFLMiCzAMEDDaCu6Z3brZ7aMAEC3Zf/Ydlo2Vr+XVaLeiCaKB2eFd35adbTfOA
zVNfFfgBDEZnGohhTFBfKHB80hOBrTKBzFNZFehZzZdgjgUDRuVYc7aFsPeBzJIGM7AlBlFwnvVY
qYdnnsVfDvaGb0hfEbdlnuWBUDB+2GeHX4hwnmUBSHVbduhZknVbZUhhHuh7SP8IEl8wG4aihFiW
WaflWUylYXk2hl6mAwAghqUFgNCDhayihQHoZj9oAUW4hQHWh541P/CHJh4gAGt4EIzFPFXAgYtI
P7kYPWOQetJTBcCocMM4Sw2YBmWhAhtwAXUhAFOwEEHwOhCwAS+wA01gBWw4HpToiAqXZ6y4igEI
crLnVpL2PjS4Wg/Gf4HYYSiAd7cFA1sGiyCoLE3QjLXYeKu2efrYdwNRBk2wAxugALLjaAjDO9M4
AzswBYIlGE8gAkiQBgmxjddXW+p4bO04BiiQem32PqS4KqZ4jh/wYPE4PWNgUxsJP7F4JmVQIbS4
Jbe4j5OWR1MwAxCgOw0gAmL/sBCksQE8WZO9Q5BcMQEw8pAGIZF7NgZsN5Lx830cmWoSaIUbZwEt
CAWllVuOFT8n+T5coACy0ZVe+ZVgGZZiOZZkWZZmeZZomZZqSZYB4DotiUD5CJP7CABBIAICEDsQ
IAIJmZMX8UFEsAPK2ACxA5GDMSZ24ZCE6QYSCQMtWASotTxXGT8oGD8dqSofCQCHyF+R+T5ZST0n
YDygGZqiOZqkWTy0+ARxKZeT5omvYwAmEARWwAYlEYlBsAMesAFBsBBpYALUuAOSSBWC+TqIKZGH
aAFfuJnUQ2zz15TlmIDS05m79jzQKT0CWZrWeZ3YmZ29swEYoJr7mAEVcgE//3AFPBGNr6MAG6AC
O4AE2KgUsiEGpQE7AqAAOyc9Cxh91ec8rCWKROWUWQiVRkhUO+g8XldV0xk9RyAAPLmgDNqgDvqg
EBqhEjqhFFqhFnqhGCqhdymcH5Sa3kl8G9IEickTXxCcujONHrAD1piNM1EGsqGiIrABPtmMQxA7
F/AFRnmFA8p5DsBFeMaf/dmcHeeHpwWO53ig0JOSZ8Kh3BNJYxCExZhhUVoF4IhjDZgTYlAWNyCj
vCMAX9BIfOkRSACjPCmUvFOPr7MDApGj0lOkAYpnu8iclASg3Tc9hggDTCB3boefGzSPrfIFFRIj
+BhJrGkXWUZ+H2d+bXWlP//hov/4Alz6OmolEMwoOxP6jApRHryDnikqG64DAeS5pvV5hMHoWXiq
p5LFfx9gVKxKmf5ZinR6XwioU3LoX7uXffLYLDsAIwf0kjnkYEFYWlYIg6QKaYxqFMhoBSr6BLq5
ocWzAdAYO5yqogrJohrSHrI5ENvohNTjBbW6gS9YgU3oqkIKdH7KKjcJUb6KQ1nJd1lgg8LIjbgI
r3GKT4TRBA3aOwbQBAzxBLApGyPKEFNQFwqAqQSxjRNVmYliihOlpECSBpO6rjd0kkiZU++ImUJl
YBXnWXjGX3roX162sV5ojEITjR7Aooo5qsT3qh4ZqxjlsKsisRrkYKwqd/n/pWYWAAXNV1sqqIO5
hX8zCGv852sJF0nH2iwqgAQRqbLrx7KW6bINe64OI7MZ5Il2OH24mFp1epLCxnEJBmtM2V/Laa9B
E7AFgbD3pLCIwrD3BLOqQrUTdJJeN1Rlx4qn2Fi5xXfzNYhd6Ic5dLQxg7b2pLaHwrb2pG5gYBaU
Zxa7MXUGYXjlxXgIRHQC4RWfshCWSwPaQQT/syijgiBIZxaUixxLNmUeekVZGY91m2w0SHd6K1ln
V7NiZrQmYRb8UwZmgSCGJ7kDMRwFUXm5knSUWxC/kqkaAHU1IbjaRLiGYrja9GMfogSVARvWURYu
IgIjJGMEgb1olWSHNSoo/7VHs9FpB0ED7YRWk3Id2rFVlTttkJJ0X1E+gQdTp6tDqftgq1tbXGuV
EadgkkWDRRClVwS4FfEp0hIY0asEJeIG3Ku9sSJH70tSSUccKOsGhrcQnTKpM6G81cS8aeK81fRj
2ksDgbEgWaIELOJCOXMy7GsnhyRMCvJG/yOoWUIbLBNMLOxEvoEr0vJvV4LCYKAGW+BbNfMo8VQj
QPMkNnMcRdwQcCtBG+kFFUe30JdsvMZgQPBhpae1tgZrQHuDWku7I8G+PUwE6ARvKVzDBFEZ5vsl
F1IobqQCGVMz2kEDNIBpScxGGpAXYPAzgLLEK6IGPzMWTfzHigTIG8HBtf/kwWgCwrUEvXjxW7/x
ANTBuL1LyQdBBEvmQA58wgmxx8zRTgXRTmsRXE/yGCRnTJesu7kBQmuhwPDmJPeRbyLwHJMBy9jr
BtahIKVri/X7q5hphwaWv/lVceLqsW8Ipzp4WlhrSQRMEcfLabpRyvFkQSzSMtjYw9VRH3CsSI8R
Q3b8AFGAVQsCzs/Ruc9BTPcBK3sEKroBKtibG9HkR84hQzRAcpebyEwLgU67sFDbtlKLMHKyK31i
JXKcQskhXZwsTJ/GwPtGzc/BSv/xQUjCvveMQJPyvmbhXSr8H2dMHaAszhiNMGKxaZQsAoKydU16
R08ahM9ThlmQejuVU1n/sIpekIv+2zxRBQQCjEXPPBG2cR2TAcrVDBrzpM0FTVLePLnvERiMC7xG
YiU9DClooQbo1MPaW8ofIs3t+71lMLwVoci0xMhn4si0JMLXAl5JLRC57DIts9CjvJB/fLxDTBBf
LdKgHE3s+8YdYxwanXmjjFi0YcZLRCWqzM0qBhYPwLm3Mb8M8cTV9QERR4AT9dMR0T5oYR0TfdgM
TGhIPSLdjD6Vm3JOfRpKQNqK9FzlUhZfAWWnQdSPwW+P8RxrUcEUIdazRNZmYtaz9GNEvVULk8oe
fRD/Q9S78sLqkWTCvdmccj6MS9Q0htETDCufnU6CnSUj9Ft5kdH+Qkx7/1wzSbwmuKIQkC1Xc6sD
H/CJi0oSjGInpGHae+K9qZ0goe10RWcFiVva953f863NlaEENePaamzYawHetKEE5JsRuG1Juh0k
vG1JP3bQFgwrwr3A1GzE38sibAjXdq1XGK27xTtkSmQcRP0Xj4HS/VjRqQbKsF3VKsLdoJ3heywC
9GHcCVHecuUFrPrPdmTZEKHAgPIYXoEwJE50OVPdlrxXA1EZv+EbbK3fTs7AUq3aI3LGAs7cjwFv
tQErTpLGGrHgkdTgQPLgkaRurb3AwfRH7KIcNTMpbQQWCq0cZqEck2IdciJuAZdV6ETDnkYlbFjL
W9DLgJQXNKwWfZTKGf99Moz75suR2PLtyx+qjz4OEeZ7Helh6LCy5rix3bQR6PRNUrgR5W9+HrBS
GTROb9GkSNR9Mp0CFmtkyTQsbXJyy/SGvLe9z+bdz2vL488b0P0YUBChwQ1h2wUhZSNB7DBU7A+B
45HuzNjzEsYecBAR7QmRjcIuEWB+R2L+I2R+R26bKMze7Hc06fKS7Xa07T7S7Xb07YgS7uJOtktj
7nWE7hKiASVQA/ie7/q+7/ze7/7+7//uAr4eL1awAAB/8Aif8Aq/8Azf8PpO7vHCAC7g8BTf8CWg
64eirCq68Rzf8R7v8RowAR8/8iS/8cwaM2zwAyW/8izf8iQ/ASHg8jL/P/Mlr7RM8wQ0n/M6r6Jy
DTW7uiFEce3IYuA7Eistc9q2HhHUXhWlYfOaQXUSYeB5nOyK1HiIpxFCjzo/vy1CkVw70kkbPd4F
4Uba20YkF7996ZQBBBXxCQBOjxlJ/hBgX3J4btxk3EexnPXmxRCCDjpbbxdAqRSfvRgIQfafwUvL
lPYLUd1K0fZ18fYRYvgIYffpC0uRgRFebyen8/cVEvgbgelsPetUkhyQktDb8xiPIS19JNIOTerz
DUiB0UYJTdDdVh/nU7wjYuguosDJccba02+qfct9BMrJQXNf0fc/4fh2AflL0TFfMRnmO/sltxgm
I8pGsrvUdh3oVOnE/zH24Bv63kX5pmzXqW0+C3PmkxFDrm7Y/+HXw28coQErvM/6nTMFDGoACrqg
zC90HEIESrD9APHDzQMibgYWHFjGDREVA91sebDFjRINbn40dCOiosGHD3581KhmoMQyD8AM1JBS
w4OKIgRyhGnwxwOZDTWIVEMTzAORRERs0QBUohWebqxUBLoQo4qTMZ0+hRpV6lSqbpBswLpBgIKs
GyRWBRtW7FiDO3uKACPCYJSKM0W6tYjxQZmPB92UNLpxZkyPH1U8sBLXIA21KlXSJLIRKsShFZXQ
GCxQBEINZjUoMRjRTU6FNBMaxUhW9GjSpU2fRp1a9Wo3GxqwrqohMP/MMlt+aBDo2aFBFQUrO0z6
sGJQg4lhQvyoQa1wji5HboFOo6KKl1B/QO5ocMtjmtePP/AoE/fHuUmJisAMW33YBqHXvw/rHaaa
LQzbYpeP14raurq7v9yJL780UMgN4twI8DLotqOJIqmCG+ik2m7LjS/ltOtrJsw8E+EBGpqCL0QR
RySxRBFdM9GgAw1SwkMiaKgwM46OCo6m4JI60EGOIMSNOd5iFG8hxYyqzqKXIDLQpSj++25JhX5w
6aMf6NuojMQASxG+9rJMsS6OdqLOQS+9zEgJ9IzczSEv8YJJNxWWOxCvFZEMECYVRNJOsYhapOFF
IDNLLIqOpPwhMN3/rPhrOS4XZbRRR1lDMUUVsKNBOkHdoC5N3QzsTcYbp3tJhSEhJAqMkvDEctPb
MpstI+xkWs7M4PDSka2koJxoIzVEoHKhl2B8VLUtg32vVtywE/MlMs30rD+OGlyOiE3TzKmgTHM1
8KvsMqpu1R2LkvPSTDW4VDaaiFLjVN4MNWi5nIiFN155iY3UxJIqnUu6i0RQyz+YpC3Qxo2SUsMw
9yDEVC19RZALJm9bFIGGBxSV6YFJK7sXSpM4nSmK4DTwzSUNINsJLQ+lA3FesoZVWTUNqHsgiiWv
6xBNmzPDyFkZMzqMr395ulc6ieb0DIyUpPvtW9wuc0PfN9WaWdTd/2hoaOGNWCrjTSjda7lrr78u
rd4UrWi1vpNO0lZboxT9CsSzH6KrSARjapsIENVWI2WznfoIjPTuUiKwu5UosKm8tbP7S5KU+Bts
sFh2nLTtCidCIonUwBNzmJLWPO3NEAQD4YfoxtOKv1MefcfKnQKqDMJVfxvwrzxHcHWDatPuB9Qj
57133sX+GqhWo6K6DKOHF5FM3xuFfHn41DBuqqNMvZZE0Z3HPnvtxQLe64jBuo3cFIlAaPsUmzdf
tcTUjoqiHk0Eg+v056cf++7rxz9/jtDXv3///wcgvO4XQAL2jn8FRGACFbjAsAyQgQ8M1gEhOEEK
VrB+DrRgBkUkQf8NdtCDHxTga0A4wvVwkIQnRGEKU4NBFbZwKiZ0YQxlOMPWiJCGN3wKDHG4Qx5W
kIU9VKEOgThEIgLwh0UcoRCRuEQmau+ITdSgEqE4RSp27YlVnKAUsbhFLi7qil1UoBbBOEYyqueL
ZQygGNG4RjaS5Yxt1N8FXgBHOtbxNG+04/zKkIY89tGPVMHjHwU5SEJuL5CFRGQiFTmvGWxgkY+E
ZCQlOUlKVtKSf4ReTMhmkcht8pKfBGUPRVcXinlNeaFEZSoZiLnQFQhB0DkOdBSzBTDUpW210Vvs
DII5WmrHc7CsjStD15SUEXMLrnxILeWmSmY203+3mdTGtKYRFUX/syL3+kuFIDKy8GAzJQ5LiU0u
dhKWSOxNEjuJvl7WNOwwJGG3wQw2w+NMetazfg9TS2igVRxQ/Qg4RTkKpkI1JG9NikX9EhRRfqSu
gVihTpXREV6uVT17VtSivvMSkugiKiYx50DO+lS2WETQlxhmJbsJzkcgNC6HtoUlKQGA0b5yyovW
1KbzyuhcPLKFd2V0ODPV5sB+yk+HlbRyC0KpXn4AIecwpFMXWdDQgHpTqlaVWN6C6kYUGlCLtAUj
zhFYngRTMJLWpDj9EiuaNJOTpoDHIOjKzkXatUyr1tWuIQrfhQykHFFJBGl61UhKtLmcLSznLy97
1c0C+xvPFFYm/wJpUUr+xi+OSGwl6VksXe+6Wc6ipi7IRCZHQhtaqLyuaZoVbVh25xTUkbazr4Xt
aGi6msQoAWCxxW1ue+fJ91jhI67VbXCFO1ziFte4x0VucpW7XOY217nPhW50pTtd6lbXutfFbna1
u13udte73wVveMU7XvKW17znRW961bte9rbXve+Fb3zlO1/61te+98VvfvW7X/7217//BXCABTxg
AhfYwAdGcIIVvGAGN9jBD4ZwhCU8YQpX2MIXxnCGNbxhDnfYwx8GcYhFPGISl9jEJ0ZxilW8Yha3
2MUvhnGMZTxjGtfYxjfGcY6tGjpY9o99Or4wWwAwZAB4SF4z0f8MWSjygCKLALhAfrAViAweIsuv
UT8Y8o+pQoQhUxkAQ4KyhEVQ5NkQpchPzhJ9tEwVJhNoIUMuX5gjrIEvgzNpLPoIEUKrhI80Ts13
6XNMlPkDPSvOVL/9M0x8+1uo7GSeAwEAauWs4DEDQATI2xGdp3wpoBC5zjIpsrSIrBgVeLrITaEz
TAFABCwDQFua7nJinYKnkkR60hLeyZRBhkwme2gmRVZRkWHE5OW0GgDU0TRmpHzs6wwZTl0+aau/
ommRDVnSvBnyam+94KOY+gHp4TIA0rOkoCx73Nm2iLXLom7oVSfVwRY3R6Q9EXUHe1pOKfWxt01h
MEiHyUMOzJj/753uiCyIyQKZd2ZsrboOfZrOqsoypoDNESUAPCr5BvO+J5xvm0w8JrA2NcIjrvBf
/ZvKG3m4wyKe8h3VG99DzrjGFQwRI7epzgI/zmCKHFXovGXkkBY5AGgwNId/GtSuzojHjWLxlxtd
5g7utbYqru9wp0fKHpk6p3+gBJ8jneQGMvq7wU7QiIe7fAInbRRgjqenO7jVE7sNkQNTa1/3ujNF
9tjDn/Tzg4M9ZnTpcrDJ7vV/w6jSslZ4kcEDnmu3PcD59vS3Kf7vLo+b8kVOT8KB7ga1d3liExf7
0Wd3eX07ZdmmXrjjFWwFpLlktOGjAWhh78pFs/0jZRbVh9Tw/5GeEFrRvIeJmV6G6bcSilDEV33y
lb985jff+c+HfvSlP33qV9/618d+9rW/fe533/vfB3/4xT/+qiwadcrcM6HRXLunRAH55Jv1lKQC
f/KTxvya9H1M+Fxoqbi//cgvlPhju6egv0kqNZj6Gxr4ssu6nZVICcmLim+im0f7uIzbAq+DCgms
P7I4QDqbLJYAj6YoAwdkwMWgQAzRrBN8CAx8Cg2MJDBYtYq5HQj8i3ZRjJlwLaNxOs7ruxaMuTXj
CBfcQLCAQYTYi4lIMsC6wblovx7kiCVJPQF5CiBUkZhTpBZpOYk4wszAjPdZwR+TFlEZkr+QGM0S
Qu3YpZPgs/+/0cBeGsKpwELtQLp1eism9MIL/DEypEA9TEG6apvea5U21DZBKgmEqMG9apNlqrjd
8T8X/IHOMEMLRLq8ojM42Yi/oMI3vAuC4A3PeDQY/LFF5BtIdBhSfAoVxENOeamFk0BMhKTIWolp
cw863JxSqsBTjETWmcQYfLOT+CZX1EQ4fKkkg0AudAq9ggoVHIg+1MWhSbJD/MUkW6QRHA+98kJE
3JyiiMCYU0ZsPI5J1I2SGJqXYcJglApqTI7lkMZl/DhtTEa66kZUnEPFiMNwKkf92QGT0sd95Md+
9Md/ZIHTOMRNDJnNqQ6jcTOpOEN29MFmtIhN0YyH2xiwKAP/DvjHi8TIjNTIjeTIjOwAPmqho+jI
kSTJkjTJi6yB1BjIQrSLZ9EWhFw/ZYzHZUrFNvQMiRxEsMjHk+RJfmQBDegBKBDKoSTKojTKo0TK
pEzKI2CA0xiZzWmJIZmnbYoNbsxFugHHNnFGsgoLK4gApQTLsBTLsSTLsjRLokwAMSALJCvGpgEP
tBCtDmGJS3EKiZnLKVzHdrHF78jEsNiBEjjLwBTMwSRMsGTK1HjKIKyIR0vFjrBCKXSKmXRIm1QR
nlhIsQDKwtTMo2RKDYACNADN0BTN0STN0jTN0zxNLmhK03BBi1kI3QDFjrCyhozMq/xGLYTIcUSQ
bjQ9DUDN/98EzuAUzuEkzuIUzQVQS7HAssrBMnGJGaDQjZSAjuasy+f8i91pTDuZTTnsS52sAeME
z/AUz/H8TdVETKlsCMoqjsZyzaqQSWbESt3EkCrczcZTyM8kz/wkTdX0TP30z9A0T9NQO0MEgNlw
Ta7cK57bJfmDSlzMwKCIqi98SK3ExpnIyRnxzf/U0A39T+QcC1q8kJK4lGpBQlc6w2KUx+6Mz9TY
ge/k0BeF0eIM0NMYUGwLDCkrCIjADumMUCKpTQc9xaGL0JqcpZvUi4kUjf6M0fDkT/xcUuOc0dKQ
lsWjS5pjCbRZvCy1nLxUT8h0CrnUUsaYUJfMCEW5TE3K0P8nVdM1BU0PxczQuJA4pM9MUsypSFF8
a4i0KCzG487B4BXSaFE2FdQljVLTmFLwoMsWAQ+MsFItHdNEBNLIzFK3EtMuRZIyrdPRUNJBBc4m
5dTgLNTScEO6uVDtOYpPRdUOTc6wmJktuM5HbZqMKwnNoo+/IK3srNML/DZXLVAJBcbRCNRUFVbx
DFXTGNXjWL/82dRhHU1PZdb9XE0cOlXSLAIdAAIvGE0osNbR9AIg0IEiAE4mcFLRBIIxQM0PMNds
1QEdyILRzIJ1xVbRrNZrPc13ZVfTdNOw2JXFyxmCurczRTIrw1X6vMDyCQ887CvTCNbR9FZwFc1u
1YFxRQP/e5XYh/XWihXNLPiA0pzXeA1NbQUCbm3YcMXYci3NYh2iZX1W0HTWlQXQaL2haRVNC3AA
mnWAKgjND6hZB3CAdkUDJqhZm8VZ06wCB9ABagWAoS3NoiVNFAAAC7AAAHBYNICBp6VZh/UCmoVa
B5haebVaAICB0sxXsEgJkRhB/vDX+UiJCy0Zh7zF7OyRC/TA01hY0MwCntXa0ARaqAUAFAjNqt1a
C1jaoK3Z09QBvx1NreVZpdVZm/XZvRXa0yzaox3NIkjak4VZJFLZlW1Zl0UDlHUhmQVNILhZ0PwA
wUWDIihdNLCAjUUDB0BcNDhd0wRaAKDc0NSBIVNa0oSB/9i1WwAIWTTQAQcATS/gWtBEAeKVXdQV
Xgfw2OJ1gOAFAgDw2eNc1aq4QBBpEbrYFKnBkMfUv3vs07fFwLj9sr8YQNGo2+UFzTFwgLBlXcS1
3M/MAuBtX9glTQtA3KIN3vztWjQg3aGd3dRd3dYFTfw1XeYdzdq9XdDM3cuFVija3GftXJcF3ZBM
U+Rl3uEFTf39WOe9W6Xl4KZ9X6Od2feF4NK0AIlV3dCsgssd4QMGVwu43Rfe3Yn13dW1XrGACFfC
Q4UKQkZtz6fYFdqLqRUl31cTCDzMie30ztF839CEWjQoWo/14BaWYgVGgzGAgeqlYdNUXtFEgQ1W
Xg8GTf8oAGEdjmExLuEGptmqvWGWzdwimmBmrWDOnWMZEl0CHloDft3brd84Tt7S1AFsNWHcpeIU
Js0wDk3jDd5BZl0FPmSvrd7SJN3nbdPrpYpZ5YhDnErJKwkn5mQbdNsGhdslRjq1o0v1ddHQHGNz
ndzmFc0BhmLXJdrjJU0o0GI+7mDXneRAJmFCNuQGPlobxlwJxlg7ZoA6HtYLVqE9ptqdZV5cluHR
jOXTnGQXVmR53WUC3to+9l0znllbbtqrFVtNpgoso44OSY+KgxnDWkCV+KpYYbYO+TG5NRhEPGUJ
xRR3JIv1ld2dRdw1XuPRBYBkBoI3Nk0UaOC/lebQpOb/1/3fawbjhk7kOP7cPE7ZZG7mZeZoYXXm
FNpjNGZoGIji193dbC5aci7NbAZNYy5NhibNrKVhHfDjL87ixHWAdLVkm+5Z0hxbsECUkUmZKNCI
8mE140OIAhzq2CNi4/M9+Ns9tiOCwJjq2wlAYG1lB37fwz1emxbNgrZci/5Yr/7fA45jktYBk4Zf
Hf5j0Vzp33Tpiz7mJmJmkPZoz31ZHtpjcbbcdo1e0dRhoPXdiiZNmF7kSkbeMHZk1iVnnJ5YqMVk
0/TjHW6hum3sxZZl3FXg3O1f1ITkjGVkKY7dv37dzx5sBEbNuUZs0QxpHLrrVL1jCtbo0M3g12UC
wT7a/0mGacstbMO25m2229HuYPjtYMGl5bem4sKt17Am7qA+obplWm2uAtKdWeZN3rMOzUpubQBm
6QPObYje7RqGYN8OTtYW7oxGZr2W49hG1deGiS9Q0QLa45NGA+MF1w+wZetOXakVTvTG6MNVYUn2
W/6e2Mst2t927lneZegmIek+6NBUXS+oXyc95OTF6JeOcK7235Y2bvyW3f1WXsvV7pa26O6WY6pg
AysIgh1wceT7IPf+1NkezTGGWqgtZIbVWhSYbC/47tSsbYMQgxb3gAkgsjmSCjHAihcIAitgA//Z
Y5P+zKxVXiiw36INW+NFgSrgci4/Y4sGcBXWbiawX/80cFr8xN8xmOJI7nIv32IdMFctN+jwtmwV
Wl/JRgM0dt3TxdbkxVbLBYI291kgCF48R2PjhujJjuYpp9kzvvIo1vI2H1ptXeQTT2+UbYId8IAG
QD0WhAorAEkIcm8bv/EcJ9cdf14mOF0U+GjXzuvf1Nob59nwzoI3XleaveFGF06U3YIdMPJOdySp
uAHUawCXuAL8gWaTxtvqVV2eHWiehXae5XAoPnG3hujTJF1op/OiXfbljvbFXe6hrQKbjejQdPAH
2gIkkIr19XFoD2dtN91vd4A9t2Wd5VlEP+NuBk1lr1lmd3eulvdp1+3DtvYUhwkxuAEF6HRP+wKp
YAP/CBgyAdiAFyCCY1cg9471rXUAWrd1nx7a3IWBw/XvTn111FxziEZdqOXpSP5Ymx3OQr2CGeD0
TueKGVi/LZj5hd+AHZiCJ98eaH5pRa8CRYfRDHdhxX5ppBfOLDD6c2cgNlCABlD3pwDo+8Zopg9P
L8jwMVB6uBZ6on/RGW0CD+h0CBABF3fxhnd4AVh4Oap4AsJ4LWZulb/uA77d0EZNGq970TTpPAcA
OgdNJkABWH7fvt/1aLWCDSD2F2gCGI+KMpiCHRABiG/7HbB45wF69tZrp2egGRgyqXeKqtd8C27K
NCB7T7uAqh6NK1ABrVh4AJD4HXDy/on70ex7Kwf8/58d/DFAgeotaNPU+5yeZeI1fNMcA2z9fSA3
CsX3tAnYgflWcSvQdLZHPQMwgTjrpNse/c1H5wmaAk8DfY4Q/e1X5itQ+CEzgBdQe9SAfE0//06/
gBl4glBPn9of/mgezuQG8rjvcihw2qMFCAsO0BAsaLCgjoEHFxbkkmADgIgADOwQ4+YixowaN3Lk
eOWHCAMSJaroaPIkypQqL1rRwPAlzJgyZ9KsaZPmAosrd/Ls6fPnl5ERGyC5uKPGzaRKlzJtykVk
RANE2PzcKebJjg0ChEZUoLMq2LAnNUCZacFClbRQUADQgUZgzSIAmNDkwoCsWQAO9u51+1ahzIQ2
V/+MpJhGrM+PECOaQOwY45YZO3YgsWJli8aWTTdz7rz5ANfQokeTLm36NOrUQoke9ez6NeyDJCRO
+PJ458eQI5/c7r2RzY3JPyxbOZwRr0wLevk68At3plwYNe0ij3n2peCFXg5mp6kg6g7jvneymUJE
/PiqO0Zv2EChQuz48jdDVW3/Pv78+TUgne//v0wDRKQCVemt9AURJvxgYHpb1Ldaew+UlZwF2AFm
0HYFwQBAETZRN6F1FTIEBQAgEgSFAyZ2NxMQAoTH4HhW7DBFgTBidANpO7gEII89FoTABe0JOSSR
RRp5JJJJKrkkk0lqIJoKYrTmI5X+4SBAEzb2lsb/BAJsMCN6Wm60xVaibVAdTNeNWOJBKE6IggMd
eniXiS+pydBZYxh0J0ErymSXmL3VN8EMT5RhIxvfhTbcjvKNkVZaWcSUhaQLVaFnlTLlFCinYm3B
VZRG9SdfFpBWkeFLlzJURaZ/MtApYk9wpYAHM37F6QyiQZAGmnaKiKcFmBKkJpys3vShWb9auhcM
TOggkLEIXegqrIgpKhQELwRhRY2ObfGDBwGE9oIbms2ng1Bx+spQc63GtGm18a4kK0m3TimfchI5
gNZL7R5UBQDRunsQoPL+lMYLpBnw5ba3+rZFECIIOKtFvQILUxXMOgstGiR+oAPIINdF50wooBCT
/xdw7oUCqgUB8cGcBleVBrhlhqbAl01YYdtOW1jRxA66jeYBS43Gl5CpbNVJEBBAsOvXwAvBKzPV
GpkwoMNu3BvfWaY+t5AOSwMscNQEFVx1T7lBYBoEG9xgBVhsWEZE0A9yJQBmbli8kMkoq+wAy0yf
NbgFMM+EbNkMnY12TxCbcC1pG/BsUsKjLTDSBAWaK5+f/hLkRaX/Suo5GlWEblBaPU7NuMxpCBAq
R1vHxufYBmXRckGn1p477gSZzuPirPMkdxAqXFBa3iY94QGRdocWgVBTYLR34ognTvCrwld1VdBr
i7bgSQ0IJYAHP1xRrkQNfLX50ReOoS4aDgDhAP8ALxteBF9w+oX/Xh9YsD9z6PKf1VULDMmr2hey
lhHZwYZPTHDAdjK2IQdkwV8w4MuGjHXBlTlAg3yxwOniEzzt/eQKQDOBViQigEOZxHWo8dIOuOUG
7wEgCMdZ2vWsd72GZI+EYjHhDlSwgQkAAAIKzMgUPGCCHRDhfBlhw1YMcED2xSYhIXvWr/ZShLJc
xwuAIwhb3OLFk6EhjB2rHxghOMAjruQBbnQj+EDiBjA8AG5uUMMDDviDB4jAhx1h4GsEErILSqd0
ALAAFOjSLrl0yAvKYRUj0eDIgKEhIWUZA59E2EM/IkZul0kJDQvTnuA04YAXyRUAZqAR6pVNhzv/
RMMIOVm1BghAehmhImzQxRwAkDF+vbzOitoVTLf4zyAOKOR8CNiTB0DmAUpwww80cBEiSNMNIgDf
9OwoywWOimvL4YtfACan+LmlcAUhEavMSZAsUPKYBfEiDl0Ty23CiDiWYaNG1tPHVcazlSR7JQ/p
yTqibASXr1kRigznuevw6X9vUZZD90K4fa0xLMzEiBKkGU2MqIAGcsyICh6gASWoIJpEcIMKRKAB
8ImACCoFAw1EUJKLpFQEYLhITFeaHkC6hk9AaIsho9Uu0nWQnMY8lUQHB9T5zFOgrCPCBbp1EVZG
zZU7bKpTO1WUghqtitO6IEEWWqGGlhOibnHA/8eu6DT/KJMnF73IFpi50Yvg8QFq2IgGMKOBvKqh
pW4oQx7d8ICS0KCOenumBk5qBWYqoY9l0MBNfcNTz2TyOrszKlFZlVl2ouCKYfMPVrNKteJwhKoD
s2oONyla1hnUNX4Cq1GHVaFhogG2YS2rQYoQwti0dSdvdUNcoVnNO7qRhcfR6zMzElfMPOBQW6jm
D36w3C081wpKeAARjCvZbs5OWQ8NakHapU40sDOdhiNvO6GGhiIIS5OrFa1p3YXa6qn2vVVrrWe6
4wX8KRRqXZQf04A6RjACNZJoYAKHKgqW3y5WuBgRAQ1iile95u26Mg3sRZ97kejGda97PWljRf+q
3cdMtjN3ygK6nHbZRRa1jJSMJCYpWSyCXLB3rwmtfVkX31bN1585Zm1Xc/nN/oXXvyLCH+EA2D+H
uvgsvARQb9sI0pLMda46Pa7e8hbYLAsWrtD9AR0xQgQwWIam2LxNiTmjHL7opZAr9gucBDLj2uav
xQI5C/yYWt8fk3DHmepxVfeMUxGIIAocJTRGQALhjhDhzHrbCDU97GiNGBolUXAjp/DbmUeZ6l/C
otQ7gdChLLT3d57LQtN2G58oq+QB0Y0mdKUZ18guF8t5vQh2v+XMLgP3y9ZUga7dcGnLaKDSvUnz
ZkrVadSh7tOfFZgXTlXe3OmgCDaGTWijEF3/4zba2FaIrrE1AmaNzPSWrx7OSUbMkShooNzy8nOV
AH1aQf+gJHE9lF9d6oaM3rWkkHY1Rh772w3TgLrP3SdHBl7a5AZK0wCdH6Yy1k8FV+Xc2rQCiMMd
BYa7gQh39fhFYKqCKJQZfGo4abns6NIfsDAKKlCBNo/NXYAe5APnnZ98BX0RdmP8oittiaEXS/KR
bkQJADhgSDcCklc/gAYdAcNwTeJMdcMK3lSSd847cs2pMhcjDwDDD1Cu4YwQ2qMhx67Co4sRPEa2
0SzvOMA7vu2MEKHpGP823JQQXTtKV+3aZrjeUS7svXPE4QDdlw7gdN5MsZrPO505zc+JVh18/wAA
yIy3zq0JvrxC3ctuMHu5om7NvebtsUkXNzbvDdctRDajtGa9RmoNBjVs4a5loC5GwHD7mxowIwY0
rgFNiRKr+wjrPBa00DcaXK5PWSOHUntG0n5mna402LWu/h59P1I17HU4NAD2dW/KxyiodDiGffm3
pNmSLVxX3YZ/OMjG2arGO367kYeJF0I28f9gld+LLcNH8VqiIdxFIFbeqAHcSN9xnFS7RZPTFRYD
lpQGOF2iuRr3fVhG1VtzdVhhfd/ppVQ0PRO7KdpOEF+PGN+fId8EItrYcVkBil6iOZoCTs+CJBce
4VoB0tXA3VpiscRdcdnXAddFeVSYcR018f9e4QXZ/dEc/dUfmkHeEl5V5j2WBgwWNGHTb81aaZnS
DE7VD6gBBWqYhoGh50XfVFHguGVZXN2VhAkW+1UTYFkTyk2aSZgg8PwTzc2TBtiRChBBC94aSsFg
DGpEF+rNgrDbXl3URSFiFa4ShYWcSlVh1/XahkkXALwRwIVU0yVhFEZhEzqhYyBbJx7fSfiVNekd
FmLUlk0YISrd9C3It0UiJZYLSOxVK7pgx9HAk1CXr2XZHnkYAIDBpTVdZKmEHQIICmJeR7xVvQlg
EL7cSUCf17ni2n0dHdmRIs6RYQkg8wEidjFfhn3Z8gGXGpRjrwkeRrzfKDIePoHiE65jHmb/HjOq
QEZdRBzuGyBu4S1mhDQKlhVcmhLwIiUCpECaoQu22xY8VkFCX17Vm8EljxUUFtWV1v7l3DHyn6DJ
1F8VmxzuWx9Fk8HdFMbxowwqXcG9ob3ZFdzhGnWpZN05ogsG1mIlYBmqXQ/+n76hFDoWDTwyYTv2
Bh2ihBqcG7p1xJmNZAGWn1iIYk+eYOb1oE4C1seVxKX9IF0VIy7iIOrZowpoFBrKmldumOj5nJbd
FR4t5Ob5jEoGlwgkVz4OX0UenwaUQA3UpV3eJV7mpV7uJV/ypQvoXFdC5ejZ1Oh5WEkQgbsRwU4S
4DR5WFtihC4mlgrclC7C1IdNJkjdFGbi/+MEKqY1hdxMeSYYiIBIVVpk0qEVLEBfriZrtqZrviZs
xuZdEsBP3gZjqsRzGRwNAEDMGaRYThXMbUFXhsUOZIBsHidyJqdyruZfnsRz7dVMXddeHUoVvtFH
EqAIcKHSYeJM0dFeFdZfuZF3TuDAXVR20tReyZR07RP0nWdhVeEzddgEliBdLqd95uVfyshk7Cd/
9qd//ieABqiA7gBvuGO8sMEPDKiCLiiD9udeNSiERuh/2tBK4J49Wihw3V6G1p5xYUbe6B7sXWgZ
mCNkRJ2/zVGIcuNGBaDehFtPSImExmiE5kAKyICM3iiDFmi6bcREGghWasSPpkSPcsSPBv8pSugn
jiZpgOqogTZpk64HAOxAjpmeRGZgSB2KSEFWlraEPUoTM3EgwF1aLZ5ZC3LfSeliNM3Ub20U0Tkp
RrQBD4DACGiBm9apnd4pnv4YlEaElL5XhG2Y3kXWrT1ApREqrlHmgnypSnLpHuIamWZpFZaEVOJa
AmKiSLmhncIpCGzqnOapp34qqIZqteypRPQpfJkSEeji0TkjZDqdBmDpLGrYW52ol1FXSpUhSiUq
P0pTo7qppm4qp9KpqA4rsRarsa4EqY6EqTpVr6oB1AGbQrKqPRLqPn1pNcnqg5HpcGlkC27dmkpT
R4FUUK7WrwJrsB4ruqZroAhfStDeQ57/BFbOXsA1Wm+ChZE6VbIKxbLSUzPqpEqepbReBKEll7V6
nl/FlbYGnKEGFtupqDQBlh0t1r2KVrma67mqa1hgKMZurMKlxNL9wHt2RAsaIk5NYJoixsiu27gK
TwNsAJ9FYh8FpnoG7L691Zfu0xY4FmmqVMzl7K7W7F4RLD/uEyNyZJOaAQgsgZP6bE+oFKHBp1Ge
2Zb9IukhxnmehBJM7MbymTQC7JhEnU7Vo9dx3E+kLDXSU8s26ZBilLsx2vSw69PxxNr+GNIqrZNq
bUfk40tyRD8GVjT94HUhxlvqY0o4wdb6BNR9Z685La6RZlyRZmNNo1wF5qvOkQaoFK1e/2E1YoaF
7drIUh86/iiEQecLkiYa8hFkiSFkfV56auOuXe7l+lDaiuoe4e2vRYEuHq5K1K3wlAGhEeZoqpSh
gUFNEW/ZVRrxEi9KNdaVBW+9YWU+3iO7aaTmeh1zxdxiuhQgkh+hRVZMFRqXkdSGEZqhSacB/a6R
toDu8oQpQtbIgSPKfaNgHQpidtke9duC+BUendnHRlO1YgZgGRCkVmGiwi1wCiximSUz0dHHZWde
3Vq/NqPa1S9K2W61zG6o/oCLmkTgrW9K8K6OgZiXwk2DfYofmvAb0pQf8uqrBvBhddyqTk9A+ky7
hSfc5G7/7lFCdmz0lUSD0RH9gmtKKv+k2H7fRsIND2JGTmJEGIRBCzSxB6eEwpGZDgdsH+qN+EET
GuqqwPLvNe0R+HSrdOWVwenUKpYW3+GsEoAnyCoXHAFndLExLPIR2Q6Uy0YxHn9w0rJOEQLXX/3V
pQkhXNksrGpYm5LxcJ2xh1XhHFKgYIHdF0dXHvXxMrIQ0R0KGFDT/Iac3oAnrkWBrbqqXsHcRpCB
DdgACJwyGeTxMpLbSmXUJArg+lWTXMURF+cqSQ4y3LRgSX1u/vIvxwEim15TIPdjXF0adZbUq1Vv
GVDTNrLsHbOyNGsECKNNyr4neI4dL/9A5Bpy3iDy22JZIFbi2/Ytc2FlFFilAOpUJA7/5w5ebvwu
ckncWhkU1iZuhPpOc2lV2h6qJKba7HFcsf3ast5gI/9i00ZNqj/6crn4Mx6F25X14djFodiym4bJ
UbiWC5UtSKPh1MrKCwZ7MInq80VUc9X0cXb6c8HOojaKwC7z6jez3kV5LfN5YceVW3OZM0o5sgt7
nSV/20xxaRCi1PoB8SOzhKFB8CBzRD6TdEaI6XA2oEqdFECLWXPhIPSp3WIlIsf1o06hKbeCLfgU
1svd8/Q03XAClkeR5k01IKGOXWIBVkcZat3RAB1F2OpqT0ivbz9yRMHprklXjUwJp0299ZVqM9iG
40FixsuBRDCKs7Bdda5Bo07LNcbN/2f0NaQ0UZPPkKZwbcFLQvBH7uF1IbFdT2D6OfVKlEFApqMS
jOhdJc8UIRxmkKg53tQjrp06a+gcjVnu+Z5VloF1qVtelZk9KgHcFCP7sVBkOStLvDZk3BRr1zHj
7LXu9jUrHm5gVw1iopzL2bXHnRxdoeOf3tFJgVzHAS6YDRx6T5OhAeBjphw/WiVi0kC91pFAd9w1
DWUBlhT9/uAX7ltH2RHYwQ1I7KRqP0yvjsVJBXKnDG6oWvedDhbklmyFB2Lsql3ksm7smi/UmW66
brd9cd/aPtZdcWmn8HCCZ9WiCWnxwspmEquE2+k34lEZjObObfZM9WF0iW0EzzNmPP9mX4X4Hjte
XLWtUWapARuIiq+4k2/tjNfpW/Ug7SEmr8ZcNG1ZA4IsM0HwYNUrsYr4k485mTt1lLvplK93SdXj
W5pUNW25TX6oLjb5p4p5md85nq8vEWzVp27j17UxPu40TnnULwu6RnMZKWdlsRpBGOS5oz86pK+W
SIEEVbpaTDGTWkuk2gWwXBeWoQnvddWbIEa6k66BFGhEF3SBG0jBGpC6q78669hV1uaeH/oxS9gR
icpruUA3XN1VJoM5rLtjGNiARjiB4QrBKge7si97oNA5s4fqGqwBGYTBGWDEGUAxEzcxsV9EGJCB
sbtBspPBtSc7t68yuT87uqc7Stz/prqLqhPYgBAkQQusMhXYgBMIQQtUO7zLO7GfQQskAb4brg00
cQvYgLwbrr8D/Cm3O8M3vMMf67tfBBX4gBs4QbIP/MRfhBQQuxAYrht0vBsMvBO3ehdwvMcLwbY/
vMrvxNVOI9O6lWPMOko4u7J/e0b4QBNTfHokAdrgvMHYvBNrfBKgchgAPbEP/EV8u8hv+7CHfKO7
Qb2vvNQbo3bOkU8seQliPTcyvM1jBNKf+200fdUgvbwAvfrCO7UPvNE7fdILvLZz+9E//cZPPcO3
lErlDfcSJkrJ1K0FL3gqLz0q5RwR2vOS3Rx1VPcCF/qOL/haky6aLzSRLyRCGM2v/7gPSIEPkD0W
+ADnJ7sTcD7If7wPoHy3C8Gqf/7oY4QQjL4TnLrqT7y9XwQW2EDqu4EPtIDpq/67nzrqYwG4xzvn
n0Hme/zs174PVHvFU4EbbL4PeLzok/7Pb/u9u0ELtPoaPHHJJz2xT7/tu73YN/30r8HC0726W+EP
X7UmQ6PRIRdKFex0ujDREUEM46AJf14f3Zq+GfFjJSCwcZn+NypAaFDiRsUDNwcRJlS4kGFDhw8h
RpQ4kaLDFkLcdGnhhkyLM26k2HBDxcaaMC2cuBGCkQqIMGFEOmnRxY0PKSoxakyJ0IaNM2dakAFK
M4lImAp7hlmTBOMZG13CgLjpw/8n0J8z3RRVedONTyw+VaZcOdJlRbMRnfS04eOgkJ4+hKQs+vYg
1Z4pfbxk6ybMXiEtbAhJcpZwYcOHESdWvJhxY8cOH5Q5KNCNZDBENLgxOHnLlswHDXp2Q3l058+a
tyQMvVm0BhVWED6I0lkFDc2SS2uevaW2aNCPgQcXjtDjQRtU3HwkE7IrTTdOUm40/jImxufRee40
jrxrGCeDDwY9mvB4eCwvBZ88+H06+/BkuoiM39XJS5JupHcfDhF6coUf/wswIioATEK7/RBMUMEF
GWzwsM1G+8ENETRwLTMINTAtNjdaS60033Lb0DfRyqDhgQdse6DCClXQDKEMNVv/0TUQIXTQxgbz
swGvntzS7zr8eKLuxx/zM5C8MNrTzgYhjwxPrcDG6687KfULSgjknlwLyOluHDK4kKiQorguySzT
zDPRVCiyyaz4oUU3rLgQtwzBgDC0zGAsrc6D1HjAw99GzExCDg16AIyDrIjCRc40OxTOKPb8Lc1J
FRvzKSesm88H7oy0VEgp+7P0wCWnk8I6/M4YL8j3DuriPJGGXNJU4j7CVDqbDjojOgBJvbEL54Tr
AjoAKS3W2GORpUjFLX7IDLMtrBDBoGaZBSA1EVTg7c4QYVRBhR9EAMBRQD9rjQZmBdXACiUegA1D
GsBodt12J8y2oGTxjQgw70QK/ymMLnzYSCMsqEDpuSWdcOkoUFMKyVauuKxSijDGOgliH9PqomCo
YJWS1BYmHiu5i1ptgYr4UkrLu7Lybdnll2GOGTQrVCACISJE+EGNQZUQgQgi1DgI5ygkVMNmoIUO
2g0lfogUoaJtdsPog8CNeunaYHNjUDfihU0JrG8WgWiZX55JCIil8MGJNXbqQjAsnKPCJinWWOOm
X1t1Ttj4kESI7oP+1nVTvw/8+yAqBKPJ7rwBXyM5Jwb3mwyEumCKu5HmdpzszTnv3PPganysDA2C
jvPz0x/LL7in3FhjTNRhj1322WUO/bEfVMyT9t0nUh24r2wwmffhiS/e+OORTxBe+eWZb97556GP
XvrpXw4IADs=
------=_Part_480_15606254.1102468026652
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

------=_Part_480_15606254.1102468026652--



From rohc-bounces@ietf.org  Tue Dec  7 20:29:38 2004
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 UAA26376
	for <rohc-web-archive@ietf.org>; Tue, 7 Dec 2004 20:29:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cbqkr-000730-Hx
	for rohc-web-archive@ietf.org; Tue, 07 Dec 2004 20:36:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cbqcc-0000bK-H8; Tue, 07 Dec 2004 20:28:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbqYV-0008BA-Om
	for rohc@megatron.ietf.org; Tue, 07 Dec 2004 20:23:47 -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 UAA26030
	for <rohc@ietf.org>; Tue, 7 Dec 2004 20:23:46 -0500 (EST)
Received: from mproxy.gmail.com ([216.239.56.241])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cbqf9-0006wK-NK
	for rohc@ietf.org; Tue, 07 Dec 2004 20:30:41 -0500
Received: by mproxy.gmail.com with SMTP id q44so124600cwc
	for <rohc@ietf.org>; Tue, 07 Dec 2004 17:23:44 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=ZDXzmnkGl6X2kY/S2fBfrxks/DNxInuH+8zhJJJ91bazJLOo/uxmciAnebOdgQYLsODwNFehbl6UB+4Hpgt6xp8gBiH54ZyGuH2s8i99z47ipwsDPqrQuuje25BHoDIJDXNFm34tM/UydNsXfgrXhiFuFgZk2pvjcXmMSqrIFiA=
Received: by 10.11.94.63 with SMTP id r63mr147034cwb;
	Tue, 07 Dec 2004 17:23:43 -0800 (PST)
Received: by 10.11.116.73 with HTTP; Tue, 7 Dec 2004 17:23:43 -0800 (PST)
Message-ID: <db95d40c04120717231f86bbe3@mail.gmail.com>
Date: Wed, 8 Dec 2004 01:23:43 +0000
From: Pedro Fortuna <pedro.fortuna@gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] Re: Review of draft-bormann-rohc-over-802-00.txt
In-Reply-To: <550877E8-420B-11D9-82C1-000A95DC4DB6@tzi.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_484_16579352.1102469023702"
References: <3F2E01E1D7B04F4EBEC92D3FA324D8803857FC@rsys004a.roke.co.uk>
	<550877E8-420B-11D9-82C1-000A95DC4DB6@tzi.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 441f623df000f14368137198649cb083
Cc: "rohc@ietf.org" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Pedro Fortuna <pedro.fortuna@gmail.com>
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: b5216aa5b0df24d46eaed76d4f65aa31

------=_Part_484_16579352.1102469023702
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Dear Carsten,

I've carefully read the draft but there an issue regarding section 5
(encapsulation proposal) that I didn't quite understood.
Let's say that we come to the conclusion that 802.3 LLC+SNAP
encapsulation is the best one for addressing the padding problem. With
this in mind, let's analyze the following example scenarios (see
attached gif):

Scenario 1
|  PC1 |=3D=3D=3D=3D802.3=3D=3D=3D=3D=3D=3D|  802.3/802.11 bridge |~~~~802.=
11~~~~|  PC2  |

PC1 sends RoHC packets encapsulated with 802.3 LLC+SNAP. The packets
arrive to the bridge where padding, if any, is stripped by the bridge
and the RoHC payload is then sent to PC2 encapsulated in 802.11 data
frames. This scenario works because we can make PC1 send packets with
the Ethernet encapsulation of our choice (i.e. 802.3 LLC+SNAP).

Scenario 2
|  PC1 |~~802.11~~| 802.11/802.3 bridge|=3D=3D802.3=3D=3D|802.3/802.11
bridge|~~802.11~~| PC2 |

Now we have two PC's connected to 2 different AP's, interconnected by
an 802.3 link. In this scenario PC1 sends RoHC packets encapsulated
with 802.3 LLC+SNAP. The packets arrive to the bridge with no padding
(since it is 802.11), then the bridge chooses one encapsulation type
and adds padding if necessary. Imagine that a set of particular
packets are small enough to need padding when crossing the 802.3 link.
In this case, if the AP chooses to use DIX Frames, then the second AP
will not be able to tell that the packet has padding (due to the fact
that we aren't carrying IP packets in the Ethernet frame's payload).
If this thought is correct, the padding will be transported in the
second 802.11 link, falling in the problem we are trying to resolve.
I made the following test: PC1 connected by a 802.11 link to one AP,
connected by 802.3 to a second PC. I sent a 0 byte ping packet sent
from PC1 to PC2, and after sniffing it in PC2, I got a DIX frame
(source MAC=3DPC1 mac,dest MAC=3DPC2). Is this a general AP behavior (i.e.
choosing DIX framing) ?
In this scenario the problem of padding isn't resolved because we
can't force bridges to use the Ethernet encapsulation of our choice
_WITHOUT_ changing the bridges software/firmware or some kind of
reconfiguration (if the bridge allows such reconfiguration).

So, unless I'm missing some major point, choosing an encapsulation
isn't enough. If that is the case, please fill me in on the pieces of
the puzzle that I'm missing.

Best Regards,
Pedro Fortuna
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Pedro Fortuna <pfortuna_at_dei.isep.ipp.pt>, <pedro.fortuna_at_gmail.com>
Computer Engineering Department, ISEP-IPP
Polytechnic Institute of Porto
Rua Dr. Ant=F3nio Bernardino de Almeida 431
P-4200-072 Porto - PORTUGAL
www: http://www.dei.isep.ipp.pt/~pfortuna/
Office Phone: +351 22 8340500 Ext. 1775
Fax: +351 228321159

------=_Part_484_16579352.1102469023702
Content-Type: image/gif; name="scenarios.gif"
Content-Disposition: attachment; filename="scenarios.gif"
Content-Transfer-Encoding: base64

R0lGODlhwgIyAXAAACwAAAAAwgIyAYcAAAAEBAQICAgMDAwMDBAMEBAQEBAQEBQUFBQUFBgYGBgc
HBwcHCAgICAgICQkJCQoKCgsLCwsLDAwMDA0NDQ0NDg0ODg4ODg4ODw4PDw8PDxAQEBEREREREhI
SEhITEz/AABMTExQUFD/CAhQVVlVWV1ZWVlZWV1ZXWHWKChhYWFhYWVlZWn/JCRlaW1paWlpbXFt
bXGhWVlxcXF1dXV1dXn/PDx5eXl5eYGBeXl5fYF9fX3/SEiBhYn/UFCFhYWFiY2NjY3/YWGRkZGV
lZWVmZ3/cXGZnaGdnZ3/dXWhoaH/fX2hpaqlpaX/hYWurq6usrqysrL/lZW2trb/oaG6vsa+vr7G
xsb/srLGytL/trbOzs7K0tr/vr7S1t7W1tba2tr/zs7e3t7e4ur/2trm5ub/3t7/5ubq7vbu7u7y
8vL/8vL29vb/9vb///8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAI/wDdCBxI
sKDBgwgTKlzIsKHDhxAjSpxIsaLFixgzatzIsaPHjyBDihxJsqTJkyhTqlzJsqXLlzBjypxJs6bN
mzhz6tzJs6fPn0CDCh1KtKjRo0iTKl3KtKnTp1CjSp1KtarVq1izat0aVIkIDWB/lKlp5ccPNRZV
aCDCta3bt3DjxtQAoK7dB1to/qibl6KVuj/kCh5MuLBhhnsBiDArou4DmkTAgqEY5QHgw5gza95c
la4Ggir4Ji0T2m5gzqhTq169k+4DKwOtWOkrkMiD2w9oELR9W0OUgZFFqFGBW8lAMCJw5x6oVgWN
20Qia5gsMIoG3CrGHkxc+jTr7+DDi/8PmRiABhqwC5a+XVeFQBqOLQMw7mbvg+vyAVC3jPuyG9d2
lSWaG0rc5Rh1Bf0gwmz+jefggxBGmFBjdgHwgHsC/QUAhqVtUYZlHFooUGIajEXEZZXh5YYaln32
X10ibMFWYnl9aB5sJ5qn0BYNSujjj0Cq5lV+OroB3wPaqUFEXiciKZCNxiWWnhuWeXecZwK5pl19
okk5EHz6JcQjAFYGaeaZaMplxXN1seXaQaWBBdZlNA5U5ZOR5efimwPVyadAY7KF0JhlpmnooYgu
pcYPNPw20BYtvviYQRTKKeeMA1JJphtg8KfBD1hKSpCfIj7appg9JqrqqqzyZKMIBLH/qOORWy4m
oJMG1SnQnY09gNaLexY5omi09pmpQYS2quyyzMZEoQqTbUEXAGxpiCGYSoDR3oi3waarpoHxKWuw
Lg4LQF4aaoCWFZGiummz8MYrL0idGlhXuRSyV2Sc07r47Z1xEsdflsJyea5A68mnoruFzuvwwxAz
hFx+FxbEpoUYvqdwxj/cRtttpyWHcYqTJQdrnx6j7JgICA4KcsQwxyxzQVts0TLNtOEsURk5TwSG
hzMHLfTQRBdt9NFIJ6300kw37fTTUEct9dRUV2311VhnrfXWXHft9ddghy322GSXbfbZaKet9tps
t+3223DHLffcdNdt991456333nz3/+3334AHLvjghBdu+OGIJ6744ow37vjjkEcu+eSUV2755Zhn
rvnmnHfu+eeghy766KSXbvrpqKeu+rIxVOj667DHLvvssIcgsxgF0K777rz37vvvvEvQdAjAF198
DBBrAAUazDfv/PPQRy/99NNzwcBJEz9wcob4WclbxQdJe1vGBYmw/aMLI2R+TFZoQP378Mcv//z0
1+88ADZ1fBt9tfXmqBtlSM59/ncQFvXMDexy2QHXJ6b0kYQBXLCfBOsHhXLNS3kTzGD8rHeS+2yh
fS76kApk9K4TLQmEBhHhFipDvoGAxSBgmI5CXgiT9mnwhjjMof3wpxdqbWEvjirQkv9Ckx6w1AyI
CFEDXXoGqUkh62DqaSHNoFgSCOrwimioYPKWh8UccrAk7NLOXyajFpTtKmN/6dlzBqIEJxKEhhGB
o0ts2MU62jGDPJyJBjKmgZOdZyDra+OW5MhG9uRMf24kCI8OyJBFnsSKd8ygFh+GwUhO8IskCWN1
wvQA7zhSNqY64JbaeBBCckqGRFCBdQaYJRdJS1AqoaMlZ0nL5+VRJnt0Iaw+RJuOrQiW/7GgnX7g
SED5xpfhoyJzMBQjgWGomDQQjkggWcv5TdJhlaym/DBJErBYgYW7spIDEZZIRbZRNwYxpSM7poHZ
XKeVboCUFE8iS23as463jElliEn/nGhRMYEF+VDDAKVMbg2qoMHcVSdJGBhHEoeRHKHmPal3zQty
caLU4+ZI2oib9DiwkwUpEP8MghsCulCY8TzYXqjjSCMupyX1bF4RdAAELzxvpkV4nheAoIOcTg+n
1MvCB6IHBR3oIAvPy4JRbeq8mdb0fVkAQvSYcFFb1kQNAgQfpBRZUFNy9YDIfOIBaai9k6Z0C2qB
aEQjiFGKohRe2Wxr9DQaEpHWBgCweQ1BHjDSAqFTIfCZklmnmJewUikv+ClnSmKKBgs4wLEOqALz
vODYyjaPCY+FrGShV1kHOICp0NMBCqCHAgBYwAIA8CkaYGBax/qUspl1gGqjd1ro/1XBATqQXj5h
Aha0lKGP8XQjpLakRBmiCqyKPWs6XQTSEX2GR3QZaUgkKtfnVVReca2u8+gKEuDayT3NBWD6QiPd
hIDvjShdpxtVRJeODdQkMQVCZJn3AQswDwX2RcNtc4sGB4yWvvl1Hn6bZ4Gh0na2aMgCAKSKBh04
YLKyve+D0VDf5jkYtM7LAmoDzDzMAoC/0NutS3iEIEEWk0BOhNRbCZur5J54sOEFVUr36KsHslW7
1l0xs7KLYzRw9yO5NOsfM4Qr4ph0VH/9z/ngyWLDsvczHbsZSmI6YOY5mHkRZh4MHpyF+Vp5ws6j
afNgwGHngVmmYK4CACR75eZF2P8CIFbzZp0nX/xyGAUO2DKIrTqT4YaSSlNaY3DnKdYWH3SszPWO
jBfJIkKvtcc53iKkt3u9khDnV5CaUY3dUEYjjVM9m/5LedWp0vUidk86zqT7murlAut3zc2Tb/Tw
TL0xWOC/1i0zGrzgAAbTurEcxi30igAApD6PqsAOs02FHT0Rt0SgzJkUA6nkHhE65MUGTSaiw9mn
5x4sCgA4ckeo2+PrxovHOP6xR4rLqPuc9AfEgc2H7mOpaC0sLM+Z53UsNR317vXUAunUe0fC2C1b
Vr+fbd5tMYzwPWfYsQYmrcOZV4TYbvbWzsP481w9vdpCj9khrsleVKAgvgZce6D/qnFo+M3MJWO7
Pi42j6XcQ1ZFe7svl57mjSdtbrhWFdLq/khwgGmkPVJnUWZJ+llWtPTa9LG8tVG6WdSwqHVZaenR
Ac7ARRJTKPhXB1uGAcKdJ2eyOyDi0BsD2P0bPS87j7Jw1gHH4ZzxMjt2DNTz+PNAzmeaWEEtNGgZ
GAD/KyJI/QeCynqsmk6QsiTx8GxR/A+mZAW2VP1Jk9f5pJvX82ahW7tBh1dMNY4GYmdBzcYe+2XZ
Dj/TJ/XMzfv1rnvdWLTTnXkatgDDOavr/k6cec4uGrlx3Pkd/7zHoW9WTB3ABDMfFdZflikAcA09
hvMdDUBAO4HFTmD7VtjN/L1t/+953/bfoyH4RBu+dou/rM9XN/nMWj73Z59TkH+f2Aje+/yhAICf
WyD/yeZmoyVruAdrt0V9edd719c86Dc06ldd7Kcs7hd7p1WBOsBwQFBZKLB7XqB9GVVpMBNTW7Y8
sPVly0NszcdrKFAFLMiCzAMEDDaCu6Z3brZ7aMAEC3Zf/Ydlo2Vr+XVaLeiCaKB2eFd35adbTfOA
zVNfFfgBDEZnGohhTFBfKHB80hOBrTKBzFNZFehZzZdgjgUDRuVYc7aFsPeBzJIGM7AlBlFwnvVY
qYdnnsVfDvaGb0hfEbdlnuWBUDB+2GeHX4hwnmUBSHVbduhZknVbZUhhHuh7SP8IEl8wG4aihFiW
WaflWUylYXk2hl6mAwAghqUFgNCDhayihQHoZj9oAUW4hQHWh541P/CHJh4gAGt4EIzFPFXAgYtI
P7kYPWOQetJTBcCocMM4Sw2YBmWhAhtwAXUhAFOwEEHwOhCwAS+wA01gBWw4HpToiAqXZ6y4igEI
crLnVpL2PjS4Wg/Gf4HYYSiAd7cFA1sGiyCoLE3QjLXYeKu2efrYdwNRBk2wAxugALLjaAjDO9M4
AzswBYIlGE8gAkiQBgmxjddXW+p4bO04BiiQem32PqS4KqZ4jh/wYPE4PWNgUxsJP7F4JmVQIbS4
Jbe4j5OWR1MwAxCgOw0gAmL/sBCksQE8WZO9Q5BcMQEw8pAGIZF7NgZsN5Lx830cmWoSaIUbZwEt
CAWllVuOFT8n+T5coACy0ZVe+ZVgGZZiOZZkWZZmeZZomZZqSZYB4DotiUD5CJP7CABBIAICEDsQ
IAIJmZMX8UFEsAPK2ACxA5GDMSZ24ZCE6QYSCQMtWASotTxXGT8oGD8dqSofCQCHyF+R+T5ZST0n
YDygGZqiOZqkWTy0+ARxKZeT5omvYwAmEARWwAYlEYlBsAMesAFBsBBpYALUuAOSSBWC+TqIKZGH
aAFfuJnUQ2zz15TlmIDS05m79jzQKT0CWZrWeZ3YmZ29swEYoJr7mAEVcgE//3AFPBGNr6MAG6AC
O4AE2KgUsiEGpQE7AqAAOyc9Cxh91ec8rCWKROWUWQiVRkhUO+g8XldV0xk9RyAAPLmgDNqgDvqg
EBqhEjqhFFqhFnqhGCqhdymcH5Sa3kl8G9IEickTXxCcujONHrAD1piNM1EGsqGiIrABPtmMQxA7
F/AFRnmFA8p5DsBFeMaf/dmcHeeHpwWO53ig0JOSZ8Kh3BNJYxCExZhhUVoF4IhjDZgTYlAWNyCj
vCMAX9BIfOkRSACjPCmUvFOPr7MDApGj0lOkAYpnu8iclASg3Tc9hggDTCB3boefGzSPrfIFFRIj
+BhJrGkXWUZ+H2d+bXWlP//hov/4Alz6OmolEMwoOxP6jApRHryDnikqG64DAeS5pvV5hMHoWXiq
p5LFfx9gVKxKmf5ZinR6XwioU3LoX7uXffLYLDsAIwf0kjnkYEFYWlYIg6QKaYxqFMhoBSr6BLq5
ocWzAdAYO5yqogrJohrSHrI5ENvohNTjBbW6gS9YgU3oqkIKdH7KKjcJUb6KQ1nJd1lgg8LIjbgI
r3GKT4TRBA3aOwbQBAzxBLApGyPKEFNQFwqAqQSxjRNVmYliihOlpECSBpO6rjd0kkiZU++ImUJl
YBXnWXjGX3roX162sV5ojEITjR7Aooo5qsT3qh4ZqxjlsKsisRrkYKwqd/n/pWYWAAXNV1sqqIO5
hX8zCGv852sJF0nH2iwqgAQRqbLrx7KW6bINe64OI7MZ5Il2OH24mFp1epLCxnEJBmtM2V/Laa9B
E7AFgbD3pLCIwrD3BLOqQrUTdJJeN1Rlx4qn2Fi5xXfzNYhd6Ic5dLQxg7b2pLaHwrb2pG5gYBaU
Zxa7MXUGYXjlxXgIRHQC4RWfshCWSwPaQQT/syijgiBIZxaUixxLNmUeekVZGY91m2w0SHd6K1ln
V7NiZrQmYRb8UwZmgSCGJ7kDMRwFUXm5knSUWxC/kqkaAHU1IbjaRLiGYrja9GMfogSVARvWURYu
IgIjJGMEgb1olWSHNSoo/7VHs9FpB0ED7YRWk3Id2rFVlTttkJJ0X1E+gQdTp6tDqftgq1tbXGuV
EadgkkWDRRClVwS4FfEp0hIY0asEJeIG3Ku9sSJH70tSSUccKOsGhrcQnTKpM6G81cS8aeK81fRj
2ksDgbEgWaIELOJCOXMy7GsnhyRMCvJG/yOoWUIbLBNMLOxEvoEr0vJvV4LCYKAGW+BbNfMo8VQj
QPMkNnMcRdwQcCtBG+kFFUe30JdsvMZgQPBhpae1tgZrQHuDWku7I8G+PUwE6ARvKVzDBFEZ5vsl
F1IobqQCGVMz2kEDNIBpScxGGpAXYPAzgLLEK6IGPzMWTfzHigTIG8HBtf/kwWgCwrUEvXjxW7/x
ANTBuL1LyQdBBEvmQA58wgmxx8zRTgXRTmsRXE/yGCRnTJesu7kBQmuhwPDmJPeRbyLwHJMBy9jr
BtahIKVri/X7q5hphwaWv/lVceLqsW8Ipzp4WlhrSQRMEcfLabpRyvFkQSzSMtjYw9VRH3CsSI8R
Q3b8AFGAVQsCzs/Ruc9BTPcBK3sEKroBKtibG9HkR84hQzRAcpebyEwLgU67sFDbtlKLMHKyK31i
JXKcQskhXZwsTJ/GwPtGzc/BSv/xQUjCvveMQJPyvmbhXSr8H2dMHaAszhiNMGKxaZQsAoKydU16
R08ahM9ThlmQejuVU1n/sIpekIv+2zxRBQQCjEXPPBG2cR2TAcrVDBrzpM0FTVLePLnvERiMC7xG
YiU9DClooQbo1MPaW8ofIs3t+71lMLwVoci0xMhn4si0JMLXAl5JLRC57DIts9CjvJB/fLxDTBBf
LdKgHE3s+8YdYxwanXmjjFi0YcZLRCWqzM0qBhYPwLm3Mb8M8cTV9QERR4AT9dMR0T5oYR0TfdgM
TGhIPSLdjD6Vm3JOfRpKQNqK9FzlUhZfAWWnQdSPwW+P8RxrUcEUIdazRNZmYtaz9GNEvVULk8oe
fRD/Q9S78sLqkWTCvdmccj6MS9Q0htETDCufnU6CnSUj9Ft5kdH+Qkx7/1wzSbwmuKIQkC1Xc6sD
H/CJi0oSjGInpGHae+K9qZ0goe10RWcFiVva953f863NlaEENePaamzYawHetKEE5JsRuG1Juh0k
vG1JP3bQFgwrwr3A1GzE38sibAjXdq1XGK27xTtkSmQcRP0Xj4HS/VjRqQbKsF3VKsLdoJ3heywC
9GHcCVHecuUFrPrPdmTZEKHAgPIYXoEwJE50OVPdlrxXA1EZv+EbbK3fTs7AUq3aI3LGAs7cjwFv
tQErTpLGGrHgkdTgQPLgkaRurb3AwfRH7KIcNTMpbQQWCq0cZqEck2IdciJuAZdV6ETDnkYlbFjL
W9DLgJQXNKwWfZTKGf99Moz75suR2PLtyx+qjz4OEeZ7Helh6LCy5rix3bQR6PRNUrgR5W9+HrBS
GTROb9GkSNR9Mp0CFmtkyTQsbXJyy/SGvLe9z+bdz2vL488b0P0YUBChwQ1h2wUhZSNB7DBU7A+B
45HuzNjzEsYecBAR7QmRjcIuEWB+R2L+I2R+R26bKMze7Hc06fKS7Xa07T7S7Xb07YgS7uJOtktj
7nWE7hKiASVQA/ie7/q+7/ze7/7+7//uAr4eL1awAAB/8Aif8Aq/8Azf8PpO7vHCAC7g8BTf8CWg
64eirCq68Rzf8R7v8RowAR8/8iS/8cwaM2zwAyW/8izf8iQ/ASHg8jL/P/Mlr7RM8wQ0n/M6r6Jy
DTW7uiFEce3IYuA7Eistc9q2HhHUXhWlYfOaQXUSYeB5nOyK1HiIpxFCjzo/vy1CkVw70kkbPd4F
4Uba20YkF7996ZQBBBXxCQBOjxlJ/hBgX3J4btxk3EexnPXmxRCCDjpbbxdAqRSfvRgIQfafwUvL
lPYLUd1K0fZ18fYRYvgIYffpC0uRgRFebyen8/cVEvgbgelsPetUkhyQktDb8xiPIS19JNIOTerz
DUiB0UYJTdDdVh/nU7wjYuguosDJccba02+qfct9BMrJQXNf0fc/4fh2AflL0TFfMRnmO/sltxgm
I8pGsrvUdh3oVOnE/zH24Bv63kX5pmzXqW0+C3PmkxFDrm7Y/+HXw28coQErvM/6nTMFDGoACrqg
zC90HEIESrD9APHDzQMibgYWHFjGDREVA91sebDFjRINbn40dCOiosGHD3581KhmoMQyD8AM1JBS
w4OKIgRyhGnwxwOZDTWIVEMTzAORRERs0QBUohWebqxUBLoQo4qTMZ0+hRpV6lSqbpBswLpBgIKs
GyRWBRtW7FiDO3uKACPCYJSKM0W6tYjxQZmPB92UNLpxZkyPH1U8sBLXIA21KlXSJLIRKsShFZXQ
GCxQBEINZjUoMRjRTU6FNBMaxUhW9GjSpU2fRp1a9Wo3GxqwrqohMP/MMlt+aBDo2aFBFQUrO0z6
sGJQg4lhQvyoQa1wji5HboFOo6KKl1B/QO5ocMtjmtePP/AoE/fHuUmJisAMW33YBqHXvw/rHaaa
LQzbYpeP14raurq7v9yJL780UMgN4twI8DLotqOJIqmCG+ik2m7LjS/ltOtrJsw8E+EBGpqCL0QR
RySxRBFdM9GgAw1SwkMiaKgwM46OCo6m4JI60EGOIMSNOd5iFG8hxYyqzqKXIDLQpSj++25JhX5w
6aMf6NuojMQASxG+9rJMsS6OdqLOQS+9zEgJ9IzczSEv8YJJNxWWOxCvFZEMECYVRNJOsYhapOFF
IDNLLIqOpPwhMN3/rPhrOS4XZbRRR1lDMUUVsKNBOkHdoC5N3QzsTcYbp3tJhSEhJAqMkvDEctPb
MpstI+xkWs7M4PDSka2koJxoIzVEoHKhl2B8VLUtg32vVtywE/MlMs30rD+OGlyOiE3TzKmgTHM1
8KvsMqpu1R2LkvPSTDW4VDaaiFLjVN4MNWi5nIiFN155iY3UxJIqnUu6i0RQyz+YpC3Qxo2SUsMw
9yDEVC19RZALJm9bFIGGBxSV6YFJK7sXSpM4nSmK4DTwzSUNINsJLQ+lA3FesoZVWTUNqHsgiiWv
6xBNmzPDyFkZMzqMr395ulc6ieb0DIyUpPvtW9wuc0PfN9WaWdTd/2hoaOGNWCrjTSjda7lrr78u
rd4UrWi1vpNO0lZboxT9CsSzH6KrSARjapsIENVWI2WznfoIjPTuUiKwu5UosKm8tbP7S5KU+Bts
sFh2nLTtCidCIonUwBNzmJLWPO3NEAQD4YfoxtOKv1MefcfKnQKqDMJVfxvwrzxHcHWDatPuB9Qj
57133sX+GqhWo6K6DKOHF5FM3xuFfHn41DBuqqNMvZZE0Z3HPnvtxQLe64jBuo3cFIlAaPsUmzdf
tcTUjoqiHk0Eg+v056cf++7rxz9/jtDXv3///wcgvO4XQAL2jn8FRGACFbjAsAyQgQ8M1gEhOEEK
VrB+DrRgBkUkQf8NdtCDHxTga0A4wvVwkIQnRGEKU4NBFbZwKiZ0YQxlOMPWiJCGN3wKDHG4Qx5W
kIU9VKEOgThEIgLwh0UcoRCRuEQmau+ITdSgEqE4RSp27YlVnKAUsbhFLi7qil1UoBbBOEYyqueL
ZQygGNG4RjaS5Yxt1N8FXgBHOtbxNG+04/zKkIY89tGPVMHjHwU5SEJuL5CFRGQiFTmvGWxgkY+E
ZCQlOUlKVtKSf4ReTMhmkcht8pKfBGUPRVcXinlNeaFEZSoZiLnQFQhB0DkOdBSzBTDUpW210Vvs
DII5WmrHc7CsjStD15SUEXMLrnxILeWmSmY203+3mdTGtKYRFUX/syL3+kuFIDKy8GAzJQ5LiU0u
dhKWSOxNEjuJvl7WNOwwJGG3wQw2w+NMetazfg9TS2igVRxQ/Qg4RTkKpkI1JG9NikX9EhRRfqSu
gVihTpXREV6uVT17VtSivvMSkugiKiYx50DO+lS2WETQlxhmJbsJzkcgNC6HtoUlKQGA0b5yyovW
1KbzyuhcPLKFd2V0ODPV5sB+yk+HlbRyC0KpXn4AIecwpFMXWdDQgHpTqlaVWN6C6kYUGlCLtAUj
zhFYngRTMJLWpDj9EiuaNJOTpoDHIOjKzkXatUyr1tWuIQrfhQykHFFJBGl61UhKtLmcLSznLy97
1c0C+xvPFFYm/wJpUUr+xi+OSGwl6VksXe+6Wc6ipi7IRCZHQhtaqLyuaZoVbVh25xTUkbazr4Xt
aGi6msQoAWCxxW1ue+fJ91jhI67VbXCFO1ziFte4x0VucpW7XOY217nPhW50pTtd6lbXutfFbna1
u13udte73wVveMU7XvKW17znRW961bte9rbXve+Fb3zlO1/61te+98VvfvW7X/7217//BXCABTxg
AhfYwAdGcIIVvGAGN9jBD4ZwhCU8YQpX2MIXxnCGNbxhDnfYwx8GcYhFPGISl9jEJ0ZxilW8Yha3
2MUvhnGMZTxjGtfYxjfGcY6tGjpY9o99Or4wWwAwZAB4SF4z0f8MWSjygCKLALhAfrAViAweIsuv
UT8Y8o+pQoQhUxkAQ4KyhEVQ5NkQpchPzhJ9tEwVJhNoIUMuX5gjrIEvgzNpLPoIEUKrhI80Ts13
6XNMlPkDPSvOVL/9M0x8+1uo7GSeAwEAauWs4DEDQATI2xGdp3wpoBC5zjIpsrSIrBgVeLrITaEz
TAFABCwDQFua7nJinYKnkkR60hLeyZRBhkwme2gmRVZRkWHE5OW0GgDU0TRmpHzs6wwZTl0+aau/
ommRDVnSvBnyam+94KOY+gHp4TIA0rOkoCx73Nm2iLXLom7oVSfVwRY3R6Q9EXUHe1pOKfWxt01h
MEiHyUMOzJj/753uiCyIyQKZd2ZsrboOfZrOqsoypoDNESUAPCr5BvO+J5xvm0w8JrA2NcIjrvBf
/ZvKG3m4wyKe8h3VG99DzrjGFQwRI7epzgI/zmCKHFXovGXkkBY5AGgwNId/GtSuzojHjWLxlxtd
5g7utbYqru9wp0fKHpk6p3+gBJ8jneQGMvq7wU7QiIe7fAInbRRgjqenO7jVE7sNkQNTa1/3ujNF
9tjDn/Tzg4M9ZnTpcrDJ7vV/w6jSslZ4kcEDnmu3PcD59vS3Kf7vLo+b8kVOT8KB7ga1d3liExf7
0Wd3eX07ZdmmXrjjFWwFpLlktOGjAWhh78pFs/0jZRbVh9Tw/5GeEFrRvIeJmV6G6bcSilDEV33y
lb985jff+c+HfvSlP33qV9/618d+9rW/fe533/vfB3/4xT/+qiwadcrcM6HRXLunRAH55Jv1lKQC
f/KTxvya9H1M+Fxoqbi//cgvlPhju6egv0kqNZj6Gxr4ssu6nZVICcmLim+im0f7uIzbAq+DCgms
P7I4QDqbLJYAj6YoAwdkwMWgQAzRrBN8CAx8Cg2MJDBYtYq5HQj8i3ZRjJlwLaNxOs7ruxaMuTXj
CBfcQLCAQYTYi4lIMsC6wblovx7kiCVJPQF5CiBUkZhTpBZpOYk4wszAjPdZwR+TFlEZkr+QGM0S
Qu3YpZPgs/+/0cBeGsKpwELtQLp1eism9MIL/DEypEA9TEG6apvea5U21DZBKgmEqMG9apNlqrjd
8T8X/IHOMEMLRLq8ojM42Yi/oMI3vAuC4A3PeDQY/LFF5BtIdBhSfAoVxENOeamFk0BMhKTIWolp
cw863JxSqsBTjETWmcQYfLOT+CZX1EQ4fKkkg0AudAq9ggoVHIg+1MWhSbJD/MUkW6QRHA+98kJE
3JyiiMCYU0ZsPI5J1I2SGJqXYcJglApqTI7lkMZl/DhtTEa66kZUnEPFiMNwKkf92QGT0sd95Md+
9Md/ZIHTOMRNDJnNqQ6jcTOpOEN29MFmtIhN0YyH2xiwKAP/DvjHi8TIjNTIjeTIjOwAPmqho+jI
kSTJkjTJi6yB1BjIQrSLZ9EWhFw/ZYzHZUrFNvQMiRxEsMjHk+RJfmQBDegBKBDKoSTKojTKo0TK
pEzKI2CA0xiZzWmJIZmnbYoNbsxFugHHNnFGsgoLK4gApQTLsBTLsSTLsjRLokwAMSALJCvGpgEP
tBCtDmGJS3EKiZnLKVzHdrHF78jEsNiBEjjLwBTMwSRMsGTK1HjKIKyIR0vFjrBCKXSKmXRIm1QR
nlhIsQDKwtTMo2RKDYACNADN0BTN0STN0jTN0zxNLmhK03BBi1kI3QDFjrCyhozMq/xGLYTIcUSQ
bjQ9DUDN/98EzuAUzuEkzuIUzQVQS7HAssrBMnGJGaDQjZSAjuasy+f8i91pTDuZTTnsS52sAeME
z/AUz/H8TdVETKlsCMoqjsZyzaqQSWbESt3EkCrczcZTyM8kz/wkTdX0TP30z9A0T9NQO0MEgNlw
Ta7cK57bJfmDSlzMwKCIqi98SK3ExpnIyRnxzf/U0A39T+QcC1q8kJK4lGpBQlc6w2KUx+6Mz9TY
ge/k0BeF0eIM0NMYUGwLDCkrCIjADumMUCKpTQc9xaGL0JqcpZvUi4kUjf6M0fDkT/xcUuOc0dKQ
lsWjS5pjCbRZvCy1nLxUT8h0CrnUUsaYUJfMCEW5TE3K0P8nVdM1BU0PxczQuJA4pM9MUsypSFF8
a4i0KCzG487B4BXSaFE2FdQljVLTmFLwoMsWAQ+MsFItHdNEBNLIzFK3EtMuRZIyrdPRUNJBBc4m
5dTgLNTScEO6uVDtOYpPRdUOTc6wmJktuM5HbZqMKwnNoo+/IK3srNML/DZXLVAJBcbRCNRUFVbx
DFXTGNXjWL/82dRhHU1PZdb9XE0cOlXSLAIdAAIvGE0osNbR9AIg0IEiAE4mcFLRBIIxQM0PMNds
1QEdyILRzIJ1xVbRrNZrPc13ZVfTdNOw2JXFyxmCurczRTIrw1X6vMDyCQ887CvTCNbR9FZwFc1u
1YFxRQP/e5XYh/XWihXNLPiA0pzXeA1NbQUCbm3YcMXYci3NYh2iZX1W0HTWlQXQaL2haRVNC3AA
mnWAKgjND6hZB3CAdkUDJqhZm8VZ06wCB9ABagWAoS3NoiVNFAAAC7AAAHBYNICBp6VZh/UCmoVa
B5haebVaAICB0sxXsEgJkRhB/vDX+UiJCy0Zh7zF7OyRC/TA01hY0MwCntXa0ARaqAUAFAjNqt1a
C1jaoK3Z09QBvx1NreVZpdVZm/XZvRXa0yzaox3NIkjak4VZJFLZlW1Zl0UDlHUhmQVNILhZ0PwA
wUWDIihdNLCAjUUDB0BcNDhd0wRaAKDc0NSBIVNa0oSB/9i1WwAIWTTQAQcATS/gWtBEAeKVXdQV
Xgfw2OJ1gOAFAgDw2eNc1aq4QBBpEbrYFKnBkMfUv3vs07fFwLj9sr8YQNGo2+UFzTFwgLBlXcS1
3M/MAuBtX9glTQtA3KIN3vztWjQg3aGd3dRd3dYFTfw1XeYdzdq9XdDM3cuFVija3GftXJcF3ZBM
U+Rl3uEFTf39WOe9W6Xl4KZ9X6Od2feF4NK0AIlV3dCsgssd4QMGVwu43Rfe3Yn13dW1XrGACFfC
Q4UKQkZtz6fYFdqLqRUl31cTCDzMie30ztF839CEWjQoWo/14BaWYgVGgzGAgeqlYdNUXtFEgQ1W
Xg8GTf8oAGEdjmExLuEGptmqvWGWzdwimmBmrWDOnWMZEl0CHloDft3brd84Tt7S1AFsNWHcpeIU
Js0wDk3jDd5BZl0FPmSvrd7SJN3nbdPrpYpZ5YhDnErJKwkn5mQbdNsGhdslRjq1o0v1ddHQHGNz
ndzmFc0BhmLXJdrjJU0o0GI+7mDXneRAJmFCNuQGPlobxlwJxlg7ZoA6HtYLVqE9ptqdZV5cluHR
jOXTnGQXVmR53WUC3to+9l0znllbbtqrFVtNpgoso44OSY+KgxnDWkCV+KpYYbYO+TG5NRhEPGUJ
xRR3JIv1ld2dRdw1XuPRBYBkBoI3Nk0UaOC/lebQpOb/1/3fawbjhk7kOP7cPE7ZZG7mZeZoYXXm
FNpjNGZoGIji193dbC5aci7NbAZNYy5NhibNrKVhHfDjL87ixHWAdLVkm+5Z0hxbsECUkUmZKNCI
8mE140OIAhzq2CNi4/M9+Ns9tiOCwJjq2wlAYG1lB37fwz1emxbNgrZci/5Yr/7fA45jktYBk4Zf
Hf5j0Vzp33Tpiz7mJmJmkPZoz31ZHtpjcbbcdo1e0dRhoPXdiiZNmF7kSkbeMHZk1iVnnJ5YqMVk
0/TjHW6hum3sxZZl3FXg3O1f1ITkjGVkKY7dv37dzx5sBEbNuUZs0QxpHLrrVL1jCtbo0M3g12UC
wT7a/0mGacstbMO25m2229HuYPjtYMGl5bem4sKt17Am7qA+obplWm2uAtKdWeZN3rMOzUpubQBm
6QPObYje7RqGYN8OTtYW7oxGZr2W49hG1deGiS9Q0QLa45NGA+MF1w+wZetOXakVTvTG6MNVYUn2
W/6e2Mst2t927lneZegmIek+6NBUXS+oXyc95OTF6JeOcK7235Y2bvyW3f1WXsvV7pa26O6WY6pg
AysIgh1wceT7IPf+1NkezTGGWqgtZIbVWhSYbC/47tSsbYMQgxb3gAkgsjmSCjHAihcIAitgA//Z
Y5P+zKxVXiiw36INW+NFgSrgci4/Y4sGcBXWbiawX/80cFr8xN8xmOJI7nIv32IdMFctN+jwtmwV
Wl/JRgM0dt3TxdbkxVbLBYI291kgCF48R2PjhujJjuYpp9kzvvIo1vI2H1ptXeQTT2+UbYId8IAG
QD0WhAorAEkIcm8bv/EcJ9cdf14mOF0U+GjXzuvf1Nob59nwzoI3XleaveFGF06U3YIdMPJOdySp
uAHUawCXuAL8gWaTxtvqVV2eHWiehXae5XAoPnG3hujTJF1op/OiXfbljvbFXe6hrQKbjejQdPAH
2gIkkIr19XFoD2dtN91vd4A9t2Wd5VlEP+NuBk1lr1lmd3eulvdp1+3DtvYUhwkxuAEF6HRP+wKp
YAP/CBgyAdiAFyCCY1cg9471rXUAWrd1nx7a3IWBw/XvTn111FxziEZdqOXpSP5Ymx3OQr2CGeD0
TueKGVi/LZj5hd+AHZiCJ98eaH5pRa8CRYfRDHdhxX5ppBfOLDD6c2cgNlCABlD3pwDo+8Zopg9P
L8jwMVB6uBZ6on/RGW0CD+h0CBABF3fxhnd4AVh4Oap4AsJ4LWZulb/uA77d0EZNGq970TTpPAcA
OgdNJkABWH7fvt/1aLWCDSD2F2gCGI+KMpiCHRABiG/7HbB45wF69tZrp2egGRgyqXeKqtd8C27K
NCB7T7uAqh6NK1ABrVh4AJD4HXDy/on70ex7Kwf8/58d/DFAgeotaNPU+5yeZeI1fNMcA2z9fSA3
CsX3tAnYgflWcSvQdLZHPQMwgTjrpNse/c1H5wmaAk8DfY4Q/e1X5itQ+CEzgBdQe9SAfE0//06/
gBl4glBPn9of/mgezuQG8rjvcihw2qMFCAsO0BAsaLCgjoEHFxbkkmADgIgADOwQ4+YixowaN3Lk
eOWHCAMSJaroaPIkypQqL1rRwPAlzJgyZ9KsaZPmAosrd/Ls6fPnl5ERGyC5uKPGzaRKlzJtykVk
RANE2PzcKebJjg0ChEZUoLMq2LAnNUCZacFClbRQUADQgUZgzSIAmNDkwoCsWQAO9u51+1ahzIQ2
V/+MpJhGrM+PECOaQOwY45YZO3YgsWJli8aWTTdz7rz5ANfQokeTLm36NOrUQoke9ez6NeyDJCRO
+PJ458eQI5/c7r2RzY3JPyxbOZwRr0wLevk68At3plwYNe0ij3n2peCFXg5mp6kg6g7jvneymUJE
/PiqO0Zv2EChQuz48jdDVW3/Pv78+TUgne//v0wDRKQCVemt9AURJvxgYHpb1Ldaew+UlZwF2AFm
0HYFwQBAETZRN6F1FTIEBQAgEgSFAyZ2NxMQAoTH4HhW7DBFgTBidANpO7gEII89FoTABe0JOSSR
RRp5JJJJKrkkk0lqIJoKYrTmI5X+4SBAEzb2lsb/BAJsMCN6Wm60xVaibVAdTNeNWOJBKE6IggMd
eniXiS+pydBZYxh0J0ErymSXmL3VN8EMT5RhIxvfhTbcjvKNkVZaWcSUhaQLVaFnlTLlFCinYm3B
VZRG9SdfFpBWkeFLlzJURaZ/MtApYk9wpYAHM37F6QyiQZAGmnaKiKcFmBKkJpys3vShWb9auhcM
TOggkLEIXegqrIgpKhQELwRhRY2ObfGDBwGE9oIbms2ng1Bx+spQc63GtGm18a4kK0m3TimfchI5
gNZL7R5UBQDRunsQoPL+lMYLpBnw5ba3+rZFECIIOKtFvQILUxXMOgstGiR+oAPIINdF50wooBCT
/xdw7oUCqgUB8cGcBleVBrhlhqbAl01YYdtOW1jRxA66jeYBS43Gl5CpbNVJEBBAsOvXwAvBKzPV
GpkwoMNu3BvfWaY+t5AOSwMscNQEFVx1T7lBYBoEG9xgBVhsWEZE0A9yJQBmbli8kMkoq+wAy0yf
NbgFMM+EbNkMnY12TxCbcC1pG/BsUsKjLTDSBAWaK5+f/hLkRaX/Suo5GlWEblBaPU7NuMxpCBAq
R1vHxufYBmXRckGn1p477gSZzuPirPMkdxAqXFBa3iY94QGRdocWgVBTYLR34ognTvCrwld1VdBr
i7bgSQ0IJYAHP1xRrkQNfLX50ReOoS4aDgDhAP8ALxteBF9w+oX/Xh9YsD9z6PKf1VULDMmr2hey
lhHZwYZPTHDAdjK2IQdkwV8w4MuGjHXBlTlAg3yxwOniEzzt/eQKQDOBViQigEOZxHWo8dIOuOUG
7wEgCMdZ2vWsd72GZI+EYjHhDlSwgQkAAAIKzMgUPGCCHRDhfBlhw1YMcED2xSYhIXvWr/ZShLJc
xwuAIwhb3OLFk6EhjB2rHxghOMAjruQBbnQj+EDiBjA8AG5uUMMDDviDB4jAhx1h4GsEErILSqd0
ALAAFOjSLrl0yAvKYRUj0eDIgKEhIWUZA59E2EM/IkZul0kJDQvTnuA04YAXyRUAZqAR6pVNhzv/
RMMIOVm1BghAehmhImzQxRwAkDF+vbzOitoVTLf4zyAOKOR8CNiTB0DmAUpwww80cBEiSNMNIgDf
9OwoywWOimvL4YtfACan+LmlcAUhEavMSZAsUPKYBfEiDl0Ty23CiDiWYaNG1tPHVcazlSR7JQ/p
yTqibASXr1kRigznuevw6X9vUZZD90K4fa0xLMzEiBKkGU2MqIAGcsyICh6gASWoIJpEcIMKRKAB
8ImACCoFAw1EUJKLpFQEYLhITFeaHkC6hk9AaIsho9Uu0nWQnMY8lUQHB9T5zFOgrCPCBbp1EVZG
zZU7bKpTO1WUghqtitO6IEEWWqGGlhOibnHA/8eu6DT/KJMnF73IFpi50Yvg8QFq2IgGMKOBvKqh
pW4oQx7d8ICS0KCOenumBk5qBWYqoY9l0MBNfcNTz2TyOrszKlFZlVl2ouCKYfMPVrNKteJwhKoD
s2oONyla1hnUNX4Cq1GHVaFhogG2YS2rQYoQwti0dSdvdUNcoVnNO7qRhcfR6zMzElfMPOBQW6jm
D36w3C081wpKeAARjCvZbs5OWQ8NakHapU40sDOdhiNvO6GGhiIIS5OrFa1p3YXa6qn2vVVrrWe6
4wX8KRRqXZQf04A6RjACNZJoYAKHKgqW3y5WuBgRAQ1iile95u26Mg3sRZ97kejGda97PWljRf+q
3cdMtjN3ygK6nHbZRRa1jJSMJCYpWSyCXLB3rwmtfVkX31bN1585Zm1Xc/nN/oXXvyLCH+EA2D+H
uvgsvARQb9sI0pLMda46Pa7e8hbYLAsWrtD9AR0xQgQwWIam2LxNiTmjHL7opZAr9gucBDLj2uav
xQI5C/yYWt8fk3DHmepxVfeMUxGIIAocJTRGQALhjhDhzHrbCDU97GiNGBolUXAjp/DbmUeZ6l/C
otQ7gdChLLT3d57LQtN2G58oq+QB0Y0mdKUZ18guF8t5vQh2v+XMLgP3y9ZUga7dcGnLaKDSvUnz
ZkrVadSh7tOfFZgXTlXe3OmgCDaGTWijEF3/4zba2FaIrrE1AmaNzPSWrx7OSUbMkShooNzy8nOV
AH1aQf+gJHE9lF9d6oaM3rWkkHY1Rh772w3TgLrP3SdHBl7a5AZK0wCdH6Yy1k8FV+Xc2rQCiMMd
BYa7gQh39fhFYKqCKJQZfGo4abns6NIfsDAKKlCBNo/NXYAe5APnnZ98BX0RdmP8oittiaEXS/KR
bkQJADhgSDcCklc/gAYdAcNwTeJMdcMK3lSSd847cs2pMhcjDwDDD1Cu4YwQ2qMhx67Co4sRPEa2
0SzvOMA7vu2MEKHpGP823JQQXTtKV+3aZrjeUS7svXPE4QDdlw7gdN5MsZrPO505zc+JVh18/wAA
yIy3zq0JvrxC3ctuMHu5om7NvebtsUkXNzbvDdctRDajtGa9RmoNBjVs4a5loC5GwHD7mxowIwY0
rgFNiRKr+wjrPBa00DcaXK5PWSOHUntG0n5mna402LWu/h59P1I17HU4NAD2dW/KxyiodDiGffm3
pNmSLVxX3YZ/OMjG2arGO367kYeJF0I28f9gld+LLcNH8VqiIdxFIFbeqAHcSN9xnFS7RZPTFRYD
lpQGOF2iuRr3fVhG1VtzdVhhfd/ppVQ0PRO7KdpOEF+PGN+fId8EItrYcVkBil6iOZoCTs+CJBce
4VoB0tXA3VpiscRdcdnXAddFeVSYcR018f9e4QXZ/dEc/dUfmkHeEl5V5j2WBgwWNGHTb81aaZnS
DE7VD6gBBWqYhoGh50XfVFHguGVZXN2VhAkW+1UTYFkTyk2aSZgg8PwTzc2TBtiRChBBC94aSsFg
DGpEF+rNgrDbXl3URSFiFa4ShYWcSlVh1/XahkkXALwRwIVU0yVhFEZhEzqhYyBbJx7fSfiVNekd
FmLUlk0YISrd9C3It0UiJZYLSOxVK7pgx9HAk1CXr2XZHnkYAIDBpTVdZKmEHQIICmJeR7xVvQlg
EL7cSUCf17ni2n0dHdmRIs6RYQkg8wEidjFfhn3Z8gGXGpRjrwkeRrzfKDIePoHiE65jHmb/HjOq
QEZdRBzuGyBu4S1mhDQKlhVcmhLwIiUCpECaoQu22xY8VkFCX17Vm8EljxUUFtWV1v7l3DHyn6DJ
1F8VmxzuWx9Fk8HdFMbxowwqXcG9ob3ZFdzhGnWpZN05ogsG1mIlYBmqXQ/+n76hFDoWDTwyYTv2
Bh2ihBqcG7p1xJmNZAGWn1iIYk+eYOb1oE4C1seVxKX9IF0VIy7iIOrZowpoFBrKmldumOj5nJbd
FR4t5Ob5jEoGlwgkVz4OX0UenwaUQA3UpV3eJV7mpV7uJV/ypQvoXFdC5ejZ1Oh5WEkQgbsRwU4S
4DR5WFtihC4mlgrclC7C1IdNJkjdFGbi/+MEKqY1hdxMeSYYiIBIVVpk0qEVLEBfriZrtqZrviZs
xuZdEsBP3gZjqsRzGRwNAEDMGaRYThXMbUFXhsUOZIBsHidyJqdyruZfnsRz7dVMXddeHUoVvtFH
EqAIcKHSYeJM0dFeFdZfuZF3TuDAXVR20tReyZR07RP0nWdhVeEzddgEliBdLqd95uVfyshk7Cd/
9qd//ieABqiA7gBvuGO8sMEPDKiCLiiD9udeNSiERuh/2tBK4J49Wihw3V6G1p5xYUbe6B7sXWgZ
mCNkRJ2/zVGIcuNGBaDehFtPSImExmiE5kAKyICM3iiDFmi6bcREGghWasSPpkSPcsSPBv8pSugn
jiZpgOqogTZpk64HAOxAjpmeRGZgSB2KSEFWlraEPUoTM3EgwF1aLZ5ZC3LfSeliNM3Ub20U0Tkp
RrQBD4DACGiBm9apnd4pnv4YlEaElL5XhG2Y3kXWrT1ApREqrlHmgnypSnLpHuIamWZpFZaEVOJa
AmKiSLmhncIpCGzqnOapp34qqIZqteypRPQpfJkSEeji0TkjZDqdBmDpLGrYW52ol1FXSpUhSiUq
P0pTo7qppm4qp9KpqA4rsRarsa4EqY6EqTpVr6oB1AGbQrKqPRLqPn1pNcnqg5HpcGlkC27dmkpT
R4FUUK7WrwJrsB4ruqZroAhfStDeQ57/BFbOXsA1Wm+ChZE6VbIKxbLSUzPqpEqepbReBKEll7V6
nl/FlbYGnKEGFtupqDQBlh0t1r2KVrma67mqa1hgKMZurMKlxNL9wHt2RAsaIk5NYJoixsiu27gK
TwNsAJ9FYh8FpnoG7L691Zfu0xY4FmmqVMzl7K7W7F4RLD/uEyNyZJOaAQgsgZP6bE+oFKHBp1Ge
2Zb9IukhxnmehBJM7MbymTQC7JhEnU7Vo9dx3E+kLDXSU8s26ZBilLsx2vSw69PxxNr+GNIqrZNq
bUfk40tyRD8GVjT94HUhxlvqY0o4wdb6BNR9Z685La6RZlyRZmNNo1wF5qvOkQaoFK1e/2E1YoaF
7drIUh86/iiEQecLkiYa8hFkiSFkfV56auOuXe7l+lDaiuoe4e2vRYEuHq5K1K3wlAGhEeZoqpSh
gUFNEW/ZVRrxEi9KNdaVBW+9YWU+3iO7aaTmeh1zxdxiuhQgkh+hRVZMFRqXkdSGEZqhSacB/a6R
toDu8oQpQtbIgSPKfaNgHQpidtke9duC+BUendnHRlO1YgZgGRCkVmGiwi1wCiximSUz0dHHZWde
3Vq/NqPa1S9K2W61zG6o/oCLmkTgrW9K8K6OgZiXwk2DfYofmvAb0pQf8uqrBvBhddyqTk9A+ky7
hSfc5G7/7lFCdmz0lUSD0RH9gmtKKv+k2H7fRsIND2JGTmJEGIRBCzSxB6eEwpGZDgdsH+qN+EET
GuqqwPLvNe0R+HSrdOWVwenUKpYW3+GsEoAnyCoXHAFndLExLPIR2Q6Uy0YxHn9w0rJOEQLXX/3V
pQkhXNksrGpYm5LxcJ2xh1XhHFKgYIHdF0dXHvXxMrIQ0R0KGFDT/Iac3oAnrkWBrbqqXsHcRpCB
DdgACJwyGeTxMpLbSmXUJArg+lWTXMURF+cqSQ4y3LRgSX1u/vIvxwEim15TIPdjXF0adZbUq1Vv
GVDTNrLsHbOyNGsECKNNyr4neI4dL/9A5Bpy3iDy22JZIFbi2/Ytc2FlFFilAOpUJA7/5w5ebvwu
ckncWhkU1iZuhPpOc2lV2h6qJKba7HFcsf3ast5gI/9i00ZNqj/6crn4Mx6F25X14djFodiym4bJ
UbiWC5UtSKPh1MrKCwZ7MInq80VUc9X0cXb6c8HOojaKwC7z6jez3kV5LfN5YceVW3OZM0o5sgt7
nSV/20xxaRCi1PoB8SOzhKFB8CBzRD6TdEaI6XA2oEqdFECLWXPhIPSp3WIlIsf1o06hKbeCLfgU
1svd8/Q03XAClkeR5k01IKGOXWIBVkcZat3RAB1F2OpqT0ivbz9yRMHprklXjUwJp0299ZVqM9iG
40FixsuBRDCKs7Bdda5Bo07LNcbN/2f0NaQ0UZPPkKZwbcFLQvBH7uF1IbFdT2D6OfVKlEFApqMS
jOhdJc8UIRxmkKg53tQjrp06a+gcjVnu+Z5VloF1qVtelZk9KgHcFCP7sVBkOStLvDZk3BRr1zHj
7LXu9jUrHm5gVw1iopzL2bXHnRxdoeOf3tFJgVzHAS6YDRx6T5OhAeBjphw/WiVi0kC91pFAd9w1
DWUBlhT9/uAX7ltH2RHYwQ1I7KRqP0yvjsVJBXKnDG6oWvedDhbklmyFB2Lsql3ksm7smi/UmW66
brd9cd/aPtZdcWmn8HCCZ9WiCWnxwspmEquE2+k34lEZjObObfZM9WF0iW0EzzNmPP9mX4X4Hjte
XLWtUWapARuIiq+4k2/tjNfpW/Ug7SEmr8ZcNG1ZA4IsM0HwYNUrsYr4k485mTt1lLvplK93SdXj
W5pUNW25TX6oLjb5p4p5md85nq8vEWzVp27j17UxPu40TnnULwu6RnMZKWdlsRpBGOS5oz86pK+W
SIEEVbpaTDGTWkuk2gWwXBeWoQnvddWbIEa6k66BFGhEF3SBG0jBGpC6q78669hV1uaeH/oxS9gR
icpruUA3XN1VJoM5rLtjGNiARjiB4QrBKge7si97oNA5s4fqGqwBGYTBGWDEGUAxEzcxsV9EGJCB
sbtBspPBtSc7t68yuT87uqc7Stz/prqLqhPYgBAkQQusMhXYgBMIQQtUO7zLO7GfQQskAb4brg00
cQvYgLwbrr8D/Cm3O8M3vMMf67tfBBX4gBs4QbIP/MRfhBQQuxAYrht0vBsMvBO3ehdwvMcLwbY/
vMrvxNVOI9O6lWPMOko4u7J/e0b4QBNTfHokAdrgvMHYvBNrfBKgchgAPbEP/EV8u8hv+7CHfKO7
Qb2vvNQbo3bOkU8seQliPTcyvM1jBNKf+200fdUgvbwAvfrCO7UPvNE7fdILvLZz+9E//cZPPcO3
lErlDfcSJkrJ1K0FL3gqLz0q5RwR2vOS3Rx1VPcCF/qOL/haky6aLzSRLyRCGM2v/7gPSIEPkD0W
+ADnJ7sTcD7If7wPoHy3C8Gqf/7oY4QQjL4TnLrqT7y9XwQW2EDqu4EPtIDpq/67nzrqYwG4xzvn
n0Hme/zs174PVHvFU4EbbL4PeLzok/7Pb/u9u0ELtPoaPHHJJz2xT7/tu73YN/30r8HC0726W+EP
X7UmQ6PRIRdKFex0ujDREUEM46AJf14f3Zq+GfFjJSCwcZn+NypAaFDiRsUDNwcRJlS4kGFDhw8h
RpQ4kaLDFkLcdGnhhkyLM26k2HBDxcaaMC2cuBGCkQqIMGFEOmnRxY0PKSoxakyJ0IaNM2dakAFK
M4lImAp7hlmTBOMZG13CgLjpw/8n0J8z3RRVedONTyw+VaZcOdJlRbMRnfS04eOgkJ4+hKQs+vYg
1Z4pfbxk6ybMXiEtbAhJcpZwYcOHESdWvJhxY8cOH5Q5KNCNZDBENLgxOHnLlswHDXp2Q3l058+a
tyQMvVm0BhVWED6I0lkFDc2SS2uevaW2aNCPgQcXjtDjQRtU3HwkE7IrTTdOUm40/jImxufRee40
jrxrGCeDDwY9mvB4eCwvBZ88+H06+/BkuoiM39XJS5JupHcfDhF6coUf/wswIioATEK7/RBMUMEF
GWzwsM1G+8ENETRwLTMINTAtNjdaS60033Lb0DfRyqDhgQdse6DCClXQDKEMNVv/0TUQIXTQxgbz
swGvntzS7zr8eKLuxx/zM5C8MNrTzgYhjwxPrcDG6687KfULSgjknlwLyOluHDK4kKiQorguySzT
zDPRVCiyyaz4oUU3rLgQtwzBgDC0zGAsrc6D1HjAw99GzExCDg16AIyDrIjCRc40OxTOKPb8Lc1J
FRvzKSesm88H7oy0VEgp+7P0wCWnk8I6/M4YL8j3DuriPJGGXNJU4j7CVDqbDjojOgBJvbEL54Tr
AjoAKS3W2GORpUjFLX7IDLMtrBDBoGaZBSA1EVTg7c4QYVRBhR9EAMBRQD9rjQZmBdXACiUegA1D
GsBodt12J8y2oGTxjQgw70QK/ymMLnzYSCMsqEDpuSWdcOkoUFMKyVauuKxSijDGOgliH9PqomCo
YJWS1BYmHiu5i1ptgYr4UkrLu7Lybdnll2GOGTQrVCACISJE+EGNQZUQgQgi1DgI5ygkVMNmoIUO
2g0lfogUoaJtdsPog8CNeunaYHNjUDfihU0JrG8WgWiZX55JCIil8MGJNXbqQjAsnKPCJinWWOOm
X1t1Ttj4kESI7oP+1nVTvw/8+yAqBKPJ7rwBXyM5Jwb3mwyEumCKu5HmdpzszTnv3PPganysDA2C
jvPz0x/LL7in3FhjTNRhj1322WUO/bEfVMyT9t0nUh24r2wwmffhiS/e+OORTxBe+eWZb97556GP
XvrpXw4IADs=
------=_Part_484_16579352.1102469023702
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

------=_Part_484_16579352.1102469023702--



From rohc-bounces@ietf.org  Wed Dec  8 03:12:53 2004
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 DAA29468
	for <rohc-web-archive@ietf.org>; Wed, 8 Dec 2004 03:12:53 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cbx39-0007EI-BU
	for rohc-web-archive@ietf.org; Wed, 08 Dec 2004 03:19:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cbwsh-0000eE-Cf; Wed, 08 Dec 2004 03:09:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbwhU-0006jj-UV
	for rohc@megatron.ietf.org; Wed, 08 Dec 2004 02:57:29 -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 CAA28113
	for <rohc@ietf.org>; Wed, 8 Dec 2004 02:57:27 -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 1CbwoD-0006tf-U5
	for rohc@ietf.org; Wed, 08 Dec 2004 03:04:26 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iB87vH6H028376; Wed, 8 Dec 2004 08:57:19 +0100 (MET)
In-Reply-To: <db95d40c0412071707b0c2e1b@mail.gmail.com>
References: <3F2E01E1D7B04F4EBEC92D3FA324D8803857FC@rsys004a.roke.co.uk>
	<550877E8-420B-11D9-82C1-000A95DC4DB6@tzi.org>
	<db95d40c0412071707b0c2e1b@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <C7666E10-48EE-11D9-B3CF-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] Re: Review of draft-bormann-rohc-over-802-00.txt
Date: Wed, 8 Dec 2004 08:57:16 +0100
To: Pedro Fortuna <pedro.fortuna@gmail.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: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, "rohc@ietf.org" <rohc@ietf.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.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit

Hi Pedro,

this is a very good point.

> In this case, if the AP chooses to use DIX Frames,

I should have been more specific in section 5: The idea is to use an 
encapsulation that is *not* the equivalent of a DIX (type-based) frame.
So the AP will simply not have that choice.

E.g., in variant 3 we would use an OUI that is not zero.

I would still prefer to use variant 2 or 1, which both also don't have 
that problem (variant 2 will be seen as a non-zero OUI by a standard 
SNAP implementation, and variant 1 cannot be mistaken as SNAP).

Variant 1: constant overhead of three bytes (LLC) plus possibly one 
byte used for demultiplexing (e.g., short vs. long CID, other IETF 
protocols sharing the LSAP allocation).
We need to go to ISO to get an LSAP.

Variant 2: as with the 3+1 subvariant of variant 1.
We would have to agree with 802 to use the reserved value 1 of the M 
bit.
Also, it would probably not be a good idea to send less than 8 bytes in 
total, so there is a minimum ROHC frame size of 4 bytes (not a problem, 
since we have padding built in to ROHC).

Variant 3:
a) constant overhead of at least six bytes (3 LLC, 3 OUI -- we can use 
the type ID part of the SNAP "protocol identifier" as we want), with a 
minimum ROHC frame size of 2 bytes (at least have to complete the 802 
"protocol identifier").
b) constant overhead of seven bytes (3 LLC, 3 OUI, 1 demux -- again in 
the type ID), with a minimum ROHC frame size of 1 bytes.
We need an OUI (or possibly re-use the IETF OUI -- I haven't checked 
who else uses this).

Resulting VoIP header sizes, assuming we have a way to use short CIDs 
(add one otherwise):

1a	4
1b	5
2	5 (with at least 3 bytes of payload)
3a	7 (with at least 1 byte of payload)
3b	8

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Wed Dec  8 05:04:23 2004
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 FAA08694
	for <rohc-web-archive@ietf.org>; Wed, 8 Dec 2004 05:04:23 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cbyn6-0001AJ-46
	for rohc-web-archive@ietf.org; Wed, 08 Dec 2004 05:11:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbyZK-0004Z5-FT; Wed, 08 Dec 2004 04:57:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbyWW-0003cS-5U
	for rohc@megatron.ietf.org; Wed, 08 Dec 2004 04:54:16 -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 EAA08007
	for <rohc@ietf.org>; Wed, 8 Dec 2004 04:54:14 -0500 (EST)
Received: from rproxy.gmail.com ([64.233.170.196])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbydF-0000x5-Jj
	for rohc@ietf.org; Wed, 08 Dec 2004 05:01:14 -0500
Received: by rproxy.gmail.com with SMTP id z35so139076rne
	for <rohc@ietf.org>; Wed, 08 Dec 2004 01:54:13 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding;
	b=XIFVjQHIBr8We3EK7xd0AltELM1c6thc/NBiXDNt46g/598Gw6IEYcIuFCp8PnYpsd+4X8guh0/MWz1/siLubn8qemN9X/CCCw9Jm+WCmSSpNVV+VAhlFaBcikW4y1pE83tgDimE0cX8qt2p3TsDufZ7Ts8Io253wksriAZHikw=
Received: by 10.38.14.44 with SMTP id 44mr834250rnn;
	Wed, 08 Dec 2004 01:54:13 -0800 (PST)
Received: by 10.38.83.41 with HTTP; Wed, 8 Dec 2004 01:54:13 -0800 (PST)
Message-ID: <1bd254fc041208015459198a9a@mail.gmail.com>
Date: Wed, 8 Dec 2004 15:24:13 +0530
From: chitrak gupta <mailfromchitrak@gmail.com>
To: rohc@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 202a3ece0492a8c7e7c8672d5214398f
Content-Transfer-Encoding: 7bit
Subject: [rohc] Problem with COPY-OFFSET Torture Test
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: chitrak gupta <mailfromchitrak@gmail.com>
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: 2bf730a014b318fd3efd65b39b48818c
Content-Transfer-Encoding: 7bit

Dear All,

I am implementing the UDVM. I am nearing finish but I am stuck at one
particular instruction, which is COPY-OFFSET. The COPY-OFFSET as I
understood I implemented but I am not getting the desired result from
the torture test. I am attaching below the group of instructions in
the torture test followed by the Memory dump after executing my UDVM.
 
------------------------------------------------------------------------------------------------------------------------
 
3.7.  COPY-LITERAL and COPY-OFFSET 
    
   This section gives assembly code to test the COPY-LITERAL and COPY-
   OFFSET instructions. The code is designed to test similar boundary 
   cases to the code for the COPY instruction, as well as the following 
   condition specific to COPY-LITERAL and COPY-OFFSET: 
    
   1. The COPY-LITERAL or COPY-OFFSET instruction overwrites the value 
   of its destination or offset operand. 
    
   at (64) 
    
   :byte_copy_left                  pad (2) 
   :byte_copy_right                 pad (2) 
   :destination                     pad (2) 
   :offset                          pad (2) 
    
   at (128) 
    
   LOAD (32, 16384) 
   LOAD (byte_copy_left, 64) 
   LOAD (byte_copy_right, 128) 
   LOAD (destination, 33) 
 
 
UDVM MEMORY DUMP (Start + 32)
>> 
0x0043FD70 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 

0x0043FD80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 

0x0043FD90 00 40 00 80 00 21 00 00 00 00 00 00 00 00 00 00 

0x0043FDA0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 


    
   COPY-LITERAL (32, 128, $destination) 
   COPY-LITERAL (68, 8, $destination) 

>> MEMORY DUMP (Start + 32)

0x0043FD70 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 

0x0043FD80 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 

0x0043FD90 40 40 40 40 00 69 40 40 40 40 40 40 40 40 40 40 

0x0043FDA0 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 

0x0043FDB0 40 00 61 40 40 40 40 40 40 40 40 40 40 40 40 40 

0x0043FDC0 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 

    
   LOAD (byte_copy_left, 66) 
   LOAD (byte_copy_right, 74) 

>> Memory Dump (Start + 32)
0x0043FD70 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 

0x0043FD80 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 

0x0043FD90 00 42 00 4a 00 69 40 40 40 40 40 40 40 40 40 40 

0x0043FDA0 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 

0x0043FDB0 40 00 61 40 40 40 40 40 40 40 40 40 40 40 40 40 

0x0043FDC0 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 



   COPY-OFFSET (8, 6, $destination) 

>>UDVM Memory Dump: (Start + 32)

0x0043FD70 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 

0x0043FD80 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 

0x0043FD90 00 42 00 4a 00 6f 40 40 40 40 40 40 40 40 40 40 

0x0043FDA0 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 

0x0043FDB0 40 00 61 40 40 40 40 40 40 00 61 40 40 40 40 40 

0x0043FDC0 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 


    
   LOAD ($offset, 1) 
    
   COPY-OFFSET ($offset, 5 ,$destination) 

>>UDVM Memory Dump: (Start + 32)

0x0043FD70 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 

0x0043FD80 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 

0x0043FD90 00 42 00 4a 00 74 40 40 40 40 40 40 40 40 40 40 

0x0043FDA0 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 

0x0043FDB0 40 00 61 40 40 40 40 40 40 00 61 40 40 40 40 40 

0x0043FDC0 40 40 00 4a 40 40 40 40 40 40 40 40 40 40 40 40 


    
   OUTPUT (32, 48) 
    
   END-MESSAGE (0, 0, 0, 0, 0, 0, 0) 
    
   The expected output of the code is 32 instances of 0x40 followed by 
   0x0042 004a 0074 4040 4040 004a 0074 4040. The expected cost of 
   executing the code is 208 UDVM cycles. 

__________________________________________________________________________________________________________________________
 
I have marked the mismatched location in red. 
I want to know the following,
 
i)  at which step I am going wrong
ii) if it is at COPY_OFFSET can you please explain the steps I should
follow in COPY-OFFSET.
I am using the following algorithm for COPY-OFFSET:
 
-----------------------------------------------------------------------------------------------------------------------
STEP 1) Get the value offset, length and destination. 
 
STEP 2) Read the bytecopy registers and get the values of bytecopyleft
and bytecopyright.
 
STEP 3) Get the position (source) value by the following code;
 
while(offset>0)
{
    if(position==bytecopyleft)
        position = (bytecopyright -1)% 0xffff;
    else
        position --;
    offset--;
}
 
STEP 4) Copy the content of position to destination byte by byte and
increment the addresses following the byte copy rule of Section 8.4 of
RFC 3320.
 
bdestination = destination // save the value of destination.
for(i = 0; i<length;i++)
{
    UDVMMEMORY[destination] = UDVMMEMORY[position];
    position = respectboundaryandincrement(position);
    destination = respectboundaryandincrement(destination);
}
bdestination +=length;   //to reflect the destination address for the
next copy instruction
 
STEP 5: Save bdestination into the destination operand. 
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
Please help!!!
 
 
Sincerely,
Chitrak Gupta.

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


From rohc-bounces@ietf.org  Wed Dec  8 07:01:59 2004
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 HAA16634
	for <rohc-web-archive@ietf.org>; Wed, 8 Dec 2004 07:01:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cc0cv-0003I3-H3
	for rohc-web-archive@ietf.org; Wed, 08 Dec 2004 07:09:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cc0V8-0001OP-1w; Wed, 08 Dec 2004 07:00:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cc0PC-0000ib-DB
	for rohc@megatron.ietf.org; Wed, 08 Dec 2004 06:54:50 -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 GAA16190
	for <rohc@ietf.org>; Wed, 8 Dec 2004 06:54:47 -0500 (EST)
Received: from [194.237.235.30] (helo=effnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cc0Vw-0003Bt-SK
	for rohc@ietf.org; Wed, 08 Dec 2004 07:01:50 -0500
Received: from effnet.com (c-b97c71d5.04-205-6c756c1.cust.bredbandsbolaget.se
	[213.113.124.178]) (authenticated bits=0)
	by effnet.com (8.12.3/8.12.3) with ESMTP id iB8ArdLh004834
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Wed, 8 Dec 2004 11:53:39 +0100
Message-ID: <41B6EBAE.9040700@effnet.com>
Date: Wed, 08 Dec 2004 12:55:26 +0100
From: Kristofer Sandlund <kristofer.sandlund@effnet.com>
Organization: Effnet
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "West, Mark" <mark.a.west@roke.co.uk>
Subject: Re: [rohc] ROHC-TCP, ack number compression
References: <Pine.LNX.4.44.0412072316480.22606-100000@mjw-pc.roke.co.uk>
In-Reply-To: <Pine.LNX.4.44.0412072316480.22606-100000@mjw-pc.roke.co.uk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 93df555cbdbcdae9621e5b95d44b301e
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, "'rohc@ietf.org'" <rohc@ietf.org>,
        "Ghyslain Pelletier \(LU/EAB\)" <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.1 (/)
X-Scan-Signature: ec7c6dab5a62df223002ae71b5179d41
Content-Transfer-Encoding: 7bit

Hi Mark. Comments inline.

West, Mark wrote:
> Hi all,
> 
> Apologies for the 'usual' delayed-ACK...
> 

We're used to it by now :)

> Comments in-line.
> 
> Cheers,
> 
> Mark.
> 
> 
>>- The implicit ACK number scaling in bidirectional deployments seems to only
>>have the support from Mark, while myself, Lars-Erik, Ghyslain and Carsten have
>>doubts about the complexity required (Mark, if you want to keep this, please
>>explain IN DETAIL how you want it to work). I think we should leave this out of
>>the spec. (if I have misjudged the opinions of anyone or if someone else finds
>>this to be compelling, please yell out before we scrap it)
>>
> 
> 
> I'm assuming that this is referring to the proposal to use sequence
> numbers in one direction to infer acks in the reverse direction?  (it's
> just that I wouldn't call this scaling, but that's being picky!)
> 
> Well, I cannot deny that I'm still rather attached to the idea of this
> scheme -- it just seems like a really nice idea from the TCP perspective.
> Also, for a more applicable argument, it's going to have most effect on
> 'pure ACK' packets which are, in fact, 'pure overhead'.  So, arguably,
> these are a good target to try and squeeze harder...
> 
> However I also cannot deny that there are a number of issues to be ironed
> out and corner cases to be thought through.  Having said which, I still
> believe that it is possible to specify it in a reasonable and manageable
> way.

As Carsten pointed out, one would need to "point out" both channel ID and CID 
for the reverse context which I'm taking the scaling from. You would also have 
to send the "reverse-direction MSN" to know which scaling value to use (the 
sliding window you refered to earlier). Therefore, to use the dual-directional 
implicit stuff would probably require an overhead of at least a couple of bytes. 
And some new fields to the packet formats which would add even more packet 
formats. And with this kind of overhead, I think that an explicit stride value 
would be as efficient if the compressor is smart. See more below.

> 
> If anyone actually thinks that it would be useful for me to write a more
> detailed description, for discussion, then I'm quite happy to do that.
> However, I get a fairly strong sense that it wouldn't be worth the effort;
> certainly nobody has indicated any interest following this mail.  In which
> case, I bow to the majority view...
> 
> 
>>This leaves us with (at least) the following different roads for this:
>>a) Only send unscaled ACK numbers. Not very optimal, will often have to send
>>about one byte extra compared to a scaled scheme. Simple and clearly interoperable.
> 
> 
>>b) Explicit scaling (ack_stride, 16 bit value) by letting the compressor send
>>over a scaling value in a compressed packet (for example, this value could be
>>transmitted in the dynamic chain and co_common, but nowhere else). How this
>>value is inferred by the compressor would be an implementation detail, so that
>>it can use the reverse-directional stream, it could look at the traffic or it
>>could use some proprietory out-of-band signalling etc. In this scheme, only one
>>scaling value is legal at any one time and if the ack number change rate is very
>>variable, then either we need a frequent update of the stride or we have to send
>>unscaled values until the same stride "comes back". Not being a TCP expert, I
>>can't really say how much gain/loss this would be in the end, but I think it
>>seems worth considering.
>>Also, if we go for this strategy we need to decide how to handle it at context
>>replication (always, never or optional).
> 
> 
> I'm really not sure how much benefit you'd actually get in this case (in
> terms of overall average compressed header size).  There are definitely
> going to be cases where large gains can be made: some flows will have long
> runs of 2 x MSS intervals in the ack flow.  This will work just as well as
> deriving acks from seqno, in that case.
> 
> However, in many other cases you will be faced with the 'how long will
> this persist / is it worth setting the scaling now / when will I have to
> change it back' trade-off.  Ok, there's scope for clever compressors to do
> better; but if it's too complex, who will bother?

That's pretty much my point. If it is explicit, it will be up to the compressor 
to decide if it wants to use this or not. Therefore, he _can_ use the 
reverse-directional seq to obtain a suitable stride, or any other smart trick he 
likes. Making it optional to me means that one can allow a lot more complexity 
on the compressor side, as long as the decompressor does not have to be really 
smart (and with this scheme, I think the decomrpessor can be dumb no matter if 
the feature is used or not).

> 
> Carsten's observation suggests that this might typically be able to save a
> few bits per header, but how often do you have to send the 16-bit
> ack_stride (+ the base-size of the header to carry that information).
> 

If the compressor is really bright and uses a lot of "good ideas" when deciding 
the stride value, it could be efficient. And if the compressor is more "stupid" 
(or the flow is not suitable for ACK scaling), it should just ignore this 
feature altogether. Therefore, I think we should try to specify this idea. If it 
turns out that it has some flaws, we can drop it before publication.

> 
>>c) optional feedback option sending the ack_stride (the sending entity's
>>decompressor could take this value from the co-located compressor). This is like
>>the bidirectional stuff but it is "explicit and optional" instead of "implicit
>>and mandatory". Downsides are the delay before this can be used and also this
>>will probably lead to some sliding window of scaling values so that
>>compressor/decompressor keep in synch. I'm not for such a solution, since it
>>seems complex and slightly evil.
>>
> 
> 
> Surely this case is more the remote end-point being able to 'suggest' (in
> a feedback option) suitable value(s) for scaling, as defined in (b)?  In
> other words, I see this as suggesting a refinement to (b) rather than a
> separate scheme.  (I agree with 'complex and slightly evil' as an
> assessment of this scheme on its own...)
> 

Yep, you're right. This would be a complement to b). But since we both feel it 
is evil, I think we should leave it out for now.

> 
>>I could consider option b), but as I stated, I cannot really estimate the gain,
>>so possibly a) is good enough.
>>
> 
> 
> I would consider (b), too.
> 
> I suppose that I have difficulty accepting the statement "(a) is good
> enough" when there are clearly ways of achieving better compression than
> this.  Although I freely accept that the trade-off of complexity vs.
> saving is not obvious.

Ok, let's try to get b) working then. Some questions:

- When should we have scaled ack compression? Should it only be used for "pure 
ACK streams (i.e. as in packet 4 in baseheaders.txt), should it be usable on 
streams that have changes to both ack and seq, should it be usable in co_common 
and/or packet 10, should it be useable ir IR/IR-DYN? Opinions please.

- When should we be able to transmit the ack_stride factor? My suggestion would 
be co_common and possibly as an optional in tcp dynamic chain. Or do we want to 
add it to other packet formats as well?

- Are there any issues with this? We need to be very clear on what happens when 
the ack_stride is zero, so we don't get into slope-ish zero-division discussions 
later on. My suggestion is that a stride of zero means that we should not use 
scaled packet formats. Do we set a default-value for ack_stride and in that case 
what is it (zero or nonzero)?

If I get some answers to these questions I can add some things to 
baseheaders.txt and suggest some text for the tcp-draft explaining what this is.

> 
> If we're going to take *that* strong a line on complexity, then (a) is the
> only way to go, of course.  And we probably ought to take a good hard look
> at the draft to make sure that it's really as simple as we think/hope.
>

No, we don't need to discard everything that is complex, but my feeling is that 
the bidirectional stuff seems hard to get interoperable due to the coupling of 
flows from different channels/context spaces. But, I agree that it would be a 
good idea to go over the draft and try to see if we do "too much" for some 
fringe cases.

I'm going to write up another mail with some outstanding discussion items on the 
packet formats in a while, but please provide some feedback on this stuff so I 
can start working on a solution.

/Kristofer Sandlund, Effnet AB

> Cheers,
> 
> Mark.
> 
> 
> _______________________________________________
> 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


From rohc-bounces@ietf.org  Wed Dec  8 08:09:21 2004
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 IAA20393
	for <rohc-web-archive@ietf.org>; Wed, 8 Dec 2004 08:09:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cc1g6-0004d6-31
	for rohc-web-archive@ietf.org; Wed, 08 Dec 2004 08:16:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cc1O8-0001xq-TP; Wed, 08 Dec 2004 07:57:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cc1KN-0001V0-D4
	for rohc@megatron.ietf.org; Wed, 08 Dec 2004 07:53:55 -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 HAA19396
	for <rohc@ietf.org>; Wed, 8 Dec 2004 07:53:54 -0500 (EST)
Received: from [194.237.235.30] (helo=effnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cc1R8-0004DX-8i
	for rohc@ietf.org; Wed, 08 Dec 2004 08:00:55 -0500
Received: from effnet.com (c-b97c71d5.04-205-6c756c1.cust.bredbandsbolaget.se
	[213.113.124.178]) (authenticated bits=0)
	by effnet.com (8.12.3/8.12.3) with ESMTP id iB8BqrLh004975
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Wed, 8 Dec 2004 12:52:54 +0100
Message-ID: <41B6F991.1000304@effnet.com>
Date: Wed, 08 Dec 2004 13:54:41 +0100
From: Kristofer Sandlund <kristofer.sandlund@effnet.com>
Organization: Effnet
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: rohc@ietf.org
Content-Type: multipart/mixed; boundary="------------020508050401080904010609"
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 946b615681bce2b72aace5af8d0d8a1d
Subject: [rohc] TCP packet formats - more design questions
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.2 (/)
X-Scan-Signature: d2ef8a017d8070cfdc3108436d3b9538

This is a multi-part message in MIME format.
--------------020508050401080904010609
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi all!

During the Washington meeting offline discussions, we decided to produce a new 
set for the base header part of the ROHC-TCP packet formats. These new formats 
are hand-generated headers instead of the old machine-generated ones. This to 
get a better overview of what the different packet formats are actually used 
for. These packet formats contains co_common + 10 seq-IPID headers + 10 rnd-IPID 
headers. The file with the latest FN code for that is attached to this mail 
(also includes box notation for all of us who like ascii pictures).

The current "design rationale" for these are as follows (_similar_ text will be 
added to the next revision of the tcp draft, but it will be edited to make a bit 
more sense).

    1: This packet format transmits changes to the TCP sequence number
    and its principal use should be on the downstream of a data transfer.

    2: Transmits the TCP sequence number in scaled form, and will
    normally be used on the downstream of a data transfer where the
    payload size is constant for multiple packets.

    3: Is used to transmit changes in the TCP acknowledgement number, and
    will be used in acknowledgement direction of data transfer.

    4: Is similar to 3, but sends only a few bits of ACK number. The
    format is expected to have its principle use on the acknowledgement
    stream interactive data connections such as Telnet.

    5: Transmits both TCP sequence number and acknowledgement number, and
    has its largest use on streams that send data in both directions.

    6: Is similar to 5, but sends the sequence number in scaled form to
    be used when the payload size is static for certain intervals in a
    data stream.

    7: Is used to transmit changes to both TCP sequence number and TCP
    window, and is expected to be used on all data transfers.

    8: Is used to transmit changes to both TCP acknowledgement number and
    TCP window, and is expected to be used on acknowledgement streams of
    data connections.

    9: Similar to 7, but sends the sequence number in scaled form to
    allow higher compression rates on streams with a constant payload
    size,

    10: This packet is used to transmit changes to some of the more
    seldom changing fields in the streams, such as ECN behaviour,
    Reset/SYN/FIN flags, the TTL/Hop Limit and the TCP options list. This
    packet is protected by a 7-bit CRC, since it can change contents of
    the irregular chain in later packets. Note that this can be seen as a
    reduced form of the common packet format.

So, to try to get these closer to finalizing, I'm going to summarize some issues 
and changes that might be done to them (or not).

Issue 1: We do not have any way to transmit changes in TTL/Hoplimit fields of 
outer IP headers except to use IR-DYN packets. This seems a bit weak, but how do 
we add this to the packet formats since we have to do it for an arbitrary number 
of IP headers?
My suggestion would be to do this semi-well and add a flag to co_common, and if 
this is set, we transmit the TTL of all outer IP headers inside this packet. 
This means that a change in one TTL field will mean that we have to send 
co_common and that this packet has to contain multiple TTL fields even if they 
are unchanged (only costs extra if we have more than 2 IP headers).
Another alternative (even less efficient) is to set up a control field and say 
that if this ttl-is-present bit is set, then the TTL of all headers is added to 
the irregular chain. So that some streams always send these while otehrs never 
sent this.
Also, we _could_ do both the alternatives listed above.
We don't want to spend too much effort on this case, but I feel that a TTL 
change to the tunnel header should not have ot back off to IR-DYNs. But if 
others feel that would be ok, then we can leave it as it is now.

Issue 2: Do we keep packet format 4? Do we expect to see a large enough number 
of small changes to the ACK number to warrant this packet format? If we drop it, 
we _could_ replace it with a scaled ACK number format (see other mail thread).

Issue 3: Is packet format 10 useful enough? We _could_ drop this and say that 
co_common is good enough. I don't really know what would be the best approach.

Issue 4: Do we have any kind of zero-division issue with the scaled sequence 
numbers? (since the residue is established when sending unscaled seq, is there 
some wierd worst-case where we the current FN could tell decompressors to divide 
by zero?).

Comments appreciated.

Rgds,
	Kristofer Sandlund, Effnet AB


--------------020508050401080904010609
Content-Type: text/plain;
 name="baseheaders.txt"
Content-Disposition: inline;
 filename="baseheaders.txt"
Content-Transfer-Encoding: 7bit

% just the base header packet formats for TCP-ROHC
%
% $Id: baseheaders.txt,v 1.6 2004/11/12 14:23:39 eilert Exp $


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Common compressed packet format
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

   format_co_common             =   discriminator,       %[ 4 ]
                                    ack_flag,            %[ 1 ]
                                    psh_flag,            %[ 1 ]
                                    rsf_flags,           %[ 2 ]

                                    msn,                 %[ 8 ]

                                    seq_indicator,       %[ 2 ]
                                    ack_indicator,       %[ 2 ]
				    ip_id_indicator,     %[ 2 ]
				    window_indicator,    %[ 2 ]

                                    urg_ptr_present,     %[ 1 ]
                                    ecn_used,            %[ 1 ]
				    tos_tc_present,      %[ 1 ]
                                    ttl_hopl_present,    %[ 1 ]
				    list_present,        %[ 1 ]

                                    ip_id_behavior,      %[ 2 ]

                                    urg_flag,            %[ 1 ]
                                    df,                  %[ 1 ]

                                    header_crc,          %[ 7 ]

                                    seq_number,          % 0, 8, 16, 32 bits
                                    ack_number,          % 0, 8, 16, 32 bits
                                    ip_id,               % 0, 8, 16 bits
                                    window,              % 0, 8, 16 bits
                                    urg_ptr,             % 0 or 16 bits
                                    ip_ecn_flags,        % 0 or 2 bits
                                    tcp_ecn_flags,       % 0 or 2 bits
                                    tcp_res_flags,       % 0 or 4 bits
                                    tos_tc,              % 0 or 8 bits
                                    ttl_hopl,            % 0 or 8 bits
                                    options_list,        % n bits
   {
             discriminator      ::= '1110';
             tos_tc_present     ::= irregular(1);
             ttl_hopl_present   ::= irregular(1);
             ack_flag           ::= irregular(1);
             psh_flag           ::= irregular(1);
             msn                ::= lsb (8, 64); % this could be fewer bits
             df                 ::= dont_fragment(version:uncomp_value);
             header_crc         ::= crc7(this:uncomp_value,
                                         this:uncomp_length);
             urg_flag           ::= irregular(1);
             urg_ptr_present    ::= irregular(1);
             ecn_used           ::= irregular(1);
             list_present       ::= irregular(1);
             ip_id_behavior     ::= ip_id_behavior_enc;
             rsf_flags          ::= rsf_index_enc;

             window_indicator   ::= irregular(2);
             ip_id_indicator    ::= irregular(2);
             seq_indicator      ::= irregular(2);
             ack_indicator      ::= irregular(2);

             seq_number         ::= variable_length_32_enc(seq_indicator);
             ack_number         ::= variable_length_32_enc(ack_indicator);
             window             ::= variable_length_16_enc(window_indicator);
             ip_id              ::= variable_length_16_enc(ip_id_indicator);
             urg_ptr            ::= static_or_irreg16(urg_ptr_present);
             ttl_hops           ::= static_or_irreg8(ttl_hopl_present);
             ip_ecn_flags       ::= ip_irreg_ecn(ecn_used_flag);
             tcp_ecn_flags      ::= tcp_ecn_flags_enc(ecn_used_flag);
             tcp_res_flags      ::= tcp_res_flags_enc(ecn_used_flag);
             tos_tc             ::= tos_tc_enc(tos_tc_present);
             options_list       ::= tcp_list_presence_enc
                                           ((data_offset:uncomp_value + 20) / 4,
                                            list_present);
   };

%   0   1   2   3   4   5   6   7
% +---+---+---+---+---+---+---+---+
% | 1   1   1   0 |ACK|PSH|  RSF  |
% +===+===+===+===+===+===+===+===+
% |              MSN              |
% +---+---+---+---+---+---+---+---+
% |  sn   | a_sn  | ip_id |  win  |
% +---+---+---+---+---+---+---+---+
% |urg|ecn|tos|ttl|lst|IPIDbeh|URG|
% +---+---+---+---+---+---+---+---+
% |DF |            CRC            |
% +---+---+---+---+---+---+---+---+
% /              SN               /  0, 8, 16, 32 bits, indicated by sn
%  --- --- --- --- --- --- --- ---
% /            ACK_SN             /  0, 8, 16, 32 bits, indicated by a_sn
%  --- --- --- --- --- --- --- ---
% /             IP-ID             /  0, 8, 16 bits, indicated by ip_id
%  --- --- --- --- --- --- --- ---
% /            WINDOW             /  0, 8, 16 bits, indicated by win
%  --- --- --- --- --- --- --- ---
% /            URG-PTR            /  16 bits, if urg=1
%  --- --- --- --- --- --- --- ---
% /IP-ECN |TCP-ECN|    TCP_RES    /  8 bits, if ecn=1
%  --- --- --- --- --- --- --- ---
% /              TOS              /  8 bits, if tos=1
%  --- --- --- --- --- --- --- ---
% /              TTL              /  8 bits, if ttl=1
%  --- --- --- --- --- --- --- ---
% /         options_list          /  n*8 bits, if lst=1
%  --- --- --- --- --- --- --- ---


% NON-SEQUENTIAL PACKET FORMATS

% +------+-------+-----+-----+-----+---------+---------+
% |Name  |Disc   |MSN  |SN   |ACK  |Window   |Comment  |
% +------+-------+-----+-----+-----+---------+---------+
% |_1    |100    |4    |13   |0    |         |         |
% +------+-------+-----+-----+-----+---------+---------+
% |_2    |01     |4    |*6   |0    |         |         |
% +------+-------+-----+-----+-----+---------+---------+
% |_3    |101    |4    |0    |13   |         |         |
% +------+-------+-----+-----+-----+---------+---------+
% |_4    |110    |4    |0    |5    |         |         |
% +------+-------+-----+-----+-----+---------+---------+
% |_5    |00100  |4    |15   |12   |         |         |
% +------+-------+-----+-----+-----+---------+---------+
% |_6    |0011   |4    |*7   |13   |         |         |
% +------+-------+-----+-----+-----+---------+---------+
% |_7    |00101  |4    |11   |0    |16       |         |
% +------+-------+-----+-----+-----+---------+---------+
% |_8    |00011  |4    |0    |11   |16       |         |
% +------+-------+-----+-----+-----+---------+---------+
% |_9    |00000  |4    |*8   |0    |11       |         |
% +------+-------+-----+-----+-----+---------+---------+
% |_10   |00001  |4    |12   |12   |         |and more |
% +------+-------+-----+-----+-----+---------+---------+

   % Send LSBs of sequence number
   format_rnd_1 = discriminator, %[ 3 ]
		  seq_number,	 %[ 13 ]
		  msn,		 %[ 4 ]
		  psh_flag,      %[ 1 ]
		  header_crc,	 %[ 3 ]
   {
      let ((ip_id_behavior:uncomp_value == 2) ||
           (ip_id_behavior:uncomp_value == 3));
      discriminator       ::= '100';
      msn                 ::= lsb(4, 4);
      header_crc          ::= crc3 (this:uncomp_value,
                                    this:uncomp_length);
      psh_flag            ::= irregular (1);
      seq_number	  ::= lsb(13, 4095);
   };

%   0   1   2   3   4   5   6   7
% +---+---+---+---+---+---+---+---+
% | 1   0   0 |        SN...      |
% +===+===+===+===+===+===+===+===+
% |           ...SN               |
% +---+---+---+---+---+---+---+---+
% |      MSN      |PSH|    CRC    |
% +---+---+---+---+---+---+---+---+


   % Send scaled sequence number LSBs
   format_rnd_2 = discriminator, %[ 2 ]
		  seq_number_scaled, %[ 6 ]
		  msn,		 %[ 4 ]
		  psh_flag,      %[ 1 ]
		  header_crc,	 %[ 3 ]
   {
      let ((ip_id_behavior:uncomp_value == 2) ||
           (ip_id_behavior:uncomp_value == 3));
      discriminator       ::= '01';
      msn                 ::= lsb(4, 4);
      header_crc          ::= crc3 (this:uncomp_value,
                                    this:uncomp_length);
      psh_flag            ::= irregular (1);
      seq_number_scaled   ::= lsb(6, 31);
      seq_number_residue  ::= static;
   };

%   0   1   2   3   4   5   6   7
% +---+---+---+---+---+---+---+---+
% | 0   1 |       SN_SCALED       |
% +===+===+===+===+===+===+===+===+
% |      MSN      |PSH|    CRC    |
% +---+---+---+---+---+---+---+---+


   % Send acknowledgement number LSBs
   format_rnd_3 = discriminator, %[ 3 ]
		  ack_number,    %[ 13 ]
		  msn,		 %[ 4 ]
		  psh_flag,      %[ 1 ]
		  header_crc,	 %[ 3 ]
   {
      let ((ip_id_behavior:uncomp_value == 2) ||
           (ip_id_behavior:uncomp_value == 3));
      discriminator       ::= '101';
      msn                 ::= lsb(4, 4);
      header_crc          ::= crc3 (this:uncomp_value,
                                    this:uncomp_length);
      psh_flag            ::= irregular (1);
      ack_number	  ::= lsb(13, 2047);
   };

%   0   1   2   3   4   5   6   7
% +---+---+---+---+---+---+---+---+
% | 1   0   1 |      ACK_SN...    |
% +===+===+===+===+===+===+===+===+
% |         ...ACK_SN             |
% +---+---+---+---+---+---+---+---+
% |      MSN      |PSH|    CRC    |
% +---+---+---+---+---+---+---+---+


   % Send small ACK numbers for small packet ACK streams (telnet/ssh etc).
   format_rnd_4 = discriminator, %[ 3 ]
		  ack_number,	 %[ 5 ]
		  msn,		 %[ 4 ]
		  psh_flag,      %[ 1 ]
		  header_crc,	 %[ 3 ]
   {
      let ((ip_id_behavior:uncomp_value == 2) ||
           (ip_id_behavior:uncomp_value == 3));
      discriminator       ::= '110';
      msn                 ::= lsb(4, 4);
      header_crc          ::= crc3 (this:uncomp_value,
                                    this:uncomp_length);
      psh_flag            ::= irregular (1);
      ack_number	  ::= lsb(5, 7);
   };

%   0   1   2   3   4   5   6   7
% +---+---+---+---+---+---+---+---+
% | 1   1   0 |      ACK_SN       |
% +===+===+===+===+===+===+===+===+
% |      MSN      |PSH|    CRC    |
% +---+---+---+---+---+---+---+---+


   % Send ACK and sequence number
   format_rnd_5 = discriminator, %[ 5 ]
		  header_crc,	 %[ 3 ]
		  msn,		 %[ 4 ]
		  ack_number,    %[ 12 ]
		  psh_flag,      %[ 1 ]
		  seq_number,    %[ 15 ]
   {
      let ((ip_id_behavior:uncomp_value == 2) ||
           (ip_id_behavior:uncomp_value == 3));
      discriminator       ::= '00100';
      msn                 ::= lsb(4, 4);
      header_crc          ::= crc3 (this:uncomp_value,
                                    this:uncomp_length);
      psh_flag            ::= irregular (1);
      ack_number	  ::= lsb(12, 1023);
      seq_number	  ::= lsb(15, 16383);
   };

%   0   1   2   3   4   5   6   7
% +---+---+---+---+---+---+---+---+
% | 0   0   1   0   0 |    CRC    |
% +===+===+===+===+===+===+===+===+
% |      MSN      |    ACK_SN...  |
% +---+---+---+---+---+---+---+---+
% |         ...ACK_SN             |
% +---+---+---+---+---+---+---+---+
% |PSH|            SN...          |
% +---+---+---+---+---+---+---+---+
% |           ...SN               |
% +---+---+---+---+---+---+---+---+


   % Send both ACK and scaled sequence number LSBs
   format_rnd_6 = discriminator, %[ 4 ]
		  psh_flag,      %[ 1 ]
		  header_crc,	 %[ 3 ]
		  msn,		 %[ 4 ]
		  ack_number,    %[ 13 ]
		  seq_number_scaled, %[ 7 ],
   {
      let ((ip_id_behavior:uncomp_value == 2) ||
           (ip_id_behavior:uncomp_value == 3));
      discriminator       ::= '0011';
      msn                 ::= lsb(4, 4);
      header_crc          ::= crc3 (this:uncomp_value,
                                    this:uncomp_length);
      psh_flag            ::= irregular (1);
      ack_number	  ::= lsb(13, 2047);
      seq_number_scaled   ::= lsb(7, 63);
      seq_number_residue  ::= static;
   };

% +---+---+---+---+---+---+---+---+
% | 0   0   1   1 |PSH|    CRC    |
% +===+===+===+===+===+===+===+===+
% |  MSN          | ACK_SN...
% +---+---+---+---+---+---+---+---+
% |  ...ACK_SN...                 |
% +---+---+---+---+---+---+---+---+
% |..A|        ...SN              |
% +---+---+---+---+---+---+---+---+

   % Send sequence number and window
   format_rnd_7 = discriminator, %[ 5 ]
		  header_crc,	 %[ 3 ]
		  msn,		 %[ 4 ]
		  psh_flag,      %[ 1 ]
		  seq_number,    %[ 11 ]
		  window,	 %[ 16 ]
   {
      let ((ip_id_behavior:uncomp_value == 2) ||
           (ip_id_behavior:uncomp_value == 3));
      discriminator       ::= '00101';
      msn                 ::= lsb(4, 4);
      header_crc          ::= crc3 (this:uncomp_value,
                                    this:uncomp_length);
      psh_flag            ::= irregular (1);
      seq_number	  ::= lsb(11, 1023);
      window		  ::= irregular(16);
   };

% +---+---+---+---+---+---+---+---+
% | 0   0   1   0   1 |    CRC    |
% +===+===+===+===+===+===+===+===+
% |      MSN      |PSH|    SN...  |
% +---+---+---+---+---+---+---+---+
% |           ...SN               |
% +---+---+---+---+---+---+---+---+
% |                               |
% +            WINDOW             +
% |                               |
% +---+---+---+---+---+---+---+---+


   % Send ACK and window
   format_rnd_8 = discriminator, %[ 5 ]
		  header_crc,	 %[ 3 ]
		  msn,		 %[ 4 ]
		  psh_flag,      %[ 1 ]
		  ack_number,	 %[ 11 ]
		  window,	 %[ 16 ]
   {
      let ((ip_id_behavior:uncomp_value == 2) ||
           (ip_id_behavior:uncomp_value == 3));
      discriminator       ::= '00011';
      msn                 ::= lsb(4, 4);
      header_crc          ::= crc3 (this:uncomp_value,
                                    this:uncomp_length);
      psh_flag            ::= irregular (1);
      ack_number	  ::= lsb(11, 1023);
      window		  ::= irregular(16);
   };

% +---+---+---+---+---+---+---+---+
% | 0   0   0   1   1 |    CRC    |
% +===+===+===+===+===+===+===+===+
% |      MSN      |PSH|  ACK_SN...|
% +---+---+---+---+---+---+---+---+
% |         ...ACK_SN             |
% +---+---+---+---+---+---+---+---+
% |                               |
% +            WINDOW             +
% |                               |
% +---+---+---+---+---+---+---+---+


   % Send scaled sequence number and window.
   format_rnd_9 = discriminator, %[ 5 ]
		  header_crc,	 %[ 3 ]
		  msn,		 %[ 4 ]
		  psh_flag,      %[ 1 ]
		  window,	 %[ 14 ]
		  seq_number_scaled, %[ 5 ]
   {
      let ((ip_id_behavior:uncomp_value == 2) ||
           (ip_id_behavior:uncomp_value == 3));
      discriminator       ::= '00000';
      msn                 ::= lsb(4, 4);
      header_crc          ::= crc3 (this:uncomp_value,
                                    this:uncomp_length);
      psh_flag            ::= irregular (1);
      window		  ::= lsb(14, 8191);
      seq_number_scaled	  ::= lsb(5, 15);
      seq_number_residue  ::= static;
   };

% +---+---+---+---+---+---+---+---+
% | 0   0   0   0   0 |    CRC    |
% +===+===+===+===+===+===+===+===+
% |      MSN      |PSH|SN_SCALED..|
% +---+---+---+---+---+---+---+---+
% |SN_SC..|      WINDOW...        |
% +---+---+---+---+---+---+---+---+
% |           ...WINDOW           |
% +---+---+---+---+---+---+---+---+


   % A packet halfway between co_common and compressed packets
   % Can send LSBs of TTL, RSF flags, change ECN behavior and options list
   format_rnd_10 = discriminator, %[ 5 ]
		   ecn_used,	  %[ 1 ]
		   rsf_flags,	  %[ 2 ]
		   psh_flag,      %[ 1 ]
		   ttl_hopl,	  %[ 3 ]
		   msn,		  %[ 4 ]
		   list_present,  %[ 1 ]
		   header_crc,	  %[ 7 ]
		   ack_number,	  %[ 12 ]
		   seq_number,	  %[ 12 ]
		   options_list,  % 0 or X bits
   {
      let ((ip_id_behavior:uncomp_value == 2) ||
           (ip_id_behavior:uncomp_value == 3));
      discriminator       ::= '00001';
      msn                 ::= lsb(4, 4);
      header_crc          ::= crc7 (this:uncomp_value,
                                    this:uncomp_length);
      psh_flag            ::= irregular (1);
      list_present        ::= irregular(1);
      options_list        ::= tcp_list_presence_enc
                                      ((data_offset:uncomp_value + 20) / 4,
                                       list_present);
      rsf_flags           ::= rsf_index_enc;
      ecn_used		  ::= irregular(1);
      ttl_hopl		  ::= lsb(3, 3);
      seq_number	  ::= lsb(12, 2047);
      ack_number	  ::= lsb(12, 1023);
   };

% +---+---+---+---+---+---+---+---+
% | 0   0   0   0   1 |ECN|  RSF  |
% +===+===+===+===+===+===+===+===+
% |PSH|    TTL    |      MSN      |
% +---+---+---+---+---+---+---+---+
% |lst|            CRC            |
% +---+---+---+---+---+---+---+---+
% |            ACK_SN...          |
% +---+---+---+---+---+---+---+---+
% | ...ACK_SN     |      SN...    |
% +---+---+---+---+---+---+---+---+
% |           ...SN               |
% +---+---+---+---+---+---+---+---+
% /         options_list          /  n*8 bits, if lst=1
%  --- --- --- --- --- --- --- ---


% SEQUENTIAL PACKET FORMATS

% +------+-----+-----+-----+-----+-----+-----+---------+
% |Name  |Disc |MSN  |ID   |SN   |ACK  |Win  |Comment  |
% +------+-----+-----+-----+-----+-----+-----+---------+
% |_1    |100  |4    |5    |16   |0    |     |         |
% +------+-----+-----+-----+-----+-----+-----+---------+
% |_2    |0011 |4    |6    |*6   |0    |     |         |
% +------+-----+-----+-----+-----+-----+-----+---------+
% |_3    |00100|4    |3    |0    |16   |     |         |
% +------+-----+-----+-----+-----+-----+-----+---------+
% |_4    |01   |4    |2    |0    |4    |     |         |
% +------+-----+-----+-----+-----+-----+-----+---------+
% |_5    |00000|4    |3    |12   |12   |     |         |
% +------+-----+-----+-----+-----+-----+-----+---------+
% |_6    |101  |4    |4    |*5   |12   |     |         |
% +------+-----+-----+-----+-----+-----+-----+---------+
% |_7    |00001|4    |3    |16   |0    |16   |         |
% +------+-----+-----+-----+-----+-----+-----+---------+
% |_8    |110  |4    |5    |0    |16   |16   |         |
% +------+-----+-----+-----+-----+-----+-----+---------+
% |_9    |00101|4    |3    |*5   |0    |11   |         |
% +------+-----+-----+-----+-----+-----+-----+---------+
% |_10   |00011|4    |4    |14   |14   |     |and more |
% +------+-----+-----+-----+-----+-----+-----+---------+


   % Send LSBs of sequence number
   format_seq_1 = discriminator, %[ 3 ]
		  ip_id,         %[ 5 ]
		  seq_number,	 %[ 16 ]
		  msn,		 %[ 4 ]
		  psh_flag,      %[ 1 ]
		  header_crc,	 %[ 3 ]
   {
      let ((ip_id_behavior:uncomp_value == 2) ||
           (ip_id_behavior:uncomp_value == 3));
      discriminator       ::= '100';
      msn                 ::= lsb(4, 4);
      ip_id               ::= ip_id_lsb (ip_id_behavior, msn, 5, 3);
      header_crc          ::= crc3 (this:uncomp_value,
                                    this:uncomp_length);
      psh_flag            ::= irregular (1);
      seq_number	  ::= lsb(16, 32767);
   };

% +---+---+---+---+---+---+---+---+
% | 1   0   0 |       IP-ID       |
% +===+===+===+===+===+===+===+===+
% |                               |
% +              SN               +
% |                               |
% +---+---+---+---+---+---+---+---+
% |      MSN      |PSH|    CRC    |
% +---+---+---+---+---+---+---+---+


   % Send scaled sequence number LSBs
   format_seq_2 = discriminator, %[ 4 ]
		  ip_id,         %[ 6 ]
		  seq_number_scaled, %[ 6 ]
		  msn,		 %[ 4 ]
		  psh_flag,      %[ 1 ]
		  header_crc,	 %[ 3 ]
   {
      let ((ip_id_behavior:uncomp_value == 2) ||
           (ip_id_behavior:uncomp_value == 3));
      discriminator       ::= '0011';
      msn                 ::= lsb(4, 4);
      ip_id               ::= ip_id_lsb (ip_id_behavior, msn, 6, 3);
      header_crc          ::= crc3 (this:uncomp_value,
                                    this:uncomp_length);
      psh_flag            ::= irregular (1);
      seq_number_scaled   ::= lsb(6, 31);
      seq_number_residue  ::= static;
   };

% +---+---+---+---+---+---+---+---+
% | 0   0   1   1 |     IP-ID...  |
% +===+===+===+===+===+===+===+===+
% | ...ID |      SN               |
% +---+---+---+---+---+---+---+---+
% |      MSN      |PSH|    CRC    |
% +---+---+---+---+---+---+---+---+


   % Send acknowledgement number LSBs
   format_seq_3 = discriminator, %[ 5 ]
		  ip_id,         %[ 3 ]
		  ack_number,	 %[ 16 ]
		  msn,		 %[ 4 ]
		  psh_flag,      %[ 1 ]
		  header_crc,	 %[ 3 ]
   {
      let ((ip_id_behavior:uncomp_value == 2) ||
           (ip_id_behavior:uncomp_value == 3));
      discriminator       ::= '00100';
      msn                 ::= lsb(4, 4);
      ip_id               ::= ip_id_lsb (ip_id_behavior, msn, 3, 3);
      header_crc          ::= crc3 (this:uncomp_value,
                                    this:uncomp_length);
      psh_flag            ::= irregular (1);
      ack_number	  ::= lsb(16, 16383);
   };

% +---+---+---+---+---+---+---+---+
% | 0   0   1   0   0 |   IP-ID   |
% +===+===+===+===+===+===+===+===+
% |                               |
% +            ACK_SN             +
% |                               |
% +---+---+---+---+---+---+---+---+
% |      MSN      |PSH|    CRC    |
% +---+---+---+---+---+---+---+---+


   % Send small ACK numbers for small packet ACK streams (telnet/ssh etc).
   format_seq_4 = discriminator, %[ 2 ]
		  ack_number,    %[ 4 ]
		  ip_id,         %[ 2 ]
   		  msn,		 %[ 4 ]
		  psh_flag,      %[ 1 ]
		  header_crc,	 %[ 3 ]
   {
      let ((ip_id_behavior:uncomp_value == 2) ||
           (ip_id_behavior:uncomp_value == 3));
      discriminator       ::= '01';
      msn                 ::= lsb(4, 4);
      % Note that due to having very few msn bits, no reordering offset
      ip_id               ::= ip_id_lsb (ip_id_behavior, msn, 2, 1);
      header_crc          ::= crc3 (this:uncomp_value,
                                    this:uncomp_length);
      psh_flag            ::= irregular (1);
      ack_number	  ::= lsb(4, 3);
   };

% +---+---+---+---+---+---+---+---+
% | 0   1 |    ACK_SN     | IP-ID |
% +===+===+===+===+===+===+===+===+
% |      MSN      |PSH|    CRC    |
% +---+---+---+---+---+---+---+---+


   % Send ACK and sequence number
   format_seq_5 = discriminator, %[ 5 ]
		  ip_id,         %[ 3 ]
		  ack_number,    %[ 12 ]
		  seq_number,    %[ 12 ]
		  msn,		 %[ 4 ]
		  psh_flag,      %[ 1 ]
		  header_crc,	 %[ 3 ]
   {
      let ((ip_id_behavior:uncomp_value == 2) ||
           (ip_id_behavior:uncomp_value == 3));
      discriminator       ::= '00000';
      msn                 ::= lsb(4, 4);
      ip_id               ::= ip_id_lsb (ip_id_behavior, msn, 3, 3);
      header_crc          ::= crc3 (this:uncomp_value,
                                    this:uncomp_length);
      psh_flag            ::= irregular (1);
      ack_number	  ::= lsb(12, 1023);
      seq_number	  ::= lsb(12, 2047);
   };

% +---+---+---+---+---+---+---+---+
% | 0   0   0   0   0 |   IP-ID   |
% +===+===+===+===+===+===+===+===+
% |            ACK_SN...          |
% +---+---+---+---+---+---+---+---+
% | ...ACK_SN     |      SN...    |
% +---+---+---+---+---+---+---+---+
% |           ...SN               |
% +---+---+---+---+---+---+---+---+
% |      MSN      |PSH|    CRC    |
% +---+---+---+---+---+---+---+---+


   % Send both ACK and scaled sequence number LSBs
   format_seq_6 = discriminator, %[ 3 ]
		  psh_flag,      %[ 1 ]
		  msn,		 %[ 4 ]
		  ip_id,         %[ 4 ]
  		  ack_number,    %[ 12 ]
		  seq_number_scaled, %[ 5 ]
		  header_crc,	 %[ 3 ]
   {
      let ((ip_id_behavior:uncomp_value == 2) ||
           (ip_id_behavior:uncomp_value == 3));
      discriminator       ::= '101';
      seq_number_scaled   ::= lsb(5, 15);
      seq_number_residue  ::= static;
      ip_id               ::= ip_id_lsb (ip_id_behavior, msn, 4, 3);
      ack_number	  ::= lsb(12, 1023);
      msn                 ::= lsb(4, 4);
      psh_flag            ::= irregular (1);
      header_crc          ::= crc3 (this:uncomp_value,
                                    this:uncomp_length);
   };

% +---+---+---+---+---+---+---+---+
% | 1   0   1 |     SN_SCALED     |
% +===+===+===+===+===+===+===+===+
% |     IP-ID     |    ACK_SN...  |
% +---+---+---+---+---+---+---+---+
% |         ...ACK_SN             |
% +---+---+---+---+---+---+---+---+
% |      MSN      |PSH|    CRC    |
% +---+---+---+---+---+---+---+---+


   % Send sequence number and window
   format_seq_7 = discriminator, %[ 5 ]
		  ip_id,         %[ 3 ]
		  seq_number,    %[ 16 ]
		  window,	 %[ 16 ]
		  msn,		 %[ 4 ]
		  psh_flag,      %[ 1 ]
		  header_crc,	 %[ 3 ]
   {
      let ((ip_id_behavior:uncomp_value == 2) ||
           (ip_id_behavior:uncomp_value == 3));
      discriminator       ::= '00001';
      msn                 ::= lsb(4, 4);
      ip_id               ::= ip_id_lsb (ip_id_behavior, msn, 3, 3);
      header_crc          ::= crc3 (this:uncomp_value,
                                    this:uncomp_length);
      psh_flag            ::= irregular (1);
      seq_number	  ::= lsb(16, 32767);
      window		  ::= irregular(16);
   };

% +---+---+---+---+---+---+---+---+
% | 0   0   0   0   1 |   IP-ID   |
% +===+===+===+===+===+===+===+===+
% |                               |
% +            ACK_SN             +
% |                               |
% +---+---+---+---+---+---+---+---+
% |                               |
% +              SN               +
% |                               |
% +---+---+---+---+---+---+---+---+
% |      MSN      |PSH|    CRC    |
% +---+---+---+---+---+---+---+---+


   % Send ACK and window
   format_seq_8 = discriminator, %[ 3 ]
		  ip_id,         %[ 5 ]
		  ack_number,    %[ 16 ]
		  window,	 %[ 16 ]
		  msn,		 %[ 4 ]
		  psh_flag,      %[ 1 ]
		  header_crc,	 %[ 3 ]
   {
      let ((ip_id_behavior:uncomp_value == 2) ||
           (ip_id_behavior:uncomp_value == 3));
      discriminator       ::= '110';
      msn                 ::= lsb(4, 4);
      ip_id               ::= ip_id_lsb (ip_id_behavior, msn, 5, 3);
      header_crc          ::= crc3 (this:uncomp_value,
                                    this:uncomp_length);
      psh_flag            ::= irregular (1);
      ack_number	  ::= lsb(16, 32767);
      window		  ::= irregular(16);
   };

% +---+---+---+---+---+---+---+---+
% | 1   1   0 |       IP-ID       |
% +===+===+===+===+===+===+===+===+
% |                               |
% +            ACK_SN             +
% |                               |
% +---+---+---+---+---+---+---+---+
% |                               |
% +            WINDOW             +
% |                               |
% +---+---+---+---+---+---+---+---+
% |      MSN      |PSH|    CRC    |
% +---+---+---+---+---+---+---+---+


   % Send scaled sequence number and window.
   format_seq_9 = discriminator, %[ 5 ]
		  ip_id,         %[ 3 ]
		  window,	 %[ 11 ]
		  seq_number_scaled, %[ 5 ]
		  msn,		 %[ 4 ]
		  psh_flag,      %[ 1 ]
		  header_crc,	 %[ 3 ]
   {
      let ((ip_id_behavior:uncomp_value == 2) ||
           (ip_id_behavior:uncomp_value == 3));
      discriminator       ::= '00101';
      msn                 ::= lsb(4, 4);
      ip_id               ::= ip_id_lsb (ip_id_behavior, msn, 3, 3);
      header_crc          ::= crc3 (this:uncomp_value,
                                    this:uncomp_length);
      psh_flag            ::= irregular (1);
      window		  ::= lsb(11, 1023);
      seq_number_scaled	  ::= lsb(5, 31);
      seq_number_residue  ::= static;
   };

% +---+---+---+---+---+---+---+---+
% | 0   0   1   0   1 |   IP-ID   |
% +===+===+===+===+===+===+===+===+
% |            WINDOW...          |
% +---+---+---+---+---+---+---+---+
% |...WINDOW  |     SN_SCALED     |
% +---+---+---+---+---+---+---+---+
% |      MSN      |PSH|    CRC    |
% +---+---+---+---+---+---+---+---+


   % A packet halfway between co_common and compressed packets
   % Can send LSBs of TTL, RSF flags, change ECN behavior and options list
   format_seq_10 = discriminator, %[ 5 ]
		   ttl_hopl,	  %[ 3 ]
		   ip_id,	  %[ 4 ]
		   msn,		  %[ 4 ]
		   ack_number,	  %[ 14 ]
		   rsf_flags,	  %[ 2 ]
		   seq_number,	  %[ 14 ]
		   psh_flag,      %[ 1 ]
		   ecn_used,	  %[ 1 ]
		   list_present,  %[ 1 ]
		   header_crc,	  %[ 7 ]
		   options_list,  % Nx8 bits
   {
      let ((ip_id_behavior:uncomp_value == 2) ||
           (ip_id_behavior:uncomp_value == 3));
      discriminator       ::= '00011';
      msn                 ::= lsb(4, 4);
      ip_id               ::= ip_id_lsb (ip_id_behavior, msn, 4, 3);
      header_crc          ::= crc7 (this:uncomp_value,
                                    this:uncomp_length);
      psh_flag            ::= irregular (1);
      list_present        ::= irregular(1);
      options_list        ::= tcp_list_presence_enc
                                      ((data_offset:uncomp_value + 20) / 4,
                                       list_present);
      rsf_flags           ::= rsf_index_enc;
      ecn_used		  ::= irregular(1);
      ttl_hopl		  ::= lsb(3, 3);
      seq_number	  ::= lsb(14, 8191);
      ack_number	  ::= lsb(14, 4095);
   };

% +---+---+---+---+---+---+---+---+
% | 0   0   0   1   1 |    TTL    |
% +===+===+===+===+===+===+===+===+
% |     IP-ID     |      MSN      |
% +---+---+---+---+---+---+---+---+
% |            ACK_SN...          |
% +---+---+---+---+---+---+---+---+
% |     ...ACK_SN         |  RSF  |
% +---+---+---+---+---+---+---+---+
% |              SN...            |
% +---+---+---+---+---+---+---+---+
% |       ...SN           |PSH|ECN|
% +---+---+---+---+---+---+---+---+
% |lst|            CRC            |
% +---+---+---+---+---+---+---+---+
% /         options_list          /  n*8 bits, if lst=1
%  --- --- --- --- --- --- --- ---

--------------020508050401080904010609
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--------------020508050401080904010609--



From rohc-bounces@ietf.org  Wed Dec  8 19:32:12 2004
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 TAA29448
	for <rohc-web-archive@ietf.org>; Wed, 8 Dec 2004 19:32:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcCL3-0006nn-EM
	for rohc-web-archive@ietf.org; Wed, 08 Dec 2004 19:39:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcCDG-0001hQ-7K; Wed, 08 Dec 2004 19:31:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcC8J-0000Nx-Ly
	for rohc@megatron.ietf.org; Wed, 08 Dec 2004 19:26:13 -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 TAA29043
	for <rohc@ietf.org>; Wed, 8 Dec 2004 19:26:07 -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 1CcCF7-0006hU-6m
	for rohc@ietf.org; Wed, 08 Dec 2004 19:33:17 -0500
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iB90Pov18613; Thu, 9 Dec 2004 02:25:54 +0200 (EET)
X-Scanned: Thu, 9 Dec 2004 02:26:31 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks001.ntc.nokia.com (8.12.9/8.12.9) id iB90QVf4017939;
	Thu, 9 Dec 2004 02:26:31 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks001.ntc.nokia.com 00q9SrxJ; Thu, 09 Dec 2004 02:26:31 EET
Received: from daebh001.NOE.Nokia.com (daebh001.americas.nokia.com
	[10.241.35.121])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iB90Lna19827; Thu, 9 Dec 2004 02:21:50 +0200 (EET)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by
	daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 8 Dec 2004 18:21:41 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] The discussion on slope(s)
Date: Wed, 8 Dec 2004 19:21:40 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B82891CF@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] The discussion on slope(s)
Thread-Index: AcTawXOzuOv7skxSR7ihN4Gd5o7f7ACvKS+Q
To: <kristofer.sandlund@effnet.com>
X-OriginalArrivalTime: 09 Dec 2004 00:21:41.0558 (UTC)
	FILETIME=[0E6C3D60:01C4DD85]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: quoted-printable
Cc: cabo@tzi.org, rohc@ietf.org, ghyslain.pelletier@ericsson.com,
        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.3 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: quoted-printable

Kristofer,

> The problem I was pointing out that we get context damage=20
> that will NEVER be detected on such a stream as I showed.=20

My understanding of your example is that an undetected error
in an update packet (say X) can lead to a wrong slope on the=20
decompressor side. However, the undetected error in X will be=20
likely (if not absolutely by theory) detected when the=20
compressor sends the next update packet Y. Note that Y uses X
as reference. Once the context damage is detected, NACK(s) will
be sent by decompressor and compressor will re-establish context,
including slope.=20

Also to put things into perspective, the chance of an undetected=20
error in an UOR-2 packet is low, should be less than 1/128 due=20
to 7-bit CRC. In practice, it should be even lower since residual
errors are *real* headache to ROHC (see section 5.3.2.2.5).

Another note is that R-0-CRC has to be sent at least every 64 SO=20
packets. That curbs the residual error propagation. Of course, this=20
does not help for a short SO state like in your example. If the=20
compressor is unsure, it should send R-0-CRC in the middle of a string=20
even if it doesn't have to. Or, it can re-sync the slope even if
it is the same as the previous string.

> Could you please comment on the worst-case mail, since to me=20
> this is a  huge problem. You could (theoretically at least) have=20
> a video stream running for days in a row, without detecting that=20
> the context is damaged.

Please see above.

> Also, the second-biggest problem to me is the actual updating of the=20
> slope (both in U/O and R-mode) and so far, the examples you have=20
> provided have only dealt with situations where the slope has already=20
> been set. It would be interesting to see some of this as well.

I guess your question is what happens if current slope !=3D =
default-slope?=20
I think I explained in the email to Carsten. But let me know if
I wasn't clear.

BR, Zhigang
=20

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


From rohc-bounces@ietf.org  Wed Dec  8 21:09:51 2004
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 VAA09253
	for <rohc-web-archive@ietf.org>; Wed, 8 Dec 2004 21:09:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcDrY-0000T8-ND
	for rohc-web-archive@ietf.org; Wed, 08 Dec 2004 21:17:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcDU3-0008OG-Vy; Wed, 08 Dec 2004 20:52:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcDSq-0007tz-5D
	for rohc@megatron.ietf.org; Wed, 08 Dec 2004 20:51:28 -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 UAA06014
	for <rohc@ietf.org>; Wed, 8 Dec 2004 20:51:26 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcDZf-0008Oa-TE
	for rohc@ietf.org; Wed, 08 Dec 2004 20:58:35 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <YHL6RXRQ>; Thu, 9 Dec 2004 01:52:40 -0000
Received: from mjw-pc.roke.co.uk ([193.118.194.159]) by rsys002a.roke.co.uk
	with SMTP (Microsoft Exchange Internet Mail Service Version
	5.5.2657.72) id YF4R0W0F; Thu, 9 Dec 2004 01:52:47 -0000
From: "West, Mark" <mark.a.west@roke.co.uk>
To: rohc@ietf.org
Date: Thu, 9 Dec 2004 01:50:49 +0000 (GMT)
X-X-Sender: maw@mjw-pc.roke.co.uk
Subject: RE: [rohc] The discussion on slope(s) (redux)
Message-ID: <Pine.LNX.4.44.0412090109280.26529-100000@mjw-pc.roke.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32029c790f79bd4a84a26bd2915c54b9
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: 850245b51c39701e2700a112f3032caa


Hi All,

We decided it was about time we put our two penn'orth / Eurocent / Kronor
/ cents / whatever (or more) into this discussion.  This is going to be
quite a long mail so we'll put a summary first with detail to support it
below:

Firstly, and as no great surpise, we agree that the concept of slope in
3095 is confused and not properly defined. :-)

In particular, we agree that the concept of implicit slope has potential
synchronisation problems; and we don't believe has been actually
implemented / tested.

However, we do think that the concept of slope is useful for compressing
timestamp efficiently (particularly in the case of video).  It could also,
perhaps, have been used to solve the linux-zero-ip-id-problem..!

Consequently, it seems best for the implementers' guide to clarify that,
although the concept of slope exists in 3095, it is confused and either:
- should not be considered at all; or
- (if it is 'used') that there is no way to change the default slope.

As we'll explain below, though, it is possible to define and use slope to
compress 'video'-style RTP headers efficiently; we just think that is
should be done with explicit signalling of slope.  (As to 'how': well,
that's a separate thread!)  We'd certainly support more discussion on this
approach!


Without further ado, here's the gory detail:

First of all, from reading the quoted sections of 3095, the concept of
slope is confused.  Before thinking about timestamp, let's consider IP-ID.

IP-ID is a non SN field so according to 5.1.2.2 it should follow the rule:

  non-SN-field = SN * slope + offset           [1]

Fine.  But section 4.5.5 states that for the IP-ID the offset should be
compressed with LSB encoding and the offset is given by:

  Offset_i = ID_i - SN_i,                      [2]

To make these equations compatible, the slope for IP-ID is fixed and equal
to 1.

First "Question to implementers": do you solely rely on equation [2] for
compressing IP-ID or do you include the concept of slope?  (I assume by
the fact that we have interoperable implementations, that we actually all
just use equation [2].)

Section 5.7 makes no mention of default-slope(IP-ID) but it does say that
the default-slope(IP_ID_offset) is 0.  Referring to the default-slope
(IP_ID_offset) implies that IP_ID_offset can fit into equation [1].  If
you put it into equation [1] you either stick with the default-slope
(IP_ID_offset) = 0 and equation [1] is the identity OR you allow the slope
to change and equation [1] becomes recursive :-( We assume, therefore,
that this has to indicate a mistake, somewhere along the line...

If we do consider the possibility of using equation [1] for IP-ID, then,
with a slope of zero, the linux-zero-ip-id-behaviour (for which there is a
completely different and new solution in the ip-only profile) could be
handled.  However, there is no way to change the slope of IP-ID within
3095 and we would hazard a guess that none of the implementers, at least,
considered slope with respect to IP-ID.

Another question is: what is the expected behaviour in the case where the
source IP stack is sending two flows which happen to be alternating
packets?  This may lead to the IP-ID for each flow incrementing in regular
steps of 2.  From what's in the rfc and what we *assume* folks have
implemented, we believe that LSBs of IP-ID-offset would be sent in every
packet and you'd never reach SO state.  Any comments..?

Why are we waffling on about IP-ID, I hear you ask?

Because it's all related in the dingy soup of RFC 3095!

But, OK, let's consider timestamp.  Again it is a non-SN-field so it can
be expressed using equation [1].  However, 4.5.3 also defines scaling
using the equation:

  TS = TS_SCALED * TS_STRIDE + TS_OFFSET		[3]

Point 2 of this section states that TS_SCALED can be compressed using
either W-LSB encoding or timer-based encoding.  Obviously in this
discussion we are focussing on W-LSB encoding.  Consider the audio case:

> Example 1 (audio stream with TS_STRIDE = 160):
>
>             <------ String 1 ------>    <-- String 2 --->
> SN           11  12  13  14 ...   60    61    62    63    64 ...
> TS          200 360 420 580 ... 8040 16040 16200 16360 16520 ...
> TS_SCALED     1   2   3   4 ...   50   100   101   102   103 ...
> TS_OFFSET    40  40  40  40       40    40    40    40    40 ...

If you compress TS_SCALED using W-LSB encoding, then in the same way as
for SN you will need to send LSBs on *EVERY* packet (so you'll never get
to SO state).  4.5.3 says nothing about relating TS_SCALED to SN.

So when _we_ (at least) implemented 3095 we assumed that once you had
scaled the TS you offset it from the SN in the same way as for IP-ID.
That is, you get extra lines in the above table:

TS_SC_offset -10 -10 -10 -10 ...   -10    39    39    39    39 ...
send (LSB)   -10 -10 -10  -  ...    -     39    39    39     - ...

We send the LSBs of the TS_SC_offset value rather than of the TS_SCALED
value.  Question to other implementers: do you do the same?  (We assume
so, otherwise we don't see how we interoperated - which we did last time
we came out to play [which was a couple of interops ago, but...])

If this assumption is correct, then we are all using the equations:

  TS = (SN + TS_SC_offset) * TS_STRIDE + TS_OFFSET	[4]

Which assumes:

  TS_SCALED = SN + TS_SC_offset 				[5]

Therefore we are actually considering TS_SCALED as a non-SN-field that
follows equation [1] with a fixed slope of 1.

Note that if this assumption is *NOT* correct, then the LSBs can only be
applied to TS_SCALED.  But that, we believe, would assume a fixed
TS_SC_offset (i.e. a slope of 1...)

The main problem comes when we consider video:

If we set TS_STRIDE to 3000, as suggested by Zhigang, we get:

              <------ String 1 ---------->  <-- String 2 --->
SN              11    12    13  ...    25    26    27    28    29    30...
TS            4000  4000  4000  ...  4000  7000  7000  7000  7000  7000...
TS_SCALED        1     1     1  ...     1     2     2     2     2     2...
TS_OFFSET     1000  1000  1000  ...  1000  1000  1000  1000  1000  1000...
TS_SC_OFFSET   -10   -11    -12 ...   -24   -24   -25   -26   -27   -28...
send (LSB)     -10   -11    -12 ...   -24   -24   -25   -26   -27   -28...

We are, once again, having to send LSBs of a timestamp related field on
*EVERY* packet.

Does setting TS_STRIDE to zero (and restating the equations to avoid
division by zero), as suggested by Kristofer and Lars-Erik help?  No,
because we get:

              <------ String 1 ---------->  <-- String 2 --->
SN              11    12    13  ...    25    26    27    28    29    30...
TS            4000  4000  4000  ...  4000  7000  7000  7000  7000  7000...
TS_SCALED        -     -     -  ...     -     -     -     -     -     -...
TS_OFFSET     4000  4000  4000  ...  4000  7000  7000  7000  7000  7000...
TS_SC_OFFSET -3989 -3988  -3987 ... -3975 -6974 -6973 -6972 -6971 -6970...
send (LSB)   -3989 -3988  -3987 ... -3975 -6974 -6973 -6972 -6971 -6970...

We're still sending LSBs of a timestamp related field on EVERY packet.

Consequently, we think the "real" equation required for timestamp (and,
in fact, any 'non-SN-field') is:

  TS = (a * SN + off_a) * b + off_b		[6]

where we might refer to 'a' as 'slope' and 'b' as 'scale' and 'off_b' is
in the range 0 .. off_b - 1.

Thus, setting a (slope) to 1 and b (scale) to 1 (eliminating off_b), we
get:

  x = (SN + off_a)				[7]

which is exactly the IP-ID case.

Setting a (slope) to 1, off_a to TS_SC_offset,  b (scale) to TS_STRIDE,
and off_b to TS_OFFSET, we get:

  TS = (SN + TS_SC_offset) * TS_STRIDE + TS_OFFSET		[8]

But allowing the slope to vary gives:

  TS = (a * SN + TS_SC_offset) * TS_STRIDE + TS_OFFSET		[9]

This assumes:

  TS_SCALED = a * SN + TS_SC_offset			[10]

Which, [9], is in exactly the form of equation [1].  In the audio case a =
1, in the video case a = 0.

Thus, we think that the concept of slope (= a) is useful to state
explicitly and use explicitly for the most efficient compression of
timestamp in the widest set of cases.

*BUT*, it's a bit of a mess in 3095, as it stands.

We also agree with Kristofer, that the idea of *implicit* slope could lead
to incorrectly decompressed R-mode packets being passed up the stack
without detection (see
http://www.ietf.org/mail-archive/web/rohc/current/msg03067.html).

Zhigang's latest mail answers this in part: but we haven't thought through
the implications of "change of slope" fully -- i.e. how to re-evaluate 'a'
whilst sending TS_SC_offset for 'a != 1'.  Frankly, though, it seems
complex and error prone.  (The derivation of TS_OFFSET, in contrast,
requires only the use of the fact that a/b gives a quotiant and remainder
such that a=b*q+r, with 0<=r<q).

Also, if the implementers' guide were to state that there was implicit
slope for timestamp, then why would this not apply to IP ID?  (Although it
appears that the application of this to IP ID is internally
contradictory...)

Anyway, for slope to be useful, we think that it's best if it is:

- Clearly defined;
- Applicable in all modes;
- Explicitly transmitted; and
- Explicitly applied (or not) to each applicable 'non-SN-field'.

Therefore, with respect to the implementers' guide, our proposal is that
it should either:

- indicate that the concept of slope exists; but that there is no way to
change the 'default' slope and that the slope for both IP-ID and TS_SCALED
is 1; or

- that the concept of slope is ill-defined and should not be used, at all.

We prefer the former, as this opens the way to make use of an explicitly
signalled slope to make the compression (at least of TS) more flexible.
As to how such explicit signalling could be done (new control field;
random abuse of the existing control fields; ...), well that's a different
discussion!

There may be a couple of other points that we intended to make, but this
feels like a reasonable summary of our opinion(s).  And if you've actually
read this far, then we're really quite impressed..!

Cheers,

Abbie and Mark

PS -- Abbie did most of the serious thinking; any random errors are
probably mine!


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


From rohc-bounces@ietf.org  Thu Dec  9 02:14:44 2004
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 CAA26104
	for <rohc-web-archive@ietf.org>; Thu, 9 Dec 2004 02:14:44 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcIcb-0006P2-Uw
	for rohc-web-archive@ietf.org; Thu, 09 Dec 2004 02:21:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcIUn-0007ld-IV; Thu, 09 Dec 2004 02:13:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcITV-00075f-AE
	for rohc@megatron.ietf.org; Thu, 09 Dec 2004 02:12:29 -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 CAA24054
	for <rohc@ietf.org>; Thu, 9 Dec 2004 02:12:28 -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 1CcIaR-0006NC-10
	for rohc@ietf.org; Thu, 09 Dec 2004 02:19:39 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iB97CMJm008648; Thu, 9 Dec 2004 08:12:24 +0100 (MET)
In-Reply-To: <Pine.LNX.4.44.0412090109280.26529-100000@mjw-pc.roke.co.uk>
References: <Pine.LNX.4.44.0412090109280.26529-100000@mjw-pc.roke.co.uk>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <ABA48B4C-49B1-11D9-B3CF-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] The discussion on slope(s) (redux)
Date: Thu, 9 Dec 2004 08:12:22 +0100
To: "West, Mark" <mark.a.west@roke.co.uk>
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: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, rohc@ietf.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.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit

Mark,

I believe 4.5.3 is quite explicit about what we send if we *do* send a 
(scaled) timestamp.
So I think your proposal to explicitly send an offset (TS_scaled - SN) 
instead of just the timestamp is not supported by the text.

The issue we have, I think, is that 3095 is not very explicit about 
what we do when we *don't* send a field.
Indeed, my assumption here is that this is the place where the 
default-slope values come in.
What 5.7 tells me is that for IP-ID-offset, default-slope is 0, and for 
TS-scaled, default-slope is 1.
Both mean the same: the default value for a non-encoded field is 
growing with the SN, both IP-ID slope and TS-scaled slope are set to 1.

(Note that defining a default-slope for Tsc=0 is just covering for the 
special case of an ext3 with Tsc==0 and R-TS==0 -- we can live with a 
variable slope here because it is explicitly signaled as TS_STRIDE, but 
I have no idea why you would use this combination in the first place, 
except that you can.)

In summary, I believe the text of 3095 supports your proposal 1.

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Thu Dec  9 02:42:52 2004
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 CAA28188
	for <rohc-web-archive@ietf.org>; Thu, 9 Dec 2004 02:42:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcJ3r-0006ou-Dw
	for rohc-web-archive@ietf.org; Thu, 09 Dec 2004 02:50:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcIv0-0001NJ-6X; Thu, 09 Dec 2004 02:40:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcIr5-0000L6-F9
	for rohc@megatron.ietf.org; Thu, 09 Dec 2004 02:36:51 -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 CAA27749
	for <rohc@ietf.org>; Thu, 9 Dec 2004 02:36:50 -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 1CcIy0-0006hH-E6
	for rohc@ietf.org; Thu, 09 Dec 2004 02:44:01 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iB97aasE016617; Thu, 9 Dec 2004 08:36:37 +0100 (MET)
In-Reply-To: <7B5AF06E216CB74DA8A5960A3181B5B82891CF@ajebe001.americas.nokia.com>
References: <7B5AF06E216CB74DA8A5960A3181B5B82891CF@ajebe001.americas.nokia.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <0DFEE498-49B5-11D9-B3CF-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] The discussion on slope(s)
Date: Thu, 9 Dec 2004 08:36:35 +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: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, rohc@ietf.org,
        kristofer.sandlund@effnet.com, 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: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit

> decompressor side. However, the undetected error in X will be
> likely (if not absolutely by theory) detected when the
> compressor sends the next update packet Y. Note that Y uses X
> as reference.

But it won't use any "slope" component of X as a reference unless it is 
a R-0-CRC.
I think that has been Kristofer's main concern:  A dynamic slope 
element of the context would not be protected by a CRC in any other 
header than R-0-CRC (and a few more less likely cases that also don't 
explicitly send a timestamp such as UOR-2-ID).

> Also to put things into perspective, the chance of an undetected
> error in an UOR-2 packet is low, should be less than 1/128 due
> to 7-bit CRC. In practice, it should be even lower since residual
> errors are *real* headache to ROHC (see section 5.3.2.2.5).

One would hope so.
Unfortunately, hope is a not really a legitimate protocol mechanism :-)

> Another note is that R-0-CRC has to be sent at least every 64 SO
> packets.

I think Kristofer's example shows that this may not always be the case, 
because you may be forced to send context-updating packets that do 
include a TS.
The part I'm not sure about is why Kristofer thinks these wouldn't 
update the dynamic slope, too.
(I don't think anyone has proposed a detailed algorithm for when/how 
exactly dynamic slopes would be updated, yet.)

> That curbs the residual error propagation. Of course, this
> does not help for a short SO state like in your example. If the
> compressor is unsure, it should send R-0-CRC in the middle of a string
> even if it doesn't have to.

Requiring the compressor to periodically send slope-validating headers 
(i.e., with CRC, but without TS) would indeed solve Kristofer's issue.
(This is, essentially, including a grain of U/O mode thinking into R 
mode, just to cover the dynamic slope which is not protected by the 
CRC.)

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Thu Dec  9 04:16:57 2004
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 EAA04593
	for <rohc-web-archive@ietf.org>; Thu, 9 Dec 2004 04:16:57 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcKWl-00008s-KS
	for rohc-web-archive@ietf.org; Thu, 09 Dec 2004 04:24:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcKO0-0000Am-SV; Thu, 09 Dec 2004 04:14:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcKG7-0007Kb-VJ
	for rohc@megatron.ietf.org; Thu, 09 Dec 2004 04:06:48 -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 EAA04043
	for <rohc@ietf.org>; Thu, 9 Dec 2004 04:06:46 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcKMr-0008Pq-OL
	for rohc@ietf.org; Thu, 09 Dec 2004 04:13:59 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iB996XO6016590 for <rohc@ietf.org>; Thu, 9 Dec 2004 10:06:33 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 9 Dec 2004 10:06:33 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <XVCWT3HQ>; Thu, 9 Dec 2004 10:06:29 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E9A07@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'Carsten Bormann'" <cabo@tzi.org>, "West, Mark" <mark.a.west@roke.co.uk>
Subject: RE: [rohc] The discussion on slope(s) (redux)
Date: Thu, 9 Dec 2004 10:06:04 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 09 Dec 2004 09:06:33.0359 (UTC)
	FILETIME=[60FFB9F0:01C4DDCE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: rohc@ietf.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.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581

> Mark,
> 
> I believe 4.5.3 is quite explicit about what we send if we 
> *do* send a (scaled) timestamp. The issue we have, I think,
> is that 3095 is not very explicit about what we do when we
> *don't* send a field.

Exactly. This is the compression step. While 4.5.3 only talkes
about scaling, the actual compression step is in 4.5.3 referred
to as "WLSB or timer-based". This is indeed correct, I think,
but 3095 is not completely clear on how certain fields are
compressed based on other fields, i.e. the details TS and IP-ID
details for how to decompress them if no bits are actually sent.

/L-E


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


From rohc-bounces@ietf.org  Thu Dec  9 05:26:25 2004
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 FAA09181
	for <rohc-web-archive@ietf.org>; Thu, 9 Dec 2004 05:26:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcLcA-0001XB-Gb
	for rohc-web-archive@ietf.org; Thu, 09 Dec 2004 05:33:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcLL3-000209-1v; Thu, 09 Dec 2004 05:15:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcLIN-0001AZ-1Y
	for rohc@megatron.ietf.org; Thu, 09 Dec 2004 05:13:11 -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 FAA08151
	for <rohc@ietf.org>; Thu, 9 Dec 2004 05:13:09 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcLPK-0001Fn-Gh
	for rohc@ietf.org; Thu, 09 Dec 2004 05:20:22 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <YHL6R6TD>; Thu, 9 Dec 2004 10:14:29 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8803D5AA5@rsys004a.roke.co.uk>
From: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
To: "'Carsten Bormann'" <cabo@tzi.org>, "West, Mark"
	<mark.a.west@roke.co.uk>,
        rohc@ietf.org
Subject: RE: [rohc] The discussion on slope(s) (redux)
Date: Thu, 9 Dec 2004 10:14:26 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
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: b132cb3ed2d4be2017585bf6859e1ede

Hi Carsten, all,
> 
> I believe 4.5.3 is quite explicit about what we send if we 
> *do* send a 
> (scaled) timestamp.
> So I think your proposal to explicitly send an offset 
> (TS_scaled - SN) 
> instead of just the timestamp is not supported by the text.

I've just double-checked our code and you are right.  We have an
interoperable implementation that does send bits of TS_SCALED not bits of
TS_SC_offset.  (Sorry for causing (even more) confusion.)
 
However, we use the concept of TS_SC_offset to work out whether to send any
bits of TS_SCALED.

Section 4.5.3 says 'compression method could be either W-LSB encoding or
Timer-based...' which makes no mention of slopes.  Consequently, I think
that 4.5.3 says if you don't use timer based compression then you use W-LSB
(in the same way as for SN), thereby sending LSBs in every packet for an
increasing field.
> 
> The issue we have, I think, is that 3095 is not very explicit about 
> what we do when we *don't* send a field.

I think that 3095 is not very explicit about *whether/when* we don't send a
field, as well as what we do when we don't send it.

> Indeed, my assumption here is that this is the place where the 
> default-slope values come in.

That would make sense.  However, it's too subtle in the RFC for me ;-) it's
certainly not something I considered when implementing it.

> What 5.7 tells me is that for IP-ID-offset, default-slope is 
> 0, and for 
> TS-scaled, default-slope is 1.

5.7 says that the default-slope for TS is 1.  I assume that in this case, TS
is actually referring to TS_SCALED?  Otherwise you've got an equation like:

TS = slope * SN x+ offset and the concept of TS_STRIDE has disappeared?

> Both mean the same: the default value for a non-encoded field is 
> growing with the SN, both IP-ID slope and TS-scaled slope are 
> set to 1.

I'm a bit confused here.  In the IP-ID case we have:

Non-encoded field = IP-ID
Encoded field = IP-ID-offset
Default slope of encoded field stated = 0 (as stated in 5.7)
Implies slope of non-encoded field = 1

In the Timestamp case we have:

Non-encoded field = TS
Encoded field = TS_SCALED
Default slope of encoded field stated = 1 (assuming TS in 5.7 is TS_SCALED)
Which says nothing about the non-encoded field.

So in the IP-ID case the non-encoded field grows with SN and in the
Timestamp case the encoded field grows with SN.

When doing our implementation, and in a (possibly vain) attempt to harmonise
the handling of TS/IP_ID, we *conceptually* treat it as:

'Non-encoded' field = TS_SCALED
'Encoded' field = TS_SC_OFFSET
Assumed default slope of encoded field = 0
Implies slope of non-encoded field = 1
*BUT* when bits are required for 'encoded' field, actually *send* bits of
'non-encoded' field (and hope that the other end will interpret it
correctly..!)

> 
> (Note that defining a default-slope for Tsc=0 is just 
> covering for the 
> special case of an ext3 with Tsc==0 and R-TS==0 -- we can live with a 
> variable slope here because it is explicitly signaled as 
> TS_STRIDE, but 
> I have no idea why you would use this combination in the first place, 
> except that you can.)
> 
Agreed.  This highlights the fact that there are two concepts - scale
(TS_STRIDE) and slope.

So, normally:
- you use slope = 1 you set scale = TS_STRIDE
- in the 'ext3 Tsc==0...' case you set slope to TS_STRIDE (and scale is 1)
  giving (assuming TS_STRIDE of 160):

    TS = (160 * SN + offset) * 1 + 0

In the case where no bits are sent, which you do makes no difference (a
change in SN gives the same change in TS either way).  In the case where
bits are sent, the bits sent and the interpretation that should be put on
them depends on which way round you have defined scale and slope.

> In summary, I believe the text of 3095 supports your proposal 1.

I'm not sure which you're referring to as proposal 1?

Best regards,

Abbie

> 
> Gruesse, Carsten
> 
> 
> _______________________________________________
> 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


From rohc-bounces@ietf.org  Thu Dec  9 06:56:51 2004
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 GAA15723
	for <rohc-web-archive@ietf.org>; Thu, 9 Dec 2004 06:56:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcN1i-0003LV-8T
	for rohc-web-archive@ietf.org; Thu, 09 Dec 2004 07:04:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcMqF-0004O9-Q4; Thu, 09 Dec 2004 06:52:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcMnn-0003wi-N6
	for rohc@megatron.ietf.org; Thu, 09 Dec 2004 06:49:43 -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 GAA15300
	for <rohc@ietf.org>; Thu, 9 Dec 2004 06:49:41 -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 1CcMub-0003Cl-Rv
	for rohc@ietf.org; Thu, 09 Dec 2004 06:56:56 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iB9BnOWe013906; Thu, 9 Dec 2004 12:49:26 +0100 (MET)
In-Reply-To: <3F2E01E1D7B04F4EBEC92D3FA324D8803D5AA5@rsys004a.roke.co.uk>
References: <3F2E01E1D7B04F4EBEC92D3FA324D8803D5AA5@rsys004a.roke.co.uk>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <5F49D36A-49D8-11D9-B3CF-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] The discussion on slope(s) (redux)
Date: Thu, 9 Dec 2004 12:49:24 +0100
To: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
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: 68ba2b07ef271dba6ee42a93832cfa4c
Content-Transfer-Encoding: 7bit
Cc: "West, Mark" <mark.a.west@roke.co.uk>, Carsten Bormann <cabo@tzi.org>,
        rohc@ietf.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.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Content-Transfer-Encoding: 7bit

> However, we use the concept of TS_SC_offset to work out whether to 
> send any
> bits of TS_SCALED.

Right, since this is about whether you send it at all.

> Section 4.5.3 says 'compression method could be either W-LSB encoding 
> or
> Timer-based...' which makes no mention of slopes.  Consequently, I 
> think
> that 4.5.3 says if you don't use timer based compression then you use 
> W-LSB
> (in the same way as for SN), thereby sending LSBs in every packet for 
> an
> increasing field.

Again, 4.5 has this problem in that it describes what you send if you 
do send.

>> The issue we have, I think, is that 3095 is not very explicit about
>> what we do when we *don't* send a field.
>
> I think that 3095 is not very explicit about *whether/when* we don't 
> send a
> field, as well as what we do when we don't send it.

Well, that rule is simple: You can only "not send" if the decompressor 
will regenerate the right header!
So the rule is implictly created from the rule that says what the 
decompressor will do if a field is not encoded in the header.

>> Indeed, my assumption here is that this is the place where the
>> default-slope values come in.
>
> That would make sense.  However, it's too subtle in the RFC for me ;-) 
> it's
> certainly not something I considered when implementing it.

Yes, I think we all agree that's a bug in the RFC.

>> What 5.7 tells me is that for IP-ID-offset, default-slope is
>> 0, and for
>> TS-scaled, default-slope is 1.
>
> 5.7 says that the default-slope for TS is 1.

Well, it says this in a somewhat disambiguating context:

       If value(Tsc) = 1, Scaled RTP Timestamp encoding is used before
       compression (see section 4.5.3), and default-slope(TS) = 1.

       If value(Tsc) = 0, the Timestamp value is compressed as-is, and
       default-slope(TS) = value(TS_STRIDE).

> I assume that in this case, TS
> is actually referring to TS_SCALED?

Yes, this is how I read it.
The problem is that a lot of other places also just say "TS" and really 
mean "the thing that you get out of section 4.5 to encode TS".

>> Both mean the same: the default value for a non-encoded field is
>> growing with the SN, both IP-ID slope and TS-scaled slope are
>> set to 1.
>
> I'm a bit confused here.  In the IP-ID case we have:
>
> Non-encoded field = IP-ID
> Encoded field = IP-ID-offset
> Default slope of encoded field stated = 0 (as stated in 5.7)
> Implies slope of non-encoded field = 1

Yes.

> In the Timestamp case we have:
>
> Non-encoded field = TS
> Encoded field = TS_SCALED
> Default slope of encoded field stated = 1 (assuming TS in 5.7 is 
> TS_SCALED)
> Which says nothing about the non-encoded field.

No.  Neither did I, above?

> So in the IP-ID case the non-encoded field grows with SN and in the
> Timestamp case the encoded field grows with SN.

That's my conclusion, which I would put slightly differently:
With IP-ID, if it is not encoded in the header, it grows in parallel SN.
With TS, if it is not encoded in the header, it grows in parallel with 
TS_STRIDE*SN (independent of Tsc!).

> When doing our implementation, and in a (possibly vain) attempt to 
> harmonise
> the handling of TS/IP_ID, we *conceptually* treat it as:
>
> 'Non-encoded' field = TS_SCALED
> 'Encoded' field = TS_SC_OFFSET
> Assumed default slope of encoded field = 0
> Implies slope of non-encoded field = 1
> *BUT* when bits are required for 'encoded' field, actually *send* bits 
> of
> 'non-encoded' field (and hope that the other end will interpret it
> correctly..!)

You lost me.
Maybe "non-encoded" and "encoded" mean something different here than in 
my mind...

>> In summary, I believe the text of 3095 supports your proposal 1.
>
> I'm not sure which you're referring to as proposal 1?

The first one of:

>>> Therefore, with respect to the implementers' guide, our proposal is 
>>> that
>>> it should either:
>>>
>>> - indicate that the concept of slope exists; but that there is no 
>>> way to
>>> change the 'default' slope and that the slope for both IP-ID and 
>>> TS_SCALED
>>> is 1; or
>>>
>>> - that the concept of slope is ill-defined and should not be used, 
>>> at all.

I would maybe word it slightly differently, as the text explicitly says 
that "default-slope(IP-ID offset) = 0", which of course *is* equivalent 
to "default-slope(IP-ID) = 1".

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Thu Dec  9 08:07:56 2004
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 IAA19713
	for <rohc-web-archive@ietf.org>; Thu, 9 Dec 2004 08:07:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcO8J-0004g6-T8
	for rohc-web-archive@ietf.org; Thu, 09 Dec 2004 08:15:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcNvG-0002QT-AA; Thu, 09 Dec 2004 08:01:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcNrb-0001LA-Ud
	for rohc@megatron.ietf.org; Thu, 09 Dec 2004 07:57:44 -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 HAA18721
	for <rohc@ietf.org>; Thu, 9 Dec 2004 07:57:43 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcNyO-0004NL-Js
	for rohc@ietf.org; Thu, 09 Dec 2004 08:04:57 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iB9CvTh5011816
	for <rohc@ietf.org>; Thu, 9 Dec 2004 13:57:29 +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); 
	Thu, 9 Dec 2004 13:57:29 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <XVCWVP5Y>; Thu, 9 Dec 2004 13:57:29 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E9A0A@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'Carsten Bormann'" <cabo@tzi.org>,
        "Surtees, Abigail"
	<abigail.surtees@roke.co.uk>
Subject: RE: [rohc] The discussion on slope(s) (redux)
Date: Thu, 9 Dec 2004 13:57:23 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 09 Dec 2004 12:57:29.0122 (UTC)
	FILETIME=[A3AD6020:01C4DDEE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: "West, Mark" <mark.a.west@roke.co.uk>, rohc@ietf.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.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0

Folks,

> > So in the IP-ID case the non-encoded field grows with SN and in the
> > Timestamp case the encoded field grows with SN.
> 
> That's my conclusion, which I would put slightly differently:
> With IP-ID, if it is not encoded in the header, it grows in 
> parallel SN.
> With TS, if it is not encoded in the header, it grows in 
> parallel with TS_STRIDE*SN (independent of Tsc!).

Which could also be expressed as:
With TS, if it is not encoded in the header, its scaled
representation grows in parallel with TS_STRIDE.

TS can thus be communicated in three ways:
1) Unscaled
2) SCALED and sent with WLSB
3) SCALED, inferred from SN

It seems like 1) and 2) are "clear" from 3095, while what is really
missing is a defined decompression (and thus compression)
logic for 3). The "default slope" value would be an important
part of that logic, and I guess most implementers have actually
used that value for the simple function
TS_SCALED=(SN-SN_OLD)*default_slope + TS_SCALED(SN_OLD)
for decompression of TS_SCALED when no TS bits are sent.

Q: Would default_slope be used when decompressing based
   on TS bits actually sent?
Q: Can default_slope be anything but 1? 
Q: Can TS bits ever be omitted when sent unscaled?

I think the answers to all these questions are all NO!
Therefore, I do not think default_slope would ever (when used)
be equal to TS_STRIDE, as stated on page 75.

To sum up, we seem to agree that either there should be no mentioning
of slope at all, or it should not be possible to change the default
slope. Personally, I read these two as meaning the same thing, but in
any case we have a strong agreement on not doing any implicit slope
updates, which is the most important point from these discussions.
 
For TS, I therefore conclude that we will have to clarify 3).

For IP-ID, 4.5.5 is very clear on how to decompress the ID with
offset IP-ID encoding, both with and without ID offset bits in the
header. Since IP-ID is always offset encoded if sent compressed,
I think there is nothing missing when it comes to IP-ID and slopes,
more than to clarify the meaning of default_slope on page 75, which
simply means exactly what is said on the second and third line of
page 35 (the additional mentioning on page 75 is thus just confusing). 

/L-E
 

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


From rohc-bounces@ietf.org  Thu Dec  9 08:43:38 2004
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 IAA21805
	for <rohc-web-archive@ietf.org>; Thu, 9 Dec 2004 08:43:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcOh2-0005Kk-HT
	for rohc-web-archive@ietf.org; Thu, 09 Dec 2004 08:50:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcOWj-0000kS-Ch; Thu, 09 Dec 2004 08:40:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcOMZ-0007TU-8J
	for rohc@megatron.ietf.org; Thu, 09 Dec 2004 08:29:43 -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 IAA20751
	for <rohc@ietf.org>; Thu, 9 Dec 2004 08:29:42 -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 1CcOTX-00050T-Ab
	for rohc@ietf.org; Thu, 09 Dec 2004 08:36:56 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iB9DTDEx007506; Thu, 9 Dec 2004 14:29:31 +0100 (MET)
In-Reply-To: <A943FD84BD9ED41193460008C7918050072E9A0A@ESEALNT419.al.sw.ericsson.se>
References: <A943FD84BD9ED41193460008C7918050072E9A0A@ESEALNT419.al.sw.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <5FAA9894-49E4-11D9-B3CF-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] The discussion on slope(s) (redux)
Date: Thu, 9 Dec 2004 14:15:19 +0100
To: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.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: 0fa76816851382eb71b0a882ccdc29ac
Content-Transfer-Encoding: 7bit
Cc: "West, Mark" <mark.a.west@roke.co.uk>,
        "Surtees,
	Abigail" <abigail.surtees@roke.co.uk>,
        Carsten Bormann <cabo@tzi.org>, rohc@ietf.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.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Content-Transfer-Encoding: 7bit


On Dec 09 2004, at 13:57 Uhr, Lars-Erik Jonsson (LU/EAB) wrote:

> Folks,
>
>>> So in the IP-ID case the non-encoded field grows with SN and in the
>>> Timestamp case the encoded field grows with SN.
>>
>> That's my conclusion, which I would put slightly differently:
>> With IP-ID, if it is not encoded in the header, it grows in
>> parallel SN.
>> With TS, if it is not encoded in the header, it grows in
>> parallel with TS_STRIDE*SN (independent of Tsc!).
>
> Which could also be expressed as:
> With TS, if it is not encoded in the header, its scaled
> representation grows in parallel with TS_STRIDE.

s/scaled/unscaled/

(The scaled representation grows in parallel with SN.)


> TS can thus be communicated in three ways:
> 1) Unscaled

...and sent with WLSB

> 2) SCALED and sent with WLSB
> 3) SCALED, inferred from SN

Yes.

> It seems like 1) and 2) are "clear" from 3095, while what is really
> missing is a defined decompression (and thus compression)
> logic for 3).

Well, at least 3095 says that Tsc is 1 in the context, so SCALED is the 
more likely interpretation, I'd say.

> The "default slope" value would be an important
> part of that logic, and I guess most implementers have actually
> used that value for the simple function
> TS_SCALED=(SN-SN_OLD)*default_slope + TS_SCALED(SN_OLD)
> for decompression of TS_SCALED when no TS bits are sent.
>
> Q: Would default_slope be used when decompressing based
>    on TS bits actually sent?

No.  4.5.3 is quite clear on what to do.

> Q: Can default_slope be anything but 1?

(If Tsc is 1:) No.  See 5.7.

> Q: Can TS bits ever be omitted when sent unscaled?

Yes, with an ext3 if Tsc is 0, R-TS is 0, and no TS bits are in the 
base (i.e., UOR-2-ID) header carrying the ext3.

> I think the answers to all these questions are all NO!
> Therefore, I do not think default_slope would ever (when used)
> be equal to TS_STRIDE, as stated on page 75.

See the unlikely, but possible case above.
But the logic is clear: Look at Tsc, if it is 0, the default-slope is 
TS-STRIDE, if it is 1, the default-slope is 1.

> I think there is nothing missing when it comes to IP-ID and slopes,
> more than to clarify the meaning of default_slope on page 75, which
> simply means exactly what is said on the second and third line of
> page 35 (the additional mentioning on page 75 is thus just confusing).

Yes.

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Thu Dec  9 09:37:21 2004
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 JAA25448
	for <rohc-web-archive@ietf.org>; Thu, 9 Dec 2004 09:37:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcPX2-0006JM-Co
	for rohc-web-archive@ietf.org; Thu, 09 Dec 2004 09:44:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcPOI-0002qB-4x; Thu, 09 Dec 2004 09:35:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcPAy-0001MI-9Q
	for rohc@megatron.ietf.org; Thu, 09 Dec 2004 09:21:48 -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 JAA24139
	for <rohc@ietf.org>; Thu, 9 Dec 2004 09:21:47 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcPHx-00060L-Qs
	for rohc@ietf.org; Thu, 09 Dec 2004 09:29:02 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <YHL6R9YH>; Thu, 9 Dec 2004 14:23:01 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8803D5AAA@rsys004a.roke.co.uk>
From: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
To: "'Carsten Bormann'" <cabo@tzi.org>
Subject: RE: [rohc] The discussion on slope(s) (redux)
Date: Thu, 9 Dec 2004 14:22:57 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48
Cc: "West, Mark" <mark.a.west@roke.co.uk>, rohc@ietf.org,
        "'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: 156eddb66af16eef49a76ae923b15b92

Hi again,
> 
> >> The issue we have, I think, is that 3095 is not very explicit about
> >> what we do when we *don't* send a field.
> >
> > I think that 3095 is not very explicit about *whether/when* 
> we don't 
> > send a
> > field, as well as what we do when we don't send it.
> 
> Well, that rule is simple: You can only "not send" if the 
> decompressor 
> will regenerate the right header!
> So the rule is implicitly created from the rule that says what the 
> decompressor will do if a field is not encoded in the header.

Agreed, but as far as I can see, the RFC doesn't say what the decompressor
will do if a field is not encoded in the header.  In particular, 4.5.3 only
states the translation from TS_SCALED back to full TS.  It makes no mention
of what to do if no bits are received.  

> The problem is that a lot of other places also just say "TS" 
> and really 
> mean "the thing that you get out of section 4.5 to encode TS".

OK, fair enough.
> 
> >> Both mean the same: the default value for a non-encoded field is
> >> growing with the SN, both IP-ID slope and TS-scaled slope are
> >> set to 1.
> >
> > I'm a bit confused here.  In the IP-ID case we have:
> >
> > Non-encoded field = IP-ID
> > Encoded field = IP-ID-offset
> > Default slope of encoded field stated = 0 (as stated in 5.7)
> > Implies slope of non-encoded field = 1
> 
> Yes.
> 
> > In the Timestamp case we have:
> >
> > Non-encoded field = TS
> > Encoded field = TS_SCALED
> > Default slope of encoded field stated = 1 (assuming TS in 5.7 is 
> > TS_SCALED)
> > Which says nothing about the non-encoded field.
> 
> No.  Neither did I, above?

OK, we are probably using different definitions here.  I assumed that by
encoded field you meant the field for which bits are sent.  By non-encoded
field I assumed you meant the original field from the uncompressed header,
that can be inferred from the bits sent.  So for the IP-ID and timestamp
cases I assumed you meant:

> > Non-encoded field = IP-ID
> > Encoded field = IP-ID-offset

> > Non-encoded field = TS
> > Encoded field = TS_SCALED

So in your sentence:
> >> Both mean the same: the default value for a non-encoded field is
> >> growing with the SN, both IP-ID slope and TS-scaled slope are
> >> set to 1.

I agree that both IP-ID slope and TS-scaled slope are set to 1, but they are
not both non-encoded fields (which is the implication of the first half of
your sentence).

I think this may be a language interpretation issue rather than a technical
one ;-)
> 
> > So in the IP-ID case the non-encoded field grows with SN and in the
> > Timestamp case the encoded field grows with SN.
> 
> That's my conclusion, which I would put slightly differently:
> With IP-ID, if it is not encoded in the header, it grows in 
> parallel SN.
> With TS, if it is not encoded in the header, it grows in 
> parallel with 
> TS_STRIDE*SN (independent of Tsc!).
> 
I agree with these statements and Lars-Erik's interpretation of these into
what implementer's have actually done - if this statement holds true, no
bits are needed:
TS_SCALED=(SN-SN_OLD)*default_slope + TS_SCALED(SN_OLD)

> > When doing our implementation, and in a (possibly vain) attempt to 
> > harmonise
> > the handling of TS/IP_ID, we *conceptually* treat it as:
> >
> > 'Non-encoded' field = TS_SCALED
> > 'Encoded' field = TS_SC_OFFSET
> > Assumed default slope of encoded field = 0
> > Implies slope of non-encoded field = 1
> > *BUT* when bits are required for 'encoded' field, actually 
> *send* bits 
> > of
> > 'non-encoded' field (and hope that the other end will interpret it
> > correctly..!)
> 
> You lost me.
> Maybe "non-encoded" and "encoded" mean something different 
> here than in 
> my mind...
> 
Does the definition of non-encoded and encoded above help?

We used this as an internal mechanism to decide when to send bits of
TS_SCALED in the same way as we do for IP_ID.  (As you say, determining
whether or not the decompressor will be able to correctly decompress the
packet.)

Two further points are:

It appears that IP_ID offset bits are sent in order to minimise the number
of bits required when there is jitter.  As TS_SCALED is the only other
(non-SN) field that uses LSB, we (optimistically) assumed it would/tried to
make it work in the same way.

By sending bits of offset for IP_ID, you explicitly transmit the offset
value (some/no bits) and then use the slope equation (non_SN_field = slope *
SN + offset) to get back to the IP_ID.
However, in the timestamp case, you can use the slope equation when no bits
are sent, but if bits are sent, the slope is ignored.  The bits that are
sent allow you to directly re-create TS_SCALED without any reference to
slope.

> >> In summary, I believe the text of 3095 supports your proposal 1.
> >
> > I'm not sure which you're referring to as proposal 1?
> 
> The first one of:
> 
> >>> Therefore, with respect to the implementers' guide, our 
> proposal is 
> >>> that
> >>> it should either:
> >>>
> >>> - indicate that the concept of slope exists; but that there is no 
> >>> way to
> >>> change the 'default' slope and that the slope for both IP-ID and 
> >>> TS_SCALED
> >>> is 1; or
> >>>
> >>> - that the concept of slope is ill-defined and should not 
> be used, 
> >>> at all.
> 
> I would maybe word it slightly differently, as the text 
> explicitly says 
> that "default-slope(IP-ID offset) = 0", which of course *is* 
> equivalent 
> to "default-slope(IP-ID) = 1".
> 
OK, that's fine by us :-)

Best regards, 

Abbie

> Gruesse, Carsten
> 

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


From rohc-bounces@ietf.org  Thu Dec  9 09:42:11 2004
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 JAA25820
	for <rohc-web-archive@ietf.org>; Thu, 9 Dec 2004 09:42:11 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcPbX-0006PZ-6n
	for rohc-web-archive@ietf.org; Thu, 09 Dec 2004 09:49:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcPOO-0002wd-FB; Thu, 09 Dec 2004 09:35:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcPFu-0001Xr-G8
	for rohc@megatron.ietf.org; Thu, 09 Dec 2004 09:26:54 -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 JAA24566
	for <rohc@ietf.org>; Thu, 9 Dec 2004 09:26:53 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcPMj-00065Z-P9
	for rohc@ietf.org; Thu, 09 Dec 2004 09:34:08 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iB9EQeO6027478 for <rohc@ietf.org>; Thu, 9 Dec 2004 15:26:40 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 9 Dec 2004 15:26:40 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <XVCWW1B8>; Thu, 9 Dec 2004 15:26:39 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E9A0B@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'Carsten Bormann'" <cabo@tzi.org>
Subject: RE: [rohc] The discussion on slope(s) (redux)
Date: Thu, 9 Dec 2004 15:26:31 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 09 Dec 2004 14:26:40.0335 (UTC)
	FILETIME=[193FADF0:01C4DDFB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: "West, Mark" <mark.a.west@roke.co.uk>,
        "Surtees,
	Abigail" <abigail.surtees@roke.co.uk>, rohc@ietf.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.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8

> > It seems like 1) and 2) are "clear" from 3095, while what is really
> > missing is a defined decompression (and thus compression)
> > logic for 3).
> 
> Well, at least 3095 says that Tsc is 1 in the context, so 
> SCALED is the more likely interpretation, I'd say.

Yes, to make the default_slope=1 wording on page 75 correct,
that should be the interpretation.

 
> > The "default slope" value would be an important
> > part of that logic, and I guess most implementers have actually
> > used that value for the simple function
> > TS_SCALED=(SN-SN_OLD)*default_slope + TS_SCALED(SN_OLD)
> > for decompression of TS_SCALED when no TS bits are sent.
> >
> > Q: Would default_slope be used when decompressing based
> >    on TS bits actually sent?
> 
> No.  4.5.3 is quite clear on what to do.

Clear to the extent that it does not define the use of slope,
but 4.5.3 does not really care if bits are sent or not, that
is part of the compression step, after scaling. That 4.5.3
does not say anything does not make 3095 clear on that point.
However, I just wanted to ensure we agree the whole
slope/default_slope thing is only about "inferred decompression".


> > Q: Can default_slope be anything but 1?
> 
> (If Tsc is 1:) No.  See 5.7.
> 
> > Q: Can TS bits ever be omitted when sent unscaled?
> 
> Yes, with an ext3 if Tsc is 0, R-TS is 0, and no TS bits are in the 
> base (i.e., UOR-2-ID) header carrying the ext3.

True, you're right there is a case. This means we will have to
define "inferred decompression" both for scaled and unscaled TS.


> But the logic is clear: Look at Tsc, if it is 0, the default-slope is 
> TS-STRIDE, if it is 1, the default-slope is 1.

Yes, the "only" thing that is missing is an explanation of what 
default-slope is and how to use it for "inferred decompression".
A rather important tiny detail. Also "default slope" can be a
confusing name, as there is no way to ever change it.

/L-E

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


From rohc-bounces@ietf.org  Thu Dec  9 10:19:44 2004
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 KAA29502
	for <rohc-web-archive@ietf.org>; Thu, 9 Dec 2004 10:19:44 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcQC4-0007Gz-Eb
	for rohc-web-archive@ietf.org; Thu, 09 Dec 2004 10:27:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcQ48-0007s5-Qn; Thu, 09 Dec 2004 10:18:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcPsA-0002zO-IN
	for rohc@megatron.ietf.org; Thu, 09 Dec 2004 10:06:28 -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 KAA27647
	for <rohc@ietf.org>; Thu, 9 Dec 2004 10:06:24 -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 1CcPz9-0006u9-5s
	for rohc@ietf.org; Thu, 09 Dec 2004 10:13:40 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iB9F6EX8007707; Thu, 9 Dec 2004 16:06:16 +0100 (MET)
In-Reply-To: <A943FD84BD9ED41193460008C7918050072E9A0B@ESEALNT419.al.sw.ericsson.se>
References: <A943FD84BD9ED41193460008C7918050072E9A0B@ESEALNT419.al.sw.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <DEE41666-49F3-11D9-B3CF-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] The discussion on slope(s) (redux)
Date: Thu, 9 Dec 2004 16:06:14 +0100
To: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.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: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit
Cc: "West, Mark" <mark.a.west@roke.co.uk>,
        "Surtees,
	Abigail" <abigail.surtees@roke.co.uk>,
        Carsten Bormann <cabo@tzi.org>, rohc@ietf.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.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit

> Yes, the "only" thing that is missing is an explanation of what
> default-slope is and how to use it for "inferred decompression".
> A rather important tiny detail.

Yes.

> Also "default slope" can be a
> confusing name, as there is no way to ever change it.

Well, it's the slope you use to "default" TS in case it's not present 
in the header.

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Thu Dec  9 17:57:32 2004
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 RAA24613
	for <rohc-web-archive@ietf.org>; Thu, 9 Dec 2004 17:57:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcXLB-0004zX-40
	for rohc-web-archive@ietf.org; Thu, 09 Dec 2004 18:04:53 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcXB3-0008SJ-Li; Thu, 09 Dec 2004 17:54:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcX6q-0007HV-NX
	for rohc@megatron.ietf.org; Thu, 09 Dec 2004 17:50:06 -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 RAA24251
	for <rohc@ietf.org>; Thu, 9 Dec 2004 17:50:01 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from mgw-x2.nokia.com ([131.228.20.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcXDs-0004qR-K8
	for rohc@ietf.org; Thu, 09 Dec 2004 17:57:22 -0500
Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158])
	by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iB9MnkF29799; Fri, 10 Dec 2004 00:49:47 +0200 (EET)
X-Scanned: Fri, 10 Dec 2004 00:47:24 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id iB9MlOZe019916;
	Fri, 10 Dec 2004 00:47:24 +0200
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks003.ntc.nokia.com 00MciZVh; Fri, 10 Dec 2004 00:47:23 EET
Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com
	[10.241.35.122])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iB9MlLS26756; Fri, 10 Dec 2004 00:47:21 +0200 (EET)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by
	daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Thu, 9 Dec 2004 16:46:50 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] The discussion on slope(s)
Date: Thu, 9 Dec 2004 17:46:48 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B81D0C2D@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] The discussion on slope(s)
Thread-Index: AcTdwl1iiIKqmTuzSPSh9/6ThEpbSwASIa+w
To: <cabo@tzi.org>
X-OriginalArrivalTime: 09 Dec 2004 22:46:50.0277 (UTC)
	FILETIME=[F8916D50:01C4DE40]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: quoted-printable
Cc: rohc@ietf.org, kristofer.sandlund@effnet.com,
        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.3 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: quoted-printable

> But it won't use any "slope" component of X as a reference=20
> unless it is a R-0-CRC.

Right, but it will use the {SN, TS} in X as reference, which
is also used to calculate the slope. So, if {SN, TS} has
an undetected error (the reason of incorrect slope), the error
will be detected with high probability this time and triggers=20
a context resynchorinzation, including the slope value.

Probably this will be clearer below.

> The part I'm not sure about is why Kristofer thinks these wouldn't=20
> update the dynamic slope, too.
> (I don't think anyone has proposed a detailed algorithm for when/how=20
> exactly dynamic slopes would be updated, yet.)

I think I more or less explained the algorithm in previous emails.
http://www1.ietf.org/mail-archive/web/rohc/old-archive/msg00934.html
http://www1.ietf.org/mail-archive/web/rohc/current/msg03054.html
But let me try again, because it's critical for the discussion.=20

For simplicity, I'll use TS as example below, but the same can=20
be applied to IP-ID and other header fields. Furthermore, I'll
assume TS is unscaled, i.e. TS =3D TS_SCALED.

- Initialization. For TS and IP-ID, default-slopes are specified
in section 5.7 of 3095.=20

- When to update slope(TS)?=20

The compressor will update slope(TS) if the cur_slope(TS)=20
!=3D prev_slope(TS), where cur_slope(TS) and prev_slope(TS) are
the slope(TS) of current and previous string, respectively.=20

Note: for the first string for a context, prev_slope(TS) =3D =
default-slope(TS).

Note: if cur_slope(TS) =3D=3D prev_slope(TS), the compressor does not
have to update slope(TS) during current string. But it may do so=20
if it is not confident about prev_slope(TS).

- How to update slope(TS)?=20

The compressor must be sure that the decompressor has at least
received and correctly decompressed two update packets that
a) belong to current string, AND=20
b) both of them carry TS field.=20

As usual, the confidence of the compressor depends on mode. For=20
UO-mode, it's the repetition (i.e. L). For R-mode, it's the ACKs.

The decompressor calculates cur_slope(TS) as follows:

    cur_slope(TS) =3D (TS2 - TS1) / (SN2 - SN1)

where {SN1, TS1} and {SN2, TS2} are the decompressed SN and TS values
of the last two update packets it has received and ACKed.

For example and more details, see bottom part of msg03054.

BR,
Zhigang

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


From rohc-bounces@ietf.org  Thu Dec  9 19:24:22 2004
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 TAA02294
	for <rohc-web-archive@ietf.org>; Thu, 9 Dec 2004 19:24:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcYhE-0006lf-Pp
	for rohc-web-archive@ietf.org; Thu, 09 Dec 2004 19:31:45 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcYYy-0003lv-TS; Thu, 09 Dec 2004 19:23:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcYWs-00033o-OJ
	for rohc@megatron.ietf.org; Thu, 09 Dec 2004 19:21:02 -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 TAA01947
	for <rohc@ietf.org>; Thu, 9 Dec 2004 19:20:59 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcYdx-0006gu-HQ
	for rohc@ietf.org; Thu, 09 Dec 2004 19:28:22 -0500
Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iBA0Kwj10010; Fri, 10 Dec 2004 02:20:59 +0200 (EET)
X-Scanned: Fri, 10 Dec 2004 02:20:40 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id iBA0Keqt025039;
	Fri, 10 Dec 2004 02:20:40 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks003.ntc.nokia.com 00MmZgD1; Fri, 10 Dec 2004 02:20:38 EET
Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com
	[10.241.35.122])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iBA0KWa06094; Fri, 10 Dec 2004 02:20:33 +0200 (EET)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by
	daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Thu, 9 Dec 2004 18:20:30 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] The discussion on slope(s) (redux)
Date: Thu, 9 Dec 2004 19:20:28 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B82891D5@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] The discussion on slope(s) (redux)
Thread-Index: AcTdlHvrPs7gEsPxTmu6XrxtoJDnXgAriOSw
To: <mark.a.west@roke.co.uk>, <rohc@ietf.org>
X-OriginalArrivalTime: 10 Dec 2004 00:20:30.0389 (UTC)
	FILETIME=[0E6A7650:01C4DE4E]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Content-Transfer-Encoding: quoted-printable
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: 34d35111647d654d033d58d318c0d21a
Content-Transfer-Encoding: quoted-printable

Mark,

Long email, long reply ... :-)=20

BR, Zhigang

> In particular, we agree that the concept of implicit slope=20
> has potential synchronisation problems;=20

This is still being discussed. I have to be honest: there might=20
be, but I'm not sure yet. Either way, I don't think it's a=20
problem serious enough to kill implicit slope.

> and we don't believe has been actually
> implemented / tested.

Yes, it has been implemented in Nokia code. And it survived
our stress tests: injected bit corruption, packet loss, and=20
even limited mis-ordering.

> However, we do think that the concept of slope is useful for=20
> compressing
> timestamp efficiently (particularly in the case of video). =20
> It could also,
> perhaps, have been used to solve the linux-zero-ip-id-problem..!

Yes, I still remember Mikael and I touched the slope issue when
discussing zero ip-id long time ago. Unfortunately, it was
turned down, partially due to a "bug" in 3095 text (don't remember
which one).

For me, it's hard to understand what SO state is without thinking
of slope.
=20
> IP-ID is a non SN field so according to 5.1.2.2 it should=20
> follow the rule:
>=20
>   non-SN-field =3D SN * slope + offset           [1]
>=20
> Fine.  But section 4.5.5 states that for the IP-ID the offset=20
> should be
> compressed with LSB encoding and the offset is given by:
>=20
>   Offset_i =3D ID_i - SN_i,                      [2]

You just hit the heart of the confusion! Three clarifications
(at least what I had in mind when writing those sections):

1) equation [1] and the concept of slope is for SO state, not FO state.
2) section 4.5.5 is about sending FO information, not SO.
3) non-SN-field does not has to be a header field. It can be
a header field after transformation, in particular, Offset_i=20
and TS_SCALED. This can be evident in section 5.7 as you raised.

> Another question is: what is the expected behaviour in the=20
> case where the source IP stack is sending two flows which=20
> happen to be alternating packets?  This may lead to the=20
> IP-ID for each flow incrementing in regular steps of 2. =20
> From what's in the rfc and what we *assume* folks have
> implemented, we believe that LSBs of IP-ID-offset would be=20
> sent in every packet and you'd never reach SO state. Any comments..?

With slope, you can enter SO state. I believe this has been=20
discussed when drafting 3095. Oh well, so many things have=20
been discussed but ...

SN                       1    2    3    4    5  ...
IP-ID                  101  103  105  107  109  ...
IP_ID Offset           100  101  102  103  104  ...
slope(IP-ID Offset)    N/A    1    1    1    1  ...
offset(IP-ID Offset)   N/A   99   99   99   99  ...
Compressor sends       CUP  CUP   -0   -0   -0  ...

Notes:
- CUP =3D Context Update Packet
- assume "immdieate ACKs"
=20
> But, OK, let's consider timestamp.  Again it is a=20
> non-SN-field so it can be expressed using equation [1].=20
> However, 4.5.3 also defines scaling using the equation:
>=20
>   TS =3D TS_SCALED * TS_STRIDE + TS_OFFSET		[3]

Again, there are two steps as my text in 4.5.3 intended to say
1) Scale step: transform TS to TS_SCALED before compression.
This is what [3] about.
2) Compression step: compress TS_SCALED just as if it's a
"normal" TS. Here, the SO state comes as in [1]. And W-LSB
encoding for FO state.


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


From rohc-bounces@ietf.org  Fri Dec 10 01:57:34 2004
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 BAA00790
	for <rohc-web-archive@ietf.org>; Fri, 10 Dec 2004 01:57:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ccepm-0005UM-6r
	for rohc-web-archive@ietf.org; Fri, 10 Dec 2004 02:04:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcefF-0008FS-82; Fri, 10 Dec 2004 01:54:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CceKT-0001uA-P9
	for rohc@megatron.ietf.org; Fri, 10 Dec 2004 01:32:38 -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 BAA29286
	for <rohc@ietf.org>; Fri, 10 Dec 2004 01:32:31 -0500 (EST)
Received: from bay2-f2.bay2.hotmail.com ([65.54.247.2] helo=hotmail.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CceRW-00053E-Iw
	for rohc@ietf.org; Fri, 10 Dec 2004 01:39:55 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Thu, 9 Dec 2004 22:32:00 -0800
Message-ID: <BAY2-F2D7FDAF04016FD97F8DBAA9A80@phx.gbl>
Received: from 61.11.58.162 by by2fd.bay2.hotmail.msn.com with HTTP;
	Fri, 10 Dec 2004 06:31:25 GMT
X-Originating-IP: [61.11.58.162]
X-Originating-Email: [basudeb@hotmail.com]
X-Sender: basudeb@hotmail.com
In-Reply-To: <3F2E01E1D7B04F4EBEC92D3FA324D8803D5AAA@rsys004a.roke.co.uk>
From: "Basudeb Gupta" <basudeb@hotmail.com>
To: abigail.surtees@roke.co.uk, cabo@tzi.org
Date: Fri, 10 Dec 2004 12:01:25 +0530
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
X-OriginalArrivalTime: 10 Dec 2004 06:32:00.0500 (UTC)
	FILETIME=[F45B7B40:01C4DE81]
X-Spam-Score: 2.0 (++)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id BAA29286
Cc: mark.a.west@roke.co.uk, rohc@ietf.org, lars-erik.jonsson@ericsson.com
Subject: [rohc] SOS from a newbie in sigcomp
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: 2.0 (++)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
Content-Transfer-Encoding: quoted-printable

Hello Mr. Abigal,

We are designing a UDVM ( delivery date 11th December) and are stuck in t=
he=20
COPY-OFFSET torture test for last 2 weeks now. Everything else is passing=
=20
except this.

We need your help in a few matters in the torture text document and the=20
definition of COPY-OFFSET urgently. Will  appreciate greatly if I can get=
 it=20
as early as possible.

I am writing below each step in the torture test. Please help me correct =
our=20
implementation and understanding of the 3320 RFC.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Torture t=
est steps and our results =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
3.7.  COPY-LITERAL and COPY-OFFSET

   This section gives assembly code to test the COPY-LITERAL and COPY-
   OFFSET instructions. The code is designed to test similar boundary
   cases to the code for the COPY instruction, as well as the following
   condition specific to COPY-LITERAL and COPY-OFFSET:

   1. The COPY-LITERAL or COPY-OFFSET instruction overwrites the value
   of its destination or offset operand.

   at (64)

   :byte_copy_left                  pad (2)
   :byte_copy_right                 pad (2)
   :destination                     pad (2)
   :offset                          pad (2)

   at (128)

   LOAD (32, 16384)
   LOAD (byte_copy_left, 64)
   LOAD (byte_copy_right, 128)
   LOAD (destination, 33)


UDVM MEMORY DUMP (Start + 32)
>>
0x0043FD70 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

0x0043FD80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

0x0043FD90 00 40 00 80 00 21 00 00 00 00 00 00 00 00 00 00

0x0043FDA0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00



   COPY-LITERAL (32, 128, $destination)
   COPY-LITERAL (68, 8, $destination)

>>MEMORY DUMP (Start + 32)

0x0043FD70 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40

0x0043FD80 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40

0x0043FD90 40 40 40 40 00 69 40 40 40 40 40 40 40 40 40 40

0x0043FDA0 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40

0x0043FDB0 40 00 61 40 40 40 40 40 40 40 40 40 40 40 40 40

0x0043FDC0 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40


   LOAD (byte_copy_left, 66)
   LOAD (byte_copy_right, 74)

>>Memory Dump (Start + 32)
0x0043FD70 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40

0x0043FD80 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40

0x0043FD90 00 42 00 4a 00 69 40 40 40 40 40 40 40 40 40 40

0x0043FDA0 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40

0x0043FDB0 40 00 61 40 40 40 40 40 40 40 40 40 40 40 40 40

0x0043FDC0 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40



   COPY-OFFSET (8, 6, $destination)

>>UDVM Memory Dump: (Start + 32)

0x0043FD70 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40

0x0043FD80 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40

0x0043FD90 00 42 00 4a 00 6f 40 40 40 40 40 40 40 40 40 40

0x0043FDA0 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40

0x0043FDB0 40 00 61 40 40 40 40 40 40 00 61 40 40 40 40 40

0x0043FDC0 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40



   LOAD ($offset, 1)

   COPY-OFFSET ($offset, 5 ,$destination)

>>UDVM Memory Dump: (Start + 32)

0x0043FD70 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40

0x0043FD80 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40

0x0043FD90 00 42 00 4a 00 74 40 40 40 40 40 40 40 40 40 40

0x0043FDA0 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40

0x0043FDB0 40 00 61 40 40 40 40 40 40 00 61 40 40 40 40 40

0x0043FDC0 40 40 00 4a 40 40 40 40 40 40 40 40 40 40 40 40



   OUTPUT (32, 48)

   END-MESSAGE (0, 0, 0, 0, 0, 0, 0)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
   The expected output of the code is 32 instances of 0x40 followed by
   0x0042 004a 0074 4040 4040 004a 0074 4040. The expected cost of
   executing the code is 208 UDVM cycles.

Please help!!! And only you can help me here.

Thanks and Regards,
Basudeb

_________________________________________________________________
Microsoft=92s festive bonanza! Buy a branded Home PC.=20
http://server1.msn.co.in/sp04/festivebonanza/ Win a fabulous holiday!


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


From rohc-bounces@ietf.org  Fri Dec 10 03:31:16 2004
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 DAA22559
	for <rohc-web-archive@ietf.org>; Fri, 10 Dec 2004 03:31:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcgIS-0007Kq-N7
	for rohc-web-archive@ietf.org; Fri, 10 Dec 2004 03:38:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ccg8e-0002sk-JJ; Fri, 10 Dec 2004 03:28:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcVp5-0006T4-Ob
	for rohc@megatron.ietf.org; Thu, 09 Dec 2004 16:27:39 -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 QAA08019
	for <rohc@ietf.org>; Thu, 9 Dec 2004 16:27:37 -0500 (EST)
Received: from wproxy.gmail.com ([64.233.184.192])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcVw6-0008Gi-U7
	for rohc@ietf.org; Thu, 09 Dec 2004 16:34:56 -0500
Received: by wproxy.gmail.com with SMTP id 71so20794wri
	for <rohc@ietf.org>; Thu, 09 Dec 2004 13:27:01 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding;
	b=rBFIhMzK1xvRcuVmU6ZqgouBLSIRKLasHXlixXNb75cd1TzDw5pKRZKL+6JPW8uMkqZfVrw56p0h6JhhFJqDIyPPouiVgzdyMTDfN/r2lGielsmAGClZsME3rBQKIFY1J08HadTPfc/QdygCu/JBkyDO4qOrunqfDj5Hjrq7UP8=
Received: by 10.54.36.36 with SMTP id j36mr1498685wrj;
	Thu, 09 Dec 2004 13:27:01 -0800 (PST)
Received: by 10.54.32.40 with HTTP; Thu, 9 Dec 2004 13:27:01 -0800 (PST)
Message-ID: <40d587af04120913275d78e04a@mail.gmail.com>
Date: Thu, 9 Dec 2004 17:27:01 -0400
From: =?ISO-8859-1?Q?Eli=E9zer_Moura?= <eliezermoura@gmail.com>
To: rohc@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Fri, 10 Dec 2004 03:28:28 -0500
Subject: [rohc] ROHC
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: =?ISO-8859-1?Q?Eli=E9zer_Moura?= <eliezermoura@gmail.com>
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: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: quoted-printable

I'm a student of the Amazon Federal University (UFAM) and I'm
researching the ROHC. I would like to know in how many milliseconds the ROH=
C
compresses a RTP/UDP/IP header and in how many milliseconds it
decompresses this header.

Regard
Eli=E9zer Moura

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


From rohc-bounces@ietf.org  Fri Dec 10 03:55:50 2004
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 DAA24675
	for <rohc-web-archive@ietf.org>; Fri, 10 Dec 2004 03:55:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ccgg5-00080s-7X
	for rohc-web-archive@ietf.org; Fri, 10 Dec 2004 04:03:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcgVE-00081o-Tc; Fri, 10 Dec 2004 03:51:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcgQm-0007BA-BQ
	for rohc@megatron.ietf.org; Fri, 10 Dec 2004 03:47:16 -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 DAA24130
	for <rohc@ietf.org>; Fri, 10 Dec 2004 03:47:14 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcgXv-0007jR-QQ
	for rohc@ietf.org; Fri, 10 Dec 2004 03:54:40 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBA8lEh5023869
	for <rohc@ietf.org>; Fri, 10 Dec 2004 09:47:14 +0100 (MET)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 10 Dec 2004 09:47:14 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <XVCW5RPH>; Fri, 10 Dec 2004 09:47:14 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E9A14@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'zhigang.c.liu@nokia.com'" <zhigang.c.liu@nokia.com>,
        mark.a.west@roke.co.uk, rohc@ietf.org
Subject: RE: [rohc] The discussion on slope(s) (redux)
Date: Fri, 10 Dec 2004 09:47:12 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 10 Dec 2004 08:47:14.0142 (UTC)
	FILETIME=[D876FFE0:01C4DE94]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
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: 538aad3a3c4f01d8b6a6477ca4248793

> > IP-ID is a non SN field so according to 5.1.2.2 it should 
> > follow the rule:
> > 
> >   non-SN-field = SN * slope + offset           [1]
> > 
> > Fine.  But section 4.5.5 states that for the IP-ID the offset 
> > should be
> > compressed with LSB encoding and the offset is given by:
> > 
> >   Offset_i = ID_i - SN_i,                      [2]
> 
> You just hit the heart of the confusion! Three clarifications
> (at least what I had in mind when writing those sections):
> 
> 1) equation [1] and the concept of slope is for SO state, not 
> FO state.
> 2) section 4.5.5 is about sending FO information, not SO.

This is not true, 4.5.5 actually specifies exactly how to 
compress IP-ID, nothing is really missing to implement it.

4.5.5 explains what to do both with and without bits in the
compressed header, specifically note the following line:
"Note that m may contain zero LSBs for Offset_m, in which case
Offset_m = Offset_ref."

The only possible interpretation of "default-slope(IP-ID offset)"
would be to see it in light of what section 4.5.5 says, and it
actually fits well together as a slope of 0 means the same
as Offset_m=Offset_ref.

However, there is no way to find anything that indicates this
0-slope would ever change, that would also go against what is
actually specified in 4.5.5.


> > Another question is: what is the expected behaviour in the 
> > case where the source IP stack is sending two flows which 
> > happen to be alternating packets?  This may lead to the 
> > IP-ID for each flow incrementing in regular steps of 2.  

This example was mentioned at some point in the 3095 development,
but it was agreed that it is a rather non-realistic scenario that
it would not make sense to build special mechanisms for.

For IP-ID (offset), there is clearly no learned slope in 3095.

/L-E

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


From rohc-bounces@ietf.org  Fri Dec 10 06:32:02 2004
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 GAA05751
	for <rohc-web-archive@ietf.org>; Fri, 10 Dec 2004 06:32:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ccj7H-0002Tk-Sm
	for rohc-web-archive@ietf.org; Fri, 10 Dec 2004 06:39:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ccisb-0004Ui-E5; Fri, 10 Dec 2004 06:24:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CciqW-0003yG-A6
	for rohc@megatron.ietf.org; Fri, 10 Dec 2004 06:22:00 -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 GAA05053
	for <rohc@ietf.org>; Fri, 10 Dec 2004 06:21:57 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcixU-0002Fp-5z
	for rohc@ietf.org; Fri, 10 Dec 2004 06:29:25 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBABLjvD014340
	for <rohc@ietf.org>; Fri, 10 Dec 2004 12:21:45 +0100 (MET)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 10 Dec 2004 12:21:44 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <XVCW6ZWD>; Fri, 10 Dec 2004 12:21:43 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E9A1A@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'Carsten Bormann'" <cabo@tzi.org>
Subject: IP-ID clarification (was: [rohc] The discussion on slope(s) (redu x))
Date: Fri, 10 Dec 2004 12:21:40 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 10 Dec 2004 11:21:44.0045 (UTC)
	FILETIME=[6DC1F1D0:01C4DEAA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: "West, Mark" <mark.a.west@roke.co.uk>,
        "Surtees,
	Abigail" <abigail.surtees@roke.co.uk>, rohc@ietf.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.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d

To capture this conclusion and avoid further confusion on IP-ID offset
encoding, I propose to add the following at the end of section 8.2 of
the implementer's guide:

   "When RND=0 but no IP-ID bits are sent in the compressed header, the
    SN offset for IP-ID stays unchanged, meaning that Offset_m equals
    Offset_ref, as described in Section 4.5.5. This is further expressed
    in a slightly different way (with the same meaning) in Section 5.7,
    where it is said that "default-slope(IP-ID offset) = 0", meaning that
    if no bits are sent for IP-ID, its SN offset slope defaults to 0."

/L-E


> > I think there is nothing missing when it comes to IP-ID and slopes,
> > more than to clarify the meaning of default_slope on page 75, which
> > simply means exactly what is said on the second and third line of
> > page 35 (the additional mentioning on page 75 is thus just 
> confusing).
> 
> Yes.
> 
> Gruesse, Carsten
 

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


From rohc-bounces@ietf.org  Fri Dec 10 06:39:00 2004
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 GAA06405
	for <rohc-web-archive@ietf.org>; Fri, 10 Dec 2004 06:39:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcjEB-0002d1-VF
	for rohc-web-archive@ietf.org; Fri, 10 Dec 2004 06:46:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ccj3B-00069X-3h; Fri, 10 Dec 2004 06:35:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ccixr-0004t1-8j
	for rohc@megatron.ietf.org; Fri, 10 Dec 2004 06:29:35 -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 GAA05518
	for <rohc@ietf.org>; Fri, 10 Dec 2004 06:29:32 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ccj4z-0002Q0-Bc
	for rohc@ietf.org; Fri, 10 Dec 2004 06:37:00 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <YHL6SKJX>; Fri, 10 Dec 2004 11:30:47 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8803D5AB9@rsys004a.roke.co.uk>
From: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
To: "'Lars-Erik Jonsson (LU/EAB)'" <lars-erik.jonsson@ericsson.com>,
        "'Carsten Bormann'" <cabo@tzi.org>
Subject: RE: IP-ID clarification (was: [rohc] The discussion on slope(s) (
	redu x))
Date: Fri, 10 Dec 2004 11:30:42 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: "West, Mark" <mark.a.west@roke.co.uk>, rohc@ietf.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.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8

Agreed.  Is it also worth explicitly stating that there is no way to change
its SN offset slope? 

(The alternating IP-ID example was an example to show that the concept slope
could be useful rather than anything else.  I.E. I agree that 'For IP-ID
(offset), there is clearly no learned slope in 3095.')

Best regards,

Abbie

> -----Original Message-----
> From: Lars-Erik Jonsson (LU/EAB) 
> [mailto:lars-erik.jonsson@ericsson.com] 
> Sent: Friday, December 10, 2004 11:22 AM
> To: 'Carsten Bormann'
> Cc: West, Mark; Surtees, Abigail; rohc@ietf.org
> Subject: IP-ID clarification (was: [rohc] The discussion on 
> slope(s) (redu x))
> 
> 
> To capture this conclusion and avoid further confusion on IP-ID offset
> encoding, I propose to add the following at the end of section 8.2 of
> the implementer's guide:
> 
>    "When RND=0 but no IP-ID bits are sent in the compressed 
> header, the
>     SN offset for IP-ID stays unchanged, meaning that Offset_m equals
>     Offset_ref, as described in Section 4.5.5. This is 
> further expressed
>     in a slightly different way (with the same meaning) in 
> Section 5.7,
>     where it is said that "default-slope(IP-ID offset) = 0", 
> meaning that
>     if no bits are sent for IP-ID, its SN offset slope defaults to 0."
> 
> /L-E
> 
> 
> > > I think there is nothing missing when it comes to IP-ID 
> and slopes,
> > > more than to clarify the meaning of default_slope on page 
> 75, which
> > > simply means exactly what is said on the second and third line of
> > > page 35 (the additional mentioning on page 75 is thus just 
> > confusing).
> > 
> > Yes.
> > 
> > Gruesse, Carsten
>  
> 

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


From rohc-bounces@ietf.org  Fri Dec 10 07:25:37 2004
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 HAA09245
	for <rohc-web-archive@ietf.org>; Fri, 10 Dec 2004 07:25:37 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcjxG-0003UU-UR
	for rohc-web-archive@ietf.org; Fri, 10 Dec 2004 07:33:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ccjkp-0005Ed-RV; Fri, 10 Dec 2004 07:20:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ccjb7-0003k5-Gz
	for rohc@megatron.ietf.org; Fri, 10 Dec 2004 07:10:09 -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 HAA08480
	for <rohc@ietf.org>; Fri, 10 Dec 2004 07:10:06 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcjiH-0003FG-O8
	for rohc@ietf.org; Fri, 10 Dec 2004 07:17:35 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBACA6h5015472
	for <rohc@ietf.org>; Fri, 10 Dec 2004 13:10:06 +0100 (MET)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 10 Dec 2004 13:10:06 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <XVCW7HPJ>; Fri, 10 Dec 2004 13:10:06 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E9A1C@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'Surtees, Abigail'" <abigail.surtees@roke.co.uk>,
        "'Carsten Bormann'"
	<cabo@tzi.org>
Subject: RE: IP-ID clarification (was: [rohc] The discussion on slope(s) (
	redu x))
Date: Fri, 10 Dec 2004 13:10:03 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 10 Dec 2004 12:10:06.0728 (UTC)
	FILETIME=[2FE43880:01C4DEB1]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: "West, Mark" <mark.a.west@roke.co.uk>, rohc@ietf.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.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25

> Agreed.  Is it also worth explicitly stating that there is no 
> way to change its SN offset slope?

Since there is nothing in 3095 that in any way says anything
that could be interpreted as if the offset slope could be
changed, I thought that explicitly stating it can not be 
changed would not be needed. Spelling out what is already in
3095, i.e. that "if no bits are sent for IP-ID, its SN offset
slope defaults to 0", should make that clear anyway, right?

/L-E

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


From rohc-bounces@ietf.org  Fri Dec 10 08:20:32 2004
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 IAA12819
	for <rohc-web-archive@ietf.org>; Fri, 10 Dec 2004 08:20:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CckoR-0004f3-Fl
	for rohc-web-archive@ietf.org; Fri, 10 Dec 2004 08:27:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CckaU-00079l-6L; Fri, 10 Dec 2004 08:13:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CckYc-0005iO-2g
	for rohc@megatron.ietf.org; Fri, 10 Dec 2004 08:11:38 -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 IAA12470
	for <rohc@ietf.org>; Fri, 10 Dec 2004 08:11:36 -0500 (EST)
Received: from rproxy.gmail.com ([64.233.170.201])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cckfm-0004WA-Se
	for rohc@ietf.org; Fri, 10 Dec 2004 08:19:04 -0500
Received: by rproxy.gmail.com with SMTP id z35so422655rne
	for <rohc@ietf.org>; Fri, 10 Dec 2004 05:11:35 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding;
	b=XVUrERYZIIJU5sH7Wj2uHC6bes3U0EkmLfFXyqAzzjRN1iEaynjMrjXwMT6QHuqCqwL6bW9tAVOtuI0fVbwqHNIkPRf5IZEdYapo5zKILUKefCUdBNmkHnFMuq5i7qrXuoNU8n4RbfTcw8E2UeCoL6/K2HfUyXGKQ9bE/sZJmdI=
Received: by 10.38.150.8 with SMTP id x8mr1753284rnd;
	Fri, 10 Dec 2004 05:11:35 -0800 (PST)
Received: by 10.38.83.41 with HTTP; Fri, 10 Dec 2004 05:11:35 -0800 (PST)
Message-ID: <1bd254fc041210051133f553e3@mail.gmail.com>
Date: Fri, 10 Dec 2004 18:41:35 +0530
From: chitrak gupta <mailfromchitrak@gmail.com>
To: rohc@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
Subject: [rohc] Failure in Copy-offset torture test.
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: chitrak gupta <mailfromchitrak@gmail.com>
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: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit

Dear All,

After trying for the last 2 weeks to pass the torture test for
copy-offset I started searching for answers when I landed upon a UDVM
implementation by Anders Broman anders.broman@ericsson.com.  I ran and
compiled the code along with the torture test bytecode. What I got
from the code is this:

40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 

40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40

00 42 00 4a 40 74 40 40 40 40 40 40 40 40 40 40

 

But the result given in the torture test is this 

The expected output of the code is 32 instances of 0x40 followed by 
0x0042 004a 0074 4040 4040 004a 0074 4040.

So can anyone please clarify if the result in the torture test
document is valid or if there is an error in my interpretation. Is
there any flaw in the source code I got?

Waiting for a response,

Thanks in advance.

Chitrak

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


From rohc-bounces@ietf.org  Fri Dec 10 09:05:32 2004
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 JAA15870
	for <rohc-web-archive@ietf.org>; Fri, 10 Dec 2004 09:05:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CclVz-0005YL-1h
	for rohc-web-archive@ietf.org; Fri, 10 Dec 2004 09:13:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CclEf-0003NX-61; Fri, 10 Dec 2004 08:55:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CckWb-0005Qn-HE
	for rohc@megatron.ietf.org; Fri, 10 Dec 2004 08:09:33 -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 IAA12404
	for <rohc@ietf.org>; Fri, 10 Dec 2004 08:09:32 -0500 (EST)
Received: from smtp107.mail.sc5.yahoo.com ([66.163.169.227])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Cckdl-0004UU-Ul
	for rohc@ietf.org; Fri, 10 Dec 2004 08:16:59 -0500
Received: from unknown (HELO chitrak) (chitrakg@61.11.58.91 with login)
	by smtp107.mail.sc5.yahoo.com with SMTP; 10 Dec 2004 13:09:29 -0000
Message-ID: <001001c4deb9$12091e40$6500a8c0@chitrak>
From: "Chitrak" <chitrakg@yahoo.com>
To: <rohc@ietf.org>
Date: Fri, 10 Dec 2004 18:36:28 +0530
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
X-Mailman-Approved-At: Fri, 10 Dec 2004 08:55:04 -0500
Subject: [rohc] Copy offset torture test failure
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>
Content-Type: multipart/mixed; boundary="===============1388489552=="
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d

This is a multi-part message in MIME format.

--===============1388489552==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000D_01C4DEE7.294BED70"

This is a multi-part message in MIME format.

------=_NextPart_000_000D_01C4DEE7.294BED70
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear All,

After trying for the last 2 weeks to pass the torture test for =
copy-offset I started searching for answers when I landed upon a UDVM =
implementation by Anders Broman anders.broman@ericsson.com.  I ran and =
compiled the code along with the torture test bytecode. What I got from =
the code is this:

40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40=20

40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40

00 42 00 4a 40 74 40 40 40 40 40 40 40 40 40 40



But the result given in the torture test is this=20

The expected output of the code is 32 instances of 0x40 followed by  =
0x0042 004a 0074 4040 4040 004a 0074 4040.

So can anyone please clarify if the result in the torture test document =
is valid or if there is an error in my interpretation. Is there any flaw =
in the source code I got?

Waiting for a response,

Thanks in advance.

Chitrak =20









 sigcomp-udvm.c

 Routines making up the Universal Decompressor Virtual Machine (UDVM) =
used for

 Signaling Compression (SigComp) dissection.

 Copyright 2004, Anders Broman anders.broman@ericsson.com

------=_NextPart_000_000D_01C4DEE7.294BED70
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><FONT color=3D#008000 size=3D2>
<P><FONT color=3D#000000>Dear All,</FONT></P>
<P><FONT color=3D#000000>After trying for the last 2 weeks to pass the =
torture=20
test for copy-offset I started searching for answers when I landed upon =
a UDVM=20
implementation by <FONT color=3D#008000>Anders Broman </FONT><A=20
href=3D"mailto:anders.broman@ericsson.com">anders.broman@ericsson.com</A>=
</FONT><FONT=20
color=3D#008000>.&nbsp; </FONT><FONT color=3D#000000>I ran and compiled =
the code=20
along with the torture test bytecode. What I got from the code is=20
this:</FONT></P><FONT size=3D2>
<P><FONT color=3D#000000>40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 =

</FONT></P>
<P><FONT color=3D#000000>40 40 40 40 40 40 40 40 40 40 40 40 40 40 40=20
40</FONT></P></FONT><FONT color=3D#000000 size=3D2>
<P>00 42 00 4a 40 74 40 40 40 40 40 40 40 40 40 40</P>
<P>&nbsp;</P>
<P>But the result given in the torture test is this </P>
<P>The expected output of the code is 32 instances of 0x40 followed =
by&nbsp;=20
0x0042 004a 0074 4040 4040 004a 0074 4040.</P>
<P>So can anyone&nbsp;please clarify if&nbsp;the&nbsp;result in the =
torture test=20
document is valid or&nbsp;if there is an error =
in&nbsp;my&nbsp;interpretation.=20
Is there any flaw in the source code I got?</P>
<P>Waiting for a response,</P>
<P>Thanks in advance.</P>
<P>Chitrak &nbsp;<FONT size=3D1></P></FONT>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P>
<P>&nbsp;</P></FONT>
<P>&nbsp;sigcomp-udvm.c</P>
<P>&nbsp;Routines making up the Universal Decompressor Virtual Machine =
(UDVM)=20
used for</P>
<P>&nbsp;Signaling Compression (SigComp) dissection.</P>
<P>&nbsp;Copyright 2004, Anders Broman <A=20
href=3D"mailto:anders.broman@ericsson.com">anders.broman@ericsson.com</A>=
</P></FONT></FONT></DIV></BODY></HTML>

------=_NextPart_000_000D_01C4DEE7.294BED70--



--===============1388489552==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1388489552==--




From rohc-bounces@ietf.org  Fri Dec 10 10:09:53 2004
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 KAA20916
	for <rohc-web-archive@ietf.org>; Fri, 10 Dec 2004 10:09:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcmW6-0006mj-RV
	for rohc-web-archive@ietf.org; Fri, 10 Dec 2004 10:17:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcmFD-0000jE-Hc; Fri, 10 Dec 2004 09:59:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ccm7o-0007RW-QS
	for rohc@megatron.ietf.org; Fri, 10 Dec 2004 09:52: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 JAA19284
	for <rohc@ietf.org>; Fri, 10 Dec 2004 09:52:03 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcmEp-0006Qh-I7
	for rohc@ietf.org; Fri, 10 Dec 2004 09:59:32 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBAEppO6021295 for <rohc@ietf.org>; Fri, 10 Dec 2004 15:51:51 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 10 Dec 2004 15:51:51 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <XVCW8HNH>; Fri, 10 Dec 2004 15:51:51 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E9A25@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Fri, 10 Dec 2004 15:51:49 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 10 Dec 2004 14:51:51.0270 (UTC)
	FILETIME=[C83FD060:01C4DEC7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: [rohc] IPR notice
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: 1ac7cc0a4cd376402b85bc1961a86ac2

Several observant WG members have asked me to make the WG aware of
the following patent application, which they think might relate to
one of the currently ongoing discussions on the ROHC list. Now I
have done so, and leave it up to interested parties to form their
own opinions on the value of it, as well as potential relations or
implications to ROHC work.

http://appft1.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=%2Fnetahtml%2FPTO%2Fsearch-bool.html&r=18&f=G&l=50&co1=AND&d=PG01&s1=khiem.IN.&s2=le.IN.&OS=IN/khiem+AND+IN/le&RS=IN/khiem+AND+IN/le


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


From rohc-bounces@ietf.org  Fri Dec 10 13:28:49 2004
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 NAA04839
	for <rohc-web-archive@ietf.org>; Fri, 10 Dec 2004 13:28:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ccpcq-0002GD-9T
	for rohc-web-archive@ietf.org; Fri, 10 Dec 2004 13:36:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcpLi-0005hu-8J; Fri, 10 Dec 2004 13:18:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcpCa-0003K7-Ab
	for rohc@megatron.ietf.org; Fri, 10 Dec 2004 13:09:12 -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 NAA03436
	for <rohc@ietf.org>; Fri, 10 Dec 2004 13:09:08 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcpJk-0001pY-WF
	for rohc@ietf.org; Fri, 10 Dec 2004 13:16:40 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <YHL6SP1N>; Fri, 10 Dec 2004 18:10:27 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D88024D421@rsys004a.roke.co.uk>
From: "West, Mark" <mark.a.west@roke.co.uk>
To: "'chitrak gupta'" <mailfromchitrak@gmail.com>, rohc@ietf.org
Subject: RE: [rohc] Failure in Copy-offset torture test.
Date: Fri, 10 Dec 2004 18:10:20 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
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: c3a18ef96977fc9bcc21a621cbf1174b


Chitrak,

There is nothing wrong with the torture test (not that it couldn't be
'improved' -- see below, but as it is, it works fine).

I haven't run Anders code from Ethereal for SigComp, but at a cursory glance
looks correct.  Are you looking at the result of the 'OUTPUT' instruction?
(rather than just the contents of VM memory)

This is important because arguably this is as much a test of OUTPUT as of
COPY-OFFSET: the repeated string of bytes comes from the OUTPUT honouring
byte_copy_left/_right and delivering bytes 66 onwards twice!

Which leads to an interesting observation... despite being billed as a
'COPY-OFFSET' torture-test, if COPY-OFFSET is implemented correctly it
actually has *no* impact on the output of the test (except, pedantically, on
the cycle count!)

After the first COPY-LITERAL, the 'destination' never encounters
byte_copy_right (it is either too far away, at 0x4040, or below the current
value -- destination is 97 after the first COPY; byte_copy_right is reset to
74, later).  Thus the results of the subsequent COPY-OFFSETs (including a
very large offset and presumably with some expectation of testing the
wrapping/indexing) do not appear in the string that is OUTPUT!  The 0x40's
come from the first COPY-LITERAL, the other bytes from the update of
destination (which only proves that the right number of bytes have been
copied) and explicit loads and the repeat of these during the OUTPUT.

It might, in reissuing this document (which I believe we've agreed to do),
be prudent to tighten this test up a bit!  It might be nice, after all, if
it really *did* test COPY-OFFSET...

Cheers,

Mark.


> -----Original Message-----
> From: chitrak gupta [mailto:mailfromchitrak@gmail.com]
> Sent: 10 December 2004 13:12
> To: rohc@ietf.org
> Subject: [rohc] Failure in Copy-offset torture test.
> 
> 
> Dear All,
> 
> After trying for the last 2 weeks to pass the torture test for
> copy-offset I started searching for answers when I landed upon a UDVM
> implementation by Anders Broman anders.broman@ericsson.com.  I ran and
> compiled the code along with the torture test bytecode. What I got
> from the code is this:
> 
> 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 
> 
> 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40
> 
> 00 42 00 4a 40 74 40 40 40 40 40 40 40 40 40 40
> 
>  
> 
> But the result given in the torture test is this 
> 
> The expected output of the code is 32 instances of 0x40 followed by 
> 0x0042 004a 0074 4040 4040 004a 0074 4040.
> 
> So can anyone please clarify if the result in the torture test
> document is valid or if there is an error in my interpretation. Is
> there any flaw in the source code I got?
> 
> Waiting for a response,
> 
> Thanks in advance.
> 
> Chitrak
> 
> _______________________________________________
> 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


From rohc-bounces@ietf.org  Sat Dec 11 01:29:29 2004
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 BAA09110
	for <rohc-web-archive@ietf.org>; Sat, 11 Dec 2004 01:29:29 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cd0sM-0002uu-55
	for rohc-web-archive@ietf.org; Sat, 11 Dec 2004 01:37:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cd0jH-0003iU-HT; Sat, 11 Dec 2004 01:27:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cd0g8-0002ks-Bw
	for rohc@megatron.ietf.org; Sat, 11 Dec 2004 01:24:28 -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 BAA08919
	for <rohc@ietf.org>; Sat, 11 Dec 2004 01:24:26 -0500 (EST)
Received: from rproxy.gmail.com ([64.233.170.205])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cd0nS-0002qi-JY
	for rohc@ietf.org; Sat, 11 Dec 2004 01:32:03 -0500
Received: by rproxy.gmail.com with SMTP id z35so501838rne
	for <rohc@ietf.org>; Fri, 10 Dec 2004 22:24:26 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding;
	b=aPg5xZSXH4dGfNtZaGMyziiIwnJo5rD1HT+E7iBYSs+4SMsjTAc2Mba3ueSxal5NpVHBsRrysu5LSFRJOt1qvQqttTf7xNLv/y3pwA8VTG9oZgdqqLeC9Er832eKpYuHtC5sdEQigsN1gXnvqTQUp3tZe/yMqOqChFo1+Xerngo=
Received: by 10.38.83.22 with SMTP id g22mr704898rnb;
	Fri, 10 Dec 2004 22:24:26 -0800 (PST)
Received: by 10.38.83.41 with HTTP; Fri, 10 Dec 2004 22:24:26 -0800 (PST)
Message-ID: <1bd254fc041210222425c6cf7b@mail.gmail.com>
Date: Sat, 11 Dec 2004 11:54:26 +0530
From: chitrak gupta <mailfromchitrak@gmail.com>
To: rohc@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Subject: [rohc] Failure of Copy Offset in torture test.
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: chitrak gupta <mailfromchitrak@gmail.com>
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: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit

Hi Mark,

I am troubling you again.I made the required modification in the
OUTPUT instruction. The result came as  40 42 4A 74 40 40 40 40 4A 40
74. The result is coming from Ander's code as well as my
implementation.  But the torture test result should be.. 0042 004a
0074 4040 4040 004a 0074 4040


My Output:
40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40
40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40
42 4A 40 74 40 40 40 40 4A 40 74

So coming back to the same question: Is the torture test result
correct or am I missing something ?

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


From rohc-bounces@ietf.org  Sat Dec 11 01:40:56 2004
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 BAA09879
	for <rohc-web-archive@ietf.org>; Sat, 11 Dec 2004 01:40:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cd13R-00037q-M0
	for rohc-web-archive@ietf.org; Sat, 11 Dec 2004 01:48:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cd0ts-0005s1-V8; Sat, 11 Dec 2004 01:38:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cd0nx-0004k9-Bi
	for rohc@megatron.ietf.org; Sat, 11 Dec 2004 01:32:34 -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 BAA09320
	for <rohc@ietf.org>; Sat, 11 Dec 2004 01:32:31 -0500 (EST)
Received: from bay2-f1.bay2.hotmail.com ([65.54.247.1] helo=hotmail.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cd0vI-0002yJ-78
	for rohc@ietf.org; Sat, 11 Dec 2004 01:40:08 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Fri, 10 Dec 2004 22:32:00 -0800
Message-ID: <BAY2-F10B71234921BCA5C040B1A9A90@phx.gbl>
Received: from 61.11.58.91 by by2fd.bay2.hotmail.msn.com with HTTP;
	Sat, 11 Dec 2004 06:31:31 GMT
X-Originating-IP: [61.11.58.91]
X-Originating-Email: [basudeb@hotmail.com]
X-Sender: basudeb@hotmail.com
In-Reply-To: <3F2E01E1D7B04F4EBEC92D3FA324D88024D421@rsys004a.roke.co.uk>
From: "Basudeb Gupta" <basudeb@hotmail.com>
To: mark.a.west@roke.co.uk, mailfromchitrak@gmail.com, rohc@ietf.org
Subject: RE: [rohc] Failure in Copy-offset torture test.
Date: Sat, 11 Dec 2004 12:01:31 +0530
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
X-OriginalArrivalTime: 11 Dec 2004 06:32:00.0371 (UTC)
	FILETIME=[1EB18C30:01C4DF4B]
X-Spam-Score: 2.0 (++)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003
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: 2.0 (++)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365

Hi Mark,

Being a member of the same team as chitrak's I need a little help from you. 
I have a few doubts that are:

a) Does the Deflate byte code given in the user guide  correspond to the 
zlib Deflate compression algorithm? I say so because although I am able to 
deflate a compressed string as small as "Hi how are you?" which does not use 
COPY-OFFSET, a longer string invariably returns junk after decompression.

Is there a DEFLATE compression algorithm and Bytecode pair, that we can use 
to test our UDVM?

At least for the LZSS I have reasonable doubt that it is something different 
from the LZSS in the zlib.

2)  Is there a DEFALGE compression algorith and bytecode pair with static 
dictionary implementation that we can use to test our UDVM?

An early reply will be greatly appreciated, as we are in a delivery 
situation and the project is in a decisive stage.

Thanks in advance
Basudeb


>From: "West, Mark" <mark.a.west@roke.co.uk>
>To: "'chitrak gupta'" <mailfromchitrak@gmail.com>, rohc@ietf.org
>Subject: RE: [rohc] Failure in Copy-offset torture test.
>Date: Fri, 10 Dec 2004 18:10:20 -0000
>
>
>Chitrak,
>
>There is nothing wrong with the torture test (not that it couldn't be
>'improved' -- see below, but as it is, it works fine).
>
>I haven't run Anders code from Ethereal for SigComp, but at a cursory 
>glance
>looks correct.  Are you looking at the result of the 'OUTPUT' instruction?
>(rather than just the contents of VM memory)
>
>This is important because arguably this is as much a test of OUTPUT as of
>COPY-OFFSET: the repeated string of bytes comes from the OUTPUT honouring
>byte_copy_left/_right and delivering bytes 66 onwards twice!
>
>Which leads to an interesting observation... despite being billed as a
>'COPY-OFFSET' torture-test, if COPY-OFFSET is implemented correctly it
>actually has *no* impact on the output of the test (except, pedantically, 
>on
>the cycle count!)
>
>After the first COPY-LITERAL, the 'destination' never encounters
>byte_copy_right (it is either too far away, at 0x4040, or below the current
>value -- destination is 97 after the first COPY; byte_copy_right is reset 
>to
>74, later).  Thus the results of the subsequent COPY-OFFSETs (including a
>very large offset and presumably with some expectation of testing the
>wrapping/indexing) do not appear in the string that is OUTPUT!  The 0x40's
>come from the first COPY-LITERAL, the other bytes from the update of
>destination (which only proves that the right number of bytes have been
>copied) and explicit loads and the repeat of these during the OUTPUT.
>
>It might, in reissuing this document (which I believe we've agreed to do),
>be prudent to tighten this test up a bit!  It might be nice, after all, if
>it really *did* test COPY-OFFSET...
>
>Cheers,
>
>Mark.
>
>
> > -----Original Message-----
> > From: chitrak gupta [mailto:mailfromchitrak@gmail.com]
> > Sent: 10 December 2004 13:12
> > To: rohc@ietf.org
> > Subject: [rohc] Failure in Copy-offset torture test.
> >
> >
> > Dear All,
> >
> > After trying for the last 2 weeks to pass the torture test for
> > copy-offset I started searching for answers when I landed upon a UDVM
> > implementation by Anders Broman anders.broman@ericsson.com.  I ran and
> > compiled the code along with the torture test bytecode. What I got
> > from the code is this:
> >
> > 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40
> >
> > 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40
> >
> > 00 42 00 4a 40 74 40 40 40 40 40 40 40 40 40 40
> >
> >
> >
> > But the result given in the torture test is this
> >
> > The expected output of the code is 32 instances of 0x40 followed by
> > 0x0042 004a 0074 4040 4040 004a 0074 4040.
> >
> > So can anyone please clarify if the result in the torture test
> > document is valid or if there is an error in my interpretation. Is
> > there any flaw in the source code I got?
> >
> > Waiting for a response,
> >
> > Thanks in advance.
> >
> > Chitrak
> >
> > _______________________________________________
> > 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

_________________________________________________________________
Pep up your screen! Kickstart your day! 
http://www.msn.co.in/Cinema/screensaver/ Get these vibrant screensavers!


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


From rohc-bounces@ietf.org  Mon Dec 13 06:51:44 2004
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 GAA26856
	for <rohc-web-archive@ietf.org>; Mon, 13 Dec 2004 06:51:44 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cdorm-00032X-Is
	for rohc-web-archive@ietf.org; Mon, 13 Dec 2004 06:59:50 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cdoea-0000mz-B0; Mon, 13 Dec 2004 06:46:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cdod1-0000Og-Qu
	for rohc@megatron.ietf.org; Mon, 13 Dec 2004 06:44:38 -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 GAA25944
	for <rohc@ietf.org>; Mon, 13 Dec 2004 06:44:33 -0500 (EST)
Received: from rproxy.gmail.com ([64.233.170.197])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cdokp-0002rd-Ka
	for rohc@ietf.org; Mon, 13 Dec 2004 06:52:39 -0500
Received: by rproxy.gmail.com with SMTP id z35so632277rne
	for <rohc@ietf.org>; Mon, 13 Dec 2004 03:44:34 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:mime-version:content-type:content-transfer-encoding;
	b=tXfN4xSZAHyUi5cLajKRVgRixlhJt7YqmZy6N9yUdQaaC6NqvfVhkGsNlJFv3gIFVN+CBBacx71EQXaEjNjugJ622qpyiMY2spsv/7uVDO1kVDB4T8fsPWUxK5r9n44yaTPytgjjuNHWlpBYRhSwYejy615H9D88+jj3U43HsvU=
Received: by 10.38.150.47 with SMTP id x47mr73504rnd;
	Mon, 13 Dec 2004 03:44:34 -0800 (PST)
Received: by 10.38.83.41 with HTTP; Mon, 13 Dec 2004 03:44:34 -0800 (PST)
Message-ID: <1bd254fc041213034467d50ecf@mail.gmail.com>
Date: Mon, 13 Dec 2004 17:14:34 +0530
From: chitrak gupta <mailfromchitrak@gmail.com>
To: gzip@ftp.gnu.org, madler@alumni.caltech.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit
Cc: rohc@ietf.org
Subject: [rohc] Need help with deflate source parameter settings
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: chitrak gupta <mailfromchitrak@gmail.com>
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: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit

Hi,

This may be an unusual request. But I need it desparately to finish my
project. I am stuck and I think without your help I might not be able
to resolve the issue.

I need to generate a compressed data using deflate with the following
conditions.

1)    The DEFLATE compressed data format separates blocks of compressed  
      data by transmitting 7 consecutive zero bits. Each SigComp message 
      is assumed to contain a separate block of compressed data, so the 
      end-of-block bits are implicit and do not need to be transmitted 
      at the end of a SigComp message. 
    
2) Compressed data should have only DEFLATE block type 01 (data
compressed   with fixed Huffman codes).

How and where do I modify the settings (or code) in the deflate project.

Reference: deflate.c -- compress data using the deflation algorithm
 Copyright (C) 1995-2003 Jean-loup Gailly.
interface of the 'zlib' general purpose compression library
  version 1.2.1, November 17th, 2003................

Thanks a lot in advance,
Chitrak Gupta.
Kolkata, India.

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


From rohc-bounces@ietf.org  Mon Dec 13 10:18:00 2004
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 KAA17860
	for <rohc-web-archive@ietf.org>; Mon, 13 Dec 2004 10:18:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cds5P-0000Rx-9x
	for rohc-web-archive@ietf.org; Mon, 13 Dec 2004 10:26:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CdrfI-0000R6-BE; Mon, 13 Dec 2004 09:59:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CdrWE-0004ar-2y
	for rohc@megatron.ietf.org; Mon, 13 Dec 2004 09:49:46 -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 JAA15437
	for <rohc@ietf.org>; Mon, 13 Dec 2004 09:49:44 -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 1Cdre3-0008Bp-4N
	for rohc@ietf.org; Mon, 13 Dec 2004 09:57:51 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iBDEncXl020809; Mon, 13 Dec 2004 15:49:39 +0100 (MET)
In-Reply-To: <Pine.LNX.4.56.0411261659040.30341@internaut.com>
References: <Pine.LNX.4.56.0411261659040.30341@internaut.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <388536D0-4D16-11D9-A805-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] Review of draft-bormann-rohc-over-802-00.txt
Date: Mon, 13 Dec 2004 15:49:41 +0100
To: Bernard Aboba <aboba@internaut.com>, rohc@ietf.org
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: ded6070f7eed56e10c4f4d0d5043d9c7
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <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.0 (/)
X-Scan-Signature: 963faf56c3a5b6715f0b71b66181e01a
Content-Transfer-Encoding: 7bit

Bernard,
ROHCers,

I would like to thank Bernard again for his review.
We had a little offline mail exchange about this earlier.
I hadn't seen Bernard's copy of the review to the ROHC mailing list, so  
now here is my belated (and expanded) copy of the comments I already  
made in private mail.

> Here's my review.  There may be some tricky issues to watch out for  
> with
> respect to negotiation of ROHC capabilities on IEEE 802 networks that
> may make it difficult to achieve the desired level of uniformity.

We haven't really tackled the negotiation at all yet.
After a few experiments with our lab selection of 802.11 base stations,  
I believe there will be a need for some robustness features that are  
needed to make sure the elements in the 802 path are not doing strange  
things to sub-64-byte packets.
One problem with this is, of course, that the L2 path can change.

> Also, as noted by Mike Moreton:
>
> "The IEEE RAC gets very upset about anyone using OUIs in a non-standard
> way, so I doubt you'd get a lot of support for using the
> locally administered or I/G bits to distinguish your frames.  However,
> 802.11 already uses a full LLC/SNAP header, so using such
> a header would be fine for 802.11, and as you say elsewhere probably
> wouldn't make a great deal of difference for 802.3.

Well, 802.11 is using a SNAP header for Ethernet type packets, and can  
send other LLC natively.
If we use native LLC, we might get a shorter header than full SNAP.
This is what variant 1 and 2 in section 5 are about (variant 3 is full  
SNAP).
The variant 2 you are rightly criticizing is more of a last resort if  
using a different LSAP does not work out, though.

You are right, however, that the sentence about variant 3 "From an  
overhead perspective, this is not better than the PPPoE case..." is  
correct only for 802.3.

> I think the padding issue is interesting - it's funny how a drop-off in
> the original Ethernet specification is still causing us
> problems all these years later..."

Yes...

On to Bernard's review.

My original comment was:

> Some of the issues you have identified with the document are caused by  
> my negligence in making the terminology clear.
> E.g., where I talk about a "channel", I mean a "ROHC channel", which  
> in the architecture I'm proposing would likely encompass an 802.11 and  
> an 802.3 path segment.
> This is quite different from an architecture where ROHC would be  
> *below* the 802.1 bridging and thus would be implemented within the L2  
> nodes (access points/bridges), not just in the L2 interface of L3  
> nodes (hosts and routers) as I'm proposing.
> So, e.g., when I talk about setup/teardown, I mean the L3-node to  
> L3-node channel, not the L2 path segments like the 802.11 links.
>
> I propose that, before we seek wider review (and liaising with 802),  
> I'll try to make the document more accessible and clarify these  
> issues; again, your input is very useful here.
> I would like to keep some of the discussion material in the document,  
> perhaps more clearly identified as material that is going away before  
> the spec is completed.
>
> One specific question: When you talk about 802 invariants, where are  
> these documented?
> (I'm not talking about sequence preservation, which we actually need  
> to make ROHC in its current form work.)
> I'm seeing quite significant losses (and retransmission delays) in  
> today's 802.11 networks.
> In fact, once the link becomes lossy, it *also* acquires unpredictable  
> (though, fortunately, limited) delays.
> (The queueing delays, of course, also can be significant.)
> This is why my intuition says CRTP-style compression is less useful on  
> WLAN than ROHC-style compression.

to which Bernard replied:

>> So, e.g., when I talk about setup/teardown, I mean the L3-node to
>> L3-node channel, not the L2 path segments like the 802.11 links.
>
> Thanks.  If we're talking about ROHC capabilities negotiation between  
> L3
> endpoints (e.g. over IP) that will get around the issues with
> heterogeneity in IEEE 802 discovery facilities.
>
>> One specific question: When you talk about 802 invariants, where are
>> these documented?
>
> A good reference on IEEE 802 link invariants is "The Switch Book" by  
> Rich
> Seifert. Section 2.2.1 discusses "hard" invariants (non duplication and
> sequential delivery) and "soft" invariants (low error rate, high
> bandwidth, low delay).  See:
> http://www.amazon.com/exec/obidos/ASIN/0471345865/argospress-20/103 
> -5896643-7439011?creative=327641&camp=14573&link_code=as1
>
>> I'm seeing quite significant losses (and retransmission delays) in
>> today's 802.11 networks.
>> In fact, once the link becomes lossy, it *also* acquires unpredictable
>> (though, fortunately, limited) delays.
>
> In an indoor network, these issues are typically due to multi-path
> problems or coverage blackholes, exacerbated by poor implementations.
> In outdoor networks, the problems are more common.  For example, see:
> http://www.pdos.lcs.mit.edu/~rtm/papers/p442-aguayo.pdf
>
> Aspects of 802.11 behavior are not standardized, including roaming
> behavior and rate negotiation.  This means, for example, that some  
> 802.11
> NICs will retransmit for long periods of time before detecting that the
> connection has failed and scanning for another AP.  Even under  
> conditions
> of extreme congestion it is rare to require more than 3  
> retransmissions,
> and if the Beacon signal is missing in addition, there is little point  
> in
> continuing.  Yet, in our experiments we have seen NICs retransmit as  
> long
> as 30 seconds before scanning.

I assume fine-tuning ROHC-over-802 for existing 802.11 networks will  
require some more experiments and measurements akin to those that we  
did about LLC bridging in APs.

On to some more specific comments in the original review:

> [BA] 802.11 Access Points are not bridges as defined by 802.1D.  For
> example, they are not required to run spanning tree, do not maintain
> learning tables as specified in 802.1D, etc.

I believe this mainly identifies a terminology problem.  I need a term  
for all these bridge-like devices that are intermediate systems in the  
L2 paths we are trying to cross undamaged (and unpadded).
Any suggestion?

> [BA] Note that 802 links are only required to preserve ordering within
> a given 802.1p priority group.

Very good point; I'll add this.
(By comparison, RFC 3241 says:
    ROHC assumes that the link layer delivers packets in sequence.  PPP
    normally does not reorder packets.  When using reordering mechanisms
    such as multiclass multilink PPP [RFC2686], care must be taken so
    that packets that share the same compression context are not
    reordered.  (Note that in certain cases, reordering may be acceptable
    to ROHC, such as within a sequence of packets that all do not change
    the decompression context.)
)

There were a couple more comments similar to:

> [BA] Since it can be argued that knowledge of ROHC capabilities could  
> be
> relevant to 802.11 roaming decisions, it may not be possible to handle
> ROHC capability discovery in a generic manner for all IEEE 802 media.

If we stick with the "compression at L3-L2 boundary" model, this  
becomes a CARD/AR selection issue, I think.
Outside of 802 itself.

> [BA] LLC encapsulation does make sense to me since this is most general
> (e.g. works on 802.11 as well as 802.3).  I'd like to get more review
> comments on this from the IEEE 802 folks.

Yes, please!

I'll generate a -01 based on the discussion we had so far by this  
weekend.
I hope this will be clearer about the place in the architecture and  
more specific about the encapsulation considerations.
This might then be a good basis to try to elicit more feedback.

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Mon Dec 13 11:06:32 2004
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 LAA23018
	for <rohc-web-archive@ietf.org>; Mon, 13 Dec 2004 11:06:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CdsqM-0001hM-Rb
	for rohc-web-archive@ietf.org; Mon, 13 Dec 2004 11:14:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CdsSo-0002iz-Be; Mon, 13 Dec 2004 10:50:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CdrIu-0000QI-Ul
	for rohc@megatron.ietf.org; Mon, 13 Dec 2004 09:36:01 -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 JAA14448
	for <rohc@ietf.org>; Mon, 13 Dec 2004 09:35:59 -0500 (EST)
Received: from quest.jpl.nasa.gov ([137.79.57.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdrQj-0007rJ-0j
	for rohc@ietf.org; Mon, 13 Dec 2004 09:44:06 -0500
Received: from [10.0.1.3] (66-214-189-158.gln-eres.charterpipeline.net
	[66.214.189.158]) by quest.jpl.nasa.gov (Postfix) with ESMTP
	id 6B773C10FDB; Mon, 13 Dec 2004 06:35:27 -0800 (PST)
In-Reply-To: <1bd254fc041213034467d50ecf@mail.gmail.com>
References: <1bd254fc041213034467d50ecf@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <399490BA-4D14-11D9-931D-000A95820F30@alumni.caltech.edu>
Content-Transfer-Encoding: 7bit
From: Mark Adler <madler@alumni.caltech.edu>
Date: Mon, 13 Dec 2004 06:35:24 -0800
To: chitrak gupta <mailfromchitrak@gmail.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 13 Dec 2004 10:50:17 -0500
Cc: gzip@ftp.gnu.org, rohc@ietf.org
Subject: [rohc] Re: Need help with deflate source parameter settings
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: 2.9 (++)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit

On Dec 13, 2004, at 3:44 AM, chitrak gupta wrote:
> 2) Compressed data should have only DEFLATE block type 01 (data
> compressed   with fixed Huffman codes).
>
> How and where do I modify the settings (or code) in the deflate 
> project.

You need to recompile trees.c with FORCE_STATIC #define'd.  By the way, 
you should be using zlib 1.2.2, which you can find here:

     http://www.zlib.net/

mark


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


From rohc-bounces@ietf.org  Tue Dec 14 04:15:37 2004
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 EAA03754
	for <rohc-web-archive@ietf.org>; Tue, 14 Dec 2004 04:15:37 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ce8uQ-00024O-FO
	for rohc-web-archive@ietf.org; Tue, 14 Dec 2004 04:23:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ce8lJ-0007YE-1V; Tue, 14 Dec 2004 04:14:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ce8jN-0007Mw-29
	for rohc@megatron.ietf.org; Tue, 14 Dec 2004 04:12:29 -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 EAA03527
	for <rohc@ietf.org>; Tue, 14 Dec 2004 04:12:27 -0500 (EST)
From: Paulius.Meskauskas@nokia.com
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ce8rM-0001ze-3A
	for rohc@ietf.org; Tue, 14 Dec 2004 04:20:44 -0500
Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iBE9CCD05114; Tue, 14 Dec 2004 11:12:15 +0200 (EET)
X-Scanned: Tue, 14 Dec 2004 11:11:29 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id iBE9BTRZ013937;
	Tue, 14 Dec 2004 11:11:29 +0200
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks003.ntc.nokia.com 00jCP8t7; Tue, 14 Dec 2004 11:11:26 EET
Received: from esebh001.NOE.Nokia.com (esebh001.ntc.nokia.com [172.21.138.28])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iBE9BQ303460; Tue, 14 Dec 2004 11:11:26 +0200 (EET)
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by
	esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Tue, 14 Dec 2004 11:11:14 +0200
Received: from esebe001.NOE.Nokia.com ([172.21.138.30]) by
	esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Tue, 14 Dec 2004 11:11:14 +0200
Received: from esebe052.NOE.Nokia.com ([172.21.138.217]) by
	esebe001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Tue, 14 Dec 2004 11:11:12 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] Re: multiplexing SigComp and non-SigComp messages on t
	hesame TCP connection
Date: Tue, 14 Dec 2004 11:11:13 +0200
Message-ID: <62F243FC21653C40A45B8C54FB0D4618415C33@esebe052.ntc.nokia.com>
Thread-Topic: [rohc] Re: multiplexing SigComp and non-SigComp messages on t
	hesame TCP connection
Thread-Index: AcTL9CIP8oInb0dlREKIJ28gqLKxGAVxyHDw
To: <cabo@tzi.org>, <abigail.surtees@ROKE.CO.UK>
X-OriginalArrivalTime: 14 Dec 2004 09:11:12.0960 (UTC)
	FILETIME=[DBB83400:01C4E1BC]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: quoted-printable
Cc: mark.a.west@ROKE.CO.UK, rohc@ietf.org, zhigang.c.liu@nokia.com,
        lwc@ROKE.CO.UK
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: c3a18ef96977fc9bcc21a621cbf1174b
Content-Transfer-Encoding: quoted-printable

hello,

OMA PoC mandates the usage of SigComp and in case IMS core
is used - the compression must take place between UE and P-CSCF.

IMHO there's no need for 'uncompressed SigComp header' in order
to keep SigComp generic and allow the multiplexing.. The main thing=20
is to break the SigComp dependency to the transport layer in the =
implementation=20
i.e. text-based protocols know their delimiters and SigComp knows its =
own.=20

cheers,
	paulius


> -----Original Message-----
> From: rohc-bounces@ietf.org [mailto:rohc-bounces@ietf.org]On Behalf Of
> ext Carsten Bormann
> Sent: Tuesday, November 16, 2004 5:31 PM
> To: Surtees, Abigail
> Cc: West, Mark; Sugar Robert (Nokia-NET/Budapest); Liu Zhigang.C
> (Nokia-NRC/Dallas); rohc@ietf.org; Conroy, Lawrence (SMTP); Carsten
> Bormann
> Subject: Re: [rohc] Re: multiplexing SigComp and non-SigComp=20
> messages on
> t hesame TCP connection
>=20
>=20
> Abbie,
>=20
> 3GPP submission S2-043577 says:
>=20
> > For TCP, none of the existing standards mandates whether or not=20
> > endpoints must be able to multiplex SIP and SigComp messages on the=20
> > same TCP connection however, the IETF currently see no need to=20
> > multiplex and would like to mandate that it must not be=20
> done. We note=20
> > that with the IMS security architecture there are some constraints=20
> > with regards to the usage of ports on the P-CSCF and the UE. During=20
> > the establishment of the IPSec security association the UE and the=20
> > P-CSCF negotiate 2 ports on each side. These ports are used as the=20
> > selector for the corresponding security association and are=20
> fixed for=20
> > the duration of the security association. Consequently, if=20
> there is a=20
> > need to send both SIP and SigComp messages over TCP, they=20
> would have=20
> > to be on the same connection.
> >
> > It seems, however, that the issue is not a real issue for=20
> IMS and PoC,=20
> > as it is mandated that terminals and networks will support SigComp=20
> > (though its use is not mandatory). Consequently a terminal=20
> can decide=20
> > on the first message whether or not it is going to use=20
> SigComp and not=20
> > change. In this case, if there is a need to send an uncompressed=20
> > message (e.g. due to loss of sync between compressor and=20
> decompressor,=20
> > or to reduce processing load) when SigComp is in use, the=20
> > 'uncompressed SigComp header' can be used. This is a set of 13 well=20
> > known bytes that are prepended to the SIP message to make=20
> it a SigComp=20
> > message and are removed as a block at the decompressor.
>=20
> This fits pretty well with what was said in the San Diego WG meeting=20
> and hallway discussions, and this is what was intended by my slide in=20
> Washington.
>=20
> (Sorry if I'm incoherent -- I'm wrestling with my usual post-IETF=20
> aircon-induced fever.)
>=20
> Gruesse, Carsten
>=20
>=20
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
>=20

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


From rohc-bounces@ietf.org  Tue Dec 14 05:52:01 2004
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 FAA12319
	for <rohc-web-archive@ietf.org>; Tue, 14 Dec 2004 05:52:01 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeAPj-0004SW-Qg
	for rohc-web-archive@ietf.org; Tue, 14 Dec 2004 06:00:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeACf-00024N-9d; Tue, 14 Dec 2004 05:46:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeABa-0001nA-VH
	for rohc@megatron.ietf.org; Tue, 14 Dec 2004 05:45:43 -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 FAA11904
	for <rohc@ietf.org>; Tue, 14 Dec 2004 05:45:40 -0500 (EST)
Received: from [194.237.235.30] (helo=effnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeAJa-0004JK-82
	for rohc@ietf.org; Tue, 14 Dec 2004 05:53:59 -0500
Received: from effnet.com (c-b97c71d5.04-205-6c756c1.cust.bredbandsbolaget.se
	[213.113.124.178]) (authenticated bits=0)
	by effnet.com (8.12.3/8.12.3) with ESMTP id iBE9idLh030534
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Tue, 14 Dec 2004 10:44:41 +0100
Message-ID: <41BEC443.8050209@effnet.com>
Date: Tue, 14 Dec 2004 11:45:23 +0100
From: Kristofer Sandlund <kristofer.sandlund@effnet.com>
Organization: Effnet
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: rohc@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Content-Transfer-Encoding: 7bit
Subject: [rohc] Nits/bugs/Changes to ROHC-TCP-08
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.1 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Content-Transfer-Encoding: 7bit

Hi all!

Here's another list of nits, bugs and requested changes to the ROHC-TCP spec 
(for older stuff still-to-be-fixed, see 
http://www1.ietf.org/mail-archive/web/rohc/current/msg03072.html)

* There is a field next_header in the tcp_static part of the FN. Should go (I've 
already updated the CVS with this).

* We've managed to set the TCP-ECN stuff so that se transmit the tcp_ecn_flags 
_before_ the tcp_res_flags, but according to RFC3168, they appear in this order 
in the uncompressed header:
       +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
       |               |               | C | E | U | A | P | R | S | F |
       | Header Length |    Reserved   | W | C | R | C | S | S | Y | I |
       |               |               | R | E | G | K | H | T | N | N |
       +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
  Therefore, I will change the order of these in the FN code to make it easier 
for implementations.

* tcp_dynamic chain item has strange order of fields, so I propose updating the 
order as follows (including the ECN order change from above):
         format_tcp_dynamic =  ecn_used,              %[ 1 ]
                               padding,               %[ 1 ]
                               ack_zero,              %[ 1 ]
                               urp_zero,              %[ 1 ]
                               tcp_res_flags,         %[ 4 ]
                               tcp_ecn_flags,         %[ 2 ]
                               urg_flag,              %[ 1 ]
                               ack_flag,              %[ 1 ]
                               psh_flag,              %[ 1 ]
                               rsf_flags,             %[ 3 ]
                               msn,                   %[ 16 ]
                               seq_number,            %[ 32 ]
                               ack_number,            %  0 or 32 bits
                               window,                %[ 16 ]
                               checksum,              %[ 16 ]
                               urg_ptr,               %  0 or 16 bits
                               options,               %  n bits
Now, all the TCP flags + the reserved and ECN appear on the same order and at 
the same "byte boundaries" as in the uncompressed header, which seems to make a 
lot more sense. Will add this to the CVS.

* The discriminators used for IR and IR-CR seems a bit inconsistent. In 3095, we 
have:
11111101 = IR with dynamic + static chain
11111100 = IR with only static chain
In ROHC-TCP, we have:
11111101 = IR-CR
11111100 = IR with dynamic + static chain

Therefore, the "IR with dynamic + static chain" has different discriminators in 
the two profiles. Therefore I propose to switch places for these two 
discriminators in ROHC-TCP. Will have no functional impact, but will make things 
a bit more consistent.

* tcp_replicate is wrong in the FN code.
         format_tcp_replicate = <snip>
                                tcp_ecn_flags,       %[ 2 ]
                                ecn_used,            %[ 1 ]
			       <snip>
                                tcp_ecn_flags,       %  0 or 2 bits
                                tcp_res_flags,       %  0 or 4 bits
                                options_list,        %  n bits
First of all, it appears that the tcp_ecn_flags could appear twice and there is 
no control bit for the tcp_res_flags presence.
Secondly, the optional part is not octet-aligned, which is bad.

Therefore, I suggest that ecn_used controls if those two fields are present or 
not (since that's how we use it elsewhere) and that I add 2 bits of padding in 
the optional part of the chain. Also, the first place where tcp_ecn_flags is 
located will be replaced by more padding (or we can use it for something else, 
such as ack_stride indicator when/if we add ack scaling).

* section 3.2:
    "This means that on the
    forward path (from server to client), only the sequence number is
    changing while the acknowledgement number remains constant for most
    packets; on the backward path (from client to server), only the
    sequence number is changing and the acknowledgement number remains
    constant for most packets."
I guess that's a cut&paste error, since it says that both directions have a 
changing sequence number and a constant ack. I guess the "backward path" should 
switch places of those two words.

BR,
	Kristofer Sandlund, Effnet AB

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


From rohc-bounces@ietf.org  Tue Dec 14 14:33:56 2004
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 OAA08528
	for <rohc-web-archive@ietf.org>; Tue, 14 Dec 2004 14:33:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeIYh-0003Qe-F6
	for rohc-web-archive@ietf.org; Tue, 14 Dec 2004 14:42:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeIHm-0000B0-FV; Tue, 14 Dec 2004 14:24:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeIEr-00081s-NK
	for rohc@megatron.ietf.org; Tue, 14 Dec 2004 14:21:38 -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 OAA07420
	for <rohc@ietf.org>; Tue, 14 Dec 2004 14:21:36 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeIMv-00035t-VR
	for rohc@ietf.org; Tue, 14 Dec 2004 14:29:58 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBEJLZO6005384 for <rohc@ietf.org>; Tue, 14 Dec 2004 20:21:35 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 14 Dec 2004 20:21:34 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <XVCXRVMF>; Tue, 14 Dec 2004 20:21:34 +0100
Message-ID: <A943FD84BD9ED41193460008C79180500C5706E2@ESEALNT419.al.sw.ericsson.se>
From: "Ghyslain Pelletier (LU/EAB)" <ghyslain.pelletier@ericsson.com>
To: "'Kristofer Sandlund'" <kristofer.sandlund@effnet.com>, rohc@ietf.org
Date: Tue, 14 Dec 2004 20:21:32 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 14 Dec 2004 19:21:34.0380 (UTC)
	FILETIME=[1FC96EC0:01C4E212]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Subject: [rohc] RE: Comments on tcp-08
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: 5d7a7e767f20255fce80fa0b77fb2433

Hi Kristofer,

Thanks for your comments. See inline.

/Ghyslain

> -----Original Message-----
> - General comments:

> section (4.6) should move to somewhere inside section 6, 

Will do.

> Also, I think I'd prefer to move section 6.8 to being 
> before all the ROHC-FN-code, so that the FN definitions

Agree.

> 
> - 5.2.7
>       In NC state:
> 

I suggest to write this pointer in the sentence above, as follow:

  "Once the feedback channel is established, the decompressor is
   REQUIRED to continue sending feedback (subject to the feedback
   rate limiting considerations later in this section) for the
   lifetime of the packet stream as follow:

   In NC state:
  "

Ok?

>      Also:
> 
>       In FC state:
> 
>          The decompressor SHOULD send a NACK when decompression of any
>          packet type fails and if context damage is assumed (see also
>          section 5.2.3).
> 
> This text seems a bit hard to interpret. Maybe it would 
> be better to write:
> 
>    When context damage is assumed and the decompression of any
>    compressed packet fails, the decompressor SHOULD 
>    send a NACK (see also section 5.2.3).
> 
>      Because that's the intention, right?

Actually, the intention of the text is to say that "if you don't have assumed context damage yet, and if the decompression of any packet type fails which leads you to assume context damage, the decompressor should send a NACK". Which is why the text uses "when" and then "if". That is, the condition that context damage is already assumed from the failure of a previous packet is no pre-requisite, which is how I interpret your suggested text. So I wouldn't make changes...
 
> - 6.5 "ends with the static part of a TCP packet" -> "packet" 
> is not a good word here. Maybe "ends with a TCP replication
> item" or maybe even "ends with a TCP static chain item". Not sure.

How about:

   6.5.  Initialization

   The static context of ROHC TCP streams can be initialized in either
   two ways:

   1) By using an IR packet as in section 6.6.1, where the profile is
   six (6) and the static chain ends with the static part of a TCP
   header. 

   2) By replicating an existing context using the mechanism defined
   by ROHC-CR. This is done with the IR-CR packet defined in section
   6.6.2, where the profile number is six (6). 

Note that I have simply replaced TCP packet with TCP header in 1), and removed the last bit in 2) since it seems to be actually sufficient that the packet type be IR-CR with profile number being ROHC-TCP. It seems we don't need to have more text there.
 
> - 6.6 "30 packet formats" - not that many in there right now. 
> Maybe remove this sentence altogether.

I'll leave it in for now and make sure that the numbers are right once all packet formats are set in stone.
 
> - 6.6.2 The coding of small CIDs in the "Base CID" field is 
> not obvious, since 
> in other CID fields, the small CID is encoded as an add-CID 
> with 0xe<value>, but 
> here I guess it should be 0x0<value> instead. Maybe draw 
> something like:
> 
>     +---+---+---+---+---+---+---+---+
>     :      0        | Base CID Small: 1 octet, if small CID and B=1
>     +---+---+---+---+---+---+---+---+
>     :                               :
>     /        Base CID Large         / 1-2 octets, if large 
> CIDs and B=1
>     :                               :
>     +---+---+---+---+---+---+---+---+

Fixed from our offline discussion.
 
> - 6.6.3 "variable number of bits" (base header field). Since 
> this will always be 
> a multiple of 8 bits, it might be better to say "variable 
> number of octets".

Fixed.
 
> - 6.7 The two constants defined are not used any longer so 
> they should be 
> removed and also the sentence above them.

Fixed.
 
> - 6.8.2 Some references to 3095 are for the wrong section:
> 	"section 5.7.6.6" should be "section 5.7.6.7" (CLOCK option)
> 	"section 5.7.6.7" should be "section 5.7.6.8" (JITTER option)
> 

Actually, I have removed those bullets and instead included explicitly all relevant 3095 options to the ROHC-TCP profile in the draft.

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


From rohc-bounces@ietf.org  Tue Dec 14 14:39:27 2004
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 OAA09136
	for <rohc-web-archive@ietf.org>; Tue, 14 Dec 2004 14:39:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeIeD-0003ac-2l
	for rohc-web-archive@ietf.org; Tue, 14 Dec 2004 14:47:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeIRl-0002fh-1T; Tue, 14 Dec 2004 14:34:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeIMN-0001EW-Rm
	for rohc@megatron.ietf.org; Tue, 14 Dec 2004 14:29: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 OAA07971
	for <rohc@ietf.org>; Tue, 14 Dec 2004 14:29:19 -0500 (EST)
Received: from hoemail1.lucent.com ([192.11.226.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeIUP-0003Iz-BP
	for rohc@ietf.org; Tue, 14 Dec 2004 14:37:41 -0500
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com
	[135.86.145.57])
	by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id iBEJTGbH002028
	for <rohc@ietf.org>; Tue, 14 Dec 2004 13:29:17 -0600 (CST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service
	(5.5.2657.72) id <YSX8DRP3>; Tue, 14 Dec 2004 19:29:16 -0000
Message-ID: <475FF955A05DD411980D00508B6D5FB00C29027A@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: "'Paulius.Meskauskas@nokia.com'" <Paulius.Meskauskas@nokia.com>,
        cabo@tzi.org, abigail.surtees@ROKE.CO.UK
Subject: RE: [rohc] Re: multiplexing SigComp and non-SigComp messages on t
	hesame TCP connection
Date: Tue, 14 Dec 2004 19:29:12 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ded6070f7eed56e10c4f4d0d5043d9c7
Cc: rohc@ietf.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.0 (/)
X-Scan-Signature: 963faf56c3a5b6715f0b71b66181e01a

For information, we ended up with the following text (unofficial version - official version of CR still being implemented) covering 3GPP IMS compression in 3GPP TS 24.229 as a result of the latest round of meetings.

Our discussions in 3GPP assumed that the statement regarding multiplexing of Sigcomp and non-Sigcomp in draft-ietf-rohc-sigcomp-sip-01 to stand.

regards

Keith

8	SIP compression

8.1	SIP compression procedures at the UE

8.1.1	SIP compression

The UE shall support SigComp as specified in RFC 3320 [32]. When using SigComp the UE shall send compressed SIP messages in accordance with RFC 3486 [55]. When the UE will create the compartment is implementation specific, but the compartment shall not be created until a set of security associations are set up. The compartment shall finish when the UE is deregistered. State creations and announcements shall be allowed only for messages received in a security association.

NOTE:	Exchange of bytecodes during registration will prevent unnecessary delays during session setup.

Editor's note: 	The draft-ietf-rohc-sigcomp-sip-01 [79] can lead to the need for additional changes or clarifications.

The UE shall support the SIP dictionary specified in RFC 3485 [42]. If compression is enabled, the UE shall use the dictionary to compress the first message. 

The following apply when signalling compression is used:

-	State Memory Size (SMS) greater than zero is needed to give room for the UDVM byte code and make dynamic compression possible. A State Memory Size of at least 4096 bytes shall be a minimum value; and

-	A Decompression Memory Size (DMS) of at least 8192 bytes should be a minimum value.

8.1.2	Compression of SIP requests and responses transmitted to the P-CSCF

The UE should compress the requests and responses transmitted to the P-CSCF according to subclause 8.1.1.

NOTE 1:	Compression of SIP messages is an implementation option. However, compression is strongly recommended.

NOTE 2:	Since compression support is mandatory, the UE may send even the first message compressed. Sigcomp provides mechanisms to allow the UE to know if state has been created in the P-CSCF or not.

8.1.3	Decompression of SIP requests and responses received from the P-CSCF

The UE shall decompress the compressed requests and responses received from the P-CSCF according to subclause 8.1.1.

If the UE detects a decompression failure at the P-CSCF, the recovery mechanism is implementation specific and this may, as an example, include resetting the compartment, changing the algorithm.

8.2	SIP compression procedures at the P-CSCF

8.2.1	SIP compression

The P-CSCF shall support SigComp as specified in RFC 3320 [32]. When using SigComp the P-CSCF shall send compressed SIP messages in accordance with RFC 3486 [55]. When the P-CSCF will create the compartment is implementation specific, but the compartment shall not be created until a set of security associations are set up. The compartment shall finish when the UE is deregistered. State creations and announcements shall be allowed only for messages received in a security association.

The P-CSCF shall support the SIP dictionary specified in RFC 3485 [42]. If compression is enabled, the P-CSCF shall use the dictionary to compress the first message.

NOTE:	Exchange of bytecodes during registration will prevent unnecessary delays during session setup.

Editor's note: 	The draft-ietf-rohc-sigcomp-sip-01 [79] can lead to the need for additional changes or clarifications.

The following apply when signalling compression is used:

-	State Memory Size (SMS) greater than zero is needed to give room for the UDVM byte code and make dynamic compression possible. A State Memory Size of at least 4096 bytes shall be a minimum value; and

-	A Decompression Memory Size (DMS) of at least 8192 bytes should be a minimum value.

8.2.2	Compression of SIP requests and responses transmitted to the UE

The P-CSCF should compress the requests and responses transmitted to the UE according to subclause 8.2.1.

NOTE:	Compression of SIP messages is an implementation option. However, compression is strongly recommended.

8.2.3	Decompression of SIP requests and responses received from the UE

The P-CSCF shall decompress the compressed requests and responses received from the UE according to subclause 8.2.1.

If the P-CSCF detects a decompression failure at the UE, the recovery mechanism is implementation specific and this may, as an example, include resetting the compartment, changing the algorithm.


> -----Original Message-----
> From: rohc-bounces@ietf.org [mailto:rohc-bounces@ietf.org]On Behalf Of
> Paulius.Meskauskas@nokia.com
> Sent: 14 December 2004 09:11
> To: cabo@tzi.org; abigail.surtees@ROKE.CO.UK
> Cc: mark.a.west@ROKE.CO.UK; rohc@ietf.org; zhigang.c.liu@nokia.com;
> lwc@ROKE.CO.UK
> Subject: RE: [rohc] Re: multiplexing SigComp and non-SigComp 
> messages on
> t hesame TCP connection
> 
> 
> hello,
> 
> OMA PoC mandates the usage of SigComp and in case IMS core
> is used - the compression must take place between UE and P-CSCF.
> 
> IMHO there's no need for 'uncompressed SigComp header' in order
> to keep SigComp generic and allow the multiplexing.. The main thing 
> is to break the SigComp dependency to the transport layer in 
> the implementation 
> i.e. text-based protocols know their delimiters and SigComp 
> knows its own. 
> 
> cheers,
> 	paulius
> 
> 
> > -----Original Message-----
> > From: rohc-bounces@ietf.org 
> [mailto:rohc-bounces@ietf.org]On Behalf Of
> > ext Carsten Bormann
> > Sent: Tuesday, November 16, 2004 5:31 PM
> > To: Surtees, Abigail
> > Cc: West, Mark; Sugar Robert (Nokia-NET/Budapest); Liu Zhigang.C
> > (Nokia-NRC/Dallas); rohc@ietf.org; Conroy, Lawrence (SMTP); Carsten
> > Bormann
> > Subject: Re: [rohc] Re: multiplexing SigComp and non-SigComp 
> > messages on
> > t hesame TCP connection
> > 
> > 
> > Abbie,
> > 
> > 3GPP submission S2-043577 says:
> > 
> > > For TCP, none of the existing standards mandates whether or not 
> > > endpoints must be able to multiplex SIP and SigComp 
> messages on the 
> > > same TCP connection however, the IETF currently see no need to 
> > > multiplex and would like to mandate that it must not be 
> > done. We note 
> > > that with the IMS security architecture there are some 
> constraints 
> > > with regards to the usage of ports on the P-CSCF and the 
> UE. During 
> > > the establishment of the IPSec security association the 
> UE and the 
> > > P-CSCF negotiate 2 ports on each side. These ports are 
> used as the 
> > > selector for the corresponding security association and are 
> > fixed for 
> > > the duration of the security association. Consequently, if 
> > there is a 
> > > need to send both SIP and SigComp messages over TCP, they 
> > would have 
> > > to be on the same connection.
> > >
> > > It seems, however, that the issue is not a real issue for 
> > IMS and PoC, 
> > > as it is mandated that terminals and networks will 
> support SigComp 
> > > (though its use is not mandatory). Consequently a terminal 
> > can decide 
> > > on the first message whether or not it is going to use 
> > SigComp and not 
> > > change. In this case, if there is a need to send an uncompressed 
> > > message (e.g. due to loss of sync between compressor and 
> > decompressor, 
> > > or to reduce processing load) when SigComp is in use, the 
> > > 'uncompressed SigComp header' can be used. This is a set 
> of 13 well 
> > > known bytes that are prepended to the SIP message to make 
> > it a SigComp 
> > > message and are removed as a block at the decompressor.
> > 
> > This fits pretty well with what was said in the San Diego 
> WG meeting 
> > and hallway discussions, and this is what was intended by 
> my slide in 
> > Washington.
> > 
> > (Sorry if I'm incoherent -- I'm wrestling with my usual post-IETF 
> > aircon-induced fever.)
> > 
> > Gruesse, Carsten
> > 
> > 
> > _______________________________________________
> > 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


From rohc-bounces@ietf.org  Wed Dec 15 04:27:47 2004
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 EAA14841
	for <rohc-web-archive@ietf.org>; Wed, 15 Dec 2004 04:27:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeVZy-0008E8-66
	for rohc-web-archive@ietf.org; Wed, 15 Dec 2004 04:36:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeVOM-0002es-AM; Wed, 15 Dec 2004 04:24:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeVBp-0000hb-HM
	for rohc@megatron.ietf.org; Wed, 15 Dec 2004 04:11:22 -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 EAA13701
	for <rohc@ietf.org>; Wed, 15 Dec 2004 04:11:19 -0500 (EST)
From: Paulius.Meskauskas@nokia.com
Received: from mgw-x2.nokia.com ([131.228.20.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeVJs-0007mf-15
	for rohc@ietf.org; Wed, 15 Dec 2004 04:19:49 -0500
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120])
	by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iBF9Ajr18577; Wed, 15 Dec 2004 11:10:46 +0200 (EET)
X-Scanned: Wed, 15 Dec 2004 11:15:35 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks001.ntc.nokia.com (8.12.9/8.12.9) id iBF9FZOj022622;
	Wed, 15 Dec 2004 11:15:35 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks001.ntc.nokia.com 00SZdnU3; Wed, 15 Dec 2004 11:15:22 EET
Received: from esebh001.NOE.Nokia.com (esebh001.ntc.nokia.com [172.21.138.28])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iBF99wD19239; Wed, 15 Dec 2004 11:09:58 +0200 (EET)
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by
	esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 15 Dec 2004 11:09:48 +0200
Received: from esebe018.NOE.Nokia.com ([172.21.138.57]) by
	esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 15 Dec 2004 11:09:46 +0200
Received: from esebe052.NOE.Nokia.com ([172.21.138.217]) by
	esebe018.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 15 Dec 2004 11:09:47 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] Re: multiplexing SigComp and non-SigComp messages on t
	hesame TCP connection
Date: Wed, 15 Dec 2004 11:09:47 +0200
Message-ID: <62F243FC21653C40A45B8C54FB0D4618415C4B@esebe052.ntc.nokia.com>
Thread-Topic: [rohc] Re: multiplexing SigComp and non-SigComp messages on t
	hesame TCP connection
Thread-Index: AcTiE1yvg8OiKp5KSh2RwjJomAb/zgAbQw/Q
To: <drage@lucent.com>, <cabo@tzi.org>, <abigail.surtees@ROKE.CO.UK>
X-OriginalArrivalTime: 15 Dec 2004 09:09:47.0462 (UTC)
	FILETIME=[D32BFE60:01C4E285]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: e178fd6cb61ffb6940cd878e7fea8606
Content-Transfer-Encoding: quoted-printable
Cc: rohc@ietf.org, georg.mayer@nokia.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.3 (/)
X-Scan-Signature: 27ec2ff0f5c3b18b49c722f4f1748838
Content-Transfer-Encoding: quoted-printable

Keith,

thank you for the information. However, I want to point
out that if the statement about the multiplexing in =
draft-ietf-rohc-sigcomp-sip-01=20
is the final one- it will cause unnecessary changes in the =
implementations
already supporting multiplexing (and will break backwards =
compatibility).
That's why I think that multiplexing should be allowed without any=20
extra 'uncompressed SigComp headers".

regards,
	paulius

> -----Original Message-----
> From: ext Drage, Keith (Keith) [mailto:drage@lucent.com]
> Sent: Tuesday, December 14, 2004 9:29 PM
> To: Meskauskas Paulius (Nokia-TP-MSW/Helsinki); cabo@tzi.org;
> abigail.surtees@ROKE.CO.UK
> Cc: rohc@ietf.org
> Subject: RE: [rohc] Re: multiplexing SigComp and non-SigComp=20
> messages on
> t hesame TCP connection
>=20
>=20
> For information, we ended up with the following text=20
> (unofficial version - official version of CR still being=20
> implemented) covering 3GPP IMS compression in 3GPP TS 24.229=20
> as a result of the latest round of meetings.
>=20
> Our discussions in 3GPP assumed that the statement regarding=20
> multiplexing of Sigcomp and non-Sigcomp in=20
> draft-ietf-rohc-sigcomp-sip-01 to stand.
>=20
> regards
>=20
> Keith
>=20
> 8	SIP compression
>=20
> 8.1	SIP compression procedures at the UE
>=20
> 8.1.1	SIP compression
>=20
> The UE shall support SigComp as specified in RFC 3320 [32].=20
> When using SigComp the UE shall send compressed SIP messages=20
> in accordance with RFC 3486 [55]. When the UE will create the=20
> compartment is implementation specific, but the compartment=20
> shall not be created until a set of security associations are=20
> set up. The compartment shall finish when the UE is=20
> deregistered. State creations and announcements shall be=20
> allowed only for messages received in a security association.
>=20
> NOTE:	Exchange of bytecodes during registration will prevent=20
> unnecessary delays during session setup.
>=20
> Editor's note: 	The draft-ietf-rohc-sigcomp-sip-01 [79]=20
> can lead to the need for additional changes or clarifications.
>=20
> The UE shall support the SIP dictionary specified in RFC 3485=20
> [42]. If compression is enabled, the UE shall use the=20
> dictionary to compress the first message.=20
>=20
> The following apply when signalling compression is used:
>=20
> -	State Memory Size (SMS) greater than zero is needed to=20
> give room for the UDVM byte code and make dynamic compression=20
> possible. A State Memory Size of at least 4096 bytes shall be=20
> a minimum value; and
>=20
> -	A Decompression Memory Size (DMS) of at least 8192=20
> bytes should be a minimum value.
>=20
> 8.1.2	Compression of SIP requests and responses transmitted=20
> to the P-CSCF
>=20
> The UE should compress the requests and responses transmitted=20
> to the P-CSCF according to subclause 8.1.1.
>=20
> NOTE 1:	Compression of SIP messages is an=20
> implementation option. However, compression is strongly recommended.
>=20
> NOTE 2:	Since compression support is mandatory, the UE=20
> may send even the first message compressed. Sigcomp provides=20
> mechanisms to allow the UE to know if state has been created=20
> in the P-CSCF or not.
>=20
> 8.1.3	Decompression of SIP requests and responses received=20
> from the P-CSCF
>=20
> The UE shall decompress the compressed requests and responses=20
> received from the P-CSCF according to subclause 8.1.1.
>=20
> If the UE detects a decompression failure at the P-CSCF, the=20
> recovery mechanism is implementation specific and this may,=20
> as an example, include resetting the compartment, changing=20
> the algorithm.
>=20
> 8.2	SIP compression procedures at the P-CSCF
>=20
> 8.2.1	SIP compression
>=20
> The P-CSCF shall support SigComp as specified in RFC 3320=20
> [32]. When using SigComp the P-CSCF shall send compressed SIP=20
> messages in accordance with RFC 3486 [55]. When the P-CSCF=20
> will create the compartment is implementation specific, but=20
> the compartment shall not be created until a set of security=20
> associations are set up. The compartment shall finish when=20
> the UE is deregistered. State creations and announcements=20
> shall be allowed only for messages received in a security association.
>=20
> The P-CSCF shall support the SIP dictionary specified in RFC=20
> 3485 [42]. If compression is enabled, the P-CSCF shall use=20
> the dictionary to compress the first message.
>=20
> NOTE:	Exchange of bytecodes during registration will prevent=20
> unnecessary delays during session setup.
>=20
> Editor's note: 	The draft-ietf-rohc-sigcomp-sip-01 [79]=20
> can lead to the need for additional changes or clarifications.
>=20
> The following apply when signalling compression is used:
>=20
> -	State Memory Size (SMS) greater than zero is needed to=20
> give room for the UDVM byte code and make dynamic compression=20
> possible. A State Memory Size of at least 4096 bytes shall be=20
> a minimum value; and
>=20
> -	A Decompression Memory Size (DMS) of at least 8192=20
> bytes should be a minimum value.
>=20
> 8.2.2	Compression of SIP requests and responses transmitted to the UE
>=20
> The P-CSCF should compress the requests and responses=20
> transmitted to the UE according to subclause 8.2.1.
>=20
> NOTE:	Compression of SIP messages is an implementation=20
> option. However, compression is strongly recommended.
>=20
> 8.2.3	Decompression of SIP requests and responses received from the UE
>=20
> The P-CSCF shall decompress the compressed requests and=20
> responses received from the UE according to subclause 8.2.1.
>=20
> If the P-CSCF detects a decompression failure at the UE, the=20
> recovery mechanism is implementation specific and this may,=20
> as an example, include resetting the compartment, changing=20
> the algorithm.
>=20
>=20
> > -----Original Message-----
> > From: rohc-bounces@ietf.org=20
> [mailto:rohc-bounces@ietf.org]On Behalf Of
> > Paulius.Meskauskas@nokia.com
> > Sent: 14 December 2004 09:11
> > To: cabo@tzi.org; abigail.surtees@ROKE.CO.UK
> > Cc: mark.a.west@ROKE.CO.UK; rohc@ietf.org; zhigang.c.liu@nokia.com;
> > lwc@ROKE.CO.UK
> > Subject: RE: [rohc] Re: multiplexing SigComp and non-SigComp=20
> > messages on
> > t hesame TCP connection
> >=20
> >=20
> > hello,
> >=20
> > OMA PoC mandates the usage of SigComp and in case IMS core
> > is used - the compression must take place between UE and P-CSCF.
> >=20
> > IMHO there's no need for 'uncompressed SigComp header' in order
> > to keep SigComp generic and allow the multiplexing.. The main thing=20
> > is to break the SigComp dependency to the transport layer in=20
> > the implementation=20
> > i.e. text-based protocols know their delimiters and SigComp=20
> > knows its own.=20
> >=20
> > cheers,
> > 	paulius
> >=20
> >=20
> > > -----Original Message-----
> > > From: rohc-bounces@ietf.org=20
> > [mailto:rohc-bounces@ietf.org]On Behalf Of
> > > ext Carsten Bormann
> > > Sent: Tuesday, November 16, 2004 5:31 PM
> > > To: Surtees, Abigail
> > > Cc: West, Mark; Sugar Robert (Nokia-NET/Budapest); Liu Zhigang.C
> > > (Nokia-NRC/Dallas); rohc@ietf.org; Conroy, Lawrence=20
> (SMTP); Carsten
> > > Bormann
> > > Subject: Re: [rohc] Re: multiplexing SigComp and non-SigComp=20
> > > messages on
> > > t hesame TCP connection
> > >=20
> > >=20
> > > Abbie,
> > >=20
> > > 3GPP submission S2-043577 says:
> > >=20
> > > > For TCP, none of the existing standards mandates whether or not=20
> > > > endpoints must be able to multiplex SIP and SigComp=20
> > messages on the=20
> > > > same TCP connection however, the IETF currently see no need to=20
> > > > multiplex and would like to mandate that it must not be=20
> > > done. We note=20
> > > > that with the IMS security architecture there are some=20
> > constraints=20
> > > > with regards to the usage of ports on the P-CSCF and the=20
> > UE. During=20
> > > > the establishment of the IPSec security association the=20
> > UE and the=20
> > > > P-CSCF negotiate 2 ports on each side. These ports are=20
> > used as the=20
> > > > selector for the corresponding security association and are=20
> > > fixed for=20
> > > > the duration of the security association. Consequently, if=20
> > > there is a=20
> > > > need to send both SIP and SigComp messages over TCP, they=20
> > > would have=20
> > > > to be on the same connection.
> > > >
> > > > It seems, however, that the issue is not a real issue for=20
> > > IMS and PoC,=20
> > > > as it is mandated that terminals and networks will=20
> > support SigComp=20
> > > > (though its use is not mandatory). Consequently a terminal=20
> > > can decide=20
> > > > on the first message whether or not it is going to use=20
> > > SigComp and not=20
> > > > change. In this case, if there is a need to send an=20
> uncompressed=20
> > > > message (e.g. due to loss of sync between compressor and=20
> > > decompressor,=20
> > > > or to reduce processing load) when SigComp is in use, the=20
> > > > 'uncompressed SigComp header' can be used. This is a set=20
> > of 13 well=20
> > > > known bytes that are prepended to the SIP message to make=20
> > > it a SigComp=20
> > > > message and are removed as a block at the decompressor.
> > >=20
> > > This fits pretty well with what was said in the San Diego=20
> > WG meeting=20
> > > and hallway discussions, and this is what was intended by=20
> > my slide in=20
> > > Washington.
> > >=20
> > > (Sorry if I'm incoherent -- I'm wrestling with my usual post-IETF=20
> > > aircon-induced fever.)
> > >=20
> > > Gruesse, Carsten
> > >=20
> > >=20
> > > _______________________________________________
> > > Rohc mailing list
> > > Rohc@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/rohc
> > >=20
> >=20
> > _______________________________________________
> > Rohc mailing list
> > Rohc@ietf.org
> > https://www1.ietf.org/mailman/listinfo/rohc
> >=20
>=20

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


From rohc-bounces@ietf.org  Wed Dec 15 04:46:11 2004
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 EAA16278
	for <rohc-web-archive@ietf.org>; Wed, 15 Dec 2004 04:46:10 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeVrm-0000HK-00
	for rohc-web-archive@ietf.org; Wed, 15 Dec 2004 04:54:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeVfr-00067y-5F; Wed, 15 Dec 2004 04:42:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeVV8-0004Kb-QZ
	for rohc@megatron.ietf.org; Wed, 15 Dec 2004 04:31:19 -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 EAA15058
	for <rohc@ietf.org>; Wed, 15 Dec 2004 04:31:15 -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 1CeVdK-0008J8-3Y
	for rohc@ietf.org; Wed, 15 Dec 2004 04:39:46 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iBF9V79L008542; Wed, 15 Dec 2004 10:31:08 +0100 (MET)
In-Reply-To: <62F243FC21653C40A45B8C54FB0D4618415C4B@esebe052.ntc.nokia.com>
References: <62F243FC21653C40A45B8C54FB0D4618415C4B@esebe052.ntc.nokia.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <0EC79268-4E7C-11D9-A805-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] Re: multiplexing SigComp and non-SigComp messages on t
	hesame TCP connection
Date: Wed, 15 Dec 2004 10:31:11 +0100
To: <Paulius.Meskauskas@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: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit
Cc: abigail.surtees@ROKE.CO.UK, Carsten Bormann <cabo@tzi.org>, rohc@ietf.org,
        georg.mayer@nokia.com, drage@lucent.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: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit

> thank you for the information. However, I want to point
> out that if the statement about the multiplexing in 
> draft-ietf-rohc-sigcomp-sip-01
> is the final one- it will cause unnecessary changes in the 
> implementations
> already supporting multiplexing (and will break backwards 
> compatibility).
> That's why I think that multiplexing should be allowed without any
> extra 'uncompressed SigComp headers".

Paulius,

this is surprising.
RFC3320 is quite clear about the way a stream-based (TCP) connection 
works: messages are delimited by the record marking scheme (section 
4.2.2).

The proposal that later came up to mix this SigComp framing with SIP 
framing on one connection has received nearly unanimous rejection by 
SIP implementers.
We have discussed this on the mailing list for a long time and, despite 
some vocal support for this, in each round this was generally seen as 
the wrong way to do this.

SigComp shim headers are a standard-conforming way to multiplex 
compressed and uncompressed messages on one SigComp TCP connection that 
is interoperable today.
I'd like to hear a good reason why we need something else that is not 
compatible with the SigComp architecture.

(An extension that would be compatible would be to allow uncompressed 
messages in the second and following records in the SigComp TCP record 
marking syntax.
[You can allow uncompressed messages in the first message only if you 
don't need to differentiate between SIP and SigComp connections.]
This is trivial to implement, but still an extension.  Again, I'd like 
to hear arguments why you need to save those 13 bytes.)

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Wed Dec 15 05:30:56 2004
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 FAA18553
	for <rohc-web-archive@ietf.org>; Wed, 15 Dec 2004 05:30:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeWZ6-0001Gm-I6
	for rohc-web-archive@ietf.org; Wed, 15 Dec 2004 05:39:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeWP3-0005UN-DP; Wed, 15 Dec 2004 05:29:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeWMf-0004z4-Si
	for rohc@megatron.ietf.org; Wed, 15 Dec 2004 05:26:37 -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 FAA18318
	for <rohc@ietf.org>; Wed, 15 Dec 2004 05:26:35 -0500 (EST)
From: Paulius.Meskauskas@nokia.com
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeWUs-0001AU-4x
	for rohc@ietf.org; Wed, 15 Dec 2004 05:35:06 -0500
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iBFAQMK15129; Wed, 15 Dec 2004 12:26:23 +0200 (EET)
X-Scanned: Wed, 15 Dec 2004 12:31:14 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks001.ntc.nokia.com (8.12.9/8.12.9) id iBFAVDPd014220;
	Wed, 15 Dec 2004 12:31:14 +0200
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks001.ntc.nokia.com 00dpuLyW; Wed, 15 Dec 2004 12:31:04 EET
Received: from esebh004.NOE.Nokia.com (esebh004.ntc.nokia.com [172.21.138.84])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iBFAPm315508; Wed, 15 Dec 2004 12:25:48 +0200 (EET)
Received: from esebe009.NOE.Nokia.com ([172.21.138.41]) by
	esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 15 Dec 2004 12:24:55 +0200
Received: from esebe052.NOE.Nokia.com ([172.21.138.217]) by
	esebe009.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 15 Dec 2004 12:24:55 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] Re: multiplexing SigComp and non-SigComp messages on t
	hesame TCP connection
Date: Wed, 15 Dec 2004 12:24:54 +0200
Message-ID: <62F243FC21653C40A45B8C54FB0D4618415C4F@esebe052.ntc.nokia.com>
Thread-Topic: [rohc] Re: multiplexing SigComp and non-SigComp messages on t
	hesame TCP connection
Thread-Index: AcTiiV8ZuvTa23quT8SlBnQ0CXdCXQAASd7A
To: <cabo@tzi.org>
X-OriginalArrivalTime: 15 Dec 2004 10:24:55.0813 (UTC)
	FILETIME=[525BC350:01C4E290]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: quoted-printable
Cc: abigail.surtees@ROKE.CO.UK, rohc@ietf.org, georg.mayer@nokia.com,
        drage@lucent.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.3 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: quoted-printable

hello,

inline:

>
>=20
> The proposal that later came up to mix this SigComp framing with SIP=20
> framing on one connection has received nearly unanimous rejection by=20
> SIP implementers.
> We have discussed this on the mailing list for a long time=20
> and, despite=20
> some vocal support for this, in each round this was generally seen as=20
> the wrong way to do this.

Yes, I know that I'm late with my comments but I just want
to clarify things.


>=20
> SigComp shim headers are a standard-conforming way to multiplex=20
> compressed and uncompressed messages on one SigComp TCP=20
> connection that=20
> is interoperable today.
> I'd like to hear a good reason why we need something else that is not=20
> compatible with the SigComp architecture.

Why it is not compatible with SigComp architecture? I interpreted
RFC3320 in such a way that you mark only compressed messages with
SigComp delimeters. (chapter 4.2.2).
I'd say that TCP connection is for SIP and it just uses SigComp
for compression/decompression services and therefore SIP
does not need to add SigComp delimeter is case it must send
SIP message uncompressed.

IMHO the problem if implementations follow the architecture depicted=20
in the Figure 1 in RFC3320- in this case the usage
of SigComp header for uncompressed message is intelligible
i.e. the "SigComp TCP connection" for keeping SigComp-layer generic.


danke,
	paulius



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


From rohc-bounces@ietf.org  Wed Dec 15 06:39:55 2004
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 GAA22142
	for <rohc-web-archive@ietf.org>; Wed, 15 Dec 2004 06:39:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeXds-0002ld-7I
	for rohc-web-archive@ietf.org; Wed, 15 Dec 2004 06:48:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeXUz-0001tE-Hi; Wed, 15 Dec 2004 06:39:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeXNU-0000eT-4f
	for rohc@megatron.ietf.org; Wed, 15 Dec 2004 06:31:32 -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 GAA21567
	for <rohc@ietf.org>; Wed, 15 Dec 2004 06:31:28 -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 1CeXVX-0002Yl-B4
	for rohc@ietf.org; Wed, 15 Dec 2004 06:40:01 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iBFBVBi3024943; Wed, 15 Dec 2004 12:31:13 +0100 (MET)
In-Reply-To: <62F243FC21653C40A45B8C54FB0D4618415C4F@esebe052.ntc.nokia.com>
References: <62F243FC21653C40A45B8C54FB0D4618415C4F@esebe052.ntc.nokia.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <D584EB02-4E8C-11D9-A805-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] Re: multiplexing SigComp and non-SigComp messages on t
	hesame TCP connection
Date: Wed, 15 Dec 2004 12:31:16 +0100
To: Paulius.Meskauskas@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: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: 7bit
Cc: rohc@ietf.org, abigail.surtees@ROKE.CO.UK, Carsten Bormann <cabo@tzi.org>,
        drage@lucent.com, georg.mayer@nokia.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: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: 7bit

> Why it is not compatible with SigComp architecture? I interpreted
> RFC3320 in such a way that you mark only compressed messages with
> SigComp delimeters. (chapter 4.2.2).

That's not what 4.2.2 says, it says:

    For a stream-based transport, the dispatcher delimits messages by
    parsing the compressed data stream for instances of 0xFF and taking
    the following actions:

Of course, the assumption at the time was that you would decide wether 
a data stream is compressed or not at the outset (either by just 
declaring it compressed, e.g., by using a separate port, or from the 
first byte of the TCP connection).

> I'd say that TCP connection is for SIP and it just uses SigComp
> for compression/decompression services and therefore SIP
> does not need to add SigComp delimeter is case it must send
> SIP message uncompressed.

Again, that's not what it says.  When TCP (or any other stream 
protocol) is used, it is used for the "compressed data stream".
You have to apply 4.2.2 before you have messages.

The text in 3.1 is unfortunate in that it talks about "multiplexing 
messages" (we were mainly concerning ourselves with UDP at the time).
But even if you take it for face value, you need 4.2.2 before you have 
"messages" on a compressed stream.
(Taking it for face value would mean that the "extension" referred to 
in my previous message is already foreseen by RFC3320.
I don't think so, but I don't have a hard position on this, and I 
actually think it would be a good way to handle the problem, once I 
understand what the problem is.)

> IMHO the problem if implementations follow the architecture depicted
> in the Figure 1 in RFC3320- in this case the usage
> of SigComp header for uncompressed message is intelligible
> i.e. the "SigComp TCP connection" for keeping SigComp-layer generic.

Figure 1 is pretty much an illustrative figure, it can't tell the whole 
picture.
4.2.2 clearly says it is the dispatcher that parses the data stream.

The main point in the architecture is that SigComp handles the 
transport interface.
It cannot do this if it has to apply both SIP message parsing rules and 
SigComp message parsing rules -- then the SIP implementation comes in 
in a way that implementors did *not* like.

So in summary:

1) Mixing SIP message parsing and SigComp record marking in one 
connection: bad.

2) Mixing uncompressed and compressed messages in a SigComp record 
marked stream: good, but not necessarily already required by the 
standard.

3) Mixing compressed and uncompressed messages in a SigComp record 
marked stream by sending the latter with a SigComp shim header: 
standard, interoperable now.

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Wed Dec 15 08:18:34 2004
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 IAA29282
	for <rohc-web-archive@ietf.org>; Wed, 15 Dec 2004 08:18:33 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeZBK-0005OA-2T
	for rohc-web-archive@ietf.org; Wed, 15 Dec 2004 08:27:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeYyb-0006G3-PM; Wed, 15 Dec 2004 08:13:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeYue-00055L-1x
	for rohc@megatron.ietf.org; Wed, 15 Dec 2004 08:09:52 -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 IAA28699
	for <rohc@ietf.org>; Wed, 15 Dec 2004 08:09:50 -0500 (EST)
From: Paulius.Meskauskas@nokia.com
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeZ2s-0005Bj-68
	for rohc@ietf.org; Wed, 15 Dec 2004 08:18:22 -0500
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iBFD9YD06497; Wed, 15 Dec 2004 15:09:35 +0200 (EET)
X-Scanned: Wed, 15 Dec 2004 15:07:52 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks001.ntc.nokia.com (8.12.9/8.12.9) id iBFD7qng005212;
	Wed, 15 Dec 2004 15:07:52 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks001.ntc.nokia.com 00ADclK3; Wed, 15 Dec 2004 15:07:51 EET
Received: from esebh001.NOE.Nokia.com (esebh001.ntc.nokia.com [172.21.138.28])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iBFD2XD15546; Wed, 15 Dec 2004 15:02:33 +0200 (EET)
Received: from esebe018.NOE.Nokia.com ([172.21.138.57]) by
	esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 15 Dec 2004 15:01:34 +0200
Received: from esebe052.NOE.Nokia.com ([172.21.138.217]) by
	esebe018.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 15 Dec 2004 15:01:32 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] Re: multiplexing SigComp and non-SigComp messages on t
	hesame TCP connection
Date: Wed, 15 Dec 2004 15:01:32 +0200
Message-ID: <62F243FC21653C40A45B8C54FB0D4618415C57@esebe052.ntc.nokia.com>
Thread-Topic: [rohc] Re: multiplexing SigComp and non-SigComp messages on t
	hesame TCP connection
Thread-Index: AcTimo6JK09VhJOxTLWmd4vjPu5tNQABIlig
To: <cabo@tzi.org>
X-OriginalArrivalTime: 15 Dec 2004 13:01:32.0806 (UTC)
	FILETIME=[33671A60:01C4E2A6]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: quoted-printable
Cc: rohc@ietf.org, abigail.surtees@ROKE.CO.UK, drage@lucent.com,
        georg.mayer@nokia.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.3 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: quoted-printable

> Figure 1 is pretty much an illustrative figure, it can't tell=20
> the whole=20
> picture.
> 4.2.2 clearly says it is the dispatcher that parses the data stream.
>=20
> The main point in the architecture is that SigComp handles the=20
> transport interface.
> It cannot do this if it has to apply both SIP message parsing=20
> rules and=20
> SigComp message parsing rules -- then the SIP implementation comes in=20
> in a way that implementors did *not* like.

So RFC3320 actually mandates that SigComp handles tranport-layer?
If SIP handles the transport layer (as it normally does) and uses=20
SigComp just for compression/decompression - mixing in the same TCP
connection is not the problem, because SIP knows its delimeters and =
SigComp
knows its own. When SIP reads the stream and encounters SigComp magic =
bits
it just passes the message to the SigComp. SIP (or whatever text based
protocol) does not have to know the SigComp magic bits but is sure knows =
that
the message can be compressed since it wanted compression to take place.
And SIP anyway must implement compartment handling logic etc...=20
This is an alternative way how to implement it without the need to =
involve
the SigComp in case the compression must not take place.



I do agree that if RFC3320 architecture is followed in the =
implementation
the 3) is the best way to go.=20

regards,
	paulius


>=20
> So in summary:
>=20
> 1) Mixing SIP message parsing and SigComp record marking in one=20
> connection: bad.
>=20
> 2) Mixing uncompressed and compressed messages in a SigComp record=20
> marked stream: good, but not necessarily already required by the=20
> standard.
>=20
> 3) Mixing compressed and uncompressed messages in a SigComp record=20
> marked stream by sending the latter with a SigComp shim header:=20
> standard, interoperable now.

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


From rohc-bounces@ietf.org  Wed Dec 15 13:07:56 2004
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 NAA23752
	for <rohc-web-archive@ietf.org>; Wed, 15 Dec 2004 13:07:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CedhQ-00054n-2U
	for rohc-web-archive@ietf.org; Wed, 15 Dec 2004 13:16:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CedF8-0004zZ-PF; Wed, 15 Dec 2004 12:47:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ced7r-0000Qq-NG
	for rohc@megatron.ietf.org; Wed, 15 Dec 2004 12:39:47 -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 MAA20055
	for <rohc@ietf.org>; Wed, 15 Dec 2004 12:39:44 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CedG8-0003jH-1U
	for rohc@ietf.org; Wed, 15 Dec 2004 12:48:20 -0500
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iBFHdWK20529; Wed, 15 Dec 2004 19:39:33 +0200 (EET)
X-Scanned: Wed, 15 Dec 2004 19:39:27 +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 iBFHdRJo032596;
	Wed, 15 Dec 2004 19:39:27 +0200
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks002.ntc.nokia.com 00fpcFPh; Wed, 15 Dec 2004 19:39:25 EET
Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com
	[10.241.35.122])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iBFHdO317096; Wed, 15 Dec 2004 19:39:24 +0200 (EET)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by
	daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 15 Dec 2004 11:39:07 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] Re: multiplexing SigComp and non-SigComp messages on
	thesame TCP connection
Date: Wed, 15 Dec 2004 12:39:05 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B82891E3@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] Re: multiplexing SigComp and non-SigComp messages on
	thesame TCP connection
Thread-Index: AcTii0QsX5RMKRPiRsypH570GiESqAAO6CNg
To: <cabo@tzi.org>, <Paulius.Meskauskas@nokia.com>
X-OriginalArrivalTime: 15 Dec 2004 17:39:07.0164 (UTC)
	FILETIME=[FA2C75C0:01C4E2CC]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: quoted-printable
Cc: abigail.surtees@ROKE.CO.UK, rohc@ietf.org, georg.mayer@nokia.com,
        drage@lucent.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.3 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: quoted-printable

> [You can allow uncompressed messages in the first message only if you=20
> don't need to differentiate between SIP and SigComp connections.]
> This is trivial to implement, but still an extension.  Again,=20
> I'd like to hear arguments why you need to save those 13 bytes.)

(I've been keeping silence since the Carsten holds the editing
baton of sigcomp-sip-02. Thought somehow not good to make noise=20
before it comes out. But this caught my eyes ...)

IMO, I don't think saving 13 bytes is worth the extension. But
does the extension allow a sender to send non-SigComp message
(i.e. plain SIP) and later "switch on" SigComp on the same TCP
connection? If yes, I think it's a good to have.=20

The reason (which I've raised earlier) is that a sender=20
may not know whether a receiver supports SigComp or not when
sending the first SIP message (e.g. request). So it has to send
the first message as is. Later (e.g. after receiving a response
to the request), it may discover the receiver actually supports=20
SigComp. In that case, it would be good that the sender can
send the second and subsequent SIP messages using SigComp on
the same TCP connection already opened.

Of course, this is needed only if both of following are true:
1) SigComp support is not mandatory. (It is in 3GPP, but do we
expect it's always the case in general?)
2) The sender wants to reuse the same TCP connection. (Of
course, the sender may open a second TCP connection. But
there are benefits to reuse TCP connections.)

BR, Zhigang


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


From osjdwcytvyf@msn.com  Thu Dec 16 01:23:19 2004
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 BAA10285
	for <rohc-web-archive@ietf.org>; Thu, 16 Dec 2004 01:23:19 -0500 (EST)
Received: from [62.102.247.191] (helo=132.151.6.1)
	by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1CepB1-00087s-Cd
	for rohc-web-archive@ietf.org; Thu, 16 Dec 2004 01:32:00 -0500
Received: from circumcircle [172.248.204.120] (helo=boomerang.tough.dearriba.com)
	by smtp2.cistron.nl with esmtp (bronze 3.35 #1 (belying))
	id 402LFL-0075PT-82
Message-ID: <81237723144732.R37448@craw.noc.donaldson.gr>
Sender: freeradius-devel-osjdwcytvyf@msn.com
X-Mailman-Version: 2.0.1
Date: Thu, 16 Dec 2004 01:17:48 -0500
From: "Sammie Kaplan" <osjdwcytvyf@msn.com>
To: rohc-web-archive@ietf.org
Subject:  Message subject
X-Spam-Score: 3.3 (+++)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32


The L0west price of all med's is here. 

 Viicodin	- $199.95
 Tylenol 	- $189.95
 V1a'gra 	- $199.95 
 Va|ium 	- $259.95 
 Cia|is 	- $189.95 
 Xa'nax 	- $233.95
and many m0reeee.....

We are the bes't available nowadays

http://www.ohwyohwhy.com/2/vicodin.php?wid=200007









This is 1 tiime maillling. N0-removalll are requiired
XPbaWEQpXbXtIXteYMP4cxWU5sJRiOZQccD2aFmYWW7zDVc98Ux


From rohc-bounces@ietf.org  Thu Dec 16 13:22:11 2004
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 NAA20598
	for <rohc-web-archive@ietf.org>; Thu, 16 Dec 2004 13:22:11 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cf0Ox-0002X8-G9
	for rohc-web-archive@ietf.org; Thu, 16 Dec 2004 13:31:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cf0Cs-0006wc-0J; Thu, 16 Dec 2004 13:18:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cf01s-0003a8-G8
	for rohc@megatron.ietf.org; Thu, 16 Dec 2004 13:07:08 -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 NAA19318
	for <rohc@ietf.org>; Thu, 16 Dec 2004 13:07:05 -0500 (EST)
From: lists@nirendra.net
Received: from u15156313.onlinehome-server.com ([217.160.252.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cf0AL-00022U-8S
	for rohc@ietf.org; Thu, 16 Dec 2004 13:15:54 -0500
Received: (qmail 19925 invoked from network); 16 Dec 2004 18:07:06 -0000
Received: from localhost (127.0.0.1)
	by localhost with SMTP; 16 Dec 2004 18:07:06 -0000
Received: from 61.246.177.131 ([61.246.177.131]) 
	by webmail.nirendra.net (IMP) with HTTP 
	for <lists@nirendra.net@localhost>; Thu, 16 Dec 2004 13:07:06 -0500
Message-ID: <1103220426.41c1ceca76637@webmail.nirendra.net>
Date: Thu, 16 Dec 2004 13:07:06 -0500
To: rohc@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.2
X-Originating-IP: 61.246.177.131
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 8bit
Subject: [rohc] Problem in decompressing message compressed with zlib
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: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 8bit

Dear All,

Whether the deflate bytecode mentioned in document 
http://mirrors.isc.org/pub/www.watersprings.org/pub/id/draft-price-rohc-sigcomp-user-guide-01.txt
is compatible with all versions of zlib including 1.1.3 and 1.2.1

Also, are there any changes in zlib's compression algorithm in newer version of
library.

Waiting for a response,

Thanks in advance.

Nirendra



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


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


From rohc-bounces@ietf.org  Fri Dec 17 00:15:16 2004
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 AAA24191
	for <rohc-web-archive@ietf.org>; Fri, 17 Dec 2004 00:15:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CfAb5-0007U9-66
	for rohc-web-archive@ietf.org; Fri, 17 Dec 2004 00:24:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfAR8-0005DK-QN; Fri, 17 Dec 2004 00:13:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfAL0-0003XV-4b
	for rohc@megatron.ietf.org; Fri, 17 Dec 2004 00:07:34 -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 AAA23781
	for <rohc@ietf.org>; Fri, 17 Dec 2004 00:07:30 -0500 (EST)
Received: from bay2-f16.bay2.hotmail.com ([65.54.247.16] helo=hotmail.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfATX-0007FN-Ux
	for rohc@ietf.org; Fri, 17 Dec 2004 00:16:25 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Thu, 16 Dec 2004 21:07:00 -0800
Message-ID: <BAY2-F1612E4D49BA990322322C3A9AF0@phx.gbl>
Received: from 61.11.57.63 by by2fd.bay2.hotmail.msn.com with HTTP;
	Fri, 17 Dec 2004 05:06:07 GMT
X-Originating-IP: [61.11.57.63]
X-Originating-Email: [basudeb@hotmail.com]
X-Sender: basudeb@hotmail.com
In-Reply-To: <1103220426.41c1ceca76637@webmail.nirendra.net>
From: "Basudeb Gupta" <basudeb@hotmail.com>
To: lists@nirendra.net, rohc@ietf.org
Subject: RE: [rohc] Problem in decompressing message compressed with zlib
Date: Fri, 17 Dec 2004 10:36:07 +0530
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
X-OriginalArrivalTime: 17 Dec 2004 05:07:00.0589 (UTC)
	FILETIME=[3D7711D0:01C4E3F6]
X-Spam-Score: 2.0 (++)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
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: 2.0 (++)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64

Hi Nirendra,

We have come to know that Zlib 1.2.2  will be compatible with the bytecode 
if you build it using FORCE-STATIC option defined.

This was conveyed by  Adler himself. It seems to work in the limited tests 
that we have done so far.

Hope it helps.

Basudeb

>From: lists@nirendra.net
>To: rohc@ietf.org
>Subject: [rohc] Problem in decompressing message compressed with zlib
>Date: Thu, 16 Dec 2004 13:07:06 -0500
>
>Dear All,
>
>Whether the deflate bytecode mentioned in document
>http://mirrors.isc.org/pub/www.watersprings.org/pub/id/draft-price-rohc-sigcomp-user-guide-01.txt
>is compatible with all versions of zlib including 1.1.3 and 1.2.1
>
>Also, are there any changes in zlib's compression algorithm in newer 
>version of
>library.
>
>Waiting for a response,
>
>Thanks in advance.
>
>Nirendra
>
>
>
>----------------------------------------------------------------
>This message was sent using IMP, the Internet Messaging Program.
>
>
>_______________________________________________
>Rohc mailing list
>Rohc@ietf.org
>https://www1.ietf.org/mailman/listinfo/rohc

_________________________________________________________________
Chat with 1000s of singles.  
http://www.bharatmatrimony.com/cgi-bin/bmclicks1.cgi?74 Let 
BharatMatrimony.com's Instant Messenger show you how.


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


From rohc-bounces@ietf.org  Fri Dec 17 06:53:57 2004
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 GAA08887
	for <rohc-web-archive@ietf.org>; Fri, 17 Dec 2004 06:53:57 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CfGow-0001b6-Up
	for rohc-web-archive@ietf.org; Fri, 17 Dec 2004 07:02:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfGWv-0008Qu-TC; Fri, 17 Dec 2004 06:44:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfGUJ-0006z7-7S
	for rohc@megatron.ietf.org; Fri, 17 Dec 2004 06:41:35 -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 GAA07723
	for <rohc@ietf.org>; Fri, 17 Dec 2004 06:41:32 -0500 (EST)
Received: from bay21-f6.bay21.hotmail.com ([65.54.233.95] helo=hotmail.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfGcv-0001Bc-1p
	for rohc@ietf.org; Fri, 17 Dec 2004 06:50:30 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Fri, 17 Dec 2004 03:41:00 -0800
Message-ID: <BAY21-F6421C943D6E312D17655685AF0@phx.gbl>
Received: from 194.218.191.2 by by21fd.bay21.hotmail.msn.com with HTTP;
	Fri, 17 Dec 2004 11:40:49 GMT
X-Originating-IP: [194.218.191.2]
X-Originating-Email: [gustav_kung@hotmail.com]
X-Sender: gustav_kung@hotmail.com
From: "Gustav E" <gustav_kung@hotmail.com>
To: rohc@ietf.org
Date: Fri, 17 Dec 2004 12:40:49 +0100
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
X-OriginalArrivalTime: 17 Dec 2004 11:41:00.0716 (UTC)
	FILETIME=[48142EC0:01C4E42D]
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Subject: [rohc] [SigComp]Shared mode and some other SigComp-state related
	stuff.
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.8 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002

Hi all.

Since I'm fairly new to this list and SigComp in general, I have a few 
questions:
1. Regarding Shared mode: What became the consensus of the previous 
discussions on the list? Is the general somewhat simplified recommendation  
to only "allow" a compressor to create one shared-state?
2. State memory: If  compressor A for any reason creates a local state, 
valid only in one compartment, should the size of that local state be 
considerad to use any of the available State memory in A? I'm guessing that 
it should, simply writing the question to be assured.
3. USD. I fully understand the usage of a USD. However, I do not understand 
if a USD-state should be treated any differenty then any other state created 
at the remote end. Is a USD per definition a shared state? I'm guessing that 
it must be if the sending compressor is to have any advantage of the 
USD-state at the remote end. Then, again, should the USD-state (local state) 
at A be considered to occupy State-memory? Should it be considered any 
differently then any other shared state?
4. General shared-state issue: 3321 states that shared-state is an 
uncompressed message. Is the recommendation to only use complet uncompressed 
messages as shared state? What about parts of messages or even other 
textual-protocol-specific data?
5. (Little bit off-topic, PoC specific question): In the PoC NEMS Signalling 
Spec. "Signalling flows (UNI) v2.06", a procedure for establishing a USD is 
described. Among others it states that the four first bytes of the 
state-value should be "usd1". Can any helpful individual explain to me what 
the purpose might be? Should either local or remote endpoint take any 
specific action here?
The spec says:
"For USD identification it is important that the identifier string is placed 
in the beginning of the state_value of the USD, therefore special attention 
must be paid in the case of large USD as the UDVM has a circular buffer."
I do not understand the purpose here..

Appologies for all these questions. Simply hoping to get some sort of 
clarifications here.

Best Regards,
/Gustav E

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/


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


From rohc-bounces@ietf.org  Fri Dec 17 16:49:20 2004
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 QAA15400
	for <rohc-web-archive@ietf.org>; Fri, 17 Dec 2004 16:49:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CfQ71-0007HC-ET
	for rohc-web-archive@ietf.org; Fri, 17 Dec 2004 16:58:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfPeW-0000Zc-U9; Fri, 17 Dec 2004 16:28:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfPF3-0007Mj-Lr
	for rohc@megatron.ietf.org; Fri, 17 Dec 2004 16:02:25 -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 QAA05944
	for <rohc@ietf.org>; Fri, 17 Dec 2004 16:02:23 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfPNb-00044p-D1
	for rohc@ietf.org; Fri, 17 Dec 2004 16:11:26 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBHL29vD006418
	for <rohc@ietf.org>; Fri, 17 Dec 2004 22:02:09 +0100 (MET)
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 17 Dec 2004 22:02:07 +0100
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <YDR25VKZ>; Fri, 17 Dec 2004 22:02:07 +0100
Message-ID: <F005CD411D18D3119C8F00508B0874800DC40544@ehubunt100.eth.ericsson.se>
From: "Lajos Zaccomer (IJ/ETH)" <lajos.zaccomer@ericsson.com>
To: "'Gustav E'" <gustav_kung@hotmail.com>, rohc@ietf.org
Subject: RE: [rohc] [SigComp]Shared mode and some other SigComp-state rela
	ted stuff.
Date: Fri, 17 Dec 2004 22:02:05 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 17 Dec 2004 21:02:07.0763 (UTC)
	FILETIME=[AB33DE30:01C4E47B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
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: 057ebe9b96adec30a7efb2aeda4c26a4

Hi,

See the answers inline ...

br/Zacco

> -----Original Message-----
> From: rohc-bounces@ietf.org [mailto:rohc-bounces@ietf.org]On 
> Behalf Of Gustav E
> Sent: Friday, December 17, 2004 12:41 PM
> To: rohc@ietf.org
> Subject: [rohc] [SigComp]Shared mode and some other 
> SigComp-state related stuff.
> 
> 
> Hi all.
> 
> Since I'm fairly new to this list and SigComp in general, I 
> have a few 
> questions:
> 1. Regarding Shared mode: What became the consensus of the previous 
> discussions on the list? Is the general somewhat simplified 
> recommendation  
> to only "allow" a compressor to create one shared-state?

See the latest implementor's guide.

> 2. State memory: If  compressor A for any reason creates a 
> local state, 
> valid only in one compartment, should the size of that local state be 
> considerad to use any of the available State memory in A? I'm 
> guessing that 
> it should, simply writing the question to be assured.

Yes, it definitely should.

> 3. USD. I fully understand the usage of a USD. However, I do 
> not understand 
> if a USD-state should be treated any differenty then any 
> other state created 
> at the remote end. Is a USD per definition a shared state? 

No, it isn't. RFC 3321 says it's a regular state. POC USD is something different. I would say it's a regular and a shared state at the same time.

> I'm guessing that 
> it must be if the sending compressor is to have any advantage of the 
> USD-state at the remote end. Then, again, should the 
> USD-state (local state) 
> at A be considered to occupy State-memory? Should it be 
> considered any 
> differently then any other shared state?

It depends on which USD you are talking about. A regular state is not saved in a state memory at the compressor side, so if you go for the RFC 3321 USD, it decreases the available memory at B in the state memory of compresssor at A. In case POC USD is used, it must be saved as a local state, otherwise the compressor at B would not be able to access it.

> 4. General shared-state issue: 3321 states that shared-state is an 
> uncompressed message. Is the recommendation to only use 
> complet uncompressed 
> messages as shared state? What about parts of messages or even other 
> textual-protocol-specific data?

By definition, it is the message itself, unless the state memory of A is known and is smaller than the size of the message + 64, in which case a truncated message will be the shared state.

> 5. (Little bit off-topic, PoC specific question): In the PoC 
> NEMS Signalling 
> Spec. "Signalling flows (UNI) v2.06", a procedure for 
> establishing a USD is 
> described. Among others it states that the four first bytes of the 
> state-value should be "usd1". Can any helpful individual 
> explain to me what 
> the purpose might be? Should either local or remote endpoint take any 
> specific action here?
> The spec says:
> "For USD identification it is important that the identifier 
> string is placed 
> in the beginning of the state_value of the USD, therefore 
> special attention 
> must be paid in the case of large USD as the UDVM has a 
> circular buffer."
> I do not understand the purpose here..

Suppose Endpoint 2 supports USD (without the optional requirement of moving it to the local state location) and the explicit acknowledgement specified in RFC 3321, too. If Endpoint 2 explicitlly acks the uploaded USD state ID, Endpoint 1 will think USD is moved to the local states location (indication is the same as if it was an explicit ack) and will not update (decrease) its remote available SMS. Later on it may result in decompression failure if a state is saved deleting another one in use, due to the remote available SMS out of synchron.

> 
> Appologies for all these questions. Simply hoping to get some sort of 
> clarifications here.
> 
> Best Regards,
> /Gustav E
> 
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today 
> it's FREE! 
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> 
> 
> _______________________________________________
> 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


From rohc-bounces@ietf.org  Mon Dec 20 05:00:01 2004
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 FAA15990
	for <rohc-web-archive@ietf.org>; Mon, 20 Dec 2004 05:00:01 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgKTw-00044R-PU
	for rohc-web-archive@ietf.org; Mon, 20 Dec 2004 05:09:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgKJZ-0007tz-4S; Mon, 20 Dec 2004 04:58:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgKHb-0007ga-4e
	for rohc@megatron.ietf.org; Mon, 20 Dec 2004 04:56:51 -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 EAA15849
	for <rohc@ietf.org>; Mon, 20 Dec 2004 04:56:48 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgKQp-0003zn-Jd
	for rohc@ietf.org; Mon, 20 Dec 2004 05:06:23 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <YHL6VY55>; Mon, 20 Dec 2004 09:58:17 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8803D5B19@rsys004a.roke.co.uk>
From: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
To: "'Lajos Zaccomer (IJ/ETH)'" <lajos.zaccomer@ericsson.com>,
        "'Gustav E'"
	<gustav_kung@hotmail.com>, rohc@ietf.org
Subject: RE: [rohc] [SigComp]Shared mode and some other SigComp-state rela
	ted stuff.
Date: Mon, 20 Dec 2004 09:58:18 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
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: 9182cfff02fae4f1b6e9349e01d62f32

Hi Gustav, Zacco,

> > Since I'm fairly new to this list and SigComp in general, I 
> > have a few 
> > questions:
> > 1. Regarding Shared mode: What became the consensus of the previous 
> > discussions on the list? Is the general somewhat simplified 
> > recommendation  
> > to only "allow" a compressor to create one shared-state?
> 
> See the latest implementor's guide.

The latest version of the implementer's guide is available at
<http://sigcomp.srmr.co.uk/~ahs/draft-ietf-rohc-sigcomp-impl-guide-04.txt>.
It has not been submitted yet and all comments are welcome.  I am intending
to submit it early in January.
 
Best regards,

Abbie

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


From rohc-bounces@ietf.org  Mon Dec 20 11:20:51 2004
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 LAA13576
	for <rohc-web-archive@ietf.org>; Mon, 20 Dec 2004 11:20:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgQQW-0004zv-MV
	for rohc-web-archive@ietf.org; Mon, 20 Dec 2004 11:30:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgQFT-0004M9-J1; Mon, 20 Dec 2004 11:19:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgQBq-0003ka-VC
	for rohc@megatron.ietf.org; Mon, 20 Dec 2004 11:15:19 -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 LAA12539
	for <rohc@ietf.org>; Mon, 20 Dec 2004 11:15:16 -0500 (EST)
Received: from mproxy.gmail.com ([216.239.56.251])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgQL8-0004iU-1w
	for rohc@ietf.org; Mon, 20 Dec 2004 11:24:55 -0500
Received: by mproxy.gmail.com with SMTP id q44so57709cwc
	for <rohc@ietf.org>; Mon, 20 Dec 2004 08:15:16 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=DM7IhskZbOyWNOmmzDuNDeq6zPLN9szu7Cdxk/ZuFEuZZKZtr1CNDt7ch1S1gRLHMCND29gQj4p524/x2jsL57q6ih8Vp5V1yHIKX8eRi1kPTiet1Mhqt1ANYtpF1ck1mfhMPeB90sUk8TkoNiyHdle94X9vs5DfLom9KmOxmZ4=
Received: by 10.11.116.77 with SMTP id o77mr208961cwc;
	Mon, 20 Dec 2004 08:15:16 -0800 (PST)
Received: by 10.11.99.49 with HTTP; Mon, 20 Dec 2004 08:15:16 -0800 (PST)
Message-ID: <db95d40c04122008155a0416fe@mail.gmail.com>
Date: Mon, 20 Dec 2004 16:15:16 +0000
From: Pedro Fortuna <pedro.fortuna@gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] Re: Review of draft-bormann-rohc-over-802-00.txt
In-Reply-To: <C7666E10-48EE-11D9-B3CF-000A95DC4DB6@tzi.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_Part_788_4470748.1103559316093"
References: <3F2E01E1D7B04F4EBEC92D3FA324D8803857FC@rsys004a.roke.co.uk>
	<550877E8-420B-11D9-82C1-000A95DC4DB6@tzi.org>
	<db95d40c0412071707b0c2e1b@mail.gmail.com>
	<C7666E10-48EE-11D9-B3CF-000A95DC4DB6@tzi.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f560cc438c8be83d0aa5c816c29b481c
Cc: "rohc@ietf.org" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Pedro Fortuna <pedro.fortuna@gmail.com>
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: dadeebe491e67c033a493fd3c7d6792b

------=_Part_788_4470748.1103559316093
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Hi Carsten,

Sorry for not answering sooner. I've read again my previous email, and
think I wasn't clear in some parts, and also I've found some errors
that might have led to some confusion. My fault! Anyway, you addressed
the issue I was trying to focus.

> So the AP will simply not have that choice.
This is what I was trying to say. No matter what encapsulation variant
is chosen, the solution will only work if the AP is forced to use the
chosen variant. This can only be achieved by changing in the embedded
software running on the AP's. My question is: can this be avoided in
any way?

Merry Christmas to all ROHCers :)

Best Regards,
Pedro Fortuna


====================================================
A revised and smaller version of my previous e-mail:
I've carefully read the draft but there is an issue regarding possible
changes in the software running in bridges that should be addressed.

To demonstrate my point, I provide a couple of example scenarios.
Let's say that we come to the conclusion that 802.3 LLC+SNAP
encapsulation is the best solution for addressing the padding problem
(I'm not trying to say that it is, I'm just using it as an example of
a possible solution).

Scenario 1 (See attached gif)
______                  ____________                   ______
|  PC1 |==802.3==|  802.3/802.11 |~~802.11~~|  PC2  |
|_____|                 | ___bridge____|                  |_____|

PC1 sends RoHC packets encapsulated with 802.3 LLC+SNAP. The packets
arrive to the bridge where padding, if any, is stripped by the bridge,
and then the RoHC payload is sent to PC2 with 802.11 Link Layer
encapsulation. This scenario works because we can make PC1 send frames
with the desired encapsulation. Also, changes to the embedded software
running in the bridge are not necessary.

Scenario 2 (See attached gif)
_____                   ___________                  ___________      
            _____
| PC1 |~~802.11~~| 802.11/802.3|==802.3==|802.3/802.11|~~802.11~~| PC2 |
|____|                   |___bridge___|                 |___bridge__| 
                 |____|

In this scenario, we have two PC's connected to 2 different AP's,
interconnected by a 802.3 link. In this scenario PC1 sends RoHC
packets with 802.11 Link Layer encapsulation. The packets arrive to
the bridge (with no padding), and at this point the bridge must choose
an Ethernet encapsulation type and add padding if necessary. The
problem is that, unless changes are made to the embedded software
running at the AP, it will always choose to use DIX Frames, thus
making it impossible for the second bridge to tell if the DIX Frames
carry padding or not, propagating the padding to the 802.11 link.



On Wed, 8 Dec 2004 08:57:16 +0100, Carsten Bormann <cabo@tzi.org> wrote:
> Hi Pedro,
> 
> this is a very good point.
> 
> > In this case, if the AP chooses to use DIX Frames,
> 
> I should have been more specific in section 5: The idea is to use an
> encapsulation that is *not* the equivalent of a DIX (type-based) frame.
> So the AP will simply not have that choice.
> 
> E.g., in variant 3 we would use an OUI that is not zero.
> 
> I would still prefer to use variant 2 or 1, which both also don't have
> that problem (variant 2 will be seen as a non-zero OUI by a standard
> SNAP implementation, and variant 1 cannot be mistaken as SNAP).
> 
> Variant 1: constant overhead of three bytes (LLC) plus possibly one
> byte used for demultiplexing (e.g., short vs. long CID, other IETF
> protocols sharing the LSAP allocation).
> We need to go to ISO to get an LSAP.
> 
> Variant 2: as with the 3+1 subvariant of variant 1.
> We would have to agree with 802 to use the reserved value 1 of the M
> bit.
> Also, it would probably not be a good idea to send less than 8 bytes in
> total, so there is a minimum ROHC frame size of 4 bytes (not a problem,
> since we have padding built in to ROHC).
> 
> Variant 3:
> a) constant overhead of at least six bytes (3 LLC, 3 OUI -- we can use
> the type ID part of the SNAP "protocol identifier" as we want), with a
> minimum ROHC frame size of 2 bytes (at least have to complete the 802
> "protocol identifier").
> b) constant overhead of seven bytes (3 LLC, 3 OUI, 1 demux -- again in
> the type ID), with a minimum ROHC frame size of 1 bytes.
> We need an OUI (or possibly re-use the IETF OUI -- I haven't checked
> who else uses this).
> 
> Resulting VoIP header sizes, assuming we have a way to use short CIDs
> (add one otherwise):
> 
> 1a      4
> 1b      5
> 2       5 (with at least 3 bytes of payload)
> 3a      7 (with at least 1 byte of payload)
> 3b      8
> 
> Gruesse, Carsten
> 
>

------=_Part_788_4470748.1103559316093
Content-Type: image/gif; name="scenarios.gif"
Content-Disposition: attachment; filename="scenarios.gif"
Content-Transfer-Encoding: base64

R0lGODlhwgIyAXAAACwAAAAAwgIyAYcAAAAEBAQICAgMDAwMDBAMEBAQEBAQEBQUFBQUFBgYGBgc
HBwcHCAgICAgICQkJCQoKCgsLCwsLDAwMDA0NDQ0NDg0ODg4ODg4ODw4PDw8PDxAQEBEREREREhI
SEhITEz/AABMTExQUFD/CAhQVVlVWV1ZWVlZWV1ZXWHWKChhYWFhYWVlZWn/JCRlaW1paWlpbXFt
bXGhWVlxcXF1dXV1dXn/PDx5eXl5eYGBeXl5fYF9fX3/SEiBhYn/UFCFhYWFiY2NjY3/YWGRkZGV
lZWVmZ3/cXGZnaGdnZ3/dXWhoaH/fX2hpaqlpaX/hYWurq6usrqysrL/lZW2trb/oaG6vsa+vr7G
xsb/srLGytL/trbOzs7K0tr/vr7S1t7W1tba2tr/zs7e3t7e4ur/2trm5ub/3t7/5ubq7vbu7u7y
8vL/8vL29vb/9vb///8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAI/wDdCBxI
sKDBgwgTKlzIsKHDhxAjSpxIsaLFixgzatzIsaPHjyBDihxJsqTJkyhTqlzJsqXLlzBjypxJs6bN
mzhz6tzJs6fPn0CDCh1KtKjRo0iTKl3KtKnTp1CjSp1KtarVq1izat0aVIkIDWB/lKlp5ccPNRZV
aCDCta3bt3DjxtQAoK7dB1to/qibl6KVuj/kCh5MuLBhhnsBiDArou4DmkTAgqEY5QHgw5gza95c
la4Ggir4Ji0T2m5gzqhTq169k+4DKwOtWOkrkMiD2w9oELR9W0OUgZFFqFGBW8lAMCJw5x6oVgWN
20Qia5gsMIoG3CrGHkxc+jTr7+DDi/8PmRiABhqwC5a+XVeFQBqOLQMw7mbvg+vyAVC3jPuyG9d2
lSWaG0rc5Rh1Bf0gwmz+jefggxBGmFBjdgHwgHsC/QUAhqVtUYZlHFooUGIajEXEZZXh5YYaln32
X10ibMFWYnl9aB5sJ5qn0BYNSujjj0Cq5lV+OroB3wPaqUFEXiciKZCNxiWWnhuWeXecZwK5pl19
okk5EHz6JcQjAFYGaeaZaMplxXN1seXaQaWBBdZlNA5U5ZOR5efimwPVyadAY7KF0JhlpmnooYgu
pcYPNPw20BYtvviYQRTKKeeMA1JJphtg8KfBD1hKSpCfIj7appg9JqrqqqzyZKMIBLH/qOORWy4m
oJMG1SnQnY09gNaLexY5omi09pmpQYS2quyyzMZEoQqTbUEXAGxpiCGYSoDR3oi3waarpoHxKWuw
Lg4LQF4aaoCWFZGiummz8MYrL0idGlhXuRSyV2Sc07r47Z1xEsdflsJyea5A68mnoruFzuvwwxAz
hFx+FxbEpoUYvqdwxj/cRtttpyWHcYqTJQdrnx6j7JgICA4KcsQwxyxzQVts0TLNtOEsURk5TwSG
hzMHLfTQRBdt9NFIJ6300kw37fTTUEct9dRUV2311VhnrfXWXHft9ddghy322GSXbfbZaKet9tps
t+3223DHLffcdNdt991456333nz3/+3334AHLvjghBdu+OGIJ6744ow37vjjkEcu+eSUV2755Zhn
rvnmnHfu+eeghy766KSXbvrpqKeu+rIxVOj667DHLvvssIcgsxgF0K777rz37vvvvEvQdAjAF198
DBBrAAUazDfv/PPQRy/99NNzwcBJEz9wcob4WclbxQdJe1vGBYmw/aMLI2R+TFZoQP378Mcv//z0
1+88ADZ1fBt9tfXmqBtlSM59/ncQFvXMDexy2QHXJ6b0kYQBXLCfBOsHhXLNS3kTzGD8rHeS+2yh
fS76kApk9K4TLQmEBhHhFipDvoGAxSBgmI5CXgiT9mnwhjjMof3wpxdqbWEvjirQkv9Ckx6w1AyI
CFEDXXoGqUkh62DqaSHNoFgSCOrwimioYPKWh8UccrAk7NLOXyajFpTtKmN/6dlzBqIEJxKEhhGB
o0ts2MU62jGDPJyJBjKmgZOdZyDra+OW5MhG9uRMf24kCI8OyJBFnsSKd8ygFh+GwUhO8IskCWN1
wvQA7zhSNqY64JbaeBBCckqGRFCBdQaYJRdJS1AqoaMlZ0nL5+VRJnt0Iaw+RJuOrQiW/7GgnX7g
SED5xpfhoyJzMBQjgWGomDQQjkggWcv5TdJhlaym/DBJErBYgYW7spIDEZZIRbZRNwYxpSM7poHZ
XKeVboCUFE8iS23as463jElliEn/nGhRMYEF+VDDAKVMbg2qoMHcVSdJGBhHEoeRHKHmPal3zQty
caLU4+ZI2oib9DiwkwUpEP8MghsCulCY8TzYXqjjSCMupyX1bF4RdAAELzxvpkV4nheAoIOcTg+n
1MvCB6IHBR3oIAvPy4JRbeq8mdb0fVkAQvSYcFFb1kQNAgQfpBRZUFNy9YDIfOIBaai9k6Z0C2qB
aEQjiFGKohRe2Wxr9DQaEpHWBgCweQ1BHjDSAqFTIfCZklmnmJewUikv+ClnSmKKBgs4wLEOqALz
vODYyjaPCY+FrGShV1kHOICp0NMBCqCHAgBYwAIA8CkaYGBax/qUspl1gGqjd1ro/1XBATqQXj5h
Aha0lKGP8XQjpLakRBmiCqyKPWs6XQTSEX2GR3QZaUgkKtfnVVReca2u8+gKEuDayT3NBWD6QiPd
hIDvjShdpxtVRJeODdQkMQVCZJn3AQswDwX2RcNtc4sGB4yWvvl1Hn6bZ4Gh0na2aMgCAKSKBh04
YLKyve+D0VDf5jkYtM7LAmoDzDzMAoC/0NutS3iEIEEWk0BOhNRbCZur5J54sOEFVUr36KsHslW7
1l0xs7KLYzRw9yO5NOsfM4Qr4ph0VH/9z/ngyWLDsvczHbsZSmI6YOY5mHkRZh4MHpyF+Vp5ws6j
afNgwGHngVmmYK4CACR75eZF2P8CIFbzZp0nX/xyGAUO2DKIrTqT4YaSSlNaY3DnKdYWH3SszPWO
jBfJIkKvtcc53iKkt3u9khDnV5CaUY3dUEYjjVM9m/5LedWp0vUidk86zqT7murlAut3zc2Tb/Tw
TL0xWOC/1i0zGrzgAAbTurEcxi30igAApD6PqsAOs02FHT0Rt0SgzJkUA6nkHhE65MUGTSaiw9mn
5x4sCgA4ckeo2+PrxovHOP6xR4rLqPuc9AfEgc2H7mOpaC0sLM+Z53UsNR317vXUAunUe0fC2C1b
Vr+fbd5tMYzwPWfYsQYmrcOZV4TYbvbWzsP481w9vdpCj9khrsleVKAgvgZce6D/qnFo+M3MJWO7
Pi42j6XcQ1ZFe7svl57mjSdtbrhWFdLq/khwgGmkPVJnUWZJ+llWtPTa9LG8tVG6WdSwqHVZaenR
Ac7ARRJTKPhXB1uGAcKdJ2eyOyDi0BsD2P0bPS87j7Jw1gHH4ZzxMjt2DNTz+PNAzmeaWEEtNGgZ
GAD/KyJI/QeCynqsmk6QsiTx8GxR/A+mZAW2VP1Jk9f5pJvX82ahW7tBh1dMNY4GYmdBzcYe+2XZ
Dj/TJ/XMzfv1rnvdWLTTnXkatgDDOavr/k6cec4uGrlx3Pkd/7zHoW9WTB3ABDMfFdZflikAcA09
hvMdDUBAO4HFTmD7VtjN/L1t/+953/bfoyH4RBu+dou/rM9XN/nMWj73Z59TkH+f2Aje+/yhAICf
WyD/yeZmoyVruAdrt0V9edd719c86Dc06ldd7Kcs7hd7p1WBOsBwQFBZKLB7XqB9GVVpMBNTW7Y8
sPVly0NszcdrKFAFLMiCzAMEDDaCu6Z3brZ7aMAEC3Zf/Ydlo2Vr+XVaLeiCaKB2eFd35adbTfOA
zVNfFfgBDEZnGohhTFBfKHB80hOBrTKBzFNZFehZzZdgjgUDRuVYc7aFsPeBzJIGM7AlBlFwnvVY
qYdnnsVfDvaGb0hfEbdlnuWBUDB+2GeHX4hwnmUBSHVbduhZknVbZUhhHuh7SP8IEl8wG4aihFiW
WaflWUylYXk2hl6mAwAghqUFgNCDhayihQHoZj9oAUW4hQHWh541P/CHJh4gAGt4EIzFPFXAgYtI
P7kYPWOQetJTBcCocMM4Sw2YBmWhAhtwAXUhAFOwEEHwOhCwAS+wA01gBWw4HpToiAqXZ6y4igEI
crLnVpL2PjS4Wg/Gf4HYYSiAd7cFA1sGiyCoLE3QjLXYeKu2efrYdwNRBk2wAxugALLjaAjDO9M4
AzswBYIlGE8gAkiQBgmxjddXW+p4bO04BiiQem32PqS4KqZ4jh/wYPE4PWNgUxsJP7F4JmVQIbS4
Jbe4j5OWR1MwAxCgOw0gAmL/sBCksQE8WZO9Q5BcMQEw8pAGIZF7NgZsN5Lx830cmWoSaIUbZwEt
CAWllVuOFT8n+T5coACy0ZVe+ZVgGZZiOZZkWZZmeZZomZZqSZYB4DotiUD5CJP7CABBIAICEDsQ
IAIJmZMX8UFEsAPK2ACxA5GDMSZ24ZCE6QYSCQMtWASotTxXGT8oGD8dqSofCQCHyF+R+T5ZST0n
YDygGZqiOZqkWTy0+ARxKZeT5omvYwAmEARWwAYlEYlBsAMesAFBsBBpYALUuAOSSBWC+TqIKZGH
aAFfuJnUQ2zz15TlmIDS05m79jzQKT0CWZrWeZ3YmZ29swEYoJr7mAEVcgE//3AFPBGNr6MAG6AC
O4AE2KgUsiEGpQE7AqAAOyc9Cxh91ec8rCWKROWUWQiVRkhUO+g8XldV0xk9RyAAPLmgDNqgDvqg
EBqhEjqhFFqhFnqhGCqhdymcH5Sa3kl8G9IEickTXxCcujONHrAD1piNM1EGsqGiIrABPtmMQxA7
F/AFRnmFA8p5DsBFeMaf/dmcHeeHpwWO53ig0JOSZ8Kh3BNJYxCExZhhUVoF4IhjDZgTYlAWNyCj
vCMAX9BIfOkRSACjPCmUvFOPr7MDApGj0lOkAYpnu8iclASg3Tc9hggDTCB3boefGzSPrfIFFRIj
+BhJrGkXWUZ+H2d+bXWlP//hov/4Alz6OmolEMwoOxP6jApRHryDnikqG64DAeS5pvV5hMHoWXiq
p5LFfx9gVKxKmf5ZinR6XwioU3LoX7uXffLYLDsAIwf0kjnkYEFYWlYIg6QKaYxqFMhoBSr6BLq5
ocWzAdAYO5yqogrJohrSHrI5ENvohNTjBbW6gS9YgU3oqkIKdH7KKjcJUb6KQ1nJd1lgg8LIjbgI
r3GKT4TRBA3aOwbQBAzxBLApGyPKEFNQFwqAqQSxjRNVmYliihOlpECSBpO6rjd0kkiZU++ImUJl
YBXnWXjGX3roX162sV5ojEITjR7Aooo5qsT3qh4ZqxjlsKsisRrkYKwqd/n/pWYWAAXNV1sqqIO5
hX8zCGv852sJF0nH2iwqgAQRqbLrx7KW6bINe64OI7MZ5Il2OH24mFp1epLCxnEJBmtM2V/Laa9B
E7AFgbD3pLCIwrD3BLOqQrUTdJJeN1Rlx4qn2Fi5xXfzNYhd6Ic5dLQxg7b2pLaHwrb2pG5gYBaU
Zxa7MXUGYXjlxXgIRHQC4RWfshCWSwPaQQT/syijgiBIZxaUixxLNmUeekVZGY91m2w0SHd6K1ln
V7NiZrQmYRb8UwZmgSCGJ7kDMRwFUXm5knSUWxC/kqkaAHU1IbjaRLiGYrja9GMfogSVARvWURYu
IgIjJGMEgb1olWSHNSoo/7VHs9FpB0ED7YRWk3Id2rFVlTttkJJ0X1E+gQdTp6tDqftgq1tbXGuV
EadgkkWDRRClVwS4FfEp0hIY0asEJeIG3Ku9sSJH70tSSUccKOsGhrcQnTKpM6G81cS8aeK81fRj
2ksDgbEgWaIELOJCOXMy7GsnhyRMCvJG/yOoWUIbLBNMLOxEvoEr0vJvV4LCYKAGW+BbNfMo8VQj
QPMkNnMcRdwQcCtBG+kFFUe30JdsvMZgQPBhpae1tgZrQHuDWku7I8G+PUwE6ARvKVzDBFEZ5vsl
F1IobqQCGVMz2kEDNIBpScxGGpAXYPAzgLLEK6IGPzMWTfzHigTIG8HBtf/kwWgCwrUEvXjxW7/x
ANTBuL1LyQdBBEvmQA58wgmxx8zRTgXRTmsRXE/yGCRnTJesu7kBQmuhwPDmJPeRbyLwHJMBy9jr
BtahIKVri/X7q5hphwaWv/lVceLqsW8Ipzp4WlhrSQRMEcfLabpRyvFkQSzSMtjYw9VRH3CsSI8R
Q3b8AFGAVQsCzs/Ruc9BTPcBK3sEKroBKtibG9HkR84hQzRAcpebyEwLgU67sFDbtlKLMHKyK31i
JXKcQskhXZwsTJ/GwPtGzc/BSv/xQUjCvveMQJPyvmbhXSr8H2dMHaAszhiNMGKxaZQsAoKydU16
R08ahM9ThlmQejuVU1n/sIpekIv+2zxRBQQCjEXPPBG2cR2TAcrVDBrzpM0FTVLePLnvERiMC7xG
YiU9DClooQbo1MPaW8ofIs3t+71lMLwVoci0xMhn4si0JMLXAl5JLRC57DIts9CjvJB/fLxDTBBf
LdKgHE3s+8YdYxwanXmjjFi0YcZLRCWqzM0qBhYPwLm3Mb8M8cTV9QERR4AT9dMR0T5oYR0TfdgM
TGhIPSLdjD6Vm3JOfRpKQNqK9FzlUhZfAWWnQdSPwW+P8RxrUcEUIdazRNZmYtaz9GNEvVULk8oe
fRD/Q9S78sLqkWTCvdmccj6MS9Q0htETDCufnU6CnSUj9Ft5kdH+Qkx7/1wzSbwmuKIQkC1Xc6sD
H/CJi0oSjGInpGHae+K9qZ0goe10RWcFiVva953f863NlaEENePaamzYawHetKEE5JsRuG1Juh0k
vG1JP3bQFgwrwr3A1GzE38sibAjXdq1XGK27xTtkSmQcRP0Xj4HS/VjRqQbKsF3VKsLdoJ3heywC
9GHcCVHecuUFrPrPdmTZEKHAgPIYXoEwJE50OVPdlrxXA1EZv+EbbK3fTs7AUq3aI3LGAs7cjwFv
tQErTpLGGrHgkdTgQPLgkaRurb3AwfRH7KIcNTMpbQQWCq0cZqEck2IdciJuAZdV6ETDnkYlbFjL
W9DLgJQXNKwWfZTKGf99Moz75suR2PLtyx+qjz4OEeZ7Helh6LCy5rix3bQR6PRNUrgR5W9+HrBS
GTROb9GkSNR9Mp0CFmtkyTQsbXJyy/SGvLe9z+bdz2vL488b0P0YUBChwQ1h2wUhZSNB7DBU7A+B
45HuzNjzEsYecBAR7QmRjcIuEWB+R2L+I2R+R26bKMze7Hc06fKS7Xa07T7S7Xb07YgS7uJOtktj
7nWE7hKiASVQA/ie7/q+7/ze7/7+7//uAr4eL1awAAB/8Aif8Aq/8Azf8PpO7vHCAC7g8BTf8CWg
64eirCq68Rzf8R7v8RowAR8/8iS/8cwaM2zwAyW/8izf8iQ/ASHg8jL/P/Mlr7RM8wQ0n/M6r6Jy
DTW7uiFEce3IYuA7Eistc9q2HhHUXhWlYfOaQXUSYeB5nOyK1HiIpxFCjzo/vy1CkVw70kkbPd4F
4Uba20YkF7996ZQBBBXxCQBOjxlJ/hBgX3J4btxk3EexnPXmxRCCDjpbbxdAqRSfvRgIQfafwUvL
lPYLUd1K0fZ18fYRYvgIYffpC0uRgRFebyen8/cVEvgbgelsPetUkhyQktDb8xiPIS19JNIOTerz
DUiB0UYJTdDdVh/nU7wjYuguosDJccba02+qfct9BMrJQXNf0fc/4fh2AflL0TFfMRnmO/sltxgm
I8pGsrvUdh3oVOnE/zH24Bv63kX5pmzXqW0+C3PmkxFDrm7Y/+HXw28coQErvM/6nTMFDGoACrqg
zC90HEIESrD9APHDzQMibgYWHFjGDREVA91sebDFjRINbn40dCOiosGHD3581KhmoMQyD8AM1JBS
w4OKIgRyhGnwxwOZDTWIVEMTzAORRERs0QBUohWebqxUBLoQo4qTMZ0+hRpV6lSqbpBswLpBgIKs
GyRWBRtW7FiDO3uKACPCYJSKM0W6tYjxQZmPB92UNLpxZkyPH1U8sBLXIA21KlXSJLIRKsShFZXQ
GCxQBEINZjUoMRjRTU6FNBMaxUhW9GjSpU2fRp1a9Wo3GxqwrqohMP/MMlt+aBDo2aFBFQUrO0z6
sGJQg4lhQvyoQa1wji5HboFOo6KKl1B/QO5ocMtjmtePP/AoE/fHuUmJisAMW33YBqHXvw/rHaaa
LQzbYpeP14raurq7v9yJL780UMgN4twI8DLotqOJIqmCG+ik2m7LjS/ltOtrJsw8E+EBGpqCL0QR
RySxRBFdM9GgAw1SwkMiaKgwM46OCo6m4JI60EGOIMSNOd5iFG8hxYyqzqKXIDLQpSj++25JhX5w
6aMf6NuojMQASxG+9rJMsS6OdqLOQS+9zEgJ9IzczSEv8YJJNxWWOxCvFZEMECYVRNJOsYhapOFF
IDNLLIqOpPwhMN3/rPhrOS4XZbRRR1lDMUUVsKNBOkHdoC5N3QzsTcYbp3tJhSEhJAqMkvDEctPb
MpstI+xkWs7M4PDSka2koJxoIzVEoHKhl2B8VLUtg32vVtywE/MlMs30rD+OGlyOiE3TzKmgTHM1
8KvsMqpu1R2LkvPSTDW4VDaaiFLjVN4MNWi5nIiFN155iY3UxJIqnUu6i0RQyz+YpC3Qxo2SUsMw
9yDEVC19RZALJm9bFIGGBxSV6YFJK7sXSpM4nSmK4DTwzSUNINsJLQ+lA3FesoZVWTUNqHsgiiWv
6xBNmzPDyFkZMzqMr395ulc6ieb0DIyUpPvtW9wuc0PfN9WaWdTd/2hoaOGNWCrjTSjda7lrr78u
rd4UrWi1vpNO0lZboxT9CsSzH6KrSARjapsIENVWI2WznfoIjPTuUiKwu5UosKm8tbP7S5KU+Bts
sFh2nLTtCidCIonUwBNzmJLWPO3NEAQD4YfoxtOKv1MefcfKnQKqDMJVfxvwrzxHcHWDatPuB9Qj
57133sX+GqhWo6K6DKOHF5FM3xuFfHn41DBuqqNMvZZE0Z3HPnvtxQLe64jBuo3cFIlAaPsUmzdf
tcTUjoqiHk0Eg+v056cf++7rxz9/jtDXv3///wcgvO4XQAL2jn8FRGACFbjAsAyQgQ8M1gEhOEEK
VrB+DrRgBkUkQf8NdtCDHxTga0A4wvVwkIQnRGEKU4NBFbZwKiZ0YQxlOMPWiJCGN3wKDHG4Qx5W
kIU9VKEOgThEIgLwh0UcoRCRuEQmau+ITdSgEqE4RSp27YlVnKAUsbhFLi7qil1UoBbBOEYyqueL
ZQygGNG4RjaS5Yxt1N8FXgBHOtbxNG+04/zKkIY89tGPVMHjHwU5SEJuL5CFRGQiFTmvGWxgkY+E
ZCQlOUlKVtKSf4ReTMhmkcht8pKfBGUPRVcXinlNeaFEZSoZiLnQFQhB0DkOdBSzBTDUpW210Vvs
DII5WmrHc7CsjStD15SUEXMLrnxILeWmSmY203+3mdTGtKYRFUX/syL3+kuFIDKy8GAzJQ5LiU0u
dhKWSOxNEjuJvl7WNOwwJGG3wQw2w+NMetazfg9TS2igVRxQ/Qg4RTkKpkI1JG9NikX9EhRRfqSu
gVihTpXREV6uVT17VtSivvMSkugiKiYx50DO+lS2WETQlxhmJbsJzkcgNC6HtoUlKQGA0b5yyovW
1KbzyuhcPLKFd2V0ODPV5sB+yk+HlbRyC0KpXn4AIecwpFMXWdDQgHpTqlaVWN6C6kYUGlCLtAUj
zhFYngRTMJLWpDj9EiuaNJOTpoDHIOjKzkXatUyr1tWuIQrfhQykHFFJBGl61UhKtLmcLSznLy97
1c0C+xvPFFYm/wJpUUr+xi+OSGwl6VksXe+6Wc6ipi7IRCZHQhtaqLyuaZoVbVh25xTUkbazr4Xt
aGi6msQoAWCxxW1ue+fJ91jhI67VbXCFO1ziFte4x0VucpW7XOY217nPhW50pTtd6lbXutfFbna1
u13udte73wVveMU7XvKW17znRW961bte9rbXve+Fb3zlO1/61te+98VvfvW7X/7217//BXCABTxg
AhfYwAdGcIIVvGAGN9jBD4ZwhCU8YQpX2MIXxnCGNbxhDnfYwx8GcYhFPGISl9jEJ0ZxilW8Yha3
2MUvhnGMZTxjGtfYxjfGcY6tGjpY9o99Or4wWwAwZAB4SF4z0f8MWSjygCKLALhAfrAViAweIsuv
UT8Y8o+pQoQhUxkAQ4KyhEVQ5NkQpchPzhJ9tEwVJhNoIUMuX5gjrIEvgzNpLPoIEUKrhI80Ts13
6XNMlPkDPSvOVL/9M0x8+1uo7GSeAwEAauWs4DEDQATI2xGdp3wpoBC5zjIpsrSIrBgVeLrITaEz
TAFABCwDQFua7nJinYKnkkR60hLeyZRBhkwme2gmRVZRkWHE5OW0GgDU0TRmpHzs6wwZTl0+aau/
ommRDVnSvBnyam+94KOY+gHp4TIA0rOkoCx73Nm2iLXLom7oVSfVwRY3R6Q9EXUHe1pOKfWxt01h
MEiHyUMOzJj/753uiCyIyQKZd2ZsrboOfZrOqsoypoDNESUAPCr5BvO+J5xvm0w8JrA2NcIjrvBf
/ZvKG3m4wyKe8h3VG99DzrjGFQwRI7epzgI/zmCKHFXovGXkkBY5AGgwNId/GtSuzojHjWLxlxtd
5g7utbYqru9wp0fKHpk6p3+gBJ8jneQGMvq7wU7QiIe7fAInbRRgjqenO7jVE7sNkQNTa1/3ujNF
9tjDn/Tzg4M9ZnTpcrDJ7vV/w6jSslZ4kcEDnmu3PcD59vS3Kf7vLo+b8kVOT8KB7ga1d3liExf7
0Wd3eX07ZdmmXrjjFWwFpLlktOGjAWhh78pFs/0jZRbVh9Tw/5GeEFrRvIeJmV6G6bcSilDEV33y
lb985jff+c+HfvSlP33qV9/618d+9rW/fe533/vfB3/4xT/+qiwadcrcM6HRXLunRAH55Jv1lKQC
f/KTxvya9H1M+Fxoqbi//cgvlPhju6egv0kqNZj6Gxr4ssu6nZVICcmLim+im0f7uIzbAq+DCgms
P7I4QDqbLJYAj6YoAwdkwMWgQAzRrBN8CAx8Cg2MJDBYtYq5HQj8i3ZRjJlwLaNxOs7ruxaMuTXj
CBfcQLCAQYTYi4lIMsC6wblovx7kiCVJPQF5CiBUkZhTpBZpOYk4wszAjPdZwR+TFlEZkr+QGM0S
Qu3YpZPgs/+/0cBeGsKpwELtQLp1eism9MIL/DEypEA9TEG6apvea5U21DZBKgmEqMG9apNlqrjd
8T8X/IHOMEMLRLq8ojM42Yi/oMI3vAuC4A3PeDQY/LFF5BtIdBhSfAoVxENOeamFk0BMhKTIWolp
cw863JxSqsBTjETWmcQYfLOT+CZX1EQ4fKkkg0AudAq9ggoVHIg+1MWhSbJD/MUkW6QRHA+98kJE
3JyiiMCYU0ZsPI5J1I2SGJqXYcJglApqTI7lkMZl/DhtTEa66kZUnEPFiMNwKkf92QGT0sd95Md+
9Md/ZIHTOMRNDJnNqQ6jcTOpOEN29MFmtIhN0YyH2xiwKAP/DvjHi8TIjNTIjeTIjOwAPmqho+jI
kSTJkjTJi6yB1BjIQrSLZ9EWhFw/ZYzHZUrFNvQMiRxEsMjHk+RJfmQBDegBKBDKoSTKojTKo0TK
pEzKI2CA0xiZzWmJIZmnbYoNbsxFugHHNnFGsgoLK4gApQTLsBTLsSTLsjRLokwAMSALJCvGpgEP
tBCtDmGJS3EKiZnLKVzHdrHF78jEsNiBEjjLwBTMwSRMsGTK1HjKIKyIR0vFjrBCKXSKmXRIm1QR
nlhIsQDKwtTMo2RKDYACNADN0BTN0STN0jTN0zxNLmhK03BBi1kI3QDFjrCyhozMq/xGLYTIcUSQ
bjQ9DUDN/98EzuAUzuEkzuIUzQVQS7HAssrBMnGJGaDQjZSAjuasy+f8i91pTDuZTTnsS52sAeME
z/AUz/H8TdVETKlsCMoqjsZyzaqQSWbESt3EkCrczcZTyM8kz/wkTdX0TP30z9A0T9NQO0MEgNlw
Ta7cK57bJfmDSlzMwKCIqi98SK3ExpnIyRnxzf/U0A39T+QcC1q8kJK4lGpBQlc6w2KUx+6Mz9TY
ge/k0BeF0eIM0NMYUGwLDCkrCIjADumMUCKpTQc9xaGL0JqcpZvUi4kUjf6M0fDkT/xcUuOc0dKQ
lsWjS5pjCbRZvCy1nLxUT8h0CrnUUsaYUJfMCEW5TE3K0P8nVdM1BU0PxczQuJA4pM9MUsypSFF8
a4i0KCzG487B4BXSaFE2FdQljVLTmFLwoMsWAQ+MsFItHdNEBNLIzFK3EtMuRZIyrdPRUNJBBc4m
5dTgLNTScEO6uVDtOYpPRdUOTc6wmJktuM5HbZqMKwnNoo+/IK3srNML/DZXLVAJBcbRCNRUFVbx
DFXTGNXjWL/82dRhHU1PZdb9XE0cOlXSLAIdAAIvGE0osNbR9AIg0IEiAE4mcFLRBIIxQM0PMNds
1QEdyILRzIJ1xVbRrNZrPc13ZVfTdNOw2JXFyxmCurczRTIrw1X6vMDyCQ887CvTCNbR9FZwFc1u
1YFxRQP/e5XYh/XWihXNLPiA0pzXeA1NbQUCbm3YcMXYci3NYh2iZX1W0HTWlQXQaL2haRVNC3AA
mnWAKgjND6hZB3CAdkUDJqhZm8VZ06wCB9ABagWAoS3NoiVNFAAAC7AAAHBYNICBp6VZh/UCmoVa
B5haebVaAICB0sxXsEgJkRhB/vDX+UiJCy0Zh7zF7OyRC/TA01hY0MwCntXa0ARaqAUAFAjNqt1a
C1jaoK3Z09QBvx1NreVZpdVZm/XZvRXa0yzaox3NIkjak4VZJFLZlW1Zl0UDlHUhmQVNILhZ0PwA
wUWDIihdNLCAjUUDB0BcNDhd0wRaAKDc0NSBIVNa0oSB/9i1WwAIWTTQAQcATS/gWtBEAeKVXdQV
Xgfw2OJ1gOAFAgDw2eNc1aq4QBBpEbrYFKnBkMfUv3vs07fFwLj9sr8YQNGo2+UFzTFwgLBlXcS1
3M/MAuBtX9glTQtA3KIN3vztWjQg3aGd3dRd3dYFTfw1XeYdzdq9XdDM3cuFVija3GftXJcF3ZBM
U+Rl3uEFTf39WOe9W6Xl4KZ9X6Od2feF4NK0AIlV3dCsgssd4QMGVwu43Rfe3Yn13dW1XrGACFfC
Q4UKQkZtz6fYFdqLqRUl31cTCDzMie30ztF839CEWjQoWo/14BaWYgVGgzGAgeqlYdNUXtFEgQ1W
Xg8GTf8oAGEdjmExLuEGptmqvWGWzdwimmBmrWDOnWMZEl0CHloDft3brd84Tt7S1AFsNWHcpeIU
Js0wDk3jDd5BZl0FPmSvrd7SJN3nbdPrpYpZ5YhDnErJKwkn5mQbdNsGhdslRjq1o0v1ddHQHGNz
ndzmFc0BhmLXJdrjJU0o0GI+7mDXneRAJmFCNuQGPlobxlwJxlg7ZoA6HtYLVqE9ptqdZV5cluHR
jOXTnGQXVmR53WUC3to+9l0znllbbtqrFVtNpgoso44OSY+KgxnDWkCV+KpYYbYO+TG5NRhEPGUJ
xRR3JIv1ld2dRdw1XuPRBYBkBoI3Nk0UaOC/lebQpOb/1/3fawbjhk7kOP7cPE7ZZG7mZeZoYXXm
FNpjNGZoGIji193dbC5aci7NbAZNYy5NhibNrKVhHfDjL87ixHWAdLVkm+5Z0hxbsECUkUmZKNCI
8mE140OIAhzq2CNi4/M9+Ns9tiOCwJjq2wlAYG1lB37fwz1emxbNgrZci/5Yr/7fA45jktYBk4Zf
Hf5j0Vzp33Tpiz7mJmJmkPZoz31ZHtpjcbbcdo1e0dRhoPXdiiZNmF7kSkbeMHZk1iVnnJ5YqMVk
0/TjHW6hum3sxZZl3FXg3O1f1ITkjGVkKY7dv37dzx5sBEbNuUZs0QxpHLrrVL1jCtbo0M3g12UC
wT7a/0mGacstbMO25m2229HuYPjtYMGl5bem4sKt17Am7qA+obplWm2uAtKdWeZN3rMOzUpubQBm
6QPObYje7RqGYN8OTtYW7oxGZr2W49hG1deGiS9Q0QLa45NGA+MF1w+wZetOXakVTvTG6MNVYUn2
W/6e2Mst2t927lneZegmIek+6NBUXS+oXyc95OTF6JeOcK7235Y2bvyW3f1WXsvV7pa26O6WY6pg
AysIgh1wceT7IPf+1NkezTGGWqgtZIbVWhSYbC/47tSsbYMQgxb3gAkgsjmSCjHAihcIAitgA//Z
Y5P+zKxVXiiw36INW+NFgSrgci4/Y4sGcBXWbiawX/80cFr8xN8xmOJI7nIv32IdMFctN+jwtmwV
Wl/JRgM0dt3TxdbkxVbLBYI291kgCF48R2PjhujJjuYpp9kzvvIo1vI2H1ptXeQTT2+UbYId8IAG
QD0WhAorAEkIcm8bv/EcJ9cdf14mOF0U+GjXzuvf1Nob59nwzoI3XleaveFGF06U3YIdMPJOdySp
uAHUawCXuAL8gWaTxtvqVV2eHWiehXae5XAoPnG3hujTJF1op/OiXfbljvbFXe6hrQKbjejQdPAH
2gIkkIr19XFoD2dtN91vd4A9t2Wd5VlEP+NuBk1lr1lmd3eulvdp1+3DtvYUhwkxuAEF6HRP+wKp
YAP/CBgyAdiAFyCCY1cg9471rXUAWrd1nx7a3IWBw/XvTn111FxziEZdqOXpSP5Ymx3OQr2CGeD0
TueKGVi/LZj5hd+AHZiCJ98eaH5pRa8CRYfRDHdhxX5ppBfOLDD6c2cgNlCABlD3pwDo+8Zopg9P
L8jwMVB6uBZ6on/RGW0CD+h0CBABF3fxhnd4AVh4Oap4AsJ4LWZulb/uA77d0EZNGq970TTpPAcA
OgdNJkABWH7fvt/1aLWCDSD2F2gCGI+KMpiCHRABiG/7HbB45wF69tZrp2egGRgyqXeKqtd8C27K
NCB7T7uAqh6NK1ABrVh4AJD4HXDy/on70ex7Kwf8/58d/DFAgeotaNPU+5yeZeI1fNMcA2z9fSA3
CsX3tAnYgflWcSvQdLZHPQMwgTjrpNse/c1H5wmaAk8DfY4Q/e1X5itQ+CEzgBdQe9SAfE0//06/
gBl4glBPn9of/mgezuQG8rjvcihw2qMFCAsO0BAsaLCgjoEHFxbkkmADgIgADOwQ4+YixowaN3Lk
eOWHCAMSJaroaPIkypQqL1rRwPAlzJgyZ9KsaZPmAosrd/Ls6fPnl5ERGyC5uKPGzaRKlzJtykVk
RANE2PzcKebJjg0ChEZUoLMq2LAnNUCZacFClbRQUADQgUZgzSIAmNDkwoCsWQAO9u51+1ahzIQ2
V/+MpJhGrM+PECOaQOwY45YZO3YgsWJli8aWTTdz7rz5ANfQokeTLm36NOrUQoke9ez6NeyDJCRO
+PJ458eQI5/c7r2RzY3JPyxbOZwRr0wLevk68At3plwYNe0ij3n2peCFXg5mp6kg6g7jvneymUJE
/PiqO0Zv2EChQuz48jdDVW3/Pv78+TUgne//v0wDRKQCVemt9AURJvxgYHpb1Ldaew+UlZwF2AFm
0HYFwQBAETZRN6F1FTIEBQAgEgSFAyZ2NxMQAoTH4HhW7DBFgTBidANpO7gEII89FoTABe0JOSSR
RRp5JJJJKrkkk0lqIJoKYrTmI5X+4SBAEzb2lsb/BAJsMCN6Wm60xVaibVAdTNeNWOJBKE6IggMd
eniXiS+pydBZYxh0J0ErymSXmL3VN8EMT5RhIxvfhTbcjvKNkVZaWcSUhaQLVaFnlTLlFCinYm3B
VZRG9SdfFpBWkeFLlzJURaZ/MtApYk9wpYAHM37F6QyiQZAGmnaKiKcFmBKkJpys3vShWb9auhcM
TOggkLEIXegqrIgpKhQELwRhRY2ObfGDBwGE9oIbms2ng1Bx+spQc63GtGm18a4kK0m3TimfchI5
gNZL7R5UBQDRunsQoPL+lMYLpBnw5ba3+rZFECIIOKtFvQILUxXMOgstGiR+oAPIINdF50wooBCT
/xdw7oUCqgUB8cGcBleVBrhlhqbAl01YYdtOW1jRxA66jeYBS43Gl5CpbNVJEBBAsOvXwAvBKzPV
GpkwoMNu3BvfWaY+t5AOSwMscNQEFVx1T7lBYBoEG9xgBVhsWEZE0A9yJQBmbli8kMkoq+wAy0yf
NbgFMM+EbNkMnY12TxCbcC1pG/BsUsKjLTDSBAWaK5+f/hLkRaX/Suo5GlWEblBaPU7NuMxpCBAq
R1vHxufYBmXRckGn1p477gSZzuPirPMkdxAqXFBa3iY94QGRdocWgVBTYLR34ognTvCrwld1VdBr
i7bgSQ0IJYAHP1xRrkQNfLX50ReOoS4aDgDhAP8ALxteBF9w+oX/Xh9YsD9z6PKf1VULDMmr2hey
lhHZwYZPTHDAdjK2IQdkwV8w4MuGjHXBlTlAg3yxwOniEzzt/eQKQDOBViQigEOZxHWo8dIOuOUG
7wEgCMdZ2vWsd72GZI+EYjHhDlSwgQkAAAIKzMgUPGCCHRDhfBlhw1YMcED2xSYhIXvWr/ZShLJc
xwuAIwhb3OLFk6EhjB2rHxghOMAjruQBbnQj+EDiBjA8AG5uUMMDDviDB4jAhx1h4GsEErILSqd0
ALAAFOjSLrl0yAvKYRUj0eDIgKEhIWUZA59E2EM/IkZul0kJDQvTnuA04YAXyRUAZqAR6pVNhzv/
RMMIOVm1BghAehmhImzQxRwAkDF+vbzOitoVTLf4zyAOKOR8CNiTB0DmAUpwww80cBEiSNMNIgDf
9OwoywWOimvL4YtfACan+LmlcAUhEavMSZAsUPKYBfEiDl0Ty23CiDiWYaNG1tPHVcazlSR7JQ/p
yTqibASXr1kRigznuevw6X9vUZZD90K4fa0xLMzEiBKkGU2MqIAGcsyICh6gASWoIJpEcIMKRKAB
8ImACCoFAw1EUJKLpFQEYLhITFeaHkC6hk9AaIsho9Uu0nWQnMY8lUQHB9T5zFOgrCPCBbp1EVZG
zZU7bKpTO1WUghqtitO6IEEWWqGGlhOibnHA/8eu6DT/KJMnF73IFpi50Yvg8QFq2IgGMKOBvKqh
pW4oQx7d8ICS0KCOenumBk5qBWYqoY9l0MBNfcNTz2TyOrszKlFZlVl2ouCKYfMPVrNKteJwhKoD
s2oONyla1hnUNX4Cq1GHVaFhogG2YS2rQYoQwti0dSdvdUNcoVnNO7qRhcfR6zMzElfMPOBQW6jm
D36w3C081wpKeAARjCvZbs5OWQ8NakHapU40sDOdhiNvO6GGhiIIS5OrFa1p3YXa6qn2vVVrrWe6
4wX8KRRqXZQf04A6RjACNZJoYAKHKgqW3y5WuBgRAQ1iile95u26Mg3sRZ97kejGda97PWljRf+q
3cdMtjN3ygK6nHbZRRa1jJSMJCYpWSyCXLB3rwmtfVkX31bN1585Zm1Xc/nN/oXXvyLCH+EA2D+H
uvgsvARQb9sI0pLMda46Pa7e8hbYLAsWrtD9AR0xQgQwWIam2LxNiTmjHL7opZAr9gucBDLj2uav
xQI5C/yYWt8fk3DHmepxVfeMUxGIIAocJTRGQALhjhDhzHrbCDU97GiNGBolUXAjp/DbmUeZ6l/C
otQ7gdChLLT3d57LQtN2G58oq+QB0Y0mdKUZ18guF8t5vQh2v+XMLgP3y9ZUga7dcGnLaKDSvUnz
ZkrVadSh7tOfFZgXTlXe3OmgCDaGTWijEF3/4zba2FaIrrE1AmaNzPSWrx7OSUbMkShooNzy8nOV
AH1aQf+gJHE9lF9d6oaM3rWkkHY1Rh772w3TgLrP3SdHBl7a5AZK0wCdH6Yy1k8FV+Xc2rQCiMMd
BYa7gQh39fhFYKqCKJQZfGo4abns6NIfsDAKKlCBNo/NXYAe5APnnZ98BX0RdmP8oittiaEXS/KR
bkQJADhgSDcCklc/gAYdAcNwTeJMdcMK3lSSd847cs2pMhcjDwDDD1Cu4YwQ2qMhx67Co4sRPEa2
0SzvOMA7vu2MEKHpGP823JQQXTtKV+3aZrjeUS7svXPE4QDdlw7gdN5MsZrPO505zc+JVh18/wAA
yIy3zq0JvrxC3ctuMHu5om7NvebtsUkXNzbvDdctRDajtGa9RmoNBjVs4a5loC5GwHD7mxowIwY0
rgFNiRKr+wjrPBa00DcaXK5PWSOHUntG0n5mna402LWu/h59P1I17HU4NAD2dW/KxyiodDiGffm3
pNmSLVxX3YZ/OMjG2arGO367kYeJF0I28f9gld+LLcNH8VqiIdxFIFbeqAHcSN9xnFS7RZPTFRYD
lpQGOF2iuRr3fVhG1VtzdVhhfd/ppVQ0PRO7KdpOEF+PGN+fId8EItrYcVkBil6iOZoCTs+CJBce
4VoB0tXA3VpiscRdcdnXAddFeVSYcR018f9e4QXZ/dEc/dUfmkHeEl5V5j2WBgwWNGHTb81aaZnS
DE7VD6gBBWqYhoGh50XfVFHguGVZXN2VhAkW+1UTYFkTyk2aSZgg8PwTzc2TBtiRChBBC94aSsFg
DGpEF+rNgrDbXl3URSFiFa4ShYWcSlVh1/XahkkXALwRwIVU0yVhFEZhEzqhYyBbJx7fSfiVNekd
FmLUlk0YISrd9C3It0UiJZYLSOxVK7pgx9HAk1CXr2XZHnkYAIDBpTVdZKmEHQIICmJeR7xVvQlg
EL7cSUCf17ni2n0dHdmRIs6RYQkg8wEidjFfhn3Z8gGXGpRjrwkeRrzfKDIePoHiE65jHmb/HjOq
QEZdRBzuGyBu4S1mhDQKlhVcmhLwIiUCpECaoQu22xY8VkFCX17Vm8EljxUUFtWV1v7l3DHyn6DJ
1F8VmxzuWx9Fk8HdFMbxowwqXcG9ob3ZFdzhGnWpZN05ogsG1mIlYBmqXQ/+n76hFDoWDTwyYTv2
Bh2ihBqcG7p1xJmNZAGWn1iIYk+eYOb1oE4C1seVxKX9IF0VIy7iIOrZowpoFBrKmldumOj5nJbd
FR4t5Ob5jEoGlwgkVz4OX0UenwaUQA3UpV3eJV7mpV7uJV/ypQvoXFdC5ejZ1Oh5WEkQgbsRwU4S
4DR5WFtihC4mlgrclC7C1IdNJkjdFGbi/+MEKqY1hdxMeSYYiIBIVVpk0qEVLEBfriZrtqZrviZs
xuZdEsBP3gZjqsRzGRwNAEDMGaRYThXMbUFXhsUOZIBsHidyJqdyruZfnsRz7dVMXddeHUoVvtFH
EqAIcKHSYeJM0dFeFdZfuZF3TuDAXVR20tReyZR07RP0nWdhVeEzddgEliBdLqd95uVfyshk7Cd/
9qd//ieABqiA7gBvuGO8sMEPDKiCLiiD9udeNSiERuh/2tBK4J49Wihw3V6G1p5xYUbe6B7sXWgZ
mCNkRJ2/zVGIcuNGBaDehFtPSImExmiE5kAKyICM3iiDFmi6bcREGghWasSPpkSPcsSPBv8pSugn
jiZpgOqogTZpk64HAOxAjpmeRGZgSB2KSEFWlraEPUoTM3EgwF1aLZ5ZC3LfSeliNM3Ub20U0Tkp
RrQBD4DACGiBm9apnd4pnv4YlEaElL5XhG2Y3kXWrT1ApREqrlHmgnypSnLpHuIamWZpFZaEVOJa
AmKiSLmhncIpCGzqnOapp34qqIZqteypRPQpfJkSEeji0TkjZDqdBmDpLGrYW52ol1FXSpUhSiUq
P0pTo7qppm4qp9KpqA4rsRarsa4EqY6EqTpVr6oB1AGbQrKqPRLqPn1pNcnqg5HpcGlkC27dmkpT
R4FUUK7WrwJrsB4ruqZroAhfStDeQ57/BFbOXsA1Wm+ChZE6VbIKxbLSUzPqpEqepbReBKEll7V6
nl/FlbYGnKEGFtupqDQBlh0t1r2KVrma67mqa1hgKMZurMKlxNL9wHt2RAsaIk5NYJoixsiu27gK
TwNsAJ9FYh8FpnoG7L691Zfu0xY4FmmqVMzl7K7W7F4RLD/uEyNyZJOaAQgsgZP6bE+oFKHBp1Ge
2Zb9IukhxnmehBJM7MbymTQC7JhEnU7Vo9dx3E+kLDXSU8s26ZBilLsx2vSw69PxxNr+GNIqrZNq
bUfk40tyRD8GVjT94HUhxlvqY0o4wdb6BNR9Z685La6RZlyRZmNNo1wF5qvOkQaoFK1e/2E1YoaF
7drIUh86/iiEQecLkiYa8hFkiSFkfV56auOuXe7l+lDaiuoe4e2vRYEuHq5K1K3wlAGhEeZoqpSh
gUFNEW/ZVRrxEi9KNdaVBW+9YWU+3iO7aaTmeh1zxdxiuhQgkh+hRVZMFRqXkdSGEZqhSacB/a6R
toDu8oQpQtbIgSPKfaNgHQpidtke9duC+BUendnHRlO1YgZgGRCkVmGiwi1wCiximSUz0dHHZWde
3Vq/NqPa1S9K2W61zG6o/oCLmkTgrW9K8K6OgZiXwk2DfYofmvAb0pQf8uqrBvBhddyqTk9A+ky7
hSfc5G7/7lFCdmz0lUSD0RH9gmtKKv+k2H7fRsIND2JGTmJEGIRBCzSxB6eEwpGZDgdsH+qN+EET
GuqqwPLvNe0R+HSrdOWVwenUKpYW3+GsEoAnyCoXHAFndLExLPIR2Q6Uy0YxHn9w0rJOEQLXX/3V
pQkhXNksrGpYm5LxcJ2xh1XhHFKgYIHdF0dXHvXxMrIQ0R0KGFDT/Iac3oAnrkWBrbqqXsHcRpCB
DdgACJwyGeTxMpLbSmXUJArg+lWTXMURF+cqSQ4y3LRgSX1u/vIvxwEim15TIPdjXF0adZbUq1Vv
GVDTNrLsHbOyNGsECKNNyr4neI4dL/9A5Bpy3iDy22JZIFbi2/Ytc2FlFFilAOpUJA7/5w5ebvwu
ckncWhkU1iZuhPpOc2lV2h6qJKba7HFcsf3ast5gI/9i00ZNqj/6crn4Mx6F25X14djFodiym4bJ
UbiWC5UtSKPh1MrKCwZ7MInq80VUc9X0cXb6c8HOojaKwC7z6jez3kV5LfN5YceVW3OZM0o5sgt7
nSV/20xxaRCi1PoB8SOzhKFB8CBzRD6TdEaI6XA2oEqdFECLWXPhIPSp3WIlIsf1o06hKbeCLfgU
1svd8/Q03XAClkeR5k01IKGOXWIBVkcZat3RAB1F2OpqT0ivbz9yRMHprklXjUwJp0299ZVqM9iG
40FixsuBRDCKs7Bdda5Bo07LNcbN/2f0NaQ0UZPPkKZwbcFLQvBH7uF1IbFdT2D6OfVKlEFApqMS
jOhdJc8UIRxmkKg53tQjrp06a+gcjVnu+Z5VloF1qVtelZk9KgHcFCP7sVBkOStLvDZk3BRr1zHj
7LXu9jUrHm5gVw1iopzL2bXHnRxdoeOf3tFJgVzHAS6YDRx6T5OhAeBjphw/WiVi0kC91pFAd9w1
DWUBlhT9/uAX7ltH2RHYwQ1I7KRqP0yvjsVJBXKnDG6oWvedDhbklmyFB2Lsql3ksm7smi/UmW66
brd9cd/aPtZdcWmn8HCCZ9WiCWnxwspmEquE2+k34lEZjObObfZM9WF0iW0EzzNmPP9mX4X4Hjte
XLWtUWapARuIiq+4k2/tjNfpW/Ug7SEmr8ZcNG1ZA4IsM0HwYNUrsYr4k485mTt1lLvplK93SdXj
W5pUNW25TX6oLjb5p4p5md85nq8vEWzVp27j17UxPu40TnnULwu6RnMZKWdlsRpBGOS5oz86pK+W
SIEEVbpaTDGTWkuk2gWwXBeWoQnvddWbIEa6k66BFGhEF3SBG0jBGpC6q78669hV1uaeH/oxS9gR
icpruUA3XN1VJoM5rLtjGNiARjiB4QrBKge7si97oNA5s4fqGqwBGYTBGWDEGUAxEzcxsV9EGJCB
sbtBspPBtSc7t68yuT87uqc7Stz/prqLqhPYgBAkQQusMhXYgBMIQQtUO7zLO7GfQQskAb4brg00
cQvYgLwbrr8D/Cm3O8M3vMMf67tfBBX4gBs4QbIP/MRfhBQQuxAYrht0vBsMvBO3ehdwvMcLwbY/
vMrvxNVOI9O6lWPMOko4u7J/e0b4QBNTfHokAdrgvMHYvBNrfBKgchgAPbEP/EV8u8hv+7CHfKO7
Qb2vvNQbo3bOkU8seQliPTcyvM1jBNKf+200fdUgvbwAvfrCO7UPvNE7fdILvLZz+9E//cZPPcO3
lErlDfcSJkrJ1K0FL3gqLz0q5RwR2vOS3Rx1VPcCF/qOL/haky6aLzSRLyRCGM2v/7gPSIEPkD0W
+ADnJ7sTcD7If7wPoHy3C8Gqf/7oY4QQjL4TnLrqT7y9XwQW2EDqu4EPtIDpq/67nzrqYwG4xzvn
n0Hme/zs174PVHvFU4EbbL4PeLzok/7Pb/u9u0ELtPoaPHHJJz2xT7/tu73YN/30r8HC0726W+EP
X7UmQ6PRIRdKFex0ujDREUEM46AJf14f3Zq+GfFjJSCwcZn+NypAaFDiRsUDNwcRJlS4kGFDhw8h
RpQ4kaLDFkLcdGnhhkyLM26k2HBDxcaaMC2cuBGCkQqIMGFEOmnRxY0PKSoxakyJ0IaNM2dakAFK
M4lImAp7hlmTBOMZG13CgLjpw/8n0J8z3RRVedONTyw+VaZcOdJlRbMRnfS04eOgkJ4+hKQs+vYg
1Z4pfbxk6ybMXiEtbAhJcpZwYcOHESdWvJhxY8cOH5Q5KNCNZDBENLgxOHnLlswHDXp2Q3l058+a
tyQMvVm0BhVWED6I0lkFDc2SS2uevaW2aNCPgQcXjtDjQRtU3HwkE7IrTTdOUm40/jImxufRee40
jrxrGCeDDwY9mvB4eCwvBZ88+H06+/BkuoiM39XJS5JupHcfDhF6coUf/wswIioATEK7/RBMUMEF
GWzwsM1G+8ENETRwLTMINTAtNjdaS60033Lb0DfRyqDhgQdse6DCClXQDKEMNVv/0TUQIXTQxgbz
swGvntzS7zr8eKLuxx/zM5C8MNrTzgYhjwxPrcDG6687KfULSgjknlwLyOluHDK4kKiQorguySzT
zDPRVCiyyaz4oUU3rLgQtwzBgDC0zGAsrc6D1HjAw99GzExCDg16AIyDrIjCRc40OxTOKPb8Lc1J
FRvzKSesm88H7oy0VEgp+7P0wCWnk8I6/M4YL8j3DuriPJGGXNJU4j7CVDqbDjojOgBJvbEL54Tr
AjoAKS3W2GORpUjFLX7IDLMtrBDBoGaZBSA1EVTg7c4QYVRBhR9EAMBRQD9rjQZmBdXACiUegA1D
GsBodt12J8y2oGTxjQgw70QK/ymMLnzYSCMsqEDpuSWdcOkoUFMKyVauuKxSijDGOgliH9PqomCo
YJWS1BYmHiu5i1ptgYr4UkrLu7Lybdnll2GOGTQrVCACISJE+EGNQZUQgQgi1DgI5ygkVMNmoIUO
2g0lfogUoaJtdsPog8CNeunaYHNjUDfihU0JrG8WgWiZX55JCIil8MGJNXbqQjAsnKPCJinWWOOm
X1t1Ttj4kESI7oP+1nVTvw/8+yAqBKPJ7rwBXyM5Jwb3mwyEumCKu5HmdpzszTnv3PPganysDA2C
jvPz0x/LL7in3FhjTNRhj1322WUO/bEfVMyT9t0nUh24r2wwmffhiS/e+OORTxBe+eWZb97556GP
XvrpXw4IADs=
------=_Part_788_4470748.1103559316093
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

------=_Part_788_4470748.1103559316093--



From rohc-bounces@ietf.org  Mon Dec 20 16:43:05 2004
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 QAA12809
	for <rohc-web-archive@ietf.org>; Mon, 20 Dec 2004 16:43:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgVSQ-0006Jb-PA
	for rohc-web-archive@ietf.org; Mon, 20 Dec 2004 16:52:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgVGV-0006fo-Pq; Mon, 20 Dec 2004 16:40:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgUyV-0002jz-AE; Mon, 20 Dec 2004 16:21:51 -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 QAA08930;
	Mon, 20 Dec 2004 16:21:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgV7q-0004yY-6P; Mon, 20 Dec 2004 16:31:30 -0500
Received: from apache by megatron.ietf.org with local (Exim 4.32)
	id 1CgUeG-0006St-L4; Mon, 20 Dec 2004 16:00:56 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1CgUeG-0006St-L4@megatron.ietf.org>
Date: Mon, 20 Dec 2004 16:00:56 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: rohc mailing list <rohc@ietf.org>, rohc chair <cabo@tzi.org>,
        Internet Architecture Board <iab@iab.org>,
        rohc chair <lars-erik.jonsson@ericsson.com>,
        RFC Editor <rfc-editor@rfc-editor.org>
Subject: [rohc] Protocol Action: 'A Negative Acknowledgement Mechanism for 
 Signaling Compression' to Proposed Standard 
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: bb8f917bb6b8da28fc948aeffb74aa17

The IESG has approved the following document:

- 'A Negative Acknowledgement Mechanism for Signaling Compression '
   <draft-ietf-rohc-sigcomp-nack-02.txt> as a Proposed Standard

This document is the product of the Robust Header Compression Working Group. 

The IESG contact persons are Allison Mankin and Jon Peterson.

Technical Summary
 
   This specification describes a mechanism that allows Signaling Compression
   (SigComp RFC 3320) implementations to report precise error information upon
   receipt of a message which cannot be decompressed.  This negative
   feedback can be used by the recipient to make fine-grained
   adjustments to the compressed message before retransmitting it,
   allowing for rapid and efficient recovery from error situations.
 
Working Group Summary
  
 The working group supported advanced of this document.  There were
  comments from the SIP and using cellular community as well the working
  group. 

Protocol Quality
 
 The awareness that this specification was needed arose from implementation
  experience with SigComp.  The error messages and feedback are pragmatic
  in nature.  The document was reviewed for the IESG by Allison Mankin.


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


From rohc-bounces@ietf.org  Wed Dec 22 13:11:15 2004
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 NAA18974
	for <rohc-web-archive@ietf.org>; Wed, 22 Dec 2004 13:11:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChB6u-0006dq-AA
	for rohc-web-archive@ietf.org; Wed, 22 Dec 2004 13:21:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChAvf-0002am-QR; Wed, 22 Dec 2004 13:09:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ChAp5-0000Fl-J5
	for rohc@megatron.ietf.org; Wed, 22 Dec 2004 13:02:57 -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 NAA18355
	for <rohc@ietf.org>; Wed, 22 Dec 2004 13:02:52 -0500 (EST)
Message-Id: <200412221802.NAA18355@ietf.org>
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ChAyk-0006Oz-6P
	for rohc@ietf.org; Wed, 22 Dec 2004 13:12:58 -0500
Received: from localhost ([127.0.0.1] helo=psg.com)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1ChAoy-0002xu-Uh; Wed, 22 Dec 2004 18:02:48 +0000
To: lars-erik.jonsson@ericsson.com, cabo@tzi.org
Date: Wed, 22 Dec 2004 10:02:48 -0800
From: Allison Mankin <mankin@psg.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: rohc@ietf.org
Subject: [rohc] ROHC documents, next steps
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mankin@psg.com
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.8 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c

Hi, Lars-Erik, Carsten, ROHCers,

As you know, the IESG approved draft-ietf-rohc-sigcomp-nack-02.txt 
last week.  There were some light worries by the Security ADs, but the
Security ADs decided they didn't merit Discuss.  Also IANA asked if
the error codes shouldn't merit their own registry.  Adam wrote a good
response as to why not, which is entered as a comment in the tracker,
for anyone who wants to track it down.

Three more ROHC documents are awaiting IESG action.  I've just sent 

draft-ietf-rohc-context-replication 

for IETF Last Call, after reading it through carefully myself.  It
names TCP as a key use case, and you've asked to advance the 
background Informational documents:

draft-ietf-rohc-tcp-field-behavor
draft-ietf-rohch-tcp-requirements

In field-behavior, Figure 12 I'd say the Row 20, RFC 2385, should probably
be marked with a *.  Even though the MD5 option is not well-regarded, it
is the recommended protection still for both BGP and LDP over TCP. 
I've been surprised too many times to rule out that their flowing over
a link needing compression.

And so it also struck me that a couple-week review of tcp-field-behavior
in the TCPM WG is probably a good idea - so I'm going to send the draft
to them with a request for review, timeout the same as the context-replication
i-d Last Call, January 12.

During this same time, the chairs should  prepare three questionnaire
writeups, one for each of the documents to be published.  These are
described in 

draft-ietf-proto-wgchair-doc-shepherding-01.txt

Thanks, and happy holidays, everyone,

Allison







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


From rohc-bounces@ietf.org  Thu Dec 23 04:54:04 2004
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 EAA23375
	for <rohc-web-archive@ietf.org>; Thu, 23 Dec 2004 04:54:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChPpS-0005ol-2U
	for rohc-web-archive@ietf.org; Thu, 23 Dec 2004 05:04:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChPac-0000Zv-2d; Thu, 23 Dec 2004 04:48:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ChPYT-0008TX-Sn
	for rohc@megatron.ietf.org; Thu, 23 Dec 2004 04:46:46 -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 EAA22840
	for <rohc@ietf.org>; Thu, 23 Dec 2004 04:46:43 -0500 (EST)
Received: from texworld.com ([203.129.254.200] helo=twmail.Texworld.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ChPiK-0005ZL-4u
	for rohc@ietf.org; Thu, 23 Dec 2004 04:56:57 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] [SigComp]Shared mode and some other SigComp-state related
	stuff.
Date: Thu, 23 Dec 2004 15:20:39 +0530
Message-ID: <A43E318AFF9617408F27295C904F5A73A404B2@twmail.Texworld.com>
Thread-Topic: [rohc] [SigComp]Shared mode and some other SigComp-state related
	stuff.
Thread-Index: AcTme1BmhutB5OP6SJCT9Vo7NlJYQACWYJdg
From: "Ninoo Pauls" <ninoo@Texworld.com>
To: "Surtees, Abigail" <abigail.surtees@roke.co.uk>,
        "Lajos Zaccomer \(IJ/ETH\)" <lajos.zaccomer@ericsson.com>,
        "Gustav E" <gustav_kung@hotmail.com>, <rohc@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: quoted-printable
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: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: quoted-printable

Hi=20
      This document has a para

   "This document does not address compression specific issues such as
   different compressor types and bytecode.  This information can be
   found in a separate document."

  Can someone give the pointer for the document specified.



Regards
Ninoo

-----Original Message-----
From: rohc-bounces@ietf.org [mailto:rohc-bounces@ietf.org] On Behalf Of
Surtees, Abigail
Sent: Monday, December 20, 2004 3:28 PM
To: 'Lajos Zaccomer (IJ/ETH)'; 'Gustav E'; rohc@ietf.org
Subject: RE: [rohc] [SigComp]Shared mode and some other SigComp-state
related stuff.

Hi Gustav, Zacco,

> > Since I'm fairly new to this list and SigComp in general, I=20
> > have a few=20
> > questions:
> > 1. Regarding Shared mode: What became the consensus of the previous=20
> > discussions on the list? Is the general somewhat simplified=20
> > recommendation =20
> > to only "allow" a compressor to create one shared-state?
>=20
> See the latest implementor's guide.

The latest version of the implementer's guide is available at
<http://sigcomp.srmr.co.uk/~ahs/draft-ietf-rohc-sigcomp-impl-guide-04.tx
t>.
It has not been submitted yet and all comments are welcome.  I am
intending
to submit it early in January.
=20
Best regards,

Abbie

_______________________________________________
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


From rohc-bounces@ietf.org  Thu Dec 23 05:18:30 2004
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 FAA24330
	for <rohc-web-archive@ietf.org>; Thu, 23 Dec 2004 05:18:30 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChQD6-0006KN-48
	for rohc-web-archive@ietf.org; Thu, 23 Dec 2004 05:28:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChPmf-0002uT-PU; Thu, 23 Dec 2004 05:01:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ChPji-0002Gd-45
	for rohc@megatron.ietf.org; Thu, 23 Dec 2004 04:58:22 -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 EAA23493
	for <rohc@ietf.org>; Thu, 23 Dec 2004 04:58:19 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ChPtY-0005sk-Oc
	for rohc@ietf.org; Thu, 23 Dec 2004 05:08:33 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <YHL6W95B>; Thu, 23 Dec 2004 09:59:49 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8803D5B3D@rsys004a>
From: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
To: "'Ninoo Pauls'" <ninoo@Texworld.com>,
        "Lajos Zaccomer (IJ/ETH)"
	<lajos.zaccomer@ericsson.com>,
        Gustav E <gustav_kung@hotmail.com>, rohc@ietf.org
Subject: RE: [rohc] [SigComp]Shared mode and some other SigComp-state rela
	ted stuff.
Date: Thu, 23 Dec 2004 09:59:35 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
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: 6cca30437e2d04f45110f2ff8dc1b1d5

Hi Ninoo,

The document referred to is the user guide which has currently expired.  It
will be revived early next year.  In the mean time, the last version is
available from
<http://sigcomp.srmr.co.uk/~ahs/draft-ietf-rohc-sigcomp-user-guide-00.txt>.

Best regards,

Abbie


> -----Original Message-----
> From: Ninoo Pauls [mailto:ninoo@Texworld.com] 
> Sent: Thursday, December 23, 2004 9:51 AM
> To: Surtees, Abigail; Lajos Zaccomer (IJ/ETH); Gustav E; rohc@ietf.org
> Subject: RE: [rohc] [SigComp]Shared mode and some other 
> SigComp-state related stuff.
> 
> 
> Hi 
>       This document has a para
> 
>    "This document does not address compression specific issues such as
>    different compressor types and bytecode.  This information can be
>    found in a separate document."
> 
>   Can someone give the pointer for the document specified.
> 
> 
> 
> Regards
> Ninoo
> 
> -----Original Message-----
> From: rohc-bounces@ietf.org [mailto:rohc-bounces@ietf.org] On 
> Behalf Of
> Surtees, Abigail
> Sent: Monday, December 20, 2004 3:28 PM
> To: 'Lajos Zaccomer (IJ/ETH)'; 'Gustav E'; rohc@ietf.org
> Subject: RE: [rohc] [SigComp]Shared mode and some other SigComp-state
> related stuff.
> 
> Hi Gustav, Zacco,
> 
> > > Since I'm fairly new to this list and SigComp in general, I 
> > > have a few 
> > > questions:
> > > 1. Regarding Shared mode: What became the consensus of 
> the previous 
> > > discussions on the list? Is the general somewhat simplified 
> > > recommendation  
> > > to only "allow" a compressor to create one shared-state?
> > 
> > See the latest implementor's guide.
> 
> The latest version of the implementer's guide is available at
> <http://sigcomp.srmr.co.uk/~ahs/draft-ietf-rohc-sigcomp-impl-g
uide-04.tx
t>.
It has not been submitted yet and all comments are welcome.  I am
intending
to submit it early in January.
 
Best regards,

Abbie

_______________________________________________
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


From rohc-bounces@ietf.org  Thu Dec 23 05:52:35 2004
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 FAA26528
	for <rohc-web-archive@ietf.org>; Thu, 23 Dec 2004 05:52:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChQjv-0007DI-7Q
	for rohc-web-archive@ietf.org; Thu, 23 Dec 2004 06:02:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChQU9-0004gV-K1; Thu, 23 Dec 2004 05:46:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChQPD-0002ov-Cl; Thu, 23 Dec 2004 05:41:15 -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 FAA25742;
	Thu, 23 Dec 2004 05:41:12 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChQYu-0006tP-B7; Thu, 23 Dec 2004 05:51:26 -0500
Received: from esealmw129.eemea.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBNAeYOi026235; Thu, 23 Dec 2004 11:41:03 +0100
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 23 Dec 2004 11:41:00 +0100
Received: from [153.88.8.195] ([153.88.8.195]) by esealmw127.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 23 Dec 2004 11:40:59 +0100
Message-ID: <41C9E759.8070807@ericsson.com>
Date: Wed, 22 Dec 2004 22:30:01 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>, rohc@ietf.org, mpls@ietf.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Dec 2004 10:40:59.0996 (UTC)
	FILETIME=[E45C69C0:01C4E8DB]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit
Subject: [rohc] Comments on draft-ash-avt-ecrtp-over-mpls-protocol-01.txt
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.4 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit

Hi,

Sorry for the crossposting, however this is something that I think needs
to be generally discussed between all 3 WGs. To me it looks like the
proposed solution for VoIP header compression across an MPLS network
contains a problematic demultiplexing mechanism. I don't think people 
has realized the issues with the proposed mechanism due to lack of 
communication between the header compression and MPLS folks. If it is my 
lack of knowledge please educate me, and the others. I would request 
that people providing input in this discussion is overly explaining as 
education seems necessary.

The current draft is available at:
http://www.watersprings.org/pub/id/draft-ash-avt-ecrtp-over-mpls-protocol-01.txt
it should also be available in the IETF repository if it hasn't expired.

The header compression mechanisms such as CRTP and ROHC to my 
understanding assumes that they have a lower link layer that carries 
their compressed messages between compressor and decompressor. This is 
due to that they are intended to be used with only a single link between 
the compressor and decompressor. In the case of CRTP, it also assumes 
that the link-layer can also provide the with identification of the 
packet types, while ROHC makes this identification internally.

The MPLS network uses one or more labels in the transport between 
ingress and egress from the MPLS network. Due to the possible relabeling 
in the middle of the network, it can't be generally assumed that packets 
arriving with the same label comes from the same ingress point. This 
makes the label not sufficient to identify the ingress for the egress, 
thus not making labels equal to a link.

The proposed solution has thought of the above MPLS problem and proposes 
that one uses the setup signalling to allow the decompressor point to 
select which parts of its context identifier (SCID) space that belongs 
to different ingress points that arrives over the same label. However my 
understanding is that this definitely not without problems for the 
header compression mechanisms. I would like the header compression guy 
to clarify what problems that would arise from such a solution. One 
thing I definitely can see would be an issue, the proposed change would 
prevent MPLS HC to use any standard implementation of the HC mechanism used.

I would also like to point out that the Header Compression mechanism 
needs a return path from the decompressor mechanism. However the draft 
does not seem to discuss this issue at all. Or is a MPLS label path 
automatically reversible?

It would be desirable if the MPLS people could consider if there exist 
other ways of providing for the standard assumption on link layers that 
header compression has? For these assumption please see chapter 2 of RFC 
2508, section 4.1 of RFC 3095, and RFC 3409.

For example, what would be the effects of requiring unique labels 
between ingress and egress and for the reverse path?

What effects would it have to put the multiplexing point in the layer 
two extension?

I would also like to see the draft be more header compression agnostic 
as has been agreed on in the requirements phase. There is no problem 
with using ECRTP as an example how one realize the solution, however the 
necessary hooks and signalling must be in place for any header 
compression mechanism.

So lets get the discussion going and hope that something good results.

Cheers

Magnus Westerlund
AVT Chair



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


From rohc-bounces@ietf.org  Thu Dec 23 06:15:25 2004
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 GAA28005
	for <rohc-web-archive@ietf.org>; Thu, 23 Dec 2004 06:15:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChR5y-0007mK-SZ
	for rohc-web-archive@ietf.org; Thu, 23 Dec 2004 06:25:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChQgS-0007Nr-Kd; Thu, 23 Dec 2004 05:59:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChQdZ-0006kL-37; Thu, 23 Dec 2004 05:56:05 -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 FAA26900;
	Thu, 23 Dec 2004 05:56:02 -0500 (EST)
Received: from mail.riverstonenet.com ([63.113.148.10] helo=riverstonenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChQnF-0007IG-8Z; Thu, 23 Dec 2004 06:06:16 -0500
Received: from mgate1.riverstonenet.com by riverstonenet.com
	(8.9.3+Sun/SMI-SVR4-Yago)
	id CAA24022; Thu, 23 Dec 2004 02:55:21 -0800 (PST)
Received: (from daemon@localhost)
	by mgate1.riverstonenet.com (8.13.1/8.13.1) id iBNAtLSg007136;
	Thu, 23 Dec 2004 02:55:21 -0800 (PST)
X-Authentication-Warning: mgate1.riverstonenet.com: Processed by daemon with
	-C /etc/mail/sendmail-simple.cf
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by mgate1.riverstonenet.com (8.13.1/8.13.1) with ESMTP id
	iBNAtIqw007108; Thu, 23 Dec 2004 02:55:19 -0800 (PST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChQUA-0004hM-Sx; Thu, 23 Dec 2004 05:46:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChQPD-0002ov-Cl; Thu, 23 Dec 2004 05:41:15 -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 FAA25742;
	Thu, 23 Dec 2004 05:41:12 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChQYu-0006tP-B7; Thu, 23 Dec 2004 05:51:26 -0500
Received: from esealmw129.eemea.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBNAeYOi026235; Thu, 23 Dec 2004 11:41:03 +0100
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 23 Dec 2004 11:41:00 +0100
Received: from [153.88.8.195] ([153.88.8.195]) by esealmw127.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 23 Dec 2004 11:40:59 +0100
Message-ID: <41C9E759.8070807@ericsson.com>
Date: Wed, 22 Dec 2004 22:30:01 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>, rohc@ietf.org, mpls@ietf.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Dec 2004 10:40:59.0996 (UTC)
	FILETIME=[E45C69C0:01C4E8DB]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Archive: <http://www1.ietf.org/pipermail/mpls>
X-Spam-Status: No, score=0.0 required=4.0 tests=none autolearn=failed 
	version=3.0.1
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on 
	mgate1.riverstonenet.com
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit
Subject: [rohc] [mpls] Comments on
	draft-ash-avt-ecrtp-over-mpls-protocol-01.txt
X-BeenThere: rohc@ietf.org
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.4 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: 7bit

Hi,

Sorry for the crossposting, however this is something that I think needs
to be generally discussed between all 3 WGs. To me it looks like the
proposed solution for VoIP header compression across an MPLS network
contains a problematic demultiplexing mechanism. I don't think people 
has realized the issues with the proposed mechanism due to lack of 
communication between the header compression and MPLS folks. If it is my 
lack of knowledge please educate me, and the others. I would request 
that people providing input in this discussion is overly explaining as 
education seems necessary.

The current draft is available at:
http://www.watersprings.org/pub/id/draft-ash-avt-ecrtp-over-mpls-protocol-01.txt
it should also be available in the IETF repository if it hasn't expired.

The header compression mechanisms such as CRTP and ROHC to my 
understanding assumes that they have a lower link layer that carries 
their compressed messages between compressor and decompressor. This is 
due to that they are intended to be used with only a single link between 
the compressor and decompressor. In the case of CRTP, it also assumes 
that the link-layer can also provide the with identification of the 
packet types, while ROHC makes this identification internally.

The MPLS network uses one or more labels in the transport between 
ingress and egress from the MPLS network. Due to the possible relabeling 
in the middle of the network, it can't be generally assumed that packets 
arriving with the same label comes from the same ingress point. This 
makes the label not sufficient to identify the ingress for the egress, 
thus not making labels equal to a link.

The proposed solution has thought of the above MPLS problem and proposes 
that one uses the setup signalling to allow the decompressor point to 
select which parts of its context identifier (SCID) space that belongs 
to different ingress points that arrives over the same label. However my 
understanding is that this definitely not without problems for the 
header compression mechanisms. I would like the header compression guy 
to clarify what problems that would arise from such a solution. One 
thing I definitely can see would be an issue, the proposed change would 
prevent MPLS HC to use any standard implementation of the HC mechanism used.

I would also like to point out that the Header Compression mechanism 
needs a return path from the decompressor mechanism. However the draft 
does not seem to discuss this issue at all. Or is a MPLS label path 
automatically reversible?

It would be desirable if the MPLS people could consider if there exist 
other ways of providing for the standard assumption on link layers that 
header compression has? For these assumption please see chapter 2 of RFC 
2508, section 4.1 of RFC 3095, and RFC 3409.

For example, what would be the effects of requiring unique labels 
between ingress and egress and for the reverse path?

What effects would it have to put the multiplexing point in the layer 
two extension?

I would also like to see the draft be more header compression agnostic 
as has been agreed on in the requirements phase. There is no problem 
with using ECRTP as an example how one realize the solution, however the 
necessary hooks and signalling must be in place for any header 
compression mechanism.

So lets get the discussion going and hope that something good results.

Cheers

Magnus Westerlund
AVT Chair



_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls

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


From rohc-bounces@ietf.org  Thu Dec 23 06:17:22 2004
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 GAA28241
	for <rohc-web-archive@ietf.org>; Thu, 23 Dec 2004 06:17:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChR7s-0007rx-T4
	for rohc-web-archive@ietf.org; Thu, 23 Dec 2004 06:27:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChQgV-0007PN-U0; Thu, 23 Dec 2004 05:59:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChQdk-0006ls-LM; Thu, 23 Dec 2004 05:56:16 -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 FAA26929;
	Thu, 23 Dec 2004 05:56:13 -0500 (EST)
Received: from mail.riverstonenet.com ([63.113.148.10] helo=riverstonenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChQnR-0007Ij-IC; Thu, 23 Dec 2004 06:06:28 -0500
Received: from mgate1.riverstonenet.com by riverstonenet.com
	(8.9.3+Sun/SMI-SVR4-Yago)
	id CAA24043; Thu, 23 Dec 2004 02:55:34 -0800 (PST)
Received: (from daemon@localhost)
	by mgate1.riverstonenet.com (8.13.1/8.13.1) id iBNAtYkH007163;
	Thu, 23 Dec 2004 02:55:34 -0800 (PST)
X-Authentication-Warning: mgate1.riverstonenet.com: Processed by daemon with
	-C /etc/mail/sendmail-simple.cf
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by mgate1.riverstonenet.com (8.13.1/8.13.1) with ESMTP id
	iBNAtVqm007146; Thu, 23 Dec 2004 02:55:32 -0800 (PST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChQUA-0004hM-Ia; Thu, 23 Dec 2004 05:46:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChQPD-0002ov-Cl; Thu, 23 Dec 2004 05:41:15 -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 FAA25742;
	Thu, 23 Dec 2004 05:41:12 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChQYu-0006tP-B7; Thu, 23 Dec 2004 05:51:26 -0500
Received: from esealmw129.eemea.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBNAeYOi026235; Thu, 23 Dec 2004 11:41:03 +0100
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 23 Dec 2004 11:41:00 +0100
Received: from [153.88.8.195] ([153.88.8.195]) by esealmw127.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 23 Dec 2004 11:40:59 +0100
Message-ID: <41C9E759.8070807@ericsson.com>
Date: Wed, 22 Dec 2004 22:30:01 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF AVT WG <avt@ietf.org>, rohc@ietf.org, mpls@ietf.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Dec 2004 10:40:59.0996 (UTC)
	FILETIME=[E45C69C0:01C4E8DB]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Archive: <http://www1.ietf.org/pipermail/mpls>
X-Spam-Status: No, score=0.0 required=4.0 tests=none autolearn=failed 
	version=3.0.1
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on 
	mgate1.riverstonenet.com
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit
Subject: [rohc] [mpls] Comments on
	draft-ash-avt-ecrtp-over-mpls-protocol-01.txt
X-BeenThere: rohc@ietf.org
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.4 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: 7bit

Hi,

Sorry for the crossposting, however this is something that I think needs
to be generally discussed between all 3 WGs. To me it looks like the
proposed solution for VoIP header compression across an MPLS network
contains a problematic demultiplexing mechanism. I don't think people 
has realized the issues with the proposed mechanism due to lack of 
communication between the header compression and MPLS folks. If it is my 
lack of knowledge please educate me, and the others. I would request 
that people providing input in this discussion is overly explaining as 
education seems necessary.

The current draft is available at:
http://www.watersprings.org/pub/id/draft-ash-avt-ecrtp-over-mpls-protocol-01.txt
it should also be available in the IETF repository if it hasn't expired.

The header compression mechanisms such as CRTP and ROHC to my 
understanding assumes that they have a lower link layer that carries 
their compressed messages between compressor and decompressor. This is 
due to that they are intended to be used with only a single link between 
the compressor and decompressor. In the case of CRTP, it also assumes 
that the link-layer can also provide the with identification of the 
packet types, while ROHC makes this identification internally.

The MPLS network uses one or more labels in the transport between 
ingress and egress from the MPLS network. Due to the possible relabeling 
in the middle of the network, it can't be generally assumed that packets 
arriving with the same label comes from the same ingress point. This 
makes the label not sufficient to identify the ingress for the egress, 
thus not making labels equal to a link.

The proposed solution has thought of the above MPLS problem and proposes 
that one uses the setup signalling to allow the decompressor point to 
select which parts of its context identifier (SCID) space that belongs 
to different ingress points that arrives over the same label. However my 
understanding is that this definitely not without problems for the 
header compression mechanisms. I would like the header compression guy 
to clarify what problems that would arise from such a solution. One 
thing I definitely can see would be an issue, the proposed change would 
prevent MPLS HC to use any standard implementation of the HC mechanism used.

I would also like to point out that the Header Compression mechanism 
needs a return path from the decompressor mechanism. However the draft 
does not seem to discuss this issue at all. Or is a MPLS label path 
automatically reversible?

It would be desirable if the MPLS people could consider if there exist 
other ways of providing for the standard assumption on link layers that 
header compression has? For these assumption please see chapter 2 of RFC 
2508, section 4.1 of RFC 3095, and RFC 3409.

For example, what would be the effects of requiring unique labels 
between ingress and egress and for the reverse path?

What effects would it have to put the multiplexing point in the layer 
two extension?

I would also like to see the draft be more header compression agnostic 
as has been agreed on in the requirements phase. There is no problem 
with using ECRTP as an example how one realize the solution, however the 
necessary hooks and signalling must be in place for any header 
compression mechanism.

So lets get the discussion going and hope that something good results.

Cheers

Magnus Westerlund
AVT Chair



_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls

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


From rohc-bounces@ietf.org  Thu Dec 23 09:57:31 2004
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 JAA14091
	for <rohc-web-archive@ietf.org>; Thu, 23 Dec 2004 09:57:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChUZ9-0005WB-H3
	for rohc-web-archive@ietf.org; Thu, 23 Dec 2004 10:07:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChU9a-0007w4-JM; Thu, 23 Dec 2004 09:41:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChU7P-0007LX-NB; Thu, 23 Dec 2004 09:39:07 -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 JAA11820;
	Thu, 23 Dec 2004 09:39:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChUHJ-0004i4-GZ; Thu, 23 Dec 2004 09:49:21 -0500
Received: from apache by megatron.ietf.org with local (Exim 4.32)
	id 1ChU3p-0006TG-OC; Thu, 23 Dec 2004 09:35:25 -0500
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1ChU3p-0006TG-OC@megatron.ietf.org>
Date: Thu, 23 Dec 2004 09:35:25 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: rohc@ietf.org
Subject: [rohc] Last Call: 'RObust Header Compression (ROHC):Context
 Replication for ROHC Profiles' to Proposed Standard 
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org
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: 856eb5f76e7a34990d1d457d8e8e5b7f

The IESG has received a request from the Robust Header Compression WG to 
consider the following document:

- 'RObust Header Compression (ROHC):Context Replication for ROHC Profiles '
   <draft-ietf-rohc-context-replication-06.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2005-01-13.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-rohc-context-replication-06.txt


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


From rohc-bounces@ietf.org  Sat Dec 25 19:14:24 2004
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 TAA25581
	for <rohc-web-archive@ietf.org>; Sat, 25 Dec 2004 19:14:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CiMDV-0006Ur-N2
	for rohc-web-archive@ietf.org; Sat, 25 Dec 2004 19:25:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CiM0v-00016A-Iu; Sat, 25 Dec 2004 19:12:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CiM07-0000zI-O3
	for rohc@megatron.ietf.org; Sat, 25 Dec 2004 19:11:14 -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 TAA25406
	for <rohc@ietf.org>; Sat, 25 Dec 2004 19:11:04 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CiMAQ-0006Qi-7u
	for rohc@ietf.org; Sat, 25 Dec 2004 19:21:52 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iBQ0B1O6029852 for <rohc@ietf.org>; Sun, 26 Dec 2004 01:11:01 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Sun, 26 Dec 2004 01:10:55 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <Z2FY6QA6>; Sun, 26 Dec 2004 01:11:00 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E9A5C@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'Carsten Bormann'" <cabo@tzi.org>
Subject: TS clarification (was: [rohc] The discussion on slope(s) (redux))
Date: Sun, 26 Dec 2004 01:10:59 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 26 Dec 2004 00:10:55.0002 (UTC)
	FILETIME=[5E115FA0:01C4EADF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: "West, Mark" <mark.a.west@roke.co.uk>,
        "Surtees,
	Abigail" <abigail.surtees@roke.co.uk>, rohc@ietf.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.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196

To capture the findings of this discussion, I propose to add the
following two sections to the implementer's guide.

BR
/L-E 


4.2. (De)compression of TS without transmitted TS bits

RFC 3095 briefly explains that ROHC RTP in its most efficient compression operation, conceptually described as the SO-state, apart from packet type identification and the error detection CRC, compressed headers only carry RTP sequence number (SN) bits. All other fields are then either omitted because they are unchanged, or can be reconstructed through a function from the SN, i.e. by combining the transmitted SN bits with state information from the context. Although it is never spelled out explicitly what fields are inferred from the SN in this way, one should be able to figure out that this principle applies to the IP Identification (IP-ID) field and the RTP Timestamp (TS) field.

For IP-ID, compression and decompression, both with and without transmitted IP-ID bits in the compressed header, are well defined in section 4.5.5 (see section 8.2 of this document). However, for TS it is only defined how to decompress based on actual TS bits in the compressed header, either scaled or unscaled, but not how to infer the TS from the SN, i.e. the SO-state operation. Although the general idea is simple, the actual operation must be clearly defined to ensure interoperability. There are also inconsistent text pieces that might confuse an implementer and result in non-interoperable implementations. This section therefore provides the necessary clarifications to SN-to-TS decompression, i.e. decompression of TS (scaled or unscaled) when no TS bits are transmitted in the compressed header.

When no TS bits are transmitted in the compressed header, the encoded TS value (scaled or unscaled) is to be decompressed assuming a linear extrapolation from the SN, i.e. delta_TS = delta_SN * default_slope. 

Section 5.7 defines the potential values for default_slope as:

  If value(Tsc) = 1, Scaled RTP Timestamp encoding is used before
  compression (see section 4.5.3), and default-slope(TS) = 1.

  If value(Tsc) = 0, the Timestamp value is compressed as-is, and
  default-slope(TS) = value(TS_STRIDE).

What must be noted here is that there is no other slope value used than the default_slope value, as defined in section 5.7, and it can never be changed. There is confusing text in section 5.5.1.2 that might mistakenly be interpreted as if the slope can have different values and be "learned", which is incorrect. The default_slope from 5.7 is always the value used when decompressing TS based on SN.


4.4. TS_STRIDE for scaled timestamp encoding

The timestamp stride (TS_STRIDE) is defined as the expected increase in the timestamp value between two RTP packets with consecutive sequence numbers. TS_STRIDE is set by the compressor and explicitly communicated to the decompressor, and it is used either as the scaling factor for scaled TS encoding, or constitutes the default_slope used when decompressing an unscaled TS through a linear extrapolation from the SN (see also section 4.2 above).

The relation between TS and TS_SCALED, given by the following equality in section 4.5.3, defines the mathematical meaning of TS_STRIDE:

   TS = TS_SCALED * TS_STRIDE + TS_OFFSET

In the compression step explained following this core equality of section 4.5.3, TS_SCALED is incorrectly written as TS / TS_STRIDE. This formula is incorrect both because it excludes TS_OFFSET, and because it would prevent a TS_STRIDE value of 0. If "/" were a generally unambiguously defined operation meaning "the integral part of the result from dividing X with Y", the absence of TS_OFFSET could be explained, but the formula still lacks a proper output for TS_STRIDE equal to 0. As the core equality above does not prevent setting TS_STRIDE to 0, and there is no reason to not allow a compressor to do that, the formula of "2. Compression" should not be read as having any formal meaning.



> -----Original Message-----
> From: Carsten Bormann [mailto:cabo@tzi.org]
> Sent: den 9 december 2004 14:15
> To: Lars-Erik Jonsson (LU/EAB)
> Cc: West, Mark; Surtees, Abigail; Carsten Bormann; rohc@ietf.org
> Subject: Re: [rohc] The discussion on slope(s) (redux)
> 
> 
> 
> On Dec 09 2004, at 13:57 Uhr, Lars-Erik Jonsson (LU/EAB) wrote:
> 
> > Folks,
> >
> >>> So in the IP-ID case the non-encoded field grows with SN 
> and in the
> >>> Timestamp case the encoded field grows with SN.
> >>
> >> That's my conclusion, which I would put slightly differently:
> >> With IP-ID, if it is not encoded in the header, it grows in
> >> parallel SN.
> >> With TS, if it is not encoded in the header, it grows in
> >> parallel with TS_STRIDE*SN (independent of Tsc!).
> >
> > Which could also be expressed as:
> > With TS, if it is not encoded in the header, its scaled
> > representation grows in parallel with TS_STRIDE.
> 
> s/scaled/unscaled/
> 
> (The scaled representation grows in parallel with SN.)
> 
> 
> > TS can thus be communicated in three ways:
> > 1) Unscaled
> 
> ...and sent with WLSB
> 
> > 2) SCALED and sent with WLSB
> > 3) SCALED, inferred from SN
> 
> Yes.
> 
> > It seems like 1) and 2) are "clear" from 3095, while what is really
> > missing is a defined decompression (and thus compression)
> > logic for 3).
> 
> Well, at least 3095 says that Tsc is 1 in the context, so 
> SCALED is the 
> more likely interpretation, I'd say.
> 
> > The "default slope" value would be an important
> > part of that logic, and I guess most implementers have actually
> > used that value for the simple function
> > TS_SCALED=(SN-SN_OLD)*default_slope + TS_SCALED(SN_OLD)
> > for decompression of TS_SCALED when no TS bits are sent.
> >
> > Q: Would default_slope be used when decompressing based
> >    on TS bits actually sent?
> 
> No.  4.5.3 is quite clear on what to do.
> 
> > Q: Can default_slope be anything but 1?
> 
> (If Tsc is 1:) No.  See 5.7.
> 
> > Q: Can TS bits ever be omitted when sent unscaled?
> 
> Yes, with an ext3 if Tsc is 0, R-TS is 0, and no TS bits are in the 
> base (i.e., UOR-2-ID) header carrying the ext3.
> 
> Gruesse, Carsten
> 

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


From vqdvw@tys-site.com  Wed Dec 29 04:32:01 2004
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 EAA22554;
	Wed, 29 Dec 2004 04:32:01 -0500 (EST)
Received: from user-0cetd7d.cable.mindspring.com ([24.238.180.237])
	by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1CjaMd-0000s8-4Y; Wed, 29 Dec 2004 04:43:31 -0500
Received: from august.anu.contempt.au ([249.141.185.0] helo=anu.sworn.au)
	by smtp1.radiosonde.co with esmtp 
	id 1A5Ys6-949158-39
Message-ID: <NCBcreatingboggyAKEOAA.unwieldy.eighty@cde.Com>
Sender: freeradius-devel-vqdvw@tys-site.com
X-Mailman-Version: 2.0.1
Date: Wed, 29 Dec 2004 10:27:58 +0100
From: "Rosario Forbes" <vqdvw@tys-site.com>
To: ipcdn@ietf.org
Subject:  How have you been? Order all your meds here . . keystone
X-Spam-Score: 6.0 (++++++)
X-Spam-Flag: YES
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228

The best prices and specials online

Buy FDA-approved prescription medications:

Ambien - $3.99
Cialis - $6.66
Viagra - $4.99
Xanax - $3.99
Valium - $3.99

and much more in our online shop

Please click below and check out our offer.

http://desperado.cheapestrxmeds.info/gate.php?sid=I7cExMje&pj=415










beribbon norwalk l's sardine tiny agone sedge quandary lynx danbury
disdain became formatting proximate puritanic once algiers compliant gibberish
descriptor schwab duplex affect sanitary wilkins petticoat appertain compendia duly dan
threefold valediction anthropomorphism dogbane marigold tokyo birefringent ethan
agricultural fungicide apothecary semper babbitt frictional vegetate vicious
course boastful chase clifford embargo arsenate andrews brandeis


From rohc-bounces@ietf.org  Wed Dec 29 18:51:04 2004
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 SAA02791
	for <rohc-web-archive@ietf.org>; Wed, 29 Dec 2004 18:51:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cjnm6-0007O0-SA
	for rohc-web-archive@ietf.org; Wed, 29 Dec 2004 19:02:43 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjnXh-00024E-Oy; Wed, 29 Dec 2004 18:47:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjnWq-0001VM-O6
	for rohc@megatron.ietf.org; Wed, 29 Dec 2004 18:46:57 -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 SAA02467
	for <rohc@ietf.org>; Wed, 29 Dec 2004 18:46:53 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cjni3-0007If-LM
	for rohc@ietf.org; Wed, 29 Dec 2004 18:58:32 -0500
Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iBTNkgK06646; Thu, 30 Dec 2004 01:46:43 +0200 (EET)
X-Scanned: Thu, 30 Dec 2004 01:46:35 +0200 Nokia Message Protector V1.3.34
	2004121512 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id iBTNkZ5b023300;
	Thu, 30 Dec 2004 01:46:35 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks003.ntc.nokia.com 00dAeJtT; Thu, 30 Dec 2004 01:46:33 EET
Received: from daebh001.NOE.Nokia.com (daebh001.americas.nokia.com
	[10.241.35.121])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iBTNkQU05001; Thu, 30 Dec 2004 01:46:26 +0200 (EET)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by
	daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 29 Dec 2004 17:46:24 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: TS clarification (was: [rohc] The discussion on slope(s) (redux))
Date: Wed, 29 Dec 2004 18:46:22 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B82891F9@ajebe001.americas.nokia.com>
Thread-Topic: TS clarification (was: [rohc] The discussion on slope(s) (redux))
Thread-Index: AcTq4B6+6V7+GCaFTsqPwsz1nIh5/QDGFvOA
To: <lars-erik.jonsson@ericsson.com>, <cabo@tzi.org>
X-OriginalArrivalTime: 29 Dec 2004 23:46:24.0237 (UTC)
	FILETIME=[9B1371D0:01C4EE00]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 6a45e05c1e4343200aa6b327df2c43fc
Content-Transfer-Encoding: quoted-printable
Cc: mark.a.west@roke.co.uk, abigail.surtees@roke.co.uk, rohc@ietf.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: 32029c790f79bd4a84a26bd2915c54b9
Content-Transfer-Encoding: quoted-printable

Hi,

I have to disagree with the text. It makes significant changes
to RFC 3095 in order to preclude learned slope, now that the
*existence* of slope in RFC 3095 is finally admitted.=20

- Why learned or dynamic slope is such a bad idea? Its benefits
have been discussed with many examples. It's algorithm has been
explained and scrutinized. The only concern was raised by Kristofer,=20
which I addressed.

- In terms of specification, why make such a big effort to
change RFC 3095, instead of clarifying it with text on learned
slope (like the one I proposed)? Many texts in RFC 3095 point
to the existence of learned slope. With clarification on learned
slope, ROHC falls much more nicely together. Why take the pains
to erase each of those texts in order to preclude learned slope?

- Do we have some basic rules here for discussion, i.e., not using
double standard? How can we say certain text in RFC 3095 is correct
when it fits our argument, while at the same time claim other text
is "incorrect" when it does not?

- Now to the details, the text of section 4.5.3 RFC 3095 is quite=20
clear on the concept and operations of scaling TS before compression=20
(copied below). How come it's "incorrect"?

   1. Initialization: The compressor sends to the decompressor the value
      of TS_STRIDE and the absolute value of one or several TS fields.
      The latter are used by the decompressor to initialize TS_OFFSET to
      (absolute value) modulo TS_STRIDE.  Note that TS_OFFSET is the
      same regardless of which absolute value is used, as long as the
      unscaled TS value does not wrap around; see 4) below.

   2. Compression: After initialization, the compressor no longer
      compresses the original TS values.  Instead, it compresses the
      downscaled values: TS_SCALED =3D TS / TS_STRIDE.  The compression
      method could be either W-LSB encoding or the timer-based encoding
      described in the next section.

   3. Decompression: When receiving the compressed value of TS_SCALED,
      the decompressor first derives the value of the original
      TS_SCALED.  The original RTP TS is then calculated as TS =3D
      TS_SCALED * TS_STRIDE + TS_OFFSET.

- How come the text on section 5.5.1.2 is "incorrect"? Simply because
it states how learned slope works in R-mode?=20

- Default-slope means default slope. That's the slope the decompressor
assumes to initialize its context, which implies slope can be later =
updated
by the decompressor. In dictionary, default means "a selection =
automatically=20
used by a computer program in the absence of a choice made by the user". =

Isn't that obvious?

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 December, 2004 06:11 PM
> To: 'Carsten Bormann'
> Cc: West, Mark; Surtees,Abigail; rohc@ietf.org
> Subject: TS clarification (was: [rohc] The discussion on slope(s)
> (redux))
>=20
>=20
> To capture the findings of this discussion, I propose to add the
> following two sections to the implementer's guide.
>=20
> BR
> /L-E=20
>=20
>=20
> 4.2. (De)compression of TS without transmitted TS bits
>=20
> RFC 3095 briefly explains that ROHC RTP in its most efficient=20
> compression operation, conceptually described as the=20
> SO-state, apart from packet type identification and the error=20
> detection CRC, compressed headers only carry RTP sequence=20
> number (SN) bits. All other fields are then either omitted=20
> because they are unchanged, or can be reconstructed through a=20
> function from the SN, i.e. by combining the transmitted SN=20
> bits with state information from the context. Although it is=20
> never spelled out explicitly what fields are inferred from=20
> the SN in this way, one should be able to figure out that=20
> this principle applies to the IP Identification (IP-ID) field=20
> and the RTP Timestamp (TS) field.
>=20
> For IP-ID, compression and decompression, both with and=20
> without transmitted IP-ID bits in the compressed header, are=20
> well defined in section 4.5.5 (see section 8.2 of this=20
> document). However, for TS it is only defined how to=20
> decompress based on actual TS bits in the compressed header,=20
> either scaled or unscaled, but not how to infer the TS from=20
> the SN, i.e. the SO-state operation. Although the general=20
> idea is simple, the actual operation must be clearly defined=20
> to ensure interoperability. There are also inconsistent text=20
> pieces that might confuse an implementer and result in=20
> non-interoperable implementations. This section therefore=20
> provides the necessary clarifications to SN-to-TS=20
> decompression, i.e. decompression of TS (scaled or unscaled)=20
> when no TS bits are transmitted in the compressed header.
>=20
> When no TS bits are transmitted in the compressed header, the=20
> encoded TS value (scaled or unscaled) is to be decompressed=20
> assuming a linear extrapolation from the SN, i.e. delta_TS =3D=20
> delta_SN * default_slope.=20
>=20
> Section 5.7 defines the potential values for default_slope as:
>=20
>   If value(Tsc) =3D 1, Scaled RTP Timestamp encoding is used before
>   compression (see section 4.5.3), and default-slope(TS) =3D 1.
>=20
>   If value(Tsc) =3D 0, the Timestamp value is compressed as-is, and
>   default-slope(TS) =3D value(TS_STRIDE).
>=20
> What must be noted here is that there is no other slope value=20
> used than the default_slope value, as defined in section 5.7,=20
> and it can never be changed. There is confusing text in=20
> section 5.5.1.2 that might mistakenly be interpreted as if=20
> the slope can have different values and be "learned", which=20
> is incorrect. The default_slope from 5.7 is always the value=20
> used when decompressing TS based on SN.
>=20
>=20
> 4.4. TS_STRIDE for scaled timestamp encoding
>=20
> The timestamp stride (TS_STRIDE) is defined as the expected=20
> increase in the timestamp value between two RTP packets with=20
> consecutive sequence numbers. TS_STRIDE is set by the=20
> compressor and explicitly communicated to the decompressor,=20
> and it is used either as the scaling factor for scaled TS=20
> encoding, or constitutes the default_slope used when=20
> decompressing an unscaled TS through a linear extrapolation=20
> from the SN (see also section 4.2 above).
>=20
> The relation between TS and TS_SCALED, given by the following=20
> equality in section 4.5.3, defines the mathematical meaning=20
> of TS_STRIDE:
>=20
>    TS =3D TS_SCALED * TS_STRIDE + TS_OFFSET
>=20
> In the compression step explained following this core=20
> equality of section 4.5.3, TS_SCALED is incorrectly written=20
> as TS / TS_STRIDE. This formula is incorrect both because it=20
> excludes TS_OFFSET, and because it would prevent a TS_STRIDE=20
> value of 0. If "/" were a generally unambiguously defined=20
> operation meaning "the integral part of the result from=20
> dividing X with Y", the absence of TS_OFFSET could be=20
> explained, but the formula still lacks a proper output for=20
> TS_STRIDE equal to 0. As the core equality above does not=20
> prevent setting TS_STRIDE to 0, and there is no reason to not=20
> allow a compressor to do that, the formula of "2.=20
> Compression" should not be read as having any formal meaning.
>=20
>=20
>=20
> > -----Original Message-----
> > From: Carsten Bormann [mailto:cabo@tzi.org]
> > Sent: den 9 december 2004 14:15
> > To: Lars-Erik Jonsson (LU/EAB)
> > Cc: West, Mark; Surtees, Abigail; Carsten Bormann; rohc@ietf.org
> > Subject: Re: [rohc] The discussion on slope(s) (redux)
> >=20
> >=20
> >=20
> > On Dec 09 2004, at 13:57 Uhr, Lars-Erik Jonsson (LU/EAB) wrote:
> >=20
> > > Folks,
> > >
> > >>> So in the IP-ID case the non-encoded field grows with SN=20
> > and in the
> > >>> Timestamp case the encoded field grows with SN.
> > >>
> > >> That's my conclusion, which I would put slightly differently:
> > >> With IP-ID, if it is not encoded in the header, it grows in
> > >> parallel SN.
> > >> With TS, if it is not encoded in the header, it grows in
> > >> parallel with TS_STRIDE*SN (independent of Tsc!).
> > >
> > > Which could also be expressed as:
> > > With TS, if it is not encoded in the header, its scaled
> > > representation grows in parallel with TS_STRIDE.
> >=20
> > s/scaled/unscaled/
> >=20
> > (The scaled representation grows in parallel with SN.)
> >=20
> >=20
> > > TS can thus be communicated in three ways:
> > > 1) Unscaled
> >=20
> > ...and sent with WLSB
> >=20
> > > 2) SCALED and sent with WLSB
> > > 3) SCALED, inferred from SN
> >=20
> > Yes.
> >=20
> > > It seems like 1) and 2) are "clear" from 3095, while what=20
> is really
> > > missing is a defined decompression (and thus compression)
> > > logic for 3).
> >=20
> > Well, at least 3095 says that Tsc is 1 in the context, so=20
> > SCALED is the=20
> > more likely interpretation, I'd say.
> >=20
> > > The "default slope" value would be an important
> > > part of that logic, and I guess most implementers have actually
> > > used that value for the simple function
> > > TS_SCALED=3D(SN-SN_OLD)*default_slope + TS_SCALED(SN_OLD)
> > > for decompression of TS_SCALED when no TS bits are sent.
> > >
> > > Q: Would default_slope be used when decompressing based
> > >    on TS bits actually sent?
> >=20
> > No.  4.5.3 is quite clear on what to do.
> >=20
> > > Q: Can default_slope be anything but 1?
> >=20
> > (If Tsc is 1:) No.  See 5.7.
> >=20
> > > Q: Can TS bits ever be omitted when sent unscaled?
> >=20
> > Yes, with an ext3 if Tsc is 0, R-TS is 0, and no TS bits are in the=20
> > base (i.e., UOR-2-ID) header carrying the ext3.
> >=20
> > Gruesse, Carsten
> >=20
>=20
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
>=20

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


