From exim@www1.ietf.org  Mon Mar  1 06:35:38 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11921
	for <rohc-archive@odin.ietf.org>; Mon, 1 Mar 2004 06:35:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxlhX-0001Bv-1q
	for rohc-archive@odin.ietf.org; Mon, 01 Mar 2004 06:35:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21BZBSI004579
	for rohc-archive@odin.ietf.org; Mon, 1 Mar 2004 06:35:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxlhW-0001Bm-TF
	for rohc-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 06:35:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11826
	for <rohc-web-archive@ietf.org>; Mon, 1 Mar 2004 06:35:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxlhS-0001zp-00
	for rohc-web-archive@ietf.org; Mon, 01 Mar 2004 06:35:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxlgP-0001oC-00
	for rohc-web-archive@ietf.org; Mon, 01 Mar 2004 06:34:01 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxlfR-0001ec-00
	for rohc-web-archive@ietf.org; Mon, 01 Mar 2004 06:33:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxlfR-0000xy-L3; Mon, 01 Mar 2004 06:33:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxlfI-0000xL-LD
	for rohc@optimus.ietf.org; Mon, 01 Mar 2004 06:32:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11630
	for <rohc@ietf.org>; Mon, 1 Mar 2004 06:32:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxlfE-0001d7-00
	for rohc@ietf.org; Mon, 01 Mar 2004 06:32:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxleG-0001VI-00
	for rohc@ietf.org; Mon, 01 Mar 2004 06:31:48 -0500
Received: from imh.informatik.uni-bremen.de ([134.102.224.4] helo=informatik.uni-bremen.de)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxldR-0001PQ-00
	for rohc@ietf.org; Mon, 01 Mar 2004 06:30:57 -0500
Received: from [IPv6:::1] (imh.informatik.uni-bremen.de [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id i21BUreb013322;
	Mon, 1 Mar 2004 12:30:55 +0100 (MET)
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <E55646C8-6B73-11D8-89E5-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>
From: Carsten Bormann <cabo@tzi.org>
Date: Mon, 1 Mar 2004 20:30:52 +0900
To: rohc@ietf.org
X-Mailer: Apple Mail (2.612)
Content-Transfer-Encoding: 7bit
Subject: [rohc] Another ad-hoc header compression scheme
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

In mip4, I just learned of a new ad-hoc header compression scheme:
draft-vaarala-mip4-optudp-00.txt "optimizes" out an IP header if it has 
the address previously agreed by some mobileip(v4) negotiation (i.e., 
one context only).
Since one of the motivations of this seems to be mobile VoIP, I pointed 
out that CRTP or ROHC can "optimize" out 37 to 39 bytes, and can do 
multiple contexts, which seems to be one of the requirements from 
multiple people in the room.

However, the header configurations to be compressed weren't quite 
clear, so it wasn't clear how much of the job ROHC could do even when a 
3241-equivalent is defined for mobile IP.
So it's back to finding out about the requirements.

I would like to hear from those who might be interested in working on 
this problem.

Gruesse, Carsten


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



From exim@www1.ietf.org  Mon Mar  1 07:13:21 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13826
	for <rohc-archive@odin.ietf.org>; Mon, 1 Mar 2004 07:13:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxmI0-0004rf-Mo
	for rohc-archive@odin.ietf.org; Mon, 01 Mar 2004 07:12:53 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21CCqFS018693
	for rohc-archive@odin.ietf.org; Mon, 1 Mar 2004 07:12:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxmI0-0004rQ-Fc
	for rohc-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 07:12:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13802
	for <rohc-web-archive@ietf.org>; Mon, 1 Mar 2004 07:12:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxmHz-0005zk-00
	for rohc-web-archive@ietf.org; Mon, 01 Mar 2004 07:12:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxmGy-0005sX-00
	for rohc-web-archive@ietf.org; Mon, 01 Mar 2004 07:11:49 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxmGB-0005ko-00
	for rohc-web-archive@ietf.org; Mon, 01 Mar 2004 07:10:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxmGE-0004kv-Gv; Mon, 01 Mar 2004 07:11:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxmGC-0004kB-5A
	for rohc@optimus.ietf.org; Mon, 01 Mar 2004 07:11:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13578
	for <rohc@ietf.org>; Mon, 1 Mar 2004 07:10:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxmG7-0005k0-00
	for rohc@ietf.org; Mon, 01 Mar 2004 07:10:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxmEw-0005cb-00
	for rohc@ietf.org; Mon, 01 Mar 2004 07:09:42 -0500
Received: from imh.informatik.uni-bremen.de ([134.102.224.4] helo=informatik.uni-bremen.de)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxmE6-0005Xc-00
	for rohc@ietf.org; Mon, 01 Mar 2004 07:08:50 -0500
Received: from [IPv6:::1] (imh.informatik.uni-bremen.de [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id i21C8OEr008384;
	Mon, 1 Mar 2004 13:08:28 +0100 (MET)
In-Reply-To: <004b01c3fbac$a9543280$3405120a@in.huawei.com>
References: <004b01c3fbac$a9543280$3405120a@in.huawei.com>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <1F9FE93A-6B79-11D8-89E5-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: quoted-printable
Cc: Carsten Bormann <cabo@tzi.org>, rohc@ietf.org
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] SIP and SigComp
Date: Mon, 1 Mar 2004 21:08:17 +0900
To: Jaspreet Singh <jaspreet@huawei.com>
X-Mailer: Apple Mail (2.612)
Content-Transfer-Encoding: quoted-printable
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

On Feb 25 2004, at 15:35 Uhr, Jaspreet Singh wrote:

> Hi,
> =A0
> Is there any recommended compression algorithm for compressing SIP=20
> using sigcomp ?

Jaspreet,

you are probably aware that the whole point of SigComp is that there is=20=

no need to agree on compression algorithms to achieve interoperability.
So I read your question as "what are good compression algorithms that=20
could be used for compressing SIP with SigComp?".

Research papers that attempt to answer this question are starting to=20
appear.
Clearly, important issues that haven't been discussed in the existing=20
literature are:

-- balancing decompressor code size with compression efficiency
-- extracting maximum benefit from state management
-- making good use of the static SIP/SDP dictionary (RFC 3485)=20

Gruesse, Carsten


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



From exim@www1.ietf.org  Mon Mar  1 07:52:35 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16049
	for <rohc-archive@odin.ietf.org>; Mon, 1 Mar 2004 07:52:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axmtz-0008A8-B5
	for rohc-archive@odin.ietf.org; Mon, 01 Mar 2004 07:52:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21Cq6Xh031358
	for rohc-archive@odin.ietf.org; Mon, 1 Mar 2004 07:52:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axmtx-00089X-Is
	for rohc-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 07:52:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15938
	for <rohc-web-archive@ietf.org>; Mon, 1 Mar 2004 07:52:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axmtw-0002vl-00
	for rohc-web-archive@ietf.org; Mon, 01 Mar 2004 07:52:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxmsU-0002Z6-00
	for rohc-web-archive@ietf.org; Mon, 01 Mar 2004 07:50:35 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axmqu-0002Ci-00
	for rohc-web-archive@ietf.org; Mon, 01 Mar 2004 07:48:56 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AxmdW-0005yz-Qn
	for rohc-web-archive@ietf.org; Mon, 01 Mar 2004 07:35:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxmdT-0005m2-PG; Mon, 01 Mar 2004 07:35:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxmdB-0005kl-89
	for rohc@optimus.ietf.org; Mon, 01 Mar 2004 07:34:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14889
	for <rohc@ietf.org>; Mon, 1 Mar 2004 07:34:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxmdA-0000gB-00
	for rohc@ietf.org; Mon, 01 Mar 2004 07:34:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxmcK-0000ZB-00
	for rohc@ietf.org; Mon, 01 Mar 2004 07:33:53 -0500
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxmbU-0000MM-00
	for rohc@ietf.org; Mon, 01 Mar 2004 07:33:00 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <1ZGMLR75>; Mon, 1 Mar 2004 12:32:29 -0000
Message-ID: <EA943CD30BCB104E9D38F5B5DC2D9A7014615D@rsys004a.roke.co.uk>
From: "Price, Richard" <richard.price@roke.co.uk>
To: "'Jaspreet Singh'" <jaspreet@huawei.com>, rohc@ietf.org
Subject: RE: [rohc] SIP and SigComp
Date: Mon, 1 Mar 2004 12:32:39 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="gb2312"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Hi Jaspreet,

The SigComp User Guide has bytecode for five compression
algorithms that can be used for compressing SIP: these
are LZSS, LZW, DEFLATE, LZJH and EPIC. Any of these
algorithms will give a good performance when compressing
SIP messages.

We don't recommend a single "best" algorithm for SIP
because there isn't one: the best algorithm for you
depends on whether you're interested in high compression
radio, low processing and memory requirements, simple
design etc., and whether you're worried about using
IPR-encumbered technology. SigComp lets each implementer
make their own choice of compression algorithm.

The current version of the user guide has just expired
(oops - must remember to update it), but is available from:

http://www.roke.co.uk/networks/epic/draft-ietf-rohc-sigcomp-user-guide-00.tx
t

Regards,

Richard

-----Original Message-----
From: Jaspreet Singh [mailto:jaspreet@huawei.com]
Sent: Wednesday, February 25, 2004 2:36 PM
To: rohc@ietf.org
Subject: [rohc] SIP and SigComp


Hi,

Is there any recommended compression algorithm for compressing SIP using
sigcomp ? 

Can someone please point me to a web resource which analyses how different
compression algorithms perform when used along with sigcomp for compressing
SIP.

Cheers,
Jaspreet

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



From exim@www1.ietf.org  Mon Mar  1 21:24:36 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23728
	for <rohc-archive@odin.ietf.org>; Mon, 1 Mar 2004 21:24:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzZq-0006rR-2W
	for rohc-archive@odin.ietf.org; Mon, 01 Mar 2004 21:24:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i222OATY026372
	for rohc-archive@odin.ietf.org; Mon, 1 Mar 2004 21:24:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzZp-0006rH-VA
	for rohc-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 21:24:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23640
	for <rohc-web-archive@ietf.org>; Mon, 1 Mar 2004 21:24:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzZn-0007Jo-00
	for rohc-web-archive@ietf.org; Mon, 01 Mar 2004 21:24:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxzYn-00078p-00
	for rohc-web-archive@ietf.org; Mon, 01 Mar 2004 21:23:06 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzXm-0006xo-00
	for rohc-web-archive@ietf.org; Mon, 01 Mar 2004 21:22:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzXn-0006Rc-Lv; Mon, 01 Mar 2004 21:22:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzXE-0006OM-C7
	for rohc@optimus.ietf.org; Mon, 01 Mar 2004 21:21:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23489
	for <rohc@ietf.org>; Mon, 1 Mar 2004 21:21:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzXB-0006sL-00
	for rohc@ietf.org; Mon, 01 Mar 2004 21:21:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxzWB-0006kB-00
	for rohc@ietf.org; Mon, 01 Mar 2004 21:20:24 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzVX-0006cc-00
	for rohc@ietf.org; Mon, 01 Mar 2004 21:19:43 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i222JhYG020334
	for <rohc@ietf.org>; Tue, 2 Mar 2004 03:19:43 +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.0);
	 Tue, 2 Mar 2004 03:19:42 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <FYFVAHGB>; Tue, 2 Mar 2004 03:19:42 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E9480@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Tue, 2 Mar 2004 03:19:08 +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 Mar 2004 02:19:42.0935 (UTC) FILETIME=[D2C31E70:01C3FFFC]
Subject: [rohc] Another 3095 interop?
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

ROHCers,

We have not had an interop since November 2002, which means the 
interoperability status is not progressing. Who would be interested
in participating in another 3095 interop? Potentially, we could 
also consider testing some of the newer profiles, such as IP-only.

Comments to the list, or to me.

Cheers,
/L-E

--------------------------------------
Lars-Erik Jonsson
IETF ROHC WG Chair
E-mail: lars-erik.jonsson@ericsson.com
Phone: +46 920 20 21 07
Home: +46 920 999 57

My opinions are my personal opinions and should not be considered
as the opinions of my employer, if not explicitly stated. At the
end of this message, my employer might have automatically inserted
a stupid disclaimer. This nonsense is out of my control and should
simply be ignored.


This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Mon Mar  1 21:47:58 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24919
	for <rohc-archive@odin.ietf.org>; Mon, 1 Mar 2004 21:47:57 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzwQ-0000Rl-92
	for rohc-archive@odin.ietf.org; Mon, 01 Mar 2004 21:47:30 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i222lU9C001714
	for rohc-archive@odin.ietf.org; Mon, 1 Mar 2004 21:47:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzwQ-0000RZ-3U
	for rohc-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 21:47:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24766
	for <rohc-web-archive@ietf.org>; Mon, 1 Mar 2004 21:47:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzwN-0002Sg-00
	for rohc-web-archive@ietf.org; Mon, 01 Mar 2004 21:47:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxzvD-0002En-00
	for rohc-web-archive@ietf.org; Mon, 01 Mar 2004 21:46:16 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axzur-00028H-03
	for rohc-web-archive@ietf.org; Mon, 01 Mar 2004 21:45:53 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Axzr8-0007fp-A3
	for rohc-web-archive@ietf.org; Mon, 01 Mar 2004 21:42:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axzr7-0000EQ-BI; Mon, 01 Mar 2004 21:42:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzqF-0000Ct-J5
	for rohc@optimus.ietf.org; Mon, 01 Mar 2004 21:41:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24672
	for <rohc@ietf.org>; Mon, 1 Mar 2004 21:41:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzqC-0001mr-00
	for rohc@ietf.org; Mon, 01 Mar 2004 21:41:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxzpI-0001iI-00
	for rohc@ietf.org; Mon, 01 Mar 2004 21:40:08 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axzp5-0001dJ-00
	for rohc@ietf.org; Mon, 01 Mar 2004 21:39:55 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i222dtqY017801
	for <rohc@ietf.org>; Tue, 2 Mar 2004 03:39:56 +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.0);
	 Tue, 2 Mar 2004 03:39:55 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <FYFVAKWB>; Tue, 2 Mar 2004 03:39:55 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E9481@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Tue, 2 Mar 2004 03:39:21 +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 Mar 2004 02:39:55.0857 (UTC) FILETIME=[A5B85410:01C3FFFF]
Subject: [rohc] UDP-Lite profile, feedback requested
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

ROHCers,

The UDP-Lite profile has been rather stable for a long time and
we should soon consider shipping it to the IESG. Before we issue
a WG last-call, please let us know if there are any significant
issues left.

Rgds,
/L-E

--------------------------------------
Lars-Erik Jonsson
IETF ROHC WG Chair
E-mail: lars-erik.jonsson@ericsson.com
Phone: +46 920 20 21 07
Home: +46 920 999 57

My opinions are my personal opinions and should not be considered
as the opinions of my employer, if not explicitly stated. At the
end of this message, my employer might have automatically inserted
a stupid disclaimer. This nonsense is out of my control and should
simply be ignored.


This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Wed Mar  3 08:30:53 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25958
	for <rohc-archive@odin.ietf.org>; Wed, 3 Mar 2004 08:30:48 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyWS3-0003ve-DL
	for rohc-archive@odin.ietf.org; Wed, 03 Mar 2004 08:30:19 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i23DUJuC015102
	for rohc-archive@odin.ietf.org; Wed, 3 Mar 2004 08:30:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyWS3-0003vV-0H
	for rohc-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 08:30:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25933
	for <rohc-web-archive@ietf.org>; Wed, 3 Mar 2004 08:29:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyWRN-00027v-00
	for rohc-web-archive@ietf.org; Wed, 03 Mar 2004 08:29:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyWQS-0001yh-00
	for rohc-web-archive@ietf.org; Wed, 03 Mar 2004 08:28:41 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyWPr-0001ou-00
	for rohc-web-archive@ietf.org; Wed, 03 Mar 2004 08:28:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyWPo-0003i6-OS; Wed, 03 Mar 2004 08:28:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyWOn-0003g7-EF
	for rohc@optimus.ietf.org; Wed, 03 Mar 2004 08:27:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25729
	for <rohc@ietf.org>; Wed, 3 Mar 2004 08:26:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyWOH-0001Ze-00
	for rohc@ietf.org; Wed, 03 Mar 2004 08:26:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyWNI-0001Nb-00
	for rohc@ietf.org; Wed, 03 Mar 2004 08:25:25 -0500
Received: from [194.237.235.30] (helo=effnet.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyWMN-00013q-00
	for rohc@ietf.org; Wed, 03 Mar 2004 08:24:27 -0500
Received: from effnet.com (internal.effnet.com [192.168.100.151] (may be forged))
	(authenticated bits=0)
	by effnet.com (8.12.3/8.12.3) with ESMTP id i23CNhU2023075
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Wed, 3 Mar 2004 13:23:43 +0100
Message-ID: <4045DAA5.5060506@effnet.com>
Date: Wed, 03 Mar 2004 14:16:21 +0100
From: Tommy Lundemo <tommy.lundemo@effnet.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030821
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
CC: "'rohc@ietf.org'" <rohc@ietf.org>
Subject: Re: [rohc] Another 3095 interop?
References: <A943FD84BD9ED41193460008C7918050072E9480@ESEALNT419.al.sw.ericsson.se>
In-Reply-To: <A943FD84BD9ED41193460008C7918050072E9480@ESEALNT419.al.sw.ericsson.se>
X-Enigmail-Version: 0.76.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi all,

Effnet is interested in this.
Especially for the advanced features of ROHC that have not yet been tested.

BR,
 Tommy Lundemo, Effnet AB


Lars-Erik Jonsson (LU/EAB) wrote:

>ROHCers,
>
>We have not had an interop since November 2002, which means the 
>interoperability status is not progressing. Who would be interested
>in participating in another 3095 interop? Potentially, we could 
>also consider testing some of the newer profiles, such as IP-only.
>
>Comments to the list, or to me.
>
>Cheers,
>/L-E
>
>--------------------------------------
>Lars-Erik Jonsson
>IETF ROHC WG Chair
>E-mail: lars-erik.jonsson@ericsson.com
>Phone: +46 920 20 21 07
>Home: +46 920 999 57
>
>My opinions are my personal opinions and should not be considered
>as the opinions of my employer, if not explicitly stated. At the
>end of this message, my employer might have automatically inserted
>a stupid disclaimer. This nonsense is out of my control and should
>simply be ignored.
>
>
>This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.
>
>E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.
>
>
>_______________________________________________
>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 exim@www1.ietf.org  Wed Mar  3 09:14:55 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28852
	for <rohc-archive@odin.ietf.org>; Wed, 3 Mar 2004 09:14:55 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyX8k-0002VF-Nl
	for rohc-archive@odin.ietf.org; Wed, 03 Mar 2004 09:14:27 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i23EEQII009615
	for rohc-archive@odin.ietf.org; Wed, 3 Mar 2004 09:14:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyX8k-0002V0-IH
	for rohc-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 09:14:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28778
	for <rohc-web-archive@ietf.org>; Wed, 3 Mar 2004 09:14:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyX8i-0002zj-00
	for rohc-web-archive@ietf.org; Wed, 03 Mar 2004 09:14:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyX7f-0002ig-00
	for rohc-web-archive@ietf.org; Wed, 03 Mar 2004 09:13:20 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyX6R-0002Q3-00
	for rohc-web-archive@ietf.org; Wed, 03 Mar 2004 09:12:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyX6R-0002If-Ny; Wed, 03 Mar 2004 09:12:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyX6N-0002I2-UR
	for rohc@optimus.ietf.org; Wed, 03 Mar 2004 09:12:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28424
	for <rohc@ietf.org>; Wed, 3 Mar 2004 09:11:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyX6M-0002PE-00
	for rohc@ietf.org; Wed, 03 Mar 2004 09:11:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyX55-00026f-00
	for rohc@ietf.org; Wed, 03 Mar 2004 09:10:39 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyX44-0001rM-00
	for rohc@ietf.org; Wed, 03 Mar 2004 09:09:36 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i23E9ZYG023191
	for <rohc@ietf.org>; Wed, 3 Mar 2004 15:09:35 +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.0);
	 Wed, 3 Mar 2004 15:09:35 +0100
Received: from caffreys (caffreys.ericsson.se [147.214.181.21]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id FYFVQ26K; Wed, 3 Mar 2004 15:09:35 +0100
Date: Wed, 3 Mar 2004 15:15:09 +0100 (CET)
From: Vicknesan Ayadurai <vicknesan.ayadurai@ericsson.com>
X-X-Sender: vick@caffreys.ericsson.se
To: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
cc: "'rohc@ietf.org'" <rohc@ietf.org>
Subject: Re: [rohc] Another 3095 interop?
In-Reply-To: <A943FD84BD9ED41193460008C7918050072E9480@ESEALNT419.al.sw.ericsson.se>
Message-ID: <20040303132746.M5658-100000@caffreys.ericsson.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-OriginalArrivalTime: 03 Mar 2004 14:09:35.0182 (UTC) FILETIME=[2821FEE0:01C40129]
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Hi Lars-Erik/ROHC'ers,

I think Ericsson would be interested to participate in another interop
event, if someone organised it :-)

I guess we probably need to discuss beforehand the functions/features
to test as well if this does take place.

Regards,
vick
+----------------------------------------------------+
 Vicknesan AYADURAI <vicknesan.ayadurai@ericsson.com>
 Ericsson Research: IP Networks - Stockholm, Sweden
 Phone :  +46 8 5087 8084 / Fax:  +46 8 404 7020
+----------------------------------------------------+

On Tue, 2 Mar 2004, Lars-Erik Jonsson (LU/EAB) wrote:

> ROHCers,
>
> We have not had an interop since November 2002, which means the
> interoperability status is not progressing. Who would be interested
> in participating in another 3095 interop? Potentially, we could
> also consider testing some of the newer profiles, such as IP-only.
>
> Comments to the list, or to me.
>
> Cheers,
> /L-E
>
> --------------------------------------
> Lars-Erik Jonsson
> IETF ROHC WG Chair
> E-mail: lars-erik.jonsson@ericsson.com
> Phone: +46 920 20 21 07
> Home: +46 920 999 57
>
> My opinions are my personal opinions and should not be considered
> as the opinions of my employer, if not explicitly stated. At the
> end of this message, my employer might have automatically inserted
> a stupid disclaimer. This nonsense is out of my control and should
> simply be ignored.
>
>
> This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.
>
> E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.
>
>
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
>



This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Mon Mar  8 04:42:06 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21578
	for <rohc-archive@odin.ietf.org>; Mon, 8 Mar 2004 04:42:06 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0HGQ-0003Ql-9D
	for rohc-archive@odin.ietf.org; Mon, 08 Mar 2004 04:41:37 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i289fYHR013185
	for rohc-archive@odin.ietf.org; Mon, 8 Mar 2004 04:41:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0HGO-0003QY-Nm
	for rohc-web-archive@optimus.ietf.org; Mon, 08 Mar 2004 04:41:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21572
	for <rohc-web-archive@ietf.org>; Mon, 8 Mar 2004 04:41:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0HGL-0001n8-00
	for rohc-web-archive@ietf.org; Mon, 08 Mar 2004 04:41:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0HFO-0001dy-00
	for rohc-web-archive@ietf.org; Mon, 08 Mar 2004 04:40:31 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0HEy-0001Um-00
	for rohc-web-archive@ietf.org; Mon, 08 Mar 2004 04:40:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0HEx-0003LC-Ht; Mon, 08 Mar 2004 04:40:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0HEF-0003Ij-NJ
	for rohc@optimus.ietf.org; Mon, 08 Mar 2004 04:39:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21460
	for <rohc@ietf.org>; Mon, 8 Mar 2004 04:39:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0HEC-0001SC-00
	for rohc@ietf.org; Mon, 08 Mar 2004 04:39:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0HDE-0001J1-00
	for rohc@ietf.org; Mon, 08 Mar 2004 04:38:16 -0500
Received: from mta2.huawei.com ([61.144.161.24] helo=huawei.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0HBy-00013E-00
	for rohc@ietf.org; Mon, 08 Mar 2004 04:37:10 -0500
Received: from huawei.com (localhost [127.0.0.1])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0HU900AOX42SQ8@mta2.huawei.com> for rohc@ietf.org; Mon,
 08 Mar 2004 17:37:40 +0800 (CST)
Received: from mailin.huawei.com ([10.18.1.252])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0HU900B2G42RCZ@mta2.huawei.com> for rohc@ietf.org; Mon,
 08 Mar 2004 17:37:40 +0800 (CST)
Received: from JAKKIS ([10.18.5.200])
 by mailin.huawei.com (Netscape Messaging Server 4.15)
 with ESMTP id HU948500.30U for <rohc@ietf.org>; Mon, 08 Mar 2004 17:40:53 +0800
Date: Mon, 08 Mar 2004 15:11:56 +0530
From: sasidhar <jakkis@huawei.com>
To: rohc@ietf.org
Reply-to: sasidhar <jakkis@huawei.com>
Message-id: <00db01c404f1$989f1b50$c805120a@in.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
Content-type: multipart/alternative;
 boundary="Boundary_(ID_C4vG/1rEnpGTxKuG8dc34A)"
X-Priority: 3
X-MSMail-priority: Normal
Subject: [rohc] Regd. generation of state identifier for SIP static dictionary(rfc
 3485)
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,HTML_20_30,
	HTML_FONTCOLOR_BLUE,HTML_FONTCOLOR_RED,HTML_MESSAGE autolearn=no 
	version=2.60

This is a multi-part message in MIME format.

--Boundary_(ID_C4vG/1rEnpGTxKuG8dc34A)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

We tried to generate the 20-byte SHA-1 hash (RFC-3174) over the byte string formed by concatenating the state_length, state_address, state_instruction, minimum_access_length and state_value(in that order) with the values given in the rfc 3485 (pg.7) for the static dictionary. The result didnot match with the state-identifier given for the same.The procedure we followed is according to the rfc 3320. I have verified the input many times and even with different implementations of SHA-1 hash, but it didn't work. This is very important and urgent. Please help me out of this problem. 

Thanks and regards,
Sasidhar

--Boundary_(ID_C4vG/1rEnpGTxKuG8dc34A)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>We tried to generate the 20-byte <FONT 
color=#0000ff>SHA-1</FONT> hash (RFC-<STRONG>3174)</STRONG> over the byte string 
formed by concatenating&nbsp;the state_length, 
state_address,&nbsp;state_instruction, minimum_access_length and state_value(in 
that order)&nbsp;with the <FONT color=#0000ff>values given in the rfc 3485 
(pg.7) for the static dictionary</FONT>. The result <FONT color=#ff0000>didnot 
match</FONT> with the state-identifier given for the same.The procedure we 
followed is according to the rfc <STRONG>3320</STRONG>. I have verified the 
input many times and even with different&nbsp;implementations of SHA-1 
hash,&nbsp;but it didn't work.&nbsp;This is very important and urgent. Please 
help me out of this problem. </FONT>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Thanks and regards,</FONT></DIV>
<DIV><FONT face=Arial size=2>Sasidhar</FONT></DIV></DIV></BODY></HTML>

--Boundary_(ID_C4vG/1rEnpGTxKuG8dc34A)--

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



From exim@www1.ietf.org  Mon Mar  8 05:34:00 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23409
	for <rohc-archive@odin.ietf.org>; Mon, 8 Mar 2004 05:33:59 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0I4j-0006nk-DD
	for rohc-archive@odin.ietf.org; Mon, 08 Mar 2004 05:33:33 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i28AXXtw026144
	for rohc-archive@odin.ietf.org; Mon, 8 Mar 2004 05:33:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0I4j-0006nb-5G
	for rohc-web-archive@optimus.ietf.org; Mon, 08 Mar 2004 05:33:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23392
	for <rohc-web-archive@ietf.org>; Mon, 8 Mar 2004 05:33:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0I4f-0002aH-00
	for rohc-web-archive@ietf.org; Mon, 08 Mar 2004 05:33:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0I3g-0002RP-00
	for rohc-web-archive@ietf.org; Mon, 08 Mar 2004 05:32:28 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0I3D-0002If-00
	for rohc-web-archive@ietf.org; Mon, 08 Mar 2004 05:31:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0I3F-0006kM-Gf; Mon, 08 Mar 2004 05:32:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0I2i-0006jh-NT
	for rohc@optimus.ietf.org; Mon, 08 Mar 2004 05:31:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23348
	for <rohc@ietf.org>; Mon, 8 Mar 2004 05:31:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0I2f-0002I8-00
	for rohc@ietf.org; Mon, 08 Mar 2004 05:31:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0I1i-0002A8-00
	for rohc@ietf.org; Mon, 08 Mar 2004 05:30:26 -0500
Received: from bay12-f102.bay12.hotmail.com ([64.4.35.102] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0I1C-000212-00
	for rohc@ietf.org; Mon, 08 Mar 2004 05:29:54 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Mon, 8 Mar 2004 02:29:24 -0800
Received: from 62.254.246.40 by by12fd.bay12.hotmail.msn.com with HTTP;
	Mon, 08 Mar 2004 10:29:24 GMT
X-Originating-IP: [62.254.246.40]
X-Originating-Email: [ellyptic@hotmail.com]
X-Sender: ellyptic@hotmail.com
From: "Richard Price" <ellyptic@hotmail.com>
To: jakkis@huawei.com, rohc@ietf.org
Subject: RE: [rohc] Regd. generation of state identifier for SIP static dictionary(rfc
 3485)
Date: Mon, 08 Mar 2004 10:29:24 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <BAY12-F102WNDIT6bB500005df0@hotmail.com>
X-OriginalArrivalTime: 08 Mar 2004 10:29:24.0345 (UTC) FILETIME=[39ECFE90:01C404F8]
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Sasidhar,

The first thing to check is that your implementation of SHA-1
passes the four tests specified in RFC-3174.

Assuming that this is the case, the problem might lie in the input
that you're passing to the SHA-1 hash. One point to note is that
the state_length, state_address, state_instruction and
minimum_access_length are all 2-byte values. It might also be
worth checking that you've remembered to delete the leftmost
column of RFC-3485, because this column contains line numbers
only, and is not part of the static dictionary itself.

Could you verify that the first 48 bytes you're passing to the
SHA-1 hash are as follows:

0x12e4 0000 0000 0006 0d0a 5265 6a65 6374
0x2d43 6f6e 7461 6374 3a20 0d0a 4572 726f
0x722d 496e 666f 3a20 0d0a 5469 6d65 7374 ...

Regards,

Richard


>From: sasidhar <jakkis@huawei.com>
>Reply-To: sasidhar <jakkis@huawei.com>
>To: rohc@ietf.org
>Subject: [rohc] Regd. generation of state identifier for SIP static 
>dictionary(rfc 3485)
>Date: Mon, 08 Mar 2004 15:11:56 +0530
>
>We tried to generate the 20-byte SHA-1 hash (RFC-3174) over the byte string 
>formed by concatenating the state_length, state_address, state_instruction, 
>minimum_access_length and state_value(in that order) with the values given 
>in the rfc 3485 (pg.7) for the static dictionary. The result didnot match 
>with the state-identifier given for the same.The procedure we followed is 
>according to the rfc 3320. I have verified the input many times and even 
>with different implementations of SHA-1 hash, but it didn't work. This is 
>very important and urgent. Please help me out of this problem.
>
>Thanks and regards,
>Sasidhar

_________________________________________________________________
Tired of 56k? Get a FREE BT Broadband connection 
http://www.msn.co.uk/specials/btbroadband


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



From exim@www1.ietf.org  Fri Mar 12 17:48:16 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23904
	for <rohc-archive@odin.ietf.org>; Fri, 12 Mar 2004 17:48:16 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1vRV-0000hy-JE
	for rohc-archive@odin.ietf.org; Fri, 12 Mar 2004 17:47:49 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2CMlnpN002716
	for rohc-archive@odin.ietf.org; Fri, 12 Mar 2004 17:47:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1vRV-0000hj-EP
	for rohc-web-archive@optimus.ietf.org; Fri, 12 Mar 2004 17:47:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23871
	for <rohc-web-archive@ietf.org>; Fri, 12 Mar 2004 17:47:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1vRS-0004n2-00
	for rohc-web-archive@ietf.org; Fri, 12 Mar 2004 17:47:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1vQY-0004jg-00
	for rohc-web-archive@ietf.org; Fri, 12 Mar 2004 17:46:50 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1vPn-0004hb-00
	for rohc-web-archive@ietf.org; Fri, 12 Mar 2004 17:46:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1vPm-0000dD-76; Fri, 12 Mar 2004 17:46:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1vPe-0000cV-U0
	for rohc@optimus.ietf.org; Fri, 12 Mar 2004 17:45:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23814
	for <rohc@ietf.org>; Fri, 12 Mar 2004 17:45:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1vPc-0004gG-00
	for rohc@ietf.org; Fri, 12 Mar 2004 17:45:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1vOk-0004dS-00
	for rohc@ietf.org; Fri, 12 Mar 2004 17:44:58 -0500
Received: from [216.90.186.146] (helo=mail.ipnetfusion.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1vNr-0004Sw-00
	for rohc@ietf.org; Fri, 12 Mar 2004 17:44:03 -0500
Received: from ipnetfusion.com (pc223 [192.1.2.223])
	(authenticated)
	by mail.ipnetfusion.com (8.11.6/8.11.6) with ESMTP id i2CMgfG23120
	for <rohc@ietf.org>; Fri, 12 Mar 2004 16:42:41 -0600
Message-ID: <40523CE4.9070602@ipnetfusion.com>
Date: Fri, 12 Mar 2004 16:42:44 -0600
From: Chintan Thakker <cthakker@ipnetfusion.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030723 Thunderbird/0.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "'rohc@ietf.org'" <rohc@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [rohc] Usage of SIP/SDP dictionary during compression
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,
 For SIP/Sigcomp when we say that SIP/SDP dictionary is mandatory, do we 
mean that all compression algorithms must use it ?
 I understand it is mandatory for UDVM and not using the SIP/SDP library 
while compressing might impair the compression ratio.

 Thank you,

 Chintan
 ipNetFusion, TX


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



From exim@www1.ietf.org  Sat Mar 13 00:35:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14429
	for <rohc-archive@odin.ietf.org>; Sat, 13 Mar 2004 00:35:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B21nY-0004Ky-3G
	for rohc-archive@odin.ietf.org; Sat, 13 Mar 2004 00:35:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2D5Z01H016666
	for rohc-archive@odin.ietf.org; Sat, 13 Mar 2004 00:35:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B21nX-0004Kj-TP
	for rohc-web-archive@optimus.ietf.org; Sat, 13 Mar 2004 00:34:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14415
	for <rohc-web-archive@ietf.org>; Sat, 13 Mar 2004 00:34:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B21nV-0007BE-00
	for rohc-web-archive@ietf.org; Sat, 13 Mar 2004 00:34:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B21mY-00079I-00
	for rohc-web-archive@ietf.org; Sat, 13 Mar 2004 00:33:58 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B21lb-00077X-00
	for rohc-web-archive@ietf.org; Sat, 13 Mar 2004 00:32:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B21lc-0004C0-Uz; Sat, 13 Mar 2004 00:33:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B21kf-0004BU-B1
	for rohc@optimus.ietf.org; Sat, 13 Mar 2004 00:32:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14391
	for <rohc@ietf.org>; Sat, 13 Mar 2004 00:31:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B21kc-00075V-00
	for rohc@ietf.org; Sat, 13 Mar 2004 00:31:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B21jk-00073m-00
	for rohc@ietf.org; Sat, 13 Mar 2004 00:31:05 -0500
Received: from mailrelay2.lntinfotech.com ([203.199.54.34])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B21j8-0006ya-00
	for rohc@ietf.org; Sat, 13 Mar 2004 00:30:27 -0500
Received: from Bangalore.lntinfotech.com ([107.108.204.3])
          by mailrelay2.lntinfotech.com (Lotus Domino Release 5.0.12)
          with ESMTP id 2004031310594960:11368 ;
          Sat, 13 Mar 2004 10:59:49 +0530 
To: rohc@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF85843B27.1BB82406-ON65256E56.001D6126@lntinfotech.com>
From: "Jagan S" <Jagan.S@lntinfotech.com>
Date: Sat, 13 Mar 2004 10:57:50 +0530
MIME-Version: 1.0
X-MIMETrack: Serialize by Router on BANGALORE/LNTINFOTECH(Release 5.0.9 |November 16, 2001) at
 03/13/2004 10:57:50 AM,
	Itemize by SMTP Server on MAILRELAY2/LNTINFOTECH(Release 5.0.12  |February
 13, 2003) at 03/13/2004 10:59:49 AM,
	Serialize by Router on MAILRELAY2/LNTINFOTECH(Release 5.0.12  |February 13, 2003) at
 03/13/2004 11:00:28 AM,
	Serialize complete at 03/13/2004 11:00:28 AM
Content-type: text/plain; charset=us-ascii
Subject: [rohc] ROHC: Header parsing
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Hi,

3095 specifies context identification at compressor  by parsing RTP/UDP/IP
header fields.

Yes. We can identify IP header by analyzing :' Version' / 'Length' fields
of IP header.
UDP header by analyzing: 'protocol type' field from IP header

My question is about: How to identify the presence of RTP header ?


Thanks in advance
- Jagan
.............................................................................................................................................................................................................




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



From exim@www1.ietf.org  Tue Mar 16 04:40:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20843
	for <rohc-archive@odin.ietf.org>; Tue, 16 Mar 2004 04:40:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3B39-0004pe-JA
	for rohc-archive@odin.ietf.org; Tue, 16 Mar 2004 04:40:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2G9dpdW018570
	for rohc-archive@odin.ietf.org; Tue, 16 Mar 2004 04:39:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3B38-0004pR-QQ
	for rohc-web-archive@optimus.ietf.org; Tue, 16 Mar 2004 04:39:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20830
	for <rohc-web-archive@ietf.org>; Tue, 16 Mar 2004 04:39:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3B35-0007CN-00
	for rohc-web-archive@ietf.org; Tue, 16 Mar 2004 04:39:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3B26-00077p-00
	for rohc-web-archive@ietf.org; Tue, 16 Mar 2004 04:38:46 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3B1a-00072t-00
	for rohc-web-archive@ietf.org; Tue, 16 Mar 2004 04:38:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3B1V-0004Sh-Rt; Tue, 16 Mar 2004 04:38:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3B0f-0004Gd-NT
	for rohc@optimus.ietf.org; Tue, 16 Mar 2004 04:37:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20646
	for <rohc@ietf.org>; Tue, 16 Mar 2004 04:37:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3B0c-0006vi-00
	for rohc@ietf.org; Tue, 16 Mar 2004 04:37:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3AzZ-0006m9-00
	for rohc@ietf.org; Tue, 16 Mar 2004 04:36:09 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3Ayf-0006dC-00
	for rohc@ietf.org; Tue, 16 Mar 2004 04:35:13 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2G9ZEqY007968
	for <rohc@ietf.org>; Tue, 16 Mar 2004 10:35:14 +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.0);
	 Tue, 16 Mar 2004 10:35:13 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <GX1HL5WM>; Tue, 16 Mar 2004 10:35:13 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E94AC@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'Jagan S'" <Jagan.S@lntinfotech.com>, rohc@ietf.org
Subject: RE: [rohc] ROHC: Header parsing
Date: Tue, 16 Mar 2004 10:34: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: 16 Mar 2004 09:35:13.0743 (UTC) FILETIME=[FBB87DF0:01C40B39]
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Jagan,

There is no way to explicitly know that packet stream is 
an RTP stream, but one will have to guess. The good thing
with ROHC IP/UDP/RTP compression is that it is lossless,
independent of if the UDP payload is actually RTP or not.
One can thus start with assuming RTP, and if the compression
ratio turns out to be negative for the RTP part, a profile
switch to IP/UDP-only should be performed (see section 5.11).

Cheers,
/L-E


> -----Original Message-----
> From: rohc-admin@ietf.org [mailto:rohc-admin@ietf.org]On 
> Behalf Of Jagan
> S
> Sent: den 13 mars 2004 06:28
> To: rohc@ietf.org
> Subject: [rohc] ROHC: Header parsing
> 
> 
> Hi,
> 
> 3095 specifies context identification at compressor  by 
> parsing RTP/UDP/IP
> header fields.
> 
> Yes. We can identify IP header by analyzing :' Version' / 
> 'Length' fields
> of IP header.
> UDP header by analyzing: 'protocol type' field from IP header
> 
> My question is about: How to identify the presence of RTP header ?
> 
> 
> Thanks in advance
> - Jagan
> ..............................................................
> ..............................................................
> ..............................................................
> ...................
> 
> 
> 
> 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
> 

This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Tue Mar 16 04:59:15 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21577
	for <rohc-archive@odin.ietf.org>; Tue, 16 Mar 2004 04:59:15 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3BLU-00062u-BY
	for rohc-archive@odin.ietf.org; Tue, 16 Mar 2004 04:58:48 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2G9wm4p023237
	for rohc-archive@odin.ietf.org; Tue, 16 Mar 2004 04:58:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3BLT-00062X-Jh
	for rohc-web-archive@optimus.ietf.org; Tue, 16 Mar 2004 04:58:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21554
	for <rohc-web-archive@ietf.org>; Tue, 16 Mar 2004 04:58:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3BLP-000105-00
	for rohc-web-archive@ietf.org; Tue, 16 Mar 2004 04:58:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3BKU-0000uy-00
	for rohc-web-archive@ietf.org; Tue, 16 Mar 2004 04:57:47 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3BJk-0000q4-00
	for rohc-web-archive@ietf.org; Tue, 16 Mar 2004 04:57:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3BJm-0005tj-Pc; Tue, 16 Mar 2004 04:57:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2qHA-0001Gm-Md
	for rohc@optimus.ietf.org; Mon, 15 Mar 2004 06:28:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21409
	for <rohc@ietf.org>; Mon, 15 Mar 2004 06:28:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2qH6-0006RP-00
	for rohc@ietf.org; Mon, 15 Mar 2004 06:28:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B2qGF-0006Jo-00
	for rohc@ietf.org; Mon, 15 Mar 2004 06:28:00 -0500
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2qFf-0006BB-00
	for rohc@ietf.org; Mon, 15 Mar 2004 06:27:24 -0500
Received: from courrier.rennes.enst-bretagne.fr (f1-clust.rennes.enst-bretagne.fr [193.52.74.16])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with ESMTP id i2FBQec23393;
	Mon, 15 Mar 2004 12:26:45 +0100
Received: from pcrsm7 ([193.52.74.238])
	by courrier.rennes.enst-bretagne.fr (8.11.6p2/8.11.6) with SMTP id i2FBQZh18431;
	Mon, 15 Mar 2004 12:26:35 +0100 (MET)
Message-ID: <03ba01c40a80$62eb83b0$ee4a34c1@rennes.enstbretagne.fr>
From: "kamal deep singh" <kd.singh@enst-bretagne.fr>
To: <rohc@ietf.org>, "Jagan S" <Jagan.S@lntinfotech.com>
References: <OF85843B27.1BB82406-ON65256E56.001D6126@lntinfotech.com>
Subject: Re: [rohc] ROHC: Header parsing
Date: Mon, 15 Mar 2004 12:26:34 +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.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

hi,

We can discuss that.

I use RTP version field and also I look at the values
where SN field is supposed to be there. If the values are showing sequential
behaviour then it should be SN and header should be RTP.

This can be extended further to check TS. If TS is showing the expected
behaviour of
TS = n*TS_STRIDE + TS_OFFSET (n is an integer and all others constant) then
it should be TS.

Also RTP uses even UDP port numbers according to RFC.

If anybody has another better idea? please tell me.

regards,
Kamal

----- Original Message -----
From: "Jagan S" <Jagan.S@lntinfotech.com>
To: <rohc@ietf.org>
Sent: Saturday, March 13, 2004 6:27 AM
Subject: [rohc] ROHC: Header parsing


> Hi,
>
> 3095 specifies context identification at compressor  by parsing RTP/UDP/IP
> header fields.
>
> Yes. We can identify IP header by analyzing :' Version' / 'Length' fields
> of IP header.
> UDP header by analyzing: 'protocol type' field from IP header
>
> My question is about: How to identify the presence of RTP header ?
>
>
> Thanks in advance
> - Jagan
>
............................................................................
............................................................................
.....................................................
>
>
>
>
> _______________________________________________
> 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 exim@www1.ietf.org  Tue Mar 16 08:25:14 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29659
	for <rohc-archive@odin.ietf.org>; Tue, 16 Mar 2004 08:25:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3EYl-0007Fo-VC
	for rohc-archive@odin.ietf.org; Tue, 16 Mar 2004 08:24:45 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2GDOhxX027877
	for rohc-archive@odin.ietf.org; Tue, 16 Mar 2004 08:24:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3EYl-0007FY-Qh
	for rohc-web-archive@optimus.ietf.org; Tue, 16 Mar 2004 08:24:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29648
	for <rohc-web-archive@ietf.org>; Tue, 16 Mar 2004 08:24:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3EYk-0002iA-00
	for rohc-web-archive@ietf.org; Tue, 16 Mar 2004 08:24:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3EXp-0002e0-00
	for rohc-web-archive@ietf.org; Tue, 16 Mar 2004 08:23:46 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3EX7-0002Zn-00
	for rohc-web-archive@ietf.org; Tue, 16 Mar 2004 08:23:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3EX7-0006wM-Hm; Tue, 16 Mar 2004 08:23:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3EQC-0006Fi-KN
	for rohc@optimus.ietf.org; Tue, 16 Mar 2004 08:15:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29446
	for <rohc@ietf.org>; Tue, 16 Mar 2004 08:15:50 -0500 (EST)
From: schatterjee@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3EQB-00027S-00
	for rohc@ietf.org; Tue, 16 Mar 2004 08:15:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3EPN-000230-00
	for rohc@ietf.org; Tue, 16 Mar 2004 08:15:02 -0500
Received: from [164.164.94.116] (helo=hss.hns.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3EOs-0001x8-00
	for rohc@ietf.org; Tue, 16 Mar 2004 08:14:30 -0500
Received: from pragati.hss.hns.com (pragati.hss.hns.com [139.85.249.33])
	by hss.hns.com (8.11.6/8.11.2) with ESMTP id i2GDBXD08628;
	Tue, 16 Mar 2004 18:41:54 +0530
To: rohc@ietf.org, richard.price@roke.co.uk, cabo@tzi.org,
        jan.christoffersson@epl.ericsson.se, hans.hannu@epl.ericsson.se,
        zhigang.c.liu@nokia.com, jdrosen@dynamicsoft.com
Cc: Sip-implementors@cs.columbia.edu, sauragupta@hss.hns.com,
        jbhalla@hss.hns.com, anagarajan@hss.hns.com, amannan@hss.hns.com,
        nsudarshan@hss.hns.com, schatterjee@hss.hns.com
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.0.1 February 07, 2003
Message-ID: <OF95D34183.CD0C397F-ON65256E59.00471F64-65256E59.00488AB9@hss.hns.com>
Date: Tue, 16 Mar 2004 18:42:20 +0530
X-MIMETrack: Serialize by Router on Pragati/BLR/HSS(Release 6.5|September 18, 2003) at
 03/16/2004 06:43:41 PM,
	Serialize complete at 03/16/2004 06:43:41 PM
Content-Type: multipart/alternative; boundary="=_alternative 00488AAD65256E59_="
Subject: [rohc] Implementation of Sigcomp
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE,
	NO_REAL_NAME autolearn=no version=2.60

This is a multipart message in MIME format.
--=_alternative 00488AAD65256E59_=
Content-Type: text/plain; charset="US-ASCII"

Hi, 

Currently we are working on an implementation of Sigcomp. Can anyone tell 
us if there are any open-source implementation available for this ?

Regds,
Suprabhat
--=_alternative 00488AAD65256E59_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi, </font>
<br>
<br><font size=2 face="sans-serif">Currently we are working on an implementation
of Sigcomp. Can anyone tell us if there are any open-source implementation
available for this ?</font>
<br>
<br><font size=2 face="sans-serif">Regds,</font>
<br><font size=2 face="sans-serif">Suprabhat</font>
--=_alternative 00488AAD65256E59_=--

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



From exim@www1.ietf.org  Tue Mar 16 10:14:18 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05161
	for <rohc-archive@odin.ietf.org>; Tue, 16 Mar 2004 10:14:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3GGN-0004yy-8K
	for rohc-archive@odin.ietf.org; Tue, 16 Mar 2004 10:13:51 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2GFDplX019148
	for rohc-archive@odin.ietf.org; Tue, 16 Mar 2004 10:13:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3GGN-0004yl-2F
	for rohc-web-archive@optimus.ietf.org; Tue, 16 Mar 2004 10:13:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05065
	for <rohc-web-archive@ietf.org>; Tue, 16 Mar 2004 10:13:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3GGK-000408-00
	for rohc-web-archive@ietf.org; Tue, 16 Mar 2004 10:13:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3GFN-0003vG-00
	for rohc-web-archive@ietf.org; Tue, 16 Mar 2004 10:12:50 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3GEa-0003qq-00
	for rohc-web-archive@ietf.org; Tue, 16 Mar 2004 10:12:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3GEb-0004IL-Oq; Tue, 16 Mar 2004 10:12:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3GEH-0004CH-AT
	for rohc@optimus.ietf.org; Tue, 16 Mar 2004 10:11:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04880
	for <rohc@ietf.org>; Tue, 16 Mar 2004 10:11:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3GEF-0003pP-00
	for rohc@ietf.org; Tue, 16 Mar 2004 10:11:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3GDG-0003ke-00
	for rohc@ietf.org; Tue, 16 Mar 2004 10:10:39 -0500
Received: from [194.237.235.30] (helo=effnet.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3GCK-0003dX-00
	for rohc@ietf.org; Tue, 16 Mar 2004 10:09:40 -0500
Received: from effnet.com (c-497871d5.04-205-6c756c1.cust.bredbandsbolaget.se [213.113.120.73])
	(authenticated bits=0)
	by effnet.com (8.12.3/8.12.3) with ESMTP id i2GE8tU2020086
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Tue, 16 Mar 2004 15:08:55 +0100
Message-ID: <4057189C.5060702@effnet.com>
Date: Tue, 16 Mar 2004 16:09:16 +0100
From: Kristofer Sandlund <kristofer.sandlund@effnet.com>
Organization: Effnet
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030821
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: rohc@ietf.org
CC: zhigang.c.liu@nokia.com
Subject: Re: [rohc] ROHC context reuse & mode
References: <7B5AF06E216CB74DA8A5960A3181B5B815368E@ajebe001.americas.nokia.com>
In-Reply-To: <7B5AF06E216CB74DA8A5960A3181B5B815368E@ajebe001.americas.nokia.com>
X-Enigmail-Version: 0.76.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi all,

Myself, Carsten, Ghyslain and L-E continued the "re-use" discussion at the IETF 
meeting. I will summarize that discussion here, so that we can verify these 
conclusions on the list and hopefully make some "final" decisions on this subject.

* Re-use and mode
We all agreed that the solution proposed earlier that mode is inherited when a 
new flow re-uses a context of the same profile seems like the best option. We 
should hopefully be able to verify this at the next interop. When a context is 
re-used for a different profile, the mode will be set to initial mode (e.g. 
U-mode for 3095-profiles). We propose to add some text regarding this to the 
implementer's guide.

* Keeping decompressor context after IR reception
In the earlier discussion, some people felt that all context at the decompressor 
should be discarded every time an IR is received, no matter what the reason is 
for the IR being sent (repetition, initialization, static-nack). See message 
thread below.
The discussion we had in Seoul does not agree with this (but please feel free to 
correct any mistakes in the conclusions below). It _seems_ like there won't be 
any problem for the decompressor to keep the state that is not transmitted in 
the IR packet (second-order values, list compression item confidence etc). Since 
IR stands for Initialization and Refresh, it should be possible to use in a 
simple refresh way and not lose all context.
When the compressor re-uses a context for a new flow, it should try to 
re-establish all second order values etc, but should not need to do this for a 
"normal" refresh.
Therefore, we propose to add a bit more text to the implementer's guide to 
clarify what state can be kept by the decompressor and something about what the 
compressor can assume about decompressor state after IR packets.
Naturally, if the profile is changed, then the decompressor can safely flush out 
all information, since this is the only time that the decompressor can know for 
sure that this is for a new flow.

If we would go with the other suggestion of always assuming all state is 
discarded, then the decompressor will have quite a hard time to establish 
second-order values when running in U-mode (example, expected delta of extension 
header sequence numbers), and so far no problems seen with keeping this kind of 
state.

* IR-no-dynchain packets (see 5.7.7 and 5.7.7.2 in RFC3095)
These packets (which will be transmitted without payload), only update the 
static part of the context and are then to be discarded, and not passed on to 
upper layers. Since we allow context to be kept by the decompressor when IR 
packets are received, we feel that this should not have to invalidate the 
dynamic chain, and we propose adding one sentence (impl. guide again) to 
describe that these packets only update the static chain.

* IR-DYN profile downgrade (see 5.11.1. & 5.12.1. in RFC3095)
According to the decision to go to initial mode when changing profiles with an 
IR packet (see above), it seems like a resonable assumption that these also 
should use "initial mode". It is of course _possible_ to "inherit mode" here, 
but that would require more text to specify that IR-DYN profile changes differ 
from IR profile changes. Do we really want more special cases?

Best regards,
      Kristofer Sandlund, Effnet AB


zhigang.c.liu@nokia.com wrote:
> To be accurate, we should say context ID is reused, not the context
> (e.g. header field values, parameters, etc).
> 
> In addition, we can also make a clarification related to this: an IR 
> packet will flush out the decompressor context that exists before 
> receipt of the IR packet. (Note: mode is treated differently than
> the "normal" context which can be in different states.)
> 
> BR,
> Zhigang
> 
> 
>>-----Original Message-----
>>From: ext Lars-Erik Jonsson [mailto:larsman@home.se]
>>Sent: 18 February, 2004 07:32 AM
>>To: kristofer.sandlund@effnet.com
>>Cc: rohc@ietf.org; Liu Zhigang.C (Nokia-NRC/Dallas)
>>Subject: Re: Re: [rohc] ROHC context reuse & mode
>>
>>
>>
>>OK,
>>
>>I can buy that argumentation. So, what we should clarify then is that:
>>1) This is what happens when a context is re-used 
>>   for a new flow, compressed with the same profile.
>>2) If a context is re-used for compression of a new
>>   flow using a different profile, compression is
>>   obviously restarted in U-mode, independent of 
>>   previous mode
>>
>>Would that be it?
>>/L-E
>>
>>
>>
>>Zhigang/L-E,
>>
>>I think that Zhigang's scheme of letting mode be inherited 
>>when we have the same 
>>profile seems like the best choice to me. I think this 
>>approach will be more 
>>consistent with the mode transition logic.
>>If we choose the "always U-mode when new flow" approach, and 
>>a new flow appears 
>>in the middle of a pending mode transition, we would probably 
>>have to specify 
>>that the decompressor must detect that it is a new flow (for example 
>>static-def-diffing as I suggested earlier) and also it should 
>>set D_TRANS=done & 
>>D_MODE=U-mode when we have a new flow (i.e. mode trans must 
>>be restarted). The 
>>inheritance scheme will just complete the mode transition 
>>without having to 
>>understand that it is a new flow.
>>
>>I can agree that this is slightly inconsistent with the spec, 
>>but I don't think 
>>it "clearly says new contexts must start in U-mode". All it 
>>says is "Compression 
>>with ROHC MUST start in the Unidirectional mode" (sec. 
>>4.4.1), which _could_ be 
>>interpreted as being on a per-channel basis. If so, mode 
>>inheritance is 
>>completely ok.
>>
>>Rgds,
>>	Kristofer Sandlund, Effnet AB
>>
>>
>>


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



From exim@www1.ietf.org  Wed Mar 17 02:40:58 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23072
	for <rohc-archive@odin.ietf.org>; Wed, 17 Mar 2004 02:40:58 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3VfC-0000qr-7J
	for rohc-archive@odin.ietf.org; Wed, 17 Mar 2004 02:40:30 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2H7eUBr003238
	for rohc-archive@odin.ietf.org; Wed, 17 Mar 2004 02:40:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3Vf7-0000pG-7Z
	for rohc-web-archive@optimus.ietf.org; Wed, 17 Mar 2004 02:40:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23048
	for <rohc-web-archive@ietf.org>; Wed, 17 Mar 2004 02:40:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3Vf3-00031e-00
	for rohc-web-archive@ietf.org; Wed, 17 Mar 2004 02:40:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3VeM-0002vl-00
	for rohc-web-archive@ietf.org; Wed, 17 Mar 2004 02:39:38 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3Vdo-0002ni-00
	for rohc-web-archive@ietf.org; Wed, 17 Mar 2004 02:39:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3Vdp-0000UQ-1m; Wed, 17 Mar 2004 02:39:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3EWp-0006uu-6D
	for rohc@optimus.ietf.org; Tue, 16 Mar 2004 08:22:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29602
	for <rohc@ietf.org>; Tue, 16 Mar 2004 08:22:40 -0500 (EST)
From: sauragupta@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3EWn-0002ZO-00
	for rohc@ietf.org; Tue, 16 Mar 2004 08:22:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3EVt-0002Vr-00
	for rohc@ietf.org; Tue, 16 Mar 2004 08:21:45 -0500
Received: from [61.16.168.135] (helo=hss.hns.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3EVW-0002S3-00
	for rohc@ietf.org; Tue, 16 Mar 2004 08:21:22 -0500
Received: from pragati.hss.hns.com (pragati.hss.hns.com [139.85.249.33])
	by hss.hns.com (8.11.6/8.11.2) with ESMTP id i2GDKAD08732
	for <rohc@ietf.org>; Tue, 16 Mar 2004 18:50:20 +0530
To: rohc@ietf.org
X-Mailer: Lotus Notes Release 6.0.1 February 07, 2003
Message-ID: <OF1C695A1E.F212A94A-ON65256E59.00494284-65256E59.0049E859@hss.hns.com>
Date: Tue, 16 Mar 2004 18:50:53 +0530
X-MIMETrack: Serialize by Router on Pragati/BLR/HSS(Release 6.5|September 18, 2003) at
 03/16/2004 06:51:08 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Subject: [rohc] Implementation of Sigcomp
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60





Hi,

Currently we are working on an implementation of Sigcomp. Can anyone tell
us if there are any open-source implementation available for this ?

Regds,
Suprabhat





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



From exim@www1.ietf.org  Wed Mar 17 02:40:58 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23073
	for <rohc-archive@odin.ietf.org>; Wed, 17 Mar 2004 02:40:58 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3VfC-0000qs-7q
	for rohc-archive@odin.ietf.org; Wed, 17 Mar 2004 02:40:30 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2H7eU8D003240
	for rohc-archive@odin.ietf.org; Wed, 17 Mar 2004 02:40:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3Vf8-0000pQ-5a
	for rohc-web-archive@optimus.ietf.org; Wed, 17 Mar 2004 02:40:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23051
	for <rohc-web-archive@ietf.org>; Wed, 17 Mar 2004 02:40:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3Vf4-00031j-00
	for rohc-web-archive@ietf.org; Wed, 17 Mar 2004 02:40:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3VeM-0002vt-00
	for rohc-web-archive@ietf.org; Wed, 17 Mar 2004 02:39:39 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3Vdo-0002nj-00
	for rohc-web-archive@ietf.org; Wed, 17 Mar 2004 02:39:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3Vdq-0000VF-77; Wed, 17 Mar 2004 02:39:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3Ehb-00081b-Hq
	for rohc@optimus.ietf.org; Tue, 16 Mar 2004 08:33:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00168
	for <rohc@ietf.org>; Tue, 16 Mar 2004 08:33:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3Eha-0003bj-00
	for rohc@ietf.org; Tue, 16 Mar 2004 08:33:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3Egc-0003Vm-00
	for rohc@ietf.org; Tue, 16 Mar 2004 08:32:51 -0500
Received: from smtp.wp.pl ([212.77.101.160])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3Efw-0003Kb-00
	for rohc@ietf.org; Tue, 16 Mar 2004 08:32:08 -0500
Received: (wp-smtpd smtp.wp.pl 1486 invoked from network); 16 Mar 2004 14:31:31 +0100
Received: from ofree.wp-sa.pl (HELO localhost) ([212.77.101.203])
          (envelope-sender <szym_paw@wp.pl>)
          by smtp.wp.pl (wp-smtpd) with SMTP
          for <rohc@ietf.org>; 16 Mar 2004 14:31:31 +0100
Date: Tue, 16 Mar 2004 14:31:26 +0100
From: =?ISO-8859-2?Q?Pawe=B3_Szyma=F1ski?= <szym_paw@wp.pl>
To: rohc@ietf.org
Message-ID: <405701aeee273@wp.pl>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-2
Content-Disposition: inline
X-Mailer: Interfejs WWW poczty Wirtualnej Polski
Organization: Poczta Wirtualnej Polski S.A. http://www.wp.pl/
X-IP: 192.55.37.193, 172.28.172.146
X-AntiVirus: skaner antywirusowy poczty Wirtualnej Polski S. A.
X-WP-ChangeAV: 0
X-WP-AntySpam-Rezultat: NIE-SPAM
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id IAA00169
Subject: [rohc] Slope used to compress/decompress RTP Timestamp field
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi all,

I've seen in the ROHC mailing list archive a discussion about=20
using dynamic slope values by the compressor and decompressor=20
while decompressing RTP Timestamp field from OU-0 packets (refer=20
to mail: http://www.cdt.luth.se/rohc/msg00934.html). The idea is=20
that decompressor starts with default_slope value and calculates=20
new slope value at each arrival of a packet containing TS field.

The mechanism is not described in the standard. Only=20
default_slope values are defined. Should compressor and=20
decompressor use other slope values than the default_slope when=20
they process UO-0 packets ?=20

Regards

Pawel Szymanski

----------------------------------------------------
Ju=BF dzi=B6 zaplanuj wakacje.
Im szybciej tym wi=EAksza zni=BFka - nawet do 12%.
http://klik.wp.pl/?adr=3Dhttp%3A%2F%2Fturystyka.wp.pl%2Fwiadomosc.html%3F=
wid%3D4843057&sid=3D140



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



From exim@www1.ietf.org  Wed Mar 17 09:49:11 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08662
	for <rohc-archive@odin.ietf.org>; Wed, 17 Mar 2004 09:49:11 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3cLR-00062W-L8
	for rohc-archive@odin.ietf.org; Wed, 17 Mar 2004 09:48:44 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2HEmXgB023216
	for rohc-archive@odin.ietf.org; Wed, 17 Mar 2004 09:48:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3cLR-00062N-Gh
	for rohc-web-archive@optimus.ietf.org; Wed, 17 Mar 2004 09:48:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08567
	for <rohc-web-archive@ietf.org>; Wed, 17 Mar 2004 09:48:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3cLP-0005ru-00
	for rohc-web-archive@ietf.org; Wed, 17 Mar 2004 09:48:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3cKO-0005kC-00
	for rohc-web-archive@ietf.org; Wed, 17 Mar 2004 09:47:29 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3cJR-0005cm-00
	for rohc-web-archive@ietf.org; Wed, 17 Mar 2004 09:46:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3cJP-0005nX-3o; Wed, 17 Mar 2004 09:46:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3cIk-0005lN-Ua
	for rohc@optimus.ietf.org; Wed, 17 Mar 2004 09:45:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08446
	for <rohc@ietf.org>; Wed, 17 Mar 2004 09:45:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3cIh-0005Wy-00
	for rohc@ietf.org; Wed, 17 Mar 2004 09:45:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3cHk-0005Pe-00
	for rohc@ietf.org; Wed, 17 Mar 2004 09:44:44 -0500
Received: from mailrelay2.lntinfotech.com ([203.199.54.34])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3cHD-0005Gc-00
	for rohc@ietf.org; Wed, 17 Mar 2004 09:44:12 -0500
Received: from Bangalore.lntinfotech.com ([107.108.204.3])
          by mailrelay2.lntinfotech.com (Lotus Domino Release 5.0.12)
          with ESMTP id 2004031720133268:25584 ;
          Wed, 17 Mar 2004 20:13:32 +0530 
Subject: Re: RE: [rohc] ROHC: Header parsing
To: rohc@ietf.org
Cc: lars-erik.jonsson@ericsson.com
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OFB39756E6.AA94C98A-ON65256E5A.004FDB2B@lntinfotech.com>
From: "Jagan S" <Jagan.S@lntinfotech.com>
Date: Wed, 17 Mar 2004 20:11:32 +0530
MIME-Version: 1.0
X-MIMETrack: Serialize by Router on BANGALORE/LNTINFOTECH(Release 5.0.9 |November 16, 2001) at
 03/17/2004 08:11:32 PM,
	Itemize by SMTP Server on MAILRELAY2/LNTINFOTECH(Release 5.0.12  |February
 13, 2003) at 03/17/2004 08:13:32 PM,
	Serialize by Router on MAILRELAY2/LNTINFOTECH(Release 5.0.12  |February 13, 2003) at
 03/17/2004 08:14:12 PM,
	Serialize complete at 03/17/2004 08:14:12 PM
Content-type: text/plain; charset=us-ascii
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Dear LarsErik,

Thanks for the reply.

>There is no way to explicitly know that packet stream is
>an RTP stream, but one will have to guess. The good thing
>with ROHC IP/UDP/RTP compression is that it is lossless,
>independent of if the UDP payload is actually RTP or not.
>One can thus start with assuming RTP, and if the compression
>ratio turns out to be negative for the RTP part, a profile
>switch to IP/UDP-only should be performed (see section 5.11).

>Cheers,
>/L-E

==> Assuming as RTP profile in the begining of transmission & then changing
over to UDP/IP profile,
 leads to packet losses. And moreover, if the profile is other than UDP/IP,
again another changeover
 is requried to another profile. Will this not lead to lower efficiency?

Another issue is: in U mode, it may not be possible to calculate negative
compression ratio,
 due to the absence of feedback. In this case, the compressor keeps sending
compressed packets
 assuming the profile as RTP/UDP/IP !!!

Is my understanding correct ??


~~~~~~~~~~~~~~~~~~~~
Thanks & With warm regards.,

Jagan S Nathan

L&T Infotech, Bangalore.


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



From exim@www1.ietf.org  Wed Mar 17 21:11:41 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25332
	for <rohc-archive@odin.ietf.org>; Wed, 17 Mar 2004 21:11:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3mzu-0006Ko-S4
	for rohc-archive@odin.ietf.org; Wed, 17 Mar 2004 21:11:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2I2B2L5024346
	for rohc-archive@odin.ietf.org; Wed, 17 Mar 2004 21:11:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3mzu-0006Kb-I3
	for rohc-web-archive@optimus.ietf.org; Wed, 17 Mar 2004 21:11:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25283
	for <rohc-web-archive@ietf.org>; Wed, 17 Mar 2004 21:10:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3mzr-0006al-00
	for rohc-web-archive@ietf.org; Wed, 17 Mar 2004 21:10:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3myy-0006Pv-00
	for rohc-web-archive@ietf.org; Wed, 17 Mar 2004 21:10:05 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3mxv-0006Bt-00
	for rohc-web-archive@ietf.org; Wed, 17 Mar 2004 21:08:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3mxw-0006Er-Ob; Wed, 17 Mar 2004 21:09:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3mwy-00068K-LO
	for rohc@optimus.ietf.org; Wed, 17 Mar 2004 21:08:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25049
	for <rohc@ietf.org>; Wed, 17 Mar 2004 21:07:57 -0500 (EST)
From: Zongming.Zhou@commit.cn
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3mww-0005zL-00
	for rohc@ietf.org; Wed, 17 Mar 2004 21:07:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3mvr-0005nj-00
	for rohc@ietf.org; Wed, 17 Mar 2004 21:06:52 -0500
Received: from [211.152.58.77] (helo=DIOSCURI.COMMIT)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3mup-0005VJ-00
	for rohc@ietf.org; Wed, 17 Mar 2004 21:05:48 -0500
MIME-Version: 1.0
To: rohc@ietf.org
X-Mailer: Lotus Notes Release 5.0.11   July 24, 2002
Message-ID: <OFABCCFD71.CDBBDC71-ON48256E5A.0036D358-48256E5B.000B890D@COMMIT>
Date: Thu, 18 Mar 2004 10:05:32 +0800
X-MIMETrack: Serialize by Router on penelope/commit(Release 5.0.11  |July 24, 2002) at
 2004/03/18 10:06:06 AM,
	Serialize complete at 2004/03/18 10:06:06 AM
Content-Type: multipart/alternative; boundary="=_alternative 000B890A48256E5B_="
Subject: [rohc] Question of ROHC
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.9 required=5.0 tests=AWL,EXCUSE_16,HTML_20_30,
	HTML_MESSAGE,MIME_BASE64_TEXT,NO_REAL_NAME autolearn=no version=2.60

This is a multipart message in MIME format.
--=_alternative 000B890A48256E5B_=
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

SWYgZm9yIHRoaXMgY2FzZTogDQogICArLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSsg
DQogICB8ICAgICAgICAgICAgICBSVFAgICAgICAgICAgICAgIHwgDQogICArLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLSsgDQogICB8ICAgICAgICAgICAgICBVVFAgICAgICAgICAgICAg
IHwgDQogICArLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSsgDQogICB8ICAgICAgICAg
ICAgICBBSCAgICAgICAgICAgICAgIHwgDQogICArLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLSsgDQogICB8ICAgICAgICAgICBJbm5lciBJUCAgICAgICAgICAgIHwgDQogICArLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSsgDQogICB8ICAgICAgICAgICAgICBBSCAgICAgICAg
ICAgICAgIHwgDQogICArLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSsgDQogICB8ICAg
ICAgICAgICBPdXRlciBJUCAgICAgICAgICAgIHwgDQogICArLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLSsgDQpUaGUgZm9ybWF0IG9mIElSIHBhY2tldD8gDQogICAgIDAgICAxICAgMiAg
IDMgICA0ICAgNSAgIDYgICA3IA0KICAgIC0tLSAtLS0gLS0tIC0tLSAtLS0gLS0tIC0tLSAtLS0g
DQogICB8ICAgICAgICAgQWRkLUNJRCBvY3RldCAgICAgICAgIHwgIGlmIGZvciBzbWFsbCBDSURz
IGFuZCBDSUQgIT0gMCANCiAgICstLS0rLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKyANCiAg
IHwgMSAgIDEgICAxICAgMSAgIDEgICAxICAgMCB8IEQgfCANCiAgICstLS0rLS0tKy0tLSstLS0r
LS0tKy0tLSstLS0rLS0tKyANCiAgIHwgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCAN
CiAgIC8gICAgMC0yIG9jdGV0cyBvZiBDSUQgaW5mbyAgICAgLyAgMS0yIG9jdGV0cyBpZiBmb3Ig
bGFyZ2UgQ0lEcyANCiAgIHwgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCANCiAgICst
LS0rLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKyANCiAgIHwgICAgICAgICAgICBQcm9maWxl
ICAgICAgICAgICAgfCAgMSBvY3RldCANCiAgICstLS0rLS0tKy0tLSstLS0rLS0tKy0tLSstLS0r
LS0tKyANCiAgIHwgICAgICAgICAgICAgIENSQyAgICAgICAgICAgICAgfCAgMSBvY3RldCANCiAg
ICstLS0rLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKyANCiAgIHwgICAgT3V0ZXIgSVAgc3Rh
dGljIHBhcnQ/Pz8gICAgfCANCiAgIHwgICAgSW5uZXIgSVAgc3RhdGljIHBhcnQ/Pz8gICAgfHN0
YXRpYyBjaGFpbiANCiAgIHwgICAgICAgIFVEUCBzdGF0aWMgcGFydCAgICAgICAgfCANCiAgIHwg
ICAgICAgIFJUUCBzdGF0aWMgcGFydCAgICAgICAgfHZhcmlhYmxlIGxlbmd0aCANCiAgICstLS0r
LS0tKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKyANCiAgIHwgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgfCANCiAgIHwgICAgICAgICBEeW5hbWljIGNoYWluICAgICAgICAgfCAgcHJlc2Vu
dCBpZiBEID0gMSwgdmFyaWFibGUgbGVuZ3RoIA0KICAgfCAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICB8IA0KICAgIC0gLSAtIC0gLSAtIC0gLSAtIC0gLSAtIC0gLSAtIC0gDQogICB8ICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgDQogICB8ICAgICAgICAgICBQYXlsb2FkICAg
ICAgICAgICAgIHwgIHZhcmlhYmxlIGxlbmd0aCANCiAgIHwgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgfCANCiAgICAtIC0gLSAtIC0gLSAtIC0gLSAtIC0gLSAtIC0gLSAtIA0KDQpHZW5l
cmljIGV4dGVuc2lvbiBoZWFkZXIgbGlzdCANCiAgICstLS0rLS0tKy0tLSstLS0rLS0tKy0tLSst
LS0rLS0tKyANCiAgIHwgLyBHZW5lcmljIGV4dGVuc2lvbiBoZWFkZXIgLyAgfCB2YXJpYWwgbGVu
Z3RoIA0KICAgfCAvICBsaXN0IG9mIG91dGVyIElQIChBSCkgICAvICB8ICAgDQogICArLS0tKy0t
LSstLS0rLS0tKy0tLSstLS0rLS0tKy0tLSsgDQogICB8IC8gR2VuZXJpYyBleHRlbnNpb24gaGVh
ZGVyIC8gIHwgdmFyaWFsIGxlbmd0aCANCiAgIHwgLyAgbGlzdCBvZiBpbm5lciBJUCAoQUgpICAg
LyAgfCAgIA0KICAgKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rIA0KSXMgaXQgcmln
aHQ/IA0KMS4gSXMgdGhlcmUgb25seSBvdXRlciBJUCBzdGF0aWMgcGFydCBleGlzdHMgaW4gSVIg
cGFja2V0PyANCjIuIElmIHllcywgZG9lcyBvdXRlciBJUCBzdGF0aWMgcGFydCBwcmVjZWRlIGlu
bmVyIElQIHN0YXRpYyBwYXJ0IG9yIGVsc2U/IA0KQW5kIGRvZXMgR2VuZXJpYyBleHRlbnNpb24g
aGVhZGVyIGxpc3Qgb2Ygb3V0ZXIgSVAgcHJlY2VkZSBHZW5lcmljIA0KZXh0ZW5zaW9uIA0KaGVh
ZGVyIGxpc3Qgb2YgaW5uZXIgSVA/IA0KMy4gSWYgbm8sIGhvdyB0byBleHBsYWluIHRoZSBmb2xs
b3dpbmcgMiBzZW50ZW5jZSBpbiBSRkMzMDk1PyANCiAgIDEpICBJbiBmaXJzIHBhcmFncmFwaCBv
ZiBDaGFwdGVyIDUuOC41L1JGQzMwOTUsIHRoZXJlIGlzIG9uZSBzZW50ZW5jZTogDQogICAgICAg
V2hlbiB0aGVyZSBpcyBtb3JlIHRoYW4gb25lIElQIGhlYWRlciwgdGhlcmUgaXMgbW9yZSB0aGFu
IG9uZSBsaXN0IA0Kb2YgDQogICAgICAgZXh0ZW5zaW9uIGhlYWRlcnMuIA0KICAgMikgIEluIENo
YXB0ZXIgNS44L1JGQzMwOTUsIHRoZXJlIGlzIGFub3RoZXIgc2VudGVuY2U6IA0KICAgICAgIElQ
djYgYmFzZSBoZWFkZXJzIGFuZCBJUHY0IGhlYWRlcnMgY2Fubm90IGJlIHBhcnQgb2YgYW4gZXh0
ZW5zaW9uIA0KICAgICAgIGhlYWRlciBjaGFpbi4gDQoNCg0KQmVzdCBSZWdhcmRzDQoNClpob3Ug
Wm9uZ21pbmcg1tzX2sP3DQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0NCkNPTU1JVCBJbmNvcnBvcmF0ZWQN
CkFkZDogMTggU2hlbndhbmcgUmQsIFhpbnpodWFuZyBJbmR1c3RyaWFsIERldmVsb3BtZW50IFpv
bmUsIFNoYW5naGFpIENoaW5hDQpQb3N0IENvZGU6IDIwMTEwOA0KVGVsOiArODYtMjEtNTQ0Mi00
ODg1IEV4dDozNDA1DQpGQVg6ICs4Ni0yMS01NDQyLTQ4ODYNCkVtYWlsOiB6b25nbWluZy56aG91
QGNvbW1pdC5jbg0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQpUaGUgaW5mb3JtYXRpb24gY29udGFpbmVk
IGluIHRoaXMgZS1tYWlsIGFuZCBhbnkgYXR0YWNobWVudHMgdGhlcmV0byBmcm9tIA0KQ09NTUlU
IEluY29ycG9yYXRlZCBpcyBpbnRlbmRlZCB0byBiZSBmb3IgdGhlIHVzZSBvZiB0aGUgcGVyc29u
IG5hbWVkIA0KYWJvdmUgYW5kIG1heSBiZSBwcml2YXRlLCBjb25maWRlbnRpYWwgYW5kIHByaXZp
bGVnZWQuIElmIHlvdSBhcmUgbm90IHRoZSANCmludGVuZGVkIHJlY2lwaWVudCBvZiB0aGlzIHRy
YW5zbWlzc2lvbiwgeW91IGFyZSBoZXJlYnkgbm90aWZpZWQgdGhhdCBhbnkgDQpkaXNjbG9zdXJl
LCBjb3B5aW5nLCBkaXN0cmlidXRpb24sIHByaW50aW5nIG9yIHVzZSBvZiB0aGUgY29udGVudHMg
b2YgdGhpcyANCmNvbW11bmljYXRpb24gaXMgc3RyaWN0bHkgcHJvaGliaXRlZC4gSWYgeW91IGhh
dmUgcmVjZWl2ZWQgdGhpcyBlLW1haWwgaW4gDQplcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUgc2Vu
ZGVyIGltbWVkaWF0ZWx5IGFuZCBwZXJtYW5lbnRseSBkZWxldGUgdGhlIA0Kb3JpZ2luYWwgYW5k
IGFueSBjb3BpZXMgb2YgdGhpcyBlbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIHRoZXJldG8uIA0K
--=_alternative 000B890A48256E5B_=
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCklmIGZvciB0aGlzIGNh
c2U6PC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pjxmb250IHNp
emU9MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogJm5ic3A7ICstLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tKzwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9u
dD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwOyB8ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO1JUUCAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDt8IDxicj4NCiAmbmJzcDsgKy0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rPC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5z
LXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogJm5i
c3A7IHwgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7VVRQ
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO3wgPGJyPg0K
ICZuYnNwOyArLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSsgPGJyPg0KICZuYnNwOyB8
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO0FIICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyB8IDxicj4NCiAmbmJz
cDsgKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rPC9mb250Pjxmb250IHNpemU9MyBm
YWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj48
YnI+DQogJm5ic3A7IHwgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBJbm5lciBJ
UCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO3wgPGJyPg0KICZuYnNw
OyArLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSs8L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZh
Y2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxi
cj4NCiAmbmJzcDsgfCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDtBSCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
fCA8YnI+DQogJm5ic3A7ICstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKzwvZm9udD48
Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0i
c2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwOyB8ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgT3V0ZXIgSVAgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDt8
IDxicj4NCiAmbmJzcDsgKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rIDxicj4NClRo
ZSBmb3JtYXQgb2YgSVIgcGFja2V0PzwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJp
ZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwOyAm
bmJzcDsgMCAmbmJzcDsgMSAmbmJzcDsgMiAmbmJzcDsgMyAmbmJzcDsgNCAmbmJzcDsgNSAmbmJz
cDsgNiAmbmJzcDsgNzwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9u
dD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwOyAmbmJzcDstLS0g
LS0tIC0tLSAtLS0gLS0tIC0tLSAtLS0gLS0tPC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5z
LXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogJm5i
c3A7IHwgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IEFkZC1DSUQgb2N0ZXQgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7IHwgJm5ic3A7aWYgZm9yIHNtYWxsIENJRHMgYW5kIENJRCAhPSAw
PC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9
MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogJm5ic3A7ICstLS0rLS0tKy0tLSstLS0rLS0tKy0t
LSstLS0rLS0tKzwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9udD48
Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwOyB8IDEgJm5ic3A7IDEg
Jm5ic3A7IDEgJm5ic3A7IDEgJm5ic3A7IDEgJm5ic3A7IDEgJm5ic3A7IDAgfCBEIHw8L2ZvbnQ+
PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9
InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDsgKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKy0tLSst
LS0rPC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pjxmb250IHNp
emU9MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogJm5ic3A7IHwgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgfDwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0i
c2Fucy1zZXJpZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0K
ICZuYnNwOyAvICZuYnNwOyAmbmJzcDswLTIgb2N0ZXRzIG9mIENJRCBpbmZvICZuYnNwOyAmbmJz
cDsgLyAmbmJzcDsxLTIgb2N0ZXRzIGlmIGZvciBsYXJnZSBDSURzPC9mb250Pjxmb250IHNpemU9
MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlm
Ij48YnI+DQogJm5ic3A7IHwgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgfDwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9udD48
Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwOyArLS0tKy0tLSstLS0r
LS0tKy0tLSstLS0rLS0tKy0tLSs8L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYi
PiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDsgfCAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO1Byb2ZpbGUgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDt8ICZuYnNwOzEgb2N0ZXQ8L2ZvbnQ+PGZv
bnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNh
bnMtc2VyaWYiPjxicj4NCiAmbmJzcDsgKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKy0tLSstLS0r
PC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9
MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogJm5ic3A7IHwgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7Q1JDICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwO3wgJm5ic3A7MSBvY3RldDwvZm9udD48Zm9udCBzaXplPTMg
ZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+
PGJyPg0KICZuYnNwOyArLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKy0tLSs8L2ZvbnQ+PGZv
bnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNh
bnMtc2VyaWYiPjxicj4NCiAmbmJzcDsgfCAmbmJzcDsgJm5ic3A7T3V0ZXIgSVAgc3RhdGljIHBh
cnQ/Pz8gJm5ic3A7ICZuYnNwO3w8L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYi
PiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDsgfCAm
bmJzcDsgJm5ic3A7SW5uZXIgSVAgc3RhdGljIHBhcnQ/Pz8gJm5ic3A7ICZuYnNwO3xzdGF0aWMg
Y2hhaW48L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+PGZvbnQg
c2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDsgfCAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDtVRFAgc3RhdGljIHBhcnQgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7fDwv
Zm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9udD48Zm9udCBzaXplPTIg
ZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwOyB8ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwO1JUUCBzdGF0aWMgcGFydCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDt8dmFyaWFibGUg
bGVuZ3RoPC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pg0KPGJy
Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgJm5ic3A7Ky0tLSstLS0rLS0t
Ky0tLSstLS0rLS0tKy0tLSstLS0rPC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlm
Ij4gPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogJm5ic3A7IHwg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgfDwvZm9udD48
Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0i
c2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwOyB8ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBE
eW5hbWljIGNoYWluICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyB8ICZuYnNwO3ByZXNlbnQg
aWYgRCA9IDEsIHZhcmlhYmxlIGxlbmd0aDwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1z
ZXJpZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNw
OyB8ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHw8L2Zv
bnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZh
Y2U9InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDsgJm5ic3A7LSAtIC0gLSAtIC0gLSAtIC0gLSAt
IC0gLSAtIC0gLTwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9udD48
Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwOyB8ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHw8L2ZvbnQ+PGZvbnQgc2l6ZT0z
IGZhY2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYi
Pjxicj4NCiAmbmJzcDsgfCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IFBheWxv
YWQgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgfCAmbmJzcDt2YXJp
YWJsZSBsZW5ndGg8L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+
PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDsgfCAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyB8PC9mb250Pjxmb250IHNpemU9
MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlm
Ij48YnI+DQogJm5ic3A7ICZuYnNwOy0gLSAtIC0gLSAtIC0gLSAtIC0gLSAtIC0gLSAtIC08L2Zv
bnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8YnI+DQo8L2ZvbnQ+PGZvbnQgc2l6
ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCkdlbmVyaWMgZXh0ZW5zaW9uIGhlYWRlciBsaXN0
PC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9
MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogJm5ic3A7ICstLS0rLS0tKy0tLSstLS0rLS0tKy0t
LSstLS0rLS0tKzwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9udD48
Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwOyB8IC8gR2VuZXJpYyBl
eHRlbnNpb24gaGVhZGVyIC8gJm5ic3A7fCB2YXJpYWwgbGVuZ3RoPC9mb250Pjxmb250IHNpemU9
MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlm
Ij48YnI+DQogJm5ic3A7IHwgLyAmbmJzcDtsaXN0IG9mIG91dGVyIElQIChBSCkgJm5ic3A7IC8g
Jm5ic3A7fCAmbmJzcDs8L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2Zv
bnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDsgKy0tLSstLS0r
LS0tKy0tLSstLS0rLS0tKy0tLSstLS0rPC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNl
cmlmIj4gPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogJm5ic3A7
IHwgLyBHZW5lcmljIGV4dGVuc2lvbiBoZWFkZXIgLyAmbmJzcDt8IHZhcmlhbCBsZW5ndGg8L2Zv
bnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZh
Y2U9InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDsgfCAvICZuYnNwO2xpc3Qgb2YgaW5uZXIgSVAg
KEFIKSAmbmJzcDsgLyAmbmJzcDt8ICZuYnNwOzwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fu
cy1zZXJpZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZu
YnNwOyArLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKy0tLSs8L2ZvbnQ+PGZvbnQgc2l6ZT0z
IGZhY2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYi
Pjxicj4NCklzIGl0IHJpZ2h0PzwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+
IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KMS4gSXMgdGhlcmUg
b25seSBvdXRlciBJUCBzdGF0aWMgcGFydCBleGlzdHMgaW4gSVIgcGFja2V0PzwvZm9udD48Zm9u
dCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fu
cy1zZXJpZiI+PGJyPg0KMi4gSWYgeWVzLCBkb2VzIG91dGVyIElQIHN0YXRpYyBwYXJ0IHByZWNl
ZGUgaW5uZXIgSVAgc3RhdGljIHBhcnQgb3IgZWxzZT88L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9
InNhbnMtc2VyaWYiPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4N
CkFuZCBkb2VzIEdlbmVyaWMgZXh0ZW5zaW9uIGhlYWRlciBsaXN0IG9mIG91dGVyIElQIHByZWNl
ZGUgR2VuZXJpYyBleHRlbnNpb24gPGJyPg0KaGVhZGVyIGxpc3Qgb2YgaW5uZXIgSVA/PC9mb250
Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9MiBmYWNl
PSJzYW5zLXNlcmlmIj48YnI+DQozLiBJZiBubywgaG93IHRvIGV4cGxhaW4gdGhlIGZvbGxvd2lu
ZyAyIHNlbnRlbmNlIGluIFJGQzMwOTU/PC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNl
cmlmIj4gPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogJm5ic3A7
IDEpICZuYnNwO0luIGZpcnMgcGFyYWdyYXBoIG9mIENoYXB0ZXIgNS44LjUvUkZDMzA5NSwgdGhl
cmUgaXMgb25lIHNlbnRlbmNlOjwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+
IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwOyAmbmJz
cDsgJm5ic3A7IFdoZW4gdGhlcmUgaXMgbW9yZSB0aGFuIG9uZSBJUCBoZWFkZXIsIHRoZXJlIGlz
IG1vcmUgdGhhbiBvbmUgbGlzdCBvZiA8YnI+DQogJm5ic3A7ICZuYnNwOyAmbmJzcDsgZXh0ZW5z
aW9uIGhlYWRlcnMuPC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250
Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogJm5ic3A7IDIpICZuYnNwO0lu
IENoYXB0ZXIgNS44L1JGQzMwOTUsIHRoZXJlIGlzIGFub3RoZXIgc2VudGVuY2U6IDxicj4NCiAm
bmJzcDsgJm5ic3A7ICZuYnNwOyBJUHY2IGJhc2UgaGVhZGVycyBhbmQgSVB2NCBoZWFkZXJzIGNh
bm5vdCBiZSBwYXJ0IG9mIGFuIGV4dGVuc2lvbiA8YnI+DQogJm5ic3A7ICZuYnNwOyAmbmJzcDsg
aGVhZGVyIGNoYWluLjwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDxicj4N
Cjxicj4NCjwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KQmVzdCBS
ZWdhcmRzPGJyPg0KPGJyPg0KWmhvdSBab25nbWluZyDW3Nfaw/c8YnI+DQo9PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT08YnI+DQpDT01NSVQgSW5jb3Jwb3JhdGVkPGJyPg0KQWRkOiAxOCBTaGVud2FuZyBSZCwg
WGluemh1YW5nIEluZHVzdHJpYWwgRGV2ZWxvcG1lbnQgWm9uZSwgU2hhbmdoYWkgQ2hpbmE8YnI+
DQpQb3N0IENvZGU6IDIwMTEwODxicj4NClRlbDogKzg2LTIxLTU0NDItNDg4NSBFeHQ6MzQwNTxi
cj4NCkZBWDogKzg2LTIxLTU0NDItNDg4NjwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0i
c2Fucy1zZXJpZiI+RW1haWw6IHpvbmdtaW5nLnpob3VAY29tbWl0LmNuPGJyPg0KPT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PGJyPg0KVGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBpbiB0aGlzIGUtbWFpbCBh
bmQgYW55IGF0dGFjaG1lbnRzIHRoZXJldG8gZnJvbSBDT01NSVQgSW5jb3Jwb3JhdGVkIGlzIGlu
dGVuZGVkIHRvIGJlIGZvciB0aGUgdXNlIG9mIHRoZSBwZXJzb24gbmFtZWQgYWJvdmUgYW5kIG1h
eSBiZSBwcml2YXRlLCBjb25maWRlbnRpYWwgYW5kIHByaXZpbGVnZWQuIElmIHlvdSBhcmUgbm90
IHRoZSBpbnRlbmRlZCByZWNpcGllbnQgb2YgdGhpcyB0cmFuc21pc3Npb24sIHlvdSBhcmUgaGVy
ZWJ5IG5vdGlmaWVkIHRoYXQgYW55IGRpc2Nsb3N1cmUsIGNvcHlpbmcsIGRpc3RyaWJ1dGlvbiwg
cHJpbnRpbmcgb3IgdXNlIG9mIHRoZSBjb250ZW50cyBvZiB0aGlzIGNvbW11bmljYXRpb24gaXMg
c3RyaWN0bHkgcHJvaGliaXRlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlLW1haWwgaW4g
ZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBpbW1lZGlhdGVseSBhbmQgcGVybWFuZW50
bHkgZGVsZXRlIHRoZSBvcmlnaW5hbCBhbmQgYW55IGNvcGllcyBvZiB0aGlzIGVtYWlsIGFuZCBh
bnkgYXR0YWNobWVudHMgdGhlcmV0by48L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2Vy
aWYiPiA8L2ZvbnQ+DQo=
--=_alternative 000B890A48256E5B_=--

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



From exim@www1.ietf.org  Thu Mar 18 03:03:03 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25831
	for <rohc-archive@odin.ietf.org>; Thu, 18 Mar 2004 03:03:03 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sU7-0000NS-NN
	for rohc-archive@odin.ietf.org; Thu, 18 Mar 2004 03:02:36 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2I82YoR001443
	for rohc-archive@odin.ietf.org; Thu, 18 Mar 2004 03:02:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sU6-0000NC-Qj
	for rohc-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 03:02:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25809
	for <rohc-web-archive@ietf.org>; Thu, 18 Mar 2004 03:02:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sU2-00024X-00
	for rohc-web-archive@ietf.org; Thu, 18 Mar 2004 03:02:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3sT4-0001vV-00
	for rohc-web-archive@ietf.org; Thu, 18 Mar 2004 03:01:31 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sSb-0001lv-00
	for rohc-web-archive@ietf.org; Thu, 18 Mar 2004 03:01:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sSd-0000Hk-1X; Thu, 18 Mar 2004 03:01:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sRq-00005c-Gu
	for rohc@optimus.ietf.org; Thu, 18 Mar 2004 03:00:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25658
	for <rohc@ietf.org>; Thu, 18 Mar 2004 03:00:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sRm-0001j1-00
	for rohc@ietf.org; Thu, 18 Mar 2004 03:00:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3sQq-0001al-00
	for rohc@ietf.org; Thu, 18 Mar 2004 02:59:13 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sPr-0001SR-00
	for rohc@ietf.org; Thu, 18 Mar 2004 02:58:12 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2I7wCYG011782
	for <rohc@ietf.org>; Thu, 18 Mar 2004 08:58:12 +0100 (MET)
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 18 Mar 2004 08:58:11 +0100
Received: from caffreys (caffreys.ericsson.se [147.214.181.21]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id FYFW1RWK; Thu, 18 Mar 2004 08:59:27 +0100
Date: Thu, 18 Mar 2004 09:06:06 +0100 (CET)
From: Vicknesan Ayadurai <vicknesan.ayadurai@ericsson.com>
X-X-Sender: vick@caffreys.ericsson.se
To: Jagan S <Jagan.S@lntinfotech.com>
cc: rohc@ietf.org, <lars-erik.jonsson@ericsson.com>
Subject: Re: RE: [rohc] ROHC: Header parsing
In-Reply-To: <OFB39756E6.AA94C98A-ON65256E5A.004FDB2B@lntinfotech.com>
Message-ID: <20040318084525.I3027-100000@caffreys.ericsson.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-OriginalArrivalTime: 18 Mar 2004 07:58:11.0751 (UTC) FILETIME=[C25E8370:01C40CBE]
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Hi Jagan,

The compressor knows (from the IP header "Protocol"  field) that its
payload contains UDP. However, as you observed, it doesn't know if the
UDP payload contains RTP.

The approach suggested is for the compressor to (optimistically?)
"assume" that the UDP payload contains RTP, and begin transmitting IR
packets for PROFILE 1.

However, as it transmits these IR packets, the compressor should also
observe the UDP payload, and heuristically try to determine whether
this is indeed RTP.

I guess your concern here is that during this time the compressor
could potentially send some "arbitrary" UDP payload content as RTP
fields in the IR packet. However, this shouldn't be a problem since
fields in the IR packet are used verbatim at the decompressor, so the
re-created header should remain the same.

If the stream is indeed RTP, the compressor can start shifting to a
higher state, and begin sending smaller ROHC packets, e.g., UO-0, etc.
If the UDP payload does not resemble RTP, the compressor can continue
sending the IR packets, but now indicate PROFILE 2 instead, after
which, start shifting to a higher state.

At the decompressor-end, no packets are lost/discarded since the
decompressor/decompressor support the same set of profiles, and hence,
all IR packets. There is no need for a feedback channel or "negative
compression ratios" calculations (which I didn't actually quite
follow!).

The tricky-bit is the compressor making an accurate selection of which
profile should be used, and once that is done, whatever ROHC stream it
generates should be decompressable by the other-end decompressor.

Regards,
vick
+----------------------------------------------------+
 Vicknesan AYADURAI <vicknesan.ayadurai@ericsson.com>
 Ericsson Research: IP Networks - Stockholm, Sweden
 Phone :  +46 8 5087 8084 / Fax:  +46 8 404 7020
+----------------------------------------------------+

On Wed, 17 Mar 2004, Jagan S wrote:

> Dear LarsErik,
>
> Thanks for the reply.
>
> >There is no way to explicitly know that packet stream is
> >an RTP stream, but one will have to guess. The good thing
> >with ROHC IP/UDP/RTP compression is that it is lossless,
> >independent of if the UDP payload is actually RTP or not.
> >One can thus start with assuming RTP, and if the compression
> >ratio turns out to be negative for the RTP part, a profile
> >switch to IP/UDP-only should be performed (see section 5.11).
>
> >Cheers,
> >/L-E
>
> ==> Assuming as RTP profile in the begining of transmission & then changing
> over to UDP/IP profile,
>  leads to packet losses. And moreover, if the profile is other than UDP/IP,
> again another changeover
>  is requried to another profile. Will this not lead to lower efficiency?
>
> Another issue is: in U mode, it may not be possible to calculate negative
> compression ratio,
>  due to the absence of feedback. In this case, the compressor keeps sending
> compressed packets
>  assuming the profile as RTP/UDP/IP !!!
>
> Is my understanding correct ??
>
>
> ~~~~~~~~~~~~~~~~~~~~
> Thanks & With warm regards.,
>
> Jagan S Nathan
>
> L&T Infotech, Bangalore.
>
>
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
>


This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Thu Mar 18 03:12:55 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26183
	for <rohc-archive@odin.ietf.org>; Thu, 18 Mar 2004 03:12:55 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sde-0001Cw-IK
	for rohc-archive@odin.ietf.org; Thu, 18 Mar 2004 03:12:27 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2I8CQ2t004636
	for rohc-archive@odin.ietf.org; Thu, 18 Mar 2004 03:12:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sde-0001Ch-66
	for rohc-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 03:12:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26180
	for <rohc-web-archive@ietf.org>; Thu, 18 Mar 2004 03:12:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sdc-0003HE-00
	for rohc-web-archive@ietf.org; Thu, 18 Mar 2004 03:12:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3sck-000392-00
	for rohc-web-archive@ietf.org; Thu, 18 Mar 2004 03:11:31 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3scG-000305-00
	for rohc-web-archive@ietf.org; Thu, 18 Mar 2004 03:11:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3scI-00016G-OS; Thu, 18 Mar 2004 03:11:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sbW-00014v-23
	for rohc@optimus.ietf.org; Thu, 18 Mar 2004 03:10:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26042
	for <rohc@ietf.org>; Thu, 18 Mar 2004 03:10:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sbS-0002xY-00
	for rohc@ietf.org; Thu, 18 Mar 2004 03:10:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3saV-0002q4-00
	for rohc@ietf.org; Thu, 18 Mar 2004 03:09:12 -0500
Received: from smtp1.home.se ([213.214.194.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sZm-0002je-00
	for rohc@ietf.org; Thu, 18 Mar 2004 03:08:26 -0500
Received: from jymden larsman@home.se [130.240.198.36]
	by smtp1.home.se with NetMail SMTP Agent $Revision:   3.22.1.8  $ on Novell NetWare;
	Thu, 18 Mar 2004 09:05:12 +0100
Message-ID: <01b401c40cc0$c4a29520$24c6f082@jymden>
From: "Lars-Erik Jonsson" <larsman@home.se>
To: "Vicknesan Ayadurai" <vicknesan.ayadurai@ericsson.com>,
        "Jagan S" <Jagan.S@lntinfotech.com>
Cc: <rohc@ietf.org>, <lars-erik.jonsson@ericsson.com>
References: <20040318084525.I3027-100000@caffreys.ericsson.se>
Subject: Re: RE: [rohc] ROHC: Header parsing
Date: Thu, 18 Mar 2004 09:12:34 +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
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> The tricky-bit is the compressor making an accurate selection of which
> profile should be used, and once that is done, whatever ROHC stream it
> generates should be decompressable by the other-end decompressor.

And note that the choice of compressing RTP is just an additional
compression improvement. It is a matter of compression efficiency,
the compressed stream will be decompressible with either profile,
independent of actual packet stream, and the compressor will see
from the packets (compressed) it generates whether an assumption
of RTP was correct (if all "RTP fields" are changing in a non-RTP
manner all the time, one can conclude that it is not RTP).

/L-E

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



From exim@www1.ietf.org  Fri Mar 19 09:53:16 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05733
	for <rohc-archive@odin.ietf.org>; Fri, 19 Mar 2004 09:53:15 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4LMe-0006BF-0F
	for rohc-archive@odin.ietf.org; Fri, 19 Mar 2004 09:52:48 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2JEqlAh023751
	for rohc-archive@odin.ietf.org; Fri, 19 Mar 2004 09:52:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4LMc-0006Az-Vq
	for rohc-web-archive@optimus.ietf.org; Fri, 19 Mar 2004 09:52:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05705
	for <rohc-web-archive@ietf.org>; Fri, 19 Mar 2004 09:52:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4LMa-0006sC-00
	for rohc-web-archive@ietf.org; Fri, 19 Mar 2004 09:52:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4LLf-0006mj-00
	for rohc-web-archive@ietf.org; Fri, 19 Mar 2004 09:51:50 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4LKy-0006i3-00
	for rohc-web-archive@ietf.org; Fri, 19 Mar 2004 09:51:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4LKw-00063s-Tn; Fri, 19 Mar 2004 09:51:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B44VG-0004Gf-KU
	for rohc@optimus.ietf.org; Thu, 18 Mar 2004 15:52:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08275
	for <rohc@ietf.org>; Thu, 18 Mar 2004 15:52:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B44VE-0002yn-00
	for rohc@ietf.org; Thu, 18 Mar 2004 15:52:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B44UJ-0002xe-00
	for rohc@ietf.org; Thu, 18 Mar 2004 15:51:36 -0500
Received: from cecom6.monmouth.army.mil ([134.80.0.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B44UD-0002wJ-00
	for rohc@ietf.org; Thu, 18 Mar 2004 15:51:29 -0500
Received: from mailsw2.monmouth.army.mil (mailsw2.monmouth.army.mil [134.80.5.41])
	by cecom6.monmouth.army.mil (8.12.11/8.12.11) with ESMTP id i2IKowEi015668
	for <rohc@ietf.org>; Thu, 18 Mar 2004 15:50:59 -0500 (EST)
Received: from SWGM6.monmouth.army.mil (unverified) by mailsw2.monmouth.army.mil
 (Content Technologies SMTPRS 4.3.12) with ESMTP id <T686b13ce07865005295bc@mailsw2.monmouth.army.mil> for <rohc@ietf.org>;
 Thu, 18 Mar 2004 15:50:58 -0500
Received: by SWGM6.monmouth.army.mil with Internet Mail Service (5.5.2657.72)
	id <GTTWD1JC>; Thu, 18 Mar 2004 15:50:58 -0500
Message-ID: <33120BB62E0A7643AE75E2B03CA0EDA0351F1E@mail7.monmouth.army.mil>
From: "Green, David B RDECOM CERDEC STCD SRI" <Dave.B.Green@us.army.mil>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Thu, 18 Mar 2004 15:50:56 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Subject: [rohc] Multpoint ROHC for MANET
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>

Has anyone in the group worked on a schema for point to multipoint robust
header compression 
suitable for broadcast and multicast links in MANETs? The base spec for ROHC
only seems to consider point to point links for cellular systems. I'm
normally in the MANET 
and IPv6 Ops groups but recently became very interested in ROHC as we see
ROHC as an enabling 
technolgy to get IPv6 working on a MANET radio system we are helping to
develop.
The protocol would need to be able to discover multiple neighbors, check to
see if they
are the recipients of multast or broadcast group messages, establish
compression contexts 
with them, have a mechanism to prevent collisions on any bi-directional
replies, and probably
several more problems I haven't thought of.

I'm working on a problem statement for the work now, so anyone interested
please let me know.

David B. Green
SRI International
desk (732) 532-6715
cell (732) 693-6500



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



From exim@www1.ietf.org  Fri Mar 19 09:53:16 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05734
	for <rohc-archive@odin.ietf.org>; Fri, 19 Mar 2004 09:53:15 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4LMc-0006Ay-UR
	for rohc-archive@odin.ietf.org; Fri, 19 Mar 2004 09:52:48 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2JEqkLb023734
	for rohc-archive@odin.ietf.org; Fri, 19 Mar 2004 09:52:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4LMc-0006Aj-ME
	for rohc-web-archive@optimus.ietf.org; Fri, 19 Mar 2004 09:52:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05702
	for <rohc-web-archive@ietf.org>; Fri, 19 Mar 2004 09:52:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4LMa-0006s7-00
	for rohc-web-archive@ietf.org; Fri, 19 Mar 2004 09:52:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4LLc-0006mc-00
	for rohc-web-archive@ietf.org; Fri, 19 Mar 2004 09:51:47 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4LKy-0006i2-00
	for rohc-web-archive@ietf.org; Fri, 19 Mar 2004 09:51:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4LKw-00063V-2m; Fri, 19 Mar 2004 09:51:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3n3l-0006Ty-Bh
	for rohc@optimus.ietf.org; Wed, 17 Mar 2004 21:15:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25475
	for <rohc@ietf.org>; Wed, 17 Mar 2004 21:14:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3n3i-00076c-00
	for rohc@ietf.org; Wed, 17 Mar 2004 21:14:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3n2n-0006z8-00
	for rohc@ietf.org; Wed, 17 Mar 2004 21:14:02 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3n1y-0006kW-00
	for rohc@ietf.org; Wed, 17 Mar 2004 21:13:10 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-2.cisco.com with ESMTP; 17 Mar 2004 18:16:28 +0000
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i2I2CcK2000424;
	Wed, 17 Mar 2004 18:12:38 -0800 (PST)
Received: from [10.32.130.100] ([10.32.130.100])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id ANI11783;
	Wed, 17 Mar 2004 18:12:07 -0800 (PST)
User-Agent: Microsoft-Entourage/10.1.4.030702.0
Date: Wed, 17 Mar 2004 18:12:06 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: <schatterjee@hss.hns.com>, <rohc@ietf.org>, <richard.price@roke.co.uk>,
        <cabo@tzi.org>, <jan.christoffersson@epl.ericsson.se>,
        <hans.hannu@epl.ericsson.se>, <zhigang.c.liu@nokia.com>,
        Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: <jbhalla@hss.hns.com>
Message-ID: <BC7E4576.35EE1%fluffy@cisco.com>
In-Reply-To: <OF95D34183.CD0C397F-ON65256E59.00471F64-65256E59.00488AB9@hss.hns.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3162391927_5882228"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE 
	autolearn=no version=2.60
Subject: [rohc] Re: [Sip-implementors] Implementation of Sigcomp
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3162391927_5882228
Content-type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable


I don=B9t think there is an open source one =AD Adam Roach has occasionally
talked about doing one in www.resiprocate.org stack.


On 3/16/04 5:12 AM, "schatterjee@hss.hns.com" <schatterjee@hss.hns.com>
wrote:

>=20
> Hi,=20
>=20
> Currently we are working on an implementation of Sigcomp. Can anyone tell=
 us
> if there are any open-source implementation available for this ?
>=20
> Regds,=20
> Suprabhat
>=20
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@cs.columbia.edu
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>=20



--B_3162391927_5882228
Content-type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [Sip-implementors] Implementation of Sigcomp </TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana"><SPAN STYLE=3D'font-size:14.0px'><BR>
I don&#8217;t think there is an open source one &#8211; Adam Roach has occa=
sionally talked about doing one in www.resiprocate.org stack.<BR>
<BR>
<BR>
On 3/16/04 5:12 AM, &quot;schatterjee@hss.hns.com&quot; &lt;schatterjee@hss=
.hns.com&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana"><SPAN STYLE=3D'font-size:14.0p=
x'><BR>
Hi, <BR>
<BR>
Currently we are working on an implementation of Sigcomp. Can anyone tell u=
s if there are any open-source implementation available for this ? <BR>
<BR>
Regds, <BR>
Suprabhat<BR>
<HR ALIGN=3DCENTER SIZE=3D"3" WIDTH=3D"95%"></SPAN></FONT><FONT FACE=3D"Monaco"><SP=
AN STYLE=3D'font-size:12.0px'><TT>____________________________________________=
___<BR>
Sip-implementors mailing list<BR>
Sip-implementors@cs.columbia.edu<BR>
<a href=3D"http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors">ht=
tp://lists.cs.columbia.edu/mailman/listinfo/sip-implementors</a><BR>
<BR>
</TT></SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Monaco"><SPAN STYLE=3D'font-size:=
12.0px'><TT><BR>
</TT></SPAN></FONT>
</BODY>
</HTML>


--B_3162391927_5882228--


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



From exim@www1.ietf.org  Mon Mar 22 03:27:53 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09861
	for <rohc-archive@odin.ietf.org>; Mon, 22 Mar 2004 03:27:52 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5KmJ-0001Wn-Ni
	for rohc-archive@odin.ietf.org; Mon, 22 Mar 2004 03:27:23 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2M8RNZb005806
	for rohc-archive@odin.ietf.org; Mon, 22 Mar 2004 03:27:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5KmH-0001VP-Nw
	for rohc-web-archive@optimus.ietf.org; Mon, 22 Mar 2004 03:27:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09853
	for <rohc-web-archive@ietf.org>; Mon, 22 Mar 2004 03:27:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5KmF-0006YY-00
	for rohc-web-archive@ietf.org; Mon, 22 Mar 2004 03:27:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5KlL-0006TT-00
	for rohc-web-archive@ietf.org; Mon, 22 Mar 2004 03:26:24 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Kl1-0006Nz-00
	for rohc-web-archive@ietf.org; Mon, 22 Mar 2004 03:26:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Kl1-00016N-8M; Mon, 22 Mar 2004 03:26:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5KkR-00014U-Lw
	for rohc@optimus.ietf.org; Mon, 22 Mar 2004 03:25:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09782
	for <rohc@ietf.org>; Mon, 22 Mar 2004 03:25:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5KkP-0006Mo-00
	for rohc@ietf.org; Mon, 22 Mar 2004 03:25:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5KjU-0006H0-00
	for rohc@ietf.org; Mon, 22 Mar 2004 03:24:29 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Kj4-0006As-00
	for rohc@ietf.org; Mon, 22 Mar 2004 03:24:02 -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 i2M8O2Ah016683
	for <rohc@ietf.org>; Mon, 22 Mar 2004 09:24:02 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 22 Mar 2004 09:24:02 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <HJTD7N50>; Mon, 22 Mar 2004 09:24:02 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E94CD@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'Green, David B RDECOM CERDEC STCD SRI'" <Dave.B.Green@us.army.mil>,
        "'rohc@ietf.org'" <rohc@ietf.org>
Subject: RE: [rohc] Multpoint ROHC for MANET
Date: Mon, 22 Mar 2004 09:23:56 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 22 Mar 2004 08:24:02.0502 (UTC) FILETIME=[08575660:01C40FE7]
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

David,

Would it be appropriate to use ROHC in unidirectional mode? The
compression scheme would then not depend on any feeback, and the
number of recipients would thus not affect the compression 
operation. A mapping (ROHC over xxxxx) would of course still
have to be defined.

/L-E

> -----Original Message-----
> From: rohc-admin@ietf.org [mailto:rohc-admin@ietf.org]On Behalf Of
> Green, David B RDECOM CERDEC STCD SRI
> Sent: den 18 mars 2004 21:51
> To: 'rohc@ietf.org'
> Subject: [rohc] Multpoint ROHC for MANET
> 
> 
> Has anyone in the group worked on a schema for point to 
> multipoint robust
> header compression 
> suitable for broadcast and multicast links in MANETs? The 
> base spec for ROHC
> only seems to consider point to point links for cellular systems. I'm
> normally in the MANET 
> and IPv6 Ops groups but recently became very interested in 
> ROHC as we see
> ROHC as an enabling 
> technolgy to get IPv6 working on a MANET radio system we are 
> helping to
> develop.
> The protocol would need to be able to discover multiple 
> neighbors, check to
> see if they
> are the recipients of multast or broadcast group messages, establish
> compression contexts 
> with them, have a mechanism to prevent collisions on any 
> bi-directional
> replies, and probably
> several more problems I haven't thought of.
> 
> I'm working on a problem statement for the work now, so 
> anyone interested
> please let me know.
> 
> David B. Green
> SRI International
> desk (732) 532-6715
> cell (732) 693-6500
> 
> 
> 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
> 

This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Mon Mar 22 03:47:26 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10524
	for <rohc-archive@odin.ietf.org>; Mon, 22 Mar 2004 03:47:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5L54-0002rl-Ik
	for rohc-archive@odin.ietf.org; Mon, 22 Mar 2004 03:46:58 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2M8kkEF011016
	for rohc-archive@odin.ietf.org; Mon, 22 Mar 2004 03:46:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5L53-0002rb-1h
	for rohc-web-archive@optimus.ietf.org; Mon, 22 Mar 2004 03:46:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10500
	for <rohc-web-archive@ietf.org>; Mon, 22 Mar 2004 03:46:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5L50-0000jm-00
	for rohc-web-archive@ietf.org; Mon, 22 Mar 2004 03:46:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5L42-0000bl-00
	for rohc-web-archive@ietf.org; Mon, 22 Mar 2004 03:45:43 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5L3S-0000TF-00
	for rohc-web-archive@ietf.org; Mon, 22 Mar 2004 03:45:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5L3T-0002lA-Gs; Mon, 22 Mar 2004 03:45:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5L2j-0002iB-DH
	for rohc@optimus.ietf.org; Mon, 22 Mar 2004 03:44:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10391
	for <rohc@ietf.org>; Mon, 22 Mar 2004 03:44:19 -0500 (EST)
From: Zongming.Zhou@commit.cn
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5L2g-0000PC-00
	for rohc@ietf.org; Mon, 22 Mar 2004 03:44:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5L1k-0000J6-00
	for rohc@ietf.org; Mon, 22 Mar 2004 03:43:20 -0500
Received: from [211.152.58.77] (helo=DIOSCURI.COMMIT)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5L1A-0000CK-00
	for rohc@ietf.org; Mon, 22 Mar 2004 03:42:45 -0500
To: rohc@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.11   July 24, 2002
Message-ID: <OFACFA924A.56F3A0FE-ON48256E5F.002F87E3-48256E5F.002FDEB1@COMMIT>
Date: Mon, 22 Mar 2004 16:42:26 +0800
X-MIMETrack: Serialize by Router on penelope/commit(Release 5.0.11  |July 24, 2002) at
 2004/03/22 04:43:04 PM,
	Serialize complete at 2004/03/22 04:43:04 PM
Content-Type: multipart/alternative; boundary="=_alternative 002FDEAE48256E5F_="
Subject: [rohc] how to tell p to peer decompressor entity?
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.7 required=5.0 tests=AWL,EXCUSE_16,MIME_BASE64_TEXT,
	NO_REAL_NAME autolearn=no version=2.60

This is a multipart message in MIME format.
--=_alternative 002FDEAE48256E5F_=
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

Zih2X3JlZiwgaykgPSBbdl9yZWYgLSBwLCB2X3JlZiArICgyXmsgLSAxKSAtIHBdDQoNCkluIGNo
YXB0ZXIgNC41LjEuTGVhc3QgU2lnbmlmaWNhbnQgQml0cyAoTFNCKSBlbmNvZGluZy9SRkMzMDk1
DQogDQogIFRoZSBpbnRlcnByZXRhdGlvbiBpbnRlcnZhbCBjYW4gYmUgZGVzY3JpYmVkIGFzIGEg
ZnVuY3Rpb24gZih2X3JlZiwgaykuIA0KTGV0DQogICAgICAgICAgICAgIGYodl9yZWYsIGspID0g
W3ZfcmVmIC0gcCwgdl9yZWYgKyAoMl5rIC0gMSkgLSBwXQ0KICAgd2hlcmUgcCBpcyBhbiBpbnRl
Z2VyLg0KICAgICAgICAgPC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0taW50ZXJwcmV0YXRpb24g
aW50ZXJ2YWwgKHNpemUgaXMgDQoyXmspLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPg0KIA0K
fC0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLXwNCiAgICAgICB2X3JlZiAtIHAgICAg
ICAgICAgICAgdl9yZWYgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHZfcmVmICsgDQoo
Ml5rLTEpIC0gcA0KDQpRZXN0aW9uLCBob3cgZG9lcyB0aGUgcGVlciBkZWNvbXByZXNzb3IgZW50
aXR5IGtub3dzIHdoaWNoIHZhbHVlIG9mIHAgaXMgDQp1c2VkPw0KQmVzdCBSZWdhcmRzDQogDQpa
aG91IFpvbmdtaW5nINbc19rD9w0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQpDT01NSVQgSW5jb3Jwb3Jh
dGVkDQpBZGQ6IDE4IFNoZW53YW5nIFJkLCBYaW56aHVhbmcgSW5kdXN0cmlhbCBEZXZlbG9wbWVu
dCBab25lLCBTaGFuZ2hhaSBDaGluYQ0KUG9zdCBDb2RlOiAyMDExMDgNClRlbDogKzg2LTIxLTU0
NDItNDg4NSBFeHQ6MzQwNQ0KRkFYOiArODYtMjEtNTQ0Mi00ODg2DQpFbWFpbDogem9uZ21pbmcu
emhvdUBjb21taXQuY24NCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0KVGhlIGluZm9ybWF0aW9uIGNvbnRh
aW5lZCBpbiB0aGlzIGUtbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIHRoZXJldG8gZnJvbSANCkNP
TU1JVCBJbmNvcnBvcmF0ZWQgaXMgaW50ZW5kZWQgdG8gYmUgZm9yIHRoZSB1c2Ugb2YgdGhlIHBl
cnNvbiBuYW1lZCANCmFib3ZlIGFuZCBtYXkgYmUgcHJpdmF0ZSwgY29uZmlkZW50aWFsIGFuZCBw
cml2aWxlZ2VkLiBJZiB5b3UgYXJlIG5vdCB0aGUgDQppbnRlbmRlZCByZWNpcGllbnQgb2YgdGhp
cyB0cmFuc21pc3Npb24sIHlvdSBhcmUgaGVyZWJ5IG5vdGlmaWVkIHRoYXQgYW55IA0KZGlzY2xv
c3VyZSwgY29weWluZywgZGlzdHJpYnV0aW9uLCBwcmludGluZyBvciB1c2Ugb2YgdGhlIGNvbnRl
bnRzIG9mIHRoaXMgDQpjb21tdW5pY2F0aW9uIGlzIHN0cmljdGx5IHByb2hpYml0ZWQuIElmIHlv
dSBoYXZlIHJlY2VpdmVkIHRoaXMgZS1tYWlsIGluIA0KZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhl
IHNlbmRlciBpbW1lZGlhdGVseSBhbmQgcGVybWFuZW50bHkgZGVsZXRlIHRoZSANCm9yaWdpbmFs
IGFuZCBhbnkgY29waWVzIG9mIHRoaXMgZW1haWwgYW5kIGFueSBhdHRhY2htZW50cyB0aGVyZXRv
Lg0K
--=_alternative 002FDEAE48256E5F_=
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGNvbG9yPXJlZCBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPmYodl9y
ZWYsIGspID0gW3ZfcmVmIC0gcCwgdl9yZWYgKyAoMl5rIC0gMSkgLSBwXTwvZm9udD4NCjxicj4N
Cjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+SW4gY2hhcHRlciA0LjUuMS5MZWFz
dCBTaWduaWZpY2FudCBCaXRzIChMU0IpIGVuY29kaW5nL1JGQzMwOTU8L2ZvbnQ+DQo8YnI+PGZv
bnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwOyAmbmJzcDs8L2ZvbnQ+DQo8YnI+PGZv
bnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwOyBUaGUgaW50ZXJwcmV0YXRpb24gaW50
ZXJ2YWwgY2FuIGJlIGRlc2NyaWJlZCBhcyBhIGZ1bmN0aW9uIGYodl9yZWYsIGspLiBMZXQ8L2Zv
bnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBmKHZfcmVmLCBrKSA9IFt2X3JlZiAtIHAs
IHZfcmVmICsgKDJeayAtIDEpIC0gcF08L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNh
bnMtc2VyaWYiPiZuYnNwOyAmbmJzcDt3aGVyZSBwIGlzIGFuIGludGVnZXIuPC9mb250Pg0KPGJy
Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7Jmx0Oy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0taW50ZXJwcmV0YXRpb24gaW50
ZXJ2YWwgKHNpemUgaXMgMl5rKS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSZndDs8L2ZvbnQ+
DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDt8LS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tfDwvZm9udD4N
Cjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7dl9yZWYgLSBwICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
IHZfcmVmICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwO3ZfcmVmICsgKDJeay0xKSAtIHA8L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZh
Y2U9InNhbnMtc2VyaWYiPlFlc3Rpb24sIGhvdyBkb2VzIHRoZSBwZWVyIGRlY29tcHJlc3NvciBl
bnRpdHkga25vd3Mgd2hpY2ggdmFsdWUgb2YgcCBpcyB1c2VkPzwvZm9udD4NCjxicj48Zm9udCBz
aXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+QmVzdCBSZWdhcmRzPGJyPg0KIDxicj4NClpob3UgWm9u
Z21pbmcg1tzX2sP3PGJyPg0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PGJyPg0KQ09NTUlUIEluY29ycG9y
YXRlZDxicj4NCkFkZDogMTggU2hlbndhbmcgUmQsIFhpbnpodWFuZyBJbmR1c3RyaWFsIERldmVs
b3BtZW50IFpvbmUsIFNoYW5naGFpIENoaW5hPGJyPg0KUG9zdCBDb2RlOiAyMDExMDg8YnI+DQpU
ZWw6ICs4Ni0yMS01NDQyLTQ4ODUgRXh0OjM0MDU8YnI+DQpGQVg6ICs4Ni0yMS01NDQyLTQ4ODY8
YnI+DQpFbWFpbDogem9uZ21pbmcuemhvdUBjb21taXQuY248YnI+DQo9PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT08YnI+DQpUaGUgaW5mb3JtYXRpb24gY29udGFpbmVkIGluIHRoaXMgZS1tYWlsIGFuZCBhbnkg
YXR0YWNobWVudHMgdGhlcmV0byBmcm9tIENPTU1JVCBJbmNvcnBvcmF0ZWQgaXMgaW50ZW5kZWQg
dG8gYmUgZm9yIHRoZSB1c2Ugb2YgdGhlIHBlcnNvbiBuYW1lZCBhYm92ZSBhbmQgbWF5IGJlIHBy
aXZhdGUsIGNvbmZpZGVudGlhbCBhbmQgcHJpdmlsZWdlZC4gSWYgeW91IGFyZSBub3QgdGhlIGlu
dGVuZGVkIHJlY2lwaWVudCBvZiB0aGlzIHRyYW5zbWlzc2lvbiwgeW91IGFyZSBoZXJlYnkgbm90
aWZpZWQgdGhhdCBhbnkgZGlzY2xvc3VyZSwgY29weWluZywgZGlzdHJpYnV0aW9uLCBwcmludGlu
ZyBvciB1c2Ugb2YgdGhlIGNvbnRlbnRzIG9mIHRoaXMgY29tbXVuaWNhdGlvbiBpcyBzdHJpY3Rs
eSBwcm9oaWJpdGVkLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGUtbWFpbCBpbiBlcnJvciwg
cGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGltbWVkaWF0ZWx5IGFuZCBwZXJtYW5lbnRseSBkZWxl
dGUgdGhlIG9yaWdpbmFsIGFuZCBhbnkgY29waWVzIG9mIHRoaXMgZW1haWwgYW5kIGFueSBhdHRh
Y2htZW50cyB0aGVyZXRvLjwvZm9udD4NCg==
--=_alternative 002FDEAE48256E5F_=--

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



From exim@www1.ietf.org  Mon Mar 22 04:10:11 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11289
	for <rohc-archive@odin.ietf.org>; Mon, 22 Mar 2004 04:10:11 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5LR6-0004ve-Kk
	for rohc-archive@odin.ietf.org; Mon, 22 Mar 2004 04:09:42 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2M99V2G018918
	for rohc-archive@odin.ietf.org; Mon, 22 Mar 2004 04:09:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5LR3-0004ur-2w
	for rohc-web-archive@optimus.ietf.org; Mon, 22 Mar 2004 04:09:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11286
	for <rohc-web-archive@ietf.org>; Mon, 22 Mar 2004 04:09:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5LR0-00033U-00
	for rohc-web-archive@ietf.org; Mon, 22 Mar 2004 04:09:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5LQB-0002yM-00
	for rohc-web-archive@ietf.org; Mon, 22 Mar 2004 04:08:36 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5LPf-0002rw-00
	for rohc-web-archive@ietf.org; Mon, 22 Mar 2004 04:08:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5LPf-0004gQ-Or; Mon, 22 Mar 2004 04:08:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5LOv-0004Zu-Aj
	for rohc@optimus.ietf.org; Mon, 22 Mar 2004 04:07:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11184
	for <rohc@ietf.org>; Mon, 22 Mar 2004 04:07:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5LOs-0002oM-00
	for rohc@ietf.org; Mon, 22 Mar 2004 04:07:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5LNu-0002gV-00
	for rohc@ietf.org; Mon, 22 Mar 2004 04:06:15 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5LMz-0002Zi-00
	for rohc@ietf.org; Mon, 22 Mar 2004 04:05:17 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2M95IYG014285
	for <rohc@ietf.org>; Mon, 22 Mar 2004 10:05:18 +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.0);
	 Mon, 22 Mar 2004 10:05:18 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <HJTD7619>; Mon, 22 Mar 2004 10:05:18 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E94D0@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'Zongming.Zhou@commit.cn'" <Zongming.Zhou@commit.cn>, rohc@ietf.org
Subject: RE: [rohc] how to tell p to peer decompressor entity?
Date: Mon, 22 Mar 2004 10:05:09 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C40FEC.9997FFF2"
X-OriginalArrivalTime: 22 Mar 2004 09:05:18.0162 (UTC) FILETIME=[CBF31320:01C40FEC]
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,EXCUSE_16,HTML_20_30,
	HTML_FONTCOLOR_BLUE,HTML_FONTCOLOR_UNKNOWN,HTML_MESSAGE autolearn=no 
	version=2.60

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C40FEC.9997FFF2
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

p is fixed for each packet format, see e.g page 75 of RFC 3095.
=20
/L-E

-----Original Message-----
From: rohc-admin@ietf.org [mailto:rohc-admin@ietf.org]On Behalf Of Zongmi=
ng.Zhou@commit.cn
Sent: den 22 mars 2004 09:42
To: rohc@ietf.org
Subject: [rohc] how to tell p to peer decompressor entity?



f(v_ref, k) =3D [v_ref - p, v_ref + (2^k - 1) - p]=20

In chapter 4.5.1.Least Significant Bits (LSB) encoding/RFC3095=20
   =20
  The interpretation interval can be described as a function f(v_ref, k).=
 Let=20
              f(v_ref, k) =3D [v_ref - p, v_ref + (2^k - 1) - p]=20
   where p is an integer.=20
         <--------------------------interpretation interval (size is 2^k)=
--------------------------->=20
         |---------------------+-----------------------------------------=
---------------------------|=20
       v_ref - p             v_ref                                v_ref +=
 (2^k-1) - p=20

Qestion, how does the peer decompressor entity knows which value of p is =
used?=20
Best Regards

Zhou Zongming =D6=DC=D7=DA=C3=F7
=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

COMMIT Incorporated
Add: 18 Shenwang Rd, Xinzhuang Industrial Development Zone, Shanghai Chin=
a
Post Code: 201108
Tel: +86-21-5442-4885 Ext:3405
FAX: +86-21-5442-4886
Email: zongming.zhou@commit.cn
=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

The information contained in this e-mail and any attachments thereto from=
 COMMIT Incorporated is intended to be for the use of the person named ab=
ove and may be private, confidential and privileged. If you are not the i=
ntended recipient of this transmission, you are hereby notified that any =
disclosure, copying, distribution, printing or use of the contents of thi=
s communication is strictly prohibited. If you have received this e-mail =
in error, please notify the sender immediately and permanently delete the=
 original and any copies of this email and any attachments thereto.=20


This communication is confidential and intended solely for the addressee(=
s). Any unauthorized review, use, disclosure or distribution is prohibite=
d. If you believe this message has been sent to you in error, please noti=
fy the sender by replying to this transmission and delete the message wit=
hout disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interrupt=
ion, unauthorized amendment, tampering and viruses, and we only send and =
receive e-mails on the basis that we are not liable for any such corrupti=
on, interception, amendment, tampering or viruses or any consequences the=
reof.


------_=_NextPart_001_01C40FEC.9997FFF2
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dgb2312"=
>


<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D337550309-22032004><FONT face=3DArial color=3D#0000ff =
size=3D2>p is=20
fixed for each packet format, see e.g page 75 of RFC 3095.</FONT></SPAN><=
/DIV>
<DIV><SPAN class=3D337550309-22032004></SPAN><SPAN class=3D337550309-2203=
2004><FONT=20
face=3DArial color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D337550309-22032004><FONT face=3DArial color=3D#0000ff=20=

size=3D2>/L-E</FONT></SPAN></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px so=
lid">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT face=3DT=
ahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> rohc-admin@ietf.org=
=20
  [mailto:rohc-admin@ietf.org]<B>On Behalf Of=20
  </B>Zongming.Zhou@commit.cn<BR><B>Sent:</B> den 22 mars 2004=20
  09:42<BR><B>To:</B> rohc@ietf.org<BR><B>Subject:</B> [rohc] how to tell=
 p to=20
  peer decompressor entity?<BR><BR></FONT></DIV><BR><FONT face=3D"Times N=
ew Roman"=20
  color=3Dred size=3D2>f(v_ref, k) =3D [v_ref - p, v_ref + (2^k - 1) - p]=
</FONT>=20
  <BR><BR><FONT face=3Dsans-serif size=3D2>In chapter 4.5.1.Least Signifi=
cant Bits=20
  (LSB) encoding/RFC3095</FONT> <BR><FONT face=3Dsans-serif size=3D2>&nbs=
p;=20
  &nbsp;</FONT> <BR><FONT face=3Dsans-serif size=3D2>&nbsp; The interpret=
ation=20
  interval can be described as a function f(v_ref, k). Let</FONT> <BR><FO=
NT=20
  face=3Dsans-serif size=3D2>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp;=20
  f(v_ref, k) =3D [v_ref - p, v_ref + (2^k - 1) - p]</FONT> <BR><FONT=20
  face=3Dsans-serif size=3D2>&nbsp; &nbsp;where p is an integer.</FONT> <=
BR><FONT=20
  face=3Dsans-serif size=3D2>&nbsp; &nbsp; &nbsp; &nbsp;=20
  &nbsp;&lt;--------------------------interpretation interval (size is=20=

  2^k)---------------------------&gt;</FONT> <BR><FONT face=3Dsans-serif=20=

  size=3D2>&nbsp; &nbsp; &nbsp; &nbsp;=20
  &nbsp;|---------------------+------------------------------------------=
--------------------------|</FONT>=20
  <BR><FONT face=3Dsans-serif size=3D2>&nbsp; &nbsp; &nbsp; &nbsp;v_ref -=
 p &nbsp;=20
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; v_ref &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp;=20
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=20=

  &nbsp;v_ref + (2^k-1) - p</FONT> <BR><BR><FONT face=3Dsans-serif size=3D=
2>Qestion,=20
  how does the peer decompressor entity knows which value of p is used?</=
FONT>=20
  <BR><FONT face=3Dsans-serif size=3D2>Best Regards<BR><BR>Zhou Zongming=20=

  =D6=DC=D7=DA=C3=F7<BR>=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=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D<BR>COMMIT=20
  Incorporated<BR>Add: 18 Shenwang Rd, Xinzhuang Industrial Development Z=
one,=20
  Shanghai China<BR>Post Code: 201108<BR>Tel: +86-21-5442-4885 Ext:3405<B=
R>FAX:=20
  +86-21-5442-4886<BR>Email:=20
  zongming.zhou@commit.cn<BR>=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=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>The=20
  information contained in this e-mail and any attachments thereto from C=
OMMIT=20
  Incorporated is intended to be for the use of the person named above an=
d may=20
  be private, confidential and privileged. If you are not the intended re=
cipient=20
  of this transmission, you are hereby notified that any disclosure, copy=
ing,=20
  distribution, printing or use of the contents of this communication is=20=

  strictly prohibited. If you have received this e-mail in error, please =
notify=20
  the sender immediately and permanently delete the original and any copi=
es of=20
  this email and any attachments thereto.</FONT> </BLOCKQUOTE><br>This co=
mmunication is confidential and intended solely for the addressee(s). Any=
 unauthorized review, use, disclosure or distribution is prohibited. If y=
ou believe this message has been sent to you in error, please notify the =
sender by replying to this transmission and delete the message without di=
sclosing it. Thank you.<br><br>E-mail including attachments is susceptibl=
e to data corruption, interruption, unauthorized amendment, tampering and=
 viruses, and we only send and receive e-mails on the basis that we are n=
ot liable for any such corruption, interception, amendment, tampering or =
viruses or any consequences thereof.<br></BODY></HTML>

------_=_NextPart_001_01C40FEC.9997FFF2--

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



From exim@www1.ietf.org  Tue Mar 23 01:27:45 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23250
	for <rohc-archive@odin.ietf.org>; Tue, 23 Mar 2004 01:27:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5fNR-0001rR-30
	for rohc-archive@odin.ietf.org; Tue, 23 Mar 2004 01:27:16 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2N6R5U9007131
	for rohc-archive@odin.ietf.org; Tue, 23 Mar 2004 01:27:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5fNQ-0001qn-6f
	for rohc-web-archive@optimus.ietf.org; Tue, 23 Mar 2004 01:27:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23235
	for <rohc-web-archive@ietf.org>; Tue, 23 Mar 2004 01:27:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5fNN-000453-00
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 01:27:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5fMO-0003z8-00
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 01:26:01 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5fLQ-0003ti-00
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 01:25:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5fLT-0001Zh-3D; Tue, 23 Mar 2004 01:25:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5fKd-0001Xi-Dr
	for rohc@optimus.ietf.org; Tue, 23 Mar 2004 01:24:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23173
	for <rohc@ietf.org>; Tue, 23 Mar 2004 01:24:09 -0500 (EST)
From: Zongming.Zhou@commit.cn
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5fKa-0003oK-00
	for rohc@ietf.org; Tue, 23 Mar 2004 01:24:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5fJe-0003iP-00
	for rohc@ietf.org; Tue, 23 Mar 2004 01:23:11 -0500
Received: from [211.152.58.77] (helo=DIOSCURI.COMMIT)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5fJB-0003ZK-00
	for rohc@ietf.org; Tue, 23 Mar 2004 01:22:42 -0500
To: rohc@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.11   July 24, 2002
Message-ID: <OFBFFC64A5.8FDB5CAC-ON48256E60.0021EA15-48256E60.00230824@COMMIT>
Date: Tue, 23 Mar 2004 14:22:12 +0800
X-MIMETrack: Serialize by Router on penelope/commit(Release 5.0.11  |July 24, 2002) at
 2004/03/23 02:23:00 PM,
	Serialize complete at 2004/03/23 02:23:00 PM
Content-Type: multipart/alternative; boundary="=_alternative 0023082148256E60_="
Subject: [rohc] MUST FEEDBACK-2 be used if LARGE CID is configured?
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.6 required=5.0 tests=AWL,EXCUSE_16,MIME_BASE64_TEXT,
	NO_REAL_NAME autolearn=no version=2.60

This is a multipart message in MIME format.
--=_alternative 0023082148256E60_=
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

SWYgIEZFRURCQUNLLTIgTVVTVCBiZSB1c2VkIGlmIExBUkdFIENJRCBpcyBjb25maWd1cmVkLCBk
ZXNjcmlwdGlvbiBpbiB0aGUgDQpsYXN0IG9mIENoYXRlciA1LjIuMi9SRkMzMDk1IA0Kc2hvdWxk
IGJlIG1vZGlmaWVkIG9yZGVyIHRvIGdpdmUgYSBkZXRhaWxlZCBhbmQgY2xlYXJseSBkZXNjcml0
aW9uLg0KDQpPcmlnaW5hbCBjb3B5IG9mIENoYXB0ZXIgNS4yLjIsIFJGQzMwOTUNClRoZSBjb21w
cmVzc29yIGNhbiB1c2UgdGhlIGZvbGxvd2luZyBsb2dpYyB0byBwYXJzZSB0aGUgZmVlZGJhY2sg
ZmllbGQuDQoxKSBJZiBmb3IgbGFyZ2UgQ0lEcywgdGhlIGZlZWRiYWNrIHdpbGwgYWx3YXlzIHN0
YXJ0IHdpdGggYSBDSUQgZW5jb2RlZCANCmFjY29yZGluZyB0bw0KICAgc2VjdGlvbiA0LjUuNi4g
SWYgdGhlIGZpcnN0IGJpdCBpcyAwLCB0aGUgQ0lEIHVzZXMgb25lIG9jdGV0LiBJZiB0aGUgDQpm
aXJzdCBiaXQgaXMNCiAgIDEsIHRoZSBDSUQgdXNlcyB0d28gb2N0ZXRzLg0KMikgSWYgZm9yIHNt
YWxsIENJRHMsIGFuZCB0aGUgc2l6ZSBpcyBvbmUgb2N0ZXQsIHRoZSBmZWVkYmFjayBpcyBhIA0K
RkVFREJBQ0stMS4NCjMpIElmIGZvciBzbWFsbCBDSURzLCBhbmQgdGhlIHNpemUgaXMgbGFyZ2Vy
IHRoYW4gb25lIG9jdGV0LCBhbmQgdGhlIA0KZmVlZGJhY2sgc3RhcnRzDQogICB3aXRoIHRoZSB0
d28gYml0cyAxMSwgdGhlIGZlZWRiYWNrIHN0YXJ0cyB3aXRoIGFuIEFkZC1DSUQgb2N0ZXQuIElm
IHRoZSANCnNpemUgaXMgMiwNCiAgIGl0IGlzIGZvbGxvd2VkIGJ5IEZFRURCQUNLLTEuIElmIHRo
ZSBzaXplIGlzIGxhcmdlciB0aGFuIDIsIHRoZSBBZGQtQ0lEIA0KaXMgZm9sbG93ZWQNCiAgIGJ5
IEZFRURCQUNLLTIuDQo0KSBPdGhlcndpc2UsIHRoZXJlIGlzIG5vIEFkZC1DSUQgb2N0ZXQsIGFu
ZCB0aGUgZmVlZGJhY2sgc3RhcnRzIHdpdGggYSANCkZFRURCQUNLLTIuDQoNCk1vZGlmaWNhdGlv
biB0byBDaGFwdGVyIDUuMi4yL1JGQzMwOTUNCkZvciBMYXJnZSBDSUQgDQogICAgICB0aGUgZmVl
ZGJhY2sgd2lsbCBhbHdheXMgc3RhcnQgd2l0aCBhIENJRCBlbmNvZGVkIGFjY29yZGluZyB0byBz
ZWN0aW9uIA0KNC41LjYuIElmIA0KICAgdGhlIGZpcnN0IGJpdCBpcyAwLCB0aGUgQ0lEIHVzZXMg
b25lIG9jdGV0LiBJZiB0aGUgZmlyc3QgYml0IGlzIDEsIHRoZSANCkNJRCB1c2VzDQogICB0d28g
b2N0ZXRzLiBBbmQgRkVFREJBQ0stMiBtdXN0IGJlIHVzZWQuDQoNCkZvciBzbWFsbCBDSUQ6IA0K
ICAgMSkgSWYgdGhlIHNpemUgaXMgb25lIG9jdGV0LCB0aGUgZmVlZGJhY2sgaXMgYSBGRUVEQkFD
Sy0xLg0KICAgMikgSWYgdGhlIHNpemUgaXMgbGFyZ2VyIHRoYW4gb25lIG9jdGV0LCBhbmQgdGhl
IGZlZWRiYWNrIHN0YXJ0cyB3aXRoIA0KdGhlIHR3byBiaXRzIDExLA0KICAgICAgdGhlIGZlZWRi
YWNrIHN0YXJ0cyB3aXRoIGFuIEFkZC1DSUQgb2N0ZXQuSWYgdGhlIHNpemUgaXMgMixpdCBpcyAN
CmZvbGxvd2VkIGJ5IA0KICAgICAgRkVFREJBQ0stMS4gSWYgdGhlIHNpemUgaXMgbGFyZ2VyIHRo
YW4gMiwgdGhlIEFkZC1DSUQgaXMgZm9sbG93ZWQgYnkgDQpGRUVEQkFDSy0yLg0KICAgMykgT3Ro
ZXJ3aXNlLCB0aGVyZSBpcyBubyBBZGQtQ0lEIG9jdGV0LCBhbmQgdGhlIGZlZWRiYWNrIHN0YXJ0
cyB3aXRoIGEgDQpGRUVEQkFDSy0yLg0KDQoNCg0KQmVzdCBSZWdhcmRzDQogDQpaaG91IFpvbmdt
aW5nINbc19rD9w0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQpDT01NSVQgSW5jb3Jwb3JhdGVkDQpBZGQ6
IDE4IFNoZW53YW5nIFJkLCBYaW56aHVhbmcgSW5kdXN0cmlhbCBEZXZlbG9wbWVudCBab25lLCBT
aGFuZ2hhaSBDaGluYQ0KUG9zdCBDb2RlOiAyMDExMDgNClRlbDogKzg2LTIxLTU0NDItNDg4NSBF
eHQ6MzQwNQ0KRkFYOiArODYtMjEtNTQ0Mi00ODg2DQpFbWFpbDogem9uZ21pbmcuemhvdUBjb21t
aXQuY24NCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PQ0KVGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBpbiB0
aGlzIGUtbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIHRoZXJldG8gZnJvbSANCkNPTU1JVCBJbmNv
cnBvcmF0ZWQgaXMgaW50ZW5kZWQgdG8gYmUgZm9yIHRoZSB1c2Ugb2YgdGhlIHBlcnNvbiBuYW1l
ZCANCmFib3ZlIGFuZCBtYXkgYmUgcHJpdmF0ZSwgY29uZmlkZW50aWFsIGFuZCBwcml2aWxlZ2Vk
LiBJZiB5b3UgYXJlIG5vdCB0aGUgDQppbnRlbmRlZCByZWNpcGllbnQgb2YgdGhpcyB0cmFuc21p
c3Npb24sIHlvdSBhcmUgaGVyZWJ5IG5vdGlmaWVkIHRoYXQgYW55IA0KZGlzY2xvc3VyZSwgY29w
eWluZywgZGlzdHJpYnV0aW9uLCBwcmludGluZyBvciB1c2Ugb2YgdGhlIGNvbnRlbnRzIG9mIHRo
aXMgDQpjb21tdW5pY2F0aW9uIGlzIHN0cmljdGx5IHByb2hpYml0ZWQuIElmIHlvdSBoYXZlIHJl
Y2VpdmVkIHRoaXMgZS1tYWlsIGluIA0KZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBp
bW1lZGlhdGVseSBhbmQgcGVybWFuZW50bHkgZGVsZXRlIHRoZSANCm9yaWdpbmFsIGFuZCBhbnkg
Y29waWVzIG9mIHRoaXMgZW1haWwgYW5kIGFueSBhdHRhY2htZW50cyB0aGVyZXRvLg0K
--=_alternative 0023082148256E60_=
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+SWYgJm5ic3A7RkVFREJB
Q0stMiBNVVNUIGJlIHVzZWQgaWYgTEFSR0UgQ0lEIGlzIGNvbmZpZ3VyZWQsIGRlc2NyaXB0aW9u
IGluIHRoZSBsYXN0IG9mIENoYXRlciA8L2ZvbnQ+PGZvbnQgc2l6ZT0yPjx0dD41LjIuMi9SRkMz
MDk1PC90dD48L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+IDwvZm9u
dD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj5zaG91bGQgYmUgbW9k
aWZpZWQgb3JkZXIgdG8gZ2l2ZSBhIGRldGFpbGVkIGFuZCBjbGVhcmx5IGRlc2NyaXRpb24uPC9m
b250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBjb2xvcj1yZWQ+PHR0Pk9yaWdpbmFsIGNvcHkg
b2YgQ2hhcHRlciA1LjIuMiwgUkZDMzA5NTwvdHQ+PC9mb250Pg0KPGJyPjxmb250IHNpemU9Mj48
dHQ+VGhlIGNvbXByZXNzb3IgY2FuIHVzZSB0aGUgZm9sbG93aW5nIGxvZ2ljIHRvIHBhcnNlIHRo
ZSBmZWVkYmFjayBmaWVsZC48L3R0PjwvZm9udD4NCjxicj48Zm9udCBzaXplPTI+PHR0PjEpIElm
IGZvciBsYXJnZSBDSURzLCB0aGUgZmVlZGJhY2sgd2lsbCBhbHdheXMgc3RhcnQgd2l0aCBhIENJ
RCBlbmNvZGVkIGFjY29yZGluZyB0bzwvdHQ+PC9mb250Pg0KPGJyPjxmb250IHNpemU9Mj48dHQ+
Jm5ic3A7ICZuYnNwO3NlY3Rpb24gNC41LjYuIElmIHRoZSBmaXJzdCBiaXQgaXMgMCwgdGhlIENJ
RCB1c2VzIG9uZSBvY3RldC4gSWYgdGhlIGZpcnN0IGJpdCBpczwvdHQ+PC9mb250Pg0KPGJyPjxm
b250IHNpemU9Mj48dHQ+Jm5ic3A7ICZuYnNwOzEsIHRoZSBDSUQgdXNlcyB0d28gb2N0ZXRzLjwv
dHQ+PC9mb250Pg0KPGJyPjxmb250IHNpemU9Mj48dHQ+MikgSWYgZm9yIHNtYWxsIENJRHMsIGFu
ZCB0aGUgc2l6ZSBpcyBvbmUgb2N0ZXQsIHRoZSBmZWVkYmFjayBpcyBhIEZFRURCQUNLLTEuPC90
dD48L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yPjx0dD4zKSBJZiBmb3Igc21hbGwgQ0lEcywgYW5k
IHRoZSBzaXplIGlzIGxhcmdlciB0aGFuIG9uZSBvY3RldCwgYW5kIHRoZSBmZWVkYmFjayBzdGFy
dHM8L3R0PjwvZm9udD4NCjxicj48Zm9udCBzaXplPTI+PHR0PiZuYnNwOyAmbmJzcDt3aXRoIHRo
ZSB0d28gYml0cyAxMSwgdGhlIGZlZWRiYWNrIHN0YXJ0cyB3aXRoIGFuIEFkZC1DSUQgb2N0ZXQu
IElmIHRoZSBzaXplIGlzIDIsPC90dD48L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yPjx0dD4mbmJz
cDsgJm5ic3A7aXQgaXMgZm9sbG93ZWQgYnkgRkVFREJBQ0stMS4gSWYgdGhlIHNpemUgaXMgbGFy
Z2VyIHRoYW4gMiwgdGhlIEFkZC1DSUQgaXMgZm9sbG93ZWQ8L3R0PjwvZm9udD4NCjxicj48Zm9u
dCBzaXplPTI+PHR0PiZuYnNwOyAmbmJzcDtieSBGRUVEQkFDSy0yLjwvdHQ+PC9mb250Pg0KPGJy
Pjxmb250IHNpemU9Mj48dHQ+NCkgT3RoZXJ3aXNlLCB0aGVyZSBpcyBubyBBZGQtQ0lEIG9jdGV0
LCBhbmQgdGhlIGZlZWRiYWNrIHN0YXJ0cyB3aXRoIGEgRkVFREJBQ0stMi48L3R0PjwvZm9udD4N
Cjxicj4NCjxicj48Zm9udCBzaXplPTIgY29sb3I9cmVkIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+
TW9kaWZpY2F0aW9uIHRvIENoYXB0ZXIgNS4yLjIvUkZDMzA5NTwvZm9udD4NCjxicj48Zm9udCBz
aXplPTIgY29sb3I9Ymx1ZSBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPkZvciBMYXJnZSBDSUQgPC9m
b250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPiZuYnNwOyAmbmJz
cDsgJm5ic3A7IDwvZm9udD48Zm9udCBzaXplPTI+PHR0PnRoZSBmZWVkYmFjayB3aWxsIGFsd2F5
cyBzdGFydCB3aXRoIGEgQ0lEIGVuY29kZWQgYWNjb3JkaW5nIHRvIHNlY3Rpb24gNC41LjYuIElm
IDwvdHQ+PC9mb250Pg0KPGJyPjxmb250IHNpemU9Mj48dHQ+Jm5ic3A7ICZuYnNwO3RoZSBmaXJz
dCBiaXQgaXMgMCwgdGhlIENJRCB1c2VzIG9uZSBvY3RldC4gSWYgdGhlIGZpcnN0IGJpdCBpcyAx
LCB0aGUgQ0lEIHVzZXM8L3R0PjwvZm9udD4NCjxicj48Zm9udCBzaXplPTI+PHR0PiZuYnNwOyAm
bmJzcDt0d28gb2N0ZXRzLiA8L3R0PjwvZm9udD48Zm9udCBzaXplPTIgY29sb3I9Ymx1ZT48dHQ+
QW5kIEZFRURCQUNLLTIgbXVzdCBiZSB1c2VkLjwvdHQ+PC9mb250Pg0KPGJyPg0KPGJyPjxmb250
IHNpemU9MiBjb2xvcj1ibHVlPjx0dD5Gb3Igc21hbGwgQ0lEOiA8L3R0PjwvZm9udD4NCjxicj48
Zm9udCBzaXplPTI+PHR0PiZuYnNwOyAmbmJzcDsxKSBJZiB0aGUgc2l6ZSBpcyBvbmUgb2N0ZXQs
IHRoZSBmZWVkYmFjayBpcyBhIEZFRURCQUNLLTEuPC90dD48L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6
ZT0yPjx0dD4mbmJzcDsgJm5ic3A7MikgSWYgdGhlIHNpemUgaXMgbGFyZ2VyIHRoYW4gb25lIG9j
dGV0LCBhbmQgdGhlIGZlZWRiYWNrIHN0YXJ0cyB3aXRoIHRoZSB0d28gYml0cyAxMSw8L3R0Pjwv
Zm9udD4NCjxicj48Zm9udCBzaXplPTI+PHR0PiZuYnNwOyAmbmJzcDsgJm5ic3A7IHRoZSBmZWVk
YmFjayBzdGFydHMgd2l0aCBhbiBBZGQtQ0lEIG9jdGV0LklmIHRoZSBzaXplIGlzIDIsaXQgaXMg
Zm9sbG93ZWQgYnkgPC90dD48L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yPjx0dD4mbmJzcDsgJm5i
c3A7ICZuYnNwOyBGRUVEQkFDSy0xLiBJZiB0aGUgc2l6ZSBpcyBsYXJnZXIgdGhhbiAyLCB0aGUg
QWRkLUNJRCBpcyBmb2xsb3dlZCBieSBGRUVEQkFDSy0yLjwvdHQ+PC9mb250Pg0KPGJyPjxmb250
IHNpemU9Mj48dHQ+Jm5ic3A7ICZuYnNwOzMpIE90aGVyd2lzZSwgdGhlcmUgaXMgbm8gQWRkLUNJ
RCBvY3RldCwgYW5kIHRoZSBmZWVkYmFjayBzdGFydHMgd2l0aCBhIEZFRURCQUNLLTIuPC90dD48
L2ZvbnQ+DQo8YnI+DQo8YnI+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2Vy
aWYiPkJlc3QgUmVnYXJkczxicj4NCiA8YnI+DQpaaG91IFpvbmdtaW5nINbc19rD9zxicj4NCj09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PTxicj4NCkNPTU1JVCBJbmNvcnBvcmF0ZWQ8YnI+DQpBZGQ6IDE4IFNo
ZW53YW5nIFJkLCBYaW56aHVhbmcgSW5kdXN0cmlhbCBEZXZlbG9wbWVudCBab25lLCBTaGFuZ2hh
aSBDaGluYTxicj4NClBvc3QgQ29kZTogMjAxMTA4PGJyPg0KVGVsOiArODYtMjEtNTQ0Mi00ODg1
IEV4dDozNDA1PGJyPg0KRkFYOiArODYtMjEtNTQ0Mi00ODg2PGJyPg0KRW1haWw6IHpvbmdtaW5n
Lnpob3VAY29tbWl0LmNuPGJyPg0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PGJyPg0KVGhlIGluZm9ybWF0
aW9uIGNvbnRhaW5lZCBpbiB0aGlzIGUtbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIHRoZXJldG8g
ZnJvbSBDT01NSVQgSW5jb3Jwb3JhdGVkIGlzIGludGVuZGVkIHRvIGJlIGZvciB0aGUgdXNlIG9m
IHRoZSBwZXJzb24gbmFtZWQgYWJvdmUgYW5kIG1heSBiZSBwcml2YXRlLCBjb25maWRlbnRpYWwg
YW5kIHByaXZpbGVnZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQgb2Yg
dGhpcyB0cmFuc21pc3Npb24sIHlvdSBhcmUgaGVyZWJ5IG5vdGlmaWVkIHRoYXQgYW55IGRpc2Ns
b3N1cmUsIGNvcHlpbmcsIGRpc3RyaWJ1dGlvbiwgcHJpbnRpbmcgb3IgdXNlIG9mIHRoZSBjb250
ZW50cyBvZiB0aGlzIGNvbW11bmljYXRpb24gaXMgc3RyaWN0bHkgcHJvaGliaXRlZC4gSWYgeW91
IGhhdmUgcmVjZWl2ZWQgdGhpcyBlLW1haWwgaW4gZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhlIHNl
bmRlciBpbW1lZGlhdGVseSBhbmQgcGVybWFuZW50bHkgZGVsZXRlIHRoZSBvcmlnaW5hbCBhbmQg
YW55IGNvcGllcyBvZiB0aGlzIGVtYWlsIGFuZCBhbnkgYXR0YWNobWVudHMgdGhlcmV0by48L2Zv
bnQ+DQo=
--=_alternative 0023082148256E60_=--

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



From exim@www1.ietf.org  Tue Mar 23 08:31:53 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25268
	for <rohc-archive@odin.ietf.org>; Tue, 23 Mar 2004 08:31:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5m04-0004f0-Rf
	for rohc-archive@odin.ietf.org; Tue, 23 Mar 2004 08:31:24 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2NDVO3N017913
	for rohc-archive@odin.ietf.org; Tue, 23 Mar 2004 08:31:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5m04-0004eq-NM
	for rohc-web-archive@optimus.ietf.org; Tue, 23 Mar 2004 08:31:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25234
	for <rohc-web-archive@ietf.org>; Tue, 23 Mar 2004 08:31:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5m03-0000uO-00
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 08:31:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5lz5-0000nW-00
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 08:30:24 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5lyn-0000hB-00
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 08:30:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5lym-0004TN-3t; Tue, 23 Mar 2004 08:30:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5lxz-0004RK-Mt
	for rohc@optimus.ietf.org; Tue, 23 Mar 2004 08:29:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25093
	for <rohc@ietf.org>; Tue, 23 Mar 2004 08:29:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5lxy-0000e6-00
	for rohc@ietf.org; Tue, 23 Mar 2004 08:29:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5lww-0000VP-00
	for rohc@ietf.org; Tue, 23 Mar 2004 08:28:11 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5lvw-0000Hc-00; Tue, 23 Mar 2004 08:27:09 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2NDR6qY003055;
	Tue, 23 Mar 2004 14:27:07 +0100 (MET)
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 23 Mar 2004 14:27:06 +0100
Received: from lms001.lu.erisoft.se ([150.132.144.19]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id HJS56FYM; Tue, 23 Mar 2004 14:27:15 +0100
Received: by lms001.lu.erisoft.se id OAA13961; Tue, 23 Mar 2004 14:27:10 +0100 (MET)
Message-ID: <40603B25.3E133C79@ericsson.com>
Date: Tue, 23 Mar 2004 14:27:01 +0100
X-Sybari-Trust: ac83756e 2c4885b5 26315a68 00000138
From: Ghyslain Pelletier <Ghyslain.Pelletier@ericsson.com>
Organization: Ericsson Erisoft AB, Ericsson Research Corporate Unit
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>, Carsten Bormann <cabo@tzi.org>,
        "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@ericsson.com>,
        "rohc@ietf.org" <rohc@ietf.org>
CC: seamoby@ietf.org
References: <033d01c4088d$017a74f0$366115ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=iso-8859-1
X-OriginalArrivalTime: 23 Mar 2004 13:27:06.0840 (UTC) FILETIME=[8976DD80:01C410DA]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by albatross-ext.wise.edt.ericsson.se id i2NDR6qY003055
Content-Transfer-Encoding: quoted-printable
Subject: [rohc] Re: [Seamoby] AD Review Issues with draft-ietf-seamoby-ctp-08.txt
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi,

> The review by someone from the ROHC WG turned up no issues.

Who is this reviewer? What were the comments?
If I understand correctly from an earlier mail from James Kempf (March
11th), this person is not Carsten Bormann, and I know that it is not his
ROHC co-chair either for having asked.

I think the draft should be submitted for review to the ROHC wg via
their mailing list. After all, it has been written many times on the
Seamoby mailing list that "ROHC is a potential customer of CTP", so I
don't see any reason not to send the document for a somewhat broader
review to that wg.

Best regards,

/Ghyslain =20

James Kempf wrote:
>=20
> AD Review of the CTP draft (draft-ietf-seamoby-ctp-08.txt) is now compl=
ete.
> The review by someone from the ROHC WG turned up no issues. However, in
> discussions with Allison, there were a couple issues that arose. They a=
re
> listed below. Prior to submitting a revised draft to the IESG for revie=
w,
> Allison and I would like to obtain resolution on these issues. Please s=
end
> comments to the list by next Fri. (March 19).
>=20
>             jak
>=20
> -------------------------------
>=20
> Issue 1
> --------
>=20
> Issue: The MLD example in Appendix B as written is not very persuasive.=
 The
> 3G protocols don't use ND, and 802.11 is fast enough that it wouldn't m=
ake
> much difference.
>=20
> Suggested resolution: Replace the first paragraph of Appendix B with th=
e
> following:
>=20
>    In the past, credible proposals have been made in the Seamoby Workin=
g
> Group
>    and elsewhere for using context transfer to speed handover of
> authentication, authorization,
>    and accounting information, distributed firewall state, PPP context,=
 and
> header
>    compression context. Because the Working Group was not chartered to
>    develop context profile definitions for specific applications, none =
of
> the proposals
>    submitted to Seamoby were accepted as Working Group items. At this t=
ime,
> work
>    continues to develop a context profile definition for RFC 3095 heade=
r
> compression
>    context [RFC3095] and to characterize the performance gains obtainab=
le by
> using
>    header compression, but the work is not yet complete. In addition, t=
here
> are several
>    commercial wireless products that reportedly use non-standard,
> non-interoperable
>    context transfer protocols.
>=20
>    As a consequence, it is difficult at this time to point to with a so=
lid
> example of
>    how context transfer could result in a commercially viable, widely
> deployable,
>    interoperable benefit  for wireless networks. This is one reason why=
 CTP
> is being
>    proposed as an Experimental protocol, rather than Standards Track.
> However, it
>    nevertheless seems valuable to have a simple example that shows how
> handover
>    could benefit from using CTP. As an example of how context transfer =
can
> improve the
>    performance of IP layer handover, we consider transferring IPv6 MLD =
state
> [RFC2710].
>    MLD state is a particularly good example because every IPv6 node mus=
t
>   perform two MLD messaging sequences on the wireless link to establish
>    itself as an MLD listener prior to performing router discovery
>    [RFC2461] or duplicate address detection [RFC2462] or before
>    sending/receiving any application-specific traffic (including Mobile
>    IP handover signaling, if any). The node must subscribe to the Soli-
>    cited Node Multicast Address as soon as it comes up on the link. Any
>    application-specific multicast addresses must be re-established as
>    well. Context transfer can significantly speed up re-establishing
>    multicast state by allowing the nAR to initialize MLD for a node tha=
t
>    just completed handover; without any MLD signaling on the new wire-
>    less link. The same approach could be used for transferring multicas=
t
>    context in IPv4.
>=20
> and add the following paragraph after the second paragraph Appendix B i=
n the
> current draft:
>=20
>    This example might seem a bit contrived because MLD isn't used in ty=
pical
>    cellular protocols and wireless local area network protocols typical=
ly
> have
>    enough bandwidth that sending a single MLD message might not be view=
ed
>    as such a performance burden. An example of a wireless protocol wher=
e MLD
>    context transfer might be useful is IEEE 802.15.1 (Bluetooth). IEEE
> 802.15.1 has
>    two IP "profiles": one with and one without PPP. The profile without=
 PPP
> would
>    use MLD. 802.15.1 has a maximum bandwidth of about 800kbps, shared
> between
>    all nodes on the link, so a host on a moderately loaded 802.15.1 acc=
ess
> point could
>    experience the kind of bandwith described in the previous paragraph.=
 In
> addition
>    802.15.1 handover times typically run upwards of a second or more be=
cause
> the
>    host must resynchronize its frequency hopping pattern with the acces=
s
> point, so
>    anything the IP layer could do to to alleviate further delay would b=
e
> beneficial.
>=20
> and removing the following two sentences from the second paragraph in
> Appendix B:
>=20
>   The former is approximate for a narrowband 3G cel-
>    lular links and the latter for a heavily utilized 802.11b WLAN link,
>    both running Voice over IP (VoIP).
>=20
>   Considering most ATM-based 3G voice cellular pro-
>    tocols try to keep total voice handover delay less than 40- 80 msec.=
,
>    MLD signaling could have a large impact on the performance of inter-
>    subnet VoIP handover.
>=20
> Issue 2
> --------
>=20
> Issue: The draft as written specifies using UDP without retransmit for =
the
> transport protocol. This is not acceptable from a congestion control an=
d
> usability standpoint, the points made in Appendix  A about timing
> notwidthstanding. Both Allison and James brought up these issues at var=
ious
> times during the requirements discussion and during previous reviews of=
 the
> draft.
>=20
> The issue with UDP is that CTP is expected to be used frequently betwee=
n
> access routers in a wide area network, like between two hotspot cluster=
s
> connected by T1 or other low capacity lines. Since access networks of t=
hese
> types are just where one might expect congestion to develop, the freque=
ncy
> of packet drops for UDP without retransmit would be expected to be high
> enough to render the protocol unusable in general. While the Working Gr=
oup
> could develop a specialized UDP retransmit algorithm, there is no need =
since
> both TCP and SCTP could provide adequate performance for CTP. Below are=
 two
> suggestions for resolution of the issue, and a preferred resolution.
>=20
> Suggestion 1: Use TCP.
>=20
> The advantage of this suggestion is that TCP is already widely implemen=
ted
> and is well understood, so it could serve for immediate implementation =
and
> experiment. The disadvantage is that TCP provides no way to control the
> retransmit timer in general, so the timeliness of the transfer could no=
t be
> assured without additional measures.
>=20
> Suggestion 2: Use SCTP.
>=20
> The advantage of using SCTP is that it provides a partial reliability m=
ode
> which allows the retransmit timer to be set. This would allow the timel=
iness
> of the transfer to be controlled. The disadvantage is that SCTP is not =
yet
> widely implemented.
>=20
> Preferred Resolution: Suggestion 2.
>=20
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby

--=20
Ghyslain Pelletier, Dipl. Ing.
Wireless IP Optimizations
AWARE - Advanced Wireless Algorithm Research
Ericsson Research, Corporate Unit

Ericsson AB, Laboratoriegr=E4nd 11
Box 920, S-97128 Lule=E5, SWEDEN
Phone : +46 (0) 920 20 24 32=20
Mobile: +46 (0) 706 09 27 73
Ghyslain.Pelletier@ericsson.com
http://www.ericsson.com

I have a new mail address: Ghyslain.Pelletier@ericsson.com
My old e-mail address will function until 2004-06-01.
Please change my address in your personal address book.

This communication is confidential and intended solely for the addressee(=
s). Any unauthorized review, use, disclosure or distribution is prohibite=
d. If you believe this message has been sent to you in error, please noti=
fy the sender by replying to this transmission and delete the message wit=
hout disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interrupt=
ion, unauthorized amendment, tampering and viruses, and we only send and =
receive e-mails on the basis that we are not liable for any such corrupti=
on, interception, amendment, tampering or viruses or any consequences the=
reof.


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



From exim@www1.ietf.org  Tue Mar 23 09:44:54 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29835
	for <rohc-archive@odin.ietf.org>; Tue, 23 Mar 2004 09:44:54 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5n8j-0003hu-Lt
	for rohc-archive@odin.ietf.org; Tue, 23 Mar 2004 09:44:26 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2NEiO3U014244
	for rohc-archive@odin.ietf.org; Tue, 23 Mar 2004 09:44:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5n8g-0003hX-Jf
	for rohc-web-archive@optimus.ietf.org; Tue, 23 Mar 2004 09:44:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29789
	for <rohc-web-archive@ietf.org>; Tue, 23 Mar 2004 09:44:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5n8e-0003oE-00
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 09:44:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5n7d-0003Zk-00
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 09:43:18 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5n6P-0003Lb-00
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 09:42:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5n6P-0003Yu-HR; Tue, 23 Mar 2004 09:42:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5kOA-0003PM-2z
	for rohc@optimus.ietf.org; Tue, 23 Mar 2004 06:48:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20310
	for <rohc@ietf.org>; Tue, 23 Mar 2004 06:48:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5kO6-0003de-00
	for rohc@ietf.org; Tue, 23 Mar 2004 06:48:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5kNA-0003WJ-00
	for rohc@ietf.org; Tue, 23 Mar 2004 06:47:09 -0500
Received: from [194.237.235.30] (helo=effnet.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5kMK-0003K8-00
	for rohc@ietf.org; Tue, 23 Mar 2004 06:46:16 -0500
Received: from krrn (internal.effnet.com [192.168.100.159] (may be forged))
	by effnet.com (8.12.3/8.12.3) with SMTP id i2NAjYU1016725;
	Tue, 23 Mar 2004 11:45:34 +0100
From: "Aniruddha Kulkarni" <aniruddha.kulkarni@effnet.com>
To: <rohc@ietf.org>
Cc: "Tommy Lundemo" <tommy.lundemo@effnet.com>
Date: Tue, 23 Mar 2004 12:45:47 +0100
Message-ID: <KCEJKOOBBMFEDEOJBDHGEEGDCAAA.aniruddha.kulkarni@effnet.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [rohc] Protocol Convergence Layer for header compression negotiation
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

We would like to propose a Protocol Convergence Layer for header compression
negotiation.

The functionality of the layer need not limit to header compression
negotiation
but that is the motivation for proposing such a layer. This layer is not
a link layer like PPP or Ethernet but it is more aligned to the idea of
Packet Data
Convergence Layer (PDCP) from 3GPP specifications.

			|  IP  |
  			--------
			| PCL  |
			--------
			| Link |


Header compression negotiation is the first starting point for using header
compression
functionality. In some cases (unidirectional link, administrator's choice)
it can be
avoided but in most of the cases it is needed. A standardized solution for
such negotiation
process is always preferable over any propritary solutions. This poses the
problem
of updating all link layer standards for different header compression
schemes like IPHC over
PPP (IETF), ROHC over PDCP (3GPP) etc.

Many networks/links can benefit from header compression like 802.11x,
802.16x (already has a
header compression scheme but could also support IETF defined header
compression scheme),
MANET with lot of differnet types of links etc. It would a long and tedious
process to
standardize header compression over all those link layers.

We propose a link layer which takes over the function of header compression
negotiation. This
layer would add no or minimal overhead to the data (compressed or
uncompressed) packets. It
could be extended to provide other functions such as providing frame length,
segmentation (if
not provided by lower links), buffering to handle packet reordering etc. All
these features
are independant of the header compression schemes and all header compression
schemes could
benefit from these features. Ofcourse, all features will be optional and
configurable.

Adoptation of such a layer will enable easy integration of header
compression function in
many different links and networks.

Any comments?


---Aniruddha Kulkarni
Tommy Lundemo



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



From exim@www1.ietf.org  Tue Mar 23 11:23:52 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07790
	for <rohc-archive@odin.ietf.org>; Tue, 23 Mar 2004 11:23:52 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5ogK-0004qA-Mt
	for rohc-archive@odin.ietf.org; Tue, 23 Mar 2004 11:23:24 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2NGNCEk018592
	for rohc-archive@odin.ietf.org; Tue, 23 Mar 2004 11:23:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5ofw-0004pB-6z
	for rohc-web-archive@optimus.ietf.org; Tue, 23 Mar 2004 11:22:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07660
	for <rohc-web-archive@ietf.org>; Tue, 23 Mar 2004 11:22:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5ofo-0003Cl-00
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 11:22:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5oeq-000379-00
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 11:21:41 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5oeF-00030X-00
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 11:21:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5oeE-0004jD-1c; Tue, 23 Mar 2004 11:21:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5odz-0004hB-Ve
	for rohc@optimus.ietf.org; Tue, 23 Mar 2004 11:20:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07447
	for <rohc@ietf.org>; Tue, 23 Mar 2004 11:20:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5odz-0002xy-00
	for rohc@ietf.org; Tue, 23 Mar 2004 11:20:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5ocN-0002bs-00
	for rohc@ietf.org; Tue, 23 Mar 2004 11:19:11 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5oZA-0001wM-00
	for rohc@ietf.org; Tue, 23 Mar 2004 11:15:53 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2NGFkAh025911
	for <rohc@ietf.org>; Tue, 23 Mar 2004 17:15:46 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 23 Mar 2004 17:15:45 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <HQ2WA36F>; Tue, 23 Mar 2004 17:15:45 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E94D9@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'Zongming.Zhou@commit.cn'" <Zongming.Zhou@commit.cn>, rohc@ietf.org
Subject: RE: [rohc] about CSRC List with CC=0
Date: Tue, 23 Mar 2004 13:53:06 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C410D5.A2F0E97C"
X-OriginalArrivalTime: 23 Mar 2004 16:15:45.0849 (UTC) FILETIME=[18DD1A90:01C410F2]
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.8 required=5.0 tests=AWL,DATE_IN_PAST_03_06,
	EXCUSE_16,HTML_20_30,HTML_FONTCOLOR_BLUE,HTML_FONTCOLOR_UNKNOWN,
	HTML_MESSAGE autolearn=no version=2.60

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C410D5.A2F0E97C
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

Please see the ROHC implementers guide:
http://www.ietf.org/internet-drafts/draft-ietf-rohc-rtp-impl-guide-04.txt=
 <http://www.ietf.org/internet-drafts/draft-ietf-rohc-rtp-impl-guide-04.t=
xt>=20
=20
Section 5 discusses list compression issues.
=20
/L-E
=20

-----Original Message-----
From: rohc-admin@ietf.org [mailto:rohc-admin@ietf.org]On Behalf Of Zongmi=
ng.Zhou@commit.cn
Sent: den 23 mars 2004 03:52
To: rohc@ietf.org
Subject: [rohc] about CSRC List with CC=3D0



If CC=3D0, the length of CSRC Generic CSRC list? One Octet? two Octet or =
None at all?=20
One octet=20
     0   1   2   3   4   5   6   7
  +---+---+----+---+---+---+---+---+
  | ET=3D0  |GP=3D0|PS |    CC =3D 0     |
  +---+---+----+---+---+---+---+---+

two octet=20
     0   1   2   3   4   5   6   7
  +---+---+----+---+---+---+---+---+
  | ET=3D0  |GP=3D1|PS |    CC =3D 0     |
  +---+---+----+---+---+---+---+---+
  :            gen_id             :  1 octet, if GP =3D 1
  +---+---+---=3D+---+---+---+---+---+


or None at all (because in RTP dynmaic part CC=3D0 indicates that no CSRC=
 list)=20

Best Regards

Zhou Zongming =D6=DC=D7=DA=C3=F7
=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

COMMIT Incorporated
Add: 18 Shenwang Rd, Xinzhuang Industrial Development Zone, Shanghai Chin=
a
Post Code: 201108
Tel: +86-21-5442-4885 Ext:3405
FAX: +86-21-5442-4886
Email: zongming.zhou@commit.cn
=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

The information contained in this e-mail and any attachments thereto from=
 COMMIT Incorporated is intended to be for the use of the person named ab=
ove and may be private, confidential and privileged. If you are not the i=
ntended recipient of this transmission, you are hereby notified that any =
disclosure, copying, distribution, printing or use of the contents of thi=
s communication is strictly prohibited. If you have received this e-mail =
in error, please notify the sender immediately and permanently delete the=
 original and any copies of this email and any attachments thereto.=20


This communication is confidential and intended solely for the addressee(=
s). Any unauthorized review, use, disclosure or distribution is prohibite=
d. If you believe this message has been sent to you in error, please noti=
fy the sender by replying to this transmission and delete the message wit=
hout disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interrupt=
ion, unauthorized amendment, tampering and viruses, and we only send and =
receive e-mails on the basis that we are not liable for any such corrupti=
on, interception, amendment, tampering or viruses or any consequences the=
reof.


------_=_NextPart_001_01C410D5.A2F0E97C
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dgb2312"=
>


<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D993005212-23032004><FONT face=3DArial color=3D#0000ff =
size=3D2>Please=20
see the ROHC implementers guide:</FONT></SPAN></DIV>
<DIV><SPAN class=3D993005212-23032004><FONT face=3DArial color=3D#0000ff =
size=3D2><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-rohc-rtp-impl-guid=
e-04.txt">http://www.ietf.org/internet-drafts/draft-ietf-rohc-rtp-impl-gu=
ide-04.txt</A></FONT></SPAN></DIV>
<DIV><SPAN class=3D993005212-23032004><FONT face=3DArial color=3D#0000ff=20=

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D993005212-23032004><FONT face=3DArial color=3D#0000ff=20=

size=3D2>Section 5 discusses list compression issues.</FONT></SPAN></DIV>=

<DIV><SPAN class=3D993005212-23032004><FONT face=3DArial color=3D#0000ff=20=

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D993005212-23032004><FONT face=3DArial color=3D#0000ff=20=

size=3D2>/L-E</FONT></SPAN></DIV>
<DIV><SPAN class=3D993005212-23032004></SPAN>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px so=
lid">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT face=3DT=
ahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> rohc-admin@ietf.org=
=20
  [mailto:rohc-admin@ietf.org]<B>On Behalf Of=20
  </B>Zongming.Zhou@commit.cn<BR><B>Sent:</B> den 23 mars 2004=20
  03:52<BR><B>To:</B> rohc@ietf.org<BR><B>Subject:</B> [rohc] about CSRC =
List=20
  with CC=3D0<BR><BR></FONT></DIV><BR><FONT face=3D"Times New Roman" size=
=3D2>If CC=3D0,=20
  the length of CSRC </FONT><FONT face=3D"Times New Roman" color=3Dred=20=

  size=3D2>Generic CSRC list</FONT><FONT face=3D"Times New Roman" size=3D=
2>? One=20
  Octet? two Octet or None at all?</FONT> <BR><FONT face=3D"Times New Rom=
an"=20
  size=3D2>One octet</FONT> <BR><FONT size=3D3><TT>&nbsp; &nbsp; &nbsp;0 =
&nbsp; 1=20
  &nbsp; 2 &nbsp; 3 &nbsp; 4 &nbsp; 5 &nbsp; 6 &nbsp; 7<BR>&nbsp;=20
  +---+---+----+---+---+---+---+---+<BR>&nbsp; | ET=3D0 &nbsp;|GP=3D0|PS =
| &nbsp;=20
  &nbsp;CC =3D 0 &nbsp; &nbsp; |<BR>&nbsp;=20
  +---+---+----+---+---+---+---+---+</TT></FONT><FONT face=3D"Times New R=
oman"=20
  size=3D3><BR></FONT><BR><FONT face=3D"Times New Roman" size=3D2>two oct=
et</FONT>=20
  <BR><FONT size=3D3><TT>&nbsp; &nbsp; &nbsp;0 &nbsp; 1 &nbsp; 2 &nbsp; 3=
 &nbsp; 4=20
  &nbsp; 5 &nbsp; 6 &nbsp; 7<BR>&nbsp;=20
  +---+---+----+---+---+---+---+---+<BR>&nbsp; | ET=3D0 &nbsp;|GP=3D1|PS =
| &nbsp;=20
  &nbsp;CC =3D 0 &nbsp; &nbsp; |<BR>&nbsp;=20
  +---+---+----+---+---+---+---+---+<BR>&nbsp; : &nbsp; &nbsp; &nbsp; &nb=
sp;=20
  &nbsp; &nbsp;gen_id &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : &nbsp;1=
 octet,=20
  if GP =3D 1<BR>&nbsp;=20
  +---+---+---=3D+---+---+---+---+---+<BR></TT></FONT><BR><BR><FONT=20
  face=3D"Times New Roman" size=3D2>or None at all (because in RTP dynmai=
c part CC=3D0=20
  indicates that no CSRC list)</FONT> <BR><BR><FONT face=3Dsans-serif siz=
e=3D2>Best=20
  Regards<BR><BR>Zhou Zongming=20
  =D6=DC=D7=DA=C3=F7<BR>=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=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D<BR>COMMIT=20
  Incorporated<BR>Add: 18 Shenwang Rd, Xinzhuang Industrial Development Z=
one,=20
  Shanghai China<BR>Post Code: 201108<BR>Tel: +86-21-5442-4885 Ext:3405<B=
R>FAX:=20
  +86-21-5442-4886<BR>Email:=20
  zongming.zhou@commit.cn<BR>=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=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>The=20
  information contained in this e-mail and any attachments thereto from C=
OMMIT=20
  Incorporated is intended to be for the use of the person named above an=
d may=20
  be private, confidential and privileged. If you are not the intended re=
cipient=20
  of this transmission, you are hereby notified that any disclosure, copy=
ing,=20
  distribution, printing or use of the contents of this communication is=20=

  strictly prohibited. If you have received this e-mail in error, please =
notify=20
  the sender immediately and permanently delete the original and any copi=
es of=20
  this email and any attachments thereto.</FONT> </BLOCKQUOTE><br>This co=
mmunication is confidential and intended solely for the addressee(s). Any=
 unauthorized review, use, disclosure or distribution is prohibited. If y=
ou believe this message has been sent to you in error, please notify the =
sender by replying to this transmission and delete the message without di=
sclosing it. Thank you.<br><br>E-mail including attachments is susceptibl=
e to data corruption, interruption, unauthorized amendment, tampering and=
 viruses, and we only send and receive e-mails on the basis that we are n=
ot liable for any such corruption, interception, amendment, tampering or =
viruses or any consequences thereof.<br></BODY></HTML>

------_=_NextPart_001_01C410D5.A2F0E97C--

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



From exim@www1.ietf.org  Tue Mar 23 11:49:12 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09636
	for <rohc-archive@odin.ietf.org>; Tue, 23 Mar 2004 11:49:11 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5p4r-0007xF-25
	for rohc-archive@odin.ietf.org; Tue, 23 Mar 2004 11:48:43 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2NGmXUE030577
	for rohc-archive@odin.ietf.org; Tue, 23 Mar 2004 11:48:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5p4q-0007x6-Qo
	for rohc-web-archive@optimus.ietf.org; Tue, 23 Mar 2004 11:48:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09574
	for <rohc-web-archive@ietf.org>; Tue, 23 Mar 2004 11:48:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5p4p-0005bN-00
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 11:48:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5p28-0005BZ-00
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 11:45:45 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5p0m-000517-01
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 11:44:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5oxu-0006VJ-Ho; Tue, 23 Mar 2004 11:41:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5owt-0006TC-KQ
	for rohc@optimus.ietf.org; Tue, 23 Mar 2004 11:40:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08989
	for <rohc@ietf.org>; Tue, 23 Mar 2004 11:40:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5owr-0004hz-00
	for rohc@ietf.org; Tue, 23 Mar 2004 11:40:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5ovt-0004fh-00
	for rohc@ietf.org; Tue, 23 Mar 2004 11:39:19 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5ouv-0004dK-00
	for rohc@ietf.org; Tue, 23 Mar 2004 11:38:18 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2NGc1YG004184
	for <rohc@ietf.org>; Tue, 23 Mar 2004 17:38:01 +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.0);
	 Tue, 23 Mar 2004 17:36:18 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <HQ2WAY7Q>; Tue, 23 Mar 2004 17:36:18 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E94DF@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'Zongming.Zhou@commit.cn'" <Zongming.Zhou@commit.cn>, rohc@ietf.org
Subject: RE: [rohc] Question of ROHC
Date: Tue, 23 Mar 2004 15:36:11 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C410E4.2F4F79AE"
X-OriginalArrivalTime: 23 Mar 2004 16:36:18.0542 (UTC) FILETIME=[F79B20E0:01C410F4]
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,HTML_40_50,
	HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C410E4.2F4F79AE
Content-Type: text/plain;
	charset="gb2312"

I've tried to answer below, let me know if I have misunderstood your questions.
 
/L-E

-----Original Message-----
From: rohc-admin@ietf.org [mailto:rohc-admin@ietf.org]On Behalf Of Zongming.Zhou@commit.cn
Sent: den 18 mars 2004 03:06
To: rohc@ietf.org
Subject: [rohc] Question of ROHC




If for this case: 
  +-------------------------------+ 
  |              RTP              | 
  +-------------------------------+ 
  |              UTP              | 
  +-------------------------------+ 
  |              AH               | 
  +-------------------------------+ 
  |           Inner IP            | 
  +-------------------------------+ 
  |              AH               | 
  +-------------------------------+ 
  |           Outer IP            | 
  +-------------------------------+ 
The format of IR packet? 
    0   1   2   3   4   5   6   7 
   --- --- --- --- --- --- --- --- 
  |         Add-CID octet         |  if for small CIDs and CID != 0 
  +---+---+---+---+---+---+---+---+ 
  | 1   1   1   1   1   1   0 | D | 
  +---+---+---+---+---+---+---+---+ 
  |                               | 
  /    0-2 octets of CID info     /  1-2 octets if for large CIDs 
  |                               | 
  +---+---+---+---+---+---+---+---+ 
  |            Profile            |  1 octet 
  +---+---+---+---+---+---+---+---+ 
  |              CRC              |  1 octet 
  +---+---+---+---+---+---+---+---+ 
  |    Outer IP static part???    | 
  |    Inner IP static part???    |static chain 
  |        UDP static part        | 
  |        RTP static part        |variable length 
   +---+---+---+---+---+---+---+---+ 
  |                               | 
  |         Dynamic chain         |  present if D = 1, variable length 
  |                               | 
   - - - - - - - - - - - - - - - - 
  |                               | 
  |           Payload             |  variable length 
  |                               | 
   - - - - - - - - - - - - - - - - 
[LEJ] Yes, looks ok!
  
Generic extension header list 
  +---+---+---+---+---+---+---+---+ 
  | / Generic extension header /  | varial length 
  | /  list of outer IP (AH)   /  |   
  +---+---+---+---+---+---+---+---+ 
  | / Generic extension header /  | varial length 
  | /  list of inner IP (AH)   /  |   
  +---+---+---+---+---+---+---+---+ 
Is it right? 
1. Is there only outer IP static part exists in IR packet? 
[LEJ] No! The profiles in 3095 can handle one outer and one inner IP header.
These base headers are compressed and fields sent in static/dynamic chains.
For each IP header, there are potentially an extension header list (each IP
header is thus handled separately).
 
2. If yes, does outer IP static part precede inner IP static part or else? 
And does Generic extension header list of outer IP precede Generic extension 
header list of inner IP? 
3. If no, how to explain the following 2 sentence in RFC3095? 
  1)  In firs paragraph of Chapter 5.8.5/RFC3095, there is one sentence: 
      When there is more than one IP header, there is more than one list of 
      extension headers. 
  2)  In Chapter 5.8/RFC3095, there is another sentence: 
      IPv6 base headers and IPv4 headers cannot be part of an extension 
      header chain.
[LEJ] I can not see why these two does not make sense (the first text is
taken from section 5.8.4). One can summarize these two statements with:
"Base headers are compressed, can thus not be part of an extension header
list. For each base header, there is  potentially a list of extension headers.
 


This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


------_=_NextPart_001_01C410E4.2F4F79AE
Content-Type: text/html;
	charset="gb2312"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=gb2312">


<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=495522414-23032004><FONT face=Arial color=#0000ff size=2>I've 
tried to answer below, let me know if I have misunderstood your 
questions.</FONT></SPAN></DIV>
<DIV><SPAN class=495522414-23032004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=495522414-23032004><FONT face=Arial color=#0000ff 
size=2>/L-E</FONT></SPAN></DIV>
<BLOCKQUOTE 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> rohc-admin@ietf.org 
  [mailto:rohc-admin@ietf.org]<B>On Behalf Of 
  </B>Zongming.Zhou@commit.cn<BR><B>Sent:</B> den 18 mars 2004 
  03:06<BR><B>To:</B> rohc@ietf.org<BR><B>Subject:</B> [rohc] Question of 
  ROHC<BR><BR></FONT></DIV>
  <DIV><BR><FONT face=sans-serif size=2><BR>If for this case:</FONT><FONT 
  face=sans-serif size=3> </FONT><FONT face=sans-serif size=2><BR>&nbsp; 
  +-------------------------------+</FONT><FONT face=sans-serif size=3> 
  </FONT><FONT face=sans-serif size=2><BR>&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp;RTP &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| 
  <BR>&nbsp; +-------------------------------+</FONT><FONT face=sans-serif 
  size=3> </FONT><FONT face=sans-serif size=2><BR>&nbsp; | &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp;UTP &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp;| <BR>&nbsp; +-------------------------------+ <BR>&nbsp; | &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;AH &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; | <BR>&nbsp; +-------------------------------+</FONT><FONT 
  face=sans-serif size=3> </FONT><FONT face=sans-serif size=2><BR>&nbsp; | 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Inner IP &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp;| <BR>&nbsp; +-------------------------------+</FONT><FONT 
  face=sans-serif size=3> </FONT><FONT face=sans-serif size=2><BR>&nbsp; | 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;AH &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; | <BR>&nbsp; 
  +-------------------------------+</FONT><FONT face=sans-serif size=3> 
  </FONT><FONT face=sans-serif size=2><BR>&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; Outer IP &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| <BR>&nbsp; 
  +-------------------------------+ <BR>The format of IR packet?</FONT><FONT 
  face=sans-serif size=3> </FONT><FONT face=sans-serif size=2><BR>&nbsp; &nbsp; 
  0 &nbsp; 1 &nbsp; 2 &nbsp; 3 &nbsp; 4 &nbsp; 5 &nbsp; 6 &nbsp; 7</FONT><FONT 
  face=sans-serif size=3> </FONT><FONT face=sans-serif size=2><BR>&nbsp; 
  &nbsp;--- --- --- --- --- --- --- ---</FONT><FONT face=sans-serif size=3> 
  </FONT><FONT face=sans-serif size=2><BR>&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; 
  Add-CID octet &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;if for small CIDs and CID != 
  0</FONT><FONT face=sans-serif size=3> </FONT><FONT face=sans-serif 
  size=2><BR>&nbsp; +---+---+---+---+---+---+---+---+</FONT><FONT 
  face=sans-serif size=3> </FONT><FONT face=sans-serif size=2><BR>&nbsp; | 1 
  &nbsp; 1 &nbsp; 1 &nbsp; 1 &nbsp; 1 &nbsp; 1 &nbsp; 0 | D |</FONT><FONT 
  face=sans-serif size=3> </FONT><FONT face=sans-serif size=2><BR>&nbsp; 
  +---+---+---+---+---+---+---+---+</FONT><FONT face=sans-serif size=3> 
  </FONT><FONT face=sans-serif size=2><BR>&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  |</FONT><FONT face=sans-serif size=3> </FONT><FONT face=sans-serif 
  size=2><BR>&nbsp; / &nbsp; &nbsp;0-2 octets of CID info &nbsp; &nbsp; / 
  &nbsp;1-2 octets if for large CIDs</FONT><FONT face=sans-serif size=3> 
  </FONT><FONT face=sans-serif size=2><BR>&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  |</FONT><FONT face=sans-serif size=3> </FONT><FONT face=sans-serif 
  size=2><BR>&nbsp; +---+---+---+---+---+---+---+---+</FONT><FONT 
  face=sans-serif size=3> </FONT><FONT face=sans-serif size=2><BR>&nbsp; | 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Profile &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp;| &nbsp;1 octet</FONT><FONT face=sans-serif size=3> </FONT><FONT 
  face=sans-serif size=2><BR>&nbsp; 
  +---+---+---+---+---+---+---+---+</FONT><FONT face=sans-serif size=3> 
  </FONT><FONT face=sans-serif size=2><BR>&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp;CRC &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| 
  &nbsp;1 octet</FONT><FONT face=sans-serif size=3> </FONT><FONT face=sans-serif 
  size=2><BR>&nbsp; +---+---+---+---+---+---+---+---+</FONT><FONT 
  face=sans-serif size=3> </FONT><FONT face=sans-serif size=2><BR>&nbsp; | 
  &nbsp; &nbsp;Outer IP static part??? &nbsp; &nbsp;|</FONT><FONT 
  face=sans-serif size=3> </FONT><FONT face=sans-serif size=2><BR>&nbsp; | 
  &nbsp; &nbsp;Inner IP static part??? &nbsp; &nbsp;|static chain</FONT><FONT 
  face=sans-serif size=3> </FONT><FONT face=sans-serif size=2><BR>&nbsp; | 
  &nbsp; &nbsp; &nbsp; &nbsp;UDP static part &nbsp; &nbsp; &nbsp; 
  &nbsp;|</FONT><FONT face=sans-serif size=3> </FONT><FONT face=sans-serif 
  size=2><BR>&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;RTP static part &nbsp; &nbsp; 
  &nbsp; &nbsp;|variable length</FONT><FONT face=sans-serif size=3> 
  </FONT><BR><FONT face=sans-serif size=2>&nbsp; 
  &nbsp;+---+---+---+---+---+---+---+---+</FONT><FONT face=sans-serif size=3> 
  </FONT><FONT face=sans-serif size=2><BR>&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  |</FONT><FONT face=sans-serif size=3> </FONT><FONT face=sans-serif 
  size=2><BR>&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; Dynamic chain &nbsp; &nbsp; 
  &nbsp; &nbsp; | &nbsp;present if D = 1, variable length</FONT><FONT 
  face=sans-serif size=3> </FONT><FONT face=sans-serif size=2><BR>&nbsp; | 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; |</FONT><FONT face=sans-serif size=3> </FONT><FONT 
  face=sans-serif size=2><BR>&nbsp; &nbsp;- - - - - - - - - - - - - - - 
  -</FONT><FONT face=sans-serif size=3> </FONT><FONT face=sans-serif 
  size=2><BR>&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</FONT><FONT face=sans-serif 
  size=3> </FONT><FONT face=sans-serif size=2><BR>&nbsp; | &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; Payload &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | 
  &nbsp;variable length</FONT><FONT face=sans-serif size=3> </FONT><FONT 
  face=sans-serif size=2><BR>&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</FONT><FONT 
  face=sans-serif size=3> </FONT><FONT face=sans-serif size=2><BR>&nbsp; &nbsp;- 
  - - - - - - - - - - - - - - -</FONT><FONT face=sans-serif 
  size=3>&nbsp;<BR><SPAN class=495522414-23032004><FONT face=Arial color=#0000ff 
  size=2>[LEJ]&nbsp;Yes, looks ok!</FONT></SPAN></FONT></DIV>
  <DIV><FONT face=sans-serif size=3><SPAN 
  class=495522414-23032004>&nbsp;</SPAN></FONT><FONT face=sans-serif><FONT 
  size=2><SPAN class=495522414-23032004>&nbsp;</SPAN><BR>Generic extension 
  header list</FONT></FONT><FONT face=sans-serif size=3> </FONT><FONT 
  face=sans-serif size=2><BR>&nbsp; 
  +---+---+---+---+---+---+---+---+</FONT><FONT face=sans-serif size=3> 
  </FONT><FONT face=sans-serif size=2><BR>&nbsp; | / Generic extension header / 
  &nbsp;| varial length</FONT><FONT face=sans-serif size=3> </FONT><FONT 
  face=sans-serif size=2><BR>&nbsp; | / &nbsp;list of outer IP (AH) &nbsp; / 
  &nbsp;| &nbsp;</FONT><FONT face=sans-serif size=3> </FONT><FONT 
  face=sans-serif size=2><BR>&nbsp; 
  +---+---+---+---+---+---+---+---+</FONT><FONT face=sans-serif size=3> 
  </FONT><FONT face=sans-serif size=2><BR>&nbsp; | / Generic extension header / 
  &nbsp;| varial length</FONT><FONT face=sans-serif size=3> </FONT><FONT 
  face=sans-serif size=2><BR>&nbsp; | / &nbsp;list of inner IP (AH) &nbsp; / 
  &nbsp;| &nbsp;</FONT><FONT face=sans-serif size=3> </FONT><FONT 
  face=sans-serif size=2><BR>&nbsp; 
  +---+---+---+---+---+---+---+---+</FONT><FONT face=sans-serif size=3> 
  </FONT><FONT face=sans-serif size=2><BR>Is it right?</FONT><FONT 
  face=sans-serif size=3> </FONT><FONT face=sans-serif size=2><BR>1. Is there 
  only outer IP static part exists in IR packet?</FONT><FONT face=sans-serif 
  size=3> <BR><SPAN class=495522414-23032004><FONT face=Arial color=#0000ff 
  size=2>[LEJ]&nbsp;No! The profiles in 3095 can handle one outer and one inner 
  IP header.</FONT></SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=495522414-23032004>These base headers are compressed and fields sent in 
  static/dynamic chains.</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN class=495522414-23032004>For 
  each IP header, there are potentially an extension header list (each 
  IP</SPAN></FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2><SPAN 
  class=495522414-23032004>header is thus handled 
  separately).</SPAN></FONT></DIV>
  <DIV><FONT face=sans-serif size=3><SPAN 
  class=495522414-23032004>&nbsp;</SPAN></FONT><FONT face=sans-serif><BR><FONT 
  size=2>2. If yes, does outer IP static part precede inner IP static part or 
  else?</FONT></FONT><FONT face=sans-serif size=3> </FONT><FONT face=sans-serif 
  size=2><BR>And does Generic extension header list of outer IP precede Generic 
  extension <BR>header list of inner IP?</FONT><FONT face=sans-serif size=3> 
  </FONT><FONT face=sans-serif size=2><BR>3. If no, how to explain the following 
  2 sentence in RFC3095?</FONT><FONT face=sans-serif size=3> </FONT><FONT 
  face=sans-serif size=2><BR>&nbsp; 1) &nbsp;In firs paragraph of Chapter 
  5.8.5/RFC3095, there is one sentence:</FONT><FONT face=sans-serif size=3> 
  </FONT><FONT face=sans-serif size=2><BR>&nbsp; &nbsp; &nbsp; When there is 
  more than one IP header, there is more than one list of <BR>&nbsp; &nbsp; 
  &nbsp; extension headers.</FONT><FONT face=sans-serif size=3> </FONT><FONT 
  face=sans-serif><BR><FONT size=2>&nbsp; 2) &nbsp;In Chapter 5.8/RFC3095, there 
  is another sentence: <BR>&nbsp; &nbsp; &nbsp; IPv6 base headers and IPv4 
  headers cannot be part of an extension <BR>&nbsp; &nbsp; &nbsp; header 
  chain.<BR><SPAN class=495522414-23032004><FONT face=Arial 
  color=#0000ff>[LEJ]&nbsp;I can not see&nbsp;why these two does not make sense 
  (the first text is</FONT></SPAN></FONT></FONT></DIV>
  <DIV><FONT><FONT face=Arial color=#0000ff size=2><SPAN 
  class=495522414-23032004>taken from section 5.8.4). One can summarize these 
  two statements with:</SPAN></FONT></FONT></DIV>
  <DIV><FONT face=sans-serif size=3><SPAN class=495522414-23032004><FONT 
  face=Arial color=#0000ff size=2>"Base headers are compressed, can thus not be 
  part of an extension header</FONT></SPAN></FONT></DIV>
  <DIV><FONT face=sans-serif size=3><SPAN class=495522414-23032004><FONT 
  face=Arial color=#0000ff size=2>list. For each base header, there is&nbsp; 
  potentially a list of extension headers.</FONT></SPAN></FONT></DIV>
  <DIV><FONT face=sans-serif size=3><SPAN 
  class=495522414-23032004></SPAN></FONT>&nbsp;</DIV></BLOCKQUOTE><br>This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.<br><br>E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.<br></BODY></HTML>

------_=_NextPart_001_01C410E4.2F4F79AE--

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



From exim@www1.ietf.org  Tue Mar 23 11:49:34 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09670
	for <rohc-archive@odin.ietf.org>; Tue, 23 Mar 2004 11:49:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5p5E-00080A-GA
	for rohc-archive@odin.ietf.org; Tue, 23 Mar 2004 11:49:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2NGmucM030752
	for rohc-archive@odin.ietf.org; Tue, 23 Mar 2004 11:48:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5p5E-0007zv-Cr
	for rohc-web-archive@optimus.ietf.org; Tue, 23 Mar 2004 11:48:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09615
	for <rohc-web-archive@ietf.org>; Tue, 23 Mar 2004 11:48:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5p5D-0005el-00
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 11:48:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5p2G-0005D2-00
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 11:45:53 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5p0n-000517-00
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 11:44:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5olx-0005N8-Ng; Tue, 23 Mar 2004 11:29:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5oli-0005Kw-HD
	for rohc@optimus.ietf.org; Tue, 23 Mar 2004 11:28:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08409
	for <rohc@ietf.org>; Tue, 23 Mar 2004 11:28:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5olh-00048x-00
	for rohc@ietf.org; Tue, 23 Mar 2004 11:28:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5okO-0003r4-00
	for rohc@ietf.org; Tue, 23 Mar 2004 11:27:27 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5ohp-0003U1-00
	for rohc@ietf.org; Tue, 23 Mar 2004 11:24:46 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2NGOhAh029288
	for <rohc@ietf.org>; Tue, 23 Mar 2004 17:24:43 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 23 Mar 2004 17:24:43 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <HQ2WASAL>; Tue, 23 Mar 2004 17:24:43 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E94DE@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'Zongming.Zhou@commit.cn'" <Zongming.Zhou@commit.cn>, rohc@ietf.org
Subject: RE: [rohc] MUST FEEDBACK-2 be used if LARGE CID is configured?
Date: Tue, 23 Mar 2004 15:11:30 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="gb2312"
X-OriginalArrivalTime: 23 Mar 2004 16:24:43.0090 (UTC) FILETIME=[59159320:01C410F3]
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

Hi,

I think you have misread RFC3095 here, the text can be confusing.
There is no requirement that FEEDBACK-2 must be used for LARGE_CID.
The 5.2.2. text you refer to might have caused this confusion by
its 1),2),3),4) structure, which could had been 1),2a),2b),2c)
instead. 4) does not refer to LARGE_CID, but to SMALL_CID without
an Add-CID octet (i.e. no CID).

BR
/Lars-Erik


> -----Original Message-----
> From: rohc-admin@ietf.org [mailto:rohc-admin@ietf.org]On Behalf Of Zongming.Zhou@commit.cn
> Sent: den 23 mars 2004 07:22
> To: rohc@ietf.org
> Subject: [rohc] MUST FEEDBACK-2 be used if LARGE CID is configured?
>
>
>
> If  FEEDBACK-2 MUST be used if LARGE CID is configured, description
> in the last of Chater 5.2.2/RFC3095 should be modified order to give
> a detailed and clearly descrition. 
>
> Original copy of Chapter 5.2.2, RFC3095 
> The compressor can use the following logic to parse the feedback field. 
> 1) If for large CIDs, the feedback will always start with a CID encoded according to 
>    section 4.5.6. If the first bit is 0, the CID uses one octet. If the first bit is 
>    1, the CID uses two octets. 
> 2) If for small CIDs, and the size is one octet, the feedback is a FEEDBACK-1. 
> 3) If for small CIDs, and the size is larger than one octet, and the feedback starts 
>    with the two bits 11, the feedback starts with an Add-CID octet. If the size is 2, 
>    it is followed by FEEDBACK-1. If the size is larger than 2, the Add-CID is followed 
>    by FEEDBACK-2. 
> 4) Otherwise, there is no Add-CID octet, and the feedback starts with a FEEDBACK-2. 
>
> Modification to Chapter 5.2.2/RFC3095 
> For Large CID 
>      the feedback will always start with a CID encoded according to section 4.5.6. If 
>   the first bit is 0, the CID uses one octet. If the first bit is 1, the CID uses 
>   two octets. And FEEDBACK-2 must be used. 
>
> For small CID: 
>   1) If the size is one octet, the feedback is a FEEDBACK-1. 
>   2) If the size is larger than one octet, and the feedback starts with the two bits 11, 
>      the feedback starts with an Add-CID octet.If the size is 2,it is followed by 
>      FEEDBACK-1. If the size is larger than 2, the Add-CID is followed by FEEDBACK-2. 
>   3) Otherwise, there is no Add-CID octet, and the feedback starts with a FEEDBACK-2. 


This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Tue Mar 23 20:53:23 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18639
	for <rohc-archive@odin.ietf.org>; Tue, 23 Mar 2004 20:53:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5xZU-0007O7-2g
	for rohc-archive@odin.ietf.org; Tue, 23 Mar 2004 20:52:55 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2O1qivp028395
	for rohc-archive@odin.ietf.org; Tue, 23 Mar 2004 20:52:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5xZT-0007Nu-Te
	for rohc-web-archive@optimus.ietf.org; Tue, 23 Mar 2004 20:52:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18620
	for <rohc-web-archive@ietf.org>; Tue, 23 Mar 2004 20:52:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5xZR-00063T-00
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 20:52:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5xYb-0005zF-00
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 20:51:49 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5xXq-0005uc-00
	for rohc-web-archive@ietf.org; Tue, 23 Mar 2004 20:51:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5xXp-0007Gt-Si; Tue, 23 Mar 2004 20:51:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5xTa-000732-Ra
	for rohc@optimus.ietf.org; Tue, 23 Mar 2004 20:46:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18288
	for <rohc@ietf.org>; Tue, 23 Mar 2004 20:46:36 -0500 (EST)
From: Zongming.Zhou@commit.cn
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5xTY-0005Xl-00
	for rohc@ietf.org; Tue, 23 Mar 2004 20:46:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5xSZ-0005Sm-00
	for rohc@ietf.org; Tue, 23 Mar 2004 20:45:36 -0500
Received: from [211.152.58.77] (helo=DIOSCURI.COMMIT)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5xQo-0005Dl-00
	for rohc@ietf.org; Tue, 23 Mar 2004 20:43:46 -0500
To: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
Cc: rohc@ietf.org
Subject: RE: [rohc] Question of ROHC
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.11   July 24, 2002
Message-ID: <OFC3017A1B.CF937544-ON48256E61.0007F5A6-48256E61.000980AE@COMMIT>
Date: Wed, 24 Mar 2004 09:43:21 +0800
X-MIMETrack: Serialize by Router on penelope/commit(Release 5.0.11  |July 24, 2002) at
 2004/03/24 09:44:04 AM,
	Serialize complete at 2004/03/24 09:44:04 AM
Content-Type: multipart/alternative; boundary="=_alternative 000980AB48256E61_="
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.6 required=5.0 tests=AWL,EXCUSE_16,MIME_BASE64_TEXT,
	NO_REAL_NAME autolearn=no version=2.60

This is a multipart message in MIME format.
--=_alternative 000980AB48256E61_=
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

SGksTC1FDQoNClRoYW5rcyBmb3IgeW91ciBhbnN3ZXIhIEkgYWdyZWUgd2l0aCB1IQ0KDQpJIHRo
aW5rIGluIGltcGxlbWVudGVyIGd1aWRlLCBpdCBzaG91bGQgYmUgbWFkZSBjbGVhcmx5IHRoYXQg
d2hldGhlciBPdXRlciBJUCBzdGF0aWMgcGFydCBwcmVjZWVkcyBJbm5lciBJUCBzdGF0aWMgcGFy
dCBvciBub3QgaWYgaW5uZXIgSVAgZXhpc3RzDQoNCg0KT3V0ZXIgSVAvQUgvSW5uZXIgSVAvQUgv
RVNQL1VEUC9SVFANCg0KQWNjb3JkaW5nIHRvIGV4dGVuc2lvbiAzLCBJbm5lciBJUCBwcmVjZWVk
cyBPdXRlciBJUCwgc28gSSB0aGluayBpbiBJUiANCnBhY2tldHMgbWF5YmUgdGhlIGZvbGxvd2lu
ZyBmb3JtYXQoIElubmVyIElQIHByZWNlZWRzIE91dGVyIElQKSBpcyBiZXR0ZXI6DQogICstLS0r
LS0tKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKyANCiAgfCAgICBJbm5lciBJUCBzdGF0aWMgcGFy
dD8/PyAgICB8IA0KICB8ICAgIE91dGVyIElQIHN0YXRpYyBwYXJ0Pz8/ICAgIHxzdGF0aWMgY2hh
aW4gDQogIHwgICAgICAgIFVEUCBzdGF0aWMgcGFydCAgICAgICAgfCANCiAgfCAgICAgICAgUlRQ
IHN0YXRpYyBwYXJ0ICAgICAgICB8dmFyaWFibGUgbGVuZ3RoIA0KICArLS0tKy0tLSstLS0rLS0t
Ky0tLSstLS0rLS0tKy0tLSsgDQogIHwgICAgICBJbm5lciBJUCBkeW4gcGFydD8/PyAgICAgfCAN
CiAgfCAgICAgIE91dGVyIElQIGR5biBwYXJ0Pz8/ICAgICB8c3RhdGljIGNoYWluIA0KICB8ICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgDQogICstLS0rLS0tKy0tLSstLS0rLS0tKy0t
LSstLS0rLS0tKyANCg0KDQpPdXRlciBJUCBzdGF0aWMgcGFydCBwcmVjZWVkcyBJbm50ZXIgSVAN
Cg0KICAgRXh0ZW5zaW9uIDM6DQoNCiAgICAgIDAgICAgIDEgICAgIDIgICAgIDMgICAgIDQgICAg
IDUgICAgIDYgICAgIDcNCiAgICstLS0tLSstLS0tLSstLS0tLSstLS0tLSstLS0tLSstLS0tLSst
LS0tLSstLS0tLSsNCiAgIHwgIDEgICAgIDEgIHwgIFMgIHxSLVRTIHwgVHNjIHwgIEkgIHwgaXAg
IHwgcnRwIHwgICAgICAgICAgICAoRkxBR1MpDQogICArLS0tLS0rLS0tLS0rLS0tLS0rLS0tLS0r
LS0tLS0rLS0tLS0rLS0tLS0rLS0tLS0rDQogICB8ICAgICAgICAgICAgSW5uZXIgSVAgaGVhZGVy
IGZsYWdzICAgICAgICB8IGlwMiB8ICBpZiBpcCA9IDENCiAgICAuLi4uLiAuLi4uLiAuLi4uLiAu
Li4uLiAuLi4uLiAuLi4uLiAuLi4uLiAuLi4uLg0KICAgfCAgICAgICAgICAgIE91dGVyIElQIGhl
YWRlciBmbGFncyAgICAgICAgICAgICAgfCAgaWYgaXAyID0gMQ0KICAgIC4uLi4uIC4uLi4uIC4u
Li4uIC4uLi4uIC4uLi4uIC4uLi4uIC4uLi4uIC4uLi4uDQogICB8ICAgICAgICAgICAgICAgICAg
ICAgIFNOICAgICAgICAgICAgICAgICAgICAgICB8ICBpZiBTID0gMQ0KICAgIC4uLi4uIC4uLi4u
IC4uLi4uIC4uLi4uIC4uLi4uIC4uLi4uIC4uLi4uIC4uLi4uDQogICAvICAgICAgIFRTIChlbmNv
ZGVkIGFzIGluIHNlY3Rpb24gNC41LjYpICAgICAgICAvICAxLTQgb2N0ZXRzLA0KICAgIC4uLi4u
IC4uLi4uIC4uLi4uIC4uLi4uIC4uLi4uIC4uLi4uIC4uLi4uIC4uLi4uICAgaWYgUi1UUyA9IDEN
CiAgIHwgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwNCiAg
IC8gICAgICAgICAgICBJbm5lciBJUCBoZWFkZXIgZmllbGRzICAgICAgICAgICAgIC8gIHZhcmlh
YmxlLA0KICAgfCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
fCAgaWYgaXAgPSAxDQogICAgLi4uLi4gLi4uLi4gLi4uLi4gLi4uLi4gLi4uLi4gLi4uLi4gLi4u
Li4gLi4uLi4NCiAgIHwgICAgICAgICAgICAgICAgICAgICBJUC1JRCAgICAgICAgICAgICAgICAg
ICAgIHwgIDIgb2N0ZXRzLCBpZiBJID0gMQ0KICAgIC4uLi4uIC4uLi4uIC4uLi4uIC4uLi4uIC4u
Li4uIC4uLi4uIC4uLi4uIC4uLi4uDQogICB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICB8DQogICAvICAgICAgICAgICAgT3V0ZXIgSVAgaGVhZGVyIGZpZWxk
cyAgICAgICAgICAgICAvICB2YXJpYWJsZSwNCiAgIHwgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIHwgIGlmIGlwMiA9IDENCiAgICAuLi4uLiAuLi4uLiAuLi4u
LiAuLi4uLiAuLi4uLiAuLi4uLiAuLi4uLiAuLi4uLg0KICAgfCAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgfA0KICAgLyAgICAgICAgICBSVFAgaGVhZGVyIGZs
YWdzIGFuZCBmaWVsZHMgICAgICAgICAgLyAgdmFyaWFibGUsDQogICB8ICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8ICBpZiBydHAgPSAxDQogICAgLi4uLi4g
Li4uLi4gLi4uLi4gLi4uLi4gLi4uLi4gLi4uLi4gLi4uLi4gLi4uLi4NCg0KDQoNCkJlc3QgUmVn
YXJkcw0KIA0KWmhvdSBab25nbWluZyDW3Nfaw/cNCj09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0KQ09NTUlU
IEluY29ycG9yYXRlZA0KQWRkOiAxOCBTaGVud2FuZyBSZCwgWGluemh1YW5nIEluZHVzdHJpYWwg
RGV2ZWxvcG1lbnQgWm9uZSwgU2hhbmdoYWkgQ2hpbmENClBvc3QgQ29kZTogMjAxMTA4DQpUZWw6
ICs4Ni0yMS01NDQyLTQ4ODUgRXh0OjM0MDUNCkZBWDogKzg2LTIxLTU0NDItNDg4Ng0KRW1haWw6
IHpvbmdtaW5nLnpob3VAY29tbWl0LmNuDQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0NClRoZSBpbmZvcm1h
dGlvbiBjb250YWluZWQgaW4gdGhpcyBlLW1haWwgYW5kIGFueSBhdHRhY2htZW50cyB0aGVyZXRv
IGZyb20gDQpDT01NSVQgSW5jb3Jwb3JhdGVkIGlzIGludGVuZGVkIHRvIGJlIGZvciB0aGUgdXNl
IG9mIHRoZSBwZXJzb24gbmFtZWQgDQphYm92ZSBhbmQgbWF5IGJlIHByaXZhdGUsIGNvbmZpZGVu
dGlhbCBhbmQgcHJpdmlsZWdlZC4gSWYgeW91IGFyZSBub3QgdGhlIA0KaW50ZW5kZWQgcmVjaXBp
ZW50IG9mIHRoaXMgdHJhbnNtaXNzaW9uLCB5b3UgYXJlIGhlcmVieSBub3RpZmllZCB0aGF0IGFu
eSANCmRpc2Nsb3N1cmUsIGNvcHlpbmcsIGRpc3RyaWJ1dGlvbiwgcHJpbnRpbmcgb3IgdXNlIG9m
IHRoZSBjb250ZW50cyBvZiB0aGlzIA0KY29tbXVuaWNhdGlvbiBpcyBzdHJpY3RseSBwcm9oaWJp
dGVkLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGUtbWFpbCBpbiANCmVycm9yLCBwbGVhc2Ug
bm90aWZ5IHRoZSBzZW5kZXIgaW1tZWRpYXRlbHkgYW5kIHBlcm1hbmVudGx5IGRlbGV0ZSB0aGUg
DQpvcmlnaW5hbCBhbmQgYW55IGNvcGllcyBvZiB0aGlzIGVtYWlsIGFuZCBhbnkgYXR0YWNobWVu
dHMgdGhlcmV0by4NCg0KDQoNCg0KIkxhcnMtRXJpayBKb25zc29uIChMVS9FQUIpIiA8bGFycy1l
cmlrLmpvbnNzb25AZXJpY3Nzb24uY29tPg0KMjAwNC0wMy0yMyAyMjozNg0KDQogDQogICAgICAg
IFRvOiAgICAgIidab25nbWluZy5aaG91QGNvbW1pdC5jbiciIDxab25nbWluZy5aaG91QGNvbW1p
dC5jbj4sIHJvaGNAaWV0Zi5vcmcNCiAgICAgICAgY2M6IA0KICAgICAgICBTdWJqZWN0OiAgICAg
ICAgUkU6IFtyb2hjXSBRdWVzdGlvbiBvZiBST0hDDQoNCg0KSSd2ZSB0cmllZCB0byBhbnN3ZXIg
YmVsb3csIGxldCBtZSBrbm93IGlmIEkgaGF2ZSBtaXN1bmRlcnN0b29kIHlvdXIgDQpxdWVzdGlv
bnMuDQogDQovTC1FDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogcm9oYy1hZG1p
bkBpZXRmLm9yZyBbbWFpbHRvOnJvaGMtYWRtaW5AaWV0Zi5vcmddT24gQmVoYWxmIE9mIFpvbmdt
aW5nLlpob3VAY29tbWl0LmNuDQpTZW50OiBkZW4gMTggbWFycyAyMDA0IDAzOjA2DQpUbzogcm9o
Y0BpZXRmLm9yZw0KU3ViamVjdDogW3JvaGNdIFF1ZXN0aW9uIG9mIFJPSEMNCg0KDQoNCklmIGZv
ciB0aGlzIGNhc2U6IA0KICArLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSsgDQogIHwg
ICAgICAgICAgICAgIFJUUCAgICAgICAgICAgICAgfCANCiAgKy0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0rIA0KICB8ICAgICAgICAgICAgICBVVFAgICAgICAgICAgICAgIHwgDQogICst
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKyANCiAgfCAgICAgICAgICAgICAgQUggICAg
ICAgICAgICAgICB8IA0KICArLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSsgDQogIHwg
ICAgICAgICAgIElubmVyIElQICAgICAgICAgICAgfCANCiAgKy0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0rIA0KICB8ICAgICAgICAgICAgICBBSCAgICAgICAgICAgICAgIHwgDQogICst
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKyANCiAgfCAgICAgICAgICAgT3V0ZXIgSVAg
ICAgICAgICAgICB8IA0KICArLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSsgDQpUaGUg
Zm9ybWF0IG9mIElSIHBhY2tldD8gDQogICAgMCAgIDEgICAyICAgMyAgIDQgICA1ICAgNiAgIDcg
DQogICAtLS0gLS0tIC0tLSAtLS0gLS0tIC0tLSAtLS0gLS0tIA0KICB8ICAgICAgICAgQWRkLUNJ
RCBvY3RldCAgICAgICAgIHwgIGlmIGZvciBzbWFsbCBDSURzIGFuZCBDSUQgIT0gMCANCiAgKy0t
LSstLS0rLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rIA0KICB8IDEgICAxICAgMSAgIDEgICAxICAg
MSAgIDAgfCBEIHwgDQogICstLS0rLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKyANCiAgfCAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IA0KICAvICAgIDAtMiBvY3RldHMgb2YgQ0lE
IGluZm8gICAgIC8gIDEtMiBvY3RldHMgaWYgZm9yIGxhcmdlIENJRHMgDQogIHwgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgfCANCiAgKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKy0tLSst
LS0rIA0KICB8ICAgICAgICAgICAgUHJvZmlsZSAgICAgICAgICAgIHwgIDEgb2N0ZXQgDQogICst
LS0rLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKyANCiAgfCAgICAgICAgICAgICAgQ1JDICAg
ICAgICAgICAgICB8ICAxIG9jdGV0IA0KICArLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKy0t
LSsgDQogIHwgICAgT3V0ZXIgSVAgc3RhdGljIHBhcnQ/Pz8gICAgfCANCiAgfCAgICBJbm5lciBJ
UCBzdGF0aWMgcGFydD8/PyAgICB8c3RhdGljIGNoYWluIA0KICB8ICAgICAgICBVRFAgc3RhdGlj
IHBhcnQgICAgICAgIHwgDQogIHwgICAgICAgIFJUUCBzdGF0aWMgcGFydCAgICAgICAgfHZhcmlh
YmxlIGxlbmd0aCANCiAgICstLS0rLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKyANCiAgfCAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IA0KICB8ICAgICAgICAgRHluYW1pYyBjaGFp
biAgICAgICAgIHwgIHByZXNlbnQgaWYgRCA9IDEsIHZhcmlhYmxlIGxlbmd0aCANCiAgfCAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICB8IA0KICAgLSAtIC0gLSAtIC0gLSAtIC0gLSAtIC0g
LSAtIC0gLSANCiAgfCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IA0KICB8ICAgICAg
ICAgICBQYXlsb2FkICAgICAgICAgICAgIHwgIHZhcmlhYmxlIGxlbmd0aCANCiAgfCAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICB8IA0KICAgLSAtIC0gLSAtIC0gLSAtIC0gLSAtIC0gLSAt
IC0gLSANCltMRUpdIFllcywgbG9va3Mgb2shDQogIA0KR2VuZXJpYyBleHRlbnNpb24gaGVhZGVy
IGxpc3QgDQogICstLS0rLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKyANCiAgfCAvIEdlbmVy
aWMgZXh0ZW5zaW9uIGhlYWRlciAvICB8IHZhcmlhbCBsZW5ndGggDQogIHwgLyAgbGlzdCBvZiBv
dXRlciBJUCAoQUgpICAgLyAgfCAgIA0KICArLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKy0t
LSsgDQogIHwgLyBHZW5lcmljIGV4dGVuc2lvbiBoZWFkZXIgLyAgfCB2YXJpYWwgbGVuZ3RoIA0K
ICB8IC8gIGxpc3Qgb2YgaW5uZXIgSVAgKEFIKSAgIC8gIHwgICANCiAgKy0tLSstLS0rLS0tKy0t
LSstLS0rLS0tKy0tLSstLS0rIA0KSXMgaXQgcmlnaHQ/IA0KMS4gSXMgdGhlcmUgb25seSBvdXRl
ciBJUCBzdGF0aWMgcGFydCBleGlzdHMgaW4gSVIgcGFja2V0PyANCltMRUpdIE5vISBUaGUgcHJv
ZmlsZXMgaW4gMzA5NSBjYW4gaGFuZGxlIG9uZSBvdXRlciBhbmQgb25lIGlubmVyIElQIA0KaGVh
ZGVyLg0KVGhlc2UgYmFzZSBoZWFkZXJzIGFyZSBjb21wcmVzc2VkIGFuZCBmaWVsZHMgc2VudCBp
biBzdGF0aWMvZHluYW1pYyANCmNoYWlucy4NCkZvciBlYWNoIElQIGhlYWRlciwgdGhlcmUgYXJl
IHBvdGVudGlhbGx5IGFuIGV4dGVuc2lvbiBoZWFkZXIgbGlzdCAoZWFjaCANCklQDQpoZWFkZXIg
aXMgdGh1cyBoYW5kbGVkIHNlcGFyYXRlbHkpLg0KIA0KMi4gSWYgeWVzLCBkb2VzIG91dGVyIElQ
IHN0YXRpYyBwYXJ0IHByZWNlZGUgaW5uZXIgSVAgc3RhdGljIHBhcnQgb3IgZWxzZT8gDQpBbmQg
ZG9lcyBHZW5lcmljIGV4dGVuc2lvbiBoZWFkZXIgbGlzdCBvZiBvdXRlciBJUCBwcmVjZWRlIEdl
bmVyaWMgDQpleHRlbnNpb24gDQpoZWFkZXIgbGlzdCBvZiBpbm5lciBJUD8gDQozLiBJZiBubywg
aG93IHRvIGV4cGxhaW4gdGhlIGZvbGxvd2luZyAyIHNlbnRlbmNlIGluIFJGQzMwOTU/IA0KICAx
KSAgSW4gZmlycyBwYXJhZ3JhcGggb2YgQ2hhcHRlciA1LjguNS9SRkMzMDk1LCB0aGVyZSBpcyBv
bmUgc2VudGVuY2U6IA0KICAgICAgV2hlbiB0aGVyZSBpcyBtb3JlIHRoYW4gb25lIElQIGhlYWRl
ciwgdGhlcmUgaXMgbW9yZSB0aGFuIG9uZSBsaXN0IA0Kb2YgDQogICAgICBleHRlbnNpb24gaGVh
ZGVycy4gDQogIDIpICBJbiBDaGFwdGVyIDUuOC9SRkMzMDk1LCB0aGVyZSBpcyBhbm90aGVyIHNl
bnRlbmNlOiANCiAgICAgIElQdjYgYmFzZSBoZWFkZXJzIGFuZCBJUHY0IGhlYWRlcnMgY2Fubm90
IGJlIHBhcnQgb2YgYW4gZXh0ZW5zaW9uIA0KICAgICAgaGVhZGVyIGNoYWluLg0KW0xFSl0gSSBj
YW4gbm90IHNlZSB3aHkgdGhlc2UgdHdvIGRvZXMgbm90IG1ha2Ugc2Vuc2UgKHRoZSBmaXJzdCB0
ZXh0IGlzDQp0YWtlbiBmcm9tIHNlY3Rpb24gNS44LjQpLiBPbmUgY2FuIHN1bW1hcml6ZSB0aGVz
ZSB0d28gc3RhdGVtZW50cyB3aXRoOg0KIkJhc2UgaGVhZGVycyBhcmUgY29tcHJlc3NlZCwgY2Fu
IHRodXMgbm90IGJlIHBhcnQgb2YgYW4gZXh0ZW5zaW9uIGhlYWRlcg0KbGlzdC4gRm9yIGVhY2gg
YmFzZSBoZWFkZXIsIHRoZXJlIGlzICBwb3RlbnRpYWxseSBhIGxpc3Qgb2YgZXh0ZW5zaW9uIA0K
aGVhZGVycy4NCiANCg0KVGhpcyBjb21tdW5pY2F0aW9uIGlzIGNvbmZpZGVudGlhbCBhbmQgaW50
ZW5kZWQgc29sZWx5IGZvciB0aGUgDQphZGRyZXNzZWUocykuIEFueSB1bmF1dGhvcml6ZWQgcmV2
aWV3LCB1c2UsIGRpc2Nsb3N1cmUgb3IgZGlzdHJpYnV0aW9uIGlzIA0KcHJvaGliaXRlZC4gSWYg
eW91IGJlbGlldmUgdGhpcyBtZXNzYWdlIGhhcyBiZWVuIHNlbnQgdG8geW91IGluIGVycm9yLCAN
CnBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBieSByZXBseWluZyB0byB0aGlzIHRyYW5zbWlzc2lv
biBhbmQgZGVsZXRlIHRoZSANCm1lc3NhZ2Ugd2l0aG91dCBkaXNjbG9zaW5nIGl0LiBUaGFuayB5
b3UuDQoNCkUtbWFpbCBpbmNsdWRpbmcgYXR0YWNobWVudHMgaXMgc3VzY2VwdGlibGUgdG8gZGF0
YSBjb3JydXB0aW9uLCANCmludGVycnVwdGlvbiwgdW5hdXRob3JpemVkIGFtZW5kbWVudCwgdGFt
cGVyaW5nIGFuZCB2aXJ1c2VzLCBhbmQgd2Ugb25seSANCnNlbmQgYW5kIHJlY2VpdmUgZS1tYWls
cyBvbiB0aGUgYmFzaXMgdGhhdCB3ZSBhcmUgbm90IGxpYWJsZSBmb3IgYW55IHN1Y2ggDQpjb3Jy
dXB0aW9uLCBpbnRlcmNlcHRpb24sIGFtZW5kbWVudCwgdGFtcGVyaW5nIG9yIHZpcnVzZXMgb3Ig
YW55IA0KY29uc2VxdWVuY2VzIHRoZXJlb2YuDQoNCg0K
--=_alternative 000980AB48256E61_=
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkhpLEwtRTwvZm9udD4NCjxicj4N
Cjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+VGhhbmtzIGZvciB5b3VyIGFuc3dl
ciEgSSBhZ3JlZSB3aXRoIHUhPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJz
YW5zLXNlcmlmIj5JIHRoaW5rIGluIGltcGxlbWVudGVyIGd1aWRlLCBpdCBzaG91bGQgYmUgbWFk
ZSBjbGVhcmx5IHRoYXQgPC9mb250Pjxmb250IHNpemU9MiBjb2xvcj1yZWQgZmFjZT0ic2Fucy1z
ZXJpZiI+d2hldGhlciBPdXRlciBJUCBzdGF0aWMgcGFydCBwcmVjZWVkcyBJbm5lciBJUCBzdGF0
aWM8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiBwYXJ0IG9yIG5vdCBpZiBp
bm5lciBJUCBleGlzdHM8L2ZvbnQ+DQo8YnI+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9
InNhbnMtc2VyaWYiPk91dGVyIElQL0FIL0lubmVyIElQL0FIL0VTUC9VRFAvUlRQPC9mb250Pg0K
PGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5BY2NvcmRpbmcgdG8gZXh0
ZW5zaW9uIDMsIElubmVyIElQIHByZWNlZWRzIE91dGVyIElQLCBzbyBJIHRoaW5rIGluIElSIHBh
Y2tldHMgbWF5YmUgdGhlIGZvbGxvd2luZyBmb3JtYXQoIElubmVyIElQIHByZWNlZWRzIE91dGVy
IElQKSBpcyBiZXR0ZXI6PC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlm
Ij4mbmJzcDsgKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rPC9mb250Pjxmb250IHNp
emU9MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJz
YW5zLXNlcmlmIj4mbmJzcDsgfCAmbmJzcDsgJm5ic3A7PC9mb250Pjxmb250IHNpemU9MiBjb2xv
cj1yZWQgZmFjZT0ic2Fucy1zZXJpZiI+SW5uZXI8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNh
bnMtc2VyaWYiPiBJUCBzdGF0aWMgcGFydD8/PyAmbmJzcDsgJm5ic3A7fDwvZm9udD48Zm9udCBz
aXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1z
ZXJpZiI+PGJyPg0KICZuYnNwO3wgJm5ic3A7ICZuYnNwOzwvZm9udD48Zm9udCBzaXplPTIgY29s
b3I9Ymx1ZSBmYWNlPSJzYW5zLXNlcmlmIj5PdXRlcjwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0i
c2Fucy1zZXJpZiI+IElQIHN0YXRpYyBwYXJ0Pz8/ICZuYnNwOyAmbmJzcDt8c3RhdGljIGNoYWlu
PC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9
MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogJm5ic3A7fCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDtVRFAgc3RhdGljIHBhcnQgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7fDwvZm9udD48
Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0i
c2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwO3wgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7UlRQ
IHN0YXRpYyBwYXJ0ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO3x2YXJpYWJsZSBsZW5ndGg8
L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+DQo8YnI+PGZvbnQg
c2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwOyArLS0tKy0tLSstLS0rLS0tKy0tLSstLS0r
LS0tKy0tLSs8L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+PGZv
bnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDt8ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7PC9mb250Pjxmb250IHNpemU9MiBjb2xvcj1yZWQgZmFjZT0ic2Fucy1zZXJpZiI+SW5u
ZXI8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiBJUCBkeW4gcGFydD8/PyAm
bmJzcDsgJm5ic3A7IHw8L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2Zv
bnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDt8ICZuYnNwOyAm
bmJzcDsgJm5ic3A7PC9mb250Pjxmb250IHNpemU9MiBjb2xvcj1ibHVlIGZhY2U9InNhbnMtc2Vy
aWYiPk91dGVyPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4gSVAgZHluIHBh
cnQ/Pz8gJm5ic3A7ICZuYnNwOyB8c3RhdGljIGNoYWluPC9mb250Pjxmb250IHNpemU9MyBmYWNl
PSJzYW5zLXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+
DQogJm5ic3A7fCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyB8PC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pg0KPGJyPjxm
b250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgKy0tLSstLS0rLS0tKy0tLSstLS0r
LS0tKy0tLSstLS0rPC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250
Pg0KPGJyPg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5PdXRlciBJ
UCBzdGF0aWMgcGFydCBwcmVjZWVkcyBJbm50ZXIgSVA8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0z
Pjx0dD48YnI+DQo8L3R0PjwvZm9udD48Zm9udCBzaXplPTMgY29sb3I9cmVkPjx0dD4gJm5ic3A7
IEV4dGVuc2lvbiAzOjwvdHQ+PC9mb250Pjxmb250IHNpemU9Mz48dHQ+PGJyPg0KPGJyPg0KICZu
YnNwOyAmbmJzcDsgJm5ic3A7MCAmbmJzcDsgJm5ic3A7IDEgJm5ic3A7ICZuYnNwOyAyICZuYnNw
OyAmbmJzcDsgMyAmbmJzcDsgJm5ic3A7IDQgJm5ic3A7ICZuYnNwOyA1ICZuYnNwOyAmbmJzcDsg
NiAmbmJzcDsgJm5ic3A7IDc8YnI+DQogJm5ic3A7ICstLS0tLSstLS0tLSstLS0tLSstLS0tLSst
LS0tLSstLS0tLSstLS0tLSstLS0tLSs8YnI+DQogJm5ic3A7IHwgJm5ic3A7MSAmbmJzcDsgJm5i
c3A7IDEgJm5ic3A7fCAmbmJzcDtTICZuYnNwO3xSLVRTIHwgVHNjIHwgJm5ic3A7SSAmbmJzcDt8
IGlwICZuYnNwO3wgcnRwIHwgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsoRkxBR1MpPGJyPg0KICZuYnNwOyArLS0tLS0rLS0tLS0rLS0tLS0rLS0tLS0rLS0tLS0rLS0t
LS0rLS0tLS0rLS0tLS0rPGJyPg0KICZuYnNwOyB8ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7PC90dD48L2ZvbnQ+PGZvbnQgc2l6ZT0zIGNvbG9yPXJlZD48dHQ+SW5u
ZXIgSVAgaGVhZGVyIGZsYWdzPC90dD48L2ZvbnQ+PGZvbnQgc2l6ZT0zPjx0dD4gJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7fCBpcDIgfCAmbmJzcDtpZiBpcCA9IDE8YnI+DQogJm5ic3A7ICZu
YnNwOy4uLi4uIC4uLi4uIC4uLi4uIC4uLi4uIC4uLi4uIC4uLi4uIC4uLi4uIC4uLi4uPGJyPg0K
ICZuYnNwOyB8ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7PC90dD48
L2ZvbnQ+PGZvbnQgc2l6ZT0zIGNvbG9yPWJsdWU+PHR0Pk91dGVyIElQIGhlYWRlciBmbGFnczwv
dHQ+PC9mb250Pjxmb250IHNpemU9Mz48dHQ+ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwO3wgJm5ic3A7aWYgaXAyID0gMTxicj4NCiAmbmJzcDsgJm5ic3A7
Li4uLi4gLi4uLi4gLi4uLi4gLi4uLi4gLi4uLi4gLi4uLi4gLi4uLi4gLi4uLi48YnI+DQogJm5i
c3A7IHwgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO1NOICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgfCAmbmJzcDtp
ZiBTID0gMTxicj4NCiAmbmJzcDsgJm5ic3A7Li4uLi4gLi4uLi4gLi4uLi4gLi4uLi4gLi4uLi4g
Li4uLi4gLi4uLi4gLi4uLi48YnI+DQogJm5ic3A7IC8gJm5ic3A7ICZuYnNwOyAmbmJzcDsgVFMg
KGVuY29kZWQgYXMgaW4gc2VjdGlvbiA0LjUuNikgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
LyAmbmJzcDsxLTQgb2N0ZXRzLDxicj4NCiAmbmJzcDsgJm5ic3A7Li4uLi4gLi4uLi4gLi4uLi4g
Li4uLi4gLi4uLi4gLi4uLi4gLi4uLi4gLi4uLi4gJm5ic3A7IGlmIFItVFMgPSAxPGJyPg0KICZu
YnNwOyB8ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgfDxi
cj4NCiAmbmJzcDsgLyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOzwv
dHQ+PC9mb250Pjxmb250IHNpemU9MyBjb2xvcj1yZWQ+PHR0PklubmVyIElQIGhlYWRlciBmaWVs
ZHM8L3R0PjwvZm9udD48Zm9udCBzaXplPTM+PHR0PiAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAvICZuYnNwO3ZhcmlhYmxlLDxicj4NCiAmbmJzcDsgfCAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHwgJm5ic3A7aWYgaXAgPSAx
PGJyPg0KICZuYnNwOyAmbmJzcDsuLi4uLiAuLi4uLiAuLi4uLiAuLi4uLiAuLi4uLiAuLi4uLiAu
Li4uLiAuLi4uLjxicj4NCiAmbmJzcDsgfCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgSVAtSUQgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
IHwgJm5ic3A7MiBvY3RldHMsIGlmIEkgPSAxPGJyPg0KICZuYnNwOyAmbmJzcDsuLi4uLiAuLi4u
LiAuLi4uLiAuLi4uLiAuLi4uLiAuLi4uLiAuLi4uLiAuLi4uLjxicj4NCiAmbmJzcDsgfCAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHw8YnI+DQogJm5ic3A7
IC8gJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyA8L3R0PjwvZm9udD48Zm9udCBz
aXplPTMgY29sb3I9Ymx1ZT48dHQ+Jm5ic3A7T3V0ZXIgSVAgaGVhZGVyIGZpZWxkczwvdHQ+PC9m
b250Pjxmb250IHNpemU9Mz48dHQ+ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7IC8gJm5ic3A7dmFyaWFibGUsPGJyPg0KICZuYnNwOyB8ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgfCAmbmJzcDtpZiBpcDIgPSAxPGJyPg0KICZu
YnNwOyAmbmJzcDsuLi4uLiAuLi4uLiAuLi4uLiAuLi4uLiAuLi4uLiAuLi4uLiAuLi4uLiAuLi4u
Ljxicj4NCiAmbmJzcDsgfCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7IHw8YnI+DQogJm5ic3A7IC8gJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
O1JUUCBoZWFkZXIgZmxhZ3MgYW5kIGZpZWxkcyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7LyAmbmJzcDt2YXJpYWJsZSw8YnI+DQogJm5ic3A7IHwgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyB8ICZuYnNwO2lmIHJ0cCA9IDE8YnI+DQogJm5i
c3A7ICZuYnNwOy4uLi4uIC4uLi4uIC4uLi4uIC4uLi4uIC4uLi4uIC4uLi4uIC4uLi4uIC4uLi4u
PGJyPg0KPC90dD48L2ZvbnQ+DQo8YnI+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNh
bnMtc2VyaWYiPkJlc3QgUmVnYXJkczxicj4NCiA8YnI+DQpaaG91IFpvbmdtaW5nINbc19rD9zxi
cj4NCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PTxicj4NCkNPTU1JVCBJbmNvcnBvcmF0ZWQ8YnI+DQpBZGQ6
IDE4IFNoZW53YW5nIFJkLCBYaW56aHVhbmcgSW5kdXN0cmlhbCBEZXZlbG9wbWVudCBab25lLCBT
aGFuZ2hhaSBDaGluYTxicj4NClBvc3QgQ29kZTogMjAxMTA4PGJyPg0KVGVsOiArODYtMjEtNTQ0
Mi00ODg1IEV4dDozNDA1PGJyPg0KRkFYOiArODYtMjEtNTQ0Mi00ODg2PGJyPg0KRW1haWw6IHpv
bmdtaW5nLnpob3VAY29tbWl0LmNuPGJyPg0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PGJyPg0KVGhlIGlu
Zm9ybWF0aW9uIGNvbnRhaW5lZCBpbiB0aGlzIGUtbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIHRo
ZXJldG8gZnJvbSBDT01NSVQgSW5jb3Jwb3JhdGVkIGlzIGludGVuZGVkIHRvIGJlIGZvciB0aGUg
dXNlIG9mIHRoZSBwZXJzb24gbmFtZWQgYWJvdmUgYW5kIG1heSBiZSBwcml2YXRlLCBjb25maWRl
bnRpYWwgYW5kIHByaXZpbGVnZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZCByZWNpcGll
bnQgb2YgdGhpcyB0cmFuc21pc3Npb24sIHlvdSBhcmUgaGVyZWJ5IG5vdGlmaWVkIHRoYXQgYW55
IGRpc2Nsb3N1cmUsIGNvcHlpbmcsIGRpc3RyaWJ1dGlvbiwgcHJpbnRpbmcgb3IgdXNlIG9mIHRo
ZSBjb250ZW50cyBvZiB0aGlzIGNvbW11bmljYXRpb24gaXMgc3RyaWN0bHkgcHJvaGliaXRlZC4g
SWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlLW1haWwgaW4gZXJyb3IsIHBsZWFzZSBub3RpZnkg
dGhlIHNlbmRlciBpbW1lZGlhdGVseSBhbmQgcGVybWFuZW50bHkgZGVsZXRlIHRoZSBvcmlnaW5h
bCBhbmQgYW55IGNvcGllcyBvZiB0aGlzIGVtYWlsIGFuZCBhbnkgYXR0YWNobWVudHMgdGhlcmV0
by48L2ZvbnQ+DQo8YnI+DQo8YnI+DQo8YnI+DQo8dGFibGUgd2lkdGg9MTAwJT4NCjx0ciB2YWxp
Z249dG9wPg0KPHRkPg0KPHRkPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj48Yj4mcXVv
dDtMYXJzLUVyaWsgSm9uc3NvbiAoTFUvRUFCKSZxdW90OyAmbHQ7bGFycy1lcmlrLmpvbnNzb25A
ZXJpY3Nzb24uY29tJmd0OzwvYj48L2ZvbnQ+DQo8cD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1z
ZXJpZiI+MjAwNC0wMy0yMyAyMjozNjwvZm9udD4NCjxicj4NCjx0ZD48Zm9udCBzaXplPTEgZmFj
ZT0iQXJpYWwiPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyA8L2ZvbnQ+DQo8YnI+PGZvbnQg
c2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBUbzog
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7JnF1b3Q7J1pvbmdtaW5nLlpob3VAY29tbWl0LmNu
JyZxdW90OyAmbHQ7Wm9uZ21pbmcuWmhvdUBjb21taXQuY24mZ3Q7LCByb2hjQGlldGYub3JnPC9m
b250Pg0KPGJyPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgY2M6ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOzwvZm9udD4NCjxicj48
Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
IFN1YmplY3Q6ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO1JFOiBbcm9oY10gUXVlc3Rpb24g
b2YgUk9IQzwvZm9udD48L3RhYmxlPg0KPGJyPg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBjb2xv
cj1ibHVlIGZhY2U9IkFyaWFsIj5JJ3ZlIHRyaWVkIHRvIGFuc3dlciBiZWxvdywgbGV0IG1lIGtu
b3cgaWYgSSBoYXZlIG1pc3VuZGVyc3Rvb2QgeW91ciBxdWVzdGlvbnMuPC9mb250Pg0KPGJyPjxm
b250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDs8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6
ZT0yIGNvbG9yPWJsdWUgZmFjZT0iQXJpYWwiPi9MLUU8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0y
IGZhY2U9IlRhaG9tYSI+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08Yj48YnI+DQpGcm9tOjwv
Yj4gcm9oYy1hZG1pbkBpZXRmLm9yZyBbbWFpbHRvOnJvaGMtYWRtaW5AaWV0Zi5vcmddPGI+T24g
QmVoYWxmIE9mIDwvYj5ab25nbWluZy5aaG91QGNvbW1pdC5jbjxiPjxicj4NClNlbnQ6PC9iPiBk
ZW4gMTggbWFycyAyMDA0IDAzOjA2PGI+PGJyPg0KVG86PC9iPiByb2hjQGlldGYub3JnPGI+PGJy
Pg0KU3ViamVjdDo8L2I+IFtyb2hjXSBRdWVzdGlvbiBvZiBST0hDPGJyPg0KPC9mb250Pg0KPGJy
Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQo8YnI+DQpJZiBmb3IgdGhpcyBj
YXNlOjwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9udD48Zm9udCBz
aXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwOystLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tKzwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9u
dD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwO3wgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7UlRQICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO3wgPGJyPg0KICZuYnNwOystLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKzwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1z
ZXJpZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNw
O3wgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7VVRQICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO3wgPGJyPg0KICZu
YnNwOystLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKyA8YnI+DQogJm5ic3A7fCAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtBSCAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgfCA8YnI+DQogJm5ic3A7Ky0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rPC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJz
YW5zLXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQog
Jm5ic3A7fCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IElubmVyIElQICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7fCA8YnI+DQogJm5ic3A7Ky0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rPC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5z
LXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogJm5i
c3A7fCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtBSCAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgfCA8YnI+DQog
Jm5ic3A7Ky0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rPC9mb250Pjxmb250IHNpemU9
MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlm
Ij48YnI+DQogJm5ic3A7fCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IE91dGVy
IElQICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7fCA8YnI+DQogJm5i
c3A7Ky0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rIDxicj4NClRoZSBmb3JtYXQgb2Yg
SVIgcGFja2V0PzwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9udD48
Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwOyAmbmJzcDswICZuYnNw
OyAxICZuYnNwOyAyICZuYnNwOyAzICZuYnNwOyA0ICZuYnNwOyA1ICZuYnNwOyA2ICZuYnNwOyA3
PC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9
MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogJm5ic3A7IC0tLSAtLS0gLS0tIC0tLSAtLS0gLS0t
IC0tLSAtLS08L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+PGZv
bnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDt8ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyBBZGQtQ0lEIG9jdGV0ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyB8
ICZuYnNwO2lmIGZvciBzbWFsbCBDSURzIGFuZCBDSUQgIT0gMDwvZm9udD48Zm9udCBzaXplPTMg
ZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+
PGJyPg0KICZuYnNwOystLS0rLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKzwvZm9udD48Zm9u
dCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fu
cy1zZXJpZiI+PGJyPg0KICZuYnNwO3wgMSAmbmJzcDsgMSAmbmJzcDsgMSAmbmJzcDsgMSAmbmJz
cDsgMSAmbmJzcDsgMSAmbmJzcDsgMCB8IEQgfDwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fu
cy1zZXJpZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZu
YnNwOystLS0rLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKzwvZm9udD48Zm9udCBzaXplPTMg
ZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+
PGJyPg0KICZuYnNwO3wgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgfDwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9udD48Zm9u
dCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwOy8gJm5ic3A7ICZuYnNwOzAt
MiBvY3RldHMgb2YgQ0lEIGluZm8gJm5ic3A7ICZuYnNwOyAvICZuYnNwOzEtMiBvY3RldHMgaWYg
Zm9yIGxhcmdlIENJRHM8L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2Zv
bnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDt8ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHw8L2ZvbnQ+PGZvbnQgc2l6
ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2Vy
aWYiPjxicj4NCiAmbmJzcDsrLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKy0tLSs8L2ZvbnQ+
PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9
InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDt8ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7UHJvZmlsZSAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwO3wgJm5ic3A7MSBvY3RldDwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+
IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwOystLS0r
LS0tKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKzwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fu
cy1zZXJpZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZu
YnNwO3wgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7Q1JD
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO3wgJm5ic3A7
MSBvY3RldDwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9udD48Zm9u
dCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwOystLS0rLS0tKy0tLSstLS0r
LS0tKy0tLSstLS0rLS0tKzwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwv
Zm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwO3wgJm5ic3A7
ICZuYnNwO091dGVyIElQIHN0YXRpYyBwYXJ0Pz8/ICZuYnNwOyAmbmJzcDt8PC9mb250Pjxmb250
IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5z
LXNlcmlmIj48YnI+DQogJm5ic3A7fCAmbmJzcDsgJm5ic3A7SW5uZXIgSVAgc3RhdGljIHBhcnQ/
Pz8gJm5ic3A7ICZuYnNwO3xzdGF0aWMgY2hhaW48L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNh
bnMtc2VyaWYiPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCiAm
bmJzcDt8ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO1VEUCBzdGF0aWMgcGFydCAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDt8PC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlm
Ij4gPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogJm5ic3A7fCAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtSVFAgc3RhdGljIHBhcnQgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7fHZhcmlhYmxlIGxlbmd0aDwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fu
cy1zZXJpZiI+IDwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5i
c3A7ICZuYnNwOystLS0rLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rLS0tKzwvZm9udD48Zm9udCBz
aXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1z
ZXJpZiI+PGJyPg0KICZuYnNwO3wgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgfDwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9u
dD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwO3wgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7IER5bmFtaWMgY2hhaW4gJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7IHwgJm5ic3A7cHJlc2VudCBpZiBEID0gMSwgdmFyaWFibGUgbGVuZ3RoPC9mb250Pjxmb250
IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5z
LXNlcmlmIj48YnI+DQogJm5ic3A7fCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyB8PC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9m
b250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogJm5ic3A7IC0gLSAtIC0g
LSAtIC0gLSAtIC0gLSAtIC0gLSAtIC08L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2Vy
aWYiPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDt8
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IHw8L2ZvbnQ+
PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9
InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDt8ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgUGF5bG9hZCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyB8
ICZuYnNwO3ZhcmlhYmxlIGxlbmd0aDwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJp
ZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwO3wg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgfDwvZm9udD48
Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0i
c2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwOyAtIC0gLSAtIC0gLSAtIC0gLSAtIC0gLSAtIC0gLSAt
PC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9
MiBjb2xvcj1ibHVlIGZhY2U9IkFyaWFsIj48YnI+DQpbTEVKXSBZZXMsIGxvb2tzIG9rITwvZm9u
dD4NCjxicj48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7PC9mb250Pjxmb250
IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4gPGJyPg0KR2VuZXJpYyBleHRlbnNpb24gaGVhZGVy
IGxpc3Q8L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+PGZvbnQg
c2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDsrLS0tKy0tLSstLS0rLS0tKy0t
LSstLS0rLS0tKy0tLSs8L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2Zv
bnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDt8IC8gR2VuZXJp
YyBleHRlbnNpb24gaGVhZGVyIC8gJm5ic3A7fCB2YXJpYWwgbGVuZ3RoPC9mb250Pjxmb250IHNp
emU9MyBmYWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNl
cmlmIj48YnI+DQogJm5ic3A7fCAvICZuYnNwO2xpc3Qgb2Ygb3V0ZXIgSVAgKEFIKSAmbmJzcDsg
LyAmbmJzcDt8ICZuYnNwOzwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+IDwv
Zm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNwOystLS0rLS0t
Ky0tLSstLS0rLS0tKy0tLSstLS0rLS0tKzwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1z
ZXJpZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KICZuYnNw
O3wgLyBHZW5lcmljIGV4dGVuc2lvbiBoZWFkZXIgLyAmbmJzcDt8IHZhcmlhbCBsZW5ndGg8L2Zv
bnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZh
Y2U9InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDt8IC8gJm5ic3A7bGlzdCBvZiBpbm5lciBJUCAo
QUgpICZuYnNwOyAvICZuYnNwO3wgJm5ic3A7PC9mb250Pjxmb250IHNpemU9MyBmYWNlPSJzYW5z
LXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQogJm5i
c3A7Ky0tLSstLS0rLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rPC9mb250Pjxmb250IHNpemU9MyBm
YWNlPSJzYW5zLXNlcmlmIj4gPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj48
YnI+DQpJcyBpdCByaWdodD88L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8
L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCjEuIElzIHRoZXJlIG9u
bHkgb3V0ZXIgSVAgc3RhdGljIHBhcnQgZXhpc3RzIGluIElSIHBhY2tldD88L2ZvbnQ+PGZvbnQg
c2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGNvbG9yPWJsdWUg
ZmFjZT0iQXJpYWwiPjxicj4NCltMRUpdIE5vISBUaGUgcHJvZmlsZXMgaW4gMzA5NSBjYW4gaGFu
ZGxlIG9uZSBvdXRlciBhbmQgb25lIGlubmVyIElQIGhlYWRlci48L2ZvbnQ+DQo8YnI+PGZvbnQg
c2l6ZT0yIGNvbG9yPWJsdWUgZmFjZT0iQXJpYWwiPlRoZXNlIGJhc2UgaGVhZGVycyBhcmUgY29t
cHJlc3NlZCBhbmQgZmllbGRzIHNlbnQgaW4gc3RhdGljL2R5bmFtaWMgY2hhaW5zLjwvZm9udD4N
Cjxicj48Zm9udCBzaXplPTIgY29sb3I9Ymx1ZSBmYWNlPSJBcmlhbCI+Rm9yIGVhY2ggSVAgaGVh
ZGVyLCB0aGVyZSBhcmUgcG90ZW50aWFsbHkgYW4gZXh0ZW5zaW9uIGhlYWRlciBsaXN0IChlYWNo
IElQPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBjb2xvcj1ibHVlIGZhY2U9IkFyaWFsIj5oZWFk
ZXIgaXMgdGh1cyBoYW5kbGVkIHNlcGFyYXRlbHkpLjwvZm9udD4NCjxicj48Zm9udCBzaXplPTMg
ZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7PC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNl
cmlmIj48YnI+DQoyLiBJZiB5ZXMsIGRvZXMgb3V0ZXIgSVAgc3RhdGljIHBhcnQgcHJlY2VkZSBp
bm5lciBJUCBzdGF0aWMgcGFydCBvciBlbHNlPzwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fu
cy1zZXJpZiI+IDwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KQW5k
IGRvZXMgR2VuZXJpYyBleHRlbnNpb24gaGVhZGVyIGxpc3Qgb2Ygb3V0ZXIgSVAgcHJlY2VkZSBH
ZW5lcmljIGV4dGVuc2lvbiA8YnI+DQpoZWFkZXIgbGlzdCBvZiBpbm5lciBJUD88L2ZvbnQ+PGZv
bnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNh
bnMtc2VyaWYiPjxicj4NCjMuIElmIG5vLCBob3cgdG8gZXhwbGFpbiB0aGUgZm9sbG93aW5nIDIg
c2VudGVuY2UgaW4gUkZDMzA5NT88L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYi
PiA8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDsxKSAm
bmJzcDtJbiBmaXJzIHBhcmFncmFwaCBvZiBDaGFwdGVyIDUuOC41L1JGQzMwOTUsIHRoZXJlIGlz
IG9uZSBzZW50ZW5jZTo8L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2Zv
bnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDsgJm5ic3A7ICZu
YnNwO1doZW4gdGhlcmUgaXMgbW9yZSB0aGFuIG9uZSBJUCBoZWFkZXIsIHRoZXJlIGlzIG1vcmUg
dGhhbiBvbmUgbGlzdCBvZiA8YnI+DQogJm5ic3A7ICZuYnNwOyAmbmJzcDtleHRlbnNpb24gaGVh
ZGVycy48L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPiA8L2ZvbnQ+PGZvbnQg
c2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCiAmbmJzcDsyKSAmbmJzcDtJbiBDaGFwdGVy
IDUuOC9SRkMzMDk1LCB0aGVyZSBpcyBhbm90aGVyIHNlbnRlbmNlOiA8YnI+DQogJm5ic3A7ICZu
YnNwOyAmbmJzcDtJUHY2IGJhc2UgaGVhZGVycyBhbmQgSVB2NCBoZWFkZXJzIGNhbm5vdCBiZSBw
YXJ0IG9mIGFuIGV4dGVuc2lvbiA8YnI+DQogJm5ic3A7ICZuYnNwOyAmbmJzcDtoZWFkZXIgY2hh
aW4uPC9mb250Pjxmb250IHNpemU9MiBjb2xvcj1ibHVlIGZhY2U9IkFyaWFsIj48YnI+DQpbTEVK
XSBJIGNhbiBub3Qgc2VlIHdoeSB0aGVzZSB0d28gZG9lcyBub3QgbWFrZSBzZW5zZSAodGhlIGZp
cnN0IHRleHQgaXM8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGNvbG9yPWJsdWUgZmFjZT0iQXJp
YWwiPnRha2VuIGZyb20gc2VjdGlvbiA1LjguNCkuIE9uZSBjYW4gc3VtbWFyaXplIHRoZXNlIHR3
byBzdGF0ZW1lbnRzIHdpdGg6PC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBjb2xvcj1ibHVlIGZh
Y2U9IkFyaWFsIj4mcXVvdDtCYXNlIGhlYWRlcnMgYXJlIGNvbXByZXNzZWQsIGNhbiB0aHVzIG5v
dCBiZSBwYXJ0IG9mIGFuIGV4dGVuc2lvbiBoZWFkZXI8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0y
IGNvbG9yPWJsdWUgZmFjZT0iQXJpYWwiPmxpc3QuIEZvciBlYWNoIGJhc2UgaGVhZGVyLCB0aGVy
ZSBpcyAmbmJzcDtwb3RlbnRpYWxseSBhIGxpc3Qgb2YgZXh0ZW5zaW9uIGhlYWRlcnMuPC9mb250
Pg0KPGJyPjxmb250IHNpemU9MyBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDs8L2ZvbnQ+DQo8YnI+
PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NClRoaXMgY29tbXVuaWNhdGlvbiBp
cyBjb25maWRlbnRpYWwgYW5kIGludGVuZGVkIHNvbGVseSBmb3IgdGhlIGFkZHJlc3NlZShzKS4g
QW55IHVuYXV0aG9yaXplZCByZXZpZXcsIHVzZSwgZGlzY2xvc3VyZSBvciBkaXN0cmlidXRpb24g
aXMgcHJvaGliaXRlZC4gSWYgeW91IGJlbGlldmUgdGhpcyBtZXNzYWdlIGhhcyBiZWVuIHNlbnQg
dG8geW91IGluIGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIgYnkgcmVwbHlpbmcgdG8g
dGhpcyB0cmFuc21pc3Npb24gYW5kIGRlbGV0ZSB0aGUgbWVzc2FnZSB3aXRob3V0IGRpc2Nsb3Np
bmcgaXQuIFRoYW5rIHlvdS48YnI+DQo8YnI+DQpFLW1haWwgaW5jbHVkaW5nIGF0dGFjaG1lbnRz
IGlzIHN1c2NlcHRpYmxlIHRvIGRhdGEgY29ycnVwdGlvbiwgaW50ZXJydXB0aW9uLCB1bmF1dGhv
cml6ZWQgYW1lbmRtZW50LCB0YW1wZXJpbmcgYW5kIHZpcnVzZXMsIGFuZCB3ZSBvbmx5IHNlbmQg
YW5kIHJlY2VpdmUgZS1tYWlscyBvbiB0aGUgYmFzaXMgdGhhdCB3ZSBhcmUgbm90IGxpYWJsZSBm
b3IgYW55IHN1Y2ggY29ycnVwdGlvbiwgaW50ZXJjZXB0aW9uLCBhbWVuZG1lbnQsIHRhbXBlcmlu
ZyBvciB2aXJ1c2VzIG9yIGFueSBjb25zZXF1ZW5jZXMgdGhlcmVvZi48L2ZvbnQ+DQo8YnI+DQo8
YnI+DQo=
--=_alternative 000980AB48256E61_=--

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



From exim@www1.ietf.org  Wed Mar 24 02:21:34 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21422
	for <rohc-archive@odin.ietf.org>; Wed, 24 Mar 2004 02:21:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B62hF-0005F7-Fn
	for rohc-archive@odin.ietf.org; Wed, 24 Mar 2004 02:21:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2O7L5ka020151
	for rohc-archive@odin.ietf.org; Wed, 24 Mar 2004 02:21:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B62hE-0005Ew-3p
	for rohc-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 02:21:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20833
	for <rohc-web-archive@ietf.org>; Wed, 24 Mar 2004 02:21:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B62h9-00024a-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 02:20:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B62gE-0001tE-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 02:20:03 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B62fE-0001il-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 02:19:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B62fF-0004oY-SO; Wed, 24 Mar 2004 02:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5r3j-0005gO-Jf
	for rohc@optimus.ietf.org; Tue, 23 Mar 2004 13:55:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17746
	for <rohc@ietf.org>; Tue, 23 Mar 2004 13:55:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5r3g-0001di-00
	for rohc@ietf.org; Tue, 23 Mar 2004 13:55:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5r2p-0001ZO-00
	for rohc@ietf.org; Tue, 23 Mar 2004 13:54:36 -0500
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5r26-0001WK-00; Tue, 23 Mar 2004 13:53:50 -0500
Message-ID: <01f501c41108$3e915920$366115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Ghyslain Pelletier" <Ghyslain.Pelletier@ericsson.com>,
        "Carsten Bormann" <cabo@tzi.org>,
        "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@ericsson.com>,
        <rohc@ietf.org>
Cc: <seamoby@ietf.org>, <mankin@psg.com>
References: <033d01c4088d$017a74f0$366115ac@dcml.docomolabsusa.com> <40603B25.3E133C79@ericsson.com>
Date: Tue, 23 Mar 2004 10:54:17 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Subject: [rohc] Re: [Seamoby] AD Review Issues with draft-ietf-seamoby-ctp-08.txt
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Ghyslain,

The draft is at
http://www.ietf.org/internet-drafts/draft-ietf-seamoby-ctp-08.txt. Since =
we
currently have a disagreement about what transport protocol to use, we wi=
ll
not be able to send the draft to the IESG until that is resolved, which
might take a while. If you or anyone else in ROHC have comments on the
draft, please send them to the Seamoby list by April 5. Otherwise, as wit=
h
any IETF draft, you can send your comments during IETF Last Call if you
don't manage to read the draft in the next two weeks. When you read the
draft, please keep in mind that the protocol is intended to be published =
as
Experimental, not Standards Track, because there are many open questions,
and also please remember that ROHC is not the only application for CT.

BTW, there is a draft draft-koodli-seamoby-hc-relocate-03.txt which is no=
w
expired that describes a ROHC context profile. There are efforts under wa=
y
to implement and test this draft, in the context of the MOBOPTS IRTF
research group. Since the Seamoby charter does not cover doing specific
context profiles (and the IESG wants Seamoby to close down as soon as
possible), Seamoby can't really continue working on it, but there is some
interest in seeing it discussed in ROHC, where the experts on header
compression are. Hopefully, the experiments that are currently under way =
can
help resolve some of the controversy about CT for header compression by
basing discussion about whether CT for header compression actually helps
reduce handover latency on experimental data rather than on microphone ti=
me
and mailing list opinion.

            jak


----- Original Message -----=20
From: "Ghyslain Pelletier" <Ghyslain.Pelletier@ericsson.com>
To: "James Kempf" <kempf@docomolabs-usa.com>; "Carsten Bormann"
<cabo@tzi.org>; "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@ericsson.com=
>;
<rohc@ietf.org>
Cc: <seamoby@ietf.org>
Sent: Tuesday, March 23, 2004 5:27 AM
Subject: Re: [Seamoby] AD Review Issues with draft-ietf-seamoby-ctp-08.tx=
t


> Hi,
>
> > The review by someone from the ROHC WG turned up no issues.
>
> Who is this reviewer? What were the comments?
> If I understand correctly from an earlier mail from James Kempf (March
> 11th), this person is not Carsten Bormann, and I know that it is not hi=
s
> ROHC co-chair either for having asked.
>
> I think the draft should be submitted for review to the ROHC wg via
> their mailing list. After all, it has been written many times on the
> Seamoby mailing list that "ROHC is a potential customer of CTP", so I
> don't see any reason not to send the document for a somewhat broader
> review to that wg.
>
> Best regards,
>
> /Ghyslain
>
> James Kempf wrote:
> >
> > AD Review of the CTP draft (draft-ietf-seamoby-ctp-08.txt) is now
complete.
> > The review by someone from the ROHC WG turned up no issues. However, =
in
> > discussions with Allison, there were a couple issues that arose. They
are
> > listed below. Prior to submitting a revised draft to the IESG for
review,
> > Allison and I would like to obtain resolution on these issues. Please
send
> > comments to the list by next Fri. (March 19).
> >
> >             jak
> >
> > -------------------------------
> >
> > Issue 1
> > --------
> >
> > Issue: The MLD example in Appendix B as written is not very persuasiv=
e.
The
> > 3G protocols don't use ND, and 802.11 is fast enough that it wouldn't
make
> > much difference.
> >
> > Suggested resolution: Replace the first paragraph of Appendix B with =
the
> > following:
> >
> >    In the past, credible proposals have been made in the Seamoby Work=
ing
> > Group
> >    and elsewhere for using context transfer to speed handover of
> > authentication, authorization,
> >    and accounting information, distributed firewall state, PPP contex=
t,
and
> > header
> >    compression context. Because the Working Group was not chartered t=
o
> >    develop context profile definitions for specific applications, non=
e
of
> > the proposals
> >    submitted to Seamoby were accepted as Working Group items. At this
time,
> > work
> >    continues to develop a context profile definition for RFC 3095 hea=
der
> > compression
> >    context [RFC3095] and to characterize the performance gains
obtainable by
> > using
> >    header compression, but the work is not yet complete. In addition,
there
> > are several
> >    commercial wireless products that reportedly use non-standard,
> > non-interoperable
> >    context transfer protocols.
> >
> >    As a consequence, it is difficult at this time to point to with a
solid
> > example of
> >    how context transfer could result in a commercially viable, widely
> > deployable,
> >    interoperable benefit  for wireless networks. This is one reason w=
hy
CTP
> > is being
> >    proposed as an Experimental protocol, rather than Standards Track.
> > However, it
> >    nevertheless seems valuable to have a simple example that shows ho=
w
> > handover
> >    could benefit from using CTP. As an example of how context transfe=
r
can
> > improve the
> >    performance of IP layer handover, we consider transferring IPv6 ML=
D
state
> > [RFC2710].
> >    MLD state is a particularly good example because every IPv6 node m=
ust
> >   perform two MLD messaging sequences on the wireless link to establi=
sh
> >    itself as an MLD listener prior to performing router discovery
> >    [RFC2461] or duplicate address detection [RFC2462] or before
> >    sending/receiving any application-specific traffic (including Mobi=
le
> >    IP handover signaling, if any). The node must subscribe to the Sol=
i-
> >    cited Node Multicast Address as soon as it comes up on the link. A=
ny
> >    application-specific multicast addresses must be re-established as
> >    well. Context transfer can significantly speed up re-establishing
> >    multicast state by allowing the nAR to initialize MLD for a node t=
hat
> >    just completed handover; without any MLD signaling on the new wire=
-
> >    less link. The same approach could be used for transferring multic=
ast
> >    context in IPv4.
> >
> > and add the following paragraph after the second paragraph Appendix B=
 in
the
> > current draft:
> >
> >    This example might seem a bit contrived because MLD isn't used in
typical
> >    cellular protocols and wireless local area network protocols
typically
> > have
> >    enough bandwidth that sending a single MLD message might not be
viewed
> >    as such a performance burden. An example of a wireless protocol wh=
ere
MLD
> >    context transfer might be useful is IEEE 802.15.1 (Bluetooth). IEE=
E
> > 802.15.1 has
> >    two IP "profiles": one with and one without PPP. The profile witho=
ut
PPP
> > would
> >    use MLD. 802.15.1 has a maximum bandwidth of about 800kbps, shared
> > between
> >    all nodes on the link, so a host on a moderately loaded 802.15.1
access
> > point could
> >    experience the kind of bandwith described in the previous paragrap=
h.
In
> > addition
> >    802.15.1 handover times typically run upwards of a second or more
because
> > the
> >    host must resynchronize its frequency hopping pattern with the acc=
ess
> > point, so
> >    anything the IP layer could do to to alleviate further delay would=
 be
> > beneficial.
> >
> > and removing the following two sentences from the second paragraph in
> > Appendix B:
> >
> >   The former is approximate for a narrowband 3G cel-
> >    lular links and the latter for a heavily utilized 802.11b WLAN lin=
k,
> >    both running Voice over IP (VoIP).
> >
> >   Considering most ATM-based 3G voice cellular pro-
> >    tocols try to keep total voice handover delay less than 40- 80 mse=
c.,
> >    MLD signaling could have a large impact on the performance of inte=
r-
> >    subnet VoIP handover.
> >
> > Issue 2
> > --------
> >
> > Issue: The draft as written specifies using UDP without retransmit fo=
r
the
> > transport protocol. This is not acceptable from a congestion control =
and
> > usability standpoint, the points made in Appendix  A about timing
> > notwidthstanding. Both Allison and James brought up these issues at
various
> > times during the requirements discussion and during previous reviews =
of
the
> > draft.
> >
> > The issue with UDP is that CTP is expected to be used frequently betw=
een
> > access routers in a wide area network, like between two hotspot clust=
ers
> > connected by T1 or other low capacity lines. Since access networks of
these
> > types are just where one might expect congestion to develop, the
frequency
> > of packet drops for UDP without retransmit would be expected to be hi=
gh
> > enough to render the protocol unusable in general. While the Working
Group
> > could develop a specialized UDP retransmit algorithm, there is no nee=
d
since
> > both TCP and SCTP could provide adequate performance for CTP. Below a=
re
two
> > suggestions for resolution of the issue, and a preferred resolution.
> >
> > Suggestion 1: Use TCP.
> >
> > The advantage of this suggestion is that TCP is already widely
implemented
> > and is well understood, so it could serve for immediate implementatio=
n
and
> > experiment. The disadvantage is that TCP provides no way to control t=
he
> > retransmit timer in general, so the timeliness of the transfer could =
not
be
> > assured without additional measures.
> >
> > Suggestion 2: Use SCTP.
> >
> > The advantage of using SCTP is that it provides a partial reliability
mode
> > which allows the retransmit timer to be set. This would allow the
timeliness
> > of the transfer to be controlled. The disadvantage is that SCTP is no=
t
yet
> > widely implemented.
> >
> > Preferred Resolution: Suggestion 2.
> >
> > _______________________________________________
> > Seamoby mailing list
> > Seamoby@ietf.org
> > https://www1.ietf.org/mailman/listinfo/seamoby
>
> --=20
> Ghyslain Pelletier, Dipl. Ing.
> Wireless IP Optimizations
> AWARE - Advanced Wireless Algorithm Research
> Ericsson Research, Corporate Unit
>
> Ericsson AB, Laboratoriegr=E4nd 11
> Box 920, S-97128 Lule=E5, SWEDEN
> Phone : +46 (0) 920 20 24 32
> Mobile: +46 (0) 706 09 27 73
> Ghyslain.Pelletier@ericsson.com
> http://www.ericsson.com
>
> I have a new mail address: Ghyslain.Pelletier@ericsson.com
> My old e-mail address will function until 2004-06-01.
> Please change my address in your personal address book.
>
> This communication is confidential and intended solely for the
addressee(s). Any unauthorized review, use, disclosure or distribution is
prohibited. If you believe this message has been sent to you in error,
please notify the sender by replying to this transmission and delete the
message without disclosing it. Thank you.
>
> E-mail including attachments is susceptible to data corruption,
interruption, unauthorized amendment, tampering and viruses, and we only
send and receive e-mails on the basis that we are not liable for any such
corruption, interception, amendment, tampering or viruses or any
consequences thereof.
>


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



From exim@www1.ietf.org  Wed Mar 24 02:38:38 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01200
	for <rohc-archive@odin.ietf.org>; Wed, 24 Mar 2004 02:38:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B62xc-0000mC-46
	for rohc-archive@odin.ietf.org; Wed, 24 Mar 2004 02:38:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2O7bxK6002975
	for rohc-archive@odin.ietf.org; Wed, 24 Mar 2004 02:37:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B62xb-0000lr-Fp
	for rohc-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 02:37:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01163
	for <rohc-web-archive@ietf.org>; Wed, 24 Mar 2004 02:37:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B62xX-0005Ux-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 02:37:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B62wY-0005Hp-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 02:36:55 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B62ve-00054L-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 02:35:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B62vh-00009j-DX; Wed, 24 Mar 2004 02:36:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B62up-0008TT-JL
	for rohc@optimus.ietf.org; Wed, 24 Mar 2004 02:35:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00995
	for <rohc@ietf.org>; Wed, 24 Mar 2004 02:35:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B62ul-0004pI-00
	for rohc@ietf.org; Wed, 24 Mar 2004 02:35:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B62tn-0004dO-00
	for rohc@ietf.org; Wed, 24 Mar 2004 02:34:05 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B62t3-0004Rc-00
	for rohc@ietf.org; Wed, 24 Mar 2004 02:33:17 -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 i2O7XFAh003797
	for <rohc@ietf.org>; Wed, 24 Mar 2004 08:33:15 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Wed, 24 Mar 2004 08:33:14 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <HQ46NHN7>; Wed, 24 Mar 2004 08:33:14 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E94E2@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'Zongming.Zhou@commit.cn'" <Zongming.Zhou@commit.cn>
Cc: rohc@ietf.org
Subject: RE: [rohc] Question of ROHC
Date: Wed, 24 Mar 2004 08:33:07 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C41170.AF8A0072"
X-OriginalArrivalTime: 24 Mar 2004 07:33:14.0924 (UTC) FILETIME=[44AB56C0:01C41172]
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_40_50,
	HTML_FONTCOLOR_BLUE,HTML_FONTCOLOR_UNKNOWN,HTML_MESSAGE autolearn=no 
	version=2.60

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C41170.AF8A0072
Content-Type: text/plain;
	charset="gb2312"

In the static and dynamic chains, the outer fields obviously preceeds the inner fields,
as that is the order in which they appear in the original header(s). As the static and
dynamic chains are only implicitly defined as chains of fields from the original
header(s), there is not really any other way these can be ordered. When corresponding
fields are present in compressed headers or their extensions, the order and encoding
of the fields are explicitly defined for each packet format, and as you have noted the
inner fields are put before the outer in extension 3. At this point in time, we can of
course discuss why this is the case, but arguing that it should had been the other way
around does not help us much as we can not change the way it is defined (and it
is just a cosmetic issue anyway). I would guess the reason the fields are put in this
order is to have the fields that are most commonly present listed first, and "inner" is
defined as the fields corresponding to the fields of one single IP header (see top of page 86).
 
BR
/L-E
 

-----Original Message-----
From: Zongming.Zhou@commit.cn [mailto:Zongming.Zhou@commit.cn]
Sent: den 24 mars 2004 02:43
To: Lars-Erik Jonsson (LU/EAB)
Cc: rohc@ietf.org
Subject: RE: [rohc] Question of ROHC



Hi,L-E 

Thanks for your answer! I agree with u! 

I think in implementer guide, it should be made clearly that whether Outer IP static part preceeds Inner IP static part or not if inner IP exists 


Outer IP/AH/Inner IP/AH/ESP/UDP/RTP 

According to extension 3, Inner IP preceeds Outer IP, so I think in IR packets maybe the following format( Inner IP preceeds Outer IP) is better: 
  +---+---+---+---+---+---+---+---+ 
  |    Inner IP static part???    | 
 |    Outer IP static part???    |static chain 
 |        UDP static part        | 
 |        RTP static part        |variable length 
  +---+---+---+---+---+---+---+---+ 
 |      Inner IP dyn part???     | 
 |      Outer IP dyn part???     |static chain 
 |                               | 
  +---+---+---+---+---+---+---+---+ 


Outer IP static part preceeds Innter IP 

  Extension 3:

     0     1     2     3     4     5     6     7
  +-----+-----+-----+-----+-----+-----+-----+-----+
  |  1     1  |  S  |R-TS | Tsc |  I  | ip  | rtp |            (FLAGS)
  +-----+-----+-----+-----+-----+-----+-----+-----+
  |            Inner IP header flags        | ip2 |  if ip = 1
   ..... ..... ..... ..... ..... ..... ..... .....
  |            Outer IP header flags              |  if ip2 = 1
   ..... ..... ..... ..... ..... ..... ..... .....
  |                      SN                       |  if S = 1
   ..... ..... ..... ..... ..... ..... ..... .....
  /       TS (encoded as in section 4.5.6)        /  1-4 octets,
   ..... ..... ..... ..... ..... ..... ..... .....   if R-TS = 1
  |                                               |
  /            Inner IP header fields             /  variable,
  |                                               |  if ip = 1
   ..... ..... ..... ..... ..... ..... ..... .....
  |                     IP-ID                     |  2 octets, if I = 1
   ..... ..... ..... ..... ..... ..... ..... .....
  |                                               |
  /            Outer IP header fields             /  variable,
  |                                               |  if ip2 = 1
   ..... ..... ..... ..... ..... ..... ..... .....
  |                                               |
  /          RTP header flags and fields          /  variable,
  |                                               |  if rtp = 1
   ..... ..... ..... ..... ..... ..... ..... .....





This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


------_=_NextPart_001_01C41170.AF8A0072
Content-Type: text/html;
	charset="gb2312"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=gb2312">


<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=137522107-24032004>In the 
static and dynamic chains, the outer fields obviously preceeds the inner 
fields,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=137522107-24032004>as 
that is the order in which they appear in the original header(s). As the static 
and</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=137522107-24032004>dynamic chains are only implicitly defined as chains of 
fields from the original</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=137522107-24032004>header(s), there is not really any other way these can 
be ordered. When corresponding</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=137522107-24032004>fields 
are present in compressed headers or their extensions, the order 
and</SPAN></FONT><FONT face=Arial color=#0000ff size=2><SPAN 
class=137522107-24032004>&nbsp;encoding</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=137522107-24032004>of the 
fields are explicitly defined for each packet format, and as you have noted 
the</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=137522107-24032004>inner 
fields are put before the outer in extension 3. At this point in time, we can 
of</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=137522107-24032004>course 
</SPAN></FONT><FONT face=Arial color=#0000ff size=2><SPAN 
class=137522107-24032004>discuss why this is the case, but arguing that it 
should had been the other way</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=137522107-24032004>around 
does not help us much as we can not change the way it is defined (and 
it</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=137522107-24032004>is 
just a cosmetic issue anyway). I would </SPAN></FONT><FONT face=Arial 
color=#0000ff size=2><SPAN class=137522107-24032004>guess the reason the fields 
are put in this</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=137522107-24032004>order 
is to have the fields that are most </SPAN></FONT><FONT face=Arial color=#0000ff 
size=2><SPAN class=137522107-24032004>commonly present listed first, and "inner" 
is</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=137522107-24032004>defined as the fields corresponding to the fields of 
</SPAN></FONT><FONT face=Arial color=#0000ff size=2><SPAN 
class=137522107-24032004>one single IP header (see top of page 
86).</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=137522107-24032004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=137522107-24032004>BR</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=137522107-24032004>/L-E</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=137522107-24032004></SPAN></FONT>&nbsp;</DIV>
<BLOCKQUOTE 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Zongming.Zhou@commit.cn 
  [mailto:Zongming.Zhou@commit.cn]<BR><B>Sent:</B> den 24 mars 2004 
  02:43<BR><B>To:</B> Lars-Erik Jonsson (LU/EAB)<BR><B>Cc:</B> 
  rohc@ietf.org<BR><B>Subject:</B> RE: [rohc] Question of 
  ROHC<BR><BR></FONT></DIV><BR><FONT face=sans-serif size=2>Hi,L-E</FONT> 
  <BR><BR><FONT face=sans-serif size=2>Thanks for your answer! I agree with 
  u!</FONT> <BR><BR><FONT face=sans-serif size=2>I think in implementer guide, 
  it should be made clearly that </FONT><FONT face=sans-serif color=red 
  size=2>whether Outer IP static part preceeds Inner IP static</FONT><FONT 
  face=sans-serif size=2> part or not if inner IP exists</FONT> 
  <BR><BR><BR><FONT face=sans-serif size=2>Outer IP/AH/Inner 
  IP/AH/ESP/UDP/RTP</FONT> <BR><BR><FONT face=sans-serif size=2>According to 
  extension 3, Inner IP preceeds Outer IP, so I think in IR packets maybe the 
  following format( Inner IP preceeds Outer IP) is better:</FONT> <BR><FONT 
  face=sans-serif size=2>&nbsp; +---+---+---+---+---+---+---+---+</FONT><FONT 
  face=sans-serif size=3> </FONT><BR><FONT face=sans-serif size=2>&nbsp; | 
  &nbsp; &nbsp;</FONT><FONT face=sans-serif color=red size=2>Inner</FONT><FONT 
  face=sans-serif size=2> IP static part??? &nbsp; &nbsp;|</FONT><FONT 
  face=sans-serif size=3> </FONT><FONT face=sans-serif size=2><BR>&nbsp;| &nbsp; 
  &nbsp;</FONT><FONT face=sans-serif color=blue size=2>Outer</FONT><FONT 
  face=sans-serif size=2> IP static part??? &nbsp; &nbsp;|static 
  chain</FONT><FONT face=sans-serif size=3> </FONT><FONT face=sans-serif 
  size=2><BR>&nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;UDP static part &nbsp; &nbsp; 
  &nbsp; &nbsp;|</FONT><FONT face=sans-serif size=3> </FONT><FONT 
  face=sans-serif size=2><BR>&nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;RTP static part 
  &nbsp; &nbsp; &nbsp; &nbsp;|variable length</FONT><FONT face=sans-serif 
  size=3> </FONT><BR><FONT face=sans-serif size=2>&nbsp; 
  +---+---+---+---+---+---+---+---+</FONT><FONT face=sans-serif size=3> 
  </FONT><FONT face=sans-serif size=2><BR>&nbsp;| &nbsp; &nbsp; 
  &nbsp;</FONT><FONT face=sans-serif color=red size=2>Inner</FONT><FONT 
  face=sans-serif size=2> IP dyn part??? &nbsp; &nbsp; |</FONT><FONT 
  face=sans-serif size=3> </FONT><FONT face=sans-serif size=2><BR>&nbsp;| &nbsp; 
  &nbsp; &nbsp;</FONT><FONT face=sans-serif color=blue size=2>Outer</FONT><FONT 
  face=sans-serif size=2> IP dyn part??? &nbsp; &nbsp; |static chain</FONT><FONT 
  face=sans-serif size=3> </FONT><FONT face=sans-serif size=2><BR>&nbsp;| &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; |</FONT><FONT face=sans-serif size=3> </FONT><BR><FONT 
  face=sans-serif size=2>&nbsp; +---+---+---+---+---+---+---+---+</FONT><FONT 
  face=sans-serif size=3> </FONT><BR><BR><BR><FONT face=sans-serif size=2>Outer 
  IP static part preceeds Innter IP</FONT> <BR><FONT 
  size=3><TT><BR></TT></FONT><FONT color=red size=3><TT>&nbsp; Extension 
  3:</TT></FONT><FONT size=3><TT><BR><BR>&nbsp; &nbsp; &nbsp;0 &nbsp; &nbsp; 1 
  &nbsp; &nbsp; 2 &nbsp; &nbsp; 3 &nbsp; &nbsp; 4 &nbsp; &nbsp; 5 &nbsp; &nbsp; 
  6 &nbsp; &nbsp; 7<BR>&nbsp; 
  +-----+-----+-----+-----+-----+-----+-----+-----+<BR>&nbsp; | &nbsp;1 &nbsp; 
  &nbsp; 1 &nbsp;| &nbsp;S &nbsp;|R-TS | Tsc | &nbsp;I &nbsp;| ip &nbsp;| rtp | 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(FLAGS)<BR>&nbsp; 
  +-----+-----+-----+-----+-----+-----+-----+-----+<BR>&nbsp; | &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp;</TT></FONT><FONT color=red size=3><TT>Inner IP 
  header flags</TT></FONT><FONT size=3><TT> &nbsp; &nbsp; &nbsp; &nbsp;| ip2 | 
  &nbsp;if ip = 1<BR>&nbsp; &nbsp;..... ..... ..... ..... ..... ..... ..... 
  .....<BR>&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</TT></FONT><FONT 
  color=blue size=3><TT>Outer IP header flags</TT></FONT><FONT size=3><TT> 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;if ip2 = 1<BR>&nbsp; 
  &nbsp;..... ..... ..... ..... ..... ..... ..... .....<BR>&nbsp; | &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;SN &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | 
  &nbsp;if S = 1<BR>&nbsp; &nbsp;..... ..... ..... ..... ..... ..... ..... 
  .....<BR>&nbsp; / &nbsp; &nbsp; &nbsp; TS (encoded as in section 4.5.6) &nbsp; 
  &nbsp; &nbsp; &nbsp;/ &nbsp;1-4 octets,<BR>&nbsp; &nbsp;..... ..... ..... 
  ..... ..... ..... ..... ..... &nbsp; if R-TS = 1<BR>&nbsp; | &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  |<BR>&nbsp; / &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</TT></FONT><FONT 
  color=red size=3><TT>Inner IP header fields</TT></FONT><FONT size=3><TT> 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; / &nbsp;variable,<BR>&nbsp; | &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | 
  &nbsp;if ip = 1<BR>&nbsp; &nbsp;..... ..... ..... ..... ..... ..... ..... 
  .....<BR>&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; IP-ID &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; | &nbsp;2 octets, if I = 1<BR>&nbsp; &nbsp;..... ..... ..... 
  ..... ..... ..... ..... .....<BR>&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<BR>&nbsp; / &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; </TT></FONT><FONT color=blue size=3><TT>&nbsp;Outer IP 
  header fields</TT></FONT><FONT size=3><TT> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; / &nbsp;variable,<BR>&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;if ip2 = 1<BR>&nbsp; 
  &nbsp;..... ..... ..... ..... ..... ..... ..... .....<BR>&nbsp; | &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  |<BR>&nbsp; / &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;RTP header flags and fields 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;/ &nbsp;variable,<BR>&nbsp; | &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | 
  &nbsp;if rtp = 1<BR>&nbsp; &nbsp;..... ..... ..... ..... ..... ..... ..... 
  .....<BR></TT></FONT><BR><BR></BLOCKQUOTE><br>This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.<br><br>E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.<br></BODY></HTML>

------_=_NextPart_001_01C41170.AF8A0072--

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



From exim@www1.ietf.org  Wed Mar 24 04:10:36 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06979
	for <rohc-archive@odin.ietf.org>; Wed, 24 Mar 2004 04:10:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B64Ol-0002Hd-RU
	for rohc-archive@odin.ietf.org; Wed, 24 Mar 2004 04:10:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2O9A7gX008769
	for rohc-archive@odin.ietf.org; Wed, 24 Mar 2004 04:10:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B64Ok-0002HL-UG
	for rohc-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 04:10:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06953
	for <rohc-web-archive@ietf.org>; Wed, 24 Mar 2004 04:10:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B64Oi-0002WH-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 04:10:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B64Ni-0002ID-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 04:09:03 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B64Mh-00025O-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 04:07:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B64Mj-00023k-LO; Wed, 24 Mar 2004 04:08:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B64Lo-0001oO-VD
	for rohc@optimus.ietf.org; Wed, 24 Mar 2004 04:07:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06845
	for <rohc@ietf.org>; Wed, 24 Mar 2004 04:07:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B64Lm-0001sa-00
	for rohc@ietf.org; Wed, 24 Mar 2004 04:07:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B64Ko-0001gP-00
	for rohc@ietf.org; Wed, 24 Mar 2004 04:06:02 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B64Js-0001VB-00
	for rohc@ietf.org; Wed, 24 Mar 2004 04:05:04 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2O950qY024155
	for <rohc@ietf.org>; Wed, 24 Mar 2004 10:05:04 +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.0);
	 Wed, 24 Mar 2004 10:05:00 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <HQ463LAQ>; Wed, 24 Mar 2004 10:05:00 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E94E6@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'Pawel Szymanski'" <szym_paw@wp.pl>, rohc@ietf.org
Subject: RE: [rohc] Slope used to compress/decompress RTP Timestamp field
Date: Wed, 24 Mar 2004 10:04:55 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-2"
X-OriginalArrivalTime: 24 Mar 2004 09:05:00.0178 (UTC) FILETIME=[160E6F20:01C4117F]
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

Pawel and others,

As I was not deeply involved in designing the encoding parts of RFC 3095 I had
hoped someone else would answer this question, but since no one has responded
I thought I would have to take a look at it. After checking what 3095 actually
says, as well as looking for discussions on the mail list, my conclusion is that
here we really have some confusing text lines we will have to say something about.

What does 3095 say about slopes?
The word slope appears at 6 places in 3095, three in the R-mode logic and 3 in
the beginning of the packet format section. None of these provides any definitions
or descriptions in a normative way. Let's look at the text in 5.5.1.2:

   The compressor will transit to the SO state after it has determined
   the presence of a string (see section 2), while also being confident
   that the decompressor has the string parameters.  The confidence can
   be based on ACKs.  For example, in a typical case where the string
   pattern has the form of non-SN-field = SN * slope + offset, one ACK
   is enough if the slope has been previously established by the
   decompressor (i.e., only the new offset needs to be synchronized).
   Otherwise, two ACKs are required since the decompressor needs two
   headers to learn both the new slope and the new offset.  In the SO
   state, R-0* packets will be sent.

The first "slope" could be seen as just a constant in the informative
equation, and the second "slope" would then just describe this constant.
An example of such a non-SN-field would be TS with a slope TS_STRIDE.
So far, there is nothing that says anything about any implicitly established
slope values, but the third occurrence of "slope" in this text talks about
such implicit establishments of string parameters. However, this is the
ONLY place where the RFC talks about implicit establishments of slopes,
and I can not see how that could possibly be sufficient to imply principles
requiring a behaviour to be implemented that would obviously affect
interoperability. The only conclusion I can draw from this is that the
text is a rest that should had been rewritten when the 3095 specification
evolved.

The other 3 occurrences of "slope" (actually "default-slope") is on page 75,
where it defines default-slope(IP-ID offset)=0 [which is not even a parameter
to that encoding scheme], as well as default-slope(TS)=1 for scaled TS
encoding and  =value(TS_STRIDE) for "as-is encoding" [which comes as no
surprise as TS is scaled with TS_STRIDE]. 

There is no place in the RFC that normatively says a word about implicitly
updating the slope, so my conclusion is that there should be no such thing.
The mail list discussions indicates that there were proposals to have such
principles, but the discussions point in the direction of giving up these ideas.
http://www1.ietf.org/mail-archive/working-groups/rohc/old-archive/msg00953.html

I'll put this to my list of things to clarify in the next version of the impl. guide.

BR
/L-E



> -----Original Message-----
> From: rohc-admin@ietf.org [mailto:rohc-admin@ietf.org]On 
> Behalf Of Pawel Szymanski
> Sent: den 16 mars 2004 14:31
> To: rohc@ietf.org
> Subject: [rohc] Slope used to compress/decompress RTP Timestamp field
> 
> 
> Hi all,
> 
> I've seen in the ROHC mailing list archive a discussion about 
> using dynamic slope values by the compressor and decompressor 
> while decompressing RTP Timestamp field from OU-0 packets (refer 
> to mail: http://www.cdt.luth.se/rohc/msg00934.html). The idea is 
> that decompressor starts with default_slope value and calculates 
> new slope value at each arrival of a packet containing TS field.
> 
> The mechanism is not described in the standard. Only 
> default_slope values are defined. Should compressor and 
> decompressor use other slope values than the default_slope when 
> they process UO-0 packets ? 
> 
> Regards
> 
> Pawel Szymanski

This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Wed Mar 24 04:23:34 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07853
	for <rohc-archive@odin.ietf.org>; Wed, 24 Mar 2004 04:23:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B64bK-0003ub-Fh
	for rohc-archive@odin.ietf.org; Wed, 24 Mar 2004 04:23:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2O9N6GK015031
	for rohc-archive@odin.ietf.org; Wed, 24 Mar 2004 04:23:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B64bK-0003uM-9l
	for rohc-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 04:23:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07796
	for <rohc-web-archive@ietf.org>; Wed, 24 Mar 2004 04:23:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B64bH-0005Xf-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 04:23:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B64aJ-0005J9-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 04:22:04 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B64ZI-00055f-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 04:21:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B64ZK-0003iU-5v; Wed, 24 Mar 2004 04:21:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B64YT-0003Ic-Eu
	for rohc@optimus.ietf.org; Wed, 24 Mar 2004 04:20:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07633
	for <rohc@ietf.org>; Wed, 24 Mar 2004 04:20:07 -0500 (EST)
From: jbhalla@hss.hns.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B64YQ-0004ti-00
	for rohc@ietf.org; Wed, 24 Mar 2004 04:20:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B64XW-0004hq-00
	for rohc@ietf.org; Wed, 24 Mar 2004 04:19:11 -0500
Received: from 210-210-93-102.lan.sify.net ([210.210.93.102] helo=hss.hns.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B64X5-0004Vv-00; Wed, 24 Mar 2004 04:18:43 -0500
Received: from pragati.hss.hns.com (pragati.hss.hns.com [139.85.249.33])
	by hss.hns.com (8.11.6/8.11.2) with ESMTP id i2O9HnD11588;
	Wed, 24 Mar 2004 14:47:49 +0530
In-Reply-To: <A943FD84BD9ED41193460008C7918050072E94E2@ESEALNT419.al.sw.ericsson.se>
To: rohc@ietf.org, rohc-admin@ietf.org
X-Mailer: Lotus Notes Release 6.0.1 February 07, 2003
Message-ID: <OF1B47A8C9.382B3C87-ON65256E61.0032DB2A-65256E61.003328DB@hss.hns.com>
Date: Wed, 24 Mar 2004 14:48:37 +0530
X-MIMETrack: Serialize by Router on Pragati/BLR/HSS(Release 6.5|September 18, 2003) at
 03/24/2004 02:48:39 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Subject: [rohc] Deflate Implementation
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60





Hi all,
      Can anyone tell me if there are any open-source implementations
      available for "Deflate" compression algorithm.

thanks and regards
Jyoti


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



From exim@www1.ietf.org  Wed Mar 24 05:46:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12572
	for <rohc-archive@odin.ietf.org>; Wed, 24 Mar 2004 05:46:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B65td-00045Q-C2
	for rohc-archive@odin.ietf.org; Wed, 24 Mar 2004 05:46:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2OAk5Yq015704
	for rohc-archive@odin.ietf.org; Wed, 24 Mar 2004 05:46:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B65td-00045D-7i
	for rohc-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 05:46:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12546
	for <rohc-web-archive@ietf.org>; Wed, 24 Mar 2004 05:46:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B65tZ-0001Oo-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 05:46:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B65sa-0001B7-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 05:45:01 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B65rb-0000yN-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 05:43:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B65rd-0003vq-LF; Wed, 24 Mar 2004 05:44:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B65qm-0003p4-9j
	for rohc@optimus.ietf.org; Wed, 24 Mar 2004 05:43:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12464
	for <rohc@ietf.org>; Wed, 24 Mar 2004 05:43:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B65qi-0000ms-00
	for rohc@ietf.org; Wed, 24 Mar 2004 05:43:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B65pq-0000ay-00
	for rohc@ietf.org; Wed, 24 Mar 2004 05:42:10 -0500
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B65pU-0000OT-00
	for rohc@ietf.org; Wed, 24 Mar 2004 05:41:48 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <1ZGMSWFS>; Wed, 24 Mar 2004 10:41:17 -0000
Message-ID: <EA943CD30BCB104E9D38F5B5DC2D9A70A1AED7@rsys004a.roke.co.uk>
From: "West, Mark" <mark.a.west@roke.co.uk>
To: "Rohc (E-mail)" <rohc@ietf.org>
Date: Wed, 24 Mar 2004 10:41:25 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [rohc] TCP packet formats
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


Hi all,

Thought I'd try something a bit radical and forward looking...  So, amongst
the questions on RFC 3095 & SigComp, here's something a bit different!

I'm currently revising and refining the packet formats for TCP header
compression, and we'd quite like this set to be very close to, if not
actually, the 'right' answer.

In terms of general structure, I don't see any real problems, but in terms
of targetting the *compressed* packet formats, it's worth polling for
opinions.  So, come on, don't be shy...

The issue is really this: what environment are we aiming for?

TCP is a complex protocol and there are a number of variables that affect
compression including end-system configuration; end-to-end latency; link
bandwidth; and error rates.  I'm trying to run a few simple experiments to
assess how sensitive the compression might be to changes.  

At the end of the day, though, we are going to have to pick a 'sweet-spot'
expectation.  Let me stress that this decision will *not* cause the header
compression to 'break', under any circumstances.  However, using it on a
link with wildly different characterstics from those chosen will almost
certainly reduce the compression efficiency.

My gut feel is that we are looking at systems that are configured
appropriately for links of up to a small number of Mbit/s; with up to (say)
200-300ms latency; and a modest error rate (2-3%)?

I will say again: this is *not* about constraining TCP compression to work
only on links with these characteristics: it *is* about trying to dimension
the expected changes that the compressed packet formats should deal with
most efficiently.

Any thoughts..?

Cheers,

Mark.

-- 
Mark A. West, Senior Consultant Engineer
Roke Manor Research Ltd., Romsey, Hants.  SO51 0ZN
Phone +44 (0)1794 833311   Fax  +44 (0)1794 833433
 

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



From exim@www1.ietf.org  Wed Mar 24 05:48:33 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12703
	for <rohc-archive@odin.ietf.org>; Wed, 24 Mar 2004 05:48:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B65vZ-0004JG-Qf
	for rohc-archive@odin.ietf.org; Wed, 24 Mar 2004 05:48:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2OAm5x2016560
	for rohc-archive@odin.ietf.org; Wed, 24 Mar 2004 05:48:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B65vZ-0004J1-M6
	for rohc-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 05:48:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12655
	for <rohc-web-archive@ietf.org>; Wed, 24 Mar 2004 05:48:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B65vV-0001rQ-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 05:48:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B65uV-0001cc-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 05:47:00 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B65tW-0001N3-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 05:45:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B65tZ-00042o-9u; Wed, 24 Mar 2004 05:46:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B65sf-0003zJ-Ep
	for rohc@optimus.ietf.org; Wed, 24 Mar 2004 05:45:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12520
	for <rohc@ietf.org>; Wed, 24 Mar 2004 05:45:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B65sb-0001BF-00
	for rohc@ietf.org; Wed, 24 Mar 2004 05:45:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B65rc-0000yV-00
	for rohc@ietf.org; Wed, 24 Mar 2004 05:44:00 -0500
Received: from rsys002a.roke.co.uk ([193.118.192.251])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B65qe-0000bC-00
	for rohc@ietf.org; Wed, 24 Mar 2004 05:43:01 -0500
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <1ZGNFKQQ>; Wed, 24 Mar 2004 10:42:31 -0000
Message-ID: <EA943CD30BCB104E9D38F5B5DC2D9A70A1AED8@rsys004a.roke.co.uk>
From: "West, Mark" <mark.a.west@roke.co.uk>
To: "'jbhalla@hss.hns.com'" <jbhalla@hss.hns.com>, rohc@ietf.org
Subject: RE: [rohc] Deflate Implementation
Date: Wed, 24 Mar 2004 10:42:42 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


http://www.gzip.org/zlib/?

Mark.


> -----Original Message-----
> From: jbhalla@hss.hns.com [mailto:jbhalla@hss.hns.com]
> Sent: 24 March 2004 09:19
> To: rohc@ietf.org; rohc-admin@ietf.org
> Subject: [rohc] Deflate Implementation
> 
> 
> 
> 
> 
> 
> Hi all,
>       Can anyone tell me if there are any open-source implementations
>       available for "Deflate" compression algorithm.
> 
> thanks and regards
> Jyoti
> 
> 
> _______________________________________________
> 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 exim@www1.ietf.org  Wed Mar 24 08:08:05 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19911
	for <rohc-archive@odin.ietf.org>; Wed, 24 Mar 2004 08:08:05 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B686a-00018m-Ab
	for rohc-archive@odin.ietf.org; Wed, 24 Mar 2004 08:07:36 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2OD7adq004374
	for rohc-archive@odin.ietf.org; Wed, 24 Mar 2004 08:07:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B686a-00018T-65
	for rohc-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 08:07:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19908
	for <rohc-web-archive@ietf.org>; Wed, 24 Mar 2004 08:07:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B686Z-0002JF-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 08:07:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B685e-000254-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 08:06:39 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6853-0001pW-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 08:06:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6852-0000s4-UX; Wed, 24 Mar 2004 08:06:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B684Y-0000qH-Rf
	for rohc@optimus.ietf.org; Wed, 24 Mar 2004 08:05:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19833
	for <rohc@ietf.org>; Wed, 24 Mar 2004 08:05:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B684X-0001oF-00
	for rohc@ietf.org; Wed, 24 Mar 2004 08:05:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B683T-0001a9-00
	for rohc@ietf.org; Wed, 24 Mar 2004 08:04:23 -0500
Received: from rsys002a.roke.co.uk ([193.118.192.251])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B682d-00019H-00
	for rohc@ietf.org; Wed, 24 Mar 2004 08:03:31 -0500
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <1ZGNFKXD>; Wed, 24 Mar 2004 13:02:50 -0000
Message-ID: <EA943CD30BCB104E9D38F5B5DC2D9A70A1AED9@rsys004a.roke.co.uk>
From: "West, Mark" <mark.a.west@roke.co.uk>
To: "'Green, David B RDECOM CERDEC STCD SRI'" <Dave.B.Green@us.army.mil>,
        "'rohc@ietf.org'" <rohc@ietf.org>
Subject: RE: [rohc] Multpoint ROHC for MANET
Date: Wed, 24 Mar 2004 13:02:55 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


ROHC in unidirectional mode is the most obvious starting point.  Of course, one of the curiosities of ROHC is that U-mode does allow the use of positive ACKs; however for this application I suspect that negative ACKs would be more useful...

The point-to-multipoint (broadcast) case is considered within ROHC.  The more fluid manet environment (+ multiple senders / receivers) would probably raise some additional things to consider.

One interesting issue might be the management of CID spaces: each sender (point-to-point; point-to-multipoint) assumes that it has complete control of the CID space on the remote decompressor(s).  This still works if you move to a 'mesh' environment, but means that a node needs an instance of ROHC for each sender that it is listening to.

Hmmmm... it's certainly a more interesting 'ROHC over foo' case than where foo==PPP..!

Cheers,

Mark.


> -----Original Message-----
> From: Lars-Erik Jonsson (LU/EAB) 
> [mailto:lars-erik.jonsson@ericsson.com]
> Sent: 22 March 2004 08:24
> To: 'Green, David B RDECOM CERDEC STCD SRI'; 'rohc@ietf.org'
> Subject: RE: [rohc] Multpoint ROHC for MANET
> 
> 
> David,
> 
> Would it be appropriate to use ROHC in unidirectional mode? The
> compression scheme would then not depend on any feeback, and the
> number of recipients would thus not affect the compression 
> operation. A mapping (ROHC over xxxxx) would of course still
> have to be defined.
> 
> /L-E
> 
> > -----Original Message-----
> > From: rohc-admin@ietf.org [mailto:rohc-admin@ietf.org]On Behalf Of
> > Green, David B RDECOM CERDEC STCD SRI
> > Sent: den 18 mars 2004 21:51
> > To: 'rohc@ietf.org'
> > Subject: [rohc] Multpoint ROHC for MANET
> > 
> > 
> > Has anyone in the group worked on a schema for point to 
> > multipoint robust
> > header compression 
> > suitable for broadcast and multicast links in MANETs? The 
> > base spec for ROHC
> > only seems to consider point to point links for cellular 
> systems. I'm
> > normally in the MANET 
> > and IPv6 Ops groups but recently became very interested in 
> > ROHC as we see
> > ROHC as an enabling 
> > technolgy to get IPv6 working on a MANET radio system we are 
> > helping to
> > develop.
> > The protocol would need to be able to discover multiple 
> > neighbors, check to
> > see if they
> > are the recipients of multast or broadcast group messages, establish
> > compression contexts 
> > with them, have a mechanism to prevent collisions on any 
> > bi-directional
> > replies, and probably
> > several more problems I haven't thought of.
> > 
> > I'm working on a problem statement for the work now, so 
> > anyone interested
> > please let me know.
> > 
> > David B. Green
> > SRI International
> > desk (732) 532-6715
> > cell (732) 693-6500
> > 
> > 
> > 
> > _______________________________________________
> > Rohc mailing list
> > Rohc@ietf.org
> > https://www1.ietf.org/mailman/listinfo/rohc
> > 
> 
> This communication is confidential and intended solely for 
> the addressee(s). Any unauthorized review, use, disclosure or 
> distribution is prohibited. If you believe this message has 
> been sent to you in error, please notify the sender by 
> replying to this transmission and delete the message without 
> disclosing it. Thank you.
> 
> E-mail including attachments is susceptible to data 
> corruption, interruption, unauthorized amendment, tampering 
> and viruses, and we only send and receive e-mails on the 
> basis that we are not liable for any such corruption, 
> interception, amendment, tampering or viruses or any 
> consequences thereof.
> 
> 
> _______________________________________________
> 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 exim@www1.ietf.org  Wed Mar 24 15:57:04 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20833
	for <rohc-archive@odin.ietf.org>; Wed, 24 Mar 2004 15:57:04 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6FQR-0006Ab-27
	for rohc-archive@odin.ietf.org; Wed, 24 Mar 2004 15:56:35 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2OKuZ5W023713
	for rohc-archive@odin.ietf.org; Wed, 24 Mar 2004 15:56:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6FQQ-0006AL-SK
	for rohc-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 15:56:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20771
	for <rohc-web-archive@ietf.org>; Wed, 24 Mar 2004 15:56:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6FQP-0007kr-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 15:56:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6FPR-0007bc-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 15:55:35 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6FOS-0007UW-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 15:54:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6FOR-0005xP-85; Wed, 24 Mar 2004 15:54:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6FNd-0005wB-AE
	for rohc@optimus.ietf.org; Wed, 24 Mar 2004 15:53:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20590
	for <rohc@ietf.org>; Wed, 24 Mar 2004 15:53:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6FNb-0007Nj-00
	for rohc@ietf.org; Wed, 24 Mar 2004 15:53:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6FMY-0007Gy-00
	for rohc@ietf.org; Wed, 24 Mar 2004 15:52:37 -0500
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6FLj-00078d-00
	for rohc@ietf.org; Wed, 24 Mar 2004 15:51:43 -0500
Received: from courrier.rennes.enst-bretagne.fr (f1-clust.rennes.enst-bretagne.fr [193.52.74.16])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with ESMTP id i2OKp8v10667;
	Wed, 24 Mar 2004 21:51:08 +0100
Received: from pcrsm7 ([193.52.74.238])
	by courrier.rennes.enst-bretagne.fr (8.12.11/8.12.11/2004.01.01) with SMTP id i2OKp8vr012957;
	Wed, 24 Mar 2004 21:51:08 +0100 (MET)
Message-ID: <00b901c411e1$bb9f4e70$ee4a34c1@rennes.enstbretagne.fr>
From: "kamal deep singh" <kd.singh@enst-bretagne.fr>
To: "Lars-Erik Jonsson \(LU/EAB\)" <lars-erik.jonsson@ericsson.com>,
        "'Pawel Szymanski'" <szym_paw@wp.pl>, <rohc@ietf.org>
References: <A943FD84BD9ED41193460008C7918050072E94E6@ESEALNT419.al.sw.ericsson.se>
Subject: Re: [rohc] Slope used to compress/decompress RTP Timestamp field
Date: Wed, 24 Mar 2004 21:51:08 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,


I find the meaning of "slope" to be implicitly given in the RFC. And I
believe it because of the following:

1) If we stick to the equation
SN_Non_field = SN*slope + offset given in RFC 3095.
which is another form of SN_Non_field = SN_Non_field_ref + (SN -
SN_ref)slope.
Then one of the SN_Non_field will also be TS_SCALED and will also have a
slope.
And significance of that I try to show later.

2) Packets of FO state are said to update all parameters of SN functions.
And slope is also a part of any SN function. so, it is also implicitly
stated to be updated.



I understand the meaning of the slope to be as follows:
( please correct me if something is wrong?)

TS can be perfectly calculated at decompressor given TS_SCALED (and ofcourse
TS_STRIDE, TS_OFFSET that are constant most of time)

Very ideally TS_SCALED will increase like 1, 2, 3, 4, 5 with  SN
and can be said to have slope = 1. (as TS_SCALED = 1*SN + offset).
So here will be no need of sending TS_SCALED bits if slope = 1 is
established in decompressor.

But, in most of the cases TS_SCALED will show behaviour like

1, 1 , 1, 1, 2, 2, 2, 2, 2, 2, 2, 3, 4, 5 in case of video.

1, 2, 3, 4, 6, 7, 7, 8, 9, 10  possibly in case of audio

in "above" case of video slope will be 0 most of the time and 1 sometimes.
And in "above" case of audio slope will be 1 most of the time for audio.

so, once this slope is established by L or ACK. There will be no need to
send TS_SCALED field
and UO_0 (or other depending on  behaviour of other fields)packets can be
sent until there is a change.
(Above also fits when TS is not scaled because then slope will just get
multiplied by TS_STRIDE)

 Need of this slope is that without it I do not find a way in which we can
send UO_0 packets (except when there is a long chain of TS  =  constant,  N
number of times(N being the width of sliding window). Except for this case
which is unikely(even in video!) with a normal N lets say = 14,   more than
0 bits of TS_SCALED will always be required to be sent. This is because if
TS_SCALED is encoded by W_LSB then, k (no of bits required to send according
to W_LSB) will always be >= 1 except when all values of TS_SCALED or TS are
same in the window.

And hence in this case(ofcourse I feel that choosing lesser values of N will
reduce robustness)
, according to RFC it will be impossible to send UO_0 packets!!
since they do no contain TS_SCALED bits.


Still I feel that sections on slope are confusing in the RFC and will lead
to problems in interoperability.
But, I also feel that neglecting it will reduce compression efficiency.

regards,
kamal


----- Original Message -----
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'Pawel Szymanski'" <szym_paw@wp.pl>; <rohc@ietf.org>
Sent: Wednesday, March 24, 2004 10:04 AM
Subject: RE: [rohc] Slope used to compress/decompress RTP Timestamp field


> Pawel and others,
>
> As I was not deeply involved in designing the encoding parts of RFC 3095 I
had
> hoped someone else would answer this question, but since no one has
responded
> I thought I would have to take a look at it. After checking what 3095
actually
> says, as well as looking for discussions on the mail list, my conclusion
is that
> here we really have some confusing text lines we will have to say
something about.
>
> What does 3095 say about slopes?
> The word slope appears at 6 places in 3095, three in the R-mode logic and
3 in
> the beginning of the packet format section. None of these provides any
definitions
> or descriptions in a normative way. Let's look at the text in 5.5.1.2:
>
>    The compressor will transit to the SO state after it has determined
>    the presence of a string (see section 2), while also being confident
>    that the decompressor has the string parameters.  The confidence can
>    be based on ACKs.  For example, in a typical case where the string
>    pattern has the form of non-SN-field = SN * slope + offset, one ACK
>    is enough if the slope has been previously established by the
>    decompressor (i.e., only the new offset needs to be synchronized).
>    Otherwise, two ACKs are required since the decompressor needs two
>    headers to learn both the new slope and the new offset.  In the SO
>    state, R-0* packets will be sent.
>
> The first "slope" could be seen as just a constant in the informative
> equation, and the second "slope" would then just describe this constant.
> An example of such a non-SN-field would be TS with a slope TS_STRIDE.
> So far, there is nothing that says anything about any implicitly
established
> slope values, but the third occurrence of "slope" in this text talks about
> such implicit establishments of string parameters. However, this is the
> ONLY place where the RFC talks about implicit establishments of slopes,
> and I can not see how that could possibly be sufficient to imply
principles
> requiring a behaviour to be implemented that would obviously affect
> interoperability. The only conclusion I can draw from this is that the
> text is a rest that should had been rewritten when the 3095 specification
> evolved.
>
> The other 3 occurrences of "slope" (actually "default-slope") is on page
75,
> where it defines default-slope(IP-ID offset)=0 [which is not even a
parameter
> to that encoding scheme], as well as default-slope(TS)=1 for scaled TS
> encoding and  =value(TS_STRIDE) for "as-is encoding" [which comes as no
> surprise as TS is scaled with TS_STRIDE].
>
> There is no place in the RFC that normatively says a word about implicitly
> updating the slope, so my conclusion is that there should be no such
thing.
> The mail list discussions indicates that there were proposals to have such
> principles, but the discussions point in the direction of giving up these
ideas.
>
http://www1.ietf.org/mail-archive/working-groups/rohc/old-archive/msg00953.h
tml
>
> I'll put this to my list of things to clarify in the next version of the
impl. guide.
>
> BR
> /L-E
>
>
>
> > -----Original Message-----
> > From: rohc-admin@ietf.org [mailto:rohc-admin@ietf.org]On
> > Behalf Of Pawel Szymanski
> > Sent: den 16 mars 2004 14:31
> > To: rohc@ietf.org
> > Subject: [rohc] Slope used to compress/decompress RTP Timestamp field
> >
> >
> > Hi all,
> >
> > I've seen in the ROHC mailing list archive a discussion about
> > using dynamic slope values by the compressor and decompressor
> > while decompressing RTP Timestamp field from OU-0 packets (refer
> > to mail: http://www.cdt.luth.se/rohc/msg00934.html). The idea is
> > that decompressor starts with default_slope value and calculates
> > new slope value at each arrival of a packet containing TS field.
> >
> > The mechanism is not described in the standard. Only
> > default_slope values are defined. Should compressor and
> > decompressor use other slope values than the default_slope when
> > they process UO-0 packets ?
> >
> > Regards
> >
> > Pawel Szymanski
>
> This communication is confidential and intended solely for the
addressee(s). Any unauthorized review, use, disclosure or distribution is
prohibited. If you believe this message has been sent to you in error,
please notify the sender by replying to this transmission and delete the
message without disclosing it. Thank you.
>
> E-mail including attachments is susceptible to data corruption,
interruption, unauthorized amendment, tampering and viruses, and we only
send and receive e-mails on the basis that we are not liable for any such
corruption, interception, amendment, tampering or viruses or any
consequences thereof.
>
>
> _______________________________________________
> 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 exim@www1.ietf.org  Wed Mar 24 16:09:16 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21525
	for <rohc-archive@odin.ietf.org>; Wed, 24 Mar 2004 16:09:16 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Fc8-00071m-0D
	for rohc-archive@odin.ietf.org; Wed, 24 Mar 2004 16:08:47 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2OL8dEQ027011
	for rohc-archive@odin.ietf.org; Wed, 24 Mar 2004 16:08:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Fc7-00071a-Rx
	for rohc-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 16:08:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21510
	for <rohc-web-archive@ietf.org>; Wed, 24 Mar 2004 16:08:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Fc6-000179-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 16:08:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6FbC-000123-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 16:07:43 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6FaV-0000wK-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 16:06:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6FaW-0006Vo-HV; Wed, 24 Mar 2004 16:07:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Fa5-0006Um-Mk
	for rohc@optimus.ietf.org; Wed, 24 Mar 2004 16:06:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21418
	for <rohc@ietf.org>; Wed, 24 Mar 2004 16:06:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Fa4-0000uk-00
	for rohc@ietf.org; Wed, 24 Mar 2004 16:06:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6FZH-0000qp-00
	for rohc@ietf.org; Wed, 24 Mar 2004 16:05:43 -0500
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6FYT-0000j6-00
	for rohc@ietf.org; Wed, 24 Mar 2004 16:04:53 -0500
Received: from courrier.rennes.enst-bretagne.fr (f1-clust.rennes.enst-bretagne.fr [193.52.74.16])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with ESMTP id i2OL42v11740;
	Wed, 24 Mar 2004 22:04:12 +0100
Received: from pcrsm7 ([193.52.74.238])
	by courrier.rennes.enst-bretagne.fr (8.12.11/8.12.11/2004.01.01) with SMTP id i2OL3w9T013333;
	Wed, 24 Mar 2004 22:03:58 +0100 (MET)
Message-ID: <00fe01c411e3$899af9e0$ee4a34c1@rennes.enstbretagne.fr>
From: "kamal deep singh" <kd.singh@enst-bretagne.fr>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
Cc: <rohc@ietf.org>, "Jagan S" <Jagan.S@lntinfotech.com>
References: <OF85843B27.1BB82406-ON65256E56.001D6126@lntinfotech.com> <03ba01c40a80$62eb83b0$ee4a34c1@rennes.enstbretagne.fr> <4056E6A6.3070705@ericsson.com>
Subject: Re: [rohc] ROHC: Header parsing
Date: Wed, 24 Mar 2004 22:03:58 +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.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Magnus,

I meant to use mostly the SN behaviour to predict RTP packets as it is the
base of ROHC
compression.

But, I also find the compression ratio to be "most reliable" way of
detecting wrong choice of RTP profile and switching to other ROHC profiles.

Though I feel compression ratio method to be little inefficient if we
consider costly bandwidth.


regards,
Kamal


> Hi Kamal,
>
> I think some of your checks are oversimplifying the behaviour of RTP.
> There are many users of RTP and not all are as well behaved as audio.
>
> First, the TS behaviour you are describing is present for certain media
> types, but not all, one media type that will definitely not follow that
> usage and still be valid RTP usage is text/t140, which encodes
> transmission time for when the packet is sent. As this is normally for
> each keystroke, I can guarantee you that a valid TS_stride will be quite
> impossible to get.
>
> Secondly, the restriction of using RTP on even ports has also been
> removed, and is now only a recommendation. The reason for removing this
> was simply to allow RTP to work across NATs.
>
> Also the Sequence number check is not 100% as network reorder can cause
> this to jump. There are also certain users of RTP that are a bit
> misbehaving and sends RTP packets with out of order RTP sequence
> numbers. If one needs to take into consideration of misbehaving hosts is
> of course a question, however the network reorder is of course a valid
> reason for small scale jumping around of the RTP sequence number.
>
> So in conclusion, I would only recommend that one uses static fields,
> like version number, and the over several packet compression ratio as
> better measurements.
>
> Cheers
>
> Magnus
>
> kamal deep singh wrote:
>
> > hi,
> >
> > We can discuss that.
> >
> > I use RTP version field and also I look at the values
> > where SN field is supposed to be there. If the values are showing
> > sequential
> > behaviour then it should be SN and header should be RTP.
> >
> > This can be extended further to check TS. If TS is showing the expected
> > behaviour of
> > TS = n*TS_STRIDE + TS_OFFSET (n is an integer and all others constant)
> > then
> > it should be TS.
> >
> > Also RTP uses even UDP port numbers according to RFC.
> >
> > If anybody has another better idea? please tell me.
> >
> > regards,
> > Kamal
> >
> > ----- Original Message -----
> > From: "Jagan S" <Jagan.S@lntinfotech.com>
> > To: <rohc@ietf.org>
> > Sent: Saturday, March 13, 2004 6:27 AM
> > Subject: [rohc] ROHC: Header parsing
> >
> >
> >
> >>Hi,
> >>
> >>3095 specifies context identification at compressor  by parsing
> >
> > RTP/UDP/IP
> >
> >>header fields.
> >>
> >>Yes. We can identify IP header by analyzing :' Version' / 'Length'
> >
> > fields
> >
> >>of IP header.
> >>UDP header by analyzing: 'protocol type' field from IP header
> >>
> >>My question is about: How to identify the presence of RTP header ?
> >>
> >>
> >>Thanks in advance
> >>- Jagan
> >>
> >
> > ........................................................................
> > ....
> > ........................................................................
> > ....
> > .....................................................
> >
> >>
> >>
> >>
> >>_______________________________________________
> >>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
> >
>
> --
>
> Magnus Westerlund
>
> Multimedia Technologies, Ericsson Research EAB/TVA/A
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>
>
> This communication is confidential and intended solely for the
addressee(s). Any unauthorized review, use, disclosure or distribution is
prohibited. If you believe this message has been sent to you in error,
please notify the sender by replying to this transmission and delete the
message without disclosing it. Thank you.
>
> E-mail including attachments is susceptible to data corruption,
interruption, unauthorized amendment, tampering and viruses, and we only
send and receive e-mails on the basis that we are not liable for any such
corruption, interception, amendment, tampering or viruses or any
consequences thereof.
>
>
> _______________________________________________
> 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 exim@www1.ietf.org  Wed Mar 24 20:10:06 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04087
	for <rohc-archive@odin.ietf.org>; Wed, 24 Mar 2004 20:10:06 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6JNJ-0005bm-Gn
	for rohc-archive@odin.ietf.org; Wed, 24 Mar 2004 20:09:37 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2P19b7M021552
	for rohc-archive@odin.ietf.org; Wed, 24 Mar 2004 20:09:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6JNJ-0005bX-7F
	for rohc-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 20:09:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04032
	for <rohc-web-archive@ietf.org>; Wed, 24 Mar 2004 20:09:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6JNH-0002OX-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 20:09:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6JMM-0002L2-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 20:08:38 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6JLj-0002Hb-00
	for rohc-web-archive@ietf.org; Wed, 24 Mar 2004 20:07:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6JLk-0005Uq-QP; Wed, 24 Mar 2004 20:08:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6JKL-0005ED-0y
	for rohc@optimus.ietf.org; Wed, 24 Mar 2004 20:06:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03959
	for <rohc@ietf.org>; Wed, 24 Mar 2004 20:06:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6JKJ-0002D3-00
	for rohc@ietf.org; Wed, 24 Mar 2004 20:06:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6JJW-0002AQ-00
	for rohc@ietf.org; Wed, 24 Mar 2004 20:05:42 -0500
Received: from [216.90.186.146] (helo=mail.ipnetfusion.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6JJ3-0001xq-00
	for rohc@ietf.org; Wed, 24 Mar 2004 20:05:13 -0500
Received: from ipnetfusion.com (proxy.ipnetfusion.com [216.90.186.147])
	(authenticated)
	by mail.ipnetfusion.com (8.11.6/8.11.6) with ESMTP id i2P136G19205
	for <rohc@ietf.org>; Wed, 24 Mar 2004 19:03:06 -0600
Message-ID: <4062301B.4090108@ipnetfusion.com>
Date: Wed, 24 Mar 2004 19:04:27 -0600
From: Simran Suri <ssuri@ipnetfusion.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: rohc@ietf.org
References: <OF85843B27.1BB82406-ON65256E56.001D6126@lntinfotech.com> <03ba01c40a80$62eb83b0$ee4a34c1@rennes.enstbretagne.fr> <4056E6A6.3070705@ericsson.com> <00fe01c411e3$899af9e0$ee4a34c1@rennes.enstbretagne.fr>
In-Reply-To: <00fe01c411e3$899af9e0$ee4a34c1@rennes.enstbretagne.fr>
Content-Type: multipart/alternative;
 boundary="------------050305020805000700060804"
Subject: [rohc] Record Marking in SigComp
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE,
	HTML_TITLE_EMPTY autolearn=no version=2.60

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

Hi All,

I had a basic doubt regarding record marking (RFC 3320- Section 4.2.2) 
by SigComp when stream-based transport protocols like TCP are used. This 
section describes the decompression dispatcher behavior upon 
encountering OxFF in the compressed data stream, but it does not say 
anything about the behavior of the compression dispatcher. What action 
does the compression dispatcher take when say it encounters OxFF in the 
compressed data stream? How does it "modify the message" before sending 
it out on the wire so that the remote decompression dispatcher 
understands it (besides adding a '0xFF FF' to signal the end of the 
message)?

Thanks,
Simran

--------------050305020805000700060804
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000099">
<font size="-1" face="Verdana">Hi All,<br>
<br>
I had a basic doubt regarding record marking (RFC 3320- Section 4.2.2)
by SigComp when stream-based transport protocols like TCP are used.
This section describes the decompression dispatcher behavior upon
encountering OxFF in the compressed data stream, but it does not say
anything about the behavior of the compression dispatcher. What action
does the compression dispatcher take when say it encounters </font><font
 size="-1" face="Verdana">OxFF in the compressed data stream? How does
it "modify the message" before sending it out on the wire so that the
remote de</font><font size="-1" face="Verdana">compression dispatcher
understands it (besides adding a '0xFF FF' to signal the end of the
message)?</font><br>
<font size="-1" face="Verdana"><br>
Thanks,<br>
Simran<br>
</font>
</body>
</html>

--------------050305020805000700060804--

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



From exim@www1.ietf.org  Thu Mar 25 02:32:19 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06977
	for <rohc-archive@odin.ietf.org>; Thu, 25 Mar 2004 02:32:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6PLD-0004Vm-Kd
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 02:31:51 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2P7VpfB017342
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 02:31:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6PLD-0004Vc-CJ
	for rohc-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 02:31:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06951
	for <rohc-web-archive@ietf.org>; Thu, 25 Mar 2004 02:31:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6PL9-0007kJ-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 02:31:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6PKE-0007f4-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 02:30:51 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6PJR-0007R2-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 02:30:01 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B6PJT-00078j-9n
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 02:30:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6PJS-0004KF-2A; Thu, 25 Mar 2004 02:30:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6PIs-0004HA-Aq
	for rohc@optimus.ietf.org; Thu, 25 Mar 2004 02:29:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06786
	for <rohc@ietf.org>; Thu, 25 Mar 2004 02:29:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6PIo-0007JT-00
	for rohc@ietf.org; Thu, 25 Mar 2004 02:29:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6PHh-00074G-00
	for rohc@ietf.org; Thu, 25 Mar 2004 02:28:13 -0500
Received: from imh.informatik.uni-bremen.de ([134.102.224.4] helo=informatik.uni-bremen.de)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6PFT-0006aY-00
	for rohc@ietf.org; Thu, 25 Mar 2004 02:25:55 -0500
Received: from [IPv6:::1] (imh.informatik.uni-bremen.de [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id i2P7PoU5010418;
	Thu, 25 Mar 2004 08:25:51 +0100 (MET)
In-Reply-To: <4062301B.4090108@ipnetfusion.com>
References: <OF85843B27.1BB82406-ON65256E56.001D6126@lntinfotech.com> <03ba01c40a80$62eb83b0$ee4a34c1@rennes.enstbretagne.fr> <4056E6A6.3070705@ericsson.com> <00fe01c411e3$899af9e0$ee4a34c1@rennes.enstbretagne.fr> <4062301B.4090108@ipnetfusion.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <A41CDDD4-7E2D-11D8-9A3A-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, rohc@ietf.org
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] Record Marking in SigComp
Date: Thu, 25 Mar 2004 08:25:49 +0100
To: Simran Suri <ssuri@ipnetfusion.com>
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

RFC3320 section 4.2.2 says:

4.2.2.  Record Marking

    For a stream-based transport, the dispatcher delimits messages by
    parsing the compressed data stream for instances of 0xFF and taking
    the following actions:

    Occurs in data stream:     Action:

    0xFF 00                    one 0xFF byte in the data stream
    0xFF 01                    same, but the next byte is quoted (could
                               be another 0xFF)
       :                                           :
    0xFF 7F                    same, but the next 127 bytes are quoted
    0xFF 80 to 0xFF FE         (reserved for future standardization)
    0xFF FF                    end of SigComp message

So, a simple compressor could simply replace every 0xFF by 0xFF 0x00.
A more advanced compressor will probably look out for any additional 
0xFF in the stream and use the alternate forms to save escape bytes.

Gruesse, Carsten


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



From exim@www1.ietf.org  Thu Mar 25 05:19:57 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13295
	for <rohc-archive@odin.ietf.org>; Thu, 25 Mar 2004 05:19:57 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6RxS-0008NH-1k
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 05:19:30 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PAJTPY032187
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 05:19:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6RxR-0008N4-PD
	for rohc-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 05:19:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13088
	for <rohc-web-archive@ietf.org>; Thu, 25 Mar 2004 05:19:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6RxN-0006oR-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 05:19:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6RvQ-0006Lb-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 05:17:28 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6RtR-0005wa-02
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 05:15:21 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B6Rh2-0000vJ-Cy
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 05:02:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Rgq-0005xi-Cg; Thu, 25 Mar 2004 05:02:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Qcq-0001jP-TG
	for rohc@optimus.ietf.org; Thu, 25 Mar 2004 03:54:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09606
	for <rohc@ietf.org>; Thu, 25 Mar 2004 03:54:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Qco-0006W8-00
	for rohc@ietf.org; Thu, 25 Mar 2004 03:54:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Qbm-0006QL-00
	for rohc@ietf.org; Thu, 25 Mar 2004 03:53:03 -0500
Received: from smtp.wp.pl ([212.77.101.160])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6QbI-0006K6-00
	for rohc@ietf.org; Thu, 25 Mar 2004 03:52:32 -0500
Received: (wp-smtpd smtp.wp.pl 25808 invoked from network); 25 Mar 2004 09:51:57 +0100
Received: from ofree.wp-sa.pl (HELO localhost) ([212.77.101.203])
          (envelope-sender <szym_paw@wp.pl>)
          by smtp.wp.pl (wp-smtpd) with SMTP
          for <kd.singh@enst-bretagne.fr>; 25 Mar 2004 09:51:57 +0100
Date: Thu, 25 Mar 2004 09:51:57 +0100
From: =?ISO-8859-2?Q?Pawe=B3_Szyma=F1ski?= <szym_paw@wp.pl>
To: kamal deep singh <kd.singh@enst-bretagne.fr>
Cc: "Lars-Erik Jonsson \(LU/EAB\)" <lars-erik.jonsson@ericsson.com>,
        rohc@ietf.org
Subject: Re: [rohc] Slope used to compress/decompress RTP Timestamp field
Message-ID: <40629dadba144@wp.pl>
References: <A943FD84BD9ED41193460008C7918050072E94E6@ESEALNT419.al.sw.ericsson.se> <00b901c411e1$bb9f4e70$ee4a34c1@rennes.enstbretagne.fr>
In-reply-to: <A943FD84BD9ED41193460008C7918050072E94E6@ESEALNT419.al.sw.ericsson.se> <00b901c411e1$bb9f4e70$ee4a34c1@rennes.enstbretagne.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-2
Content-Disposition: inline
X-Mailer: Interfejs WWW poczty Wirtualnej Polski
Organization: Poczta Wirtualnej Polski S.A. http://www.wp.pl/
X-IP: 192.55.37.193, 172.28.173.14
X-AntiVirus: skaner antywirusowy poczty Wirtualnej Polski S. A.
X-WP-ChangeAV: 0
X-WP-AntySpam-Rezultat: NIE-SPAM
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id DAA09607
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi,

I agree with Kamal that the notion of slope is required to use=20
UO-0 packets.
However, the RFC 3095 does not says clearly whether the=20
decompressor should decompress UO-0 packets using fixed value of=20
slope equal to the default-slope defined in section 5.7 or it=20
should calculate the slope dynamically basing on TS field values=20
received in UO-1*, UOR*, IR and IR-DYN packets. =20

If the letter case is valid, I would expect that the=20
implementation guide will describe this in detatils.

Regards

Pawel

> Hi,
>=20
>=20
> I find the meaning of "slope" to be implicitly given in the=20
RFC. And I
> believe it because of the following:
>=20
> 1) If we stick to the equation
> SN_Non_field =3D SN*slope + offset given in RFC 3095.
> which is another form of SN_Non_field =3D SN_Non_field_ref +=20
(SN -
> SN_ref)slope.
> Then one of the SN_Non_field will also be TS_SCALED and will=20
also have a
> slope.
> And significance of that I try to show later.
>=20
> 2) Packets of FO state are said to update all parameters of SN=20
functions.
> And slope is also a part of any SN function. so, it is also=20
implicitly
> stated to be updated.
>=20
>=20
>=20
> I understand the meaning of the slope to be as follows:
> ( please correct me if something is wrong?)
>=20
> TS can be perfectly calculated at decompressor given TS_SCALED=20
(and ofcourse
> TS_STRIDE, TS_OFFSET that are constant most of time)
>=20
> Very ideally TS_SCALED will increase like 1, 2, 3, 4, 5 with =20
SN
> and can be said to have slope =3D 1. (as TS_SCALED =3D 1*SN +=20
offset).
> So here will be no need of sending TS_SCALED bits if slope =3D 1=20
is
> established in decompressor.
>=20
> But, in most of the cases TS_SCALED will show behaviour like
>=20
> 1, 1 , 1, 1, 2, 2, 2, 2, 2, 2, 2, 3, 4, 5 in case of video.
>=20
> 1, 2, 3, 4, 6, 7, 7, 8, 9, 10  possibly in case of audio
>=20
> in "above" case of video slope will be 0 most of the time and=20
1 sometimes.
> And in "above" case of audio slope will be 1 most of the time=20
for audio.
>=20
> so, once this slope is established by L or ACK. There will be=20
no need to
> send TS_SCALED field
> and UO_0 (or other depending on  behaviour of other fields)
packets can be
> sent until there is a change.
> (Above also fits when TS is not scaled because then slope will=20
just get
> multiplied by TS_STRIDE)
>=20
>  Need of this slope is that without it I do not find a way in=20
which we can
> send UO_0 packets (except when there is a long chain of TS  =3D =20
constant,  N
> number of times(N being the width of sliding window). Except=20
for this case
> which is unikely(even in video!) with a normal N lets say =3D=20
14,   more than
> 0 bits of TS_SCALED will always be required to be sent. This=20
is because if
> TS_SCALED is encoded by W_LSB then, k (no of bits required to=20
send according
> to W_LSB) will always be >=3D 1 except when all values of=20
TS_SCALED or TS are
> same in the window.
>=20
> And hence in this case(ofcourse I feel that choosing lesser=20
values of N will
> reduce robustness)
> , according to RFC it will be impossible to send UO_0 packets!!
> since they do no contain TS_SCALED bits.
>=20
>=20
> Still I feel that sections on slope are confusing in the RFC=20
and will lead
> to problems in interoperability.
> But, I also feel that neglecting it will reduce compression=20
efficiency.
>=20
> regards,
> kamal
>=20
>=20
> ----- Original Message -----
> From: "Lars-Erik Jonsson (LU/EAB)" <lars-
erik.jonsson@ericsson.com>
> To: "'Pawel Szymanski'" <szym_paw@wp.pl>; <rohc@ietf.org>
> Sent: Wednesday, March 24, 2004 10:04 AM
> Subject: RE: [rohc] Slope used to compress/decompress RTP=20
Timestamp field
>=20
>=20
> > Pawel and others,
> >
> > As I was not deeply involved in designing the encoding parts=20
of RFC 3095 I
> had
> > hoped someone else would answer this question, but since no=20
one has
> responded
> > I thought I would have to take a look at it. After checking=20
what 3095
> actually
> > says, as well as looking for discussions on the mail list,=20
my conclusion
> is that
> > here we really have some confusing text lines we will have=20
to say
> something about.
> >
> > What does 3095 say about slopes?
> > The word slope appears at 6 places in 3095, three in the R-
mode logic and
> 3 in
> > the beginning of the packet format section. None of these=20
provides any
> definitions
> > or descriptions in a normative way. Let's look at the text=20
in 5.5.1.2:
> >
> >    The compressor will transit to the SO state after it has=20
determined
> >    the presence of a string (see section 2), while also=20
being confident
> >    that the decompressor has the string parameters.  The=20
confidence can
> >    be based on ACKs.  For example, in a typical case where=20
the string
> >    pattern has the form of non-SN-field =3D SN * slope +=20
offset, one ACK
> >    is enough if the slope has been previously established by=20
the
> >    decompressor (i.e., only the new offset needs to be=20
synchronized).
> >    Otherwise, two ACKs are required since the decompressor=20
needs two
> >    headers to learn both the new slope and the new offset. =20
In the SO
> >    state, R-0* packets will be sent.
> >
> > The first "slope" could be seen as just a constant in the=20
informative
> > equation, and the second "slope" would then just describe=20
this constant.
> > An example of such a non-SN-field would be TS with a slope=20
TS_STRIDE.
> > So far, there is nothing that says anything about any=20
implicitly
> established
> > slope values, but the third occurrence of "slope" in this=20
text talks about
> > such implicit establishments of string parameters. However,=20
this is the
> > ONLY place where the RFC talks about implicit establishments=20
of slopes,
> > and I can not see how that could possibly be sufficient to=20
imply
> principles
> > requiring a behaviour to be implemented that would obviously=20
affect
> > interoperability. The only conclusion I can draw from this=20
is that the
> > text is a rest that should had been rewritten when the 3095=20
specification
> > evolved.
> >
> > The other 3 occurrences of "slope" (actually "default-
slope") is on page
> 75,
> > where it defines default-slope(IP-ID offset)=3D0 [which is not=20
even a
> parameter
> > to that encoding scheme], as well as default-slope(TS)=3D1 for=20
scaled TS
> > encoding and  =3Dvalue(TS_STRIDE) for "as-is encoding" [which=20
comes as no
> > surprise as TS is scaled with TS_STRIDE].
> >
> > There is no place in the RFC that normatively says a word=20
about implicitly
> > updating the slope, so my conclusion is that there should be=20
no such
> thing.
> > The mail list discussions indicates that there were=20
proposals to have such
> > principles, but the discussions point in the direction of=20
giving up these
> ideas.
> >
> http://www1.ietf.org/mail-archive/working-groups/rohc/old-
archive/msg00953.h
> tml
> >
> > I'll put this to my list of things to clarify in the next=20
version of the
> impl. guide.
> >
> > BR
> > /L-E
> >
> >
> >
> > > -----Original Message-----
> > > From: rohc-admin@ietf.org [mailto:rohc-admin@ietf.org]On
> > > Behalf Of Pawel Szymanski
> > > Sent: den 16 mars 2004 14:31
> > > To: rohc@ietf.org
> > > Subject: [rohc] Slope used to compress/decompress RTP=20
Timestamp field
> > >
> > >
> > > Hi all,
> > >
> > > I've seen in the ROHC mailing list archive a discussion=20
about
> > > using dynamic slope values by the compressor and=20
decompressor
> > > while decompressing RTP Timestamp field from OU-0 packets=20
(refer
> > > to mail: http://www.cdt.luth.se/rohc/msg00934.html). The=20
idea is
> > > that decompressor starts with default_slope value and=20
calculates
> > > new slope value at each arrival of a packet containing TS=20
field.
> > >
> > > The mechanism is not described in the standard. Only
> > > default_slope values are defined. Should compressor and
> > > decompressor use other slope values than the default_slope=20
when
> > > they process UO-0 packets ?
> > >
> > > Regards
> > >
> > > Pawel Szymanski
> >
> > This communication is confidential and intended solely for=20
the
> addressee(s). Any unauthorized review, use, disclosure or=20
distribution is
> prohibited. If you believe this message has been sent to you=20
in error,
> please notify the sender by replying to this transmission and=20
delete the
> message without disclosing it. Thank you.
> >
> > E-mail including attachments is susceptible to data=20
corruption,
> interruption, unauthorized amendment, tampering and viruses,=20
and we only
> send and receive e-mails on the basis that we are not liable=20
for any such
> corruption, interception, amendment, tampering or viruses or=20
any
> consequences thereof.
> >
> >
> > _______________________________________________
> > Rohc mailing list
> > Rohc@ietf.org
> > https://www1.ietf.org/mailman/listinfo/rohc
> >
>=20
>=20

----------------------------------------------------
Zobacz niezwyk=B3y koncert: "Niemena Pami=EAci Gda=F1ski Rapsod"
Najwi=EAksze przeboje artysty w nowych zaskakuj=B1cych aran=BFacjach.
http://klik.wp.pl/?adr=3Dhttp%3A%2F%2Fmuzyka.wp.pl%2Fimprezy.html%3Fidn%3=
D874&sid=3D151



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



From exim@www1.ietf.org  Thu Mar 25 09:11:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22118
	for <rohc-archive@odin.ietf.org>; Thu, 25 Mar 2004 09:11:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6VZH-0007Yr-8x
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 09:11:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PEAlW4029057
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 09:10:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6VZG-0007YW-Ul
	for rohc-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 09:10:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21794
	for <rohc-web-archive@ietf.org>; Thu, 25 Mar 2004 09:10:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6VZE-0006MB-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 09:10:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6VXu-00067J-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 09:09:23 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6VXF-0005xg-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 09:08:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6VXF-0006OX-KQ; Thu, 25 Mar 2004 09:08:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6SEQ-0000dk-Mx
	for rohc@optimus.ietf.org; Thu, 25 Mar 2004 05:37:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13980
	for <rohc@ietf.org>; Thu, 25 Mar 2004 05:36:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6SEN-0000uw-00
	for rohc@ietf.org; Thu, 25 Mar 2004 05:36:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6SDQ-0000pf-00
	for rohc@ietf.org; Thu, 25 Mar 2004 05:36:01 -0500
Received: from [194.237.235.30] (helo=effnet.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6SCr-0000j4-00
	for rohc@ietf.org; Thu, 25 Mar 2004 05:35:26 -0500
Received: from effnet.com (c-497871d5.04-205-6c756c1.cust.bredbandsbolaget.se [213.113.120.73])
	(authenticated bits=0)
	by effnet.com (8.12.3/8.12.3) with ESMTP id i2P9YVU2026810
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Thu, 25 Mar 2004 10:34:31 +0100
Message-ID: <4062B5C9.4010403@effnet.com>
Date: Thu, 25 Mar 2004 11:34:49 +0100
From: Kristofer Sandlund <kristofer.sandlund@effnet.com>
Organization: Effnet
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030821
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Pawe=B3_Szyma=F1ski?= <szym_paw@wp.pl>
CC: kamal deep singh <kd.singh@enst-bretagne.fr>,
        "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>,
        rohc@ietf.org
Subject: Re: [rohc] Slope used to compress/decompress RTP Timestamp field
References: <A943FD84BD9ED41193460008C7918050072E94E6@ESEALNT419.al.sw.ericsson.se> <00b901c411e1$bb9f4e70$ee4a34c1@rennes.enstbretagne.fr> <40629dadba144@wp.pl>
In-Reply-To: <40629dadba144@wp.pl>
X-Enigmail-Version: 0.76.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Pawel, Kamal & L-E!

I think we can all agree that 3095 creates confusion in this area by including 
the text about "slope" in a few places while not defining it.It's about time we 
clear this up, since there has been a number of discussions related to this 
topic on the list.

For this discussion, let us limit ourselves for a possible slope used by the TS 
field, since that's really what we are discussion here and not use the 
"non-SN-field" term too much.

I believe that as the specis written, there cannot be room for a slope that can 
be implicitly updated. I base this on the following observations:

* 4.5.3. Scaled RTP Timestamp encoding
    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 =
       TS_SCALED * TS_STRIDE + TS_OFFSET.

If there acutally was a slope, it should have been in this formula.


* If there is an implicit update of the slope, then it is not defined anywhere 
how/when this would actually happen, which would create interoperability problems.


* 5.5.1.2.  Compression logic and packets used (R-mode)
     --non-SN-field = SN * slope + offset

I am convinced that this is just written to be general for possible future 
profiles (with other fields than TS being sent in a scaled fashion), if we 
narrow this down to TS, then we get TS = SN * slope + offset.
Compare this to the formula in 4.5.3 (quoted above), then suddenly it becomes 
clear that "slope" really means TS_STRIDE in this section.
As a side note, even if this text was meant to define a slope, this section ONLY 
applies to R-mode, so it would not impact the fact if we can use UO-0 packets or 
not on video streams with semi-constant TS.

********
So, back to the example given by Kamal regarding the need for slope:

 >>But, in most of the cases TS_SCALED will show behaviour like
 >>
 >> 1, 1 , 1, 1, 2, 2, 2, 2, 2, 2, 2, 3, 4, 5 in case of video.
 >>
 >> 1, 2, 3, 4, 6, 7, 7, 8, 9, 10  possibly in case of audio
 >>
 >> in "above" case of video slope will be 0 most of the time and
 >> 1 sometimes.
 >> And in "above" case of audio slope will be 1 most of the time
 >> for audio.

Let's say that the unscaled TS in the video example will be 30 and the starting 
value 10, then we'd have this:

10, 10, 10, 10, 40, 40, 40, 40, 40, 40, 40, 70, 100, 130

As you observe, the "video slope will be 0 most of the time". This is the 
observation that your compressor also should make, and therefore use a TS_STRIDE 
of 0.
What we can do when the TS changes from 10 to 40 is that we can interpret this 
as a change of TS_OFFSET instead of saying that TS_STRIDE (or slope) changes.
So we keep the TS_STRIDE as 0, but change TS_OFFSET from 10 to 40, which we do 
by sending some UOR-2-ext3 with an unscaled timestamp according to the 
optimistic approach, and then move back to sending UO-0 packets. This without 
ever having to change the TS_STRIDE. The sliding window depth should not impact 
here even if it is larger than the number of packets, we are in U/O-mode where 
we use the optimistic approach.

When we reach the later parts of Kamal's example (3,4,5,...), then the 
compressor will probably note that a change of 30 will be more frequent than the 
constant TS, and will after a while establish a TS_STRIDE of 30. If it does not, 
then it could update the offset as above wuthout causing extra packet losses.

Therefore, we do not need a slope to handle the case presented here (unless I'm 
proven wrong of course).

Best regards,
	Kristofer Sandlund, Effnet AB


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



From exim@www1.ietf.org  Thu Mar 25 10:45:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01649
	for <rohc-archive@odin.ietf.org>; Thu, 25 Mar 2004 10:45:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6X2V-0002MA-U7
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 10:45:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PFj3JT009053
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 10:45:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6X2V-0002Lw-Pq
	for rohc-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 10:45:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01471
	for <rohc-web-archive@ietf.org>; Thu, 25 Mar 2004 10:44:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6X2T-0001M3-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 10:45:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6X1X-0001EZ-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 10:44:04 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6X0a-0001B9-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 10:43:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6X0b-0001MN-Pb; Thu, 25 Mar 2004 10:43:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6WYB-0005WF-4m
	for rohc@optimus.ietf.org; Thu, 25 Mar 2004 10:13:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23350
	for <rohc@ietf.org>; Thu, 25 Mar 2004 09:23:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6VlT-0007jA-00
	for rohc@ietf.org; Thu, 25 Mar 2004 09:23:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Vkp-0007eH-00
	for rohc@ietf.org; Thu, 25 Mar 2004 09:22:43 -0500
Received: from bay10-f100.bay10.hotmail.com ([64.4.37.100] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Vjo-0007Un-00
	for rohc@ietf.org; Thu, 25 Mar 2004 09:21:40 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Thu, 25 Mar 2004 06:21:10 -0800
Received: from 80.74.106.2 by by10fd.bay10.hotmail.msn.com with HTTP;
	Thu, 25 Mar 2004 14:21:09 GMT
X-Originating-IP: [80.74.106.2]
X-Originating-Email: [johnyjsmith1970@hotmail.com]
X-Sender: johnyjsmith1970@hotmail.com
From: "John Smith" <johnyjsmith1970@hotmail.com>
To: rohc@ietf.org
Date: Thu, 25 Mar 2004 14:21:09 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <BAY10-F100YbB1t93Lx000122ee@hotmail.com>
X-OriginalArrivalTime: 25 Mar 2004 14:21:10.0093 (UTC) FILETIME=[6B6B7FD0:01C41274]
Subject: [rohc] SIP dialog and SigComp compartments relationship
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS 
	autolearn=no version=2.60

Hi All,

A quotation from draft-ietf-rohc-sigcomp-sip-01.txt section 3:
"When SigComp is applied to SIP, there is a one-to-one relationship between 
a SIP dialog (see section 12 of [RFC-3261]) and a pair of peer SigComp 
compartments....
The only requirement is to maintain a local one-to-one mapping between a 
dialog ID and a compartment ID."

This kind of limitation might cause inefficiency. For exmaple, in case of 
UAC, which is configured to send all its' requests to an outbound proxy. 
Instead of using single compartment, that stores common data (all the 
outgoing requests share the same destination), each established dialog will 
trigger new compartment. It seems to be wasteful.

Generally, there might be several dialogs that share common data and had 
better if they would also share the same compartment, isn't it?

Thanks in advance,
John.

_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail


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



From exim@www1.ietf.org  Thu Mar 25 12:08:06 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07261
	for <rohc-archive@odin.ietf.org>; Thu, 25 Mar 2004 12:08:06 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6YKQ-0004Zn-AK
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 12:07:39 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PH7chZ017589
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 12:07:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6YKQ-0004Zb-47
	for rohc-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 12:07:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07245
	for <rohc-web-archive@ietf.org>; Thu, 25 Mar 2004 12:07:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6YKO-0007bl-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 12:07:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6YJU-0007X3-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 12:06:41 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6YIq-0007Sf-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 12:06:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6YIr-0004Dg-1Q; Thu, 25 Mar 2004 12:06:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6YIG-00048A-Fj
	for rohc@optimus.ietf.org; Thu, 25 Mar 2004 12:05:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07036
	for <rohc@ietf.org>; Thu, 25 Mar 2004 12:05:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6YIF-0007Nr-00
	for rohc@ietf.org; Thu, 25 Mar 2004 12:05:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6YHI-0007Hn-00
	for rohc@ietf.org; Thu, 25 Mar 2004 12:04:25 -0500
Received: from [216.90.186.146] (helo=mail.ipnetfusion.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6YGO-00072u-00
	for rohc@ietf.org; Thu, 25 Mar 2004 12:03:28 -0500
Received: from ipnetfusion.com (pc223 [192.1.2.223])
	(authenticated)
	by mail.ipnetfusion.com (8.11.6/8.11.6) with ESMTP id i2PH0FG12820;
	Thu, 25 Mar 2004 11:00:15 -0600
Message-ID: <40631025.5070304@ipnetfusion.com>
Date: Thu, 25 Mar 2004 11:00:21 -0600
From: Chintan Thakker <cthakker@ipnetfusion.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030723 Thunderbird/0.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John Smith <johnyjsmith1970@hotmail.com>
CC: rohc@ietf.org
Subject: Re: [rohc] SIP dialog and SigComp compartments relationship
References: <BAY10-F100YbB1t93Lx000122ee@hotmail.com>
In-Reply-To: <BAY10-F100YbB1t93Lx000122ee@hotmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Is it that when we are done with a compartment, it frees up 
corresponding state at the State Handler (or just decreases the 
reference count). Additionally is it useful to have a different 
compression algorithm for every dialog that is established ? (3320 talks 
about the compression algorithm being a characteristic of the compartment).

Thanks,

John Smith wrote:

> Hi All,
>
> A quotation from draft-ietf-rohc-sigcomp-sip-01.txt section 3:
> "When SigComp is applied to SIP, there is a one-to-one relationship 
> between a SIP dialog (see section 12 of [RFC-3261]) and a pair of peer 
> SigComp compartments....
> The only requirement is to maintain a local one-to-one mapping between 
> a dialog ID and a compartment ID."
>
> This kind of limitation might cause inefficiency. For exmaple, in case 
> of UAC, which is configured to send all its' requests to an outbound 
> proxy. Instead of using single compartment, that stores common data 
> (all the outgoing requests share the same destination), each 
> established dialog will trigger new compartment. It seems to be wasteful.
>
> Generally, there might be several dialogs that share common data and 
> had better if they would also share the same compartment, isn't it?
>
> Thanks in advance,
> John.
>
> _________________________________________________________________
> The new MSN 8: smart spam protection and 2 months FREE*  
> http://join.msn.com/?page=features/junkmail
>
>
> _______________________________________________
> 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 exim@www1.ietf.org  Thu Mar 25 12:56:54 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11127
	for <rohc-archive@odin.ietf.org>; Thu, 25 Mar 2004 12:56:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Z5f-0002fx-Jh
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 12:56:27 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PHuRcf010281
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 12:56:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Z5f-0002fk-Fg
	for rohc-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 12:56:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11097
	for <rohc-web-archive@ietf.org>; Thu, 25 Mar 2004 12:56:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Z5d-0004Gb-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 12:56:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Z4g-0004CW-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 12:55:27 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Z3p-00047H-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 12:54:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Z3p-0002QC-Qy; Thu, 25 Mar 2004 12:54:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Z1l-0001Xf-C1
	for rohc@optimus.ietf.org; Thu, 25 Mar 2004 12:52:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10844
	for <rohc@ietf.org>; Thu, 25 Mar 2004 12:52:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Z1j-0003x5-00
	for rohc@ietf.org; Thu, 25 Mar 2004 12:52:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Z0p-0003v8-00
	for rohc@ietf.org; Thu, 25 Mar 2004 12:51:28 -0500
Received: from rsys002a.roke.co.uk ([193.118.192.251])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Yzy-0003qO-00
	for rohc@ietf.org; Thu, 25 Mar 2004 12:50:35 -0500
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <1ZGNFMM3>; Thu, 25 Mar 2004 17:49:58 -0000
Message-ID: <EA943CD30BCB104E9D38F5B5DC2D9A70A1AEEB@rsys004a.roke.co.uk>
From: "West, Mark" <mark.a.west@roke.co.uk>
To: "'Chintan Thakker'" <cthakker@ipnetfusion.com>,
        John Smith
	 <johnyjsmith1970@hotmail.com>
Cc: rohc@ietf.org
Subject: RE: [rohc] SIP dialog and SigComp compartments relationship
Date: Thu, 25 Mar 2004 17:50:11 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


Hi,

The intention was that compartments relate to dialogs (rather than any longer-lived, or more tenuous concept).  This has a number of implications on storage, security models, etc.  When we last discussed this (there's a mail somewhere in the archive!) we talked in terms of the application being able to allow state to persist after the compartment has closed.  This could be advertised to the peer application such that the state is available for some [defined] time.  (But also allows the application to bound the memory usage in the case where you have a large number of registered subscribers, few of whom are doing anything).

Additional thoughts on this subject are very welcome, however!

Cheers,

Mark.


> -----Original Message-----
> From: Chintan Thakker [mailto:cthakker@ipnetfusion.com]
> Sent: 25 March 2004 17:00
> To: John Smith
> Cc: rohc@ietf.org
> Subject: Re: [rohc] SIP dialog and SigComp compartments relationship
> 
> 
> Is it that when we are done with a compartment, it frees up 
> corresponding state at the State Handler (or just decreases the 
> reference count). Additionally is it useful to have a different 
> compression algorithm for every dialog that is established ? 
> (3320 talks 
> about the compression algorithm being a characteristic of the 
> compartment).
> 
> Thanks,
> 
> John Smith wrote:
> 
> > Hi All,
> >
> > A quotation from draft-ietf-rohc-sigcomp-sip-01.txt section 3:
> > "When SigComp is applied to SIP, there is a one-to-one relationship 
> > between a SIP dialog (see section 12 of [RFC-3261]) and a 
> pair of peer 
> > SigComp compartments....
> > The only requirement is to maintain a local one-to-one 
> mapping between 
> > a dialog ID and a compartment ID."
> >
> > This kind of limitation might cause inefficiency. For 
> exmaple, in case 
> > of UAC, which is configured to send all its' requests to an 
> outbound 
> > proxy. Instead of using single compartment, that stores common data 
> > (all the outgoing requests share the same destination), each 
> > established dialog will trigger new compartment. It seems 
> to be wasteful.
> >
> > Generally, there might be several dialogs that share common 
> data and 
> > had better if they would also share the same compartment, isn't it?
> >
> > Thanks in advance,
> > John.
> >
> > _________________________________________________________________
> > The new MSN 8: smart spam protection and 2 months FREE*  
> > http://join.msn.com/?page=features/junkmail
> >
> >
> > _______________________________________________
> > 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 exim@www1.ietf.org  Thu Mar 25 13:11:15 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12065
	for <rohc-archive@odin.ietf.org>; Thu, 25 Mar 2004 13:11:15 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZJV-0004fP-TX
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 13:10:46 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PIAjtU017893
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 13:10:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZJT-0004da-UN
	for rohc-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 13:10:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12039
	for <rohc-web-archive@ietf.org>; Thu, 25 Mar 2004 13:10:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ZJJ-0005a2-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 13:10:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6ZIW-0005Wy-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 13:09:44 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ZHl-0005TJ-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 13:08:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZHm-0004X0-55; Thu, 25 Mar 2004 13:08:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZFr-00048T-03
	for rohc@optimus.ietf.org; Thu, 25 Mar 2004 13:06:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11878
	for <rohc@ietf.org>; Thu, 25 Mar 2004 13:06:54 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ZFo-0005Lh-00
	for rohc@ietf.org; Thu, 25 Mar 2004 13:06:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6ZF3-0005Eh-00
	for rohc@ietf.org; Thu, 25 Mar 2004 13:06:10 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ZDy-00054U-00
	for rohc@ietf.org; Thu, 25 Mar 2004 13:05:03 -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 i2PI51428921
	for <rohc@ietf.org>; Thu, 25 Mar 2004 20:05:01 +0200 (EET)
X-Scanned: Thu, 25 Mar 2004 20:04:55 +0200 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i2PI4t7S022679
	for <rohc@ietf.org>; Thu, 25 Mar 2004 20:04:55 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks003.ntc.nokia.com 00qXHI5t; Thu, 25 Mar 2004 20:04:53 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 i2PI4qs25637
	for <rohc@ietf.org>; Thu, 25 Mar 2004 20:04:52 +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, 25 Mar 2004 12:04:46 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Subject: RE: [rohc] SIP dialog and SigComp compartments relationship
Date: Thu, 25 Mar 2004 13:04:41 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B8153710@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] SIP dialog and SigComp compartments relationship
Thread-Index: AcQSgGqt2HZYASngRqSHArxOk59Y1AAEdTdg
To: <johnyjsmith1970@hotmail.com>, <rohc@ietf.org>
X-OriginalArrivalTime: 25 Mar 2004 18:04:46.0508 (UTC) FILETIME=[A839F6C0:01C41293]
Content-Transfer-Encoding: quoted-printable
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Agreed. As stated in the editor's note, the current text only serves
as a starting point. A more flexible mapping of SIP messages to=20
compartment is needed. Besides combining multiple dialogs, it would
also help improve compression for SIP messages outside of a dialog.

Zhigang

> -----Original Message-----
> From: rohc-admin@ietf.org [mailto:rohc-admin@ietf.org]On Behalf Of ext
> John Smith
> Sent: 25 March, 2004 08:21 AM
> To: rohc@ietf.org
> Subject: [rohc] SIP dialog and SigComp compartments relationship
>=20
>=20
> Hi All,
>=20
> A quotation from draft-ietf-rohc-sigcomp-sip-01.txt section 3:
> "When SigComp is applied to SIP, there is a one-to-one=20
> relationship between=20
> a SIP dialog (see section 12 of [RFC-3261]) and a pair of=20
> peer SigComp=20
> compartments....
> The only requirement is to maintain a local one-to-one=20
> mapping between a=20
> dialog ID and a compartment ID."
>=20
> This kind of limitation might cause inefficiency. For=20
> exmaple, in case of=20
> UAC, which is configured to send all its' requests to an=20
> outbound proxy.=20
> Instead of using single compartment, that stores common data (all the=20
> outgoing requests share the same destination), each=20
> established dialog will=20
> trigger new compartment. It seems to be wasteful.
>=20
> Generally, there might be several dialogs that share common=20
> data and had=20
> better if they would also share the same compartment, isn't it?
>=20
> Thanks in advance,
> John.
>=20
> _________________________________________________________________
> The new MSN 8: smart spam protection and 2 months FREE* =20
> http://join.msn.com/?page=3Dfeatures/junkmail
>=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 exim@www1.ietf.org  Thu Mar 25 14:11:52 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14303
	for <rohc-archive@odin.ietf.org>; Thu, 25 Mar 2004 14:11:52 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6aGC-0003Cs-Se
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 14:11:25 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PJBOK8012320
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 14:11:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6aGC-0003Cd-Km
	for rohc-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 14:11:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14267
	for <rohc-web-archive@ietf.org>; Thu, 25 Mar 2004 14:11:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6aGA-0000qe-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 14:11:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6aFB-0000mq-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 14:10:22 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6aED-0000if-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 14:09:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6aEE-000354-S0; Thu, 25 Mar 2004 14:09:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6aDQ-00030J-Vh
	for rohc@optimus.ietf.org; Thu, 25 Mar 2004 14:08:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14195
	for <rohc@ietf.org>; Thu, 25 Mar 2004 14:08:30 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6aDO-0000fl-00
	for rohc@ietf.org; Thu, 25 Mar 2004 14:08:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6aCT-0000dD-00
	for rohc@ietf.org; Thu, 25 Mar 2004 14:07:34 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6aBq-0000ad-00
	for rohc@ietf.org; Thu, 25 Mar 2004 14:06:54 -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 i2PJ6o402816;
	Thu, 25 Mar 2004 21:06:50 +0200 (EET)
X-Scanned: Thu, 25 Mar 2004 21:06:41 +0200 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i2PJ6fcN023334;
	Thu, 25 Mar 2004 21:06:41 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 00z0o01M; Thu, 25 Mar 2004 20:38:05 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 i2PIc4s15720;
	Thu, 25 Mar 2004 20:38: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);
	 Thu, 25 Mar 2004 12:37:21 -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] SIP dialog and SigComp compartments relationship
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Thu, 25 Mar 2004 13:29:40 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B8153712@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] SIP dialog and SigComp compartments relationship
Thread-Index: AcQSjCR0GPmIIVlDTKa3Ybh3HlzbFwACHozA
To: <cthakker@ipnetfusion.com>, <johnyjsmith1970@hotmail.com>
Cc: <rohc@ietf.org>
X-OriginalArrivalTime: 25 Mar 2004 18:37:21.0785 (UTC) FILETIME=[35A98E90:01C41298]
Content-Transfer-Encoding: quoted-printable
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

> Is it that when we are done with a compartment, it frees up=20
> corresponding state at the State Handler (or just decreases the=20
> reference count).=20

It will "physically" delete a state, if it is the only compartment
in which the state is created. SigComp allows a state to be created
multiple times in different compartment. So, an implementation
would maintain a reference count and perform the actual deletion when
the count decremented down to zero.

However, see the comments from Mark about extending the lifetime of
a state beyond that of a compartment. Being "compartment-less", the
same sate can be used to compress messages from different dialogs.

> Additionally is it useful to have a different=20
> compression algorithm for every dialog that is established ?=20

The sender can choose whichever algorithm for a dialog, or even for=20
a message, as long as the decompression bytecode is made available
to the remote receiver. So, it's more related to state than compartment.

> (3320 talks about the compression algorithm being a characteristic of =
the=20
> compartment).

I have to double check the text in RFC 3320. But I think it is not the
intention to limit an implementation.

BR,
Zhigang

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



From exim@www1.ietf.org  Thu Mar 25 15:39:09 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19619
	for <rohc-archive@odin.ietf.org>; Thu, 25 Mar 2004 15:39:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6bce-0005cK-R7
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 15:38:41 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PKceEv021588
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 15:38:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6bce-0005c7-N1
	for rohc-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 15:38:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19503
	for <rohc-web-archive@ietf.org>; Thu, 25 Mar 2004 15:38:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6bcd-0005i5-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 15:38:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6bbl-0005dm-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 15:37:46 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6bb4-0005ZQ-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 15:37:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6bb4-0005Ck-08; Thu, 25 Mar 2004 15:37:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6baU-0004yz-H1
	for rohc@optimus.ietf.org; Thu, 25 Mar 2004 15:36:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19144
	for <rohc@ietf.org>; Thu, 25 Mar 2004 15:36:24 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6baS-0005Vh-00
	for rohc@ietf.org; Thu, 25 Mar 2004 15:36:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6bZU-0005Sw-00
	for rohc@ietf.org; Thu, 25 Mar 2004 15:35:24 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6bYa-0005Qj-00
	for rohc@ietf.org; Thu, 25 Mar 2004 15:34:28 -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 i2PKYQ425961;
	Thu, 25 Mar 2004 22:34:26 +0200 (EET)
X-Scanned: Thu, 25 Mar 2004 22:34:07 +0200 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id i2PKY7je007316;
	Thu, 25 Mar 2004 22:34:07 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks002.ntc.nokia.com 007uGvbC; Thu, 25 Mar 2004 22:34:02 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 i2PKY0s28993;
	Thu, 25 Mar 2004 22:34:00 +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, 25 Mar 2004 14:33:58 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Subject: RE: [rohc] Slope used to compress/decompress RTP Timestamp field
Date: Thu, 25 Mar 2004 15:33:57 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B8153713@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] Slope used to compress/decompress RTP Timestamp field
Thread-Index: AcQR4mhZT/oZEoDJQk+nbLzh9+JNFgAweu5A
To: <kd.singh@enst-bretagne.fr>, <lars-erik.jonsson@ericsson.com>,
        <szym_paw@wp.pl>, <rohc@ietf.org>
X-OriginalArrivalTime: 25 Mar 2004 20:33:58.0958 (UTC) FILETIME=[804D6CE0:01C412A8]
Content-Transfer-Encoding: quoted-printable
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi,

Please see my comments below. Sorry about being late on this issue (I =
was one of those who wrote the sections).

BR,
Zhigang

> I find the meaning of "slope" to be implicitly given in the RFC. And I
> believe it because of the following:
>=20
> 1) If we stick to the equation
> SN_Non_field =3D SN*slope + offset given in RFC 3095.
> which is another form of SN_Non_field =3D SN_Non_field_ref + (SN -
> SN_ref)slope.
> Then one of the SN_Non_field will also be TS_SCALED and will=20
> also have a slope.
> And significance of that I try to show later.
>=20
> 2) Packets of FO state are said to update all parameters of=20
> SN functions. And slope is also a part of any SN function. so, it is =
also implicitly
> stated to be updated.

Correct.

> But, in most of the cases TS_SCALED will show behaviour like
>=20
> 1, 1 , 1, 1, 2, 2, 2, 2, 2, 2, 2, 3, 4, 5 in case of video.
>=20
> 1, 2, 3, 4, 6, 7, 7, 8, 9, 10  possibly in case of audio
>=20
> in "above" case of video slope will be 0 most of the time and=20
> 1 sometimes. And in "above" case of audio slope will be 1 most of the =
time=20
> for audio.

This is one of the reasons why we need a dynamically established slope.
Besides the different behaviour between media types,  a different slope
may appear even for the same media type or codec due to different
packetization. For example, a media may encapsulate two 20 ms
voice frames into one RTP packet. So the TS_SCALED could look
like 2, 4, 6, 8, 10, with a slope of 2 instead of 1.

> so, once this slope is established by L or ACK. There will be=20
> no need to send TS_SCALED field
> and UO_0 (or other depending on  behaviour of other=20
> fields)packets can be sent until there is a change.
> (Above also fits when TS is not scaled because then slope=20
> will just get multiplied by TS_STRIDE)

Correct.

> Still I feel that sections on slope are confusing in the RFC=20
> and will lead to problems in interoperability.

It could have been described clearer in RFC 3095. We were short of time =
and different=20
authors have different opinion on how much/explicit is just enough =
without being=20
verbose. You feel the pressure when the document becomes 168 pages long. =
:-(

Anyway, a clarification on this in the implementer's I-D would help.

> But, I also feel that neglecting it will reduce compression =
efficiency.

I cannot agree more, not to mention the flexibility of ROHC. We cannot =
simply predict
the slope for different header fields for all kinds of RTP flows.

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



From exim@www1.ietf.org  Thu Mar 25 16:26:05 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25550
	for <rohc-archive@odin.ietf.org>; Thu, 25 Mar 2004 16:26:05 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6cM5-00023x-2B
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 16:25:37 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PLPbYC007929
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 16:25:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6cM4-00023o-UV
	for rohc-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 16:25:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25542
	for <rohc-web-archive@ietf.org>; Thu, 25 Mar 2004 16:25:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6cM3-00042Z-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 16:25:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6cL6-00040Y-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 16:24:37 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6cKV-0003yA-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 16:23:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6cKW-0001wd-Dy; Thu, 25 Mar 2004 16:24:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6cK2-0001vq-8z
	for rohc@optimus.ietf.org; Thu, 25 Mar 2004 16:23:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25402
	for <rohc@ietf.org>; Thu, 25 Mar 2004 16:23:27 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6cK0-0003wu-00
	for rohc@ietf.org; Thu, 25 Mar 2004 16:23:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6cJ9-0003uu-00
	for rohc@ietf.org; Thu, 25 Mar 2004 16:22:35 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6cIa-0003t7-00
	for rohc@ietf.org; Thu, 25 Mar 2004 16:22:00 -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 i2PLLxA08928;
	Thu, 25 Mar 2004 23:21:59 +0200 (EET)
X-Scanned: Thu, 25 Mar 2004 23:21:17 +0200 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i2PLLHNA021610;
	Thu, 25 Mar 2004 23:21:17 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 00c874kw; Thu, 25 Mar 2004 23:21:15 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 i2PLLDs26985;
	Thu, 25 Mar 2004 23:21: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, 25 Mar 2004 15:21:11 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] Slope used to compress/decompress RTP Timestamp field
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Thu, 25 Mar 2004 16:21:11 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B8153715@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] Slope used to compress/decompress RTP Timestamp field
Thread-Index: AcQSUJHqBgEAhlmNRrq0HCoz6+ovIAAXgXlg
To: <szym_paw@wp.pl>, <kd.singh@enst-bretagne.fr>
Cc: <lars-erik.jonsson@ericsson.com>, <rohc@ietf.org>
X-OriginalArrivalTime: 25 Mar 2004 21:21:12.0103 (UTC) FILETIME=[18FD0B70:01C412AF]
Content-Transfer-Encoding: quoted-printable
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

> I agree with Kamal that the notion of slope is required to use=20
> UO-0 packets.
> However, the RFC 3095 does not says clearly whether the=20
> decompressor should decompress UO-0 packets using fixed value of=20
> slope equal to the default-slope defined in section 5.7 or it=20
> should calculate the slope dynamically basing on TS field values=20
> received in UO-1*, UOR*, IR and IR-DYN packets. =20
>=20
> If the letter case is valid, I would expect that the=20
> implementation guide will describe this in detatils.

The intension of RFC 3095 is the latter case. That's why "default-slope" =
has a prefix "default".=20

Implementation guide would be a good place to clarify.

BR,
Zhigang

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



From exim@www1.ietf.org  Thu Mar 25 16:50:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26748
	for <rohc-archive@odin.ietf.org>; Thu, 25 Mar 2004 16:50:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6cji-0005I0-Am
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 16:50:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PLo2xv020326
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 16:50:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6cji-0005Hk-62
	for rohc-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 16:50:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26678
	for <rohc-web-archive@ietf.org>; Thu, 25 Mar 2004 16:49:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6cjg-0005Z9-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 16:50:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6ciZ-0005Rm-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 16:48:52 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6chm-0005M4-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 16:48:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6chm-0004af-CN; Thu, 25 Mar 2004 16:48:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6cgn-0004PZ-HV
	for rohc@optimus.ietf.org; Thu, 25 Mar 2004 16:47:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26508
	for <rohc@ietf.org>; Thu, 25 Mar 2004 16:46:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6cgb-0005GA-00
	for rohc@ietf.org; Thu, 25 Mar 2004 16:46:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6cfi-0005BQ-00
	for rohc@ietf.org; Thu, 25 Mar 2004 16:45:55 -0500
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6cfD-00056F-00
	for rohc@ietf.org; Thu, 25 Mar 2004 16:45:23 -0500
Received: from courrier.rennes.enst-bretagne.fr (f1-clust.rennes.enst-bretagne.fr [193.52.74.16])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with ESMTP id i2PLimR32152;
	Thu, 25 Mar 2004 22:44:48 +0100
Received: from pcrsm7 ([193.52.74.238])
	by courrier.rennes.enst-bretagne.fr (8.12.11/8.12.11/2004.01.01) with SMTP id i2PLimGM025487;
	Thu, 25 Mar 2004 22:44:49 +0100 (MET)
Message-ID: <018f01c412b2$65a27200$ee4a34c1@rennes.enstbretagne.fr>
From: "kamal deep singh" <kd.singh@enst-bretagne.fr>
To: "Kristofer Sandlund" <kristofer.sandlund@effnet.com>,
        =?iso-8859-1?Q?Pawe=B3_Szyma=F1ski?= <szym_paw@wp.pl>
Cc: "Lars-Erik Jonsson \(LU/EAB\)" <lars-erik.jonsson@ericsson.com>,
        <rohc@ietf.org>
References: <A943FD84BD9ED41193460008C7918050072E94E6@ESEALNT419.al.sw.ericsson.se> <00b901c411e1$bb9f4e70$ee4a34c1@rennes.enstbretagne.fr> <40629dadba144@wp.pl> <4062B5C9.4010403@effnet.com>
Subject: Re: [rohc] Slope used to compress/decompress RTP Timestamp field
Date: Thu, 25 Mar 2004 22:44: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.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

I  seem to see two questions.

1) Which method will be most efficient (compression ratio wise)?
 The one which considers slope or the one which ignores slope?

My answer is that the method which considers slope of TS_SCALED, will be
most efficient. As the changes in TS can be communicated just by
communicating TS_SCALED
"lsb bits".  (And not by sending TS absolute and TS_STRIDE to update
TS_OFFSET, in contrast)

2) Which method is interoperable and never assumes anything outside the RFC?

If things can be made clear by using implementer's guide, then our obvious
choice should
be to use the most efficient method. But, if that is not the case, then
Kristofer's method of
ignoring slope looks favourable to me. However I want to discuss some points
regarding that
method.

find my comments below.

> I believe that as the specis written, there cannot be room for a slope
that can
> be implicitly updated. I base this on the following observations:
>
> * 4.5.3. Scaled RTP Timestamp encoding
>     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 =
>        TS_SCALED * TS_STRIDE + TS_OFFSET.
>
> If there acutally was a slope, it should have been in this formula.

> * If there is an implicit update of the slope, then it is not defined
anywhere
> how/when this would actually happen, which would create interoperability
problems.

It is said in RFC that all parameters of the SN functions should be updated.
Slope ( or
what ever name one can choose) is also a parameter and should be updated.

>
> * 5.5.1.2.  Compression logic and packets used (R-mode)
>      --non-SN-field = SN * slope + offset
>
> I am convinced that this is just written to be general for possible future
> profiles (with other fields than TS being sent in a scaled fashion), if we
> narrow this down to TS, then we get TS = SN * slope + offset.
> Compare this to the formula in 4.5.3 (quoted above), then suddenly it
becomes
> clear that "slope" really means TS_STRIDE in this section.


TS = SN*slope + offset will not fit if we take slope = TS_STRIDE
and offset = TS modulo TS_STRIDE as given in

Section 4.5.3

" The following algorithm is used:
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 = TS / TS_STRIDE.  The compression
      method could be either W-LSB encoding or the timer-based encoding
      described in the next section.
"

> As a side note, even if this text was meant to define a slope, this
section ONLY
> applies to R-mode, so it would not impact the fact if we can use UO-0
packets or
> not on video streams with semi-constant TS.
> So, back to the example given by Kamal regarding the need for slope:
>
>  >>But, in most of the cases TS_SCALED will show behaviour like
>  >>
>  >> 1, 1 , 1, 1, 2, 2, 2, 2, 2, 2, 2, 3, 4, 5 in case of video.
>  >>
>  >> 1, 2, 3, 4, 6, 7, 7, 8, 9, 10  possibly in case of audio
>  >>
>  >> in "above" case of video slope will be 0 most of the time and
>  >> 1 sometimes.
>  >> And in "above" case of audio slope will be 1 most of the time
>  >> for audio.
>
> Let's say that the unscaled TS in the video example will be 30 and the
starting
> value 10, then we'd have this:
>
> 10, 10, 10, 10, 40, 40, 40, 40, 40, 40, 40, 70, 100, 130
>
> As you observe, the "video slope will be 0 most of the time". This is the
> observation that your compressor also should make, and therefore use a
TS_STRIDE
> of 0.
> What we can do when the TS changes from 10 to 40 is that we can interpret
this
> as a change of TS_OFFSET instead of saying that TS_STRIDE (or slope)
changes.
> So we keep the TS_STRIDE as 0, but change TS_OFFSET from 10 to 40, which
we do
> by sending some UOR-2-ext3 with an unscaled timestamp according to the
> optimistic approach, and then move back to sending UO-0 packets. This
without

Here, I would like refine a bit. If TS_OFFSET has to be communicated then
absolute TS
and TS_STRIDE both should be sent (L times) if we follow RFC and according
to the section quoted above we come to initialisation phase (and go back to
FO state). So, we can add a TS_STRIDE field and there will be no problem in
above method.

One small point is that can TS module 0 create any problem like division by
zero? But, even if it creates problem it can still be assumed that if
TS_STRIDE = 0 then TS_OFFSET = TS.

Other point is that it is an impression from RFC that TS_STRIDE and
TS_OFFSET (especially) are parameters which remain stable and do not change.
but, we are updating them very frequently.

> ever having to change the TS_STRIDE. The sliding window depth should not
impact
> here even if it is larger than the number of packets, we are in U/O-mode
where
> we use the optimistic approach.
>

fine


> When we reach the later parts of Kamal's example (3,4,5,...), then the
> compressor will probably note that a change of 30 will be more frequent
than the
> constant TS, and will after a while establish a TS_STRIDE of 30. If it
does not,
> then it could update the offset as above wuthout causing extra packet
losses.

Here, I have problem with the method. Perhaps because I dont know more
details about the above method.

We communicate TS_STRIDE = 30 with Abs TS.
After sending them L times we are sure that decompressor has
TS_STRIDE = 30
and TS_OFFSET = TS/30 = 40 in above case.

Now, if TS continues the same pattern then
 in the equation TS = TS_SCALED * TS_STRIDE + TS_OFFSET

TS_SCALED will always be missing. Hence, decompressor will need it.

This can be done by sendign TS_SCALED "lsb bits".
But, as soon as we stop sending these bits(UO_0), the decompressor has no
clue about TS_SCALED. And diff decompreessors can show diff behaviours. For
e.g. one can assume TS_SCALED constant but, it will lead to incorrect
computation of TS.
Other decompressor can say that TS_SCALED was increasing with a delta of 1
with SN so decompresor can assume that if TS_SCALED was not send then it can
use TS_SCALED_PREV + 1 (per increase of 1 in SN).

BUT, that will also be called a "slope of TS_SCALED"


regards,
Kamal



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



From exim@www1.ietf.org  Thu Mar 25 18:14:09 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01642
	for <rohc-archive@odin.ietf.org>; Thu, 25 Mar 2004 18:14:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6e2g-00030o-3C
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 18:13:43 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PNDgWu011568
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 18:13:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6e2f-00030Q-Uo
	for rohc-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 18:13:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01559
	for <rohc-web-archive@ietf.org>; Thu, 25 Mar 2004 18:13:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6e2d-0003AR-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 18:13:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6e1i-00037N-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 18:12:42 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6e10-00034H-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 18:11:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6e12-0002XL-NL; Thu, 25 Mar 2004 18:12:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6e0c-0002Oy-Mi
	for rohc@optimus.ietf.org; Thu, 25 Mar 2004 18:11:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01294
	for <rohc@ietf.org>; Thu, 25 Mar 2004 18:11:30 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6e0Z-00031F-00
	for rohc@ietf.org; Thu, 25 Mar 2004 18:11:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6dzc-0002vr-00
	for rohc@ietf.org; Thu, 25 Mar 2004 18:10:33 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6dyk-0002qQ-00
	for rohc@ietf.org; Thu, 25 Mar 2004 18:09:38 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B6dyi-0007tn-54
	for rohc@ietf.org; Thu, 25 Mar 2004 18:09:38 -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 i2PMwe420811;
	Fri, 26 Mar 2004 00:58:40 +0200 (EET)
X-Scanned: Fri, 26 Mar 2004 00:58:15 +0200 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i2PMwFQj028161;
	Fri, 26 Mar 2004 00:58:15 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 00GbFxOo; Fri, 26 Mar 2004 00:58:14 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 i2PMwCs09140;
	Fri, 26 Mar 2004 00:58:13 +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, 25 Mar 2004 16:58:10 -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] Slope used to compress/decompress RTP Timestamp field
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Thu, 25 Mar 2004 17:58:10 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B8153714@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] Slope used to compress/decompress RTP Timestamp field
Thread-Index: AcQSdABdnLMddZlDQlSfZZwtBmeuxAANTxcw
To: <kristofer.sandlund@effnet.com>, <szym_paw@wp.pl>
Cc: <kd.singh@enst-bretagne.fr>, <lars-erik.jonsson@ericsson.com>,
        <rohc@ietf.org>
X-OriginalArrivalTime: 25 Mar 2004 22:58:10.0968 (UTC) FILETIME=[A54D6180:01C412BC]
Content-Transfer-Encoding: quoted-printable
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Kristofer,

> For this discussion, let us limit ourselves for a possible=20
> slope used by the TS field, since that's really what we are=20
> discussion here and not use the "non-SN-field" term too much.

Although the question was raised due to TS, I'd like to emphasize=20
that the concept of slope is not only for TS. As Kamal pointed out,=20
slope is one parameter of the function (see text below from section =
3.4).

   The way ROHC RTP compression operates, then, is to first establish
   functions from SN to the other fields, and then reliably communicate
   the SN.  Whenever a function from SN to another field changes, i.e.,
   the existing function gives a result which is different from the
   field in the header to be compressed, additional information is sent
   to update the parameters of that function.

> I believe that as the specis written, there cannot be room=20
> for a slope that can be implicitly updated.=20

Actually this is not true. We had the slope in mind when writing the =
RFC.
Also see below.

> I base this on the following observations:
>=20
> * 4.5.3. Scaled RTP Timestamp encoding
>     3. Decompression: When receiving the compressed value of=20
> 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.
>=20
> If there acutally was a slope, it should have been in this formula.

This is a misunderstanding. Note that there are two *separate* steps
involved. The formula is for the second step: deriving TS from =
TS_SCALED.=20
The slope plays a role in the first step: "the decompressor first =
derives=20
the value of the original TS_SCALED". I thought this is clear from
section 4.5.3. More clarifications below.

> * 5.5.1.2.  Compression logic and packets used (R-mode)
>      --non-SN-field =3D SN * slope + offset
>=20
> I am convinced that this is just written to be general for=20
> possible future profiles (with other fields than TS being sent=20
> in a scaled fashion), if we narrow this down to TS, then we=20
> get TS =3D SN * slope + offset. Compare this to the formula in
> 4.5.3 (quoted above), then suddenly it becomes=20
> clear that "slope" really means TS_STRIDE in this section.

Now I can see where the confusion came from. Some clarifications:

a) No, the formula is not for future profiles. It had never been
the intension. We actually have been trying hard to reduce number of=20
profiles, which may lead to interoperability issues.

b) The formula is really just an explanation of the fundamental
concept of function mentioned in previous sections.

c) The slope concept, as part of the overall FO/SO concept, came=20
before the scale concept. Scaling was added later on top of the=20
basic compression/decompression operation (i.e.. the function),
and it applies only to TS field.

d) As explained above and in section 4.5.3, the scaling and the
compression of scaled TS are two *separate* steps. And more important,
they are two *different* concepts, although the formula looks similar.
+ Scaling is a LOCAL concept, except the synchronization of TS_STRIDE.
+ With scaling, the compressor and decompressor still need to deal with=20
the effect of packet loss/misordering on the scaled TS.=20
+ TS_OFFSET is different from the offset in above formula. TS_OFFSET=20
can be derived locally as by calculating TS modulo TS_STRIDE. Obviously,
it's not an independent variable (it depends on TS_STRIDE). On the =
contrary,=20
offset has to be synchronized explicitly to the decompressor and it=20
is one of the independent variables in the function from SN to
non-SN-field (offset does NOT depend on slope).=20

BR,
Zhigang

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



From exim@www1.ietf.org  Thu Mar 25 18:59:02 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03844
	for <rohc-archive@odin.ietf.org>; Thu, 25 Mar 2004 18:59:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ek8-0007gX-Jc
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 18:58:36 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PNwaF7029541
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 18:58:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ek8-0007gO-FC
	for rohc-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 18:58:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03837
	for <rohc-web-archive@ietf.org>; Thu, 25 Mar 2004 18:58:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ek5-0005pE-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 18:58:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6ejA-0005nA-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 18:57:36 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6eiY-0005lE-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 18:56:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6eia-0007a6-PB; Thu, 25 Mar 2004 18:57:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ei9-0007Yv-OI
	for rohc@optimus.ietf.org; Thu, 25 Mar 2004 18:56:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03776
	for <rohc@ietf.org>; Thu, 25 Mar 2004 18:56:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ei6-0005jC-00
	for rohc@ietf.org; Thu, 25 Mar 2004 18:56:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6ehF-0005g7-00
	for rohc@ietf.org; Thu, 25 Mar 2004 18:55:38 -0500
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6egB-0005cN-00
	for rohc@ietf.org; Thu, 25 Mar 2004 18:54:31 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <1ZGMTKDA>; Thu, 25 Mar 2004 23:53:54 -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 1ZGNFM4H; Thu, 25 Mar 2004 23:53:52 -0000
From: "West, Mark" <mark.a.west@roke.co.uk>
To: zhigang.c.liu@nokia.com
Cc: cthakker@ipnetfusion.com, johnyjsmith1970@hotmail.com, rohc@ietf.org
Date: Thu, 25 Mar 2004 23:53:52 +0000 (GMT)
X-X-Sender: maw@mjw-pc.roke.co.uk
Subject: RE: [rohc] SIP dialog and SigComp compartments relationship
In-Reply-To: <7B5AF06E216CB74DA8A5960A3181B5B8153712@ajebe001.americas.nokia.com>
Message-ID: <Pine.LNX.4.44.0403252344040.15667-100000@mjw-pc.roke.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


Hi all,

Some more comments...

> > Additionally is it useful to have a different
> > compression algorithm for every dialog that is established ?
>
> The sender can choose whichever algorithm for a dialog, or even for
> a message, as long as the decompression bytecode is made available
> to the remote receiver. So, it's more related to state than compartment.

Absolutely -- this is the heart of the sigcomp world-view: only the
decompressor is defined; the compressor can do whatever it likes, so long
as it fits.  And the granularity of data-access is state.

Algorithms are expressed (within sigcomp) as bytecode.  Depending upon the
application (SIP), you could use different bytecode for each dialog, or
keep it the same.  Hopefully your compressor makes the choice as best it
can to achieve the best overall efficiency...

>
> > (3320 talks about the compression algorithm being a characteristic of the
> > compartment).
>
> I have to double check the text in RFC 3320. But I think it is not the
> intention to limit an implementation.
>

It is absolutely not the intention to limit an implemention (other than by
the rules for decompression/UDVM).  A compartment may have one or more
compression algorithms associated with it [== state-items containing
bytecode].  How this is managed, of course, is a non-trivial
implementation issue.  But there is nothing in 3320 that stops you having
an arbitrary number of compression algorithms stored at the decompressor
and choosing between these (or even uploading a new one) as the compressor
sees fit...

Cheers,

Mark.


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



From exim@www1.ietf.org  Thu Mar 25 20:29:14 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07524
	for <rohc-archive@odin.ietf.org>; Thu, 25 Mar 2004 20:29:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6g9O-00061o-P8
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 20:28:46 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2Q1SkEJ023166
	for rohc-archive@odin.ietf.org; Thu, 25 Mar 2004 20:28:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6g9O-00061Z-L1
	for rohc-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 20:28:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07514
	for <rohc-web-archive@ietf.org>; Thu, 25 Mar 2004 20:28:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6g9M-0004GY-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 20:28:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6g8V-0004B9-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 20:27:52 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6g7f-00044S-00
	for rohc-web-archive@ietf.org; Thu, 25 Mar 2004 20:26:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6g7g-0005v2-GY; Thu, 25 Mar 2004 20:27:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6g7S-0005to-1T
	for rohc@optimus.ietf.org; Thu, 25 Mar 2004 20:26:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07433
	for <rohc@ietf.org>; Thu, 25 Mar 2004 20:26:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6g7Q-00042W-00
	for rohc@ietf.org; Thu, 25 Mar 2004 20:26:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6g6Q-0003xB-00
	for rohc@ietf.org; Thu, 25 Mar 2004 20:25:43 -0500
Received: from [216.90.186.146] (helo=mail.ipnetfusion.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6g5Q-0003t3-00
	for rohc@ietf.org; Thu, 25 Mar 2004 20:24:40 -0500
Received: from ipnetfusion.com (proxy.ipnetfusion.com [216.90.186.147])
	(authenticated)
	by mail.ipnetfusion.com (8.11.6/8.11.6) with ESMTP id i2Q1NpG03119;
	Thu, 25 Mar 2004 19:23:51 -0600
Message-ID: <40638679.5010903@ipnetfusion.com>
Date: Thu, 25 Mar 2004 19:25:13 -0600
From: Simran Suri <ssuri@ipnetfusion.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
CC: rohc@ietf.org
Subject: Re: [rohc] Record Marking in SigComp
References: <OF85843B27.1BB82406-ON65256E56.001D6126@lntinfotech.com> <03ba01c40a80$62eb83b0$ee4a34c1@rennes.enstbretagne.fr> <4056E6A6.3070705@ericsson.com> <00fe01c411e3$899af9e0$ee4a34c1@rennes.enstbretagne.fr> <4062301B.4090108@ipnetfusion.com> <A41CDDD4-7E2D-11D8-9A3A-000A95DC4DB6@tzi.org>
In-Reply-To: <A41CDDD4-7E2D-11D8-9A3A-000A95DC4DB6@tzi.org>
Content-Type: multipart/alternative;
 boundary="------------080207040108000006030403"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.1 required=5.0 tests=AWL,HTML_30_40,HTML_MESSAGE,
	HTML_TITLE_EMPTY autolearn=no version=2.60

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

Hi Carsten,
Just a small point : in the passage below, do you mean the 'compressor' 
OR do you mean the 'compression dispatcher'? Also, is the record marking 
performed on the compressed data(which goes into the 'remaining SigComp 
message' field) or is it performed on the whole SigComp message passed 
down to the TCP layer?
Am I missing something here?
Thanks,
Simran

Carsten Bormann wrote:

> RFC3320 section 4.2.2 says:
>
> 4.2.2.  Record Marking
>
>    For a stream-based transport, the dispatcher delimits messages by
>    parsing the compressed data stream for instances of 0xFF and taking
>    the following actions:
>
>    Occurs in data stream:     Action:
>
>    0xFF 00                    one 0xFF byte in the data stream
>    0xFF 01                    same, but the next byte is quoted (could
>                               be another 0xFF)
>       :                                           :
>    0xFF 7F                    same, but the next 127 bytes are quoted
>    0xFF 80 to 0xFF FE         (reserved for future standardization)
>    0xFF FF                    end of SigComp message
>
> So, a simple compressor could simply replace every 0xFF by 0xFF 0x00.
> A more advanced compressor will probably look out for any additional 
> 0xFF in the stream and use the alternate forms to save escape bytes.
>
> Gruesse, Carsten
>

--------------080207040108000006030403
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000099">
Hi Carsten,<br>
Just a small point : in the passage below, do you mean the 'compressor'
OR do you mean the 'compression dispatcher'? Also, is the record
marking performed on
the compressed data(which goes into the 'remaining SigComp message'
field) or is it performed on the whole SigComp message passed down to
the TCP layer? <br>
Am I missing something here?<br>
Thanks,<br>
Simran<br>
<br>
Carsten Bormann wrote:<br>
<blockquote cite="midA41CDDD4-7E2D-11D8-9A3A-000A95DC4DB6@tzi.org"
 type="cite">RFC3320 section 4.2.2 says:
  <br>
  <br>
4.2.2.&nbsp; Record Marking
  <br>
  <br>
&nbsp;&nbsp; For a stream-based transport, the dispatcher delimits messages by
  <br>
&nbsp;&nbsp; parsing the compressed data stream for instances of 0xFF and taking
  <br>
&nbsp;&nbsp; the following actions:
  <br>
  <br>
&nbsp;&nbsp; Occurs in data stream:&nbsp;&nbsp;&nbsp;&nbsp; Action:
  <br>
  <br>
&nbsp;&nbsp; 0xFF 00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; one 0xFF byte in the data stream
  <br>
&nbsp;&nbsp; 0xFF 01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; same, but the next byte is quoted (could
  <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; be another 0xFF)
  <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
  <br>
&nbsp;&nbsp; 0xFF 7F&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; same, but the next 127 bytes are quoted
  <br>
&nbsp;&nbsp; 0xFF 80 to 0xFF FE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (reserved for future standardization)
  <br>
&nbsp;&nbsp; 0xFF FF&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; end of SigComp message
  <br>
  <br>
So, a simple compressor could simply replace every 0xFF by 0xFF 0x00.
  <br>
A more advanced compressor will probably look out for any additional
0xFF in the stream and use the alternate forms to save escape bytes.
  <br>
  <br>
Gruesse, Carsten
  <br>
  <br>
</blockquote>
</body>
</html>

--------------080207040108000006030403--

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



From exim@www1.ietf.org  Fri Mar 26 03:10:28 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06048
	for <rohc-archive@odin.ietf.org>; Fri, 26 Mar 2004 03:10:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6mPg-0003C9-SF
	for rohc-archive@odin.ietf.org; Fri, 26 Mar 2004 03:10:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2Q8A0cd012281
	for rohc-archive@odin.ietf.org; Fri, 26 Mar 2004 03:10:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6mPg-0003C0-KQ
	for rohc-web-archive@optimus.ietf.org; Fri, 26 Mar 2004 03:10:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06014
	for <rohc-web-archive@ietf.org>; Fri, 26 Mar 2004 03:09:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6mPc-0002yC-00
	for rohc-web-archive@ietf.org; Fri, 26 Mar 2004 03:09:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6mOl-0002rH-00
	for rohc-web-archive@ietf.org; Fri, 26 Mar 2004 03:09:03 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6mNk-0002jN-00
	for rohc-web-archive@ietf.org; Fri, 26 Mar 2004 03:08:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6mNm-00030m-7p; Fri, 26 Mar 2004 03:08:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6mMs-0002m8-7s
	for rohc@optimus.ietf.org; Fri, 26 Mar 2004 03:07:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05836
	for <rohc@ietf.org>; Fri, 26 Mar 2004 03:07:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6mMo-0002cq-00
	for rohc@ietf.org; Fri, 26 Mar 2004 03:07:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6mM4-0002Xa-00
	for rohc@ietf.org; Fri, 26 Mar 2004 03:06:16 -0500
Received: from imh.informatik.uni-bremen.de ([134.102.224.4] helo=informatik.uni-bremen.de)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6mLM-0002RH-00
	for rohc@ietf.org; Fri, 26 Mar 2004 03:05:32 -0500
Received: from [IPv6:::1] (imh.informatik.uni-bremen.de [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id i2Q85STg018290;
	Fri, 26 Mar 2004 09:05:29 +0100 (MET)
In-Reply-To: <40638679.5010903@ipnetfusion.com>
References: <OF85843B27.1BB82406-ON65256E56.001D6126@lntinfotech.com> <03ba01c40a80$62eb83b0$ee4a34c1@rennes.enstbretagne.fr> <4056E6A6.3070705@ericsson.com> <00fe01c411e3$899af9e0$ee4a34c1@rennes.enstbretagne.fr> <4062301B.4090108@ipnetfusion.com> <A41CDDD4-7E2D-11D8-9A3A-000A95DC4DB6@tzi.org> <40638679.5010903@ipnetfusion.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <57A309C8-7EFC-11D8-8BB7-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, rohc@ietf.org
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] Record Marking in SigComp
Date: Fri, 26 Mar 2004 09:05:27 +0100
To: Simran Suri <ssuri@ipnetfusion.com>
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>  Just a small point : in the passage below, do you mean the 
> 'compressor' OR do you mean the 'compression dispatcher'?

The quip answer is: "I don't care".
The text says "dispatcher", but then where you do this has little 
impact on the protocol on the wire.
If you had asked whether the inverse is done in the decompressor (which 
runs in the UDVM) or the decompressor's dispatcher, there would be a 
difference, as in the first case the UDVM code would have to include 
code to handle record unmarking (it doesn't -- the UDVM gets passed 
entire messages, already unmarked).

Generally, we include passages about architecture in protocol standards 
less to structure implementations than to:
-- provide a mental model into which the reader can fit the 
explanations in the specification, and to
-- provide motivation and some general direction for the further 
development of the protocol or related protocols.
Of course, you are free to use the architecture in your implementation.

> Also, is the record marking performed on the compressed data(which 
> goes into the 'remaining SigComp message' field) or is it performed on 
> the whole SigComp message passed down to the TCP layer?

Since the purpose of the record marking is to delimit messages, it is 
applied to entire messages.

(RFC 3320 says so, too:

4.2.2.  Record Marking

    For a stream-based transport, the dispatcher delimits messages by
    parsing ...
)

Gruesse, Carsten


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



From exim@www1.ietf.org  Fri Mar 26 03:38:24 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07268
	for <rohc-archive@odin.ietf.org>; Fri, 26 Mar 2004 03:38:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6mqg-0004ip-Bl
	for rohc-archive@odin.ietf.org; Fri, 26 Mar 2004 03:37:55 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2Q8bsRP018148
	for rohc-archive@odin.ietf.org; Fri, 26 Mar 2004 03:37:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6mqg-0004id-2g
	for rohc-web-archive@optimus.ietf.org; Fri, 26 Mar 2004 03:37:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07259
	for <rohc-web-archive@ietf.org>; Fri, 26 Mar 2004 03:37:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6mqd-0005hx-00
	for rohc-web-archive@ietf.org; Fri, 26 Mar 2004 03:37:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6mpl-0005cH-00
	for rohc-web-archive@ietf.org; Fri, 26 Mar 2004 03:36:57 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6mor-0005Vl-00
	for rohc-web-archive@ietf.org; Fri, 26 Mar 2004 03:36:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6mos-0004MQ-Hq; Fri, 26 Mar 2004 03:36:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6mo0-0004Jf-30
	for rohc@optimus.ietf.org; Fri, 26 Mar 2004 03:35:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07147
	for <rohc@ietf.org>; Fri, 26 Mar 2004 03:35:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6mnx-0005Pw-00
	for rohc@ietf.org; Fri, 26 Mar 2004 03:35:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6mnG-0005Jx-00
	for rohc@ietf.org; Fri, 26 Mar 2004 03:34:23 -0500
Received: from smtp.wp.pl ([212.77.101.160])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6mmI-00058Q-00
	for rohc@ietf.org; Fri, 26 Mar 2004 03:33:22 -0500
Received: (wp-smtpd smtp.wp.pl 4708 invoked from network); 26 Mar 2004 09:32:48 +0100
Received: from ofree.wp-sa.pl (HELO localhost) ([212.77.101.203])
          (envelope-sender <szym_paw@wp.pl>)
          by smtp.wp.pl (wp-smtpd) with SMTP
          for <zhigang.c.liu@nokia.com>; 26 Mar 2004 09:32:48 +0100
Date: Fri, 26 Mar 2004 09:32:45 +0100
From: "Pawel Szymanski" <szym_paw@wp.pl>
To: zhigang.c.liu@nokia.com
Cc: kristofer.sandlund@effnet.com, kd.singh@enst-bretagne.fr,
        lars-erik.jonsson@ericsson.com, rohc@ietf.org
Subject: RE: [rohc] Slope used to compress/decompress RTP Timestamp field
Message-ID: <4063eaade00af@wp.pl>
References: <7B5AF06E216CB74DA8A5960A3181B5B8153714@ajebe001.americas.nokia.com>
In-reply-to: <7B5AF06E216CB74DA8A5960A3181B5B8153714@ajebe001.americas.nokia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-2
Content-Disposition: inline
X-Mailer: Interfejs WWW poczty Wirtualnej Polski
Organization: Poczta Wirtualnej Polski S.A. http://www.wp.pl/
X-IP: 192.55.37.193, 172.28.173.14
X-AntiVirus: skaner antywirusowy poczty Wirtualnej Polski S. A. [wersja 2.0c]
X-WP-AntySpam-Rezultat: NIE-SPAM
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id DAA07148
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi Zhigang,

> > I base this on the following observations:
> >=20
> > * 4.5.3. Scaled RTP Timestamp encoding
> >     3. Decompression: When receiving the compressed value of=20
> > 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.
> >=20
> > If there acutally was a slope, it should have been in this formula.
>=20
> This is a misunderstanding. Note that there are two *separate* steps
> involved. The formula is for the second step: deriving TS from TS_SCALE=
D.=20
> The slope plays a role in the first step: "the decompressor first deriv=
es=20
> the value of the original TS_SCALED". I thought this is clear from
> section 4.5.3. More clarifications below.

I think that the decompressor uses slope when it receives packets without=
 TS=20
field (for example UO-0 packets).=20

In this case it uses the formula to calculate new scaled timestamp value:
 =20
   new_scaled_timestamp =3D old_scaled_timestamp + (new_SN - old_SN)*slop=
e

Next it calculates the unscaled timestamp using the formula from 4.5.3

When the decompressor receives a packet with TS field, it does not use sl=
ope.=20
It decompresses the new scaled timestamp value using LSB method. Next it =
uses=20
the formula from 4.5.3 to calculate the unscaled timestamp.=20

When the decompressor receives two or more packets containing TS value in=
 raw,=20
it can calculate a new slope value, for example using the formula:

  new_slope =3D (new_scaled_timestamp - old_scaled_timestamp) / (new_SN -=
 old_SN)

Am I correct ?

An additional question is whether the slope is an integer number or could=
 it be=20
a floating point number ?

Regards=20

Pawel


----------------------------------------------------
Zobacz niezwyk=B3y koncert: "Niemena Pami=EAci Gda=F1ski Rapsod"
Najwi=EAksze przeboje artysty w nowych zaskakuj=B1cych aran=BFacjach.
http://klik.wp.pl/?adr=3Dhttp%3A%2F%2Fmuzyka.wp.pl%2Fimprezy.html%3Fidn%3=
D874&sid=3D151



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



From exim@www1.ietf.org  Fri Mar 26 10:00:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22982
	for <rohc-archive@odin.ietf.org>; Fri, 26 Mar 2004 10:00:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6soU-0002q1-1Z
	for rohc-archive@odin.ietf.org; Fri, 26 Mar 2004 10:00:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2QF01kL010903
	for rohc-archive@odin.ietf.org; Fri, 26 Mar 2004 10:00:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6soT-0002pm-Rs
	for rohc-web-archive@optimus.ietf.org; Fri, 26 Mar 2004 10:00:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22894
	for <rohc-web-archive@ietf.org>; Fri, 26 Mar 2004 09:59:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6soR-00033Y-00
	for rohc-web-archive@ietf.org; Fri, 26 Mar 2004 09:59:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6snU-0002zW-00
	for rohc-web-archive@ietf.org; Fri, 26 Mar 2004 09:59:01 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6smW-0002uM-00
	for rohc-web-archive@ietf.org; Fri, 26 Mar 2004 09:58:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6smX-0002kV-49; Fri, 26 Mar 2004 09:58:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6sli-0002jf-1r
	for rohc@optimus.ietf.org; Fri, 26 Mar 2004 09:57:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22760
	for <rohc@ietf.org>; Fri, 26 Mar 2004 09:57:06 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6slg-0002sh-00
	for rohc@ietf.org; Fri, 26 Mar 2004 09:57:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6skt-0002qU-00
	for rohc@ietf.org; Fri, 26 Mar 2004 09:56:20 -0500
Received: from mgw-x2.nokia.com ([131.228.20.22])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6sk1-0002nd-00
	for rohc@ietf.org; Fri, 26 Mar 2004 09:55:25 -0500
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i2QEtMn04560;
	Fri, 26 Mar 2004 16:55:22 +0200 (EET)
X-Scanned: Fri, 26 Mar 2004 16:54:48 +0200 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i2QEsmoH026485;
	Fri, 26 Mar 2004 16:54:48 +0200
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks004.ntc.nokia.com 00Bi2mqZ; Fri, 26 Mar 2004 16:51:12 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 i2QEpAF19145;
	Fri, 26 Mar 2004 16:51:10 +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, 26 Mar 2004 08:51:09 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] Slope used to compress/decompress RTP Timestamp field
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Fri, 26 Mar 2004 09:51:09 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B8153717@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] Slope used to compress/decompress RTP Timestamp field
Thread-Index: AcQTDPkxsMycQLETSl6LUv/N6XOvQgAMlRKg
To: <szym_paw@wp.pl>
Cc: <kristofer.sandlund@effnet.com>, <kd.singh@enst-bretagne.fr>,
        <lars-erik.jonsson@ericsson.com>, <rohc@ietf.org>
X-OriginalArrivalTime: 26 Mar 2004 14:51:09.0972 (UTC) FILETIME=[C6A4FD40:01C41341]
Content-Transfer-Encoding: quoted-printable
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi Pawel,

Yes, your understanding is correct. It's basically the geometry: two =
points determine a line. Besides the slope, two TS values also give you =
the offset.

No, RFC 3095 does not assume floating point. All encoding/decoding =
operations are integer based.

Zhigang

> -----Original Message-----
> From: ext Pawel Szymanski [mailto:szym_paw@wp.pl]
> Sent: 26 March, 2004 02:33 AM
> To: Liu Zhigang.C (Nokia-NRC/Dallas)
> Cc: kristofer.sandlund@effnet.com; kd.singh@enst-bretagne.fr;=20
> lars-erik.jonsson@ericsson.com; rohc@ietf.org
> Subject: RE: [rohc] Slope used to compress/decompress RTP=20
> Timestamp field
>=20
>=20
>=20
> Hi Zhigang,
>=20
> > > I base this on the following observations:
> > >=20
> > > * 4.5.3. Scaled RTP Timestamp encoding
> > >     3. Decompression: When receiving the compressed value of=20
> > > 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.
> > >=20
> > > If there acutally was a slope, it should have been in=20
> this formula.
> >=20
> > This is a misunderstanding. Note that there are two *separate* steps
> > involved. The formula is for the second step: deriving TS=20
> from TS_SCALED.=20
> > The slope plays a role in the first step: "the decompressor=20
> first derives=20
> > the value of the original TS_SCALED". I thought this is clear from
> > section 4.5.3. More clarifications below.
>=20
> I think that the decompressor uses slope when it receives=20
> packets without TS=20
> field (for example UO-0 packets).=20
>=20
> In this case it uses the formula to calculate new scaled=20
> timestamp value:
>  =20
>    new_scaled_timestamp =3D old_scaled_timestamp + (new_SN -=20
> old_SN)*slope
>=20
> Next it calculates the unscaled timestamp using the formula from 4.5.3
>=20
> When the decompressor receives a packet with TS field, it=20
> does not use slope.=20
> It decompresses the new scaled timestamp value using LSB=20
> method. Next it uses=20
> the formula from 4.5.3 to calculate the unscaled timestamp.=20
>=20
> When the decompressor receives two or more packets containing=20
> TS value in raw,=20
> it can calculate a new slope value, for example using the formula:
>=20
>   new_slope =3D (new_scaled_timestamp - old_scaled_timestamp) /=20
> (new_SN - old_SN)
>=20
> Am I correct ?
>=20
> An additional question is whether the slope is an integer=20
> number or could it be=20
> a floating point number ?
>=20
> Regards=20
>=20
> Pawel
>=20
>=20
> ----------------------------------------------------
> Zobacz niezwyk=B3y koncert: "Niemena Pami=EAci Gda=F1ski Rapsod"
> Najwi=EAksze przeboje artysty w nowych zaskakuj=B1cych aran=BFacjach.
> http://klik.wp.pl/?adr=3Dhttp%3A%2F%2Fmuzyka.wp.pl%2Fimprezy.htm
l%3Fidn%3D874&sid=3D151



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



From exim@www1.ietf.org  Fri Mar 26 11:20:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29465
	for <rohc-archive@odin.ietf.org>; Fri, 26 Mar 2004 11:20:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6u40-000663-8m
	for rohc-archive@odin.ietf.org; Fri, 26 Mar 2004 11:20:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2QGK8MK023432
	for rohc-archive@odin.ietf.org; Fri, 26 Mar 2004 11:20:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6u40-00065r-4V
	for rohc-web-archive@optimus.ietf.org; Fri, 26 Mar 2004 11:20:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29366
	for <rohc-web-archive@ietf.org>; Fri, 26 Mar 2004 11:20:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6u3z-0000cg-00
	for rohc-web-archive@ietf.org; Fri, 26 Mar 2004 11:20:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6u2z-0000VY-00
	for rohc-web-archive@ietf.org; Fri, 26 Mar 2004 11:19:06 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6u1y-0000Ow-00
	for rohc-web-archive@ietf.org; Fri, 26 Mar 2004 11:18:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6u1y-0005xx-0y; Fri, 26 Mar 2004 11:18:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6u1J-0005sA-JX
	for rohc@optimus.ietf.org; Fri, 26 Mar 2004 11:17:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29088
	for <rohc@ietf.org>; Fri, 26 Mar 2004 11:17:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6u1I-0000LB-00
	for rohc@ietf.org; Fri, 26 Mar 2004 11:17:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6u0H-0000G6-00
	for rohc@ietf.org; Fri, 26 Mar 2004 11:16:19 -0500
Received: from smtp.wp.pl ([212.77.101.160])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6tzs-0000Ac-00
	for rohc@ietf.org; Fri, 26 Mar 2004 11:15:52 -0500
Received: (wp-smtpd smtp.wp.pl 14919 invoked from network); 26 Mar 2004 16:45:56 +0100
Received: from ofree.wp-sa.pl (HELO localhost) ([212.77.101.203])
          (envelope-sender <szym_paw@wp.pl>)
          by smtp.wp.pl (wp-smtpd) with SMTP
          for <zhigang.c.liu@nokia.com>; 26 Mar 2004 16:45:56 +0100
Date: Fri, 26 Mar 2004 16:45:51 +0100
From: "Pawel Szymanski" <szym_paw@wp.pl>
To: zhigang.c.liu@nokia.com
Cc: kristofer.sandlund@effnet.com, kd.singh@enst-bretagne.fr,
        lars-erik.jonsson@ericsson.com, rohc@ietf.org
Subject: RE: [rohc] Slope used to compress/decompress RTP Timestamp field
Message-ID: <4064502f34286@wp.pl>
References: <7B5AF06E216CB74DA8A5960A3181B5B8153717@ajebe001.americas.nokia.com>
In-reply-to: <7B5AF06E216CB74DA8A5960A3181B5B8153717@ajebe001.americas.nokia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-2
Content-Disposition: inline
X-Mailer: Interfejs WWW poczty Wirtualnej Polski
Organization: Poczta Wirtualnej Polski S.A. http://www.wp.pl/
X-IP: 192.55.37.193, 172.28.173.14
X-AntiVirus: skaner antywirusowy poczty Wirtualnej Polski S. A. [wersja 2.0c]
X-WP-AntySpam-Rezultat: NIE-SPAM
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id LAA29089
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi Zighang,

I wonder how decompressor should behave if it receives only one packet wi=
th TS=20
field between two packets without TS ( for example when it receives UO-0=20
packet, next UO-1-TS and next again UO-0 packet).=20

I can see two options:

1. The decompressor uses the old slope value (e.g. the one it used to=20
decompress the first UO-0 packet) to calculate timestamp for the second U=
O-0=20
packet. Here we assume that single TS communicates change in the offset.

2. It calculates a new slope basing on the timestamp values decompressed =
from=20
the first UO-0 packet and the UO-1 packet and next it uses the new slope =
to=20
calculate the timestamp for the second UO-0 packet.

Which of the above is correct ?

Regards

Pawel

> Hi Pawel,
>=20
> Yes, your understanding is correct. It's basically the geometry: two po=
ints=20
determine a line. Besides the slope, two TS values also give you the offs=
et.
>=20
> No, RFC 3095 does not assume floating point. All encoding/decoding oper=
ations=20
are integer based.
>=20
> Zhigang
>=20
> > -----Original Message-----
> > From: ext Pawel Szymanski [mailto:szym_paw@wp.pl]
> > Sent: 26 March, 2004 02:33 AM
> > To: Liu Zhigang.C (Nokia-NRC/Dallas)
> > Cc: kristofer.sandlund@effnet.com; kd.singh@enst-bretagne.fr;=20
> > lars-erik.jonsson@ericsson.com; rohc@ietf.org
> > Subject: RE: [rohc] Slope used to compress/decompress RTP=20
> > Timestamp field
> >=20
> >=20
> >=20
> > Hi Zhigang,
> >=20
> > > > I base this on the following observations:
> > > >=20
> > > > * 4.5.3. Scaled RTP Timestamp encoding
> > > >     3. Decompression: When receiving the compressed value of=20
> > > > 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.
> > > >=20
> > > > If there acutally was a slope, it should have been in=20
> > this formula.
> > >=20
> > > This is a misunderstanding. Note that there are two *separate* step=
s
> > > involved. The formula is for the second step: deriving TS=20
> > from TS_SCALED.=20
> > > The slope plays a role in the first step: "the decompressor=20
> > first derives=20
> > > the value of the original TS_SCALED". I thought this is clear from
> > > section 4.5.3. More clarifications below.
> >=20
> > I think that the decompressor uses slope when it receives=20
> > packets without TS=20
> > field (for example UO-0 packets).=20
> >=20
> > In this case it uses the formula to calculate new scaled=20
> > timestamp value:
> >  =20
> >    new_scaled_timestamp =3D old_scaled_timestamp + (new_SN -=20
> > old_SN)*slope
> >=20
> > Next it calculates the unscaled timestamp using the formula from 4.5.=
3
> >=20
> > When the decompressor receives a packet with TS field, it=20
> > does not use slope.=20
> > It decompresses the new scaled timestamp value using LSB=20
> > method. Next it uses=20
> > the formula from 4.5.3 to calculate the unscaled timestamp.=20
> >=20
> > When the decompressor receives two or more packets containing=20
> > TS value in raw,=20
> > it can calculate a new slope value, for example using the formula:
> >=20
> >   new_slope =3D (new_scaled_timestamp - old_scaled_timestamp) /=20
> > (new_SN - old_SN)
> >=20
> > Am I correct ?
> >=20
> > An additional question is whether the slope is an integer=20
> > number or could it be=20
> > a floating point number ?
> >=20
> > Regards=20
> >=20
> > Pawel
> >=20
> >=20
> > ----------------------------------------------------
> > Zobacz niezwyk=B3y koncert: "Niemena Pami=EAci Gda=F1ski Rapsod"
> > Najwi=EAksze przeboje artysty w nowych zaskakuj=B1cych aran=BFacjach.
> > http://klik.wp.pl/?adr=3Dhttp%3A%2F%2Fmuzyka.wp.pl%2Fimprezy.htm
> l%3Fidn%3D874&sid=3D151
>=20
>=20
>=20
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
>=20

----------------------------------------------------
=A3odzi=B1 po Wi=B6le - najciekawsze etiudy w Warszawie.
http://klik.wp.pl/?adr=3Dhttp%3A%2F%2Ffilm.wp.pl%2Fp%2Fwiadomosc.html%3Fi=
d%3D55832&sid=3D152



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



From exim@www1.ietf.org  Fri Mar 26 11:28:34 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00027
	for <rohc-archive@odin.ietf.org>; Fri, 26 Mar 2004 11:28:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6uBi-0006Uk-KY
	for rohc-archive@odin.ietf.org; Fri, 26 Mar 2004 11:28:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2QGS6Ic024960
	for rohc-archive@odin.ietf.org; Fri, 26 Mar 2004 11:28:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6uBi-0006UV-GQ
	for rohc-web-archive@optimus.ietf.org; Fri, 26 Mar 2004 11:28:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29990
	for <rohc-web-archive@ietf.org>; Fri, 26 Mar 2004 11:28:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6uBh-0001GY-00
	for rohc-web-archive@ietf.org; Fri, 26 Mar 2004 11:28:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6uAg-0001D3-00
	for rohc-web-archive@ietf.org; Fri, 26 Mar 2004 11:27:02 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6u9i-00018s-00
	for rohc-web-archive@ietf.org; Fri, 26 Mar 2004 11:26:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6u9i-0006NL-4H; Fri, 26 Mar 2004 11:26:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6u94-0006Lz-CX
	for rohc@optimus.ietf.org; Fri, 26 Mar 2004 11:25:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29848
	for <rohc@ietf.org>; Fri, 26 Mar 2004 11:25:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6u93-00016y-00
	for rohc@ietf.org; Fri, 26 Mar 2004 11:25:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6u88-00012r-00
	for rohc@ietf.org; Fri, 26 Mar 2004 11:24:25 -0500
Received: from [216.90.186.146] (helo=mail.ipnetfusion.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6u7W-0000nY-00
	for rohc@ietf.org; Fri, 26 Mar 2004 11:23:46 -0500
Received: from ipnetfusion.com (pc223 [192.1.2.223])
	(authenticated)
	by mail.ipnetfusion.com (8.11.6/8.11.6) with ESMTP id i2QGKqG30165;
	Fri, 26 Mar 2004 10:20:52 -0600
Message-ID: <40645861.3000807@ipnetfusion.com>
Date: Fri, 26 Mar 2004 10:20:49 -0600
From: Chintan Thakker <cthakker@ipnetfusion.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030723 Thunderbird/0.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
CC: Simran Suri <ssuri@ipnetfusion.com>, rohc@ietf.org
Subject: Re: [rohc] Record Marking in SigComp
References: <OF85843B27.1BB82406-ON65256E56.001D6126@lntinfotech.com> <03ba01c40a80$62eb83b0$ee4a34c1@rennes.enstbretagne.fr> <4056E6A6.3070705@ericsson.com> <00fe01c411e3$899af9e0$ee4a34c1@rennes.enstbretagne.fr> <4062301B.4090108@ipnetfusion.com> <A41CDDD4-7E2D-11D8-9A3A-000A95DC4DB6@tzi.org> <40638679.5010903@ipnetfusion.com> <57A309C8-7EFC-11D8-8BB7-000A95DC4DB6@tzi.org>
In-Reply-To: <57A309C8-7EFC-11D8-8BB7-000A95DC4DB6@tzi.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

But the UDVM can say it is an end of a message when it sees END-MESSAGE.

In that case (when the actual message is escaped by the compressor) is a 
0xFF taken as an indication of END-MESSAGE by the decompressor in the UDVM ?

Thanks,

Carsten Bormann wrote:

>>  Just a small point : in the passage below, do you mean the 
>> 'compressor' OR do you mean the 'compression dispatcher'?
>
>
> The quip answer is: "I don't care".
> The text says "dispatcher", but then where you do this has little 
> impact on the protocol on the wire.
> If you had asked whether the inverse is done in the decompressor 
> (which runs in the UDVM) or the decompressor's dispatcher, there would 
> be a difference, as in the first case the UDVM code would have to 
> include code to handle record unmarking (it doesn't -- the UDVM gets 
> passed entire messages, already unmarked).
>
> Generally, we include passages about architecture in protocol 
> standards less to structure implementations than to:
> -- provide a mental model into which the reader can fit the 
> explanations in the specification, and to
> -- provide motivation and some general direction for the further 
> development of the protocol or related protocols.
> Of course, you are free to use the architecture in your implementation.
>
>> Also, is the record marking performed on the compressed data(which 
>> goes into the 'remaining SigComp message' field) or is it performed 
>> on the whole SigComp message passed down to the TCP layer?
>
>
> Since the purpose of the record marking is to delimit messages, it is 
> applied to entire messages.
>
> (RFC 3320 says so, too:
>
> 4.2.2.  Record Marking
>
>    For a stream-based transport, the dispatcher delimits messages by
>    parsing ...
> )
>
> 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 exim@www1.ietf.org  Fri Mar 26 17:43:53 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22163
	for <rohc-archive@odin.ietf.org>; Fri, 26 Mar 2004 17:43:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B702w-0001Yv-0K
	for rohc-archive@odin.ietf.org; Fri, 26 Mar 2004 17:43:27 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2QMhPOm006004
	for rohc-archive@odin.ietf.org; Fri, 26 Mar 2004 17:43:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B702v-0001Yl-Rh
	for rohc-web-archive@optimus.ietf.org; Fri, 26 Mar 2004 17:43:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22141
	for <rohc-web-archive@ietf.org>; Fri, 26 Mar 2004 17:43:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B702t-0001Qf-00
	for rohc-web-archive@ietf.org; Fri, 26 Mar 2004 17:43:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7020-0001N9-00
	for rohc-web-archive@ietf.org; Fri, 26 Mar 2004 17:42:29 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B701d-0001JP-00
	for rohc-web-archive@ietf.org; Fri, 26 Mar 2004 17:42:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B701a-0001Us-3Q; Fri, 26 Mar 2004 17:42:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B700s-0001So-RB
	for rohc@optimus.ietf.org; Fri, 26 Mar 2004 17:41:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22026
	for <rohc@ietf.org>; Fri, 26 Mar 2004 17:41:14 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B700q-0001FM-00
	for rohc@ietf.org; Fri, 26 Mar 2004 17:41:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6zzs-00016H-00
	for rohc@ietf.org; Fri, 26 Mar 2004 17:40:17 -0500
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6zyt-0000wQ-00
	for rohc@ietf.org; Fri, 26 Mar 2004 17:39:16 -0500
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i2QMdDD29527;
	Sat, 27 Mar 2004 00:39:13 +0200 (EET)
X-Scanned: Sat, 27 Mar 2004 00:38:53 +0200 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i2QMcrqe022995;
	Sat, 27 Mar 2004 00:38:53 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 00lkL77C; Sat, 27 Mar 2004 00:38:51 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 i2QMcns00020;
	Sat, 27 Mar 2004 00:38:49 +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, 26 Mar 2004 16:38:48 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] Slope used to compress/decompress RTP Timestamp field
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Fri, 26 Mar 2004 17:38:46 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B815371A@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] Slope used to compress/decompress RTP Timestamp field
Thread-Index: AcQTTbZWZQjswtQqRlGTKMKiaOzySQAM0I+g
To: <szym_paw@wp.pl>
Cc: <kristofer.sandlund@effnet.com>, <kd.singh@enst-bretagne.fr>,
        <lars-erik.jonsson@ericsson.com>, <rohc@ietf.org>
X-OriginalArrivalTime: 26 Mar 2004 22:38:48.0676 (UTC) FILETIME=[1AEF7240:01C41383]
Content-Transfer-Encoding: quoted-printable
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi Pawel,

Actually for robustness, the compressor must make sure that at least two =
("FO") packets with TS field have been received by the decompressor =
before it can transit to SO state and send Type-0 packets. It will =
ensure that the decompressor acquires both slope and offset of the =
function from SN to TS.=20

4.3.1.3.  Second Order (SO) State

   This is the state where compression is optimal.  The compressor
   enters the SO state when the header to be compressed is completely
   predictable given the SN (RTP Sequence Number) and the compressor is
   sufficiently confident that the decompressor has acquired all
   parameters of the functions from SN to other fields

BR,
Zhigang

>=20
> Hi Zighang,
>=20
> I wonder how decompressor should behave if it receives only=20
> one packet with TS=20
> field between two packets without TS ( for example when it=20
> receives UO-0=20
> packet, next UO-1-TS and next again UO-0 packet).=20
>=20
> I can see two options:
>=20
> 1. The decompressor uses the old slope value (e.g. the one it used to=20
> decompress the first UO-0 packet) to calculate timestamp for=20
> the second UO-0  packet. Here we assume that single TS communicates =
change in=20
> the offset.
>=20
> 2. It calculates a new slope basing on the timestamp values=20
> decompressed from  the first UO-0 packet and the UO-1 packet and next =
it uses=20
> the new slope to calculate the timestamp for the second UO-0 packet.
>=20
> Which of the above is correct ?
>=20
> Regards
>=20
> Pawel
>=20
> > Hi Pawel,
> >=20
> > Yes, your understanding is correct. It's basically the=20
> geometry: two points=20
> determine a line. Besides the slope, two TS values also give=20
> you the offset.
> >=20
> > No, RFC 3095 does not assume floating point. All=20
> encoding/decoding operations=20
> are integer based.
> >=20
> > Zhigang
> >=20
> > > -----Original Message-----
> > > From: ext Pawel Szymanski [mailto:szym_paw@wp.pl]
> > > Sent: 26 March, 2004 02:33 AM
> > > To: Liu Zhigang.C (Nokia-NRC/Dallas)
> > > Cc: kristofer.sandlund@effnet.com; kd.singh@enst-bretagne.fr;=20
> > > lars-erik.jonsson@ericsson.com; rohc@ietf.org
> > > Subject: RE: [rohc] Slope used to compress/decompress RTP=20
> > > Timestamp field
> > >=20
> > >=20
> > >=20
> > > Hi Zhigang,
> > >=20
> > > > > I base this on the following observations:
> > > > >=20
> > > > > * 4.5.3. Scaled RTP Timestamp encoding
> > > > >     3. Decompression: When receiving the compressed value of=20
> > > > > TS_SCALED,
> > > > >        the decompressor first derives the value of=20
> the original
> > > > >        TS_SCALED.  The original RTP TS is then=20
> calculated as TS =3D
> > > > >        TS_SCALED * TS_STRIDE + TS_OFFSET.
> > > > >=20
> > > > > If there acutally was a slope, it should have been in=20
> > > this formula.
> > > >=20
> > > > This is a misunderstanding. Note that there are two=20
> *separate* steps
> > > > involved. The formula is for the second step: deriving TS=20
> > > from TS_SCALED.=20
> > > > The slope plays a role in the first step: "the decompressor=20
> > > first derives=20
> > > > the value of the original TS_SCALED". I thought this is=20
> clear from
> > > > section 4.5.3. More clarifications below.
> > >=20
> > > I think that the decompressor uses slope when it receives=20
> > > packets without TS=20
> > > field (for example UO-0 packets).=20
> > >=20
> > > In this case it uses the formula to calculate new scaled=20
> > > timestamp value:
> > >  =20
> > >    new_scaled_timestamp =3D old_scaled_timestamp + (new_SN -=20
> > > old_SN)*slope
> > >=20
> > > Next it calculates the unscaled timestamp using the=20
> formula from 4.5.3
> > >=20
> > > When the decompressor receives a packet with TS field, it=20
> > > does not use slope.=20
> > > It decompresses the new scaled timestamp value using LSB=20
> > > method. Next it uses=20
> > > the formula from 4.5.3 to calculate the unscaled timestamp.=20
> > >=20
> > > When the decompressor receives two or more packets containing=20
> > > TS value in raw,=20
> > > it can calculate a new slope value, for example using the formula:
> > >=20
> > >   new_slope =3D (new_scaled_timestamp - old_scaled_timestamp) /=20
> > > (new_SN - old_SN)
> > >=20
> > > Am I correct ?
> > >=20
> > > An additional question is whether the slope is an integer=20
> > > number or could it be=20
> > > a floating point number ?
> > >=20
> > > Regards=20
> > >=20
> > > Pawel
> > >=20
> > >=20
> > > ----------------------------------------------------
> > > Zobacz niezwyk=B3y koncert: "Niemena Pami=EAci Gda=F1ski Rapsod"
> > > Najwi=EAksze przeboje artysty w nowych zaskakuj=B1cych =
aran=BFacjach.
> > > http://klik.wp.pl/?adr=3Dhttp%3A%2F%2Fmuzyka.wp.pl%2Fimprezy.htm
> > l%3Fidn%3D874&sid=3D151
> >=20
> >=20
> >=20
> > _______________________________________________
> > Rohc mailing list
> > Rohc@ietf.org
> > https://www1.ietf.org/mailman/listinfo/rohc
> >=20
>=20
> ----------------------------------------------------
> =A3odzi=B1 po Wi=B6le - najciekawsze etiudy w Warszawie.
> http://klik.wp.pl/?adr=3Dhttp%3A%2F%2Ffilm.wp.pl%2Fp%2Fwiadomosc
.html%3Fid%3D55832&sid=3D152



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



From exim@www1.ietf.org  Sat Mar 27 10:27:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17354
	for <rohc-archive@odin.ietf.org>; Sat, 27 Mar 2004 10:27:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7FiA-00056T-5J
	for rohc-archive@odin.ietf.org; Sat, 27 Mar 2004 10:27:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2RFR280019616
	for rohc-archive@odin.ietf.org; Sat, 27 Mar 2004 10:27:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7Fi9-00056H-86
	for rohc-web-archive@optimus.ietf.org; Sat, 27 Mar 2004 10:27:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17331
	for <rohc-web-archive@ietf.org>; Sat, 27 Mar 2004 10:26:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7Fi6-0004RZ-00
	for rohc-web-archive@ietf.org; Sat, 27 Mar 2004 10:26:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7Fh9-0004LG-00
	for rohc-web-archive@ietf.org; Sat, 27 Mar 2004 10:26:00 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7FgD-0004Fd-00
	for rohc-web-archive@ietf.org; Sat, 27 Mar 2004 10:25:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7FgE-00051B-C3; Sat, 27 Mar 2004 10:25:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7FgA-0004zh-Ad
	for rohc@optimus.ietf.org; Sat, 27 Mar 2004 10:24:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17262
	for <rohc@ietf.org>; Sat, 27 Mar 2004 10:24:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7Fg8-0004Ea-00
	for rohc@ietf.org; Sat, 27 Mar 2004 10:24:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7FfF-00049e-00
	for rohc@ietf.org; Sat, 27 Mar 2004 10:24:02 -0500
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7Fek-00043f-00
	for rohc@ietf.org; Sat, 27 Mar 2004 10:23:30 -0500
Received: from courrier.rennes.enst-bretagne.fr (f1-clust.rennes.enst-bretagne.fr [193.52.74.16])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with ESMTP id i2RFMpd22945;
	Sat, 27 Mar 2004 16:22:51 +0100
Received: from pcrsm7 ([193.52.74.238])
	by courrier.rennes.enst-bretagne.fr (8.12.11/8.12.11/2004.01.01) with SMTP id i2RFMoex016739;
	Sat, 27 Mar 2004 16:22:50 +0100 (MET)
Message-ID: <022701c4140f$5e820220$ee4a34c1@rennes.enstbretagne.fr>
From: "kamal deep singh" <kd.singh@enst-bretagne.fr>
To: <zhigang.c.liu@nokia.com>, <szym_paw@wp.pl>
Cc: <kristofer.sandlund@effnet.com>, <lars-erik.jonsson@ericsson.com>,
        <rohc@ietf.org>
References: <7B5AF06E216CB74DA8A5960A3181B5B815371A@ajebe001.americas.nokia.com>
Subject: Re: [rohc] Slope used to compress/decompress RTP Timestamp field
Date: Sat, 27 Mar 2004 16:22:49 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-2"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by laposte.rennes.enst-bretagne.fr id i2RFMpd22945
Content-Transfer-Encoding: quoted-printable
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi,

I have one question below.

> Actually for robustness, the compressor must make sure that at least tw=
o
("FO") packets with TS >field have been received by the decompressor befo=
re
it can transit to SO state and send Type-0 >packets. It will ensure that =
the
decompressor acquires both slope and offset of the function from >SN to T=
S.

In U and O mode, how will compressor base its confidence?
By sending L + 1 or 2L packets?

Or should it be left as an implementation choice?


regards,
Kamal




> 4.3.1.3.  Second Order (SO) State
>
>    This is the state where compression is optimal.  The compressor
>    enters the SO state when the header to be compressed is completely
>    predictable given the SN (RTP Sequence Number) and the compressor is
>    sufficiently confident that the decompressor has acquired all
>    parameters of the functions from SN to other fields
>
> BR,
> Zhigang
>
> >
> > Hi Zighang,
> >
> > I wonder how decompressor should behave if it receives only
> > one packet with TS
> > field between two packets without TS ( for example when it
> > receives UO-0
> > packet, next UO-1-TS and next again UO-0 packet).
> >
> > I can see two options:
> >
> > 1. The decompressor uses the old slope value (e.g. the one it used to
> > decompress the first UO-0 packet) to calculate timestamp for
> > the second UO-0  packet. Here we assume that single TS communicates
change in
> > the offset.
> >
> > 2. It calculates a new slope basing on the timestamp values
> > decompressed from  the first UO-0 packet and the UO-1 packet and next=
 it
uses
> > the new slope to calculate the timestamp for the second UO-0 packet.
> >
> > Which of the above is correct ?
> >
> > Regards
> >
> > Pawel
> >
> > > Hi Pawel,
> > >
> > > Yes, your understanding is correct. It's basically the
> > geometry: two points
> > determine a line. Besides the slope, two TS values also give
> > you the offset.
> > >
> > > No, RFC 3095 does not assume floating point. All
> > encoding/decoding operations
> > are integer based.
> > >
> > > Zhigang
> > >
> > > > -----Original Message-----
> > > > From: ext Pawel Szymanski [mailto:szym_paw@wp.pl]
> > > > Sent: 26 March, 2004 02:33 AM
> > > > To: Liu Zhigang.C (Nokia-NRC/Dallas)
> > > > Cc: kristofer.sandlund@effnet.com; kd.singh@enst-bretagne.fr;
> > > > lars-erik.jonsson@ericsson.com; rohc@ietf.org
> > > > Subject: RE: [rohc] Slope used to compress/decompress RTP
> > > > Timestamp field
> > > >
> > > >
> > > >
> > > > Hi Zhigang,
> > > >
> > > > > > I base this on the following observations:
> > > > > >
> > > > > > * 4.5.3. Scaled RTP Timestamp encoding
> > > > > >     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.
> > > > > >
> > > > > > If there acutally was a slope, it should have been in
> > > > this formula.
> > > > >
> > > > > This is a misunderstanding. Note that there are two
> > *separate* steps
> > > > > involved. The formula is for the second step: deriving TS
> > > > from TS_SCALED.
> > > > > The slope plays a role in the first step: "the decompressor
> > > > first derives
> > > > > the value of the original TS_SCALED". I thought this is
> > clear from
> > > > > section 4.5.3. More clarifications below.
> > > >
> > > > I think that the decompressor uses slope when it receives
> > > > packets without TS
> > > > field (for example UO-0 packets).
> > > >
> > > > In this case it uses the formula to calculate new scaled
> > > > timestamp value:
> > > >
> > > >    new_scaled_timestamp =3D old_scaled_timestamp + (new_SN -
> > > > old_SN)*slope
> > > >
> > > > Next it calculates the unscaled timestamp using the
> > formula from 4.5.3
> > > >
> > > > When the decompressor receives a packet with TS field, it
> > > > does not use slope.
> > > > It decompresses the new scaled timestamp value using LSB
> > > > method. Next it uses
> > > > the formula from 4.5.3 to calculate the unscaled timestamp.
> > > >
> > > > When the decompressor receives two or more packets containing
> > > > TS value in raw,
> > > > it can calculate a new slope value, for example using the formula=
:
> > > >
> > > >   new_slope =3D (new_scaled_timestamp - old_scaled_timestamp) /
> > > > (new_SN - old_SN)
> > > >
> > > > Am I correct ?
> > > >
> > > > An additional question is whether the slope is an integer
> > > > number or could it be
> > > > a floating point number ?
> > > >
> > > > Regards
> > > >
> > > > Pawel
> > > >
> > > >
> > > > ----------------------------------------------------
> > > > Zobacz niezwyk=B3y koncert: "Niemena Pami=EAci Gda=F1ski Rapsod"
> > > > Najwi=EAksze przeboje artysty w nowych zaskakuj=B1cych aran=BFacj=
ach.
> > > > http://klik.wp.pl/?adr=3Dhttp%3A%2F%2Fmuzyka.wp.pl%2Fimprezy.htm
> > > l%3Fidn%3D874&sid=3D151
> > >
> > >
> > >
> > > _______________________________________________
> > > Rohc mailing list
> > > Rohc@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/rohc
> > >
> >
> > ----------------------------------------------------
> > =A3odzi=B1 po Wi=B6le - najciekawsze etiudy w Warszawie.
> > http://klik.wp.pl/?adr=3Dhttp%3A%2F%2Ffilm.wp.pl%2Fp%2Fwiadomosc
> .html%3Fid%3D55832&sid=3D152
>
>
>


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



From exim@www1.ietf.org  Sun Mar 28 23:22:56 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22940
	for <rohc-archive@odin.ietf.org>; Sun, 28 Mar 2004 23:22:55 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7oHt-0001V6-SI
	for rohc-archive@odin.ietf.org; Sun, 28 Mar 2004 23:22:27 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2T4MDvk005766
	for rohc-archive@odin.ietf.org; Sun, 28 Mar 2004 23:22:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7oHt-0001Uv-KX
	for rohc-web-archive@optimus.ietf.org; Sun, 28 Mar 2004 23:22:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22932
	for <rohc-web-archive@ietf.org>; Sun, 28 Mar 2004 23:22:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7oHr-0001Cn-00
	for rohc-web-archive@ietf.org; Sun, 28 Mar 2004 23:22:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7oGy-00015r-00
	for rohc-web-archive@ietf.org; Sun, 28 Mar 2004 23:21:16 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7oGZ-0000yH-00
	for rohc-web-archive@ietf.org; Sun, 28 Mar 2004 23:20:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7oFm-0001Hu-0R; Sun, 28 Mar 2004 23:20:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7oEy-00015D-QI
	for rohc@optimus.ietf.org; Sun, 28 Mar 2004 23:19:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22871
	for <rohc@ietf.org>; Sun, 28 Mar 2004 23:19:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7oEs-0000pr-00
	for rohc@ietf.org; Sun, 28 Mar 2004 23:19:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7oDz-0000jC-00
	for rohc@ietf.org; Sun, 28 Mar 2004 23:18:12 -0500
Received: from mailrelay2.lntinfotech.com ([203.199.54.34])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7oD9-0000Uy-00
	for rohc@ietf.org; Sun, 28 Mar 2004 23:17:19 -0500
Received: from Bangalore.lntinfotech.com ([107.108.204.3])
          by mailrelay2.lntinfotech.com (Lotus Domino Release 5.0.12)
          with ESMTP id 2004032909463931:11603 ;
          Mon, 29 Mar 2004 09:46:39 +0530 
Subject: Re: [rohc] Slope used to compress/decompress RTP Timestamp field
To: rohc@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF61AED2EF.8CFE32E6-ON65256E66.00174780@lntinfotech.com>
From: "Kavitha KR" <Kavitha.KR@lntinfotech.com>
Date: Mon, 29 Mar 2004 09:44:33 +0530
MIME-Version: 1.0
X-MIMETrack: Serialize by Router on BANGALORE/LNTINFOTECH(Release 5.0.9 |November 16, 2001) at
 03/29/2004 09:44:34 AM,
	Itemize by SMTP Server on MAILRELAY2/LNTINFOTECH(Release 5.0.12  |February
 13, 2003) at 03/29/2004 09:46:40 AM,
	Serialize by Router on MAILRELAY2/LNTINFOTECH(Release 5.0.12  |February 13, 2003) at
 03/29/2004 09:47:21 AM,
	Serialize complete at 03/29/2004 09:47:21 AM
Content-type: text/plain; charset=us-ascii
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60


hi kamal,

I think it is rather left to implementation.
For e.g in the 3GPP2 cdma networks, the default value is simply taken to be
3.

Btw, what is 'L'?

regards,
kavitha.



                                                                                                                                       
                      "kamal deep                                                                                                      
                      singh"                   To:       <zhigang.c.liu@nokia.com>, <szym_paw@wp.pl>                                   
                      <kd.singh@enst-br        cc:       <kristofer.sandlund@effnet.com>, <lars-erik.jonsson@ericsson.com>,            
                      etagne.fr>                <rohc@ietf.org>                                                                        
                      Sent by:                 Subject:  Re: [rohc] Slope used to compress/decompress RTP Timestamp field              
                      rohc-admin@ietf.o                                                                                                
                      rg                                                                                                               
                                                                                                                                       
                                                                                                                                       
                      03/27/2004 08:52                                                                                                 
                      PM                                                                                                               
                                                                                                                                       
                                                                                                                                       




Hi,

I have one question below.

> Actually for robustness, the compressor must make sure that at least two
("FO") packets with TS >field have been received by the decompressor before
it can transit to SO state and send Type-0 >packets. It will ensure that
the
decompressor acquires both slope and offset of the function from >SN to TS.

In U and O mode, how will compressor base its confidence?
By sending L + 1 or 2L packets?

Or should it be left as an implementation choice?


regards,
Kamal




































This email may contain confidential or privileged information for the
intended recipient(s). If you are not the intended recipient, please do not
use or disseminate the information, notify the sender and delete it from
your system. Thanks


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



From exim@www1.ietf.org  Mon Mar 29 11:14:34 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10462
	for <rohc-archive@odin.ietf.org>; Mon, 29 Mar 2004 11:14:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7zOn-0003jU-Om
	for rohc-archive@odin.ietf.org; Mon, 29 Mar 2004 11:14:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2TGE5IU014348
	for rohc-archive@odin.ietf.org; Mon, 29 Mar 2004 11:14:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7zOn-0003jL-Hg
	for rohc-web-archive@optimus.ietf.org; Mon, 29 Mar 2004 11:14:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10449
	for <rohc-web-archive@ietf.org>; Mon, 29 Mar 2004 11:14:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7zOm-0002dC-00
	for rohc-web-archive@ietf.org; Mon, 29 Mar 2004 11:14:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7zNt-0002SW-00
	for rohc-web-archive@ietf.org; Mon, 29 Mar 2004 11:13:10 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7zMp-0002Fq-00
	for rohc-web-archive@ietf.org; Mon, 29 Mar 2004 11:12:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7zMm-0003RR-3E; Mon, 29 Mar 2004 11:12:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7zMa-0003Od-7g
	for rohc@optimus.ietf.org; Mon, 29 Mar 2004 11:11:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10400
	for <rohc@ietf.org>; Mon, 29 Mar 2004 11:11:43 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7zMX-0002F9-00
	for rohc@ietf.org; Mon, 29 Mar 2004 11:11:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7zLj-00027G-00
	for rohc@ietf.org; Mon, 29 Mar 2004 11:10:56 -0500
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7zKq-0001xE-00
	for rohc@ietf.org; Mon, 29 Mar 2004 11:10:01 -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 i2TG9wD28377;
	Mon, 29 Mar 2004 19:09:58 +0300 (EET DST)
X-Scanned: Mon, 29 Mar 2004 19:08:44 +0300 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i2TG8ifa031877;
	Mon, 29 Mar 2004 19:08:44 +0300
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks003.ntc.nokia.com 00veToVe; Mon, 29 Mar 2004 19:08:43 EEST
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 i2TG8gF07131;
	Mon, 29 Mar 2004 19:08:42 +0300 (EET DST)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Mon, 29 Mar 2004 10:07:16 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] Slope used to compress/decompress RTP Timestamp field
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Mon, 29 Mar 2004 11:07:14 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B815371C@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] Slope used to compress/decompress RTP Timestamp field
Thread-Index: AcQUD6ZKyoSpXfXpRiOJFc6wd4/o+gBl9pdw
To: <kd.singh@enst-bretagne.fr>, <szym_paw@wp.pl>
Cc: <kristofer.sandlund@effnet.com>, <lars-erik.jonsson@ericsson.com>,
        <rohc@ietf.org>
X-OriginalArrivalTime: 29 Mar 2004 16:07:16.0246 (UTC) FILETIME=[E7985B60:01C415A7]
Content-Transfer-Encoding: quoted-printable
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

It's not specified in RFC 3095. So, it's an implementation choice.

5.3.1.1.1.  Optimistic approach, upwards transition

   [snip]

   The compressor normally obtains its confidence about decompressor
   status by sending several packets with the same information according
   to the lower compression state.  If the decompressor receives any of
   these packets, it will be in sync with the compressor.  The number of
   consecutive packets to send for confidence is not defined in this
   document.

BR,
Zhigang

> -----Original Message-----
> From: ext kamal deep singh [mailto:kd.singh@enst-bretagne.fr]
> Sent: 27 March, 2004 09:23 AM
> To: Liu Zhigang.C (Nokia-NRC/Dallas); szym_paw@wp.pl
> Cc: kristofer.sandlund@effnet.com;=20
> lars-erik.jonsson@ericsson.com; rohc@ietf.org
> Subject: Re: [rohc] Slope used to compress/decompress RTP=20
> Timestamp field
>=20
>=20
>=20
> Hi,
>=20
> I have one question below.
>=20
> > Actually for robustness, the compressor must make sure that=20
> at least two
> ("FO") packets with TS >field have been received by the=20
> decompressor before
> it can transit to SO state and send Type-0 >packets. It will=20
> ensure that the
> decompressor acquires both slope and offset of the function=20
> from >SN to TS.
>=20
> In U and O mode, how will compressor base its confidence?
> By sending L + 1 or 2L packets?
>=20
> Or should it be left as an implementation choice?
>=20
>=20
> regards,
> Kamal
>=20
>=20
>=20
>=20
> > 4.3.1.3.  Second Order (SO) State
> >
> >    This is the state where compression is optimal.  The compressor
> >    enters the SO state when the header to be compressed is=20
> completely
> >    predictable given the SN (RTP Sequence Number) and the=20
> compressor is
> >    sufficiently confident that the decompressor has acquired all
> >    parameters of the functions from SN to other fields
> >
> > BR,
> > Zhigang
> >
> > >
> > > Hi Zighang,
> > >
> > > I wonder how decompressor should behave if it receives only
> > > one packet with TS
> > > field between two packets without TS ( for example when it
> > > receives UO-0
> > > packet, next UO-1-TS and next again UO-0 packet).
> > >
> > > I can see two options:
> > >
> > > 1. The decompressor uses the old slope value (e.g. the=20
> one it used to
> > > decompress the first UO-0 packet) to calculate timestamp for
> > > the second UO-0  packet. Here we assume that single TS=20
> communicates
> change in
> > > the offset.
> > >
> > > 2. It calculates a new slope basing on the timestamp values
> > > decompressed from  the first UO-0 packet and the UO-1=20
> packet and next it
> uses
> > > the new slope to calculate the timestamp for the second=20
> UO-0 packet.
> > >
> > > Which of the above is correct ?
> > >
> > > Regards
> > >
> > > Pawel
> > >
> > > > Hi Pawel,
> > > >
> > > > Yes, your understanding is correct. It's basically the
> > > geometry: two points
> > > determine a line. Besides the slope, two TS values also give
> > > you the offset.
> > > >
> > > > No, RFC 3095 does not assume floating point. All
> > > encoding/decoding operations
> > > are integer based.
> > > >
> > > > Zhigang
> > > >
> > > > > -----Original Message-----
> > > > > From: ext Pawel Szymanski [mailto:szym_paw@wp.pl]
> > > > > Sent: 26 March, 2004 02:33 AM
> > > > > To: Liu Zhigang.C (Nokia-NRC/Dallas)
> > > > > Cc: kristofer.sandlund@effnet.com; kd.singh@enst-bretagne.fr;
> > > > > lars-erik.jonsson@ericsson.com; rohc@ietf.org
> > > > > Subject: RE: [rohc] Slope used to compress/decompress RTP
> > > > > Timestamp field
> > > > >
> > > > >
> > > > >
> > > > > Hi Zhigang,
> > > > >
> > > > > > > I base this on the following observations:
> > > > > > >
> > > > > > > * 4.5.3. Scaled RTP Timestamp encoding
> > > > > > >     3. Decompression: When receiving the=20
> 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.
> > > > > > >
> > > > > > > If there acutally was a slope, it should have been in
> > > > > this formula.
> > > > > >
> > > > > > This is a misunderstanding. Note that there are two
> > > *separate* steps
> > > > > > involved. The formula is for the second step: deriving TS
> > > > > from TS_SCALED.
> > > > > > The slope plays a role in the first step: "the decompressor
> > > > > first derives
> > > > > > the value of the original TS_SCALED". I thought this is
> > > clear from
> > > > > > section 4.5.3. More clarifications below.
> > > > >
> > > > > I think that the decompressor uses slope when it receives
> > > > > packets without TS
> > > > > field (for example UO-0 packets).
> > > > >
> > > > > In this case it uses the formula to calculate new scaled
> > > > > timestamp value:
> > > > >
> > > > >    new_scaled_timestamp =3D old_scaled_timestamp + (new_SN -
> > > > > old_SN)*slope
> > > > >
> > > > > Next it calculates the unscaled timestamp using the
> > > formula from 4.5.3
> > > > >
> > > > > When the decompressor receives a packet with TS field, it
> > > > > does not use slope.
> > > > > It decompresses the new scaled timestamp value using LSB
> > > > > method. Next it uses
> > > > > the formula from 4.5.3 to calculate the unscaled timestamp.
> > > > >
> > > > > When the decompressor receives two or more packets containing
> > > > > TS value in raw,
> > > > > it can calculate a new slope value, for example using=20
> the formula:
> > > > >
> > > > >   new_slope =3D (new_scaled_timestamp - old_scaled_timestamp) =
/
> > > > > (new_SN - old_SN)
> > > > >
> > > > > Am I correct ?
> > > > >
> > > > > An additional question is whether the slope is an integer
> > > > > number or could it be
> > > > > a floating point number ?
> > > > >
> > > > > Regards
> > > > >
> > > > > Pawel
> > > > >
> > > > >
> > > > > ----------------------------------------------------
> > > > > Zobacz niezwyk=B3y koncert: "Niemena Pami=EAci Gda=F1ski =
Rapsod"
> > > > > Najwi=EAksze przeboje artysty w nowych zaskakuj=B1cych=20
> aran=BFacjach.
> > > > > =
http://klik.wp.pl/?adr=3Dhttp%3A%2F%2Fmuzyka.wp.pl%2Fimprezy.htm
> > > > l%3Fidn%3D874&sid=3D151
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Rohc mailing list
> > > > Rohc@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/rohc
> > > >
> > >
> > > ----------------------------------------------------
> > > =A3odzi=B1 po Wi=B6le - najciekawsze etiudy w Warszawie.
> > > http://klik.wp.pl/?adr=3Dhttp%3A%2F%2Ffilm.wp.pl%2Fp%2Fwiadomosc
> > .html%3Fid%3D55832&sid=3D152
> >
> >
> >
>=20
>=20

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



From exim@www1.ietf.org  Mon Mar 29 17:18:28 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29884
	for <rohc-archive@odin.ietf.org>; Mon, 29 Mar 2004 17:18:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8550-0001fd-6c
	for rohc-archive@odin.ietf.org; Mon, 29 Mar 2004 17:18:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2TMI2Dh006417
	for rohc-archive@odin.ietf.org; Mon, 29 Mar 2004 17:18:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B854z-0001fN-Hu
	for rohc-web-archive@optimus.ietf.org; Mon, 29 Mar 2004 17:18:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29733
	for <rohc-web-archive@ietf.org>; Mon, 29 Mar 2004 17:17:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B854x-0000yw-00
	for rohc-web-archive@ietf.org; Mon, 29 Mar 2004 17:17:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8532-0000XC-00
	for rohc-web-archive@ietf.org; Mon, 29 Mar 2004 17:16:01 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B852O-0000NC-04
	for rohc-web-archive@ietf.org; Mon, 29 Mar 2004 17:15:20 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B84wg-0000Jq-Io
	for rohc-web-archive@ietf.org; Mon, 29 Mar 2004 17:09:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B84wG-0001Hg-Px; Mon, 29 Mar 2004 17:09:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B84vy-0001De-LE
	for rohc@optimus.ietf.org; Mon, 29 Mar 2004 17:08:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29529
	for <rohc@ietf.org>; Mon, 29 Mar 2004 17:08:38 -0500 (EST)
From: davegreen@comcast.net
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B84vw-0007T8-00
	for rohc@ietf.org; Mon, 29 Mar 2004 17:08:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B84v1-0007M1-00
	for rohc@ietf.org; Mon, 29 Mar 2004 17:07:45 -0500
Received: from sccrmhc13.comcast.net ([204.127.202.64])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B84uJ-00077o-00
	for rohc@ietf.org; Mon, 29 Mar 2004 17:06:59 -0500
Received: from 204.127.205.150 ([204.127.205.150])
          by comcast.net (sccrmhc13) with SMTP
          id <2004032922062901600i2vb4e>; Mon, 29 Mar 2004 22:06:29 +0000
Received: from [192.172.8.13] by 204.127.205.150;
	Mon, 29 Mar 2004 22:06:29 +0000
To: rohc@ietf.org
Date: Mon, 29 Mar 2004 22:06:29 +0000
Message-Id: <032920042206.22762.40689DE4000C3EA3000058EA2200751150FF919A9A8D989A899E@comcast.net>
X-Mailer: AT&T Message Center Version 1 (Mar 22 2004)
X-Authenticated-Sender: ZGF2ZWdyZWVuQGNvbWNhc3QubmV0
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="NextPart_Webmail_9m3u9jl4l_22762_1080597989"
Subject: [rohc] Multipoint Robust Compression for MANET
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=2.60


--NextPart_Webmail_9m3u9jl4l_22762_1080597989
Content-Type: text/plain
Content-Transfer-Encoding: 8bit

I'm designing a MANET system suitable for handheld and automobile portable radios that can operate on the move with link rages greater than 1 km. We will be adding IPv6 to the system so header compression has become a necessity as the network generally achieves less than 100kbps on links. In order to maximize bandwidth efficiency we are using broadcast and multicast traffic (multipoint traffic) to our neighbor nodes. I propose that we either create an extension to ROHC for multipoint links or come up with a method to efficiently use the current version in multipoint MANETS. I have been in contact with representatives from Effnet and Procito who are interested in designing the compression scheme.  I have included a problem statement that defines the issues that I think need to be addressed and suggest that the ROHC group take this up as a new action item.

Please let me know what you think, and if the we can address this problem within the working group. 

Thank you,

   David Green
   SRI International
   EMail: david.green@sri.com

--NextPart_Webmail_9m3u9jl4l_22762_1080597989
Content-Type: text/plain; name="green-rohc-multipoint-problem-statement.txt"
Content-Transfer-Encoding: 7bit

ROHC Working Group                               D. Green
                                                 SRI International
 		                                       March 29, 2004

Problem Statement for ROHC Compression Profile for Multipoint MANET Links

draft-green-rohc-manet-problem-statement.txt

Status of this Memo
   This document is a draft suggestion to the ROHC working group to establish the need for an efficient method for using ROHC over multipoint (point to multipoint and broadcast) links found in Mobile Ad Hoc Network (MANET) radio systems. 

Abstract
   In ad hoc radio networks containing or contained within larger IP networks, especially IPv6 networks, the capabilities of a header compression protocol such as ROHC are desirable. This document poses the issues that need to be addressed to make ROHC work well in a network containing both traditional point-to-point unicast messaging and point-to-multipoint broadcast and multicast messaging sent across radio network topologies.



Table of Contents

   1.   Introduction . . . . . . . . . . . . . . . . . . . . . . 2
   1.1  Network Design Requirements  . . . . . . . . . . . . . . 2
   1.2  Multipoint Network General Approach  . . . . . . . . . . 3
   1.3  MANET Network General Issues . . . . . . . . . . . . . . 3
   1.4  MANET Data-Link Layer Considerations . . . . . . . . . . 4
   1.5  MANET Network Layer Considerations . . . . . . . . . . . 5
   1.6  Unique IPv6 Considerations . . . . . . . . . . . . . . . 5
   2.0  Combining MANET and ROHC - Specific Challenges . . . . . 5
   3.   Security Considerations  . . . . . . . . . . . . . . . . 5
   4.   Acknowledgements . . . . . . . . . . . . . . . . . . . . 6
   5.   References . . . . . . . . . . . . . . . . . . . . . . . 6
   6.   Authors' Addresses . . . . . . . . . . . . . . . . . . . 7
   7.   Intellectual Property and Copyright Statements . . . . . 7






1. Introduction

RFC 3509 [1], entitled "RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed" gives a good overview of the requirements for IPv4 and IPv6 header compression in wireless networks. It describes the various issues and requirements that need to be addressed in such a network, and has led to the development of a number of extensions to the base protocol [2] [3] [4] [5].

These protocols specifically address networks in which the only, or
the primary, communication vehicle is a point-to-point radio link with significant error rates, and long round-trip times. In ad hoc radio networks containing or contained within larger IP networks, many of the capabilities of ROHC are desirable and arguably necessary, but for maximum efficiency additional extensions need to be made for point-to-multipoint traffic such as broadcast and multicast traffic.

This document poses the issues that need to be addressed to make ROHC work well in a network containing both traditional point-to-point (cellular) and point to multipoint (MANET) radio network topologies. 

1.1 Network Design Requirements

In the portions of networks linked by MANET capable radios, the radio frequency (RF) physical medium is error prone (10^-3 error rates are common), data rate limited (288kbps or less for long range 1km+ mobile data radios), and high delay (10s to 100s of milliseconds per hop) medium when compared to wired networks. When networks are operating on the move, terrain masking, foliage scattering, and the changing propagation distances between nodes all exacerbate packet errors, network outages, router topology changes, and delays. 

Due to the ad-hoc nature of MANET architectures, the radio system is inherently a broadcast medium where all neighbor radios may receive the transmission of any transmitting radio if they are within the RF range of the transmitter. Given the inherent broadcast nature of the RF medium, MANET radios may transmit point-to-point style messages to single neighbors (and other neighbors discard the transmissions not meant for them), point-to-multipoint messages to groups of neighbors (neighbors in the multipoint group listen to the message while neighbors not in the group discard the message), or point-to-all messages which are received and processed by all neighbors. These capabilities enable radios to service Internet Protocol unicast, multicast, and broadcast style messages.  Since messaging applications attached to MANETs often need to send messages to multiple destinations within the MANET, multicast and broadcast messages are used heavily as they consume less data bandwidth t!
 han transmitting multiple point-to-point unicast messages.
 
MANET networks have the same RF medium characteristics of high error rates, severely limited data rates, and high delay that the ROHC base specification addresses via robust Window-based LSB encoding. MANET networks differ from the current extensions for ROHC since they must service, broadcast and multicast messages in addition to unicast point-to-point messages. Since the RF physical medium characteristics are well addressed by ROHC, and only the capability to efficiently support multicast and broadcast transmissions may not supported, we reason that ROHC may properly support multicast and broadcast links with little or no modification.


1.2 Multipoint Network General Approach. 
A node sending a broadcast or multicast message a message needs a method to check and see if the message recipients correspond to current layer 1-2 (single hop) neighbors, and a method to look into a compression context table to determine if a full header needs to be sent or what level of compression may be used. Current unidirectional-mode (u-mode) compression can support multipoint data dissemination, but higher levels of compression may be gained through feedback mechanisms if the mechanisms do not cause excessive overhead. 
Compression on point to multipoint links will probably have a lower average efficiency when compared to point to point links, but a properly designed scheme should significantly lower IP overhead for IPv4 and v6 and result in a net savings.

1.3 MANET General Issues 

RFC 2501 [2], in section 3, lists a number of important points about
MANET networks. They have dynamic topologies, which is to say that a system's list of neighboring hosts and routers changes from time to time. They are often bandwidth-constrained, both because the medium is shared with other nodes and because of limitations of the technology. They are also often power-constrained - a man portable MANET system carried by a person is running on its battery, and the simple act of transmission can be a major power drain. They also enjoy limited security: even if locked in a room, their radio transmissions can be a beacon identifying their location or giving away information about the frequency and RF waveform with which they transmit. 

>From the perspective of adapting an existing header compression protocol, these MANET characteristics have specific implications. If transmissions consume power & bandwidth while potentially compromising security, unnecessary transmission is something to be avoided. As a result, if there are several ways that a peer might establish compression context (using multicast and broadcast to exchange compression context information to multiple neighbors simultaneously, piggybacking compression on messages for neighbor discovery or routing information exchange, etc.), selecting the one that uses the least power and bandwidth will have the least impact - at least less impact than allowing duplicates. If the network is
bandwidth-constrained, limiting transmissions also preserves bandwidth for other uses, and compressing data in ways that maximize available bandwidth is extremely helpful. Security threats need to be actively addressed, and in regions of rapid network change, or during periods of rapid network change, the transmission and computation loads need to be minimized. These issues are often deemed unimportant in protocols designed for fixed usage.

1.4 MANET Data-Link Layer Considerations. 
 MANET capable radios may be based on common commercial technology such as 802.11, emergency or military radios, or other technologies. Despite the variations in radio technology, the radios are usually built using a small set of link-layer technologies. Link layer assisted schemes will vary between radios, or in the case of JTRS and other software defined radios, they will vary as the software defined waveform changes.

General similarities of most MANET Radios:
*Data Link (Logical Link Control sub layer) Protocols such as ARP, RARP, RDISC are common and may be leveraged by multipoint ROHC
 
General differences between most MANET Radios:
*Channel access protocols vary between CSMA, CDMA, TDMA, and hybrid schemes 
*MAC Frame Formats often vary




1.5 MANET Network Layer considerations
*MANETS operate on many different experimental routing protocols (AODV, OLSR, TBRPF, OSPF with MANET extensions, and others) since there is no IETF standards-track MANET protocol
*MANET protocols that maintain active neighbor lists may provide the neighbor state information needed to check against multipoint recipients to determine if a compression context is established.

1.6 Unique IPv6 considerations [6]
*Larger addresses make header compression a more urgent need
*Automatic address reassignment via autodiscovery and autoconfiguration could impact header compression
*IPv6 neighbor discovery (neighbor solicitation and advertisement)(RFC 2461) [7] could be an enabling mechanism to gather information on neighbors
 
2.0 Combining MANET and ROHC - Specific Challenges
*Determining if messages require broadcast or multicast support
*Determining/discovering neighbors to establish compression contexts 
*Method for crosschecking multicast message recipients against neighbor tables
*U-mode probably will work for a low level of compression
*To get higher efficiency, we might need to redesign the feedback logic for bi-directional modes to handle multipoint links without generating collisions or congestion in dense networks 
*Impairment considerations for multipoint links
*Method for context repair for multipoint links

3.0 Security Considerations

   As a problem statement, this note imposes no new security
   requirements on MANET networks that are not known from RFC
   2501 [2]. Those problems can, however, be extreme. RFC 2501's
   Security Considerations read:

        Mobile wireless networks are generally more prone to physical security threats than are fixed, hardwired networks. Existing link-level security techniques (e.g. encryption) are often applied within wireless networks to reduce these threats. Absent link-level encryption, at the network layer, the most pressing issue is one of inter-router authentication prior to the exchange of network control information.  Several levels of authentication ranging from no security (always an option) and       simple shared-key approaches, to full public key        infrastructure-based authentication mechanisms will be explored by the group.  As an adjunct to the working groups efforts, several optional authentication modes may be standardized for use in MANETs.

   Note, however, that the issues that routing in a wireless network are very vulnerable to attack, and appropriate security issues need to be taken seriously.

4. Acknowledgements
Initial comments were received from Tommy Lundemo, Jesus Arango, Fred Templin, and Pete Sholander to help define this problem.

5. References
[1] Bormann, C., Burmeister, C., Degermark, M., Fukushima, H., Hannu, H., Jonsson, L-E., Hakenberg, R., Koren, T.,Le, K., Liu, Z., Martensson, A., Miyazaki, A., Svanbro, K., Wiebke, T., Yoshimura, T. and H. Zheng, "Robust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed", RFC 3095, July 2001.

[2] Degermark, M., "Requirements for IP/UDP/RTP Header Compression", RFC 3096, July 2001.

[3] Jonsson, L-E., "RObust Header Compression (ROHC): Requirements and Assumptions for 0-byte IP/UDP/RTP Compression", RFC 3243, April 2002.

[4] C. Bormann, "Robust Header Compression (ROHC) over PPP", RFC 3241, April 2002.

[5] Jonsson, L. and G. Pelletier, "RObust Header Compression (ROHC): A compression profile for IP", Internet draft (work in progress), October 2003, <draft-ietf-rohc-ip- only-05.txt>

[6] Deering, S. and R. Hinden, "Internet Protocol, Version (IPv6) Specification", RFC 2460, December 1998.

[7] Narten, T., Nordmark, E., Simpson, W., and Daydreamer, "Neighbor Discovery for Ipv6", RFC 2461, December 1998

Portions of this document in its current state have been taken directly from http://www.ietf.org/Draft-Statements/draft-baker-manet-ospf-problem-statement-00.txt  as this document relates to creating an OSPF-MANET routing protocol and many general considerations in Baker's problem statement overlap with considerations for developing a MANET compression protocol.

6. Authors' Address

   David Green
   SRI International
   333 Ravenswood Ave
   Menlo Park, California  94025
   USA

   Phone: +1-732-532-6715
   Fax:   +1-732-427-2065
   EMail: david.green@sri.com

7. Intellectual Property Statement

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that this document is referenced and the above copyright notice and this paragraph are included on all such copies and derivative works.  However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the authors, IETF, or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by the authors or their successors or assigns.

The author invites any interested party to bring to their attention any implementation issues, copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. 





--NextPart_Webmail_9m3u9jl4l_22762_1080597989--

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



From exim@www1.ietf.org  Mon Mar 29 23:47:36 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15768
	for <rohc-archive@odin.ietf.org>; Mon, 29 Mar 2004 23:47:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8B9O-0000Ma-Iv
	for rohc-archive@odin.ietf.org; Mon, 29 Mar 2004 23:47:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2U4kwM3001390
	for rohc-archive@odin.ietf.org; Mon, 29 Mar 2004 23:46:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8B9O-0000MK-CL
	for rohc-web-archive@optimus.ietf.org; Mon, 29 Mar 2004 23:46:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15739
	for <rohc-web-archive@ietf.org>; Mon, 29 Mar 2004 23:46:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8B9M-0001Ut-00
	for rohc-web-archive@ietf.org; Mon, 29 Mar 2004 23:46:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8B8P-0001N0-00
	for rohc-web-archive@ietf.org; Mon, 29 Mar 2004 23:45:57 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8B7U-0001Fj-00
	for rohc-web-archive@ietf.org; Mon, 29 Mar 2004 23:45:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8B7V-0000HJ-20; Mon, 29 Mar 2004 23:45:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8B7S-0000Gg-Iw
	for rohc@optimus.ietf.org; Mon, 29 Mar 2004 23:44:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15653
	for <rohc@ietf.org>; Mon, 29 Mar 2004 23:44:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8B7Q-0001F2-00
	for rohc@ietf.org; Mon, 29 Mar 2004 23:44:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8B6V-00017m-00
	for rohc@ietf.org; Mon, 29 Mar 2004 23:44:00 -0500
Received: from mailrelay2.lntinfotech.com ([203.199.54.34])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8B5y-00010D-00
	for rohc@ietf.org; Mon, 29 Mar 2004 23:43:26 -0500
Received: from Bangalore.lntinfotech.com ([107.108.204.3])
          by mailrelay2.lntinfotech.com (Lotus Domino Release 5.0.12)
          with ESMTP id 2004033010125420:15360 ;
          Tue, 30 Mar 2004 10:12:54 +0530 
To: rohc@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OFB9F3DDBA.0B5A431F-ON65256E67.00196C53@lntinfotech.com>
From: "Kavitha KR" <Kavitha.KR@lntinfotech.com>
Date: Tue, 30 Mar 2004 10:10:47 +0530
MIME-Version: 1.0
X-MIMETrack: Serialize by Router on BANGALORE/LNTINFOTECH(Release 5.0.9 |November 16, 2001) at
 03/30/2004 10:10:48 AM,
	Itemize by SMTP Server on MAILRELAY2/LNTINFOTECH(Release 5.0.12  |February
 13, 2003) at 03/30/2004 10:12:54 AM,
	Serialize by Router on MAILRELAY2/LNTINFOTECH(Release 5.0.12  |February 13, 2003) at
 03/30/2004 10:13:28 AM,
	Serialize complete at 03/30/2004 10:13:28 AM
Content-type: text/plain; charset=us-ascii
Subject: [rohc] Correction algorithm in U Mode
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,BLANK_LINES_70_80 
	autolearn=no version=2.60

Hi,

Why is the small sequence number reconstruction algorithm specified in sec
5.3.2.2.2 of ROHC
applicable only to U-Mode? Is it not applicable to O-Mode as well?

regards
kavitha.





























This email may contain confidential or privileged information for the
intended recipient(s). If you are not the intended recipient, please do not
use or disseminate the information, notify the sender and delete it from
your system. Thanks


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



From exim@www1.ietf.org  Tue Mar 30 02:29:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04400
	for <rohc-archive@odin.ietf.org>; Tue, 30 Mar 2004 02:29:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8DgG-0003YM-Qz
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 02:29:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2U7T40j013657
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 02:29:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8DgE-0003Y6-Gc
	for rohc-web-archive@optimus.ietf.org; Tue, 30 Mar 2004 02:29:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04390
	for <rohc-web-archive@ietf.org>; Tue, 30 Mar 2004 02:28:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8DgA-0000TD-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 02:28:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8DfE-0000M1-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 02:28:00 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8DeG-0000Ev-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 02:27:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8DeI-0003QK-GZ; Tue, 30 Mar 2004 02:27:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8DdK-0003Io-9G
	for rohc@optimus.ietf.org; Tue, 30 Mar 2004 02:26:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04337
	for <rohc@ietf.org>; Tue, 30 Mar 2004 02:25:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8DdG-00007T-00
	for rohc@ietf.org; Tue, 30 Mar 2004 02:25:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8DcI-0007n1-00
	for rohc@ietf.org; Tue, 30 Mar 2004 02:24:58 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8DbH-0007Y3-00
	for rohc@ietf.org; Tue, 30 Mar 2004 02:23:55 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2U7NtYG026226
	for <rohc@ietf.org>; Tue, 30 Mar 2004 09:23:55 +0200 (MEST)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 30 Mar 2004 09:23:55 +0200
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <H8FH3P72>; Tue, 30 Mar 2004 09:23:55 +0200
Message-ID: <A943FD84BD9ED41193460008C7918050072E94F2@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'Kavitha KR'" <Kavitha.KR@lntinfotech.com>, rohc@ietf.org
Subject: RE: [rohc] Correction algorithm in U Mode
Date: Tue, 30 Mar 2004 09:23:41 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 30 Mar 2004 07:23:55.0119 (UTC) FILETIME=[F57A5FF0:01C41627]
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

RFC 3095, page 64:

"5.4.2.  Decompressor states and logic (O-mode)

   The decompression states and the state transition logic are the same
   as for the Unidirectional case (see section 5.3.2).  What differs is
   the decompression and feedback logic."

Chapter 5.4 specifies O-mode based on U-mode, covering only the parts
that differ.

BR
/L-E


> -----Original Message-----
> From: rohc-admin@ietf.org [mailto:rohc-admin@ietf.org]On Behalf Of
> Kavitha KR
> Sent: den 30 mars 2004 06:41
> To: rohc@ietf.org
> Subject: [rohc] Correction algorithm in U Mode
> 
> 
> Hi,
> 
> Why is the small sequence number reconstruction algorithm 
> specified in sec
> 5.3.2.2.2 of ROHC
> applicable only to U-Mode? Is it not applicable to O-Mode as well?
> 
> regards
> kavitha.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> This email may contain confidential or privileged information for the
> intended recipient(s). If you are not the intended recipient, 
> please do not
> use or disseminate the information, notify the sender and 
> delete it from
> your system. Thanks
> 
> 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
> 

This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Tue Mar 30 02:51:39 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05566
	for <rohc-archive@odin.ietf.org>; Tue, 30 Mar 2004 02:51:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8E1f-0005PM-Nd
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 02:51:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2U7pBg1020788
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 02:51:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8E1f-0005PD-87
	for rohc-web-archive@optimus.ietf.org; Tue, 30 Mar 2004 02:51:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05485
	for <rohc-web-archive@ietf.org>; Tue, 30 Mar 2004 02:51:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8E1b-0003mI-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 02:51:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8E0K-0003Sa-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 02:49:49 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8DzT-0003Dw-02
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 02:48:55 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B8Dmy-0000eW-Rl
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 02:36:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Dmy-00045X-Hc; Tue, 30 Mar 2004 02:36:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7zy2-0005xE-1X
	for rohc@optimus.ietf.org; Mon, 29 Mar 2004 11:50:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12058
	for <rohc@ietf.org>; Mon, 29 Mar 2004 11:50:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7zy0-0007ZA-00
	for rohc@ietf.org; Mon, 29 Mar 2004 11:50:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7zxA-0007Sb-00
	for rohc@ietf.org; Mon, 29 Mar 2004 11:49:36 -0500
Received: from [203.199.93.15] (helo=WS0005.indiatimes.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7zwY-0007DX-00
	for rohc@ietf.org; Mon, 29 Mar 2004 11:48:58 -0500
Received: from 192.168.57.15 (a1 [192.168.57.21])
	by WS0005.indiatimes.com (8.9.3/8.9.3) with SMTP id VAA26457
	for <rohc@ietf.org>; Mon, 29 Mar 2004 21:47:09 +0530
From: "jb_sigcomp" <jb_sigcomp@indiatimes.com>
Message-Id: <200403291617.VAA26457@WS0005.indiatimes.com>
To: <rohc@ietf.org>
Reply-To: "jb_sigcomp"<jb_sigcomp@indiatimes.com>
Date: Mon, 29 Mar 2004 22:14:57 +0530
X-URL: http://indiatimes.com
Content-Type: multipart/alternative;
	   boundary="=_MAILER_ATTACH_BOUNDARY1_200432912214572044897763"
MIME-Version: 1.0
Subject: [rohc] Doubt in SigComp instruction - COMPARE
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.0 required=5.0 tests=AWL,HTML_20_30,
	HTML_FONTCOLOR_GREEN,HTML_MESSAGE,NORMAL_HTTP_TO_IP autolearn=no 
	version=2.60

--=_MAILER_ATTACH_BOUNDARY1_200432912214572044897763
Content-Type: text/plain; charset=us-ascii

Hi All,
                                               
               I have doubt in understanding "COMPARE" instruction described in RFC 3220 :-

--Section 9.3.2. COMPARE -- 
The COMPARE instruction compares two operands and then jumps to one of three specified memory addresses depending on the result. COMPARE (%value_1, %value_2, @address_1, @address_2, @address_3) 

If value_1  value_2 then it jumps to the address specified by address_3. 

------DOUBT: ------ 

Memory address being talked about in above explaination is actually bytecode address. It should be like: 

if (val1 Indiatimes Email now powered by APIC Advantage. Help! 
HelpClick on the image to chat with me

--=_MAILER_ATTACH_BOUNDARY1_200432912214572044897763
Content-Type: text/html; charset=us-ascii

Hi All,
                                               
               I have doubt in understanding "COMPARE" instruction described in RFC 3220 :-

--Section 9.3.2. COMPARE -- 
The COMPARE instruction compares two operands and then jumps to one of three specified memory addresses depending on the result. COMPARE (%value_1, %value_2, @address_1, @address_2, @address_3) 

If value_1 < value_2 then the UDVM continues instruction execution at the memory address specified by address 1. If value_1 = value_2 then it jumps to the address specified by address_2. If value_1 > value_2 then it jumps to the address specified by address_3. 

------DOUBT: ------ 

Memory address being talked about in above explaination is actually bytecode address. It should be like: 

if (val1 < val2)
        move the pgm counter to address1 of bytecode 

else if (val == val2) 
         move the pgm counter to address2 of bytecode 
else
         move the pgm counter to address3 of bytecode.



thanks and regards

jyoti 

<hr><font face="Arial" size="2">Indiatimes Email now powered by <b>APIC Advantage</b>. <a href="http://email.indiatimes.com/apic/">Help!</a> </font><br><DIV align=left><a target="_blank" href="http://imaround.indiatimes.com/IMaround/presencefr.mss?userid=jb_sigcomp" ><IMG alt="My Presence" border=0 src="http://203.199.93.51/IMaround/getpresence.mss?userid=jb_sigcomp" ></a><a target="_blank" href="http://email.indiatimes.com/apic/instachat.htm"><FONT face="Arial" size=2>Help</font></a></DIV><DIV align=left><FONT color=#008000 face="Lucida Sans Unicode" size=1>Click on the image to chat with me</FONT></DIV><DIV align=left><a target="_blank" href="http://www.auctions.indiatimes.com/home/index.html"><img border=0 width=366 height=19 src="http://203.199.93.11/image/footer_01.gif"></a></DIV><DIV align=left><a target="_blank" href="http://www.auctions.indiatimes.com/home/index.html"><img border=0 height=16 src="http://203.199.93.11/image/footer_02.gif"></a></DIV>

--=_MAILER_ATTACH_BOUNDARY1_200432912214572044897763--


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



From exim@www1.ietf.org  Tue Mar 30 02:59:33 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06085
	for <rohc-archive@odin.ietf.org>; Tue, 30 Mar 2004 02:59:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8E9K-0006j4-3f
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 02:59:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2U7x6xB025848
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 02:59:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8E9J-0006ip-UL
	for rohc-web-archive@optimus.ietf.org; Tue, 30 Mar 2004 02:59:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06028
	for <rohc-web-archive@ietf.org>; Tue, 30 Mar 2004 02:59:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8E9F-0005FR-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 02:59:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8E8F-00053y-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 02:58:01 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8E7G-0004s4-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 02:56:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8E7J-0006WQ-3S; Tue, 30 Mar 2004 02:57:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8E6W-0006ME-GB
	for rohc@optimus.ietf.org; Tue, 30 Mar 2004 02:56:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05945
	for <rohc@ietf.org>; Tue, 30 Mar 2004 02:56:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8E6S-0004mZ-00
	for rohc@ietf.org; Tue, 30 Mar 2004 02:56:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8E5h-0004eg-00
	for rohc@ietf.org; Tue, 30 Mar 2004 02:55:23 -0500
Received: from [194.237.235.30] (helo=effnet.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8E5B-0004UB-00
	for rohc@ietf.org; Tue, 30 Mar 2004 02:54:50 -0500
Received: from effnet.com (c-497871d5.04-205-6c756c1.cust.bredbandsbolaget.se [213.113.120.73])
	(authenticated bits=0)
	by effnet.com (8.12.3/8.12.3) with ESMTP id i2U6ruU2018993
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Tue, 30 Mar 2004 08:53:57 +0200
Message-ID: <406927A6.8090603@effnet.com>
Date: Tue, 30 Mar 2004 09:54:14 +0200
From: Kristofer Sandlund <kristofer.sandlund@effnet.com>
Organization: Effnet
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030821
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: zhigang.c.liu@nokia.com
CC: kd.singh@enst-bretagne.fr, szym_paw@wp.pl, lars-erik.jonsson@ericsson.com,
        rohc@ietf.org
Subject: Re: [rohc] Slope used to compress/decompress RTP Timestamp field
References: <7B5AF06E216CB74DA8A5960A3181B5B815371C@ajebe001.americas.nokia.com>
In-Reply-To: <7B5AF06E216CB74DA8A5960A3181B5B815371C@ajebe001.americas.nokia.com>
X-Enigmail-Version: 0.76.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by effnet.com id i2U6ruU2018993
Content-Transfer-Encoding: quoted-printable
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi Zhigang and others!

I'm not yet convinced of the slope as described here, so I'll outline why.

1) It is not well defined in the spec (at least U/O-mode).

For example, the definition of the timestamp stride (section 2.0) is as f=
ollows:
    Timestamp stride

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

In the two examples taken so far (one semi-static TS for video, and the o=
ther=20
"2,4,6" increase of the TS), the assumption used has been that the TS_STR=
IDE is=20
set to "the difference in TS between two FRAMES", and not the difference =
between=20
two PACKETS as defined above. According to the definition above, the TS_S=
TRIDE=20
should be 0 in the semi-static case (see my last mail how I felt the slou=
tion=20
can be) and "2" in the other case, and then, no slope is needed for these=
=20
specific cases.

Zhigang wrote:
 >Although the question was raised due to TS, I'd like to emphasize
 >that the concept of slope is not only for TS. As Kamal pointed out,
 >slope is one parameter of the function (see text below from section 3.4=
).
 >
 >   The way ROHC RTP compression operates, then, is to first establish
 >   functions from SN to the other fields, and then reliably communicate
 >   the SN.  Whenever a function from SN to another field changes, i.e.,
 >   the existing function gives a result which is different from the
 >   field in the header to be compressed, additional information is sent
 >   to update the parameters of that function.

This text can as well be interpreted as if the function is simply the=20
scaling/offset scheme of the TS and that the IPID offset encoding is this=
=20
function for IPID. The slope itself is not mentioned in this section, so =
I can't=20
see this as a "proof" for slope.

(see my previous mail for some more comments on why I don't think it is d=
efined)

2) The updating of the slope in U/O-mode is inconsistent with the definit=
ion of=20
these modes.

Every time the decompressor sees a packet in U/O-modes, the context is up=
dated=20
for all fields in the compressed packet and those inferred from them. If =
slope=20
is to be used, suddenly we need two consecutive packets to update this co=
ntext=20
value. Since this is neither clear from the spec (there is no definition =
in 3095=20
that says that U/O-mode should only update slope after two packets seen),=
 and=20
the fact that it is different from all other updating, this is bound to c=
ause=20
interoperability problems.
Note: I am aware that sending "2*L" UO-1 packets can yield larger compres=
sion=20
efficiency than ("L" UO-1-ID-ext3 + "L" UO-0), but see below for other re=
asons=20
of why I think this tradeoff is worth it.

3) Slow convergence time

a) U/O-mode
Due to the need for sending "more than L" packets to update the context, =
it will=20
take longer time to update the context at the decompressor than it would =
to=20
update the TS_STRIDE (or TS_OFFSET for that matter), which means I will h=
ave to=20
send a larger number of non-SO packets. Therefore, if we see frequent cha=
nges in=20
the pattern, the scheme using slope will have a harder time to ever get t=
o use=20
UO-0 packets than a scheme without slope.

b) R-mode
Note: For R-mode, the updating of the slope is almost defined (5.5.1.2), =
so it=20
actually makes slightly sense to have a slope in R-mode than in U/O-modes=
 when=20
reading the spec.
In R-mode, two ACKs are required to update the slope. Considering the spa=
rse ACK=20
mechanism, the compressor is likely to have to wait quite a long time bef=
ore he=20
knows that the slope has been updated, and therefore, the new slope value=
 cannot=20
be used very soon. Since the slope is supposed to be used in situations w=
here=20
the TS-delta changes "frequently", it is likely that it has changed "agai=
n"=20
before the time that I have seen two ACKs. If not using slope (changing t=
he=20
TS_STRIDE or offset) would only have required one ACK meaning a faster=20
convergence time to SO.

4) Complexity
As I have written above, the slope will have a very different updating pr=
operty=20
that other fields, so it will cause quite a bit of extra complexity to ha=
ndle=20
this. Since the "common case" is a more stable pattern of the timestamp c=
hange,=20
my personal opinion is that it is not worth optimizing with the slope, si=
nce it=20
can be made to work with just the stride/offset.


I also read up in the mail archive, and the last time the slope came up o=
n the=20
list was:
http://www1.ietf.org/mail-archive/working-groups/rohc/current/msg01502.ht=
ml
And then, the conclusion seems to have been that there was no slope (for =
IPID at=20
least) in the spec.

So as a summary, I would like to see an addition to the implementer's gui=
de that=20
says that there "is no slope" (but feel free to convince me that slope is=
 a good=20
thing). At the very least, I feel quite strongly that U/O-mode should not=
 have=20
one since there's a lack of a firm definition of it in 3095.

Best regards,
      Kristofer Sandlund, Effnet AB


zhigang.c.liu@nokia.com wrote:
> It's not specified in RFC 3095. So, it's an implementation choice.
>=20
> 5.3.1.1.1.  Optimistic approach, upwards transition
>=20
>    [snip]
>=20
>    The compressor normally obtains its confidence about decompressor
>    status by sending several packets with the same information accordin=
g
>    to the lower compression state.  If the decompressor receives any of
>    these packets, it will be in sync with the compressor.  The number o=
f
>    consecutive packets to send for confidence is not defined in this
>    document.
>=20
> BR,
> Zhigang
>=20
>=20
>>-----Original Message-----
>>From: ext kamal deep singh [mailto:kd.singh@enst-bretagne.fr]
>>Sent: 27 March, 2004 09:23 AM
>>To: Liu Zhigang.C (Nokia-NRC/Dallas); szym_paw@wp.pl
>>Cc: kristofer.sandlund@effnet.com;=20
>>lars-erik.jonsson@ericsson.com; rohc@ietf.org
>>Subject: Re: [rohc] Slope used to compress/decompress RTP=20
>>Timestamp field
>>
>>
>>
>>Hi,
>>
>>I have one question below.
>>
>>
>>>Actually for robustness, the compressor must make sure that=20
>>
>>at least two
>>("FO") packets with TS >field have been received by the=20
>>decompressor before
>>it can transit to SO state and send Type-0 >packets. It will=20
>>ensure that the
>>decompressor acquires both slope and offset of the function=20
>>from >SN to TS.
>>
>>In U and O mode, how will compressor base its confidence?
>>By sending L + 1 or 2L packets?
>>
>>Or should it be left as an implementation choice?
>>
>>
>>regards,
>>Kamal
>>
>>
>>
>>
>>
>>>4.3.1.3.  Second Order (SO) State
>>>
>>>   This is the state where compression is optimal.  The compressor
>>>   enters the SO state when the header to be compressed is=20
>>
>>completely
>>
>>>   predictable given the SN (RTP Sequence Number) and the=20
>>
>>compressor is
>>
>>>   sufficiently confident that the decompressor has acquired all
>>>   parameters of the functions from SN to other fields
>>>
>>>BR,
>>>Zhigang
>>>
>>>
>>>>Hi Zighang,
>>>>
>>>>I wonder how decompressor should behave if it receives only
>>>>one packet with TS
>>>>field between two packets without TS ( for example when it
>>>>receives UO-0
>>>>packet, next UO-1-TS and next again UO-0 packet).
>>>>
>>>>I can see two options:
>>>>
>>>>1. The decompressor uses the old slope value (e.g. the=20
>>
>>one it used to
>>
>>>>decompress the first UO-0 packet) to calculate timestamp for
>>>>the second UO-0  packet. Here we assume that single TS=20
>>
>>communicates
>>change in
>>
>>>>the offset.
>>>>
>>>>2. It calculates a new slope basing on the timestamp values
>>>>decompressed from  the first UO-0 packet and the UO-1=20
>>
>>packet and next it
>>uses
>>
>>>>the new slope to calculate the timestamp for the second=20
>>
>>UO-0 packet.
>>
>>>>Which of the above is correct ?
>>>>
>>>>Regards
>>>>
>>>>Pawel
>>>>
>>>>
>>>>>Hi Pawel,
>>>>>
>>>>>Yes, your understanding is correct. It's basically the
>>>>
>>>>geometry: two points
>>>>determine a line. Besides the slope, two TS values also give
>>>>you the offset.
>>>>
>>>>>No, RFC 3095 does not assume floating point. All
>>>>
>>>>encoding/decoding operations
>>>>are integer based.
>>>>
>>>>>Zhigang
>>>>>
>>>>>
>>>>>>-----Original Message-----
>>>>>>From: ext Pawel Szymanski [mailto:szym_paw@wp.pl]
>>>>>>Sent: 26 March, 2004 02:33 AM
>>>>>>To: Liu Zhigang.C (Nokia-NRC/Dallas)
>>>>>>Cc: kristofer.sandlund@effnet.com; kd.singh@enst-bretagne.fr;
>>>>>>lars-erik.jonsson@ericsson.com; rohc@ietf.org
>>>>>>Subject: RE: [rohc] Slope used to compress/decompress RTP
>>>>>>Timestamp field
>>>>>>
>>>>>>
>>>>>>
>>>>>>Hi Zhigang,
>>>>>>
>>>>>>
>>>>>>>>I base this on the following observations:
>>>>>>>>
>>>>>>>>* 4.5.3. Scaled RTP Timestamp encoding
>>>>>>>>    3. Decompression: When receiving the=20
>>
>>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.
>>>>>>>>
>>>>>>>>If there acutally was a slope, it should have been in
>>>>>>
>>>>>>this formula.
>>>>>>
>>>>>>>This is a misunderstanding. Note that there are two
>>>>
>>>>*separate* steps
>>>>
>>>>>>>involved. The formula is for the second step: deriving TS
>>>>>>
>>>>>>from TS_SCALED.
>>>>>>
>>>>>>>The slope plays a role in the first step: "the decompressor
>>>>>>
>>>>>>first derives
>>>>>>
>>>>>>>the value of the original TS_SCALED". I thought this is
>>>>
>>>>clear from
>>>>
>>>>>>>section 4.5.3. More clarifications below.
>>>>>>
>>>>>>I think that the decompressor uses slope when it receives
>>>>>>packets without TS
>>>>>>field (for example UO-0 packets).
>>>>>>
>>>>>>In this case it uses the formula to calculate new scaled
>>>>>>timestamp value:
>>>>>>
>>>>>>   new_scaled_timestamp =3D old_scaled_timestamp + (new_SN -
>>>>>>old_SN)*slope
>>>>>>
>>>>>>Next it calculates the unscaled timestamp using the
>>>>
>>>>formula from 4.5.3
>>>>
>>>>>>When the decompressor receives a packet with TS field, it
>>>>>>does not use slope.
>>>>>>It decompresses the new scaled timestamp value using LSB
>>>>>>method. Next it uses
>>>>>>the formula from 4.5.3 to calculate the unscaled timestamp.
>>>>>>
>>>>>>When the decompressor receives two or more packets containing
>>>>>>TS value in raw,
>>>>>>it can calculate a new slope value, for example using=20
>>
>>the formula:
>>
>>>>>>  new_slope =3D (new_scaled_timestamp - old_scaled_timestamp) /
>>>>>>(new_SN - old_SN)
>>>>>>
>>>>>>Am I correct ?
>>>>>>
>>>>>>An additional question is whether the slope is an integer
>>>>>>number or could it be
>>>>>>a floating point number ?
>>>>>>
>>>>>>Regards
>>>>>>
>>>>>>Pawel
>>>>>>
>>>>>>
>>>>>>----------------------------------------------------
>>>>>>Zobacz niezwyk=B3y koncert: "Niemena Pami=EAci Gda=F1ski Rapsod"
>>>>>>Najwi=EAksze przeboje artysty w nowych zaskakuj=B1cych=20
>>
>>aran=BFacjach.
>>
>>>>>>http://klik.wp.pl/?adr=3Dhttp%3A%2F%2Fmuzyka.wp.pl%2Fimprezy.htm
>>>>>
>>>>>l%3Fidn%3D874&sid=3D151
>>>>>
>>>>>
>>>>>
>>>>>_______________________________________________
>>>>>Rohc mailing list
>>>>>Rohc@ietf.org
>>>>>https://www1.ietf.org/mailman/listinfo/rohc
>>>>>
>>>>
>>>>----------------------------------------------------
>>>>=A3odzi=B1 po Wi=B6le - najciekawsze etiudy w Warszawie.
>>>>http://klik.wp.pl/?adr=3Dhttp%3A%2F%2Ffilm.wp.pl%2Fp%2Fwiadomosc
>>>
>>>.html%3Fid%3D55832&sid=3D152
>>>
>>>
>>>
>>
>>


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



From exim@www1.ietf.org  Tue Mar 30 03:21:33 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07291
	for <rohc-archive@odin.ietf.org>; Tue, 30 Mar 2004 03:21:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8EUb-0000Qb-5T
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 03:21:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2U8L5I5001639
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 03:21:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8EUa-0000QM-8Y
	for rohc-web-archive@optimus.ietf.org; Tue, 30 Mar 2004 03:21:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07250
	for <rohc-web-archive@ietf.org>; Tue, 30 Mar 2004 03:21:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8EUX-0000rx-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 03:21:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8ETY-0000iK-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 03:20:01 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8ESa-0000Z4-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 03:19:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8ESb-0000Go-AY; Tue, 30 Mar 2004 03:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8ERp-0000FS-Ax
	for rohc@optimus.ietf.org; Tue, 30 Mar 2004 03:18:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07101
	for <rohc@ietf.org>; Tue, 30 Mar 2004 03:18:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8ERn-0000Rs-00
	for rohc@ietf.org; Tue, 30 Mar 2004 03:18:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8EQt-0000JS-00
	for rohc@ietf.org; Tue, 30 Mar 2004 03:17:16 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8EQV-0000Af-00
	for rohc@ietf.org; Tue, 30 Mar 2004 03:16:52 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2U8GqAh023257
	for <rohc@ietf.org>; Tue, 30 Mar 2004 10:16:52 +0200
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 30 Mar 2004 10:16:52 +0200
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <H8FHP1FT>; Tue, 30 Mar 2004 10:16:52 +0200
Message-ID: <A943FD84BD9ED41193460008C7918050072E94F4@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'Kristofer Sandlund'" <kristofer.sandlund@effnet.com>,
        zhigang.c.liu@nokia.com
Cc: kd.singh@enst-bretagne.fr, szym_paw@wp.pl, rohc@ietf.org
Subject: RE: [rohc] Slope used to compress/decompress RTP Timestamp field
Date: Tue, 30 Mar 2004 10:16:39 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 30 Mar 2004 08:16:52.0268 (UTC) FILETIME=[5B34D6C0:01C4162F]
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

Hi all,

I was just about to send my comments on this thread, but as 
Kristofer has already expressed similar arguments, I will just
conclude that I agree to all of them. We have to be very careful
with "over interpreting" things in our specifications. It is
clear to me that RFC 3095 really does not specify slopes in a
normative way, which would be needed for interoperability. The
implicit slope update procedure would only buy us something if
a compressor could assume the decompressor will do such updates
(and how). That would require such procedures to be normatively
defined (MUSTs, REQUIREDs, etc), which is not the case in 3095.

Further, I also agree with the questioning of its technical
merits.

/L-E


> -----Original Message-----
> From: rohc-admin@ietf.org [mailto:rohc-admin@ietf.org]On Behalf Of
> Kristofer Sandlund
> Sent: den 30 mars 2004 09:54
> To: zhigang.c.liu@nokia.com
> Cc: kd.singh@enst-bretagne.fr; szym_paw@wp.pl; Lars-Erik Jonsson
> (LU/EAB); rohc@ietf.org
> Subject: Re: [rohc] Slope used to compress/decompress RTP Timestamp
> field
> 
> 
> Hi Zhigang and others!
> 
> I'm not yet convinced of the slope as described here, so I'll 
> outline why.
> 
> 1) It is not well defined in the spec (at least U/O-mode).
> 
> For example, the definition of the timestamp stride (section 
> 2.0) is as follows:
>     Timestamp stride
> 
>        The timestamp stride (TS_STRIDE) is the expected 
> increase in the
>        timestamp value between two RTP packets with 
> consecutive sequence
>        numbers.
> 
> In the two examples taken so far (one semi-static TS for 
> video, and the other 
> "2,4,6" increase of the TS), the assumption used has been 
> that the TS_STRIDE is 
> set to "the difference in TS between two FRAMES", and not the 
> difference between 
> two PACKETS as defined above. According to the definition 
> above, the TS_STRIDE 
> should be 0 in the semi-static case (see my last mail how I 
> felt the sloution 
> can be) and "2" in the other case, and then, no slope is 
> needed for these 
> specific cases.
> 
> Zhigang wrote:
>  >Although the question was raised due to TS, I'd like to emphasize
>  >that the concept of slope is not only for TS. As Kamal pointed out,
>  >slope is one parameter of the function (see text below from 
> section 3.4).
>  >
>  >   The way ROHC RTP compression operates, then, is to first 
> establish
>  >   functions from SN to the other fields, and then reliably 
> communicate
>  >   the SN.  Whenever a function from SN to another field 
> changes, i.e.,
>  >   the existing function gives a result which is different from the
>  >   field in the header to be compressed, additional 
> information is sent
>  >   to update the parameters of that function.
> 
> This text can as well be interpreted as if the function is simply the 
> scaling/offset scheme of the TS and that the IPID offset 
> encoding is this 
> function for IPID. The slope itself is not mentioned in this 
> section, so I can't 
> see this as a "proof" for slope.
> 
> (see my previous mail for some more comments on why I don't 
> think it is defined)
> 
> 2) The updating of the slope in U/O-mode is inconsistent with 
> the definition of 
> these modes.
> 
> Every time the decompressor sees a packet in U/O-modes, the 
> context is updated 
> for all fields in the compressed packet and those inferred 
> from them. If slope 
> is to be used, suddenly we need two consecutive packets to 
> update this context 
> value. Since this is neither clear from the spec (there is no 
> definition in 3095 
> that says that U/O-mode should only update slope after two 
> packets seen), and 
> the fact that it is different from all other updating, this 
> is bound to cause 
> interoperability problems.
> Note: I am aware that sending "2*L" UO-1 packets can yield 
> larger compression 
> efficiency than ("L" UO-1-ID-ext3 + "L" UO-0), but see below 
> for other reasons 
> of why I think this tradeoff is worth it.
> 
> 3) Slow convergence time
> 
> a) U/O-mode
> Due to the need for sending "more than L" packets to update 
> the context, it will 
> take longer time to update the context at the decompressor 
> than it would to 
> update the TS_STRIDE (or TS_OFFSET for that matter), which 
> means I will have to 
> send a larger number of non-SO packets. Therefore, if we see 
> frequent changes in 
> the pattern, the scheme using slope will have a harder time 
> to ever get to use 
> UO-0 packets than a scheme without slope.
> 
> b) R-mode
> Note: For R-mode, the updating of the slope is almost defined 
> (5.5.1.2), so it 
> actually makes slightly sense to have a slope in R-mode than 
> in U/O-modes when 
> reading the spec.
> In R-mode, two ACKs are required to update the slope. 
> Considering the sparse ACK 
> mechanism, the compressor is likely to have to wait quite a 
> long time before he 
> knows that the slope has been updated, and therefore, the new 
> slope value cannot 
> be used very soon. Since the slope is supposed to be used in 
> situations where 
> the TS-delta changes "frequently", it is likely that it has 
> changed "again" 
> before the time that I have seen two ACKs. If not using slope 
> (changing the 
> TS_STRIDE or offset) would only have required one ACK meaning 
> a faster 
> convergence time to SO.
> 
> 4) Complexity
> As I have written above, the slope will have a very different 
> updating property 
> that other fields, so it will cause quite a bit of extra 
> complexity to handle 
> this. Since the "common case" is a more stable pattern of the 
> timestamp change, 
> my personal opinion is that it is not worth optimizing with 
> the slope, since it 
> can be made to work with just the stride/offset.
> 
> 
> I also read up in the mail archive, and the last time the 
> slope came up on the 
> list was:
> http://www1.ietf.org/mail-archive/working-groups/rohc/current/
> msg01502.html
> And then, the conclusion seems to have been that there was no 
> slope (for IPID at 
> least) in the spec.
> 
> So as a summary, I would like to see an addition to the 
> implementer's guide that 
> says that there "is no slope" (but feel free to convince me 
> that slope is a good 
> thing). At the very least, I feel quite strongly that 
> U/O-mode should not have 
> one since there's a lack of a firm definition of it in 3095.
> 
> Best regards,
>       Kristofer Sandlund, Effnet AB
> 
> 
> zhigang.c.liu@nokia.com wrote:
> > It's not specified in RFC 3095. So, it's an implementation choice.
> > 
> > 5.3.1.1.1.  Optimistic approach, upwards transition
> > 
> >    [snip]
> > 
> >    The compressor normally obtains its confidence about decompressor
> >    status by sending several packets with the same 
> information according
> >    to the lower compression state.  If the decompressor 
> receives any of
> >    these packets, it will be in sync with the compressor.  
> The number of
> >    consecutive packets to send for confidence is not defined in this
> >    document.
> > 
> > BR,
> > Zhigang
> > 
> > 
> >>-----Original Message-----
> >>From: ext kamal deep singh [mailto:kd.singh@enst-bretagne.fr]
> >>Sent: 27 March, 2004 09:23 AM
> >>To: Liu Zhigang.C (Nokia-NRC/Dallas); szym_paw@wp.pl
> >>Cc: kristofer.sandlund@effnet.com; 
> >>lars-erik.jonsson@ericsson.com; rohc@ietf.org
> >>Subject: Re: [rohc] Slope used to compress/decompress RTP 
> >>Timestamp field
> >>
> >>
> >>
> >>Hi,
> >>
> >>I have one question below.
> >>
> >>
> >>>Actually for robustness, the compressor must make sure that 
> >>
> >>at least two
> >>("FO") packets with TS >field have been received by the 
> >>decompressor before
> >>it can transit to SO state and send Type-0 >packets. It will 
> >>ensure that the
> >>decompressor acquires both slope and offset of the function 
> >>from >SN to TS.
> >>
> >>In U and O mode, how will compressor base its confidence?
> >>By sending L + 1 or 2L packets?
> >>
> >>Or should it be left as an implementation choice?
> >>
> >>
> >>regards,
> >>Kamal
> >>
> >>
> >>
> >>
> >>
> >>>4.3.1.3.  Second Order (SO) State
> >>>
> >>>   This is the state where compression is optimal.  The compressor
> >>>   enters the SO state when the header to be compressed is 
> >>
> >>completely
> >>
> >>>   predictable given the SN (RTP Sequence Number) and the 
> >>
> >>compressor is
> >>
> >>>   sufficiently confident that the decompressor has acquired all
> >>>   parameters of the functions from SN to other fields
> >>>
> >>>BR,
> >>>Zhigang
> >>>
> >>>
> >>>>Hi Zighang,
> >>>>
> >>>>I wonder how decompressor should behave if it receives only
> >>>>one packet with TS
> >>>>field between two packets without TS ( for example when it
> >>>>receives UO-0
> >>>>packet, next UO-1-TS and next again UO-0 packet).
> >>>>
> >>>>I can see two options:
> >>>>
> >>>>1. The decompressor uses the old slope value (e.g. the 
> >>
> >>one it used to
> >>
> >>>>decompress the first UO-0 packet) to calculate timestamp for
> >>>>the second UO-0  packet. Here we assume that single TS 
> >>
> >>communicates
> >>change in
> >>
> >>>>the offset.
> >>>>
> >>>>2. It calculates a new slope basing on the timestamp values
> >>>>decompressed from  the first UO-0 packet and the UO-1 
> >>
> >>packet and next it
> >>uses
> >>
> >>>>the new slope to calculate the timestamp for the second 
> >>
> >>UO-0 packet.
> >>
> >>>>Which of the above is correct ?
> >>>>
> >>>>Regards
> >>>>
> >>>>Pawel
> >>>>
> >>>>
> >>>>>Hi Pawel,
> >>>>>
> >>>>>Yes, your understanding is correct. It's basically the
> >>>>
> >>>>geometry: two points
> >>>>determine a line. Besides the slope, two TS values also give
> >>>>you the offset.
> >>>>
> >>>>>No, RFC 3095 does not assume floating point. All
> >>>>
> >>>>encoding/decoding operations
> >>>>are integer based.
> >>>>
> >>>>>Zhigang
> >>>>>
> >>>>>
> >>>>>>-----Original Message-----
> >>>>>>From: ext Pawel Szymanski [mailto:szym_paw@wp.pl]
> >>>>>>Sent: 26 March, 2004 02:33 AM
> >>>>>>To: Liu Zhigang.C (Nokia-NRC/Dallas)
> >>>>>>Cc: kristofer.sandlund@effnet.com; kd.singh@enst-bretagne.fr;
> >>>>>>lars-erik.jonsson@ericsson.com; rohc@ietf.org
> >>>>>>Subject: RE: [rohc] Slope used to compress/decompress RTP
> >>>>>>Timestamp field
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>Hi Zhigang,
> >>>>>>
> >>>>>>
> >>>>>>>>I base this on the following observations:
> >>>>>>>>
> >>>>>>>>* 4.5.3. Scaled RTP Timestamp encoding
> >>>>>>>>    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 =
> >>>>
> >>>>>>>>       TS_SCALED * TS_STRIDE + TS_OFFSET.
> >>>>>>>>
> >>>>>>>>If there acutally was a slope, it should have been in
> >>>>>>
> >>>>>>this formula.
> >>>>>>
> >>>>>>>This is a misunderstanding. Note that there are two
> >>>>
> >>>>*separate* steps
> >>>>
> >>>>>>>involved. The formula is for the second step: deriving TS
> >>>>>>
> >>>>>>from TS_SCALED.
> >>>>>>
> >>>>>>>The slope plays a role in the first step: "the decompressor
> >>>>>>
> >>>>>>first derives
> >>>>>>
> >>>>>>>the value of the original TS_SCALED". I thought this is
> >>>>
> >>>>clear from
> >>>>
> >>>>>>>section 4.5.3. More clarifications below.
> >>>>>>
> >>>>>>I think that the decompressor uses slope when it receives
> >>>>>>packets without TS
> >>>>>>field (for example UO-0 packets).
> >>>>>>
> >>>>>>In this case it uses the formula to calculate new scaled
> >>>>>>timestamp value:
> >>>>>>
> >>>>>>   new_scaled_timestamp = old_scaled_timestamp + (new_SN -
> >>>>>>old_SN)*slope
> >>>>>>
> >>>>>>Next it calculates the unscaled timestamp using the
> >>>>
> >>>>formula from 4.5.3
> >>>>
> >>>>>>When the decompressor receives a packet with TS field, it
> >>>>>>does not use slope.
> >>>>>>It decompresses the new scaled timestamp value using LSB
> >>>>>>method. Next it uses
> >>>>>>the formula from 4.5.3 to calculate the unscaled timestamp.
> >>>>>>
> >>>>>>When the decompressor receives two or more packets containing
> >>>>>>TS value in raw,
> >>>>>>it can calculate a new slope value, for example using 
> >>
> >>the formula:
> >>
> >>>>>>  new_slope = (new_scaled_timestamp - old_scaled_timestamp) /
> >>>>>>(new_SN - old_SN)
> >>>>>>
> >>>>>>Am I correct ?
> >>>>>>
> >>>>>>An additional question is whether the slope is an integer
> >>>>>>number or could it be
> >>>>>>a floating point number ?
> >>>>>>
> >>>>>>Regards
> >>>>>>
> >>>>>>Pawel
> 

This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Tue Mar 30 03:22:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07351
	for <rohc-archive@odin.ietf.org>; Tue, 30 Mar 2004 03:22:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8EVX-0000TD-EO
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 03:22:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2U8M3bN001801
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 03:22:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8EVX-0000Sy-9i
	for rohc-web-archive@optimus.ietf.org; Tue, 30 Mar 2004 03:22:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07311
	for <rohc-web-archive@ietf.org>; Tue, 30 Mar 2004 03:22:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8EVU-00011M-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 03:22:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8EUW-0000rp-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 03:21:01 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8ETX-0000hf-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 03:19:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8ETZ-0000Lm-8O; Tue, 30 Mar 2004 03:20:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8ESj-0000ID-UR
	for rohc@optimus.ietf.org; Tue, 30 Mar 2004 03:19:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07197
	for <rohc@ietf.org>; Tue, 30 Mar 2004 03:19:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8ESh-0000ab-00
	for rohc@ietf.org; Tue, 30 Mar 2004 03:19:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8ERo-0000SE-00
	for rohc@ietf.org; Tue, 30 Mar 2004 03:18:13 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8ERP-0000Js-00
	for rohc@ietf.org; Tue, 30 Mar 2004 03:17:47 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id i2U8HmYG008791
	for <rohc@ietf.org>; Tue, 30 Mar 2004 10:17:48 +0200 (MEST)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 30 Mar 2004 10:17:48 +0200
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <H8FHP13Q>; Tue, 30 Mar 2004 10:17:48 +0200
Message-ID: <A943FD84BD9ED41193460008C7918050072E94F5@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>,
        kd.singh@enst-bretagne.fr, szym_paw@wp.pl
Cc: kristofer.sandlund@effnet.com, rohc@ietf.org
Subject: RE: [rohc] Slope used to compress/decompress RTP Timestamp field
Date: Tue, 30 Mar 2004 10:17:34 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-2"
X-OriginalArrivalTime: 30 Mar 2004 08:17:48.0347 (UTC) FILETIME=[7CA1D0B0:01C4162F]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by penguin-ext.wise.edt.ericsson.se id i2U8HmYG008791
Content-Transfer-Encoding: quoted-printable
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Agreed, good point!

/L-E


> It's not specified in RFC 3095. So, it's an implementation choice.
>=20
> 5.3.1.1.1.  Optimistic approach, upwards transition
>=20
>    [snip]
>=20
>    The compressor normally obtains its confidence about decompressor
>    status by sending several packets with the same=20
> information according
>    to the lower compression state.  If the decompressor=20
> receives any of
>    these packets, it will be in sync with the compressor. =20
> The number of
>    consecutive packets to send for confidence is not defined in this
>    document.
>=20
> BR,
> Zhigang
>=20
> > -----Original Message-----
> > From: ext kamal deep singh [mailto:kd.singh@enst-bretagne.fr]
> > Sent: 27 March, 2004 09:23 AM
> > To: Liu Zhigang.C (Nokia-NRC/Dallas); szym_paw@wp.pl
> > Cc: kristofer.sandlund@effnet.com;=20
> > lars-erik.jonsson@ericsson.com; rohc@ietf.org
> > Subject: Re: [rohc] Slope used to compress/decompress RTP=20
> > Timestamp field
> >=20
> >=20
> >=20
> > Hi,
> >=20
> > I have one question below.
> >=20
> > > Actually for robustness, the compressor must make sure that=20
> > at least two
> > ("FO") packets with TS >field have been received by the=20
> > decompressor before
> > it can transit to SO state and send Type-0 >packets. It will=20
> > ensure that the
> > decompressor acquires both slope and offset of the function=20
> > from >SN to TS.
> >=20
> > In U and O mode, how will compressor base its confidence?
> > By sending L + 1 or 2L packets?
> >=20
> > Or should it be left as an implementation choice?
> >=20
> >=20
> > regards,
> > Kamal
> >=20
> >=20
> >=20
> >=20
> > > 4.3.1.3.  Second Order (SO) State
> > >
> > >    This is the state where compression is optimal.  The compressor
> > >    enters the SO state when the header to be compressed is=20
> > completely
> > >    predictable given the SN (RTP Sequence Number) and the=20
> > compressor is
> > >    sufficiently confident that the decompressor has acquired all
> > >    parameters of the functions from SN to other fields
> > >
> > > BR,
> > > Zhigang
> > >
> > > >
> > > > Hi Zighang,
> > > >
> > > > I wonder how decompressor should behave if it receives only
> > > > one packet with TS
> > > > field between two packets without TS ( for example when it
> > > > receives UO-0
> > > > packet, next UO-1-TS and next again UO-0 packet).
> > > >
> > > > I can see two options:
> > > >
> > > > 1. The decompressor uses the old slope value (e.g. the=20
> > one it used to
> > > > decompress the first UO-0 packet) to calculate timestamp for
> > > > the second UO-0  packet. Here we assume that single TS=20
> > communicates
> > change in
> > > > the offset.
> > > >
> > > > 2. It calculates a new slope basing on the timestamp values
> > > > decompressed from  the first UO-0 packet and the UO-1=20
> > packet and next it
> > uses
> > > > the new slope to calculate the timestamp for the second=20
> > UO-0 packet.
> > > >
> > > > Which of the above is correct ?
> > > >
> > > > Regards
> > > >
> > > > Pawel
> > > >
> > > > > Hi Pawel,
> > > > >
> > > > > Yes, your understanding is correct. It's basically the
> > > > geometry: two points
> > > > determine a line. Besides the slope, two TS values also give
> > > > you the offset.
> > > > >
> > > > > No, RFC 3095 does not assume floating point. All
> > > > encoding/decoding operations
> > > > are integer based.
> > > > >
> > > > > Zhigang
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: ext Pawel Szymanski [mailto:szym_paw@wp.pl]
> > > > > > Sent: 26 March, 2004 02:33 AM
> > > > > > To: Liu Zhigang.C (Nokia-NRC/Dallas)
> > > > > > Cc: kristofer.sandlund@effnet.com;=20
> kd.singh@enst-bretagne.fr;
> > > > > > lars-erik.jonsson@ericsson.com; rohc@ietf.org
> > > > > > Subject: RE: [rohc] Slope used to compress/decompress RTP
> > > > > > Timestamp field
> > > > > >
> > > > > >
> > > > > >
> > > > > > Hi Zhigang,
> > > > > >
> > > > > > > > I base this on the following observations:
> > > > > > > >
> > > > > > > > * 4.5.3. Scaled RTP Timestamp encoding
> > > > > > > >     3. Decompression: When receiving the=20
> > 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.
> > > > > > > >
> > > > > > > > If there acutally was a slope, it should have been in
> > > > > > this formula.
> > > > > > >
> > > > > > > This is a misunderstanding. Note that there are two
> > > > *separate* steps
> > > > > > > involved. The formula is for the second step: deriving TS
> > > > > > from TS_SCALED.
> > > > > > > The slope plays a role in the first step: "the=20
> decompressor
> > > > > > first derives
> > > > > > > the value of the original TS_SCALED". I thought this is
> > > > clear from
> > > > > > > section 4.5.3. More clarifications below.
> > > > > >
> > > > > > I think that the decompressor uses slope when it receives
> > > > > > packets without TS
> > > > > > field (for example UO-0 packets).
> > > > > >
> > > > > > In this case it uses the formula to calculate new scaled
> > > > > > timestamp value:
> > > > > >
> > > > > >    new_scaled_timestamp =3D old_scaled_timestamp + (new_SN -
> > > > > > old_SN)*slope
> > > > > >
> > > > > > Next it calculates the unscaled timestamp using the
> > > > formula from 4.5.3
> > > > > >
> > > > > > When the decompressor receives a packet with TS field, it
> > > > > > does not use slope.
> > > > > > It decompresses the new scaled timestamp value using LSB
> > > > > > method. Next it uses
> > > > > > the formula from 4.5.3 to calculate the unscaled timestamp.
> > > > > >
> > > > > > When the decompressor receives two or more packets=20
> containing
> > > > > > TS value in raw,
> > > > > > it can calculate a new slope value, for example using=20
> > the formula:
> > > > > >
> > > > > >   new_slope =3D (new_scaled_timestamp -=20
> old_scaled_timestamp) /
> > > > > > (new_SN - old_SN)
> > > > > >
> > > > > > Am I correct ?
> > > > > >
> > > > > > An additional question is whether the slope is an integer
> > > > > > number or could it be
> > > > > > a floating point number ?
> > > > > >
> > > > > > Regards
> > > > > >
> > > > > > Pawel
> > > > > >
> > > > > >
> > > > > > ----------------------------------------------------
> > > > > > Zobacz niezwyk=B3y koncert: "Niemena Pami=EAci Gda=F1ski Raps=
od"
> > > > > > Najwi=EAksze przeboje artysty w nowych zaskakuj=B1cych=20
> > aran=BFacjach.
> > > > > >=20
http://klik.wp.pl/?adr=3Dhttp%3A%2F%2Fmuzyka.wp.pl%2Fimprezy.htm
> > > > l%3Fidn%3D874&sid=3D151
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Rohc mailing list
> > > > Rohc@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/rohc
> > > >
> > >
> > > ----------------------------------------------------
> > > =A3odzi=B1 po Wi=B6le - najciekawsze etiudy w Warszawie.
> > > http://klik.wp.pl/?adr=3Dhttp%3A%2F%2Ffilm.wp.pl%2Fp%2Fwiadomosc
> > .html%3Fid%3D55832&sid=3D152
> >
> >
> >
>=20
>=20

This communication is confidential and intended solely for the addressee(=
s). Any unauthorized review, use, disclosure or distribution is prohibite=
d. If you believe this message has been sent to you in error, please noti=
fy the sender by replying to this transmission and delete the message wit=
hout disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interrupt=
ion, unauthorized amendment, tampering and viruses, and we only send and =
receive e-mails on the basis that we are not liable for any such corrupti=
on, interception, amendment, tampering or viruses or any consequences the=
reof.


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



From exim@www1.ietf.org  Tue Mar 30 06:29:56 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13386
	for <rohc-archive@odin.ietf.org>; Tue, 30 Mar 2004 06:29:55 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8HQv-0007MM-CC
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 06:29:30 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2UBTTWA028284
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 06:29:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8HQv-0007M7-5l
	for rohc-web-archive@optimus.ietf.org; Tue, 30 Mar 2004 06:29:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13379
	for <rohc-web-archive@ietf.org>; Tue, 30 Mar 2004 06:29:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8HQr-000541-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 06:29:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8HQ5-0004ti-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 06:28:38 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8HPS-0004ii-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 06:27:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8HPV-0007FH-GR; Tue, 30 Mar 2004 06:28:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8HOk-00076s-A1
	for rohc@optimus.ietf.org; Tue, 30 Mar 2004 06:27:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13257
	for <rohc@ietf.org>; Tue, 30 Mar 2004 06:27:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8HOg-0004ej-00
	for rohc@ietf.org; Tue, 30 Mar 2004 06:27:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8HNg-0004Ua-00
	for rohc@ietf.org; Tue, 30 Mar 2004 06:26:09 -0500
Received: from imh.informatik.uni-bremen.de ([134.102.224.4] helo=informatik.uni-bremen.de)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8HMi-0004JQ-00
	for rohc@ietf.org; Tue, 30 Mar 2004 06:25:08 -0500
Received: from [IPv6:::1] (imh.informatik.uni-bremen.de [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id i2UBP24V008123;
	Tue, 30 Mar 2004 13:25:03 +0200 (MEST)
In-Reply-To: <200403291617.VAA26457@WS0005.indiatimes.com>
References: <200403291617.VAA26457@WS0005.indiatimes.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <E362D010-823C-11D8-A465-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, <rohc@ietf.org>
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] Doubt in SigComp instruction - COMPARE
Date: Tue, 30 Mar 2004 13:25:03 +0200
To: "jb_sigcomp" <jb_sigcomp@indiatimes.com>
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> Memory address being talked about in above explaination is actually 
> bytecode address. It should be like:

Memory address is a technical term used in RFC3320 (about 43 times).
"Bytecode address" isn't.

> if (val1 Indiatimes Email now powered by APIC Advantage. Help!
> HelpClick on the image to chat with me

Since your message arrived garbled, maybe I didn't get your point.
(Looking at your excerpt from RFC3320, your mailer seems to eat 
everything between "<" and ">".)

Gruesse, Carsten


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



From exim@www1.ietf.org  Tue Mar 30 08:56:52 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19053
	for <rohc-archive@odin.ietf.org>; Tue, 30 Mar 2004 08:56:52 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Jj6-0004rc-5p
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 08:56:25 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2UDuOML018690
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 08:56:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Jj5-0004rN-TY
	for rohc-web-archive@optimus.ietf.org; Tue, 30 Mar 2004 08:56:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18978
	for <rohc-web-archive@ietf.org>; Tue, 30 Mar 2004 08:56:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8Jj4-0003MB-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 08:56:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8JiA-0003Bt-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 08:55:27 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8Jhk-00032w-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 08:55:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Jhl-0004Sh-5i; Tue, 30 Mar 2004 08:55:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8JhB-0004OT-Hj
	for rohc@optimus.ietf.org; Tue, 30 Mar 2004 08:54:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18889
	for <rohc@ietf.org>; Tue, 30 Mar 2004 08:54:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8JhA-00031V-00
	for rohc@ietf.org; Tue, 30 Mar 2004 08:54:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8JgA-0002tA-00
	for rohc@ietf.org; Tue, 30 Mar 2004 08:53:23 -0500
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8JfU-0002co-00
	for rohc@ietf.org; Tue, 30 Mar 2004 08:52:40 -0500
Received: from courrier.rennes.enst-bretagne.fr (f1-clust.rennes.enst-bretagne.fr [193.52.74.16])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with ESMTP id i2UDpm918870;
	Tue, 30 Mar 2004 15:51:48 +0200
Received: from pcrsm7 ([193.52.74.238])
	by courrier.rennes.enst-bretagne.fr (8.12.11/8.12.11/2004.01.01) with SMTP id i2UDpnpB016543;
	Tue, 30 Mar 2004 15:51:49 +0200 (MEST)
Message-ID: <006701c4165e$2617b000$ee4a34c1@rennes.enstbretagne.fr>
From: "kamal deep singh" <kd.singh@enst-bretagne.fr>
To: <rohc@ietf.org>, "Kavitha KR" <Kavitha.KR@lntinfotech.com>
References: <OF61AED2EF.8CFE32E6-ON65256E66.00174780@lntinfotech.com>
Subject: Re: [rohc] Slope used to compress/decompress RTP Timestamp field
Date: Tue, 30 Mar 2004 15:51:49 +0200
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.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Kavitha,

'L' is one of the parameters used in U and O mode of ROHC.

You will find it written in section 5.3.1.1.1 that .

"The compressor normally obtains its confidence about decompressor
   status by sending several packets with the same information according
   to the lower compression state.  If the decompressor receives any of
   these packets, it will be in sync with the compressor.  The number of
   consecutive packets to send for confidence is not defined in this
   document.
"
The number of consequetive packets to send is 'L'

regards,
Kamal


>
> I think it is rather left to implementation.
> For e.g in the 3GPP2 cdma networks, the default value is simply taken to
be
> 3.
>
> Btw, what is 'L'?
>
> regards,
> kavitha.
>
>
>
>
>                       "kamal deep
>                       singh"                   To:
<zhigang.c.liu@nokia.com>, <szym_paw@wp.pl>
>                       <kd.singh@enst-br        cc:
<kristofer.sandlund@effnet.com>, <lars-erik.jonsson@ericsson.com>,
>                       etagne.fr>                <rohc@ietf.org>
>                       Sent by:                 Subject:  Re: [rohc] Slope
used to compress/decompress RTP Timestamp field
>                       rohc-admin@ietf.o
>                       rg
>
>
>                       03/27/2004 08:52
>                       PM
>
>
>
>
>
>
> Hi,
>
> I have one question below.
>
> > Actually for robustness, the compressor must make sure that at least two
> ("FO") packets with TS >field have been received by the decompressor
before
> it can transit to SO state and send Type-0 >packets. It will ensure that
> the
> decompressor acquires both slope and offset of the function from >SN to
TS.
>
> In U and O mode, how will compressor base its confidence?
> By sending L + 1 or 2L packets?
>
> Or should it be left as an implementation choice?
>
>
> regards,
> Kamal
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> This email may contain confidential or privileged information for the
> intended recipient(s). If you are not the intended recipient, please do
not
> use or disseminate the information, notify the sender and delete it from
> your system. Thanks
>
>
> _______________________________________________
> 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 exim@www1.ietf.org  Tue Mar 30 12:26:21 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01347
	for <rohc-archive@odin.ietf.org>; Tue, 30 Mar 2004 12:26:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Mzp-00040f-18
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 12:25:54 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2UHPrQw015413
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 12:25:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Mzo-00040W-OW
	for rohc-web-archive@optimus.ietf.org; Tue, 30 Mar 2004 12:25:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01340
	for <rohc-web-archive@ietf.org>; Tue, 30 Mar 2004 12:25:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8Mzn-00007E-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 12:25:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8Mz3-0007jl-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 12:25:07 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8My3-0007U8-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 12:24:03 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B8My3-0002kD-Vn
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 12:24:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8My1-0003kK-Ik; Tue, 30 Mar 2004 12:24:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8MxE-0003fN-1g
	for rohc@optimus.ietf.org; Tue, 30 Mar 2004 12:23:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01092
	for <rohc@ietf.org>; Tue, 30 Mar 2004 12:23:08 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8MxC-0007Gm-00
	for rohc@ietf.org; Tue, 30 Mar 2004 12:23:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8Mvi-0006wg-00
	for rohc@ietf.org; Tue, 30 Mar 2004 12:21:40 -0500
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8MuX-0006Xi-00
	for rohc@ietf.org; Tue, 30 Mar 2004 12:20:25 -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 i2UHKGD23072;
	Tue, 30 Mar 2004 20:20:16 +0300 (EET DST)
X-Scanned: Tue, 30 Mar 2004 20:19:06 +0300 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i2UHJ6PU011477;
	Tue, 30 Mar 2004 20:19:06 +0300
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks003.ntc.nokia.com 00VuLe8G; Tue, 30 Mar 2004 20:19:04 EEST
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 i2UHJ3F02484;
	Tue, 30 Mar 2004 20:19:03 +0300 (EET DST)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Tue, 30 Mar 2004 11:18:37 -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] Slope used to compress/decompress RTP Timestamp field
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Tue, 30 Mar 2004 12:18:35 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B8153723@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] Slope used to compress/decompress RTP Timestamp field
Thread-Index: AcQWLbCWuP4odisXTh+qw13NR2WeAAAQU0CQ
To: <kristofer.sandlund@effnet.com>
Cc: <kd.singh@enst-bretagne.fr>, <szym_paw@wp.pl>,
        <lars-erik.jonsson@ericsson.com>, <rohc@ietf.org>
X-OriginalArrivalTime: 30 Mar 2004 17:18:37.0605 (UTC) FILETIME=[09E5A550:01C4167B]
Content-Transfer-Encoding: quoted-printable
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi Kristofer,

I don't know if you have read my reply to your earlier email:
http://www1.ietf.org/mail-archive/working-groups/rohc/current/msg02042.ht=
ml.
Please let me know if you agree with my comments on your observations,=20
on which you based your conclusion "there cannot be room for a slope =
...".

Also, it seems to me that two different issues are discussed here:
a) Does RFC 3095 describe slope clear enough?
b) Is the slope needed?

For a), if the conclusion is that it's not clear enough in RFC3095, it =
can=20
be clarified in implementation guide.

For b), if the conclusion is that it is not needed, we can create a new=20
profile excluding it.

I'd suggest to keep the two issues separate in order to have a =
well-pointed
discussion.

BR,
Zhigang

> -----Original Message-----
> From: rohc-admin@ietf.org [mailto:rohc-admin@ietf.org]On Behalf Of ext
> Kristofer Sandlund
> Sent: 30 March, 2004 01:54 AM
> To: Liu Zhigang.C (Nokia-NRC/Dallas)
> Cc: kd.singh@enst-bretagne.fr; szym_paw@wp.pl;
> lars-erik.jonsson@ericsson.com; rohc@ietf.org
> Subject: Re: [rohc] Slope used to compress/decompress RTP Timestamp
> field
>=20
>=20
> Hi Zhigang and others!
>=20
> I'm not yet convinced of the slope as described here, so I'll=20
> outline why.
>=20
> 1) It is not well defined in the spec (at least U/O-mode).
>=20
> For example, the definition of the timestamp stride (section=20
> 2.0) is as follows:
>     Timestamp stride
>=20
>        The timestamp stride (TS_STRIDE) is the expected=20
> increase in the
>        timestamp value between two RTP packets with=20
> consecutive sequence
>        numbers.
>=20
> In the two examples taken so far (one semi-static TS for=20
> video, and the other=20
> "2,4,6" increase of the TS), the assumption used has been=20
> that the TS_STRIDE is=20
> set to "the difference in TS between two FRAMES", and not the=20
> difference between=20
> two PACKETS as defined above. According to the definition=20
> above, the TS_STRIDE=20
> should be 0 in the semi-static case (see my last mail how I=20
> felt the sloution=20
> can be) and "2" in the other case, and then, no slope is=20
> needed for these=20
> specific cases.
>=20
> Zhigang wrote:
>  >Although the question was raised due to TS, I'd like to emphasize
>  >that the concept of slope is not only for TS. As Kamal pointed out,
>  >slope is one parameter of the function (see text below from=20
> section 3.4).
>  >
>  >   The way ROHC RTP compression operates, then, is to first=20
> establish
>  >   functions from SN to the other fields, and then reliably=20
> communicate
>  >   the SN.  Whenever a function from SN to another field=20
> changes, i.e.,
>  >   the existing function gives a result which is different from the
>  >   field in the header to be compressed, additional=20
> information is sent
>  >   to update the parameters of that function.
>=20
> This text can as well be interpreted as if the function is simply the=20
> scaling/offset scheme of the TS and that the IPID offset=20
> encoding is this=20
> function for IPID. The slope itself is not mentioned in this=20
> section, so I can't=20
> see this as a "proof" for slope.
>=20
> (see my previous mail for some more comments on why I don't=20
> think it is defined)
>=20
> 2) The updating of the slope in U/O-mode is inconsistent with=20
> the definition of=20
> these modes.
>=20
> Every time the decompressor sees a packet in U/O-modes, the=20
> context is updated=20
> for all fields in the compressed packet and those inferred=20
> from them. If slope=20
> is to be used, suddenly we need two consecutive packets to=20
> update this context=20
> value. Since this is neither clear from the spec (there is no=20
> definition in 3095=20
> that says that U/O-mode should only update slope after two=20
> packets seen), and=20
> the fact that it is different from all other updating, this=20
> is bound to cause=20
> interoperability problems.
> Note: I am aware that sending "2*L" UO-1 packets can yield=20
> larger compression=20
> efficiency than ("L" UO-1-ID-ext3 + "L" UO-0), but see below=20
> for other reasons=20
> of why I think this tradeoff is worth it.
>=20
> 3) Slow convergence time
>=20
> a) U/O-mode
> Due to the need for sending "more than L" packets to update=20
> the context, it will=20
> take longer time to update the context at the decompressor=20
> than it would to=20
> update the TS_STRIDE (or TS_OFFSET for that matter), which=20
> means I will have to=20
> send a larger number of non-SO packets. Therefore, if we see=20
> frequent changes in=20
> the pattern, the scheme using slope will have a harder time=20
> to ever get to use=20
> UO-0 packets than a scheme without slope.
>=20
> b) R-mode
> Note: For R-mode, the updating of the slope is almost defined=20
> (5.5.1.2), so it=20
> actually makes slightly sense to have a slope in R-mode than=20
> in U/O-modes when=20
> reading the spec.
> In R-mode, two ACKs are required to update the slope.=20
> Considering the sparse ACK=20
> mechanism, the compressor is likely to have to wait quite a=20
> long time before he=20
> knows that the slope has been updated, and therefore, the new=20
> slope value cannot=20
> be used very soon. Since the slope is supposed to be used in=20
> situations where=20
> the TS-delta changes "frequently", it is likely that it has=20
> changed "again"=20
> before the time that I have seen two ACKs. If not using slope=20
> (changing the=20
> TS_STRIDE or offset) would only have required one ACK meaning=20
> a faster=20
> convergence time to SO.
>=20
> 4) Complexity
> As I have written above, the slope will have a very different=20
> updating property=20
> that other fields, so it will cause quite a bit of extra=20
> complexity to handle=20
> this. Since the "common case" is a more stable pattern of the=20
> timestamp change,=20
> my personal opinion is that it is not worth optimizing with=20
> the slope, since it=20
> can be made to work with just the stride/offset.
>=20
>=20
> I also read up in the mail archive, and the last time the=20
> slope came up on the=20
> list was:
> http://www1.ietf.org/mail-archive/working-groups/rohc/current/
> msg01502.html
> And then, the conclusion seems to have been that there was no=20
> slope (for IPID at=20
> least) in the spec.
>=20
> So as a summary, I would like to see an addition to the=20
> implementer's guide that=20
> says that there "is no slope" (but feel free to convince me=20
> that slope is a good=20
> thing). At the very least, I feel quite strongly that=20
> U/O-mode should not have=20
> one since there's a lack of a firm definition of it in 3095.
>=20
> Best regards,
>       Kristofer Sandlund, Effnet AB
>=20
>=20
> zhigang.c.liu@nokia.com wrote:
> > It's not specified in RFC 3095. So, it's an implementation choice.
> >=20
> > 5.3.1.1.1.  Optimistic approach, upwards transition
> >=20
> >    [snip]
> >=20
> >    The compressor normally obtains its confidence about decompressor
> >    status by sending several packets with the same=20
> information according
> >    to the lower compression state.  If the decompressor=20
> receives any of
> >    these packets, it will be in sync with the compressor. =20
> The number of
> >    consecutive packets to send for confidence is not defined in this
> >    document.
> >=20
> > BR,
> > Zhigang
> >=20
> >=20
> >>-----Original Message-----
> >>From: ext kamal deep singh [mailto:kd.singh@enst-bretagne.fr]
> >>Sent: 27 March, 2004 09:23 AM
> >>To: Liu Zhigang.C (Nokia-NRC/Dallas); szym_paw@wp.pl
> >>Cc: kristofer.sandlund@effnet.com;=20
> >>lars-erik.jonsson@ericsson.com; rohc@ietf.org
> >>Subject: Re: [rohc] Slope used to compress/decompress RTP=20
> >>Timestamp field
> >>
> >>
> >>
> >>Hi,
> >>
> >>I have one question below.
> >>
> >>
> >>>Actually for robustness, the compressor must make sure that=20
> >>
> >>at least two
> >>("FO") packets with TS >field have been received by the=20
> >>decompressor before
> >>it can transit to SO state and send Type-0 >packets. It will=20
> >>ensure that the
> >>decompressor acquires both slope and offset of the function=20
> >>from >SN to TS.
> >>
> >>In U and O mode, how will compressor base its confidence?
> >>By sending L + 1 or 2L packets?
> >>
> >>Or should it be left as an implementation choice?
> >>
> >>
> >>regards,
> >>Kamal
> >>
> >>
> >>
> >>
> >>
> >>>4.3.1.3.  Second Order (SO) State
> >>>
> >>>   This is the state where compression is optimal.  The compressor
> >>>   enters the SO state when the header to be compressed is=20
> >>
> >>completely
> >>
> >>>   predictable given the SN (RTP Sequence Number) and the=20
> >>
> >>compressor is
> >>
> >>>   sufficiently confident that the decompressor has acquired all
> >>>   parameters of the functions from SN to other fields
> >>>
> >>>BR,
> >>>Zhigang
> >>>
> >>>
> >>>>Hi Zighang,
> >>>>
> >>>>I wonder how decompressor should behave if it receives only
> >>>>one packet with TS
> >>>>field between two packets without TS ( for example when it
> >>>>receives UO-0
> >>>>packet, next UO-1-TS and next again UO-0 packet).
> >>>>
> >>>>I can see two options:
> >>>>
> >>>>1. The decompressor uses the old slope value (e.g. the=20
> >>
> >>one it used to
> >>
> >>>>decompress the first UO-0 packet) to calculate timestamp for
> >>>>the second UO-0  packet. Here we assume that single TS=20
> >>
> >>communicates
> >>change in
> >>
> >>>>the offset.
> >>>>
> >>>>2. It calculates a new slope basing on the timestamp values
> >>>>decompressed from  the first UO-0 packet and the UO-1=20
> >>
> >>packet and next it
> >>uses
> >>
> >>>>the new slope to calculate the timestamp for the second=20
> >>
> >>UO-0 packet.
> >>
> >>>>Which of the above is correct ?
> >>>>
> >>>>Regards
> >>>>
> >>>>Pawel
> >>>>
> >>>>
> >>>>>Hi Pawel,
> >>>>>
> >>>>>Yes, your understanding is correct. It's basically the
> >>>>
> >>>>geometry: two points
> >>>>determine a line. Besides the slope, two TS values also give
> >>>>you the offset.
> >>>>
> >>>>>No, RFC 3095 does not assume floating point. All
> >>>>
> >>>>encoding/decoding operations
> >>>>are integer based.
> >>>>
> >>>>>Zhigang
> >>>>>
> >>>>>
> >>>>>>-----Original Message-----
> >>>>>>From: ext Pawel Szymanski [mailto:szym_paw@wp.pl]
> >>>>>>Sent: 26 March, 2004 02:33 AM
> >>>>>>To: Liu Zhigang.C (Nokia-NRC/Dallas)
> >>>>>>Cc: kristofer.sandlund@effnet.com; kd.singh@enst-bretagne.fr;
> >>>>>>lars-erik.jonsson@ericsson.com; rohc@ietf.org
> >>>>>>Subject: RE: [rohc] Slope used to compress/decompress RTP
> >>>>>>Timestamp field
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>Hi Zhigang,
> >>>>>>
> >>>>>>
> >>>>>>>>I base this on the following observations:
> >>>>>>>>
> >>>>>>>>* 4.5.3. Scaled RTP Timestamp encoding
> >>>>>>>>    3. Decompression: When receiving the=20
> >>
> >>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.
> >>>>>>>>
> >>>>>>>>If there acutally was a slope, it should have been in
> >>>>>>
> >>>>>>this formula.
> >>>>>>
> >>>>>>>This is a misunderstanding. Note that there are two
> >>>>
> >>>>*separate* steps
> >>>>
> >>>>>>>involved. The formula is for the second step: deriving TS
> >>>>>>
> >>>>>>from TS_SCALED.
> >>>>>>
> >>>>>>>The slope plays a role in the first step: "the decompressor
> >>>>>>
> >>>>>>first derives
> >>>>>>
> >>>>>>>the value of the original TS_SCALED". I thought this is
> >>>>
> >>>>clear from
> >>>>
> >>>>>>>section 4.5.3. More clarifications below.
> >>>>>>
> >>>>>>I think that the decompressor uses slope when it receives
> >>>>>>packets without TS
> >>>>>>field (for example UO-0 packets).
> >>>>>>
> >>>>>>In this case it uses the formula to calculate new scaled
> >>>>>>timestamp value:
> >>>>>>
> >>>>>>   new_scaled_timestamp =3D old_scaled_timestamp + (new_SN -
> >>>>>>old_SN)*slope
> >>>>>>
> >>>>>>Next it calculates the unscaled timestamp using the
> >>>>
> >>>>formula from 4.5.3
> >>>>
> >>>>>>When the decompressor receives a packet with TS field, it
> >>>>>>does not use slope.
> >>>>>>It decompresses the new scaled timestamp value using LSB
> >>>>>>method. Next it uses
> >>>>>>the formula from 4.5.3 to calculate the unscaled timestamp.
> >>>>>>
> >>>>>>When the decompressor receives two or more packets containing
> >>>>>>TS value in raw,
> >>>>>>it can calculate a new slope value, for example using=20
> >>
> >>the formula:
> >>
> >>>>>>  new_slope =3D (new_scaled_timestamp - old_scaled_timestamp) /
> >>>>>>(new_SN - old_SN)
> >>>>>>
> >>>>>>Am I correct ?
> >>>>>>
> >>>>>>An additional question is whether the slope is an integer
> >>>>>>number or could it be
> >>>>>>a floating point number ?
> >>>>>>
> >>>>>>Regards
> >>>>>>
> >>>>>>Pawel
> >>>>>>
> >>>>>>
> >>>>>>----------------------------------------------------
> >>>>>>Zobacz niezwyk=B3y koncert: "Niemena Pami=EAci Gda=F1ski Rapsod"
> >>>>>>Najwi=EAksze przeboje artysty w nowych zaskakuj=B1cych=20
> >>
> >>aran=BFacjach.
> >>
> >>>>>>http://klik.wp.pl/?adr=3Dhttp%3A%2F%2Fmuzyka.wp.pl%2Fimprezy.htm
> >>>>>
> >>>>>l%3Fidn%3D874&sid=3D151
> >>>>>
> >>>>>
> >>>>>
> >>>>>_______________________________________________
> >>>>>Rohc mailing list
> >>>>>Rohc@ietf.org
> >>>>>https://www1.ietf.org/mailman/listinfo/rohc
> >>>>>
> >>>>
> >>>>----------------------------------------------------
> >>>>=A3odzi=B1 po Wi=B6le - najciekawsze etiudy w Warszawie.
> >>>>http://klik.wp.pl/?adr=3Dhttp%3A%2F%2Ffilm.wp.pl%2Fp%2Fwiadomosc
> >>>
> >>>.html%3Fid%3D55832&sid=3D152
> >>>
> >>>
> >>>
> >>
> >>
>=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 exim@www1.ietf.org  Tue Mar 30 15:31:09 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10175
	for <rohc-archive@odin.ietf.org>; Tue, 30 Mar 2004 15:31:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Pse-0005o2-Bn
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 15:30:41 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2UKUeqJ022318
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 15:30:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Pse-0005nt-4W
	for rohc-web-archive@optimus.ietf.org; Tue, 30 Mar 2004 15:30:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10157
	for <rohc-web-archive@ietf.org>; Tue, 30 Mar 2004 15:30:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8Psc-0004Ph-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 15:30:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8Prm-0004MP-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 15:29:48 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8Pr2-0004IL-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 15:29:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Pr2-0005df-Tj; Tue, 30 Mar 2004 15:29:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8PqX-0005c9-IH
	for rohc@optimus.ietf.org; Tue, 30 Mar 2004 15:28:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09984
	for <rohc@ietf.org>; Tue, 30 Mar 2004 15:28:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8PqW-0004Dq-00
	for rohc@ietf.org; Tue, 30 Mar 2004 15:28:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8PpX-00047N-00
	for rohc@ietf.org; Tue, 30 Mar 2004 15:27:29 -0500
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8Pob-000400-00
	for rohc@ietf.org; Tue, 30 Mar 2004 15:26:29 -0500
Received: from courrier.rennes.enst-bretagne.fr (f1-clust.rennes.enst-bretagne.fr [193.52.74.16])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with ESMTP id i2UKPsl08548;
	Tue, 30 Mar 2004 22:25:54 +0200
Received: from pcrsm7 ([193.52.74.238])
	by courrier.rennes.enst-bretagne.fr (8.12.11/8.12.11/2004.01.01) with SMTP id i2UKPsDc028380;
	Tue, 30 Mar 2004 22:25:54 +0200 (MEST)
Message-ID: <004801c41695$3445e2f0$ee4a34c1@rennes.enstbretagne.fr>
From: "kamal deep singh" <kd.singh@enst-bretagne.fr>
To: "Kristofer Sandlund" <kristofer.sandlund@effnet.com>,
        <zhigang.c.liu@nokia.com>
Cc: <szym_paw@wp.pl>, <lars-erik.jonsson@ericsson.com>, <rohc@ietf.org>
References: <7B5AF06E216CB74DA8A5960A3181B5B815371C@ajebe001.americas.nokia.com> <406927A6.8090603@effnet.com>
Subject: Re: [rohc] Slope used to compress/decompress RTP Timestamp field
Date: Tue, 30 Mar 2004 22:25:54 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by laposte.rennes.enst-bretagne.fr id i2UKPsl08548
Content-Transfer-Encoding: quoted-printable
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi Kristofer,

I still have some problems regarding the method which you use
to compress Time Stamp (It may be because I do not know some points).

your method as I understand is as follows:
Also please read my comments (after the method) questioning its
interoperability.
And Please correct me if something is written wrong.

There seem to be 1 equation.

i) TS =3D SN * slope + offset;  (As written in your mail. And you intend =
to
use slope =3D TS_STRIDE)

COMPRESSOR SIDE:
------------------------
always TS_STRIDE =3D TS - TS_prev;

FO STATE: (choosing the smallest packet)
     1) Communicate TS_STRIDE L times if it changes and comes to a stable
          value.
     2) Communicate offset L times if it changes with respect to
          eq. i) and TS_STRIIDE in 1) above is not stable.
     3) If nothing changes then go to SO STATE:

SO STATE:
     1) If anything changes (TS_STRIDE , offset with respect to eq i),
......)
         then go to FO STATE.
      2) If nothing changes then send just SN (wlsb encoded)
          or UO_0.

DECOMPRESSOR SIDE:
---------------------------

    1) If Abs TS and TS_STRIDE are recieved then update them and
        also update offset =3D Abs TS%TS_STRIDE
    2) If no bits of TS are recieved then calculate
        TS =3D SN* TS_STRIDE + offset.


I have some problems with your method.
One is that equation i) which you use is nowhere given in the RFC
and instead , TS =3D TS_SCALED*TS_STRIDE + offset is mentioned.
I feel that RFC does not intend to use the equation i) and thus the metho=
d
will not
be interoperable.

Other is that you nowhere mention to use TS_SCALED and the equation
TS =3D TS_SCALED*TS_STRIDE + offset; in your method.
Variable TS_SCALED and this equation are the base to compress TS and are
explicitly given in RFC.
Thus, the method looks more interoperable to me.

Till now, I do not find your method interoperable.
Or please make your method a little more clear and it will be very helpfu=
l.

regards,
Kamal


----- Original Message -----
From: "Kristofer Sandlund" <kristofer.sandlund@effnet.com>
To: <zhigang.c.liu@nokia.com>
Cc: <kd.singh@enst-bretagne.fr>; <szym_paw@wp.pl>;
<lars-erik.jonsson@ericsson.com>; <rohc@ietf.org>
Sent: Tuesday, March 30, 2004 9:54 AM
Subject: Re: [rohc] Slope used to compress/decompress RTP Timestamp field


> Hi Zhigang and others!
>
> I'm not yet convinced of the slope as described here, so I'll outline w=
hy.
>
> 1) It is not well defined in the spec (at least U/O-mode).
>
> For example, the definition of the timestamp stride (section 2.0) is as
follows:
>     Timestamp stride
>
>        The timestamp stride (TS_STRIDE) is the expected increase in the
>        timestamp value between two RTP packets with consecutive sequenc=
e
>        numbers.
>
> In the two examples taken so far (one semi-static TS for video, and the
other
> "2,4,6" increase of the TS), the assumption used has been that the
TS_STRIDE is
> set to "the difference in TS between two FRAMES", and not the differenc=
e
between
> two PACKETS as defined above. According to the definition above, the
TS_STRIDE
> should be 0 in the semi-static case (see my last mail how I felt the
sloution
> can be) and "2" in the other case, and then, no slope is needed for the=
se
> specific cases.
>
> Zhigang wrote:
>  >Although the question was raised due to TS, I'd like to emphasize
>  >that the concept of slope is not only for TS. As Kamal pointed out,
>  >slope is one parameter of the function (see text below from section
3.4).
>  >
>  >   The way ROHC RTP compression operates, then, is to first establish
>  >   functions from SN to the other fields, and then reliably communica=
te
>  >   the SN.  Whenever a function from SN to another field changes, i.e=
.,
>  >   the existing function gives a result which is different from the
>  >   field in the header to be compressed, additional information is se=
nt
>  >   to update the parameters of that function.
>
> This text can as well be interpreted as if the function is simply the
> scaling/offset scheme of the TS and that the IPID offset encoding is th=
is
> function for IPID. The slope itself is not mentioned in this section, s=
o I
can't
> see this as a "proof" for slope.
>
> (see my previous mail for some more comments on why I don't think it is
defined)
>
> 2) The updating of the slope in U/O-mode is inconsistent with the
definition of
> these modes.
>
> Every time the decompressor sees a packet in U/O-modes, the context is
updated
> for all fields in the compressed packet and those inferred from them. I=
f
slope
> is to be used, suddenly we need two consecutive packets to update this
context
> value. Since this is neither clear from the spec (there is no definitio=
n
in 3095
> that says that U/O-mode should only update slope after two packets seen=
),
and
> the fact that it is different from all other updating, this is bound to
cause
> interoperability problems.
> Note: I am aware that sending "2*L" UO-1 packets can yield larger
compression
> efficiency than ("L" UO-1-ID-ext3 + "L" UO-0), but see below for other
reasons
> of why I think this tradeoff is worth it.
>
> 3) Slow convergence time
>
> a) U/O-mode
> Due to the need for sending "more than L" packets to update the context=
,
it will
> take longer time to update the context at the decompressor than it woul=
d
to
> update the TS_STRIDE (or TS_OFFSET for that matter), which means I will
have to
> send a larger number of non-SO packets. Therefore, if we see frequent
changes in
> the pattern, the scheme using slope will have a harder time to ever get=
 to
use
> UO-0 packets than a scheme without slope.
>
> b) R-mode
> Note: For R-mode, the updating of the slope is almost defined (5.5.1.2)=
,
so it
> actually makes slightly sense to have a slope in R-mode than in U/O-mod=
es
when
> reading the spec.
> In R-mode, two ACKs are required to update the slope. Considering the
sparse ACK
> mechanism, the compressor is likely to have to wait quite a long time
before he
> knows that the slope has been updated, and therefore, the new slope val=
ue
cannot
> be used very soon. Since the slope is supposed to be used in situations
where
> the TS-delta changes "frequently", it is likely that it has changed
"again"
> before the time that I have seen two ACKs. If not using slope (changing
the
> TS_STRIDE or offset) would only have required one ACK meaning a faster
> convergence time to SO.
>
> 4) Complexity
> As I have written above, the slope will have a very different updating
property
> that other fields, so it will cause quite a bit of extra complexity to
handle
> this. Since the "common case" is a more stable pattern of the timestamp
change,
> my personal opinion is that it is not worth optimizing with the slope,
since it
> can be made to work with just the stride/offset.
>
>
> I also read up in the mail archive, and the last time the slope came up=
 on
the
> list was:
>
http://www1.ietf.org/mail-archive/working-groups/rohc/current/msg01502.ht=
ml
> And then, the conclusion seems to have been that there was no slope (fo=
r
IPID at
> least) in the spec.
>
> So as a summary, I would like to see an addition to the implementer's
guide that
> says that there "is no slope" (but feel free to convince me that slope =
is
a good
> thing). At the very least, I feel quite strongly that U/O-mode should n=
ot
have
> one since there's a lack of a firm definition of it in 3095.
>
> Best regards,
>       Kristofer Sandlund, Effnet AB
>
>
> zhigang.c.liu@nokia.com wrote:
> > It's not specified in RFC 3095. So, it's an implementation choice.
> >
> > 5.3.1.1.1.  Optimistic approach, upwards transition
> >
> >    [snip]
> >
> >    The compressor normally obtains its confidence about decompressor
> >    status by sending several packets with the same information accord=
ing
> >    to the lower compression state.  If the decompressor receives any =
of
> >    these packets, it will be in sync with the compressor.  The number=
 of
> >    consecutive packets to send for confidence is not defined in this
> >    document.
> >
> > BR,
> > Zhigang
> >
> >
> >>-----Original Message-----
> >>From: ext kamal deep singh [mailto:kd.singh@enst-bretagne.fr]
> >>Sent: 27 March, 2004 09:23 AM
> >>To: Liu Zhigang.C (Nokia-NRC/Dallas); szym_paw@wp.pl
> >>Cc: kristofer.sandlund@effnet.com;
> >>lars-erik.jonsson@ericsson.com; rohc@ietf.org
> >>Subject: Re: [rohc] Slope used to compress/decompress RTP
> >>Timestamp field
> >>
> >>
> >>
> >>Hi,
> >>
> >>I have one question below.
> >>
> >>
> >>>Actually for robustness, the compressor must make sure that
> >>
> >>at least two
> >>("FO") packets with TS >field have been received by the
> >>decompressor before
> >>it can transit to SO state and send Type-0 >packets. It will
> >>ensure that the
> >>decompressor acquires both slope and offset of the function
> >>from >SN to TS.
> >>
> >>In U and O mode, how will compressor base its confidence?
> >>By sending L + 1 or 2L packets?
> >>
> >>Or should it be left as an implementation choice?
> >>
> >>
> >>regards,
> >>Kamal
> >>
> >>
> >>
> >>
> >>
> >>>4.3.1.3.  Second Order (SO) State
> >>>
> >>>   This is the state where compression is optimal.  The compressor
> >>>   enters the SO state when the header to be compressed is
> >>
> >>completely
> >>
> >>>   predictable given the SN (RTP Sequence Number) and the
> >>
> >>compressor is
> >>
> >>>   sufficiently confident that the decompressor has acquired all
> >>>   parameters of the functions from SN to other fields
> >>>
> >>>BR,
> >>>Zhigang
> >>>
> >>>
> >>>>Hi Zighang,
> >>>>
> >>>>I wonder how decompressor should behave if it receives only
> >>>>one packet with TS
> >>>>field between two packets without TS ( for example when it
> >>>>receives UO-0
> >>>>packet, next UO-1-TS and next again UO-0 packet).
> >>>>
> >>>>I can see two options:
> >>>>
> >>>>1. The decompressor uses the old slope value (e.g. the
> >>
> >>one it used to
> >>
> >>>>decompress the first UO-0 packet) to calculate timestamp for
> >>>>the second UO-0  packet. Here we assume that single TS
> >>
> >>communicates
> >>change in
> >>
> >>>>the offset.
> >>>>
> >>>>2. It calculates a new slope basing on the timestamp values
> >>>>decompressed from  the first UO-0 packet and the UO-1
> >>
> >>packet and next it
> >>uses
> >>
> >>>>the new slope to calculate the timestamp for the second
> >>
> >>UO-0 packet.
> >>
> >>>>Which of the above is correct ?
> >>>>
> >>>>Regards
> >>>>
> >>>>Pawel
> >>>>
> >>>>
> >>>>>Hi Pawel,
> >>>>>
> >>>>>Yes, your understanding is correct. It's basically the
> >>>>
> >>>>geometry: two points
> >>>>determine a line. Besides the slope, two TS values also give
> >>>>you the offset.
> >>>>
> >>>>>No, RFC 3095 does not assume floating point. All
> >>>>
> >>>>encoding/decoding operations
> >>>>are integer based.
> >>>>
> >>>>>Zhigang
> >>>>>
> >>>>>
> >>>>>>-----Original Message-----
> >>>>>>From: ext Pawel Szymanski [mailto:szym_paw@wp.pl]
> >>>>>>Sent: 26 March, 2004 02:33 AM
> >>>>>>To: Liu Zhigang.C (Nokia-NRC/Dallas)
> >>>>>>Cc: kristofer.sandlund@effnet.com; kd.singh@enst-bretagne.fr;
> >>>>>>lars-erik.jonsson@ericsson.com; rohc@ietf.org
> >>>>>>Subject: RE: [rohc] Slope used to compress/decompress RTP
> >>>>>>Timestamp field
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>Hi Zhigang,
> >>>>>>
> >>>>>>
> >>>>>>>>I base this on the following observations:
> >>>>>>>>
> >>>>>>>>* 4.5.3. Scaled RTP Timestamp encoding
> >>>>>>>>    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.
> >>>>>>>>
> >>>>>>>>If there acutally was a slope, it should have been in
> >>>>>>
> >>>>>>this formula.
> >>>>>>
> >>>>>>>This is a misunderstanding. Note that there are two
> >>>>
> >>>>*separate* steps
> >>>>
> >>>>>>>involved. The formula is for the second step: deriving TS
> >>>>>>
> >>>>>>from TS_SCALED.
> >>>>>>
> >>>>>>>The slope plays a role in the first step: "the decompressor
> >>>>>>
> >>>>>>first derives
> >>>>>>
> >>>>>>>the value of the original TS_SCALED". I thought this is
> >>>>
> >>>>clear from
> >>>>
> >>>>>>>section 4.5.3. More clarifications below.
> >>>>>>
> >>>>>>I think that the decompressor uses slope when it receives
> >>>>>>packets without TS
> >>>>>>field (for example UO-0 packets).
> >>>>>>
> >>>>>>In this case it uses the formula to calculate new scaled
> >>>>>>timestamp value:
> >>>>>>
> >>>>>>   new_scaled_timestamp =3D old_scaled_timestamp + (new_SN -
> >>>>>>old_SN)*slope
> >>>>>>
> >>>>>>Next it calculates the unscaled timestamp using the
> >>>>
> >>>>formula from 4.5.3
> >>>>
> >>>>>>When the decompressor receives a packet with TS field, it
> >>>>>>does not use slope.
> >>>>>>It decompresses the new scaled timestamp value using LSB
> >>>>>>method. Next it uses
> >>>>>>the formula from 4.5.3 to calculate the unscaled timestamp.
> >>>>>>
> >>>>>>When the decompressor receives two or more packets containing
> >>>>>>TS value in raw,
> >>>>>>it can calculate a new slope value, for example using
> >>
> >>the formula:
> >>
> >>>>>>  new_slope =3D (new_scaled_timestamp - old_scaled_timestamp) /
> >>>>>>(new_SN - old_SN)
> >>>>>>
> >>>>>>Am I correct ?
> >>>>>>
> >>>>>>An additional question is whether the slope is an integer
> >>>>>>number or could it be
> >>>>>>a floating point number ?
> >>>>>>
> >>>>>>Regards
> >>>>>>
> >>>>>>Pawel
> >>>>>>
> >>>>>>
> >>>>>>----------------------------------------------------
> >>>>>>Zobacz niezwyk=B3y koncert: "Niemena Pami=EAci Gda=F1ski Rapsod"
> >>>>>>Najwi=EAksze przeboje artysty w nowych zaskakuj=B1cych
> >>
> >>aran=BFacjach.
> >>
> >>>>>>http://klik.wp.pl/?adr=3Dhttp%3A%2F%2Fmuzyka.wp.pl%2Fimprezy.htm
> >>>>>
> >>>>>l%3Fidn%3D874&sid=3D151
> >>>>>
> >>>>>
> >>>>>
> >>>>>_______________________________________________
> >>>>>Rohc mailing list
> >>>>>Rohc@ietf.org
> >>>>>https://www1.ietf.org/mailman/listinfo/rohc
> >>>>>
> >>>>
> >>>>----------------------------------------------------
> >>>>=A3odzi=B1 po Wi=B6le - najciekawsze etiudy w Warszawie.
> >>>>http://klik.wp.pl/?adr=3Dhttp%3A%2F%2Ffilm.wp.pl%2Fp%2Fwiadomosc
> >>>
> >>>.html%3Fid%3D55832&sid=3D152
> >>>
> >>>
> >>>
> >>
> >>
>


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



From exim@www1.ietf.org  Tue Mar 30 15:54:09 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11106
	for <rohc-archive@odin.ietf.org>; Tue, 30 Mar 2004 15:54:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8QEv-0007MN-Ti
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 15:53:42 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2UKrfYN028291
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 15:53:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8QEv-0007ME-Ik
	for rohc-web-archive@optimus.ietf.org; Tue, 30 Mar 2004 15:53:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11092
	for <rohc-web-archive@ietf.org>; Tue, 30 Mar 2004 15:53:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8QEu-0005cH-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 15:53:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8QDy-0005ZV-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 15:52:43 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8QDI-0005WW-00
	for rohc-web-archive@ietf.org; Tue, 30 Mar 2004 15:52:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8QDI-0007C7-Lv; Tue, 30 Mar 2004 15:52:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8QCw-0007BI-Bu
	for rohc@optimus.ietf.org; Tue, 30 Mar 2004 15:51:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11049
	for <rohc@ietf.org>; Tue, 30 Mar 2004 15:51:35 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8QCu-0005W3-00
	for rohc@ietf.org; Tue, 30 Mar 2004 15:51:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8QC2-0005Tx-00
	for rohc@ietf.org; Tue, 30 Mar 2004 15:50:42 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8QB9-0005RC-00
	for rohc@ietf.org; Tue, 30 Mar 2004 15:49:47 -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 i2UKnku05632;
	Tue, 30 Mar 2004 23:49:46 +0300 (EET DST)
X-Scanned: Tue, 30 Mar 2004 23:50:47 +0300 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost)
	by esdks001.ntc.nokia.com (8.12.9/8.12.9) id i2UKolm8028583;
	Tue, 30 Mar 2004 23:50:47 +0300
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks001.ntc.nokia.com 00mm4HUL; Tue, 30 Mar 2004 23:50:46 EEST
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 i2UKmBF11538;
	Tue, 30 Mar 2004 23:48:12 +0300 (EET DST)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Tue, 30 Mar 2004 14:47:57 -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] Slope used to compress/decompress RTP Timestamp field
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Tue, 30 Mar 2004 15:47:56 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B8153727@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] Slope used to compress/decompress RTP Timestamp field
Thread-Index: AcQSdABdnLMddZlDQlSfZZwtBmeuxAEH8Cdw
To: <kristofer.sandlund@effnet.com>, <szym_paw@wp.pl>
Cc: <kd.singh@enst-bretagne.fr>, <lars-erik.jonsson@ericsson.com>,
        <rohc@ietf.org>
X-OriginalArrivalTime: 30 Mar 2004 20:47:57.0158 (UTC) FILETIME=[47F95860:01C41698]
Content-Transfer-Encoding: quoted-printable
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi,

As I replied earlier, Kamal's understanding is correct. Now that I=20
have time looking at the following interpretation, it is=20
- unfortunately - even beyond "over interpreting" (quote from=20
Lars-Erik). It is incorrect.

Please see detailed comments below.

BR,
Zhigang

[Kristofer wrote:]

> Let's say that the unscaled TS in the video example will be=20
> 30 and the starting value 10, then we'd have this:
>=20
> 10, 10, 10, 10, 40, 40, 40, 40, 40, 40, 40, 70, 100, 130
>=20
> As you observe, the "video slope will be 0 most of the time".=20
> This is the observation that your compressor also should make, and=20
> therefore use a TS_STRIDE of 0.

I'm really confused. How come TS_STRIDE is same as slope? What
do you mean by a scaling by a factor of 0? This is certainly not
what RFC 3095 says.

> What we can do when the TS changes from 10 to 40 is that we=20
> can interpret this as a change of TS_OFFSET instead of saying
> that TS_STRIDE (or slope) changes.

Again, TS_STRIDE !=3D slope.

> So we keep the TS_STRIDE as 0, but change TS_OFFSET from 10=20
> to 40, which we do by sending some UOR-2-ext3 with an unscaled
> timestamp according to the optimistic approach, and then move=20
> back to sending UO-0 packets.=20

How could this be possible? As specified in RFC 3095, TS_OFFSET=20
calculated locally as TS modulo TS_STRIDE. Don't you have problem
of division by zero?

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



From exim@www1.ietf.org  Tue Mar 30 17:35:08 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18440
	for <rohc-archive@odin.ietf.org>; Tue, 30 Mar 2004 17:35:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rjj-0006Zv-6j
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:44 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2GBi0wJ022434
	for rohc-archive@odin.ietf.org; Tue, 16 Mar 2004 06:44:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3CzH-0005pl-Ir
	for rohc-web-archive@optimus.ietf.org; Tue, 16 Mar 2004 06:43:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25375
	for <rohc-web-archive@ietf.org>; Tue, 16 Mar 2004 06:43:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3CzD-0001ea-00
	for rohc-web-archive@ietf.org; Tue, 16 Mar 2004 06:43:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3CyF-0001Ve-00
	for rohc-web-archive@ietf.org; Tue, 16 Mar 2004 06:42:56 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3CxQ-0001Ou-00
	for rohc-web-archive@ietf.org; Tue, 16 Mar 2004 06:42:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3CxT-0005IU-8b; Tue, 16 Mar 2004 06:42:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3Cx1-0005DX-4v
	for rohc@optimus.ietf.org; Tue, 16 Mar 2004 06:41:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25189
	for <rohc@ietf.org>; Tue, 16 Mar 2004 06:41:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3Cwx-0001Ke-00
	for rohc@ietf.org; Tue, 16 Mar 2004 06:41:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3Cw1-0001B4-00
	for rohc@ietf.org; Tue, 16 Mar 2004 06:40:38 -0500
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3Cuw-0000xl-00
	for rohc@ietf.org; Tue, 16 Mar 2004 06:39:30 -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 i2GBdQAh008324
	for <rohc@ietf.org>; Tue, 16 Mar 2004 12:39:26 +0100
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 16 Mar 2004 12:39:25 +0100
Received: from ericsson.com (research-1fd0e1.ki.sw.ericsson.se [147.214.34.102]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id G4AZXVH2; Tue, 16 Mar 2004 12:40:56 +0100
Message-ID: <4056E6A6.3070705@ericsson.com>
Date: Tue, 16 Mar 2004 12:36:06 +0100
X-Sybari-Trust: 74ad51a5 2c4885b5 ce6a043e 00000138
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: sv, en-us, en
MIME-Version: 1.0
To: kamal deep singh <kd.singh@enst-bretagne.fr>
CC: rohc@ietf.org, Jagan S <Jagan.S@lntinfotech.com>
Subject: Re: [rohc] ROHC: Header parsing
References: <OF85843B27.1BB82406-ON65256E56.001D6126@lntinfotech.com> <03ba01c40a80$62eb83b0$ee4a34c1@rennes.enstbretagne.fr>
In-Reply-To: <03ba01c40a80$62eb83b0$ee4a34c1@rennes.enstbretagne.fr>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 Mar 2004 11:39:25.0846 (UTC) FILETIME=[55852B60:01C40B4B]
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Kamal,

I think some of your checks are oversimplifying the behaviour of RTP. 
There are many users of RTP and not all are as well behaved as audio.

First, the TS behaviour you are describing is present for certain media 
types, but not all, one media type that will definitely not follow that 
usage and still be valid RTP usage is text/t140, which encodes 
transmission time for when the packet is sent. As this is normally for 
each keystroke, I can guarantee you that a valid TS_stride will be quite 
impossible to get.

Secondly, the restriction of using RTP on even ports has also been 
removed, and is now only a recommendation. The reason for removing this 
was simply to allow RTP to work across NATs.

Also the Sequence number check is not 100% as network reorder can cause 
this to jump. There are also certain users of RTP that are a bit 
misbehaving and sends RTP packets with out of order RTP sequence 
numbers. If one needs to take into consideration of misbehaving hosts is 
of course a question, however the network reorder is of course a valid 
reason for small scale jumping around of the RTP sequence number.

So in conclusion, I would only recommend that one uses static fields, 
like version number, and the over several packet compression ratio as 
better measurements.

Cheers

Magnus

kamal deep singh wrote:

> hi,
> 
> We can discuss that.
> 
> I use RTP version field and also I look at the values
> where SN field is supposed to be there. If the values are showing
> sequential
> behaviour then it should be SN and header should be RTP.
> 
> This can be extended further to check TS. If TS is showing the expected
> behaviour of
> TS = n*TS_STRIDE + TS_OFFSET (n is an integer and all others constant)
> then
> it should be TS.
> 
> Also RTP uses even UDP port numbers according to RFC.
> 
> If anybody has another better idea? please tell me.
> 
> regards,
> Kamal
> 
> ----- Original Message -----
> From: "Jagan S" <Jagan.S@lntinfotech.com>
> To: <rohc@ietf.org>
> Sent: Saturday, March 13, 2004 6:27 AM
> Subject: [rohc] ROHC: Header parsing
> 
> 
> 
>>Hi,
>>
>>3095 specifies context identification at compressor  by parsing
> 
> RTP/UDP/IP
> 
>>header fields.
>>
>>Yes. We can identify IP header by analyzing :' Version' / 'Length'
> 
> fields
> 
>>of IP header.
>>UDP header by analyzing: 'protocol type' field from IP header
>>
>>My question is about: How to identify the presence of RTP header ?
>>
>>
>>Thanks in advance
>>- Jagan
>>
> 
> ........................................................................
> ....
> ........................................................................
> ....
> .....................................................
> 
>>
>>
>>
>>_______________________________________________
>>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
> 

-- 

Magnus Westerlund

Multimedia Technologies, Ericsson Research EAB/TVA/A
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com


This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


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



From exim@www1.ietf.org  Tue Mar 30 17:40:02 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18786
	for <rohc-archive@odin.ietf.org>; Tue, 30 Mar 2004 17:40:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjG-0006Yx-6b
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:41 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2N2w8gW008297
	for rohc-archive@odin.ietf.org; Mon, 22 Mar 2004 21:58:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5c7D-00029j-Hz
	for rohc-web-archive@optimus.ietf.org; Mon, 22 Mar 2004 21:58:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13444
	for <rohc-web-archive@ietf.org>; Mon, 22 Mar 2004 21:58:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5c7A-0001f3-00
	for rohc-web-archive@ietf.org; Mon, 22 Mar 2004 21:58:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5c6C-0001Sl-00
	for rohc-web-archive@ietf.org; Mon, 22 Mar 2004 21:57:05 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5c59-0001HI-00
	for rohc-web-archive@ietf.org; Mon, 22 Mar 2004 21:55:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5c5A-0001kV-U9; Mon, 22 Mar 2004 21:56:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5c4D-0001Y5-NI
	for rohc@optimus.ietf.org; Mon, 22 Mar 2004 21:55:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13055
	for <rohc@ietf.org>; Mon, 22 Mar 2004 21:54:58 -0500 (EST)
From: Zongming.Zhou@commit.cn
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5c4A-00014J-00
	for rohc@ietf.org; Mon, 22 Mar 2004 21:54:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5c32-0000pp-00
	for rohc@ietf.org; Mon, 22 Mar 2004 21:53:48 -0500
Received: from [211.152.58.77] (helo=DIOSCURI.COMMIT)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5c1u-0000Ox-00
	for rohc@ietf.org; Mon, 22 Mar 2004 21:52:39 -0500
To: rohc@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.11   July 24, 2002
Message-ID: <OFBB72CE18.8E4E98B5-ON48256E60.000F09B3-48256E60.000FD09A@COMMIT>
Date: Tue, 23 Mar 2004 10:52:18 +0800
X-MIMETrack: Serialize by Router on penelope/commit(Release 5.0.11  |July 24, 2002) at
 2004/03/23 10:52:57 AM,
	Serialize complete at 2004/03/23 10:52:57 AM
Content-Type: multipart/alternative; boundary="=_alternative 000FD09348256E60_="
Subject: [rohc] about CSRC List with CC=0
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.6 required=5.0 tests=AWL,EXCUSE_16,MIME_BASE64_TEXT,
	NO_REAL_NAME autolearn=no version=2.60

This is a multipart message in MIME format.
--=_alternative 000FD09348256E60_=
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

SWYgQ0M9MCwgdGhlIGxlbmd0aCBvZiBDU1JDIEdlbmVyaWMgQ1NSQyBsaXN0PyBPbmUgT2N0ZXQ/
IHR3byBPY3RldCBvciBOb25lIGF0IGFsbD8NCk9uZSBvY3RldA0KICAgICAwICAgMSAgIDIgICAz
ICAgNCAgIDUgICA2ICAgNw0KICAgKy0tLSstLS0rLS0tLSstLS0rLS0tKy0tLSstLS0rLS0tKw0K
ICAgfCBFVD0wICB8R1A9MHxQUyB8ICAgIENDID0gMCAgICAgfA0KICAgKy0tLSstLS0rLS0tLSst
LS0rLS0tKy0tLSstLS0rLS0tKw0KDQp0d28gb2N0ZXQNCiAgICAgMCAgIDEgICAyICAgMyAgIDQg
ICA1ICAgNiAgIDcNCiAgICstLS0rLS0tKy0tLS0rLS0tKy0tLSstLS0rLS0tKy0tLSsNCiAgIHwg
RVQ9MCAgfEdQPTF8UFMgfCAgICBDQyA9IDAgICAgIHwNCiAgICstLS0rLS0tKy0tLS0rLS0tKy0t
LSstLS0rLS0tKy0tLSsNCiAgIDogICAgICAgICAgICBnZW5faWQgICAgICAgICAgICAgOiAgMSBv
Y3RldCwgaWYgR1AgPSAxDQogICArLS0tKy0tLSstLS09Ky0tLSstLS0rLS0tKy0tLSstLS0rDQoN
Cg0Kb3IgTm9uZSBhdCBhbGwgKGJlY2F1c2UgaW4gUlRQIGR5bm1haWMgcGFydCBDQz0wIGluZGlj
YXRlcyB0aGF0IG5vIENTUkMgDQpsaXN0KQ0KDQpCZXN0IFJlZ2FyZHMNCiANClpob3UgWm9uZ21p
bmcg1tzX2sP3DQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0NCkNPTU1JVCBJbmNvcnBvcmF0ZWQNCkFkZDog
MTggU2hlbndhbmcgUmQsIFhpbnpodWFuZyBJbmR1c3RyaWFsIERldmVsb3BtZW50IFpvbmUsIFNo
YW5naGFpIENoaW5hDQpQb3N0IENvZGU6IDIwMTEwOA0KVGVsOiArODYtMjEtNTQ0Mi00ODg1IEV4
dDozNDA1DQpGQVg6ICs4Ni0yMS01NDQyLTQ4ODYNCkVtYWlsOiB6b25nbWluZy56aG91QGNvbW1p
dC5jbg0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09DQpUaGUgaW5mb3JtYXRpb24gY29udGFpbmVkIGluIHRo
aXMgZS1tYWlsIGFuZCBhbnkgYXR0YWNobWVudHMgdGhlcmV0byBmcm9tIA0KQ09NTUlUIEluY29y
cG9yYXRlZCBpcyBpbnRlbmRlZCB0byBiZSBmb3IgdGhlIHVzZSBvZiB0aGUgcGVyc29uIG5hbWVk
IA0KYWJvdmUgYW5kIG1heSBiZSBwcml2YXRlLCBjb25maWRlbnRpYWwgYW5kIHByaXZpbGVnZWQu
IElmIHlvdSBhcmUgbm90IHRoZSANCmludGVuZGVkIHJlY2lwaWVudCBvZiB0aGlzIHRyYW5zbWlz
c2lvbiwgeW91IGFyZSBoZXJlYnkgbm90aWZpZWQgdGhhdCBhbnkgDQpkaXNjbG9zdXJlLCBjb3B5
aW5nLCBkaXN0cmlidXRpb24sIHByaW50aW5nIG9yIHVzZSBvZiB0aGUgY29udGVudHMgb2YgdGhp
cyANCmNvbW11bmljYXRpb24gaXMgc3RyaWN0bHkgcHJvaGliaXRlZC4gSWYgeW91IGhhdmUgcmVj
ZWl2ZWQgdGhpcyBlLW1haWwgaW4gDQplcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGlt
bWVkaWF0ZWx5IGFuZCBwZXJtYW5lbnRseSBkZWxldGUgdGhlIA0Kb3JpZ2luYWwgYW5kIGFueSBj
b3BpZXMgb2YgdGhpcyBlbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIHRoZXJldG8uDQo=
--=_alternative 000FD09348256E60_=
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+SWYgQ0M9MCwgdGhlIGxl
bmd0aCBvZiBDU1JDIDwvZm9udD48Zm9udCBzaXplPTIgY29sb3I9cmVkIGZhY2U9IlRpbWVzIE5l
dyBSb21hbiI+R2VuZXJpYyBDU1JDIGxpc3Q8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9IlRpbWVz
IE5ldyBSb21hbiI+PyBPbmUgT2N0ZXQ/IHR3byBPY3RldCBvciBOb25lIGF0IGFsbD88L2ZvbnQ+
DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+T25lIG9jdGV0PC9mb250
Pg0KPGJyPjxmb250IHNpemU9Mz48dHQ+Jm5ic3A7ICZuYnNwOyAmbmJzcDswICZuYnNwOyAxICZu
YnNwOyAyICZuYnNwOyAzICZuYnNwOyA0ICZuYnNwOyA1ICZuYnNwOyA2ICZuYnNwOyA3PGJyPg0K
ICZuYnNwOyArLS0tKy0tLSstLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rPGJyPg0KICZuYnNwOyB8
IEVUPTAgJm5ic3A7fEdQPTB8UFMgfCAmbmJzcDsgJm5ic3A7Q0MgPSAwICZuYnNwOyAmbmJzcDsg
fDxicj4NCiAmbmJzcDsgKy0tLSstLS0rLS0tLSstLS0rLS0tKy0tLSstLS0rLS0tKzwvdHQ+PC9m
b250Pjxmb250IHNpemU9MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjxicj4NCjwvZm9udD4NCjxi
cj48Zm9udCBzaXplPTIgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj50d28gb2N0ZXQ8L2ZvbnQ+DQo8
YnI+PGZvbnQgc2l6ZT0zPjx0dD4mbmJzcDsgJm5ic3A7ICZuYnNwOzAgJm5ic3A7IDEgJm5ic3A7
IDIgJm5ic3A7IDMgJm5ic3A7IDQgJm5ic3A7IDUgJm5ic3A7IDYgJm5ic3A7IDc8YnI+DQogJm5i
c3A7ICstLS0rLS0tKy0tLS0rLS0tKy0tLSstLS0rLS0tKy0tLSs8YnI+DQogJm5ic3A7IHwgRVQ9
MCAmbmJzcDt8R1A9MXxQUyB8ICZuYnNwOyAmbmJzcDtDQyA9IDAgJm5ic3A7ICZuYnNwOyB8PGJy
Pg0KICZuYnNwOyArLS0tKy0tLSstLS0tKy0tLSstLS0rLS0tKy0tLSstLS0rPGJyPg0KICZuYnNw
OyA6ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7Z2VuX2lkICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IDogJm5ic3A7MSBvY3RldCwgaWYg
R1AgPSAxPGJyPg0KICZuYnNwOyArLS0tKy0tLSstLS09Ky0tLSstLS0rLS0tKy0tLSstLS0rPGJy
Pg0KPC90dD48L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9IlRpbWVzIE5ldyBS
b21hbiI+b3IgTm9uZSBhdCBhbGwgKGJlY2F1c2UgaW4gUlRQIGR5bm1haWMgcGFydCBDQz0wIGlu
ZGljYXRlcyB0aGF0IG5vIENTUkMgbGlzdCk8L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0y
IGZhY2U9InNhbnMtc2VyaWYiPkJlc3QgUmVnYXJkczxicj4NCiA8YnI+DQpaaG91IFpvbmdtaW5n
INbc19rD9zxicj4NCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PTxicj4NCkNPTU1JVCBJbmNvcnBvcmF0ZWQ8
YnI+DQpBZGQ6IDE4IFNoZW53YW5nIFJkLCBYaW56aHVhbmcgSW5kdXN0cmlhbCBEZXZlbG9wbWVu
dCBab25lLCBTaGFuZ2hhaSBDaGluYTxicj4NClBvc3QgQ29kZTogMjAxMTA4PGJyPg0KVGVsOiAr
ODYtMjEtNTQ0Mi00ODg1IEV4dDozNDA1PGJyPg0KRkFYOiArODYtMjEtNTQ0Mi00ODg2PGJyPg0K
RW1haWw6IHpvbmdtaW5nLnpob3VAY29tbWl0LmNuPGJyPg0KPT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PGJy
Pg0KVGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBpbiB0aGlzIGUtbWFpbCBhbmQgYW55IGF0dGFj
aG1lbnRzIHRoZXJldG8gZnJvbSBDT01NSVQgSW5jb3Jwb3JhdGVkIGlzIGludGVuZGVkIHRvIGJl
IGZvciB0aGUgdXNlIG9mIHRoZSBwZXJzb24gbmFtZWQgYWJvdmUgYW5kIG1heSBiZSBwcml2YXRl
LCBjb25maWRlbnRpYWwgYW5kIHByaXZpbGVnZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRl
ZCByZWNpcGllbnQgb2YgdGhpcyB0cmFuc21pc3Npb24sIHlvdSBhcmUgaGVyZWJ5IG5vdGlmaWVk
IHRoYXQgYW55IGRpc2Nsb3N1cmUsIGNvcHlpbmcsIGRpc3RyaWJ1dGlvbiwgcHJpbnRpbmcgb3Ig
dXNlIG9mIHRoZSBjb250ZW50cyBvZiB0aGlzIGNvbW11bmljYXRpb24gaXMgc3RyaWN0bHkgcHJv
aGliaXRlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlLW1haWwgaW4gZXJyb3IsIHBsZWFz
ZSBub3RpZnkgdGhlIHNlbmRlciBpbW1lZGlhdGVseSBhbmQgcGVybWFuZW50bHkgZGVsZXRlIHRo
ZSBvcmlnaW5hbCBhbmQgYW55IGNvcGllcyBvZiB0aGlzIGVtYWlsIGFuZCBhbnkgYXR0YWNobWVu
dHMgdGhlcmV0by48L2ZvbnQ+DQo=
--=_alternative 000FD09348256E60_=--

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



From exim@www1.ietf.org  Tue Mar 30 17:58:03 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22309
	for <rohc-archive@odin.ietf.org>; Tue, 30 Mar 2004 17:58:03 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rjb-0006WI-Ts
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:27 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1T5hs43025353
	for rohc-archive@odin.ietf.org; Sun, 29 Feb 2004 00:43:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxJk2-0006aj-1i
	for rohc-web-archive@optimus.ietf.org; Sun, 29 Feb 2004 00:43:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23534
	for <rohc-web-archive@ietf.org>; Sun, 29 Feb 2004 00:43:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxJjz-00063M-00
	for rohc-web-archive@ietf.org; Sun, 29 Feb 2004 00:43:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxJiz-0005wg-00
	for rohc-web-archive@ietf.org; Sun, 29 Feb 2004 00:42:50 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxJiB-0005qO-00
	for rohc-web-archive@ietf.org; Sun, 29 Feb 2004 00:41:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxJiC-0006Cr-B6; Sun, 29 Feb 2004 00:42:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Awmok-0003Fg-C9
	for rohc@optimus.ietf.org; Fri, 27 Feb 2004 13:34:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17376
	for <rohc@ietf.org>; Fri, 27 Feb 2004 13:34:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awmoi-0003Lc-00
	for rohc@ietf.org; Fri, 27 Feb 2004 13:34:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Awmnn-0003G8-00
	for rohc@ietf.org; Fri, 27 Feb 2004 13:33:36 -0500
Received: from [216.90.186.146] (helo=mail.ipnetfusion.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awmn0-0003AJ-00
	for rohc@ietf.org; Fri, 27 Feb 2004 13:32:48 -0500
Received: from ipnetfusion.com (proxy.ipnetfusion.com [216.90.186.147])
	(authenticated)
	by mail.ipnetfusion.com (8.11.6/8.11.6) with ESMTP id i1RIUXG25235;
	Fri, 27 Feb 2004 12:30:33 -0600
Message-ID: <403F8D04.9090103@ipnetfusion.com>
Date: Fri, 27 Feb 2004 12:31:32 -0600
From: Simran Suri <ssuri@ipnetfusion.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
CC: "Price, Richard" <richard.price@roke.co.uk>, Robert.Sugar@nokia.com,
        lars-erik.jonsson@ericsson.com,
        "'zhigang.c.liu@nokia.com'" <zhigang.c.liu@nokia.com>,
        Pekka.Pessi@nokia.com, "West, Mark" <mark.a.west@roke.co.uk>,
        jan.christoffersson@ericsson.com, rohc@ietf.org,
        "Surtees, Abigail" <abigail.surtees@roke.co.uk>
Subject: Re: [rohc] SigComp assembler and interpreter ?
References: <EA943CD30BCB104E9D38F5B5DC2D9A7014615A@rsys004a.roke.co.uk> <403C0F9B.6000109@ipnetfusion.com> <2C5B6BE7-677A-11D8-B322-000A95DC4DB6@tzi.org>
In-Reply-To: <2C5B6BE7-677A-11D8-B322-000A95DC4DB6@tzi.org>
Content-Type: multipart/alternative;
 boundary="------------020008080906060000090900"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=HTML_MESSAGE,HTML_TITLE_EMPTY 
	autolearn=no version=2.60

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

Hi Carsten,
Thank you for your reply.

I understand the UDVM implementation is not the complete SigComp 
implementation, but as per my understanding it is the most significant 
part. The other components- compressors, state manager and the 
dispatchers (compression and decompression) can be built around the UDVM 
using open source components (e.g DEFLATE compression libraries etc.) 
Also, of these only the dispatchers would be higher layer/ application 
specific and thus may have IPR issues. Please correct me if I'm wrong.

So, I still have the following questions:
a) Has anyone provided a complete UDVM implementation that can be used 
in a SigComp module?
b) In your original implementation (of the -05 draft), how was the 
compressed message for "This is a test message.  What is the answer to 
life, the universe and everything ?" generated? Although the 
documentation says DEFLATE, I did not get the same result using the zlib 
DELFATE implementation. Did I miss something?
c) Is the decompression code for DEFLATE algorithm available in the UDVM 
instruction set or in bytecode?

Thanks once again.

Regards,
Simran



Carsten Bormann wrote:

> Hi Simran,
>
>> 2. Has there been any addition to the UDVM assembler/interpreter 
>> since March 2002? Specifically, has the implementation expanded to 
>> work with all the instructions in the UDVM instruction set? Also does 
>> anyone have any programming experience with the UDVM instruction set 
>> that can be shared?
>
>
> Does "the UDVM assembler/interpreter" refer to my half-baked 
> implementation of the -05 draft?
> I haven't got around to work on this implementation to upgrade it with 
> respect to the changes we made on the way to RFC3320 and the revised 
> assembler syntax we agreed on for the implementers guide.
>
>>  3. I tried out the examples posted by Carsten and these worked 
>> perfectly. However, can anyone tell me how we got the compressed 
>> message in the first place?
>
>
> A UDVM implementation is not a complete SigComp implementation.  In 
> addition you need:
> -- an interface to the higher layer protocol (e.g., SIP)
> -- a state manager
> -- a portfolio (>= 1) of compression algorithm implementations, and
> -- UDVM code to send to the decompressor for each of these.
>
> Clearly, these are significant pieces of work, some of which also have 
> interesting IPR complications.
>
> Gruesse, Carsten
>

--------------020008080906060000090900
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000099">
<font size="-1"><font face="Verdana">Hi Carsten,<br>
Thank you for your reply. <br>
<br>
I understand the UDVM implementation is not the complete SigComp
implementation, but as per my understanding it is the most significant
part. The other components- compressors, state manager and the
dispatchers (compression and decompression) can be built around the
UDVM using open source components (e.g DEFLATE compression libraries
etc.) Also, of these only the dispatchers would be higher layer/
application specific and thus may have IPR issues. Please correct me if
I'm wrong. <br>
<br>
So, I still have the following questions:<br>
a) Has anyone provided a complete UDVM implementation that can be used
in a SigComp module? <br>
b) In your original implementation (of the -05 draft), how was the
compressed message for "This is a test message.&nbsp; What is the answer to
life, the universe and everything ?" generated? Although the
documentation says DEFLATE, I did not get the same result using the
zlib DELFATE implementation. Did I miss something?<br>
c) Is the decompression code for DEFLATE algorithm available in the
UDVM instruction set or in bytecode?<br>
<br>
Thanks once again.<br>
<br>
Regards,<br>
Simran<br>
<br>
<br>
</font></font><br>
Carsten Bormann wrote:<br>
<blockquote cite="mid2C5B6BE7-677A-11D8-B322-000A95DC4DB6@tzi.org"
 type="cite">Hi Simran,
  <br>
  <br>
  <blockquote type="cite">2. Has there been any addition to the UDVM
assembler/interpreter since March 2002? Specifically, has the
implementation expanded to work with all the instructions in the UDVM
instruction set? Also does anyone have any programming experience with
the UDVM instruction set that can be shared?
    <br>
  </blockquote>
  <br>
Does "the UDVM assembler/interpreter" refer to my half-baked
implementation of the -05 draft?
  <br>
I haven't got around to work on this implementation to upgrade it with
respect to the changes we made on the way to RFC3320 and the revised
assembler syntax we agreed on for the implementers guide.
  <br>
  <br>
  <blockquote type="cite">&nbsp;3. I tried out the examples posted by
Carsten and these worked perfectly. However, can anyone tell me how we
got the compressed message in the first place?
    <br>
  </blockquote>
  <br>
A UDVM implementation is not a complete SigComp implementation.&nbsp; In
addition you need:
  <br>
-- an interface to the higher layer protocol (e.g., SIP)
  <br>
-- a state manager
  <br>
-- a portfolio (&gt;= 1) of compression algorithm implementations, and
  <br>
-- UDVM code to send to the decompressor for each of these.
  <br>
  <br>
Clearly, these are significant pieces of work, some of which also have
interesting IPR complications.
  <br>
  <br>
Gruesse, Carsten
  <br>
  <br>
</blockquote>
</body>
</html>

--------------020008080906060000090900--

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



From exim@www1.ietf.org  Tue Mar 30 18:00:21 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22900
	for <rohc-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:00:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rja-0006Xa-4r
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:27 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1T5hsQc025338
	for rohc-archive@odin.ietf.org; Sun, 29 Feb 2004 00:43:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxJk1-0006ab-TD
	for rohc-web-archive@optimus.ietf.org; Sun, 29 Feb 2004 00:43:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23531
	for <rohc-web-archive@ietf.org>; Sun, 29 Feb 2004 00:43:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxJjy-00063H-00
	for rohc-web-archive@ietf.org; Sun, 29 Feb 2004 00:43:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxJiz-0005wY-00
	for rohc-web-archive@ietf.org; Sun, 29 Feb 2004 00:42:49 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxJiB-0005qN-00
	for rohc-web-archive@ietf.org; Sun, 29 Feb 2004 00:41:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxJiC-0006Cg-0C; Sun, 29 Feb 2004 00:42:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AwWDP-0001Ps-Bt
	for rohc@optimus.ietf.org; Thu, 26 Feb 2004 19:50:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19353
	for <rohc@ietf.org>; Thu, 26 Feb 2004 19:50:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwWDN-0004aw-00
	for rohc@ietf.org; Thu, 26 Feb 2004 19:50:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwWCP-0004V8-00
	for rohc@ietf.org; Thu, 26 Feb 2004 19:49:54 -0500
Received: from hydra.mt.net.mk ([195.26.152.185] helo=penicilin1.mt.net.mk)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwWBb-0004Op-00
	for rohc@ietf.org; Thu, 26 Feb 2004 19:49:03 -0500
Received: from hydra.mt.net.mk(195.26.152.185) by penicilin1.mt.net.mk via csmap 
	 id 8ec9a13c_68be_11d8_9d8e_00304811b8b1_11284;
	Fri, 27 Feb 2004 01:47:46 +0100 (CET)
Received: from penicilin1.mt.net.mk (62.162.14.81) by mail.mt.net.mk (7.1.005)
        id 401A6F9C000AAFC1; Fri, 27 Feb 2004 01:48:54 +0100
Received: from nodnsquery(62.162.14.81) by penicilin1.mt.net.mk via csmap 
	 id 89724752_68be_11d8_93f8_00304811b8b1_11261;
	Fri, 27 Feb 2004 01:47:38 +0100 (CET)
Message-ID: <003601c3fccb$7a9a7790$510ea23e@LiljanaHpLaptop>
From: "Vladimir Atanasovski" <vlatko@mt.net.mk>
To: <rohc@ietf.org>, <richard.price@roke.co.uk>,
        <Ghyslain.Pelletier@epl.ericsson.se>, <rohc@cdt.luth.se>,
        <lars-erik.johnsson@ericsson.com>, <peter.kremer@ericsson.com>
Date: Fri, 27 Feb 2004 01:37:36 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001F_01C3FCD2.473A4A40"
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
Subject: [rohc] ROHC code
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=HTML_20_30,HTML_MESSAGE 
	autolearn=no version=2.60

This is a multi-part message in MIME format.

------=_NextPart_000_001F_01C3FCD2.473A4A40
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: quoted-printable

Dear,

I am a student at the Faculty of Electrical Engineering in Skopje, =
Macedonia. I work on my final thesis now which is about comparing =
different header compression techniques for wireless links. I ran a lot =
of simulations in ns-2 about TCP throughput without header compression =
and now I need to compare the results with a certain header compression =
scheme. From what I can find on the Internet, I see ROHC as a very =
attractive scheme. I was wondering if anyone of you can provide me with =
some information about how to validate the benefits of using ROHC in =
wireless links. Is the ROHC code available for research and academic =
purposes, is there an implementation of ROHC in ns-2 or is there some =
other tool I can use for this purpose?

Thankful in advance,
Vladimir M. Atanasovski
------=_NextPart_000_001F_01C3FCD2.473A4A40
Content-Type: text/html;
	charset="koi8-r"
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=3Dkoi8-r">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Dear,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I am a student at the Faculty of =
Electrical=20
Engineering in Skopje, Macedonia. I work on my final thesis now which is =
about=20
comparing different header compression techniques for wireless links. I =
ran a=20
lot of simulations in ns-2 about TCP throughput without header =
compression and=20
now I need to compare the results with a certain header compression =
scheme. From=20
what I can find on the Internet, I see ROHC as a very attractive scheme. =
I was=20
wondering if anyone of you can provide me with some information about =
how to=20
validate the benefits of using ROHC in wireless links. Is the ROHC code=20
available for research and academic purposes, is there an implementation =
of ROHC=20
in ns-2 or is there some other tool I can use for this =
purpose?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thankful in advance,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Vladimir M. =
Atanasovski</FONT></DIV></BODY></HTML>

------=_NextPart_000_001F_01C3FCD2.473A4A40--


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



From exim@www1.ietf.org  Tue Mar 30 18:10:26 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25703
	for <rohc-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:10:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjV-0006Xa-WB
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:22 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1C9168s012568
	for rohc-archive@odin.ietf.org; Thu, 12 Feb 2004 04:01:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArCiW-0003Gb-IQ
	for rohc-web-archive@optimus.ietf.org; Thu, 12 Feb 2004 04:01:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15146
	for <rohc-web-archive@ietf.org>; Thu, 12 Feb 2004 04:01:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArCiT-0001md-00
	for rohc-web-archive@ietf.org; Thu, 12 Feb 2004 04:01:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArChX-0001gI-00
	for rohc-web-archive@ietf.org; Thu, 12 Feb 2004 04:00:04 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArCgW-0001ZD-00
	for rohc-web-archive@ietf.org; Thu, 12 Feb 2004 03:59:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArCgX-0002za-Ml; Thu, 12 Feb 2004 03:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArCfa-0002y4-W9
	for rohc@optimus.ietf.org; Thu, 12 Feb 2004 03:58:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15053
	for <rohc@ietf.org>; Thu, 12 Feb 2004 03:58:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArCfY-0001Rt-00
	for rohc@ietf.org; Thu, 12 Feb 2004 03:58:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArCel-0001MQ-00
	for rohc@ietf.org; Thu, 12 Feb 2004 03:57:11 -0500
Received: from imh.informatik.uni-bremen.de ([134.102.224.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArCdu-0001GT-00
	for rohc@ietf.org; Thu, 12 Feb 2004 03:56:18 -0500
Received: from [IPv6:::1] (imh.informatik.uni-bremen.de [134.102.224.4])
	by imh.informatik.uni-bremen.de (8.12.10/8.12.9) with ESMTP id i1C8u8l2012510;
	Thu, 12 Feb 2004 09:56:08 +0100 (MET)
In-Reply-To: <4029DB46.4050603@effnet.com>
References: <A943FD84BD9ED41193460008C7918050072E943D@ESEALNT419.al.sw.ericsson.se> <D3D7143E-5C05-11D8-9C0E-000A95DC4DB6@tzi.org> <4029DB46.4050603@effnet.com>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <4B1C1EB8-5D39-11D8-9B78-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>,
        "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>,
        rohc@ietf.org
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] ROHC context reuse & mode
Date: Thu, 12 Feb 2004 09:56:06 +0100
To: Kristofer Sandlund <kristofer.sandlund@effnet.com>
X-Mailer: Apple Mail (2.612)
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Feb 11 2004, at 08:35 Uhr, Kristofer Sandlund wrote:

> Hi Carsten,
>
> Are you saying that every IR packet (regardless of it being for a new 
> flow or not) should flush the ENTIRE decompressor context?

Not quite (but see below).
What I was trying to say is that a compressor must be prepared to deal 
with a decompressor that does exactly this.

> One case where some state probably should be kept is for the list 
> compression. Just because an extension header (or CSRC identifier) is 
> not present in the current IR packet does not mean that it's not 
> present in the context and could reappear in a later packet. If I 
> flush the list compression tables every time I get an IR packet, I 
> will have to re-establish every item once again. This does not seem to 
> be very efficient, especially in U-mode where I should periodically 
> refresh the context with IRs.

Well, U-mode is the simple example: We are sending IR-packets because 
we don't know whether the decompressor got enough of the previous 
packets to have set up state yet.  So the compressor must be prepared 
to deal with a decompressor that has a clean slate immediately after 
the IR.

> Also, if every IR would mean the same as establishing a new context, 
> wouldn't that mean that all IR:s would need to carry U-mode? (since 
> all compression should start in U-mode). Why then a mode parameter in 
> the profile 1 IR packet?

That is the interesting part.  Given that the compressor knows (R-mode) 
or is likely to be correct (O-mode) about the state at the 
decompressor, the U-mode argument above does not apply.  But then, we 
are sending an IR packet because something isn't right, so the 
assumptions that can be made about the state are probably limited.  It 
seems to me some serious analysis is required, which I can't do at the 
moment.

The questions I have in my mind:

1) Can it be dangerous for a decompressor to retain state beyond an IR?

2) Do we have an interoperability problem?
2a) Would your compressor have problems with a decompressor that starts 
with a clean slate after each IR packet?
2b) Would your decompressor have problems with a compressor that 
assumes this?  (Related to 1 above.)

Gruesse, Carsten


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



From exim@www1.ietf.org  Tue Mar 30 18:34:49 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02318
	for <rohc-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:34:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjE-0006Yx-Qq
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAUKJ3cZ019464
	for rohc-archive@odin.ietf.org; Sun, 30 Nov 2003 15:19:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQY23-00053r-O7
	for rohc-web-archive@optimus.ietf.org; Sun, 30 Nov 2003 15:19:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12461
	for <rohc-web-archive@ietf.org>; Sun, 30 Nov 2003 15:18:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQY22-0004s3-00
	for rohc-web-archive@ietf.org; Sun, 30 Nov 2003 15:19:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQY22-0004rz-00
	for rohc-web-archive@ietf.org; Sun, 30 Nov 2003 15:19:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQY21-00053X-3B; Sun, 30 Nov 2003 15:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQY1h-00052y-RY
	for rohc@optimus.ietf.org; Sun, 30 Nov 2003 15:18:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12418
	for <rohc@ietf.org>; Sun, 30 Nov 2003 15:18:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQY1g-0004rG-00
	for rohc@ietf.org; Sun, 30 Nov 2003 15:18:40 -0500
Received: from ims21.stu.nus.edu.sg ([137.132.14.228])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQY1g-0004r5-00
	for rohc@ietf.org; Sun, 30 Nov 2003 15:18:40 -0500
Received: from MBXSRV23.stu.nus.edu.sg ([137.132.14.233]) by ims21.stu.nus.edu.sg with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 1 Dec 2003 04:18:37 +0800
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="utf-8"
Content-Transfer-Encoding: base64
Date: Mon, 1 Dec 2003 04:18:36 +0800
Message-ID: <97B6AED9BBAE4845B2559DA63E6ECDC2032280A7@MBXSRV23.stu.nus.edu.sg>
Thread-Topic: [rohc] I-D ACTION:draft-ietf-rohc-context-replication-01.txt
Thread-Index: AcOe0yy3P2FulCQ5T1q/AMpmiB+BtgYqrnMT
From: "Cho Chia Yuan" <eng01098@nus.edu.sg>
To: "Ghyslain Pelletier" <Ghyslain.Pelletier@ericsson.com>, <rohc@ietf.org>
Cc: <winston@i2r.a-star.edu.sg>, <sukanta@i2r.a-star.edu.sg>
X-OriginalArrivalTime: 30 Nov 2003 20:18:37.0030 (UTC) FILETIME=[22DF6060:01C3B77F]
Content-Transfer-Encoding: base64
Subject: [rohc] Questions on Context Replication
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

SGkgR2h5c2xhaW4sDQogDQpJIGhhdmUgYSBmZXcgcXVlc3Rpb25zIHJlZ2FyZGluZyA8ZHJhZnQt
aWV0Zi1yb2hjLWNvbnRleHQtcmVwbGljYXRpb24tMDEudHh0PjoNCiANCjEpIElzIHRoZSByZXZl
cnNlIGZlZWRiYWNrIGNoYW5uZWwgYSBjb21wdWxzb3J5IHByZS1yZXF1aXNpdGUgZm9yIGNvbnRl
eHQgcmVwbGljYXRpb24gb3IgaXMgaXQgb3B0aW9uYWw/DQogDQoyKSBXaGVuIHRoZSBkZWNvbXBy
ZXNzb3IgdmFsaWRhdGlvbiBvZiB0aGUgY29udGV4dCBmb2xsb3dpbmcgZGVjb21wcmVzc2lvbiBv
ZiBhbiBJUi1DUiBwYWNrZXQgZmFpbHMsIGlzIHRoZSBTVEFUSUMtTkFDSyBzZW50IGJhY2sgdG8g
dGhlIGNvbXByZXNzb3Igb3B0aW9uYWwgb3IgY29tcHVsc29yeT8NCiANClRoZSBuYXR1cmUgb2Yg
bXkgcXVlc3Rpb25zIGFyaXNlcyBmcm9tIHRoZSBmb2xsb3dpbmc6DQooMy4zLjMuKQ0KICAgQ29u
dGV4dCByZXBsaWNhdGlvbiBpcyBkZXNpZ25lZCB0byBvcGVyYXRlIG92ZXIgbGlua3Mgd2hlcmUg
YQ0KICAgZmVlZGJhY2sgY2hhbm5lbCBpcyBhdmFpbGFibGUuIFRoaXMgaXMgbmVjZXNzYXJ5IHRv
IGVuc3VyZSB0aGF0IHRoZQ0KICAgaW5mb3JtYXRpb24gdXNlZCB0byBjcmVhdGUgYSBuZXcgY29u
dGV4dCBpcyBzeW5jaHJvbml6ZWQgYmV0d2VlbiB0aGUNCiAgIGNvbXByZXNzb3IgYW5kIHRoZSBk
ZWNvbXByZXNzb3IuIC4uLg0KIA0KLVRoZSBhYm92ZSBzdWdnZXN0cyB0aGF0IHRoZSBmZWVkYmFj
ayBjaGFubmVsIGlzIGNvbXB1bHNvcnk/DQogDQooMy40LjMuKQ0KICAgU3BlY2lmaWNhbGx5LCB3
aGVuIHRoZSBkZWNvbXByZXNzb3IgZmFpbHMgdG8gdmFsaWRhdGUgdGhlIGNvbnRleHQNCiAgIGZv
bGxvd2luZyB0aGUgZGVjb21wcmVzc2lvbiBvZiBvbmUgb3IgbW9yZSBpbml0aWFsIElSLUNSIHBh
Y2tldHMsIGl0DQogICBNVVNUIGludmFsaWRhdGUgdGhlIGNvbnRleHQgYW5kIHJlbWFpbiBpbiBp
dHMgaW5pdGlhbCBzdGF0ZS4gSW4NCiAgIGFkZGl0aW9uLCB0aGUgZGVjb21wcmVzc29yIFNIT1VM
RCBzZW5kIGEgU1RBVElDLU5BQ0suDQogDQotU2luY2UgcmV2ZXJzZSAocG9zaXRpdmUgYW5kIG5l
Z2F0aXZlKSBmZWVkYmFja3MgYXJlIGFsbCBvcHRpb25hbCwgZG9lcyBpdCBtZWFuIHRoYXQgdGhl
IGZlZWRiYWNrIGNoYW5uZWwgaXMgb3B0aW9uYWw/DQogDQoNCk15IG9waW5pb24gaXMgdGhhdCB0
aGUgcmV2ZXJzZSBmZWVkYmFjayBjaGFubmVsIG11c3QgYmUgcHJlc2VudCBmb3IgY29udGV4dCBy
ZXBsaWNhdGlvbiwgc28gdGhhdCBTVEFUSUMtTkFDS1MgYXJlIHNlbnQgYmFjayB0byB0aGUgY29t
cHJlc3NvciB3aGVuIGNvbnRleHQgdmFsaWRhdGlvbiBmYWlscyB1cG9uIGRlY29tcHJlc3Npb24g
b2YgYW4gSVItQ1IgcGFja2V0LiBJUi1DUiBjb250ZXh0IHZhbGlkYXRpb24gZmFpbHVyZXMgbXVz
dCBiZSBjb21tdW5pY2F0ZWQgYmFjayB0byB0aGUgY29tcHJlc3Nvci4gVGhpcyBpcyBiZWNhdXNl
ICd2YWxpZCcgYmFzZSBjb250ZXh0cyBhdCB0aGUgY29tcHJlc3NvciBtYXkgYmUgYWxyZWFkeSBp
bnZhbGlkYXRlZCBhdCB0aGUgZGVjb21wcmVzc29yLiANCiANClRoZSBjYXNlIGZvciB0aGlzIC0g
c3VwcG9zZSB0aGUgcmV2ZXJzZSBmZWVkYmFjayBjaGFubmVsIGlzIG5vdCBwcmVzZW50IChvciBT
VEFUSUMtTkFDS3MgYXJlIG5vdCBzZW50IGJhY2sgdXBvbiBjb250ZXh0IHZhbGlkYXRpb24gZmFp
bHVyZSBhdCB0aGUgZGVjb21wcmVzc29yKSwgYW5kIGZ1cnRoZXJtb3JlIHRoZSBkZWNvbXByZXNz
b3IgaGFzIGRpc2NhcmRlZC9vdmVyd3JpdHRlbiBhbGwgdGhlICd2YWxpZCcgYmFzZSBjb250ZXh0
cyBzdGlsbCBrZXB0IGJ5IHRoZSBjb21wcmVzc29yLiBUaGVuLCB0aGUgY29tcHJlc3NvciBoYXMg
bm8gd2F5IG9mIGtub3dpbmcgdGhlIHRydXRoLiBBZnRlciB1cHdhcmRzIHRyYW5zaXRpb24gZnJv
bSB0aGUgQ1Igc3RhdGUgaW4gb3B0aW1pc3RpYyBtb2RlLCB0aGUgY29tcHJlc3NvciBwZXJpb2Rp
Y2FsbHkgdHJhbnNpdHMgZG93bndhcmRzIHRvIElSIHN0YXRlLCBpbiB3aGljaCBpdCBmaW5kcyBz
ZWVtaW5nbHkgJ3ZhbGlkJyBiYXNlIGNvbnRleHRzLCB0cmFuc2l0cyB0byBDUiBzdGF0ZSwgYW5k
IGFmdGVyIGEgcGVyaW9kIG9mIHRpbWUgb3B0aW1pc3RpY2FsbHkgcHJvY2VlZHMgdG8gdGhlICdI
aWdoZXIgT3JkZXIgU3RhdGUnLCAuLi4gLCBhbmQgYWxsIHRoZSB0aW1lIG5vdGhpbmcgaGFzIGJl
ZW4gcmVjZWl2ZWQgc3VjY2Vzc2Z1bGx5IGF0IGFsbC4NCiANClRodXMsIEkgdGhpbmsgU1RBVElD
LU5BQ0tzIGZvciBJUi1DUiBwYWNrZXRzIHNob3VsZCBub3QgYmUgb3B0aW9uYWwsIGJlY2F1c2Ug
YW4gYXZlbnVlIGZvciBmYWxsYmFjayB0byBJUiBwYWNrZXRzLCBpbiB0aGUgZXZlbnQgb2YgZmFp
bHVyZSwgbXVzdCBiZSBwcm92aWRlZC4NCiANCkZ1cnRoZXJtb3JlLCBpZiB0aGUgcG9saWN5IGVu
Zm9yY2VkIGlzIHN1Y2ggdGhhdCB0aGUgbW9zdCByZWNlbnQgdmFsaWQgYmFzZSBjb250ZXh0IGlz
IGNob3NlbiBmb3IgcmVwbGljYXRpb24gYWx3YXlzLCB0aGVuIG1heWJlIGl0IGNhbiBiZSBhc3N1
bWVkIHRoYXQgaWYgY29udGV4dCB2YWxpZGF0aW9uIGZvciBhbiBJUi1DUiBwYWNrZXQgZmFpbHMg
YXQgdGhlIGRlY29tcHJlc3NvciwgdGhlcmUgaXMgbm8gbmVlZCBmb3IgdGhlIGNvbXByZXNzb3Ig
dG8gYXR0ZW1wdCBjb250ZXh0IHJlcGxpY2F0aW9uIGZyb20gYW5vdGhlciBiYXNlIGNvbnRleHQ/
IFRodXMsIGNhbiB0aGUgZGVjb21wcmVzc29yIHNpbXBseSBzZW5kIGJhY2sgYSBTVEFUSUMtTkFD
SyB0byBzaWduYWwgZmFsbGJhY2sgdG8gY29udmVudGlvbmFsIGNvbnRleHQgaW5pdGlhbGl6YXRp
b24/IFRoaXMgbWF5IG1lYW4gdGhhdCB0aGUgc2VuZGluZyBvZiBTVEFUSUMtTkFDSyB3b3VsZCBi
ZSBNVVNUIGluc3RlYWQgb2YgU0hPVUxEIGluIHRoZSBhYm92ZSBzZWN0aW9uLg0KIA0KQ2hpYSBZ
dWFuIENobw0KTmF0aW9uYWwgVW5pdmVyc2l0eSBvZiBTaW5nYXBvcmUNCi8gSW5zdGl0dXRlIGZv
ciBJbmZvY29tbSBSZXNlYXJjaA0K

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



From exim@www1.ietf.org  Tue Mar 30 18:51:53 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06813
	for <rohc-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:51:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rix-0006WI-L2
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:48 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8KFdm8Q003841
	for rohc-archive@odin.ietf.org; Sat, 20 Sep 2003 11:39:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0jpr-0000zs-VD
	for rohc-web-archive@optimus.ietf.org; Sat, 20 Sep 2003 11:39:47 -0400
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13662
	for <rohc-web-archive@ietf.org>; Sat, 20 Sep 2003 11:39:39 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0jpN-0000kc-7a; Sat, 20 Sep 2003 11:39:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0joF-00005I-5y
	for rohc@optimus.ietf.org; Sat, 20 Sep 2003 11:38:07 -0400
Received: from dog.topology.org (alanke.lnk.telstra.net [139.130.140.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13270
	for <rohc@ietf.org>; Sat, 20 Sep 2003 11:37:52 -0400 (EDT)
Received: by dog.topology.org (Postfix, from userid 1321)
	id AFB0D872E1; Sun, 21 Sep 2003 01:06:35 +0930 (CST)
Date: Sun, 21 Sep 2003 01:06:35 +0930
From: Alan Kennington <ak3.rohc@topology.org>
To: ROHC mailing list <rohc@ietf.org>
Subject: Re: [rohc] ROHC packet traces/CRC calculation example.
Message-ID: <20030921010635.A20665@dog.topology.org>
Reply-To: Alan Kennington <ak3.rohc@topology.org>
References: <F54085DA4E90D511B80B00B0D0D007D26BA7E4@exchsvr.octasic.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.3.12i
In-Reply-To: <F54085DA4E90D511B80B00B0D0D007D26BA7E4@exchsvr.octasic.com>; from remi.pelland@octasic.com on Fri, Sep 19, 2003 at 06:06:42PM -0400
X-PGP-Key: http://www.topology.org/ak/key_ak2.asc
X-PGP-Key-Fingerprint: 8A7B 7A8E 1C02 8298 579F 1860 7D56 121B D363 329E
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id LAA13281
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

On Fri, Sep 19, 2003 at 06:06:42PM -0400, Remi Pelland wrote:
>=20
> Does anyone know if there are any records of packet traces taken
> during the interoperability tests?  I'm mostly interrested in the CRC
> calculation of compressed header since I would like to compare my
> algorithm against something that is known to work.
>=20

R=E9mi,

I can't help directly with that question. But for the distant future, I
have a suggestion. If an RFC was defined for "ROHC over UDP" then we
could all test our implementations over the Internet.  Of course, this
would not be a 100% test of all aspects, but it would certainly test 99%
of the protocol syntax and semantics.

This could be implemented quite simply on unix systems by modifying an
ROHC/PPP implementation so that the packets are fed to a user-space
process via a character-device, and each packet could then be sent to a
remote host in a UDP packet.

Maybe then someone could make available a standard reference ROHC over
UDP implementation for everyone to test their implementations against.
This would be much less costly than interop meetings - and even us poor
people could participate.

Cheers,
Alan Kennington.

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



From exim@www1.ietf.org  Tue Mar 30 18:58:09 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08417
	for <rohc-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:58:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Riu-0006Yx-CQ
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:44 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8KFL5AY014275
	for rohc-archive@odin.ietf.org; Sat, 20 Sep 2003 11:21:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0jXl-0003hn-DE
	for rohc-web-archive@optimus.ietf.org; Sat, 20 Sep 2003 11:21:05 -0400
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10888
	for <rohc-web-archive@ietf.org>; Sat, 20 Sep 2003 11:19:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0jVn-0002x0-TW; Sat, 20 Sep 2003 11:19:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0idb-0006f7-8l
	for rohc@optimus.ietf.org; Sat, 20 Sep 2003 10:23:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23964
	for <rohc@ietf.org>; Fri, 19 Sep 2003 18:10:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A0TSU-00029V-00
	for rohc@ietf.org; Fri, 19 Sep 2003 18:10:34 -0400
Received: from exchsvr.octasic.com ([216.208.79.4])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A0TSJ-00029S-00
	for rohc@ietf.org; Fri, 19 Sep 2003 18:10:23 -0400
Received: by exchsvr.octasic.com with Internet Mail Service (5.5.2653.19)
	id <TFX4YBT8>; Fri, 19 Sep 2003 18:06:43 -0400
Message-ID: <F54085DA4E90D511B80B00B0D0D007D26BA7E4@exchsvr.octasic.com>
From: Remi Pelland <remi.pelland@octasic.com>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Fri, 19 Sep 2003 18:06:42 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [rohc] ROHC packet traces/CRC calculation example.
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>


Hi,

Does anyone know if there are any records of packet traces taken during the
interoperability tests?  I'm mostly interrested in the CRC calculation of
compressed header since I would like to compare my algorithm against
something that is known to work.

Perhaps this could be an interresting addition to the Implementer's Guide?
There could be a few IPv4 and IPv6 headers and for each of them the
associated CRC-3/CRC-7 for the case where the packet is sent compressed, and
the associated CRC-8 values for cases where the packet is sent via IR and
IR-DYN.  I know the i.g. does provide a CRC algorithm already, but examples
with actual packets would also validate the STATIC and DYNAMIC
classifications that is defined for compressed headers.  Any kind of
tangible example would be helpful I believe.

In the mean time, if you have that information available or if you have your
own traces that you're willing to share, I would greatly appreciate it.

Thanks in advance,
Remi.


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



From exim@www1.ietf.org  Tue Mar 30 19:00:11 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08935
	for <rohc-archive@odin.ietf.org>; Tue, 30 Mar 2004 19:00:11 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Ris-0006ZK-9b
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:42 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9AJeGhm022477
	for rohc-archive@odin.ietf.org; Fri, 10 Oct 2003 15:40:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A837Y-0005qD-9E
	for rohc-web-archive@optimus.ietf.org; Fri, 10 Oct 2003 15:40:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15953
	for <rohc-web-archive@ietf.org>; Fri, 10 Oct 2003 15:40:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A837V-0000YA-00
	for rohc-web-archive@ietf.org; Fri, 10 Oct 2003 15:40:13 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A837U-0000Y5-00
	for rohc-web-archive@ietf.org; Fri, 10 Oct 2003 15:40:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A837V-0005pJ-I4; Fri, 10 Oct 2003 15:40:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A837C-0005gI-MT
	for rohc@optimus.ietf.org; Fri, 10 Oct 2003 15:39:54 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15923;
	Fri, 10 Oct 2003 15:39:46 -0400 (EDT)
Message-Id: <200310101939.PAA15923@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rohc@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 10 Oct 2003 15:39:45 -0400
Subject: [rohc] I-D ACTION:draft-ietf-rohc-udp-lite-01.txt
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Robust Header Compression Working Group of the IETF.

	Title		: RObust Header Compression (ROHC):Profiles for UDP-Lite
	Author(s)	: G. Pelletier
	Filename	: draft-ietf-rohc-udp-lite-01.txt
	Pages		: 18
	Date		: 2003-10-10
	
This document defines ROHC (Robust Header Compression) profiles for
compression of RTP/UDP-Lite/IP packets (Real-Time Transport Protocol,
User Datagram Protocol Lite, Internet Protocol) and UDP-Lite/IP.
These profiles are defined based on their differences with the
profiles specified in [RFC-3095] for UDP [RFC-768].
Although both transport protocols are very similar, ROHC profiles
must be defined separately for robust compression of UDP-Lite headers
because it does not share protocol identifier with UDP. Also, the
UDP-Lite Checksum Coverage field does not share the semantics of the
corresponding UDP Length field and as a consequence cannot always be
inferred anymore.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rohc-udp-lite-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-rohc-udp-lite-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rohc-udp-lite-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-10-10143426.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rohc-udp-lite-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rohc-udp-lite-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-10-10143426.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Tue Mar 30 19:00:26 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08983
	for <rohc-archive@odin.ietf.org>; Tue, 30 Mar 2004 19:00:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Ris-0006a4-8l
	for rohc-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:42 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9AJeG99022463
	for rohc-archive@odin.ietf.org; Fri, 10 Oct 2003 15:40:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A837Y-0005qC-8F
	for rohc-web-archive@optimus.ietf.org; Fri, 10 Oct 2003 15:40:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15952
	for <rohc-web-archive@ietf.org>; Fri, 10 Oct 2003 15:40:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A837V-0000Y7-00
	for rohc-web-archive@ietf.org; Fri, 10 Oct 2003 15:40:13 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A837U-0000Y3-00
	for rohc-web-archive@ietf.org; Fri, 10 Oct 2003 15:40:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A837V-0005oz-0e; Fri, 10 Oct 2003 15:40:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A8377-0005g9-1z
	for rohc@optimus.ietf.org; Fri, 10 Oct 2003 15:39:49 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15894;
	Fri, 10 Oct 2003 15:39:40 -0400 (EDT)
Message-Id: <200310101939.PAA15894@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rohc@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 10 Oct 2003 15:39:40 -0400
Subject: [rohc] I-D ACTION:draft-ietf-rohc-ip-only-05.txt
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Robust Header Compression Working Group of the IETF.

	Title		: RObust Header Compression (ROHC): A Compression 
			  Profile for IP
	Author(s)	: L. Jonsson, G. Pelletier
	Filename	: draft-ietf-rohc-ip-only-05.txt
	Pages		: 15
	Date		: 2003-10-10
	
The original RObust Header Compression (ROHC) RFC, RFC 3095, defines
a framework for header compression, along with compression protocols
(profiles) for IP/UDP/RTP, IP/ESP, IP/UDP, and also a profile for
uncompressed packet streams. However, no profile was defined for
compression of IP only, which has been identified as a missing piece
in RFC 3095. This document defines a ROHC compression profile for IP,
similar to the IP/UDP profile defined by RFC 3095, but simplified to
exclude UDP, and enhanced to compress IP header chains of arbitrary
length.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rohc-ip-only-05.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-rohc-ip-only-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rohc-ip-only-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-10-10143408.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rohc-ip-only-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rohc-ip-only-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-10-10143408.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Wed Mar 31 01:24:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02146
	for <rohc-archive@odin.ietf.org>; Wed, 31 Mar 2004 01:24:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Z8q-0007Sb-Bc
	for rohc-archive@odin.ietf.org; Wed, 31 Mar 2004 01:24:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2V6O0nA028673
	for rohc-archive@odin.ietf.org; Wed, 31 Mar 2004 01:24:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Z8q-0007SM-4p
	for rohc-web-archive@optimus.ietf.org; Wed, 31 Mar 2004 01:24:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02135
	for <rohc-web-archive@ietf.org>; Wed, 31 Mar 2004 01:23:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8Z8n-0003AF-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 01:23:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8Z7s-00035B-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 01:23:01 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8Z6v-000302-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 01:22:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Z6u-0007MR-Vv; Wed, 31 Mar 2004 01:22:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Z6j-0007LL-Bz
	for rohc@optimus.ietf.org; Wed, 31 Mar 2004 01:21:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02014
	for <rohc@ietf.org>; Wed, 31 Mar 2004 01:21:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8Z6g-0002y5-00
	for rohc@ietf.org; Wed, 31 Mar 2004 01:21:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8Z5i-0002ta-00
	for rohc@ietf.org; Wed, 31 Mar 2004 01:20:47 -0500
Received: from mta0.huawei.com ([61.144.161.41] helo=huawei.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8Z4m-0002mu-00
	for rohc@ietf.org; Wed, 31 Mar 2004 01:19:52 -0500
Received: from sumanccl20088 (huawei.com [172.17.1.62])
 by mta0.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.8 (built Jul 12
 2002)) with ESMTPA id <0HVF00H22G55V2@mta0.huawei.com> for rohc@ietf.org; Wed,
 31 Mar 2004 14:17:31 +0800 (CST)
Date: Wed, 31 Mar 2004 11:50:22 +0530
From: suman <sumanc@huawei.com>
To: rohc@ietf.org
Message-id: <001801c416e8$40043da0$6d05120a@sumanccl20088>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
Content-type: multipart/alternative;
 boundary="Boundary_(ID_cJTkVkU2bcOtNQeBWqYR/w)"
X-Priority: 3
X-MSMail-priority: Normal
Subject: [rohc] Regarding SIP and sigcomp
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,HTML_30_40,HTML_MESSAGE 
	autolearn=no version=2.60

This is a multi-part message in MIME format.

--Boundary_(ID_cJTkVkU2bcOtNQeBWqYR/w)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

Hi,

    The SigComp solution for compressing messages requires state memory to be allocated
on a per compartment basis.  For a sip endpoint, the recommended state memory size is 2048 bytes.
   However, for a SIP proxy implementing SIGCOMP and handling thousands of endpoints, maintaining so many states requires memory which most of the proxies cannot afford.
  Going for a simple stateless mechanism is one way of alleviating this problem, but the compromise
is the lower compression ratio.

  What is the recommded implementation at the SIP proxy ?? Is is stateful or stateless,..??

   Any comments on this would be useful,

thanks
suman

--Boundary_(ID_cJTkVkU2bcOtNQeBWqYR/w)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1106" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; The SigComp solution for 
compressing messages requires state memory to be allocated</FONT></DIV>
<DIV><FONT face=Arial size=2>on a per compartment basis.&nbsp; For a sip 
endpoint, the recommended state memory size is 2048 bytes.</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp; However, for a SIP proxy implementing 
SIGCOMP and handling thousands of endpoints, maintaining so many states 
</FONT><FONT face=Arial size=2>requires memory which most of the proxies cannot 
afford.</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp; Going for a simple stateless mechanism is 
one way of alleviating this problem, but the compromise</FONT></DIV>
<DIV><FONT face=Arial size=2>is the lower compression ratio.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;What is the recommded implementation at 
the SIP proxy ?? Is is stateful or stateless,..??</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp; Any comments on this would be 
useful,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>thanks</FONT></DIV>
<DIV><FONT face=Arial size=2>suman</FONT></DIV></BODY></HTML>

--Boundary_(ID_cJTkVkU2bcOtNQeBWqYR/w)--

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



From exim@www1.ietf.org  Wed Mar 31 04:20:34 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08280
	for <rohc-archive@odin.ietf.org>; Wed, 31 Mar 2004 04:20:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8btC-0005Ch-Qo
	for rohc-archive@odin.ietf.org; Wed, 31 Mar 2004 04:20:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2V9K2P3020002
	for rohc-archive@odin.ietf.org; Wed, 31 Mar 2004 04:20:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8btB-0005CN-P6
	for rohc-web-archive@optimus.ietf.org; Wed, 31 Mar 2004 04:20:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08240
	for <rohc-web-archive@ietf.org>; Wed, 31 Mar 2004 04:19:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8bt9-0007D0-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 04:19:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8bsA-00073F-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 04:18:59 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8brF-0006wH-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 04:18:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8brH-0004kB-AW; Wed, 31 Mar 2004 04:18:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8bql-0004gf-0y
	for rohc@optimus.ietf.org; Wed, 31 Mar 2004 04:17:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08084
	for <rohc@ietf.org>; Wed, 31 Mar 2004 04:17:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8bqi-0006sS-00
	for rohc@ietf.org; Wed, 31 Mar 2004 04:17:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8bpj-0006m1-00
	for rohc@ietf.org; Wed, 31 Mar 2004 04:16:28 -0500
Received: from [194.237.235.30] (helo=effnet.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8boz-0006dO-00
	for rohc@ietf.org; Wed, 31 Mar 2004 04:15:41 -0500
Received: from effnet.com (c-497871d5.04-205-6c756c1.cust.bredbandsbolaget.se [213.113.120.73])
	(authenticated bits=0)
	by effnet.com (8.12.3/8.12.3) with ESMTP id i2V8ElU2024137
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Wed, 31 Mar 2004 10:14:48 +0200
Message-ID: <406A8C19.2010603@effnet.com>
Date: Wed, 31 Mar 2004 11:15:05 +0200
From: Kristofer Sandlund <kristofer.sandlund@effnet.com>
Organization: Effnet
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030821
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: zhigang.c.liu@nokia.com
CC: kd.singh@enst-bretagne.fr, szym_paw@wp.pl, lars-erik.jonsson@ericsson.com,
        rohc@ietf.org
Subject: Re: [rohc] Slope used to compress/decompress RTP Timestamp field
References: <7B5AF06E216CB74DA8A5960A3181B5B8153723@ajebe001.americas.nokia.com>
In-Reply-To: <7B5AF06E216CB74DA8A5960A3181B5B8153723@ajebe001.americas.nokia.com>
X-Enigmail-Version: 0.76.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Zhigang.

Comments inlined.

zhigang.c.liu@nokia.com wrote:
> Hi Kristofer,
> 
> I don't know if you have read my reply to your earlier email:
> http://www1.ietf.org/mail-archive/working-groups/rohc/current/msg02042.html.
> Please let me know if you agree with my comments on your observations, 
> on which you based your conclusion "there cannot be room for a slope ...".
> 

Let me first clarify:
I never meant that slope can never be made to work, a slope scheme that is fully 
specified _should_ be able to interop. The problem to me is that IF there is a 
slope defined, then it contradicts a lot of places in the other text (such as 
the definition of TS_STRIDE in section 2.0).

> Also, it seems to me that two different issues are discussed here:
> a) Does RFC 3095 describe slope clear enough?
> b) Is the slope needed?
> 

I would say that the questions would be:
a) Does slope exist in 3095?

    if the answer to a) is yes, then
      a2) Is the slope needed?
         if a2) is yes then a3) How do we specify it more clearly?
         if a2) is no, what do we do instead?

    if the answer to a) is no, then
      a4) What do we do instead and how do we specify that (if needed)?

The questions you have written assume that the slope is defined in 3095, and 
both myself (and it seems L-E does as well) doubt that this is what one can read 
from the spec.

BR,
	Kristofer Sandlund, Effnet AB

> For a), if the conclusion is that it's not clear enough in RFC3095, it can 
> be clarified in implementation guide.
> 
> For b), if the conclusion is that it is not needed, we can create a new 
> profile excluding it.
> 
> I'd suggest to keep the two issues separate in order to have a well-pointed
> discussion.
> 
> BR,
> Zhigang
> 


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



From exim@www1.ietf.org  Wed Mar 31 04:24:23 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08449
	for <rohc-archive@odin.ietf.org>; Wed, 31 Mar 2004 04:24:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8bwy-0005Tj-8F
	for rohc-archive@odin.ietf.org; Wed, 31 Mar 2004 04:23:56 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2V9Nu5T021060
	for rohc-archive@odin.ietf.org; Wed, 31 Mar 2004 04:23:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8bwx-0005Tb-Ue
	for rohc-web-archive@optimus.ietf.org; Wed, 31 Mar 2004 04:23:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08427
	for <rohc-web-archive@ietf.org>; Wed, 31 Mar 2004 04:23:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8bwv-0007gR-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 04:23:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8bvy-0007Yp-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 04:22:55 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8bv4-0007QD-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 04:21:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8bv6-0005KE-K9; Wed, 31 Mar 2004 04:22:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8buA-0005Fz-1A
	for rohc@optimus.ietf.org; Wed, 31 Mar 2004 04:21:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08317
	for <rohc@ietf.org>; Wed, 31 Mar 2004 04:20:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8bu7-0007K8-00
	for rohc@ietf.org; Wed, 31 Mar 2004 04:20:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8btA-0007DM-00
	for rohc@ietf.org; Wed, 31 Mar 2004 04:20:01 -0500
Received: from [194.237.235.30] (helo=effnet.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8bsE-000708-00
	for rohc@ietf.org; Wed, 31 Mar 2004 04:19:02 -0500
Received: from effnet.com (c-497871d5.04-205-6c756c1.cust.bredbandsbolaget.se [213.113.120.73])
	(authenticated bits=0)
	by effnet.com (8.12.3/8.12.3) with ESMTP id i2V8IAU2024164
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Wed, 31 Mar 2004 10:18:10 +0200
Message-ID: <406A8CE4.8090209@effnet.com>
Date: Wed, 31 Mar 2004 11:18:28 +0200
From: Kristofer Sandlund <kristofer.sandlund@effnet.com>
Organization: Effnet
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030821
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: kamal deep singh <kd.singh@enst-bretagne.fr>
CC: zhigang.c.liu@nokia.com, szym_paw@wp.pl, lars-erik.jonsson@ericsson.com,
        rohc@ietf.org
Subject: Re: [rohc] Slope used to compress/decompress RTP Timestamp field
References: <7B5AF06E216CB74DA8A5960A3181B5B815371C@ajebe001.americas.nokia.com> <406927A6.8090603@effnet.com> <004801c41695$3445e2f0$ee4a34c1@rennes.enstbretagne.fr>
In-Reply-To: <004801c41695$3445e2f0$ee4a34c1@rennes.enstbretagne.fr>
X-Enigmail-Version: 0.76.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Kamal & Zhigang

I have put both your mails below here (Zhigangs mail below), since you both 
discuss my "semi-constant TS example".

Comments inlined.

kamal deep singh wrote:
> Hi Kristofer,
> 
> I still have some problems regarding the method which you use
> to compress Time Stamp (It may be because I do not know some points).
> 

One comment is that the method that I described was something I whipped while 
writing that mail, since it seemed like the logical interpretation. Therefore, I 
  described the principle of how I understood it to work than the exact method 
to use it. It might need some further analysis of how it can work. I'll try to 
look at that later this week.

> your method as I understand is as follows:
> Also please read my comments (after the method) questioning its
> interoperability.
> And Please correct me if something is written wrong.
> 
> There seem to be 1 equation.
> 
> i) TS = SN * slope + offset;  (As written in your mail. And you intend to
> use slope = TS_STRIDE)
> 
> COMPRESSOR SIDE:
> ------------------------
> always TS_STRIDE = TS - TS_prev;
> 
> FO STATE: (choosing the smallest packet)
>      1) Communicate TS_STRIDE L times if it changes and comes to a stable
>           value.
>      2) Communicate offset L times if it changes with respect to
>           eq. i) and TS_STRIIDE in 1) above is not stable.
>      3) If nothing changes then go to SO STATE:
> 
> SO STATE:
>      1) If anything changes (TS_STRIDE , offset with respect to eq i),
> ......)
>          then go to FO STATE.
>       2) If nothing changes then send just SN (wlsb encoded)
>           or UO_0.
> 
> DECOMPRESSOR SIDE:
> ---------------------------
> 
>     1) If Abs TS and TS_STRIDE are recieved then update them and
>         also update offset = Abs TS%TS_STRIDE
>     2) If no bits of TS are recieved then calculate
>         TS = SN* TS_STRIDE + offset.
> 
> 
> I have some problems with your method.
> One is that equation i) which you use is nowhere given in the RFC
> and instead , TS = TS_SCALED*TS_STRIDE + offset is mentioned.
> I feel that RFC does not intend to use the equation i) and thus the method
> will not
> be interoperable.
> 
> Other is that you nowhere mention to use TS_SCALED and the equation
> TS = TS_SCALED*TS_STRIDE + offset; in your method.
> Variable TS_SCALED and this equation are the base to compress TS and are
> explicitly given in RFC.
> Thus, the method looks more interoperable to me.
> 
> Till now, I do not find your method interoperable.
> Or please make your method a little more clear and it will be very helpful.
> 
> regards,
> Kamal
> 


zhigang.c.liu@nokia.com wrote:
 > Hi,
 >
 > As I replied earlier, Kamal's understanding is correct. Now that I
 > have time looking at the following interpretation, it is
 > - unfortunately - even beyond "over interpreting" (quote from
 > Lars-Erik). It is incorrect.
 >
 > Please see detailed comments below.
 >
 > BR,
 > Zhigang
 >
 > [Kristofer wrote:]
 >
 >
 >>Let's say that the unscaled TS in the video example will be
 >>30 and the starting value 10, then we'd have this:
 >>
 >>10, 10, 10, 10, 40, 40, 40, 40, 40, 40, 40, 70, 100, 130
 >>
 >>As you observe, the "video slope will be 0 most of the time".
 >>This is the observation that your compressor also should make, and
 >>therefore use a TS_STRIDE of 0.
 >
 >
 > I'm really confused. How come TS_STRIDE is same as slope? What
 > do you mean by a scaling by a factor of 0? This is certainly not
 > what RFC 3095 says.
 >

My comments are based around the assumption that "there is no slope", so I am 
not claiming that they are the same thing. TS_STRIDE is the delta in TS, so it 
is "_a_ slope of the TS", I did not mean the "slope" that you consider.

 >
 >>What we can do when the TS changes from 10 to 40 is that we
 >>can interpret this as a change of TS_OFFSET instead of saying
 >>that TS_STRIDE (or slope) changes.
 >
 >
 > Again, TS_STRIDE != slope.
 >

See above.

 >
 >>So we keep the TS_STRIDE as 0, but change TS_OFFSET from 10
 >>to 40, which we do by sending some UOR-2-ext3 with an unscaled
 >>timestamp according to the optimistic approach, and then move
 >>back to sending UO-0 packets.
 >
 >
 > How could this be possible? As specified in RFC 3095, TS_OFFSET
 > calculated locally as TS modulo TS_STRIDE. Don't you have problem
 > of division by zero?

Good point. This is something that we ran into at the interop in Berlin. Some 
testcase made some implementation set the TS_STRIDE to zero, and some of us 
discussed how this should be handled and I think we said that "if STRIDE=0 then 
TS_OFFSET = TS", since that seems logaical enough. Now I realize that this has 
never been communicated to the list, so that was a mistake of me to assume it 
was (short memory :)

But even if we would use "slope", this would be an issue. There is nothing in 
the spec that stops a compressor from setting TS_STRIDE=0, which would lead to 
zero division, so this must be clarified whichever way we go. I.e we MUST define 
what "X mod 0" means in the ROHC spec, since it can happen!

Conceptually, I can't see a problem with the solution I outlined if the "modulus 
thing" is clarified, but I should probably have to look into exactly what the 
spec says before I can say for sure.

BR,
	Kristofer Sandlund, Effnet AB


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



From exim@www1.ietf.org  Wed Mar 31 10:18:36 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27722
	for <rohc-archive@odin.ietf.org>; Wed, 31 Mar 2004 10:18:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8hTl-0000wy-LQ
	for rohc-archive@odin.ietf.org; Wed, 31 Mar 2004 10:18:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2VFI9gE003632
	for rohc-archive@odin.ietf.org; Wed, 31 Mar 2004 10:18:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8hTk-0000wV-WC
	for rohc-web-archive@optimus.ietf.org; Wed, 31 Mar 2004 10:18:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27656
	for <rohc-web-archive@ietf.org>; Wed, 31 Mar 2004 10:18:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8hTi-0005vR-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 10:18:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8hSh-0005oT-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 10:17:04 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8hRj-0005lC-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 10:16:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8hRk-0000Nw-Oj; Wed, 31 Mar 2004 10:16:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8hR4-0000Eb-Uk
	for rohc@optimus.ietf.org; Wed, 31 Mar 2004 10:15:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27401
	for <rohc@ietf.org>; Wed, 31 Mar 2004 10:15:19 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8hR2-0005i0-00
	for rohc@ietf.org; Wed, 31 Mar 2004 10:15:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8hPv-0005dN-00
	for rohc@ietf.org; Wed, 31 Mar 2004 10:14:12 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8hP5-0005Zz-00
	for rohc@ietf.org; Wed, 31 Mar 2004 10:13:19 -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 i2VFDBh27939;
	Wed, 31 Mar 2004 18:13:11 +0300 (EET DST)
X-Scanned: Wed, 31 Mar 2004 18:12:17 +0300 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i2VFCHJG008360;
	Wed, 31 Mar 2004 18:12:17 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 00Ldif3z; Wed, 31 Mar 2004 18:12:16 EEST
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 i2VFC5s18137;
	Wed, 31 Mar 2004 18:12:05 +0300 (EET DST)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Wed, 31 Mar 2004 09:11:44 -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] Slope used to compress/decompress RTP Timestamp field
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Wed, 31 Mar 2004 10:11:42 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B8153729@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] Slope used to compress/decompress RTP Timestamp field
Thread-Index: AcQXAZkSAEDg2G4oQi2DA7MckjazrgAK++4Q
To: <kristofer.sandlund@effnet.com>
Cc: <kd.singh@enst-bretagne.fr>, <szym_paw@wp.pl>,
        <lars-erik.jonsson@ericsson.com>, <rohc@ietf.org>
X-OriginalArrivalTime: 31 Mar 2004 15:11:44.0110 (UTC) FILETIME=[7A5040E0:01C41732]
Content-Transfer-Encoding: quoted-printable
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

> zhigang.c.liu@nokia.com wrote:
> > Hi Kristofer,
> >=20
> > I don't know if you have read my reply to your earlier email:
> >=20
> > =
http://www1.ietf.org/mail-archive/working-groups/rohc/current/msg02042.ht=
ml.
> > Please let me know if you agree with my comments on your =
observations,=20
> > on which you based your conclusion "there cannot be room for a slope =
...".
> >=20
>=20
> The problem to me is that IF there is a=20
> slope defined, then it contradicts a lot of places in the=20
> other text (such as the definition of TS_STRIDE in section 2.0).

Please, read my email above and tell me straight if you agree or not.

In that email, I've explained why your observations are incorrect.=20
Please let me know if you disagree.

> I would say that the questions would be:
> a) Does slope exist in 3095?

This becomes hair-splitting. But as one of the authors for encoding=20
(section 4.5), I can tell you it does. And it is described in many=20
places in RFC 3095.=20

On the other hand, it may not be described clear enough. We thought=20
the text on FO and SO and function from SN to non-SN-field is=20
sufficient (I personally wanted to add more text in RFC 3095 but it=20
was not agreed by other authors). Either way, it can be clarified=20
more in the implementation I-D.=20

BR,
Zhigang

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



From exim@www1.ietf.org  Wed Mar 31 10:28:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28759
	for <rohc-archive@odin.ietf.org>; Wed, 31 Mar 2004 10:28:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8hdK-0003CZ-96
	for rohc-archive@odin.ietf.org; Wed, 31 Mar 2004 10:28:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2VFS2sH012305
	for rohc-archive@odin.ietf.org; Wed, 31 Mar 2004 10:28:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8hdK-0003CN-3A
	for rohc-web-archive@optimus.ietf.org; Wed, 31 Mar 2004 10:28:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28692
	for <rohc-web-archive@ietf.org>; Wed, 31 Mar 2004 10:27:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8hdH-0006qu-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 10:27:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8hcK-0006l1-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 10:27:01 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8hbM-0006fq-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 10:26:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8hbN-0002x2-L2; Wed, 31 Mar 2004 10:26:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8haZ-0002s9-8K
	for rohc@optimus.ietf.org; Wed, 31 Mar 2004 10:25:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28477
	for <rohc@ietf.org>; Wed, 31 Mar 2004 10:25:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8haU-0006cT-00
	for rohc@ietf.org; Wed, 31 Mar 2004 10:25:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8hZh-0006XC-00
	for rohc@ietf.org; Wed, 31 Mar 2004 10:24:17 -0500
Received: from smtp1.utdallas.edu ([129.110.10.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8hZC-0006Sg-00
	for rohc@ietf.org; Wed, 31 Mar 2004 10:23:47 -0500
Received: from ipnetfusion.com (bluesocket02.utdallas.edu [129.110.39.13])
	by smtp1.utdallas.edu (Postfix) with ESMTP id 35B05389016;
	Wed, 31 Mar 2004 09:23:16 -0600 (CST)
Message-ID: <406AE41E.8010401@ipnetfusion.com>
Date: Wed, 31 Mar 2004 09:30:38 -0600
From: chintan <cthakker@ipnetfusion.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: suman <sumanc@huawei.com>
Cc: rohc@ietf.org
Subject: Re: [rohc] Regarding SIP and sigcomp
References: <001801c416e8$40043da0$6d05120a@sumanccl20088>
In-Reply-To: <001801c416e8$40043da0$6d05120a@sumanccl20088>
Content-Type: multipart/alternative;
 boundary="------------010704080801020307030302"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.4 required=5.0 tests=HTML_30_40,HTML_MESSAGE,
	HTML_TITLE_EMPTY autolearn=no version=2.60

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

Hi,
A sip endpoint may request state creation request upto 2048 bytes. The 
state creation request may be for a state that is already present at the 
state handler in which case there is no additional memory allocated, but 
just the state identifier returned.

Hence the amount of memory allocated may be less than (num_of_endpoints 
* 2048)

suman wrote:

> Hi,
>  
>     The SigComp solution for compressing messages requires state 
> memory to be allocated
> on a per compartment basis.  For a sip endpoint, the recommended state 
> memory size is 2048 bytes.
>    However, for a SIP proxy implementing SIGCOMP and handling 
> thousands of endpoints, maintaining so many states requires memory 
> which most of the proxies cannot afford.
>   Going for a simple stateless mechanism is one way of alleviating 
> this problem, but the compromise
> is the lower compression ratio.
>  
>   What is the recommded implementation at the SIP proxy ?? Is is 
> stateful or stateless,..??
>  
>    Any comments on this would be useful,
>  
> thanks
> suman


--------------010704080801020307030302
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Hi,<br>
A sip endpoint may request state creation request upto 2048 bytes. The
state creation request may be for a state that is already present at
the state handler in which case there is no additional memory
allocated, but just the state identifier returned.<br>
<br>
Hence the amount of memory allocated may be less than (num_of_endpoints
* 2048)<br>
<br>
suman wrote:<br>
<blockquote type="cite"
 cite="mid001801c416e8$40043da0$6d05120a@sumanccl20088">
  <meta http-equiv="Content-Type" content="text/html; ">
  <meta content="MSHTML 6.00.2800.1106" name="GENERATOR">
  <style></style>
  <div><font face="Arial" size="2">Hi,</font></div>
  <div>&nbsp;</div>
  <div><font face="Arial" size="2">&nbsp;&nbsp;&nbsp; The SigComp solution for
compressing messages requires state memory to be allocated</font></div>
  <div><font face="Arial" size="2">on a per compartment basis.&nbsp; For a
sip endpoint, the recommended state memory size is 2048 bytes.</font></div>
  <div><font face="Arial" size="2">&nbsp;&nbsp; However, for a SIP proxy
implementing SIGCOMP and handling thousands of endpoints, maintaining
so many states </font><font face="Arial" size="2">requires memory
which most of the proxies cannot afford.</font></div>
  <div><font face="Arial" size="2">&nbsp; Going for a simple stateless
mechanism is one way of alleviating this problem, but the compromise</font></div>
  <div><font face="Arial" size="2">is the lower compression ratio.</font></div>
  <div>&nbsp;</div>
  <div><font face="Arial" size="2">&nbsp;&nbsp;What is the recommded
implementation at the SIP proxy ?? Is is stateful or stateless,..??</font></div>
  <div>&nbsp;</div>
  <div><font face="Arial" size="2">&nbsp;&nbsp; Any comments on this would be
useful,</font></div>
  <div>&nbsp;</div>
  <div><font face="Arial" size="2">thanks</font></div>
  <div><font face="Arial" size="2">suman</font></div>
</blockquote>
</body>
</html>

--------------010704080801020307030302--


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



From exim@www1.ietf.org  Wed Mar 31 11:31:41 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00986
	for <rohc-archive@odin.ietf.org>; Wed, 31 Mar 2004 11:31:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8icS-0007eu-L3
	for rohc-archive@odin.ietf.org; Wed, 31 Mar 2004 11:31:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2VGVADH029433
	for rohc-archive@odin.ietf.org; Wed, 31 Mar 2004 11:31:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8icQ-0007dj-Eg
	for rohc-web-archive@optimus.ietf.org; Wed, 31 Mar 2004 11:31:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00968
	for <rohc-web-archive@ietf.org>; Wed, 31 Mar 2004 11:30:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8icA-0002XR-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 11:30:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8ibI-0002Sz-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 11:30:00 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8iaL-0002PZ-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 11:29:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8iaL-0007Uo-TZ; Wed, 31 Mar 2004 11:29:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8iaJ-0007UR-9i
	for rohc@optimus.ietf.org; Wed, 31 Mar 2004 11:28:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00938
	for <rohc@ietf.org>; Wed, 31 Mar 2004 11:28:56 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8iaI-0002Ov-00
	for rohc@ietf.org; Wed, 31 Mar 2004 11:28:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8iZT-0002NA-00
	for rohc@ietf.org; Wed, 31 Mar 2004 11:28:08 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8iYn-0002Kt-00
	for rohc@ietf.org; Wed, 31 Mar 2004 11:27:25 -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 i2VGRGh17009;
	Wed, 31 Mar 2004 19:27:16 +0300 (EET DST)
X-Scanned: Wed, 31 Mar 2004 19:25:52 +0300 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i2VGPqJg011858;
	Wed, 31 Mar 2004 19:25:52 +0300
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks003.ntc.nokia.com 00uSDqob; Wed, 31 Mar 2004 19:25:36 EEST
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 i2VGPYF18594;
	Wed, 31 Mar 2004 19:25:35 +0300 (EET DST)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Wed, 31 Mar 2004 10:25:20 -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] Slope used to compress/decompress RTP Timestamp field
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Wed, 31 Mar 2004 11:25:19 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B815372A@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] Slope used to compress/decompress RTP Timestamp field
Thread-Index: AcQXAhqRu7dQVKRdQ6ic6/1YECAh/AAMa+nQ
To: <kristofer.sandlund@effnet.com>, <kd.singh@enst-bretagne.fr>
Cc: <szym_paw@wp.pl>, <lars-erik.jonsson@ericsson.com>, <rohc@ietf.org>
X-OriginalArrivalTime: 31 Mar 2004 16:25:20.0479 (UTC) FILETIME=[C2ACAEF0:01C4173C]
Content-Transfer-Encoding: quoted-printable
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

> One comment is that the method that I described was something=20
> I whipped while writing that mail, since it seemed like the=20
> logical interpretation. Therefore, I described the principle=20
> of how I understood it to work than the exact method to use it.=20
> It might need some further analysis of how it can work. I'll=20
> try to look at that later this week.

I thought you have been "convinced" that "there cannot be room=20
for a slope" because of this? =20

It looks to me that you are now *developing* your understanding.
Do we fall into the trap that if one can develop a different
method than what is described in RFC 3095, then it proves that=20
slope does not exist in RFC 3095?

> My comments are based around the assumption that "there is no=20
> slope", so I am not claiming that they are the same thing.=20

Sorry, have you said the following in your earlier email?
http://www1.ietf.org/mail-archive/working-groups/rohc/current/msg02033.ht=
ml

"if we narrow this down to TS, then we get TS =3D SN * slope + offset.
Compare this to the formula in 4.5.3 (quoted above), then suddenly
it becomes clear that "slope" really means TS_STRIDE in this section."

> TS_STRIDE is the delta in TS, so it is "_a_ slope of the TS",=20
> I did not mean the "slope" that you consider.

Please, use TS_STRIDE as described in RFC 3095, which is a scale
factor, and use slope as what it means in mathematics for a line,
i.e., non-SN-field =3D SN * slope + offset. It will help a lot
for the discussion.

> Some testcase made some implementation set the TS_STRIDE to zero,=20

This is simply an incorrect implementation (see section 4.5.3).

It also demonstrated again the fundamental difference between
slope and TS_STRIDE. The former can be zero, while the latter
cannot.

> and some of us discussed how this should be handled and I=20
> think we said that "if STRIDE=3D0 then TS_OFFSET =3D TS", since=20
> that seems logaical enough.=20

This is NOT logical and NOT what RFC 3095 says. Again, please
read section 4.5.3.

> we MUST define what "X mod 0" means in the ROHC spec,=20

It means division by zero, as it means in basic mathematics.
Do we have to redefine every operation in mathematics?
I'm becoming speechless ...=20

BR,
Zhigang

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



From exim@www1.ietf.org  Wed Mar 31 12:02:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01849
	for <rohc-archive@odin.ietf.org>; Wed, 31 Mar 2004 12:02:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8j6I-0002OR-Tg
	for rohc-archive@odin.ietf.org; Wed, 31 Mar 2004 12:02:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2VH227N009200
	for rohc-archive@odin.ietf.org; Wed, 31 Mar 2004 12:02:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8j6I-0002OJ-Kp
	for rohc-web-archive@optimus.ietf.org; Wed, 31 Mar 2004 12:02:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01834
	for <rohc-web-archive@ietf.org>; Wed, 31 Mar 2004 12:01:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8j6H-00040N-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 12:02:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8j5E-0003xM-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 12:00:57 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8j4L-0003uf-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 12:00:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8j4L-0001uz-4X; Wed, 31 Mar 2004 12:00:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8j4E-0001uF-PK
	for rohc@optimus.ietf.org; Wed, 31 Mar 2004 11:59:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01785
	for <rohc@ietf.org>; Wed, 31 Mar 2004 11:59:51 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8j4D-0003tZ-00
	for rohc@ietf.org; Wed, 31 Mar 2004 11:59:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8j3E-0003mz-00
	for rohc@ietf.org; Wed, 31 Mar 2004 11:58:53 -0500
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8j2K-0003k4-00
	for rohc@ietf.org; Wed, 31 Mar 2004 11:57:56 -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 i2VGvf308665;
	Wed, 31 Mar 2004 19:57:41 +0300 (EET DST)
X-Scanned: Wed, 31 Mar 2004 19:57:17 +0300 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i2VGvHCe022552;
	Wed, 31 Mar 2004 19:57:17 +0300
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks003.ntc.nokia.com 00LdNMB4; Wed, 31 Mar 2004 19:57:15 EEST
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 i2VGvFF01576;
	Wed, 31 Mar 2004 19:57:15 +0300 (EET DST)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Wed, 31 Mar 2004 10:57:12 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C41741.351167D5"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Subject: RE: [rohc] Regarding SIP and sigcomp
Date: Wed, 31 Mar 2004 11:57:10 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B815372B@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] Regarding SIP and sigcomp
Thread-Index: AcQW6MH65Qpmg0VEQ2qEHBIbwpABugAVKWAw
To: <sumanc@huawei.com>, <rohc@ietf.org>
X-OriginalArrivalTime: 31 Mar 2004 16:57:12.0064 (UTC) FILETIME=[36116800:01C41741]
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,HTML_30_40,
	HTML_FONTCOLOR_BLUE,HTML_MESSAGE,NO_REAL_NAME autolearn=no 
	version=2.60

This is a multi-part message in MIME format.

------_=_NextPart_001_01C41741.351167D5
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Suman,
=20
This is still one issue in the on-going I-D: =
http://www.ietf.org/internet-drafts/draft-ietf-rohc-sigcomp-sip-01.txt. =
As you said, it's a tradeoff between compression ratio and memory.
=20
In your case, how many active endpoints a SIP proxy need to support? By =
active, I mean an endpoint that has compartment open at proxy. (Note: to =
be accurate, we should count the number of compartment because one =
endpoint can have multiple compartments created in SIP proxy, but let's =
for now assume the simple/practical case of one-to-one. )
=20
With 2KB SMS, 1GB memory can support about 524, 000 endpoints. I don't =
know how much a cost issue that would be. Personally, I tend to think it =
is not a big deal (you can buy 1GB memory for PC with $250 ~ $500). But =
it can be more expensive depending on platform, etc.
=20
Again, the bottom line is, how much you want to pay for what compression =
ratio (and ultimately reduction in call setup delay).
=20
BR,
Zhigang
=20

-----Original Message-----
From: rohc-admin@ietf.org [mailto:rohc-admin@ietf.org]On Behalf Of ext =
suman
Sent: 31 March, 2004 12:20 AM
To: rohc@ietf.org
Subject: [rohc] Regarding SIP and sigcomp


Hi,
=20
    The SigComp solution for compressing messages requires state memory =
to be allocated
on a per compartment basis.  For a sip endpoint, the recommended state =
memory size is 2048 bytes.
   However, for a SIP proxy implementing SIGCOMP and handling thousands =
of endpoints, maintaining so many states requires memory which most of =
the proxies cannot afford.
  Going for a simple stateless mechanism is one way of alleviating this =
problem, but the compromise
is the lower compression ratio.
=20
  What is the recommded implementation at the SIP proxy ?? Is is =
stateful or stateless,..??
=20
   Any comments on this would be useful,
=20
thanks
suman


------_=_NextPart_001_01C41741.351167D5
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=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><SPAN class=3D067572916-31032004><FONT face=3DArial color=3D#0000ff =
size=3D2>Hi=20
Suman,</FONT></SPAN></DIV>
<DIV><SPAN class=3D067572916-31032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D067572916-31032004><FONT face=3DArial color=3D#0000ff =
size=3D2>This=20
is still one issue in the on-going I-D: <A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-rohc-sigcomp-sip-0=
1.txt">http://www.ietf.org/internet-drafts/draft-ietf-rohc-sigcomp-sip-01=
txt</A>.=20
As you said, it's a tradeoff between compression ratio and=20
memory.</FONT></SPAN></DIV>
<DIV><SPAN class=3D067572916-31032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D067572916-31032004><FONT face=3DArial color=3D#0000ff =
size=3D2>In=20
your case, how many active endpoints a SIP proxy need to support? By =
active, I=20
mean an endpoint that has compartment open at proxy. (Note: to be =
accurate, we=20
should count the number of compartment&nbsp;because one endpoint can =
have=20
multiple compartments created in SIP proxy, but let's&nbsp;for =
now&nbsp;assume=20
the simple/practical case of one-to-one. )</FONT></SPAN></DIV>
<DIV><SPAN class=3D067572916-31032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D067572916-31032004><FONT face=3DArial color=3D#0000ff =
size=3D2>With=20
2KB SMS, 1GB memory can support about 524, 000 endpoints. I don't know =
how much=20
a cost issue that would be. Personally, I tend to think it is not a big =
deal=20
(you can buy 1GB memory for PC with $250 ~ $500). But it can be more =
expensive=20
depending on platform, etc.</FONT></SPAN></DIV>
<DIV><SPAN class=3D067572916-31032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D067572916-31032004><FONT face=3DArial color=3D#0000ff =
size=3D2>Again,=20
the bottom line is, how much you want to pay for what compression ratio =
(and=20
ultimately reduction in call setup delay).</FONT></SPAN></DIV>
<DIV><SPAN class=3D067572916-31032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D067572916-31032004><FONT face=3DArial color=3D#0000ff =

size=3D2>BR,</FONT></SPAN></DIV>
<DIV><SPAN class=3D067572916-31032004><FONT face=3DArial color=3D#0000ff =

size=3D2>Zhigang</FONT></SPAN></DIV>
<DIV><SPAN class=3D067572916-31032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> =
rohc-admin@ietf.org=20
  [mailto:rohc-admin@ietf.org]<B>On Behalf Of </B>ext =
suman<BR><B>Sent:</B> 31=20
  March, 2004 12:20 AM<BR><B>To:</B> rohc@ietf.org<BR><B>Subject:</B> =
[rohc]=20
  Regarding SIP and sigcomp<BR><BR></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; The SigComp =
solution for=20
  compressing messages requires state memory to be =
allocated</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>on a per compartment basis.&nbsp; For =
a sip=20
  endpoint, the recommended state memory size is 2048 =
bytes.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; However, for a SIP proxy =

  implementing SIGCOMP and handling thousands of endpoints, maintaining =
so many=20
  states </FONT><FONT face=3DArial size=3D2>requires memory which most =
of the=20
  proxies cannot afford.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp; Going for a simple stateless =
mechanism is=20
  one way of alleviating this problem, but the compromise</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>is the lower compression =
ratio.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;What is the recommded =
implementation=20
  at the SIP proxy ?? Is is stateful or stateless,..??</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; Any comments on this =
would be=20
  useful,</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>thanks</FONT></DIV>
  <DIV><FONT face=3DArial =
size=3D2>suman</FONT></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C41741.351167D5--

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



From exim@www1.ietf.org  Wed Mar 31 13:22:59 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05751
	for <rohc-archive@odin.ietf.org>; Wed, 31 Mar 2004 13:22:59 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8kM9-0000gb-RM
	for rohc-archive@odin.ietf.org; Wed, 31 Mar 2004 13:22:31 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2VIMSWf002637
	for rohc-archive@odin.ietf.org; Wed, 31 Mar 2004 13:22:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8kLu-0000fh-7L
	for rohc-web-archive@optimus.ietf.org; Wed, 31 Mar 2004 13:22:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05738
	for <rohc-web-archive@ietf.org>; Wed, 31 Mar 2004 13:22:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8kLr-0001Hs-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 13:22:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8kL0-0001GH-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 13:21:19 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8kKk-0001EZ-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 13:21:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8kKk-0000aq-FV; Wed, 31 Mar 2004 13:21:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8kK4-0000ZS-JT
	for rohc@optimus.ietf.org; Wed, 31 Mar 2004 13:20:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05687
	for <rohc@ietf.org>; Wed, 31 Mar 2004 13:20:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8kK2-0001DD-00
	for rohc@ietf.org; Wed, 31 Mar 2004 13:20:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8kJ1-000195-00
	for rohc@ietf.org; Wed, 31 Mar 2004 13:19:16 -0500
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8kIS-00015X-00
	for rohc@ietf.org; Wed, 31 Mar 2004 13:18:40 -0500
Received: from courrier.rennes.enst-bretagne.fr (f1-clust.rennes.enst-bretagne.fr [193.52.74.16])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with ESMTP id i2VII0w31141;
	Wed, 31 Mar 2004 20:18:00 +0200
Received: from pcrsm7 ([193.52.74.238])
	by courrier.rennes.enst-bretagne.fr (8.12.11/8.12.11/2004.01.01) with SMTP id i2VII0lL004677;
	Wed, 31 Mar 2004 20:18:00 +0200 (MEST)
Message-ID: <010b01c4174c$80ba1a90$ee4a34c1@rennes.enstbretagne.fr>
From: "kamal deep singh" <kd.singh@enst-bretagne.fr>
To: "Kristofer Sandlund" <kristofer.sandlund@effnet.com>
Cc: <zhigang.c.liu@nokia.com>, <szym_paw@wp.pl>,
        <lars-erik.jonsson@ericsson.com>, <rohc@ietf.org>
References: <7B5AF06E216CB74DA8A5960A3181B5B815371C@ajebe001.americas.nokia.com> <406927A6.8090603@effnet.com> <004801c41695$3445e2f0$ee4a34c1@rennes.enstbretagne.fr> <406A8CE4.8090209@effnet.com>
Subject: Re: [rohc] Slope used to compress/decompress RTP Timestamp field
Date: Wed, 31 Mar 2004 20:18:00 +0200
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.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Kristofer,

   I seem to see the confusion. What we may be ignoring in our discussion is
the fact that TS can be compressed after scaling or can be compressed
without scaling. This is indicated by the variable "Tsc".  This variable is
important as it tells whether TS is scaled before compression or not.

(Note that Scaled RTP Timestamp encoding may just be called as "encoding"
and not compression as its name goes. and whenever it is used , it encodes
the TS value (downscale) "before" TS gets compressed. Zhigang has already
provided clarification for this point before)

When Tsc = 0 then TS is not scaled and is "compressed as is". Here, your
method
seems to get fit as there is no mention of TS_SCALED and "slope" indeed is
equal to TS_STRIDE in TS = SN*slope + offset. And fits "default-slope(TS) =
value(TS_STRIDE)." as given in section 5.7 of RFC :
     "
      If value(TIME_STRIDE) > 0, timer-based compression of the RTP
      Timestamp is used (see section 4.5.4).

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

But when Tsc = 1 then what could slope mean?

When Tsc = 1 or according to RFC "When using scaled RTP Timestamp encoding,
the TS is downscaled by a factor of TS_STRIDE before compression."
Here, TS is already downscaled by TS_STRIDE and hence there is "no more
scope" of another
downscaling by TS_STRIDE or TS_STRIDE_2 !  in the equation
TS (downscaled) = SN*slope + offset.
rather this slope will be 1 in normal cases and thus is specified in RFC as
"default-slope(TS) = 1" in section 5.7 as above. So, if one uses scaling
then one has to use slope too.


Hence, slope , delta or pattern parameter whatever we may choose its name,
is
required while using TS scaling and is also specified in RFC.

regards,
Kamal


----- Original Message -----
From: "Kristofer Sandlund" <kristofer.sandlund@effnet.com>
To: "kamal deep singh" <kd.singh@enst-bretagne.fr>
Cc: <zhigang.c.liu@nokia.com>; <szym_paw@wp.pl>;
<lars-erik.jonsson@ericsson.com>; <rohc@ietf.org>
Sent: Wednesday, March 31, 2004 11:18 AM
Subject: Re: [rohc] Slope used to compress/decompress RTP Timestamp field


> Hi Kamal & Zhigang
>
> I have put both your mails below here (Zhigangs mail below), since you
both
> discuss my "semi-constant TS example".
>
> Comments inlined.
>
> kamal deep singh wrote:
> > Hi Kristofer,
> >
> > I still have some problems regarding the method which you use
> > to compress Time Stamp (It may be because I do not know some points).
> >
>
> One comment is that the method that I described was something I whipped
while
> writing that mail, since it seemed like the logical interpretation.
Therefore, I
>   described the principle of how I understood it to work than the exact
method
> to use it. It might need some further analysis of how it can work. I'll
try to
> look at that later this week.
>
> > your method as I understand is as follows:
> > Also please read my comments (after the method) questioning its
> > interoperability.
> > And Please correct me if something is written wrong.
> >
> > There seem to be 1 equation.
> >
> > i) TS = SN * slope + offset;  (As written in your mail. And you intend
to
> > use slope = TS_STRIDE)
> >
> > COMPRESSOR SIDE:
> > ------------------------
> > always TS_STRIDE = TS - TS_prev;
> >
> > FO STATE: (choosing the smallest packet)
> >      1) Communicate TS_STRIDE L times if it changes and comes to a
stable
> >           value.
> >      2) Communicate offset L times if it changes with respect to
> >           eq. i) and TS_STRIIDE in 1) above is not stable.
> >      3) If nothing changes then go to SO STATE:
> >
> > SO STATE:
> >      1) If anything changes (TS_STRIDE , offset with respect to eq i),
> > ......)
> >          then go to FO STATE.
> >       2) If nothing changes then send just SN (wlsb encoded)
> >           or UO_0.
> >
> > DECOMPRESSOR SIDE:
> > ---------------------------
> >
> >     1) If Abs TS and TS_STRIDE are recieved then update them and
> >         also update offset = Abs TS%TS_STRIDE
> >     2) If no bits of TS are recieved then calculate
> >         TS = SN* TS_STRIDE + offset.
> >
> >
> > I have some problems with your method.
> > One is that equation i) which you use is nowhere given in the RFC
> > and instead , TS = TS_SCALED*TS_STRIDE + offset is mentioned.
> > I feel that RFC does not intend to use the equation i) and thus the
method
> > will not
> > be interoperable.
> >
> > Other is that you nowhere mention to use TS_SCALED and the equation
> > TS = TS_SCALED*TS_STRIDE + offset; in your method.
> > Variable TS_SCALED and this equation are the base to compress TS and are
> > explicitly given in RFC.
> > Thus, the method looks more interoperable to me.
> >
> > Till now, I do not find your method interoperable.
> > Or please make your method a little more clear and it will be very
helpful.
> >
> > regards,
> > Kamal
> >
>
>
> zhigang.c.liu@nokia.com wrote:
>  > Hi,
>  >
>  > As I replied earlier, Kamal's understanding is correct. Now that I
>  > have time looking at the following interpretation, it is
>  > - unfortunately - even beyond "over interpreting" (quote from
>  > Lars-Erik). It is incorrect.
>  >
>  > Please see detailed comments below.
>  >
>  > BR,
>  > Zhigang
>  >
>  > [Kristofer wrote:]
>  >
>  >
>  >>Let's say that the unscaled TS in the video example will be
>  >>30 and the starting value 10, then we'd have this:
>  >>
>  >>10, 10, 10, 10, 40, 40, 40, 40, 40, 40, 40, 70, 100, 130
>  >>
>  >>As you observe, the "video slope will be 0 most of the time".
>  >>This is the observation that your compressor also should make, and
>  >>therefore use a TS_STRIDE of 0.
>  >
>  >
>  > I'm really confused. How come TS_STRIDE is same as slope? What
>  > do you mean by a scaling by a factor of 0? This is certainly not
>  > what RFC 3095 says.
>  >
>
> My comments are based around the assumption that "there is no slope", so I
am
> not claiming that they are the same thing. TS_STRIDE is the delta in TS,
so it
> is "_a_ slope of the TS", I did not mean the "slope" that you consider.
>
>  >
>  >>What we can do when the TS changes from 10 to 40 is that we
>  >>can interpret this as a change of TS_OFFSET instead of saying
>  >>that TS_STRIDE (or slope) changes.
>  >
>  >
>  > Again, TS_STRIDE != slope.
>  >
>
> See above.
>
>  >
>  >>So we keep the TS_STRIDE as 0, but change TS_OFFSET from 10
>  >>to 40, which we do by sending some UOR-2-ext3 with an unscaled
>  >>timestamp according to the optimistic approach, and then move
>  >>back to sending UO-0 packets.
>  >
>  >
>  > How could this be possible? As specified in RFC 3095, TS_OFFSET
>  > calculated locally as TS modulo TS_STRIDE. Don't you have problem
>  > of division by zero?
>
> Good point. This is something that we ran into at the interop in Berlin.
Some
> testcase made some implementation set the TS_STRIDE to zero, and some of
us
> discussed how this should be handled and I think we said that "if STRIDE=0
then
> TS_OFFSET = TS", since that seems logaical enough. Now I realize that this
has
> never been communicated to the list, so that was a mistake of me to assume
it
> was (short memory :)
>
> But even if we would use "slope", this would be an issue. There is nothing
in
> the spec that stops a compressor from setting TS_STRIDE=0, which would
lead to
> zero division, so this must be clarified whichever way we go. I.e we MUST
define
> what "X mod 0" means in the ROHC spec, since it can happen!
>
> Conceptually, I can't see a problem with the solution I outlined if the
"modulus
> thing" is clarified, but I should probably have to look into exactly what
the
> spec says before I can say for sure.
>
> BR,
> Kristofer Sandlund, Effnet AB
>
>
> _______________________________________________
> 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 exim@www1.ietf.org  Wed Mar 31 13:24:47 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05815
	for <rohc-archive@odin.ietf.org>; Wed, 31 Mar 2004 13:24:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8kNv-0000nG-Ku
	for rohc-archive@odin.ietf.org; Wed, 31 Mar 2004 13:24:19 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2VIOJpA003051
	for rohc-archive@odin.ietf.org; Wed, 31 Mar 2004 13:24:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8kNu-0000n3-Ay
	for rohc-web-archive@optimus.ietf.org; Wed, 31 Mar 2004 13:24:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05806
	for <rohc-web-archive@ietf.org>; Wed, 31 Mar 2004 13:24:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8kNo-0001M9-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 13:24:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8kMs-0001KX-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 13:23:15 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8kMe-0001J7-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 13:23:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8kMf-0000gt-E7; Wed, 31 Mar 2004 13:23:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8kLu-0000fe-6z
	for rohc@optimus.ietf.org; Wed, 31 Mar 2004 13:22:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05732
	for <rohc@ietf.org>; Wed, 31 Mar 2004 13:22:09 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8kLp-0001Ha-00
	for rohc@ietf.org; Wed, 31 Mar 2004 13:22:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8kKx-0001Fx-00
	for rohc@ietf.org; Wed, 31 Mar 2004 13:21:16 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8kKM-0001ER-00
	for rohc@ietf.org; Wed, 31 Mar 2004 13:20:38 -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 i2VIKP815108;
	Wed, 31 Mar 2004 21:20:25 +0300 (EET DST)
X-Scanned: Wed, 31 Mar 2004 21:19:31 +0300 Nokia Message Protector V1.3.21 2004031416 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id i2VIJVnE017136;
	Wed, 31 Mar 2004 21:19:31 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks003.ntc.nokia.com 00zJsDth; Wed, 31 Mar 2004 21:19:28 EEST
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 i2VIJFs10114;
	Wed, 31 Mar 2004 21:19:15 +0300 (EET DST)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Wed, 31 Mar 2004 12:19:02 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Subject: RE: [rohc] Slope used to compress/decompress RTP Timestamp field
Date: Wed, 31 Mar 2004 13:19:01 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B815372C@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] Slope used to compress/decompress RTP Timestamp field
Thread-Index: AcQRituwFtZYfvYYRCuziOfM/0YQuQFuHqxA
To: <lars-erik.jonsson@ERICSSON.COM>, <szym_paw@wp.pl>, <rohc@ietf.org>
X-OriginalArrivalTime: 31 Mar 2004 18:19:02.0470 (UTC) FILETIME=[A4E5E660:01C4174C]
Content-Transfer-Encoding: quoted-printable
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

> The mail list discussions indicates that there were proposals=20
> to have such principles, but the discussions point in the direction of =

> giving up these ideas.
> =
http://www1.ietf.org/mail-archive/working-groups/rohc/old-archive/msg0095=
3.html

That is not true.=20

If you read the emails below, you can see my proposal for the =
decompressor
to learn slope was agreed upon.=20

http://www1.ietf.org/mail-archive/working-groups/rohc/old-archive/msg0093=
4.html
http://www1.ietf.org/mail-archive/working-groups/rohc/old-archive/msg0093=
5.html
http://www1.ietf.org/mail-archive/working-groups/rohc/old-archive/msg0095=
2.html
http://www1.ietf.org/mail-archive/working-groups/rohc/old-archive/msg0095=
3.html
http://www1.ietf.org/mail-archive/working-groups/rohc/old-archive/msg0095=
7.html
http://www1.ietf.org/mail-archive/working-groups/rohc/old-archive/msg0096=
0.html

The email you mentioned above is a discussion on only one logic branch =
in my
proposal, i.e., whether the default-slope or the previous learned slope =
("old_slope")=20
should be used by the decompressor when it receives only one context =
update.=20
It is NOT about the slope learning itself, which has already been =
agreed. In the=20
end, you can see that my proposal to use "old_slope" in the case of one =
"FO"=20
update was also agreed.=20

BR,
Zhigang

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



From exim@www1.ietf.org  Wed Mar 31 16:36:54 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14065
	for <rohc-archive@odin.ietf.org>; Wed, 31 Mar 2004 16:36:54 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8nNr-0007Is-6W
	for rohc-archive@odin.ietf.org; Wed, 31 Mar 2004 16:36:27 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2VLaR0Z028075
	for rohc-archive@odin.ietf.org; Wed, 31 Mar 2004 16:36:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8nNr-0007Ik-0h
	for rohc-web-archive@optimus.ietf.org; Wed, 31 Mar 2004 16:36:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14059
	for <rohc-web-archive@ietf.org>; Wed, 31 Mar 2004 16:36:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8nNp-0003i2-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 16:36:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8nN4-0003fy-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 16:35:39 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8nMS-0003bm-00
	for rohc-web-archive@ietf.org; Wed, 31 Mar 2004 16:35:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8nMS-0007FT-SO; Wed, 31 Mar 2004 16:35:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8nM0-0007Dd-SU
	for rohc@optimus.ietf.org; Wed, 31 Mar 2004 16:34:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14005
	for <rohc@ietf.org>; Wed, 31 Mar 2004 16:34:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8nLy-0003Zk-00
	for rohc@ietf.org; Wed, 31 Mar 2004 16:34:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8nL7-0003Uq-00
	for rohc@ietf.org; Wed, 31 Mar 2004 16:33:37 -0500
Received: from mailhub.fokus.fraunhofer.de ([193.174.154.14])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8nKG-0003R6-00
	for rohc@ietf.org; Wed, 31 Mar 2004 16:32:45 -0500
Received: from sfo.somewhere.de (pD9E7FF89.dip.t-dialin.net [217.231.255.137])
	by mailhub.fokus.fraunhofer.de (8.11.6p2/8.11.6) with ESMTP id i2VLWhJ04751
	for <rohc@ietf.org>; Wed, 31 Mar 2004 23:32:43 +0200 (MEST)
Date: Wed, 31 Mar 2004 23:32:39 +0200
From: Stefan Foeckel <stefan.foeckel@fokus.fraunhofer.de>
Reply-To: Stefan Foeckel <stefan.foeckel@fokus.fraunhofer.de>
Organization: Fraunhofer Institut Fokus, Deutschland
X-Priority: 3 (Normal)
Message-ID: <883144150.20040331233239@fokus.fraunhofer.de>
To: rohc@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mailhub.fokus.fraunhofer.de id i2VLWhJ04751
Content-Transfer-Encoding: quoted-printable
Subject: [rohc] SigComp byte copying question
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hello,

I am looking for some clarification regarding byte copying in SigComp.

Section 8.4 RFC 3320 states:

"... if a byte is copied from/to Address m then the next byte is
copied from/to Address n where n is calculated as follows:

k :=3D m + 1 (modulo 2^16)
If k =3D byte_copy_right then set n :=3D byte_copy_left, else set n :=3D =
k
..."

What is the expected destination address, if the first address of a
byte-copying instruction is byte_copy_right ? I would assume it is not
byte_copy_left. Am I right ?

Thanks in advance.
Stefan

--
Mit freundlichen Gr=FCssen         Phone: +49 30 34637141
Stefan Foeckel                   Fax  : +49 30 34638141
http://www.fokus.fraunhofer.de   ICQ  : 46655019


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



