From mailman-owner@ietf.org  Sat Jun  1 06:09:49 2002
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 GAA15236
	for <rohc-archive@odin.ietf.org>; Sat, 1 Jun 2002 06:09:49 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA15497
	for <rohc-web-archive@ietf.org>; Sat, 1 Jun 2002 06:10:15 -0400 (EDT)
Date: Sat, 1 Jun 2002 06:10:15 -0400 (EDT)
Message-Id: <200206011010.GAA15497@optimus.ietf.org>
From: mailman-owner@ietf.org
Subject: ietf.org mailing list memberships reminder
To: rohc-web-archive@ietf.org
X-No-Archive: yes
Precedence: bulk
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Session Initiation Protocol <sip.ietf.org>

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

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

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

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

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

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


From rohc-admin@ietf.org  Mon Jun  3 01:10:30 2002
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 BAA25248
	for <rohc-archive@odin.ietf.org>; Mon, 3 Jun 2002 01:10:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA10360;
	Mon, 3 Jun 2002 01:08:38 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA10331
	for <rohc@optimus.ietf.org>; Mon, 3 Jun 2002 01:08:31 -0400 (EDT)
Received: from cwcsun41.cwc.nus.edu.sg (cwcsun41.cwc.nus.edu.sg [137.132.163.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25207
	for <rohc@ietf.org>; Mon, 3 Jun 2002 01:07:51 -0400 (EDT)
Received: from swl8273001774 ([172.16.3.158])
	by cwcsun41.cwc.nus.edu.sg (8.9.3/8.9.3) with SMTP id NAA20645
	for <rohc@ietf.org>; Mon, 3 Jun 2002 13:06:42 +0800 (SGT)
Message-ID: <000901c20abc$9ff0c100$9e0310ac@swl8273001774>
From: "Wang Haiguang" <wanghg@cwc.nus.edu.sg>
To: <rohc@ietf.org>
References: <20020531180223.C34F2B049A@mother.bln.acticom.de>
Subject: Re: [rohc] W-LSB encoding problem
Date: Mon, 3 Jun 2002 13:07:55 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org
Content-Transfer-Encoding: 7bit

Hi, Stefan.

Based on my understanding.

In my view, half of the range as the upper boundary of window width is not
safe.

For example, in a range of [0, 65535], assume you have following numbers in
your

window [29000, 60000, 50000], assume v = 19000.

60000 - 29000 = 31000 < 32767

In such case, k = 15.

If the decompressor using 50000 as reference, it will get 51768 instead of
19000.

I think the upper boundary of the window width should be 8192 in such a
case.

That means, when your window width is greater than 8192, you may got a wrong
value.

Welcome for the comments.

Best regards.

Haiguang





----- Original Message -----
From: "Stefan Hendrata" <hendrata@acticom.de>
To: <rohc@ietf.org>
Sent: Saturday, June 01, 2002 2:02 AM
Subject: Re: [rohc] W-LSB encoding problem


> Hello,
>
> your analysis looks correct.
>
> Actually, I also got some other responses telling me to use uncompressed
> IP-ID transmission in such a case. In fact I wasn't using fully randomized
> sequences but sequences that contain a random change after a number of
> uniform increments and I was thinking that the W-LSB compression would be
> "robust" enough to deal with such random changes.
>
> After discussing this issue with a colleague and thinking about it, I came
to
> the following conclusion:
>
> Remember that the sliding window contains all reference values that the
> decompressor could possibly use, and the compressor is looking for the
> reference value yielding the greatest number k of bits. Thus, using v_min
and
> v_max of a sliding window to determine the greatest number k of bits
needed
> to be transmitted works only if v_min and v_max have the minimum and
maximum
> distances to v compared with all values in the sliding window.
>
> Taking wrap-around arithmetic into account, this is only true as long as
> v_max - v_min remains smaller than the half of the range of values. If
v_max
> - v_min becomes larger, it is no longer assured that v_min and v_max have
the
> minimum and maximum distances to v (as can be seen in the example given in
my
> first posting),
>
> Thus, a simple and effective solution to my problem was:
> - If the width of the sliding window is smaller than the half of the range
of
> values, use the algorithm as described in the RFC to determine the number
k
> of bits.
> - If the width of the sliding window is equal or larger than the half of
the
> range of values, transmit all bits.
>
> This one-line-workaround made our W-LSB encoder "robust" to deal with
random
> changes.
>
> I understand that the RFC contains statements regarding the limitation of
the
> maximum width of the sliding window for U- and O-mode. So this issue may
be
> of no practical relevance but it is theoretically interesting though.
>
> Stefan Hendrata
>
>
>
> On Wednesday 29 May 2002 07:25, you wrote:
> > Hi.
> >
> > Following is based on my understanding.
> > I think the main reason is because the interpretation interval function
in
> > ROHC didn't consider the random change in numbers.
> >
> > Let's assume rule d) proposed in rfc3095 page 26 is used by both
compressor
> > and decompressor. That is:
> > f(v_ref, k) = [v_ref - 2^(k-2) + 1, v_ref + 2^(k-2) *3].
> > We also assume the maximum number is 65535 (two bytes integer)
> >
> > For your case, the window has three values (100, 60000, 50000), thus the
> > v_min = 100,
> > v_max = 60000, v = 2000.
> >
> > k1 = g(v_min, v) = g(100, 2000) = 12.
> > k2 = g(v_max, v) = g(60000, 2000) = 14;
> >
> > Thus k = max(k1, k2) = 14.
> >
> > The bits carried in header will be 00 0111 1101 0000.
> > The decompressor interprates the value by replace the lower 14 bits of
> > 50000 (1100 0011 0101 0000) by the above bits string and get 1100 0111
1101
> > 0000 = 51152.
> >
> > The reason is becuause the 50000 jumps back too much in the current rule
d)
> > and cause the value 2000 out of the intersection of the interpretation
> > interval of the 50000 and 60000.
> > Interpretation interval for 50000 : [45905, 62288]
> > Interpretation interval for 60000 : [55905, 6752]
> >
> > The lower boundry you can jump back is 55248, that means if the third
value
> > in the window is less than 55248, you may get 51152. If it is greater
than
> > or equal 55248, you will get the
> > right value, 2000.
> >
> > So, if you want to send random values, you'd better send all the bits
> > instead of using W-LSB, for example, the IP_ID filed in the IPV4 header,
> > when rnd is on, it is send without
> > compression.
> >
> > If anything wrong in my analysis, please point it out. Let's understand
it
> > together.
> >
> > Best regards.
> >
> > Haiguang
> >
> >
> > ----- Original Message -----
> > From: "Stefan Hendrata" <hendrata@acticom.de>
> > To: <rohc@ietf.org>
> > Sent: Tuesday, May 28, 2002 10:27 PM
> > Subject: [rohc] W-LSB encoding problem
> >
> > > Hello,
> > >
> > > My company is also working on a ROHC implementation and I've come
across
> > > a problem with the W-LSB encoding scheme for which I don't have an
> >
> > explanation
> >
> > > yet:
> > >
> > > I have feeded our W-LSB encoder/decoder with sequences of numbers
> >
> > containing
> >
> > > both uniform increments and random changes for testing. This brought
me
> > > to
> >
> > a
> >
> > > problem of incorrect encoding and decoding, and I don't know if the
error
> > > lies within our understanding of W-LSB encoding/decoding or if it's
> > > within the scheme itself.
> > >
> > > To come straight to the problem, please look at the following sample
> >
> > sequence:
> > > 100
> > > 60000
> > > 50000
> > > 2000
> > >
> > > After encoding and decoding the first three numbers, the W-LSB encoder
> > > has
> >
> > a
> >
> > > v_min of 100 and a v_max of 60000. v_ref of the W-LSB decoder has the
> >
> > value
> >
> > > 50000. Now, for encoding and decoding the fourth value v=2000, the
> > > encoder takes v_min and v_max to calculate the number k of bits
needed.
> > > If the decoder gets these k bits and decodes them, it yields a value
of
> > > 51152
> >
> > which
> >
> > > is of course unequal to 2000. Apparently, the number of bits k is not
> > > high enough, but k results from v_min and v_max which are closer to
the
> > > wrongly decoded value (wrap-around view) than the decoder's v_ref.
> > >
> > > So, the simple question is: What's wrong here?
> > >
> > >
> > > Thank you,
> > > Stefan Hendrata
> > > acticom GmbH, Germany
> > >
> > >
> > > _______________________________________________
> > > 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
>


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


From rohc-admin@ietf.org  Mon Jun  3 18:47:28 2002
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 SAA03351
	for <rohc-archive@odin.ietf.org>; Mon, 3 Jun 2002 18:47:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA06172;
	Mon, 3 Jun 2002 18:46:20 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA06143
	for <rohc@ns.ietf.org>; Mon, 3 Jun 2002 18:46:18 -0400 (EDT)
Received: from rsys000a.roke.co.uk (rsys000a.roke.co.uk [193.118.201.102])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA03327
	for <rohc@ietf.org>; Mon, 3 Jun 2002 18:45:47 -0400 (EDT)
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <LBMM31K7>; Mon, 3 Jun 2002 23:43:56 +0100
Received: from roke.co.uk (ras_fennel2.roke.co.uk [193.118.206.44]) by rsys002a.roke.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id KYV8Q477; Mon, 3 Jun 2002 23:43:49 +0100
From: "West, Mark (ITN)" <mark.a.west@roke.co.uk>
To: "Peter Kremer (ETH)" <Peter.Kremer@eth.ericsson.se>
Cc: "'rohc@ietf.org'" <rohc@ietf.org>,
        "Lars-Erik Jonsson (EPL)"
	 <Lars-Erik.Jonsson@epl.ericsson.se>
Message-ID: <3CFBEC34.2080206@roke.co.uk>
Date: Mon, 03 Jun 2002 23:22:44 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
Subject: Re: [rohc] RE: Clarifications for the Implementer's guide
References: <F005CD411D18D3119C8F00508B087480085435EF@ehubunt100.eth.ericsson.se>
Content-Type: multipart/mixed;
	boundary="------------InterScan_NT_MIME_Boundary"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org


This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Hi Peter, Lars-Erik,

The text on feedback links sounds quite reasonable.

 >
 >> 2) What does "presumed zero if absent" mean on page 88? The Arctic
 >>  ROHC participants agreed that c) seemed to be the  reasonable 
assumption,
 >>  which could be noted in chapter 4 of the  Implementer's guide.
 >>
 >>
 >
 > My proposed text is:
 >
 > "4.X.  What does "presumed zero if absent" mean on page 88?
 >
 > On page 88, RFC 3095 says that R-P contains the absolute value of
 > RTP Padding bit and it's presumed zero if absent.  It could be
 > absent from RTP header flags and fields, from the extension type 3
 > or from the ROHC packet. It's been agreed that the first case is
 > the most probable."
 >
 >

Simply on the basis of interoperability, we need to define what the 
assumed behaviour is going to be.  That is, not only should we say that 
the 'first case is the most probable', but we should state that "the RTP 
padding bit is presumed zero if absent from the RTP header flags."

(If, indeed, that's what we believe!)

Cheers,

Mark.

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

(Yes, I do know that my disclaimer is in an attachment.  And, no, I
didn't ask for it to be that way)


--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain;
	name="RMRL-Disclaimer.txt"
Content-Disposition: attachment;
	filename="RMRL-Disclaimer.txt"
Content-Transfer-Encoding: 7bit

The information contained in this e-mail and any attachments is confidential to Roke 
Manor Research Ltd and must not be passed to any third party without permission. This 
communication is for information only and shall not create or change any contractual 
relationship.

--------------InterScan_NT_MIME_Boundary--

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


From rohc-admin@ietf.org  Mon Jun  3 19:30:48 2002
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 TAA04127
	for <rohc-archive@odin.ietf.org>; Mon, 3 Jun 2002 19:30:47 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA08267;
	Mon, 3 Jun 2002 19:17:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA08236
	for <rohc@ns.ietf.org>; Mon, 3 Jun 2002 19:17:29 -0400 (EDT)
Received: from rsys000a.roke.co.uk (rsys000a.roke.co.uk [193.118.201.102])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA03922
	for <rohc@ietf.org>; Mon, 3 Jun 2002 19:16:58 -0400 (EDT)
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <LBMM31MS>; Tue, 4 Jun 2002 00:15:06 +0100
Received: from roke.co.uk (ras_fennel3.roke.co.uk [193.118.206.45]) by rsys002a.roke.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id KYV8Q483; Tue, 4 Jun 2002 00:14:56 +0100
From: "West, Mark (ITN)" <mark.a.west@roke.co.uk>
To: Wang Haiguang <wanghg@cwc.nus.edu.sg>
Cc: rohc@ietf.org
Message-ID: <3CFBF7AD.3050201@roke.co.uk>
Date: Tue, 04 Jun 2002 00:11:41 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
Subject: Re: [rohc] W-LSB encoding problem
References: <20020531180223.C34F2B049A@mother.bln.acticom.de> <000901c20abc$9ff0c100$9e0310ac@swl8273001774>
Content-Type: multipart/mixed;
	boundary="------------InterScan_NT_MIME_Boundary"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org


This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit


I'm doubtless missing something blindingly obvious, but...

Given:

 > window [29000, 60000, 50000], assume v = 19000.

[I'll also point out that you aren't quoting a value for 'p' in this 
case, so we can't be sure what the interpretation interval is.  But I'll 
assume that p = 0, for now...]

The possible values of v_ref are 29000, 60000 and 50000.  With modular 
arithmetic, the difference between a v of 19000 and a v_ref of 29000 is 
55536, which (with p = 0) is going to lead to k being the full 16 bits, 
isn't it?

Cheers,

Mark.



Wang Haiguang wrote:

> Hi, Stefan.
> 
> Based on my understanding.
> 
> In my view, half of the range as the upper boundary of window width is not
> safe.
> 
> For example, in a range of [0, 65535], assume you have following numbers in
> your
> 
> window [29000, 60000, 50000], assume v = 19000.
> 
> 60000 - 29000 = 31000 < 32767
> 
> In such case, k = 15.
> 
> If the decompressor using 50000 as reference, it will get 51768 instead of
> 19000.
> 
> I think the upper boundary of the window width should be 8192 in such a
> case.
> 
> That means, when your window width is greater than 8192, you may got a wrong
> value.
> 
> Welcome for the comments.
> 
> Best regards.
> 
> Haiguang
> 
> 
> 
> 
> 
> ----- Original Message -----
> From: "Stefan Hendrata" <hendrata@acticom.de>
> To: <rohc@ietf.org>
> Sent: Saturday, June 01, 2002 2:02 AM
> Subject: Re: [rohc] W-LSB encoding problem
> 
> 
> 
>>Hello,
>>
>>your analysis looks correct.
>>
>>Actually, I also got some other responses telling me to use uncompressed
>>IP-ID transmission in such a case. In fact I wasn't using fully randomized
>>sequences but sequences that contain a random change after a number of
>>uniform increments and I was thinking that the W-LSB compression would be
>>"robust" enough to deal with such random changes.
>>
>>After discussing this issue with a colleague and thinking about it, I came
>>
> to
> 
>>the following conclusion:
>>
>>Remember that the sliding window contains all reference values that the
>>decompressor could possibly use, and the compressor is looking for the
>>reference value yielding the greatest number k of bits. Thus, using v_min
>>
> and
> 
>>v_max of a sliding window to determine the greatest number k of bits
>>
> needed
> 
>>to be transmitted works only if v_min and v_max have the minimum and
>>
> maximum
> 
>>distances to v compared with all values in the sliding window.
>>
>>Taking wrap-around arithmetic into account, this is only true as long as
>>v_max - v_min remains smaller than the half of the range of values. If
>>
> v_max
> 
>>- v_min becomes larger, it is no longer assured that v_min and v_max have
>>
> the
> 
>>minimum and maximum distances to v (as can be seen in the example given in
>>
> my
> 
>>first posting),
>>
>>Thus, a simple and effective solution to my problem was:
>>- If the width of the sliding window is smaller than the half of the range
>>
> of
> 
>>values, use the algorithm as described in the RFC to determine the number
>>
> k
> 
>>of bits.
>>- If the width of the sliding window is equal or larger than the half of
>>
> the
> 
>>range of values, transmit all bits.
>>
>>This one-line-workaround made our W-LSB encoder "robust" to deal with
>>
> random
> 
>>changes.
>>
>>I understand that the RFC contains statements regarding the limitation of
>>
> the
> 
>>maximum width of the sliding window for U- and O-mode. So this issue may
>>
> be
> 
>>of no practical relevance but it is theoretically interesting though.
>>
>>Stefan Hendrata
>>
>>
>>
>>On Wednesday 29 May 2002 07:25, you wrote:
>>
>>>Hi.
>>>
>>>Following is based on my understanding.
>>>I think the main reason is because the interpretation interval function
>>>
> in
> 
>>>ROHC didn't consider the random change in numbers.
>>>
>>>Let's assume rule d) proposed in rfc3095 page 26 is used by both
>>>
> compressor
> 
>>>and decompressor. That is:
>>>f(v_ref, k) = [v_ref - 2^(k-2) + 1, v_ref + 2^(k-2) *3].
>>>We also assume the maximum number is 65535 (two bytes integer)
>>>
>>>For your case, the window has three values (100, 60000, 50000), thus the
>>>v_min = 100,
>>>v_max = 60000, v = 2000.
>>>
>>>k1 = g(v_min, v) = g(100, 2000) = 12.
>>>k2 = g(v_max, v) = g(60000, 2000) = 14;
>>>
>>>Thus k = max(k1, k2) = 14.
>>>
>>>The bits carried in header will be 00 0111 1101 0000.
>>>The decompressor interprates the value by replace the lower 14 bits of
>>>50000 (1100 0011 0101 0000) by the above bits string and get 1100 0111
>>>
> 1101
> 
>>>0000 = 51152.
>>>
>>>The reason is becuause the 50000 jumps back too much in the current rule
>>>
> d)
> 
>>>and cause the value 2000 out of the intersection of the interpretation
>>>interval of the 50000 and 60000.
>>>Interpretation interval for 50000 : [45905, 62288]
>>>Interpretation interval for 60000 : [55905, 6752]
>>>
>>>The lower boundry you can jump back is 55248, that means if the third
>>>
> value
> 
>>>in the window is less than 55248, you may get 51152. If it is greater
>>>
> than
> 
>>>or equal 55248, you will get the
>>>right value, 2000.
>>>
>>>So, if you want to send random values, you'd better send all the bits
>>>instead of using W-LSB, for example, the IP_ID filed in the IPV4 header,
>>>when rnd is on, it is send without
>>>compression.
>>>
>>>If anything wrong in my analysis, please point it out. Let's understand
>>>
> it
> 
>>>together.
>>>
>>>Best regards.
>>>
>>>Haiguang
>>>
>>>
>>>----- Original Message -----
>>>From: "Stefan Hendrata" <hendrata@acticom.de>
>>>To: <rohc@ietf.org>
>>>Sent: Tuesday, May 28, 2002 10:27 PM
>>>Subject: [rohc] W-LSB encoding problem
>>>
>>>
>>>>Hello,
>>>>
>>>>My company is also working on a ROHC implementation and I've come
>>>>
> across
> 
>>>>a problem with the W-LSB encoding scheme for which I don't have an
>>>>
>>>explanation
>>>
>>>
>>>>yet:
>>>>
>>>>I have feeded our W-LSB encoder/decoder with sequences of numbers
>>>>
>>>containing
>>>
>>>
>>>>both uniform increments and random changes for testing. This brought
>>>>
> me
> 
>>>>to
>>>>
>>>a
>>>
>>>
>>>>problem of incorrect encoding and decoding, and I don't know if the
>>>>
> error
> 
>>>>lies within our understanding of W-LSB encoding/decoding or if it's
>>>>within the scheme itself.
>>>>
>>>>To come straight to the problem, please look at the following sample
>>>>
>>>sequence:
>>>
>>>>100
>>>>60000
>>>>50000
>>>>2000
>>>>
>>>>After encoding and decoding the first three numbers, the W-LSB encoder
>>>>has
>>>>
>>>a
>>>
>>>
>>>>v_min of 100 and a v_max of 60000. v_ref of the W-LSB decoder has the
>>>>
>>>value
>>>
>>>
>>>>50000. Now, for encoding and decoding the fourth value v=2000, the
>>>>encoder takes v_min and v_max to calculate the number k of bits
>>>>
> needed.
> 
>>>>If the decoder gets these k bits and decodes them, it yields a value
>>>>
> of
> 
>>>>51152
>>>>
>>>which
>>>
>>>
>>>>is of course unequal to 2000. Apparently, the number of bits k is not
>>>>high enough, but k results from v_min and v_max which are closer to
>>>>
> the
> 
>>>>wrongly decoded value (wrap-around view) than the decoder's v_ref.
>>>>
>>>>So, the simple question is: What's wrong here?
>>>>
>>>>
>>>>Thank you,
>>>>Stefan Hendrata
>>>>acticom GmbH, Germany
>>>>
>>>>
>>>>_______________________________________________
>>>>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
>>
>>
> 
> 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
> 


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

(Yes, I do know that my disclaimer is in an attachment.  And, no, I 
didn't ask for it to be that way)


--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain;
	name="RMRL-Disclaimer.txt"
Content-Disposition: attachment;
	filename="RMRL-Disclaimer.txt"
Content-Transfer-Encoding: 7bit

The information contained in this e-mail and any attachments is confidential to Roke 
Manor Research Ltd and must not be passed to any third party without permission. This 
communication is for information only and shall not create or change any contractual 
relationship.

--------------InterScan_NT_MIME_Boundary--

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


From rohc-admin@ietf.org  Mon Jun  3 21:40:36 2002
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 VAA05742
	for <rohc-archive@odin.ietf.org>; Mon, 3 Jun 2002 21:40:36 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA14384;
	Mon, 3 Jun 2002 21:39:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA14353
	for <rohc@ns.ietf.org>; Mon, 3 Jun 2002 21:39:39 -0400 (EDT)
Received: from cwcsun41.cwc.nus.edu.sg (cwcsun41.cwc.nus.edu.sg [137.132.163.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05637
	for <rohc@ietf.org>; Mon, 3 Jun 2002 21:39:07 -0400 (EDT)
Received: from localhost (wanghg@localhost)
	by cwcsun41.cwc.nus.edu.sg (8.9.3/8.9.3) with ESMTP id JAA03373;
	Tue, 4 Jun 2002 09:38:19 +0800 (SGT)
Date: Tue, 4 Jun 2002 09:38:19 +0800 (SGT)
From: Wang Hai Guang <wanghg@cwcsun41.cwc.nus.edu.sg>
To: "West, Mark (ITN)" <mark.a.west@roke.co.uk>
cc: rohc@ietf.org
Subject: Re: [rohc] W-LSB encoding problem
In-Reply-To: <3CFBF7AD.3050201@roke.co.uk>
Message-ID: <Pine.GSO.4.10.10206040916590.461-100000@cwcsun41>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org


 I assume p = 2^(k-2) - 1.

 Because the number may change randomly, so I didn't add the

65536 when wraparound happens. I think I should add it.

Thanks Mark for the comments.

Best regards.

Haiguang



On Tue, 4 Jun 2002, West, Mark (ITN) wrote:

> 
> I'm doubtless missing something blindingly obvious, but...
> 
> Given:
> 
>  > window [29000, 60000, 50000], assume v = 19000.
> 
> [I'll also point out that you aren't quoting a value for 'p' in this 
> case, so we can't be sure what the interpretation interval is.  But I'll 
> assume that p = 0, for now...]
> 
> The possible values of v_ref are 29000, 60000 and 50000.  With modular 
> arithmetic, the difference between a v of 19000 and a v_ref of 29000 is 
> 55536, which (with p = 0) is going to lead to k being the full 16 bits, 
> isn't it?
> 
> Cheers,
> 
> Mark.
> 
> 
> 
> Wang Haiguang wrote:
> 
> > Hi, Stefan.
> > 
> > Based on my understanding.
> > 
> > In my view, half of the range as the upper boundary of window width is not
> > safe.
> > 
> > For example, in a range of [0, 65535], assume you have following numbers in
> > your
> > 
> > window [29000, 60000, 50000], assume v = 19000.
> > 
> > 60000 - 29000 = 31000 < 32767
> > 
> > In such case, k = 15.
> > 
> > If the decompressor using 50000 as reference, it will get 51768 instead of
> > 19000.
> > 
> > I think the upper boundary of the window width should be 8192 in such a
> > case.
> > 
> > That means, when your window width is greater than 8192, you may got a wrong
> > value.
> > 
> > Welcome for the comments.
> > 
> > Best regards.
> > 
> > Haiguang
> > 
> > 
> > 
> > 
> > 
> > ----- Original Message -----
> > From: "Stefan Hendrata" <hendrata@acticom.de>
> > To: <rohc@ietf.org>
> > Sent: Saturday, June 01, 2002 2:02 AM
> > Subject: Re: [rohc] W-LSB encoding problem
> > 
> > 
> > 
> >>Hello,
> >>
> >>your analysis looks correct.
> >>
> >>Actually, I also got some other responses telling me to use uncompressed
> >>IP-ID transmission in such a case. In fact I wasn't using fully randomized
> >>sequences but sequences that contain a random change after a number of
> >>uniform increments and I was thinking that the W-LSB compression would be
> >>"robust" enough to deal with such random changes.
> >>
> >>After discussing this issue with a colleague and thinking about it, I came
> >>
> > to
> > 
> >>the following conclusion:
> >>
> >>Remember that the sliding window contains all reference values that the
> >>decompressor could possibly use, and the compressor is looking for the
> >>reference value yielding the greatest number k of bits. Thus, using v_min
> >>
> > and
> > 
> >>v_max of a sliding window to determine the greatest number k of bits
> >>
> > needed
> > 
> >>to be transmitted works only if v_min and v_max have the minimum and
> >>
> > maximum
> > 
> >>distances to v compared with all values in the sliding window.
> >>
> >>Taking wrap-around arithmetic into account, this is only true as long as
> >>v_max - v_min remains smaller than the half of the range of values. If
> >>
> > v_max
> > 
> >>- v_min becomes larger, it is no longer assured that v_min and v_max have
> >>
> > the
> > 
> >>minimum and maximum distances to v (as can be seen in the example given in
> >>
> > my
> > 
> >>first posting),
> >>
> >>Thus, a simple and effective solution to my problem was:
> >>- If the width of the sliding window is smaller than the half of the range
> >>
> > of
> > 
> >>values, use the algorithm as described in the RFC to determine the number
> >>
> > k
> > 
> >>of bits.
> >>- If the width of the sliding window is equal or larger than the half of
> >>
> > the
> > 
> >>range of values, transmit all bits.
> >>
> >>This one-line-workaround made our W-LSB encoder "robust" to deal with
> >>
> > random
> > 
> >>changes.
> >>
> >>I understand that the RFC contains statements regarding the limitation of
> >>
> > the
> > 
> >>maximum width of the sliding window for U- and O-mode. So this issue may
> >>
> > be
> > 
> >>of no practical relevance but it is theoretically interesting though.
> >>
> >>Stefan Hendrata
> >>
> >>
> >>
> >>On Wednesday 29 May 2002 07:25, you wrote:
> >>
> >>>Hi.
> >>>
> >>>Following is based on my understanding.
> >>>I think the main reason is because the interpretation interval function
> >>>
> > in
> > 
> >>>ROHC didn't consider the random change in numbers.
> >>>
> >>>Let's assume rule d) proposed in rfc3095 page 26 is used by both
> >>>
> > compressor
> > 
> >>>and decompressor. That is:
> >>>f(v_ref, k) = [v_ref - 2^(k-2) + 1, v_ref + 2^(k-2) *3].
> >>>We also assume the maximum number is 65535 (two bytes integer)
> >>>
> >>>For your case, the window has three values (100, 60000, 50000), thus the
> >>>v_min = 100,
> >>>v_max = 60000, v = 2000.
> >>>
> >>>k1 = g(v_min, v) = g(100, 2000) = 12.
> >>>k2 = g(v_max, v) = g(60000, 2000) = 14;
> >>>
> >>>Thus k = max(k1, k2) = 14.
> >>>
> >>>The bits carried in header will be 00 0111 1101 0000.
> >>>The decompressor interprates the value by replace the lower 14 bits of
> >>>50000 (1100 0011 0101 0000) by the above bits string and get 1100 0111
> >>>
> > 1101
> > 
> >>>0000 = 51152.
> >>>
> >>>The reason is becuause the 50000 jumps back too much in the current rule
> >>>
> > d)
> > 
> >>>and cause the value 2000 out of the intersection of the interpretation
> >>>interval of the 50000 and 60000.
> >>>Interpretation interval for 50000 : [45905, 62288]
> >>>Interpretation interval for 60000 : [55905, 6752]
> >>>
> >>>The lower boundry you can jump back is 55248, that means if the third
> >>>
> > value
> > 
> >>>in the window is less than 55248, you may get 51152. If it is greater
> >>>
> > than
> > 
> >>>or equal 55248, you will get the
> >>>right value, 2000.
> >>>
> >>>So, if you want to send random values, you'd better send all the bits
> >>>instead of using W-LSB, for example, the IP_ID filed in the IPV4 header,
> >>>when rnd is on, it is send without
> >>>compression.
> >>>
> >>>If anything wrong in my analysis, please point it out. Let's understand
> >>>
> > it
> > 
> >>>together.
> >>>
> >>>Best regards.
> >>>
> >>>Haiguang
> >>>
> >>>
> >>>----- Original Message -----
> >>>From: "Stefan Hendrata" <hendrata@acticom.de>
> >>>To: <rohc@ietf.org>
> >>>Sent: Tuesday, May 28, 2002 10:27 PM
> >>>Subject: [rohc] W-LSB encoding problem
> >>>
> >>>
> >>>>Hello,
> >>>>
> >>>>My company is also working on a ROHC implementation and I've come
> >>>>
> > across
> > 
> >>>>a problem with the W-LSB encoding scheme for which I don't have an
> >>>>
> >>>explanation
> >>>
> >>>
> >>>>yet:
> >>>>
> >>>>I have feeded our W-LSB encoder/decoder with sequences of numbers
> >>>>
> >>>containing
> >>>
> >>>
> >>>>both uniform increments and random changes for testing. This brought
> >>>>
> > me
> > 
> >>>>to
> >>>>
> >>>a
> >>>
> >>>
> >>>>problem of incorrect encoding and decoding, and I don't know if the
> >>>>
> > error
> > 
> >>>>lies within our understanding of W-LSB encoding/decoding or if it's
> >>>>within the scheme itself.
> >>>>
> >>>>To come straight to the problem, please look at the following sample
> >>>>
> >>>sequence:
> >>>
> >>>>100
> >>>>60000
> >>>>50000
> >>>>2000
> >>>>
> >>>>After encoding and decoding the first three numbers, the W-LSB encoder
> >>>>has
> >>>>
> >>>a
> >>>
> >>>
> >>>>v_min of 100 and a v_max of 60000. v_ref of the W-LSB decoder has the
> >>>>
> >>>value
> >>>
> >>>
> >>>>50000. Now, for encoding and decoding the fourth value v=2000, the
> >>>>encoder takes v_min and v_max to calculate the number k of bits
> >>>>
> > needed.
> > 
> >>>>If the decoder gets these k bits and decodes them, it yields a value
> >>>>
> > of
> > 
> >>>>51152
> >>>>
> >>>which
> >>>
> >>>
> >>>>is of course unequal to 2000. Apparently, the number of bits k is not
> >>>>high enough, but k results from v_min and v_max which are closer to
> >>>>
> > the
> > 
> >>>>wrongly decoded value (wrap-around view) than the decoder's v_ref.
> >>>>
> >>>>So, the simple question is: What's wrong here?
> >>>>
> >>>>
> >>>>Thank you,
> >>>>Stefan Hendrata
> >>>>acticom GmbH, Germany
> >>>>
> >>>>
> >>>>_______________________________________________
> >>>>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
> >>
> >>
> > 
> > 
> > _______________________________________________
> > Rohc mailing list
> > Rohc@ietf.org
> > https://www1.ietf.org/mailman/listinfo/rohc
> > 
> 
> 
> -- 
> Mark A. West, Consultant Engineer
> Roke Manor Research Ltd., Romsey, Hants.  SO51 0ZN
> Phone +44 (0)1794 833311   Fax  +44 (0)1794 833433
> 
> (Yes, I do know that my disclaimer is in an attachment.  And, no, I 
> didn't ask for it to be that way)
> 
> 


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


From rohc-admin@ietf.org  Tue Jun  4 07:46:15 2002
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 HAA23843
	for <rohc-archive@odin.ietf.org>; Tue, 4 Jun 2002 07:46:15 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA21623;
	Tue, 4 Jun 2002 07:45:07 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA21592
	for <rohc@optimus.ietf.org>; Tue, 4 Jun 2002 07:45:05 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23644;
	Tue, 4 Jun 2002 07:44:33 -0400 (EDT)
Message-Id: <200206041144.HAA23644@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: Tue, 04 Jun 2002 07:44:33 -0400
Subject: [rohc] I-D ACTION:draft-ietf-rohc-sigcomp-07.txt
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

--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		: Signaling Compression
	Author(s)	: R. Price et al.
	Filename	: draft-ietf-rohc-sigcomp-07.txt
	Pages		: 57
	Date		: 03-Jun-02
	
This document defines SigComp, a solution for compressing messages
generated by application protocols such as SIP [RFC-2543] and RTSP
[RFC-2326]. The architecture and pre-requisites of SigComp are
outlined, along with the format of the SigComp message.
Decompression functionality for SigComp is provided by a 'Universal
Decompressor Virtual Machine' optimized for the task of running
decompression algorithms. The UDVM can be configured to understand
the output of many well-known compressors such as DEFLATE [RFC-1951].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rohc-sigcomp-07.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-sigcomp-07.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-sigcomp-07.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:	<20020603130126.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rohc-sigcomp-07.txt

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

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

--OtherAccess--

--NextPart--



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


From rohc-admin@ietf.org  Tue Jun  4 07:46:16 2002
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 HAA23856
	for <rohc-archive@odin.ietf.org>; Tue, 4 Jun 2002 07:46:16 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA21704;
	Tue, 4 Jun 2002 07:45:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA21637
	for <rohc@optimus.ietf.org>; Tue, 4 Jun 2002 07:45:10 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23674;
	Tue, 4 Jun 2002 07:44:39 -0400 (EDT)
Message-Id: <200206041144.HAA23674@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: Tue, 04 Jun 2002 07:44:38 -0400
Subject: [rohc] I-D ACTION:draft-ietf-rohc-signaling-req-assump-06.txt
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

--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		: Signaling Compression Requirements & Assumptions
	Author(s)	: H. Hannu
	Filename	: draft-ietf-rohc-signaling-req-assump-06.txt
	Pages		: 11
	Date		: 03-Jun-02
	
In wireless environments and especially in cellular systems, e.g. GSM
(Global System for Mobile communications) and UMTS (Universal Mobile
Telecommunications System), there is a need to maximize the transport
efficiency for data over the radio interface. With the introduction
of SIP/SDP (Session Initiation Protocol/Session Description Protocol)
to cellular devices, compression of the signaling messages should be
considered in order to improve both service availability and quality,
mainly by reducing the user idle time, e.g. at call setup. The
purpose of this document is to outline requirements and motivations
for development of a scheme for compression and decompression of
messages from signaling protocols.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rohc-signaling-req-assump-06.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-signaling-req-assump-06.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-signaling-req-assump-06.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:	<20020603130137.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rohc-signaling-req-assump-06.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rohc-signaling-req-assump-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--



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


From rohc-admin@ietf.org  Tue Jun  4 07:46:21 2002
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 HAA23870
	for <rohc-archive@odin.ietf.org>; Tue, 4 Jun 2002 07:46:21 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA21586;
	Tue, 4 Jun 2002 07:45:02 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA21555
	for <rohc@optimus.ietf.org>; Tue, 4 Jun 2002 07:45:00 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23626;
	Tue, 4 Jun 2002 07:44:29 -0400 (EDT)
Message-Id: <200206041144.HAA23626@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: Tue, 04 Jun 2002 07:44:29 -0400
Subject: [rohc] I-D ACTION:draft-ietf-rohc-sigcomp-extended-04.txt
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

--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		: SigComp - Extended Operations
	Author(s)	: H. Hannu et al.
	Filename	: draft-ietf-rohc-sigcomp-extended-04.txt
	Pages		: 16
	Date		: 03-Jun-02
	
This document describes how to implement certain mechanisms in
SigComp (Signaling Compression), RFC XXX, which can significantly
improve the compression efficiency compared to using simple per-
message compression.
SigComp uses a UDVM (Universal Decompressor Virtual Machine) for
decompression, and the mechanisms described in this document are
possible to implement using the UDVM instructions defined in RFC XXX.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rohc-sigcomp-extended-04.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-sigcomp-extended-04.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-sigcomp-extended-04.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:	<20020603130115.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rohc-sigcomp-extended-04.txt

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

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

--OtherAccess--

--NextPart--



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


From rohc-admin@ietf.org  Tue Jun  4 07:46:31 2002
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 HAA23885
	for <rohc-archive@odin.ietf.org>; Tue, 4 Jun 2002 07:46:31 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA21873;
	Tue, 4 Jun 2002 07:45:30 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA21763
	for <rohc@optimus.ietf.org>; Tue, 4 Jun 2002 07:45:22 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23710;
	Tue, 4 Jun 2002 07:44:50 -0400 (EDT)
Message-Id: <200206041144.HAA23710@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sipping@ietf.org, mmusic@ietf.org, rohc@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 04 Jun 2002 07:44:49 -0400
Subject: [rohc] I-D ACTION:draft-ietf-sipping-sigcomp-sip-dictionary-02.txt
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Proposal Investigation Working Group of the IETF.

	Title		: The Session Initiation Protocol (SIP) and Session 
                          Description Protocol (SDP) static dictionary for 
                          Signaling Compression (SigComp)
	Author(s)	: M. Garcia et al.
	Filename	: draft-ietf-sipping-sigcomp-sip-dictionary-02.txt
	Pages		: 29
	Date		: 03-Jun-02
	
The Session Initiation Protocol (SIP) [2] is a text-based protocol
for initiating and managing communication sessions. The protocol can
be compressed by using Signaling Compression (SigComp) [1].
Similarly, the Session Description Protocol (SDP) [24] is a text-
based protocol intended for describing multimedia sessions for the
purposes of session announcement, session invitation, and other forms
of multimedia session initiation. This memo defines the SIP/SDP-
specific static dictionary that SigComp may use in order to achieve
higher efficiency. The dictionary is compression algorithm
independent.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-sigcomp-sip-dictionary-02.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-sipping-sigcomp-sip-dictionary-02.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-sipping-sigcomp-sip-dictionary-02.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:	<20020603130157.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-sigcomp-sip-dictionary-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sipping-sigcomp-sip-dictionary-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--



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


From rohc-admin@ietf.org  Mon Jun 10 05:44:29 2002
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 FAA26592
	for <rohc-archive@odin.ietf.org>; Mon, 10 Jun 2002 05:44:24 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA19829;
	Mon, 10 Jun 2002 05:42:16 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA19798
	for <rohc@optimus.ietf.org>; Mon, 10 Jun 2002 05:42:15 -0400 (EDT)
Received: from rsys000a.roke.co.uk (rsys000a.roke.co.uk [193.118.201.102])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA26542
	for <rohc@ietf.org>; Mon, 10 Jun 2002 05:41:40 -0400 (EDT)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <KYV8Q6K3>; Mon, 10 Jun 2002 10:19:56 +0100
Message-ID: <76C92FBBFB58D411AE760090271ED41804B87F47@rsys002a.roke.co.uk>
From: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
To: "'Peter Kremer (ETH)'" <Peter.Kremer@eth.ericsson.se>,
        "'rohc@ietf.org'" <rohc@ietf.org>
Cc: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
Date: Mon, 10 Jun 2002 10:19:54 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="------------InterScan_NT_MIME_Boundary"
Subject: [rohc] RE: Clarifications for the Implementer's guide
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org


This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain;
	charset="iso-8859-1"

Hi,

>According to my notes I have a third issue, which is about the 
>id of CSRC lists.
>
>There can be an extension-3 in UO-1-ID packets with a 
>compressed CSRC list in "RTP header flags and fields". CSRC 
>list uses encoding type 0 (section 5.8.6.1, page 120) and 
>every list could have an id, which is present if a compressor 
>wants to use this list as a future reference.
>
>The problem is that the compressor intends to use this list in 
>the future but the context isn't updated (because it's a UO-1 packet).
>
>So what should a decompressor do if it receives such a packet 
>(UO-1-ID, ext-3, CSRC list with gen_id)? Should it save the 
>list because the compressor may use it in the future or should 
>it forget it after the decompression of the current packet 
>because the context isn't updated?
>
This is a good question.  The context management of CSRC lists seems to be completely separate from the main context management.  This question seems to encompass others. 

 From 5.8.2.1:

       In U/O-mode, curr_list is inserted into the sliding window
       together with its generation identifier if the compressed list had
       a generation identifier and the sliding window does not contain a
       list with that generation identifier.  All lists with generations
       older than ref_id are removed from the sliding window.

so the decompressor context management depends only on gen_id. 

The translation table however seems to be updated whatever happens - whether the packet is UO-1 or UO-2, whether there is a gen-id present or not.

 From 5.8.1:

    The decompressor conceptually maintains a table that contains all
    (Index, item) pairs it knows about.  The table is updated whenever an
    (Index, item) pair is received (and decompression is verified by a
    CRC).  The decompressor retrieves the item from the table whenever an
    Index without an accompanying item is received.

Should translation table entries sent in a UO-1-ID ext 3 count towards L (at the compressor)/update the table (at the decompressor) or not?

I think we decided in Arizona that sending a UO-1-ID with an ext-3 is a very strange thing to do but obviously the decompressor does have to be able to handle it.

>Abbey, did I missed something?
>

I think a second point of discussion was that of acknowledgements and CSRC lists.  In O-mode a compressor receiving an acknowledgement can stop sending gen-id's early as with acknowledgements of the main update packets.  However, the translation table in U/O mode stores only the number of times a particular entry has been sent (5.8.1.2) (whereas R mode stores the SNs so that entries can be acknowledged (5.8.1.1)).  This means that even if an entry is acknowledged the compressor will still send the full information because as far as the translation table is concerned the entry hasn't yet been sent enough times to be sure that the decompressor has it.

Regards,

Abbie

>-- 
>Peter Kremer, MBA                  Tel: +36-1-437-7033
>Ericsson Hungary Ltd.              Fax: +36-1-437-7767
>Conformance Center ETH/RL/S        Mobile: +36-30-311-2118
>http://conformancelab.ericsson.se  E-mail: Peter.Kremer@eth.ericsson.se
>

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain;
	name="RMRL-Disclaimer.txt"
Content-Disposition: attachment;
	filename="RMRL-Disclaimer.txt"
Content-Transfer-Encoding: 7bit

The information contained in this e-mail and any attachments is confidential to Roke 
Manor Research Ltd and must not be passed to any third party without permission. This 
communication is for information only and shall not create or change any contractual 
relationship.

--------------InterScan_NT_MIME_Boundary--

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


From rohc-admin@ietf.org  Wed Jun 12 07:16:03 2002
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 HAA23063
	for <rohc-archive@odin.ietf.org>; Wed, 12 Jun 2002 07:16:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18894;
	Wed, 12 Jun 2002 07:14:27 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18865
	for <rohc@optimus.ietf.org>; Wed, 12 Jun 2002 07:14:25 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22894;
	Wed, 12 Jun 2002 07:13:45 -0400 (EDT)
Message-Id: <200206121113.HAA22894@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: Wed, 12 Jun 2002 07:13:44 -0400
Subject: [rohc] I-D ACTION:draft-jonsson-rohc-ip-only-00.txt
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: RObust Header Compression (ROHC):A Compression Profile
                          for IP
	Author(s)	: L. Jonsson
	Filename	: draft-jonsson-rohc-ip-only-00.txt
	Pages		: 5
	Date		: 11-Jun-02
	
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 for uncompressed
packet streams. However, no profile was defined for compression of IP
only, which has been identified as a flaw in RFC 3095. This document
addresses that problem and defines a ROHC compression profile for IP,
similar to the IP/UDP profile defined by RFC 3095, but simplified to
exclude UDP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-jonsson-rohc-ip-only-00.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-jonsson-rohc-ip-only-00.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-jonsson-rohc-ip-only-00.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:	<20020611122823.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-jonsson-rohc-ip-only-00.txt

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

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

--OtherAccess--

--NextPart--



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


From rohc-admin@ietf.org  Wed Jun 12 08:09:28 2002
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 IAA24337
	for <rohc-archive@odin.ietf.org>; Wed, 12 Jun 2002 08:09:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21869;
	Wed, 12 Jun 2002 08:07:12 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21837
	for <rohc@optimus.ietf.org>; Wed, 12 Jun 2002 08:07:10 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24222
	for <rohc@ietf.org>; Wed, 12 Jun 2002 08:06:33 -0400 (EDT)
Received: from esealnt610.al.sw.ericsson.se (esealnt610.al.sw.ericsson.se [153.88.254.69])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g5CC77mG026024;
	Wed, 12 Jun 2002 14:07:08 +0200 (MEST)
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <M3J357JW>; Wed, 12 Jun 2002 14:07:07 +0200
Message-ID: <F005CD411D18D3119C8F00508B0874800854360E@ehubunt100.eth.ericsson.se>
From: "Peter Kremer (ETH)" <Peter.Kremer@eth.ericsson.se>
To: "'Surtees, Abigail'" <abigail.surtees@roke.co.uk>,
        "'rohc@ietf.org'"
	 <rohc@ietf.org>
Cc: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
Date: Wed, 12 Jun 2002 14:03:13 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [rohc] RE: Clarifications for the Implementer's guide
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

Hi,

Thanks for your reply, Abbey.

> This is a good question.  The context management of CSRC 
> lists seems to be completely separate from the main context 
> management.  This question seems to encompass others. 
> 
>  From 5.8.2.1:
> 
>        In U/O-mode, curr_list is inserted into the sliding window
>        together with its generation identifier if the 

I think you refer to a wrong section, 5.8.2.1 is about reference based compression, which differs from table-based compression. Anyway, I agree that Translation table management is different.

> Should translation table entries sent in a UO-1-ID ext 3 
> count towards L (at the compressor)/update the table (at the 
> decompressor) or not?

I think the answer is yes to both questions. The compressor has to increment Counter because of section 5.8.1.2 ("Counter is incremented by 1 whenever an (Index, item) pair is sent."). The decompessor also has to update the table in order to successfully decompress the packets.

> I think a second point of discussion was that of 
> acknowledgements and CSRC lists.  In O-mode a compressor 
> receiving an acknowledgement can stop sending gen-id's early 
> as with acknowledgements of the main update packets.  
> However, the translation table in U/O mode stores only the 
> number of times a particular entry has been sent (5.8.1.2) 
> (whereas R mode stores the SNs so that entries can be 
> acknowledged (5.8.1.1)).  This means that even if an entry is 
> acknowledged the compressor will still send the full 
> information because as far as the translation table is 
> concerned the entry hasn't yet been sent enough times to be 
> sure that the decompressor has it.

I'm afraid I don't understand it. RFC 3095, section 5.8.1 says that the compressor has to send the list until it gains enough confidence that the decompressor has learnt the mapping. It can be done by sending the list L times in U/O-mode and by receiving an acknowledgement in R-mode. But - as I remember - the compressor will never receive an acknowledgement in O-mode for type 0 and 1 packets because only STATIC-NACK or NACK can be sent, according to section 5.4.2.2 (Feedback logic in O-mode).

Best regards,
Peter

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


From rohc-admin@ietf.org  Wed Jun 12 19:50:57 2002
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 TAA16987
	for <rohc-archive@odin.ietf.org>; Wed, 12 Jun 2002 19:50:53 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA03499;
	Wed, 12 Jun 2002 19:23:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA03467
	for <rohc@optimus.ietf.org>; Wed, 12 Jun 2002 19:23:29 -0400 (EDT)
Received: from rsys000a.roke.co.uk (rsys000a.roke.co.uk [193.118.201.102])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA16563
	for <rohc@ietf.org>; Wed, 12 Jun 2002 19:22:50 -0400 (EDT)
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <LBMMPAZB>; Thu, 13 Jun 2002 00:21:04 +0100
Received: from roke.co.uk (ras_fennel2.roke.co.uk [193.118.206.44]) by rsys002a.roke.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id MWPNLD5P; Thu, 13 Jun 2002 00:21:00 +0100
From: "West, Mark (ITN)" <mark.a.west@roke.co.uk>
To: "Peter Kremer (ETH)" <Peter.Kremer@eth.ericsson.se>
Cc: "Surtees, Abigail" <abigail.surtees@roke.co.uk>,
        "'rohc@ietf.org'"
	 <rohc@ietf.org>,
        "Lars-Erik Jonsson (EPL)"
	 <Lars-Erik.Jonsson@epl.ericsson.se>
Message-ID: <3D07D19B.1040203@roke.co.uk>
Date: Wed, 12 Jun 2002 23:56:27 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
Subject: Re: [rohc] RE: Clarifications for the Implementer's guide
References: <F005CD411D18D3119C8F00508B0874800854360E@ehubunt100.eth.ericsson.se>
Content-Type: multipart/mixed;
	boundary="------------InterScan_NT_MIME_Boundary"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org


This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Hi Peter, all...

I think that there is one key question here, and a couple of others that 
fall out from that.

The main question relates to the fact that, currently, the 'context 
management' for list-based compression appears to be quite disassociated 
with the general ROHC context management.  So -- should they be 
separate, or not?

This gives rise to the original question that you posed: if a gen_id is 
quoted for a list in a UO-1 + Ext-3 packet, what happens?

(In fact, of course, we need to specify the decompressor behaviour.  Any 
compliant compressor then has to act in a manner consistent with this.)

I'll return to this question shortly!  But first...

The table-based compression also fits into this category.  This is the 
question that Abbie posed about whether updates sent in UO-1 + Ext-3 
packets count towards the value of 'L'.  Again, this is about whether 
such a packet is context updating.  According to the rules for UO-1 
packets, we should *not* update the context; but the table-based 
encoding description suggests that we *always* the table.

Ok, so, what does this mean?

Personally, I believe that the context data for list/table compression 
should be considered as part of the overall context.  Therefore, the 
overall context updating rules should apply.  (Partly this is because a 
list update can contain a lot of data, and in a UO-1 packet this is only 
protected with a 3-bit CRC).  So, I would suggest that any list encoding 
in a UO-1 packet (with Ext-3) is processed to decompress that header 
*but* does not create a new reference list (even if gen_id is given) and 
does not update any of the table references.

Finally, Abbie raised another (slightly disconnected) issue: that of 
acknowledgements of packets containing list/table compression data. 
(Clearly this does not apply in the case of UO-1 packets, since 
acknowledgements are not generated for these packets.  However, since I 
believe that these updates should probably be using UOR-2 packets, I 
think that this is a relevant issue!)
A UO-mode acknowledgment can short-circuit the sending of a list update 
multiple times.  However, it cannot prevent a table compression entry 
being sent 'L' times.  This just seems odd -- why can't an ack be used 
to indicate that a table entry has been accepted?
Unfortunately, this can't be changed without altering the data stored at 
the compressor for UO mode operation of table compression (since it is 
currently defined to only use a counter).

Hopefully this clarifies the questions (if not the answers ;-)

Mark.


 >
 >> This is a good question.  The context management of CSRC  lists
 >> seems to be completely separate from the main context  management.
 >>   This question seems to encompass others.
 >>
 >> From 5.8.2.1:
 >>
 >> In U/O-mode, curr_list is inserted into the sliding window together
 >>  with its generation identifier if the
 >>
 >
 > I think you refer to a wrong section, 5.8.2.1 is about reference
 > based compression, which differs from table-based compression.
 > Anyway, I agree that Translation table management is different.
 >
 >
 >> Should translation table entries sent in a UO-1-ID ext 3  count
 >> towards L (at the compressor)/update the table (at the  decompressor)
 >>  or not?
 >>
 >
 > I think the answer is yes to both questions. The compressor has to
 > increment Counter because of section 5.8.1.2 ("Counter is
 > incremented by 1 whenever an (Index, item) pair is sent."). The
 > decompessor also has to update the table in order to successfully
 > decompress the packets.
 >
 >
 >> I think a second point of discussion was that of  acknowledgements
 >>  and CSRC lists.  In O-mode a compressor  receiving an
 >> acknowledgement can stop sending gen-id's early  as with
 >> acknowledgements of the main update packets.   However, the
 >> translation table in U/O mode stores only the  number of times a
 >> particular entry has been sent (5.8.1.2)  (whereas R mode stores
 >> the SNs so that entries can be  acknowledged (5.8.1.1)).  This
 >> means that even if an entry is  acknowledged the compressor will
 >> still send the full  information because as far as the
 >> translation table is  concerned the entry hasn't yet been sent
 >> enough times to be  sure that the decompressor has it.
 >>
 >
 > I'm afraid I don't understand it. RFC 3095, section 5.8.1 says that
 > the compressor has to send the list until it gains enough
 > confidence that the decompressor has learnt the mapping. It can be
 > done by sending the list L times in U/O-mode and by receiving an
 > acknowledgement in R-mode. But - as I remember - the compressor
 > will never receive an acknowledgement in O-mode for type 0 and 1
 > packets because only STATIC-NACK or NACK can be sent, according to
 > section 5.4.2.2 (Feedback logic in O-mode).
 >
 > Best regards, Peter
 >
 > _______________________________________________ Rohc mailing list 
Rohc@ietf.org
 >

 > https://www1.ietf.org/mailman/listinfo/rohc
 >


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

(Yes, I do know that my disclaimer is in an attachment.  And, no, I
didn't ask for it to be that way)


--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain;
	name="RMRL-Disclaimer.txt"
Content-Disposition: attachment;
	filename="RMRL-Disclaimer.txt"
Content-Transfer-Encoding: 7bit

The information contained in this e-mail and any attachments is confidential to Roke 
Manor Research Ltd and must not be passed to any third party without permission. This 
communication is for information only and shall not create or change any contractual 
relationship.

--------------InterScan_NT_MIME_Boundary--

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


From rohc-admin@ietf.org  Thu Jun 13 08:52:51 2002
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 IAA10152
	for <rohc-archive@odin.ietf.org>; Thu, 13 Jun 2002 08:52:50 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA16568;
	Thu, 13 Jun 2002 08:50:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA16536
	for <rohc@ns.ietf.org>; Thu, 13 Jun 2002 08:50:41 -0400 (EDT)
Received: from mx1.ustc.edu.cn ([61.132.182.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09963
	for <rohc@ietf.org>; Thu, 13 Jun 2002 08:50:02 -0400 (EDT)
Received: from mail.ustc.edu.cn (mail.ustc.edu.cn [202.38.64.10])
	by mx1.ustc.edu.cn (8.8.7/8.8.6) with SMTP id UAA23961
	for <rohc@ietf.org>; Thu, 13 Jun 2002 20:43:42 +0800
Received: (qmail 8751 invoked by uid 1187); 13 Jun 2002 12:43:53 -0000
Date: Thu, 13 Jun 2002 20:43:53 +0800 (CST)
From: Wang Hui <whui@mail.ustc.edu.cn>
X-X-Sender:  <whui@mail>
To: <rohc@ietf.org>
In-Reply-To: <76C92FBBFB58D411AE760090271ED41804B87F47@rsys002a.roke.co.uk>
Message-ID: <Pine.GSO.4.31L2A.0206132023330.4566-100000@mail>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [rohc] Problems of implementating ROHC(RFC3095) on 802.11 WLAN
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

Hi folks here,

Our team is now implementing ROHC based on RFC3095.  We want to make it
run in our mobile IPv6 testbed to enhance some performance of our
mobile IPv6 demo-system.

Now we have only finished coding the U-mode and only realized the UDP only
profile.  But because our test bed is now a Wireless LAN(802.11), we have
found some problems with RFC3095.

o   The CID is allocated by the compressor.  But how to make it an unique
    identifier at the de-compressor side?  Because the WLAN is a shared
    layer 2 linker.  All the mobile nodes share the same channel within a
    WLAN.   If more than one mobile nodes send ROHC packet to one access
    router which will do de-compression, how to make the CIDs allocated by
    different mobile nodes be different?

o   The compressed packets' size may become less than 60 bytes.  60 bytes
    is the minimun size of a ethernet frame.  So if the size of a compressed
    packet is less than 60, it cannot be transefer in the ethernet.

In fact, the Wireless LAN is a broad band wireless environment.  We do not
need to use ROHC.  But I think the RFC3095 should consider these problems.

Best,
Wang Hui

--
 Wang Hui
 Next Generation Internet Research Team,
 InfoNet Lab, USTC
 http://mail.ustc.edu.cn/~whui
 Tel: +86-551-3603634



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


From rohc-admin@ietf.org  Thu Jun 13 09:27:50 2002
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 JAA11248
	for <rohc-archive@odin.ietf.org>; Thu, 13 Jun 2002 09:27:50 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA18482;
	Thu, 13 Jun 2002 09:22:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA18442
	for <rohc@ns.ietf.org>; Thu, 13 Jun 2002 09:22:31 -0400 (EDT)
Received: from nmh.informatik.uni-bremen.de (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10918
	for <rohc@ietf.org>; Thu, 13 Jun 2002 09:21:54 -0400 (EDT)
Received: from tzi.org (IDENT:PUCQAh7VAQAH83CfISwUsUH+DyY9qSVe@roman.informatik.uni-bremen.de [134.102.218.120])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with ESMTP id g5DDIRD01899;
	Thu, 13 Jun 2002 15:18:27 +0200 (MEST)
Message-ID: <3D089BA4.4060408@tzi.org>
Date: Thu, 13 Jun 2002 15:18:28 +0200
From: Carsten Bormann <cabo@tzi.org>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.0) Gecko/20020529
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Wang Hui <whui@mail.ustc.edu.cn>
CC: rohc@ietf.org
Subject: Re: [rohc] Problems of implementating ROHC(RFC3095) on 802.11 WLAN
References: <Pine.GSO.4.31L2A.0206132023330.4566-100000@mail>
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-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org
Content-Transfer-Encoding: 7bit

Hi,

> o   The CID is allocated by the compressor.  But how to make it an unique
>     identifier at the de-compressor side?  Because the WLAN is a shared
>     layer 2 linker.  All the mobile nodes share the same channel within a
>     WLAN.   If more than one mobile nodes send ROHC packet to one access
>     router which will do de-compression, how to make the CIDs allocated by
>     different mobile nodes be different?

The easiest way is to disambiguate e.g. using the source address.

> o   The compressed packets' size may become less than 60 bytes.  60 bytes
>     is the minimun size of a ethernet frame.  So if the size of a compressed
>     packet is less than 60, it cannot be transefer in the ethernet.

This is one of the applications we had in mind when we designed the padding scheme.

Gruesse, Carsten




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


From rohc-admin@ietf.org  Thu Jun 13 09:38:41 2002
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 JAA11847
	for <rohc-archive@odin.ietf.org>; Thu, 13 Jun 2002 09:38:41 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA19834;
	Thu, 13 Jun 2002 09:33:53 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA19803
	for <rohc@ns.ietf.org>; Thu, 13 Jun 2002 09:33:51 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11524
	for <rohc@ietf.org>; Thu, 13 Jun 2002 09:33:14 -0400 (EDT)
Received: from esealnt610.al.sw.ericsson.se (esealnt610.al.sw.ericsson.se [153.88.254.69])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g5DDXemH003017;
	Thu, 13 Jun 2002 15:33:40 +0200 (MEST)
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <M3JPGQS9>; Thu, 13 Jun 2002 15:33:40 +0200
Message-ID: <A943FD84BD9ED41193460008C791805003E3213C@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'Wang Hui'" <whui@mail.ustc.edu.cn>, rohc@ietf.org
Subject: RE: [rohc] Problems of implementating ROHC(RFC3095) on 802.11 WLA
	N
Date: Thu, 13 Jun 2002 15:33:36 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

Hi Wang,

> o   The CID is allocated by the compressor. But how to make 
> it an unique identifier at the de-compressor side? Because the WLAN 
> is a shared layer 2 linker. All the mobile nodes share the same 
> channel within a WLAN. If more than one mobile nodes send ROHC packet to 
> one access router which will do de-compression, how to make the CIDs 
> allocated by different mobile nodes be different?

ROHC assumes logical point-to-point channels, which can be created by
using e.g. link addressing in a shared media environment.


> o   The compressed packets' size may become less than 60 
> bytes. 60 bytes is the minimun size of a ethernet frame.  So if the
> size of a compressed packet is less than 60, it cannot be transefer
> in the ethernet.

ROHC padding might be used for this purpose.

 
> In fact, the Wireless LAN is a broad band wireless environment.
> We do not need to use ROHC. But I think the RFC3095 should consider 
> these problems.

Well, RFC 3095 does not consider this since logical point-to-point
channels are assumed. It might be useful to elaborate a little bit
more about that when we cycle the RFC for Drafts Standard. Still,
what you ask for is more of an issue for a "ROHC over X"-document,
if X is not by nature a point-to-point link.

Cheers,
/L-E 

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


From rohc-admin@ietf.org  Thu Jun 13 20:40:24 2002
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 UAA06118
	for <rohc-archive@odin.ietf.org>; Thu, 13 Jun 2002 20:40:24 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA02913;
	Thu, 13 Jun 2002 20:39:18 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA02882
	for <rohc@ns.ietf.org>; Thu, 13 Jun 2002 20:39:16 -0400 (EDT)
Received: from mail8.nc.rr.com (fe8.southeast.rr.com [24.93.67.55])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06073
	for <rohc@ietf.org>; Thu, 13 Jun 2002 20:38:41 -0400 (EDT)
Received: from mail pickup service by mail8.nc.rr.com with Microsoft SMTPSVC;
	 Thu, 13 Jun 2002 20:39:14 -0400
Received: from ncmx01.mgw.rr.com ([24.93.67.251]) by mail8.nc.rr.com  with Microsoft SMTPSVC(5.5.1877.757.75);
	 Wed, 12 Jun 2002 09:12:17 -0400
Received: from loki.ietf.org (loki.ietf.org [132.151.1.177])
	by ncmx01.mgw.rr.com (8.12.2/8.12.2) with ESMTP id g5CDCGbC011063;
	Wed, 12 Jun 2002 09:12:16 -0400 (EDT)
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id JAA07333
	for ietf-123-outbound.05@ietf.org; Wed, 12 Jun 2002 09:05:00 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id HAA06341
	for <all-ietf@loki.ietf.org>; Wed, 12 Jun 2002 07:14:20 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22894;
	Wed, 12 Jun 2002 07:13:45 -0400 (EDT)
Message-Id: <200206121113.HAA22894@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: Wed, 12 Jun 2002 07:13:44 -0400
Subject: [rohc] I-D ACTION:draft-jonsson-rohc-ip-only-00.txt
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: RObust Header Compression (ROHC):A Compression Profile
                          for IP
	Author(s)	: L. Jonsson
	Filename	: draft-jonsson-rohc-ip-only-00.txt
	Pages		: 5
	Date		: 11-Jun-02
	
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 for uncompressed
packet streams. However, no profile was defined for compression of IP
only, which has been identified as a flaw in RFC 3095. This document
addresses that problem and defines a ROHC compression profile for IP,
similar to the IP/UDP profile defined by RFC 3095, but simplified to
exclude UDP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-jonsson-rohc-ip-only-00.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-jonsson-rohc-ip-only-00.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-jonsson-rohc-ip-only-00.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:	<20020611122823.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-jonsson-rohc-ip-only-00.txt

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

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

--OtherAccess--

--NextPart--


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


From rohc-admin@ietf.org  Fri Jun 14 11:45:40 2002
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 LAA04012
	for <rohc-archive@odin.ietf.org>; Fri, 14 Jun 2002 11:45:39 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA18646;
	Fri, 14 Jun 2002 11:44:12 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA18615
	for <rohc@optimus.ietf.org>; Fri, 14 Jun 2002 11:44:10 -0400 (EDT)
Received: from mx1.ustc.edu.cn ([61.132.182.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03951
	for <rohc@ietf.org>; Fri, 14 Jun 2002 11:43:30 -0400 (EDT)
Received: from mail.ustc.edu.cn (mail.ustc.edu.cn [202.38.64.10])
	by mx1.ustc.edu.cn (8.8.7/8.8.6) with SMTP id XAA12167
	for <rohc@ietf.org>; Fri, 14 Jun 2002 23:37:45 +0800
Received: (qmail 3636 invoked by uid 1187); 14 Jun 2002 15:37:58 -0000
Date: Fri, 14 Jun 2002 23:37:58 +0800 (CST)
From: Wang Hui <whui@mail.ustc.edu.cn>
X-X-Sender:  <whui@mail>
To: Carsten Bormann <cabo@tzi.org>
cc: <rohc@ietf.org>
Subject: Re: [rohc] Problems of implementating ROHC(RFC3095) on 802.11 WLAN
In-Reply-To: <3D089BA4.4060408@tzi.org>
Message-ID: <Pine.GSO.4.31L2A.0206142335480.3132-100000@mail>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

On Thu, 13 Jun 2002, Carsten Bormann wrote:

> Hi,
>
> > o   The CID is allocated by the compressor.  But how to make it an unique
> >     identifier at the de-compressor side?  Because the WLAN is a shared
> >     layer 2 linker.  All the mobile nodes share the same channel within a
> >     WLAN.   If more than one mobile nodes send ROHC packet to one access
> >     router which will do de-compression, how to make the CIDs allocated by
> >     different mobile nodes be different?
>
> The easiest way is to disambiguate e.g. using the source address.

Yes, the source address may help it.

>
> > o   The compressed packets' size may become less than 60 bytes.  60 bytes
> >     is the minimun size of a ethernet frame.  So if the size of a compressed
> >     packet is less than 60, it cannot be transefer in the ethernet.
>
> This is one of the applications we had in mind when we designed the padding scheme.

Yes. Could you say more about your idea?

>
> Gruesse, Carsten
>
>
>
>

--
 Wang Hui
 Next Generation Internet Research Team,
 InfoNet Lab, USTC
 http://mail.ustc.edu.cn/~whui
 Tel: +86-551-3603634



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


From rohc-admin@ietf.org  Fri Jun 14 12:06:03 2002
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 MAA04586
	for <rohc-archive@odin.ietf.org>; Fri, 14 Jun 2002 12:06:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA21056;
	Fri, 14 Jun 2002 12:05:19 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA21025
	for <rohc@optimus.ietf.org>; Fri, 14 Jun 2002 12:05:17 -0400 (EDT)
Received: from mx1.ustc.edu.cn ([61.132.182.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04573
	for <rohc@ietf.org>; Fri, 14 Jun 2002 12:04:37 -0400 (EDT)
Received: from mail.ustc.edu.cn (mail.ustc.edu.cn [202.38.64.10])
	by mx1.ustc.edu.cn (8.8.7/8.8.6) with SMTP id XAA13049
	for <rohc@ietf.org>; Fri, 14 Jun 2002 23:50:57 +0800
Received: (qmail 4456 invoked by uid 1187); 14 Jun 2002 15:51:10 -0000
Date: Fri, 14 Jun 2002 23:51:10 +0800 (CST)
From: Wang Hui <whui@mail.ustc.edu.cn>
X-X-Sender:  <whui@mail>
To: "Lars-Erik Jonsson \(EPL\)" <Lars-Erik.Jonsson@epl.ericsson.se>
cc: <rohc@ietf.org>
Subject: RE: [rohc] Problems of implementating ROHC(RFC3095) on 802.11 WLA
 N
In-Reply-To: <A943FD84BD9ED41193460008C791805003E3213C@ESEALNT419.al.sw.ericsson.se>
Message-ID: <Pine.GSO.4.31L2A.0206142338260.3132-100000@mail>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

Thanks for Jonsson's reply.

On Thu, 13 Jun 2002, Lars-Erik Jonsson (EPL) wrote:

> Hi Wang,
>
> > o   The CID is allocated by the compressor. But how to make
> > it an unique identifier at the de-compressor side? Because the WLAN
> > is a shared layer 2 linker. All the mobile nodes share the same
> > channel within a WLAN. If more than one mobile nodes send ROHC packet to
> > one access router which will do de-compression, how to make the CIDs
> > allocated by different mobile nodes be different?
>
> ROHC assumes logical point-to-point channels, which can be created by
> using e.g. link addressing in a shared media environment.
>

Yes, it seems that we have to do like this.

>
> > o   The compressed packets' size may become less than 60
> > bytes. 60 bytes is the minimun size of a ethernet frame.  So if the
> > size of a compressed packet is less than 60, it cannot be transefer
> > in the ethernet.
>
> ROHC padding might be used for this purpose.

Since the minimun frame size is moderate big, we have to do padding with a
lot of packets especially when we send small packet (eg. VoIP packets)
often.  Could we choose that we dont do ROHC in such a case?

>
>
> > In fact, the Wireless LAN is a broad band wireless environment.
> > We do not need to use ROHC. But I think the RFC3095 should consider
> > these problems.
>
> Well, RFC 3095 does not consider this since logical point-to-point
> channels are assumed. It might be useful to elaborate a little bit
> more about that when we cycle the RFC for Drafts Standard. Still,
> what you ask for is more of an issue for a "ROHC over X"-document,
> if X is not by nature a point-to-point link.

Yes, I guess maybe after our expierence of implementing ROHC on 802.11b,
we might write a draft as 'ROHC over 802.11b'.  Then we can discuss these
issues in more detailed level.

Best regards,
Wang

--
 Wang Hui
 Next Generation Internet Research Team,
 InfoNet Lab, USTC
 http://mail.ustc.edu.cn/~whui
 Tel: +86-551-3603634



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


From rohc-admin@ietf.org  Sun Jun 16 16:09:10 2002
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 QAA07416
	for <rohc-archive@odin.ietf.org>; Sun, 16 Jun 2002 16:09:10 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA25658;
	Sun, 16 Jun 2002 16:07:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA15227
	for <rohc@optimus.ietf.org>; Sun, 16 Jun 2002 10:55:10 -0400 (EDT)
Received: from mail.ee.gatech.edu (mail.ee.gatech.edu [130.207.225.105])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03992
	for <rohc@ietf.org>; Sun, 16 Jun 2002 10:54:32 -0400 (EDT)
Received: from ece.gatech.edu (seiya.ece.gatech.edu [130.207.225.101])
	by mail.ee.gatech.edu (8.12.3/8.12.1) with SMTP id g5GEt95d015261
	for <rohc@ietf.org>; Sun, 16 Jun 2002 10:55:09 -0400 (EDT)
Received: from 66.156.65.207
        (SquirrelMail authenticated user vkm)
        by secure2.ece.gatech.edu with HTTP;
        Sun, 16 Jun 2002 10:55:09 -0400 (EDT)
Message-ID: <33967.66.156.65.207.1024239309.squirrel@secure2.ece.gatech.edu>
Date: Sun, 16 Jun 2002 10:55:09 -0400 (EDT)
From: "Vijay K. Madisetti" <vijay.madisetti@ece.gatech.edu>
To: <rohc@ietf.org>
In-Reply-To: <200206151600.MAA24051@optimus.ietf.org>
References: <200206151600.MAA24051@optimus.ietf.org>
X-Priority: 3
Importance: Normal
X-MSMail-Priority: Normal
Reply-To: vijay.madisetti@ece.gatech.edu
X-Mailer: SquirrelMail (version 1.2.4)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)
Content-Transfer-Encoding: 8bit
Subject: [rohc] ROHC 2095 Reference Test Suite Available ?
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org
Content-Transfer-Encoding: 8bit


Greetings -

Is there a public domain
test suite available for ROHC 3095 that we can use to check
correctness, interoperability, support for various modes, and efficiency of
our C implementations ?

This is only the test suite, not the reference implementations of ROHC
itself.

Rgds, Vijay.

Vijay Madisetti
Professor, ECE
Georgia Tech




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


From rohc-admin@ietf.org  Sun Jun 16 21:15:55 2002
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 VAA10447
	for <rohc-archive@odin.ietf.org>; Sun, 16 Jun 2002 21:15:55 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA06175;
	Sun, 16 Jun 2002 21:14:50 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA06120
	for <rohc@optimus.ietf.org>; Sun, 16 Jun 2002 21:14:47 -0400 (EDT)
Received: from mail.ict.ac.cn ([159.226.39.4])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA10424
	for <rohc@ietf.org>; Sun, 16 Jun 2002 21:14:04 -0400 (EDT)
Message-Id: <200206170114.VAA10424@ietf.org>
Received: (qmail 4380 invoked from network); 17 Jun 2002 01:01:51 -0000
Received: from unknown (HELO yanfengzheng) (159.226.42.76)
  by 159.226.39.4 with SMTP; 17 Jun 2002 01:01:51 -0000
Date: Mon, 17 Jun 2002 9:18:21 +0800
From: "Yanfeng Zheng" <yanfeng6@ict.ac.cn>
To: "rohc-admin@ietf.org" <rohc-admin@ietf.org>,
        "rohc-admin@ietf.org" <rohc-admin@ietf.org>,
        "rohc@ietf.org" <rohc@ietf.org>
X-mailer: Foxmail 4.1 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
      charset="GB2312"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id VAA06125
Subject: [rohc] rohc about ieee 802.11b
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org
Content-Transfer-Encoding: 8bit

hi,
  ROHC technique is very important for 2.5G, 3G and 4G celluar networks. Well, ieee 802.11b is actually broadband wireless networks. So i wonder there is any significance if rohc is applied to WLAN. Are there some research interests on that area?

Best regards,
			

¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡Yanfeng Zheng
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yanfeng6@ict.ac.cn
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-06-17




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


From rohc-admin@ietf.org  Sun Jun 16 21:52:33 2002
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 VAA11267
	for <rohc-archive@odin.ietf.org>; Sun, 16 Jun 2002 21:52:33 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA07566;
	Sun, 16 Jun 2002 21:51:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA07535
	for <rohc@optimus.ietf.org>; Sun, 16 Jun 2002 21:51:39 -0400 (EDT)
Received: from mx1.ustc.edu.cn ([61.132.182.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11252
	for <rohc@ietf.org>; Sun, 16 Jun 2002 21:50:58 -0400 (EDT)
Received: from mail.ustc.edu.cn (mail.ustc.edu.cn [202.38.64.10])
	by mx1.ustc.edu.cn (8.8.7/8.8.6) with SMTP id JAA24162
	for <rohc@ietf.org>; Mon, 17 Jun 2002 09:45:32 +0800
Received: (qmail 20245 invoked by uid 1187); 17 Jun 2002 01:45:37 -0000
Date: Mon, 17 Jun 2002 09:45:37 +0800 (CST)
From: Wang Hui <whui@mail.ustc.edu.cn>
X-X-Sender:  <whui@mail>
To: Yanfeng Zheng <yanfeng6@ict.ac.cn>
cc: "rohc@ietf.org" <rohc@ietf.org>
Subject: Re: [rohc] rohc about ieee 802.11b
In-Reply-To: <200206170114.VAA10424@ietf.org>
Message-ID: <Pine.GSO.4.31L2A.0206170944090.18859-100000@mail>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

Hi Zheng,

I am in the field of researching the 'ROHC over 802.11b' related issues.
We can exchange our idea.

Best,
Wang

On Mon, 17 Jun 2002, Yanfeng Zheng wrote:

> hi,
>   ROHC technique is very important for 2.5G, 3G and 4G celluar networks. Well, ieee 802.11b is actually broadband wireless networks. So i wonder there is any significance if rohc is applied to WLAN. Are there some research interests on that area?
>
> Best regards,
>
>
> ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡Yanfeng Zheng
> ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yanfeng6@ict.ac.cn
> ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-06-17
>
>

--
 Wang Hui
 Next Generation Internet Research Team,
 InfoNet Lab, USTC
 http://mail.ustc.edu.cn/~whui
 Tel: +86-551-3603634



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


From rohc-admin@ietf.org  Mon Jun 17 05:31:35 2002
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 FAA25022
	for <rohc-archive@odin.ietf.org>; Mon, 17 Jun 2002 05:31:35 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA02213;
	Mon, 17 Jun 2002 05:30:01 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA02176
	for <rohc@optimus.ietf.org>; Mon, 17 Jun 2002 05:29:59 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.47])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24978
	for <rohc@ietf.org>; Mon, 17 Jun 2002 05:29:20 -0400 (EDT)
Received: from esealnt611.al.sw.ericsson.se (esealnt611.al.sw.ericsson.se [153.88.254.68])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g5H9TmRb009623;
	Mon, 17 Jun 2002 11:29:48 +0200 (MEST)
Received: by esealnt611.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <MZT390DJ>; Mon, 17 Jun 2002 11:29:48 +0200
Message-ID: <A943FD84BD9ED41193460008C791805003E32147@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'Wang Hui'" <whui@mail.ustc.edu.cn>, rohc@ietf.org
Subject: RE: [rohc] Problems of implementating ROHC(RFC3095) on 802.11 WLA
	 N
Date: Mon, 17 Jun 2002 11:29:45 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

To clarify my previous posting:

> > In fact, the Wireless LAN is a broad band wireless environment.
> > We do not need to use ROHC. But I think the RFC3095 should consider 
> > these problems.
> 
> LEJ: Well, RFC 3095 does not consider this since logical point-to-point
> channels are assumed. It might be useful to elaborate a little bit
> more about that when we cycle the RFC for Drafts Standard. Still,
> what you ask for is more of an issue for a "ROHC over X"-document,
> if X is not by nature a point-to-point link.

The ROHC WG has written the "ROHC-over-PPP" specification, which might
also be seen as an example to follow when writing such specifications
for other link layers. However, to develop mapping standards for using
ROHC on top of other link layers than PPP is not part of the ROHC WG 
charter, but should be considered as work for each actual link-layer
standardization.

BR
/L-E

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


From rohc-admin@ietf.org  Mon Jun 17 07:35:21 2002
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 HAA26825
	for <rohc-archive@odin.ietf.org>; Mon, 17 Jun 2002 07:35:21 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA07646;
	Mon, 17 Jun 2002 07:32:59 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA07615
	for <rohc@optimus.ietf.org>; Mon, 17 Jun 2002 07:32:57 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26669;
	Mon, 17 Jun 2002 07:32:16 -0400 (EDT)
Message-Id: <200206171132.HAA26669@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: Mon, 17 Jun 2002 07:32:16 -0400
Subject: [rohc] I-D ACTION:draft-jonsson-rohc-architecture-00.txt
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: RObust Header Compression (ROHC): The ROHC 
                          Architecture
	Author(s)	: L. Jonsson
	Filename	: draft-jonsson-rohc-architecture-00.txt
	Pages		: 16
	Date		: 14-Jun-02
	
RFC 3095 defines a Proposed Standard framework with profiles for
RObust Header Compression (ROHC). Various concepts are introduced
within the standard, which might be difficult to understand, and
especially how these relate to the surrounding environments where
header compression may be used. This document aims at clarifying the
architectural aspects of ROHC, discussing terms such as ROHC
instances, ROHC channels, ROHC feedback, ROHC contexts, and how these
terms relate to other terms like network elements and IP interfaces,
commonly used when for example addressing MIB issues.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-jonsson-rohc-architecture-00.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-jonsson-rohc-architecture-00.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-jonsson-rohc-architecture-00.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:	<20020614131328.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-jonsson-rohc-architecture-00.txt

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

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

--OtherAccess--

--NextPart--



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


From rohc-admin@ietf.org  Tue Jun 18 08:54:32 2002
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 IAA15329
	for <rohc-archive@odin.ietf.org>; Tue, 18 Jun 2002 08:54:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA10239;
	Tue, 18 Jun 2002 08:52:50 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA10210
	for <rohc@ns.ietf.org>; Tue, 18 Jun 2002 08:52:48 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15315
	for <rohc@ietf.org>; Tue, 18 Jun 2002 08:52:08 -0400 (EDT)
Received: from esealnt611.al.sw.ericsson.se (esealnt611.al.sw.ericsson.se [153.88.254.68])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g5ICqkrU018103
	for <rohc@ietf.org>; Tue, 18 Jun 2002 14:52:46 +0200 (MEST)
Received: by esealnt611.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <MZTPJ320>; Tue, 18 Jun 2002 14:52:46 +0200
Message-ID: <A943FD84BD9ED41193460008C791805003E32158@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: rohc@ietf.org
Date: Tue, 18 Jun 2002 14:52:44 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [rohc] Comments appreciated: draft-jonsson-rohc-architecture-00.txt
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

Hi all,

As you might have seen, I've submitted a draft about ROHC architectural
issues, as previously promised. The draft speaks for itself, so I will
not repeat more than the abstract below. My intension is to submit an
updated version prior to the ID cut-off on July 1st. Therefore, I would
appreciate all potential comments not later than a few days before that.

Thanx!
/L-E


> 	Title		: RObust Header Compression (ROHC): The ROHC 
>                           Architecture
> 	Author(s)	: L-E. Jonsson
> 	Filename	: draft-jonsson-rohc-architecture-00.txt
> 	Pages		: 16
> 	Date		: 14-Jun-02
> 	
> RFC 3095 defines a Proposed Standard framework with profiles for
> RObust Header Compression (ROHC). Various concepts are introduced
> within the standard, which might be difficult to understand, and
> especially how these relate to the surrounding environments where
> header compression may be used. This document aims at clarifying the
> architectural aspects of ROHC, discussing terms such as ROHC
> instances, ROHC channels, ROHC feedback, ROHC contexts, and how these
> terms relate to other terms like network elements and IP interfaces,
> commonly used when for example addressing MIB issues.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-jonsson-rohc-architecture-00.txt

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


From rohc-admin@ietf.org  Tue Jun 18 09:01:16 2002
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 JAA15590
	for <rohc-archive@odin.ietf.org>; Tue, 18 Jun 2002 09:01:16 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA10624;
	Tue, 18 Jun 2002 09:00:27 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA10584
	for <rohc@ns.ietf.org>; Tue, 18 Jun 2002 09:00:25 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15496
	for <rohc@ietf.org>; Tue, 18 Jun 2002 08:59:45 -0400 (EDT)
Received: from esealnt610.al.sw.ericsson.se (esealnt610.al.sw.ericsson.se [153.88.254.69])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g5ID0MrV020432
	for <rohc@ietf.org>; Tue, 18 Jun 2002 15:00:23 +0200 (MEST)
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <M3JQF4ZS>; Tue, 18 Jun 2002 15:00:22 +0200
Message-ID: <A943FD84BD9ED41193460008C791805003E32159@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: rohc@ietf.org
Date: Tue, 18 Jun 2002 15:00:19 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [rohc] About "draft-jonsson-rohc-ip-only-00.txt"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

Hi again,

Since RFC 3095 was published, people have asked why there is no 
compression profile for IP only. Therefore, I wrote an extremely
short draft defining such a profile, based on the UDP/IP profile
of RFC 3095. If you have any comments on this draft, please let
me know not later than June 29, and I will incorporate them in 
an update before the ID cut-off (July 1).

BR
/L-E


> 	Title		: RObust Header Compression (ROHC):
>                   A Compression Profile for IP
> 	Author(s)	: L-E. Jonsson
> 	Filename	: draft-jonsson-rohc-ip-only-00.txt
> 	Pages		: 5
> 	Date		: 11-Jun-02
> 	
> 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 for uncompressed
> packet streams. However, no profile was defined for compression of IP
> only, which has been identified as a flaw in RFC 3095. This document
> addresses that problem and defines a ROHC compression profile for IP,
> similar to the IP/UDP profile defined by RFC 3095, but simplified to
> exclude UDP.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-jonsson-rohc-ip-only-00.txt

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


From rohc-admin@ietf.org  Tue Jun 18 18:44:31 2002
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 SAA07256
	for <rohc-archive@odin.ietf.org>; Tue, 18 Jun 2002 18:44:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA21642;
	Tue, 18 Jun 2002 18:43:22 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA21615
	for <rohc@optimus.ietf.org>; Tue, 18 Jun 2002 18:43:21 -0400 (EDT)
Received: from mgw-dax2.ext.nokia.com (mgw-dax2.ext.nokia.com [63.78.179.217])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07203
	for <rohc@ietf.org>; Tue, 18 Jun 2002 18:42:40 -0400 (EDT)
From: zhigang.c.liu@nokia.com
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
	by mgw-dax2.ext.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g5IMklj11755
	for <rohc@ietf.org>; Tue, 18 Jun 2002 17:46:47 -0500 (CDT)
Received: from daebh002.NOE.Nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5b90baffedac12f257126@davir04nok.americas.nokia.com>;
 Tue, 18 Jun 2002 17:43:18 -0500
Received: from daebe005.NOE.Nokia.com ([172.18.242.203]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 18 Jun 2002 17:42:43 -0500
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [rohc] Problems of implementating ROHC(RFC3095) on 802.11 WLAN
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Date: Tue, 18 Jun 2002 17:42:43 -0500
Message-ID: <DE0842B293FC4847992F9EDF8D72E1ED24A44E@daebe005.NOE.Nokia.com>
Thread-Topic: [rohc] Problems of implementating ROHC(RFC3095) on 802.11 WLAN
Thread-Index: AcIS2Rf+fqypgEhSS/GnaY9tuMF0PwENleGw
To: <whui@mail.ustc.edu.cn>, <rohc@ietf.org>
X-OriginalArrivalTime: 18 Jun 2002 22:42:43.0762 (UTC) FILETIME=[75CA7920:01C21719]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id SAA21616
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org
Content-Transfer-Encoding: 8bit

> o   The compressed packets' size may become less than 60 bytes.  60 bytes
>     is the minimun size of a ethernet frame.  So if the size of a compressed
>     packet is less than 60, it cannot be transefer in the ethernet.

Not sure you're talking about 802.11 or (wired) ethernet. If it is
ethernet and assuming you keep the ethernet frame header unchanged 
(see below), you have 46 bytes to carry the payload of ethernet frame. 
If ROHC packet is less than 46 bytes long, you can use ROHC padding as 
Carsten suggested. Or, you can add a length field (after the 14-byte 
ethernet frame header) which indicates the real ROHC packet size. 
For Linux, you can send ethernet frames < 60 bytes and the driver 
will do the padding for you.

6 bytes: dest ethernet address
6 bytes: src ethernet address
2 bytes: type

> In fact, the Wireless LAN is a broad band wireless environment.  
> We do not need to use ROHC. 

Then why implementing ROHC over WLAN where it is not needed?
Is it only for testing purpose? (I used ROHC over ethernet for
testing)

BR,
Zhigang

 

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


From rohc-admin@ietf.org  Tue Jun 18 21:41:56 2002
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 VAA10769
	for <rohc-archive@odin.ietf.org>; Tue, 18 Jun 2002 21:41:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA01278;
	Tue, 18 Jun 2002 21:40:53 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA01248
	for <rohc@optimus.ietf.org>; Tue, 18 Jun 2002 21:40:51 -0400 (EDT)
Received: from mx1.ustc.edu.cn ([61.132.182.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10717
	for <rohc@ietf.org>; Tue, 18 Jun 2002 21:40:12 -0400 (EDT)
Received: from mail.ustc.edu.cn (mail.ustc.edu.cn [202.38.64.10])
	by mx1.ustc.edu.cn (8.8.7/8.8.6) with SMTP id JAA11566
	for <rohc@ietf.org>; Wed, 19 Jun 2002 09:36:44 +0800
Received: (qmail 7010 invoked by uid 1187); 19 Jun 2002 01:36:48 -0000
Date: Wed, 19 Jun 2002 09:36:48 +0800 (CST)
From: Wang Hui <whui@mail.ustc.edu.cn>
X-X-Sender:  <whui@mail>
To: <zhigang.c.liu@nokia.com>
cc: <rohc@ietf.org>
Subject: RE: [rohc] Problems of implementating ROHC(RFC3095) on 802.11 WLAN
In-Reply-To: <DE0842B293FC4847992F9EDF8D72E1ED24A44E@daebe005.NOE.Nokia.com>
Message-ID: <Pine.GSO.4.31L2A.0206190923270.4200-100000@mail>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

On Tue, 18 Jun 2002 zhigang.c.liu@nokia.com wrote:

> > o   The compressed packets' size may become less than 60 bytes.  60 bytes
> >     is the minimun size of a ethernet frame.  So if the size of a compressed
> >     packet is less than 60, it cannot be transefer in the ethernet.
>
> Not sure you're talking about 802.11 or (wired) ethernet. If it is
> ethernet and assuming you keep the ethernet frame header unchanged
> (see below), you have 46 bytes to carry the payload of ethernet frame.
> If ROHC packet is less than 46 bytes long, you can use ROHC padding as
> Carsten suggested. Or, you can add a length field (after the 14-byte
> ethernet frame header) which indicates the real ROHC packet size.
> For Linux, you can send ethernet frames < 60 bytes and the driver
> will do the padding for you.

Yes, in my experiment, I found the Linux driver will do the padding.
But the padding is of random bytes.  The Linux driver just keeps the
minimun transport time and the 'padding data' is random which is not in
meaning.  At the receiver point we could not deduce the data length from
the layer 2 information.  So I guess 'using ROHC padding' as Carsten
suggested is a good choice. And adding a length field as you mentioned
will work  too.

>
> 6 bytes: dest ethernet address
> 6 bytes: src ethernet address
> 2 bytes: type
>
> > In fact, the Wireless LAN is a broad band wireless environment.
> > We do not need to use ROHC.
>
> Then why implementing ROHC over WLAN where it is not needed?
> Is it only for testing purpose? (I used ROHC over ethernet for
> testing)

Yes, we do it for the testing purpose.  We may move it to other platform
in future after its fully testing in WLAN or ethernet LAN.

BTW, you are do the testing work in ethernet?  I guess we have something
in common, we may keep in touch.

Best regards,
Wang

>
> BR,
> Zhigang
>
>
>

--
 Wang Hui
 Next Generation Internet Research Team,
 InfoNet Lab, USTC
 http://mail.ustc.edu.cn/~whui
 Tel: +86-551-3603634



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


From rohc-admin@ietf.org  Tue Jun 18 22:19:34 2002
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 WAA11687
	for <rohc-archive@odin.ietf.org>; Tue, 18 Jun 2002 22:19:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA02336;
	Tue, 18 Jun 2002 22:18:42 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA02303
	for <rohc@optimus.ietf.org>; Tue, 18 Jun 2002 22:18:40 -0400 (EDT)
Received: from mgw-dax2.ext.nokia.com (mgw-dax2.ext.nokia.com [63.78.179.217])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11647
	for <rohc@ietf.org>; Tue, 18 Jun 2002 22:18:01 -0400 (EDT)
From: zhigang.c.liu@nokia.com
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
	by mgw-dax2.ext.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g5J2M8j27240
	for <rohc@ietf.org>; Tue, 18 Jun 2002 21:22:08 -0500 (CDT)
Received: from daebh002.NOE.Nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5b918028eeac12f257126@davir04nok.americas.nokia.com>;
 Tue, 18 Jun 2002 21:18:39 -0500
Received: from daebe005.NOE.Nokia.com ([172.18.242.203]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 18 Jun 2002 21:18:30 -0500
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [rohc] Problems of implementating ROHC(RFC3095) on 802.11 WLAN
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Date: Tue, 18 Jun 2002 21:18:29 -0500
Message-ID: <DE0842B293FC4847992F9EDF8D72E1ED24A451@daebe005.NOE.Nokia.com>
Thread-Topic: [rohc] Problems of implementating ROHC(RFC3095) on 802.11 WLAN
Thread-Index: AcIXMly3fLoW9EkBRVS8YPlewMblCwABAueA
To: <whui@mail.ustc.edu.cn>
Cc: <rohc@ietf.org>
X-OriginalArrivalTime: 19 Jun 2002 02:18:30.0404 (UTC) FILETIME=[9A974440:01C21737]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id WAA02304
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org
Content-Transfer-Encoding: 8bit

> > Or, you can add a length field (after the 14-byte
> > ethernet frame header) which indicates the real ROHC packet size.
> > For Linux, you can send ethernet frames < 60 bytes and the driver
> > will do the padding for you.
> 
> Yes, in my experiment, I found the Linux driver will do the padding.
> But the padding is of random bytes.  The Linux driver just keeps the
> minimun transport time and the 'padding data' is random which 
> is not in meaning.  At the receiver point we could not deduce the data 
> length from the layer 2 information.  

I meant to say the padding by driver in convenient when combined with
the length field inserted. The sender simply sets the length field
and drops the frame on the interface. The receiver relies on the 
length field to retrieve data regardless of the padding.

Zhigang

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


From rohc-admin@ietf.org  Tue Jun 18 23:04:19 2002
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 XAA12688
	for <rohc-archive@odin.ietf.org>; Tue, 18 Jun 2002 23:04:19 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA04596;
	Tue, 18 Jun 2002 23:03:32 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA04565
	for <rohc@optimus.ietf.org>; Tue, 18 Jun 2002 23:03:29 -0400 (EDT)
Received: from mx1.ustc.edu.cn ([61.132.182.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12653
	for <rohc@ietf.org>; Tue, 18 Jun 2002 23:02:48 -0400 (EDT)
Received: from mail.ustc.edu.cn (mail.ustc.edu.cn [202.38.64.10])
	by mx1.ustc.edu.cn (8.8.7/8.8.6) with SMTP id KAA18825
	for <rohc@ietf.org>; Wed, 19 Jun 2002 10:37:29 +0800
Received: (qmail 19310 invoked by uid 1187); 19 Jun 2002 02:37:35 -0000
Date: Wed, 19 Jun 2002 10:37:34 +0800 (CST)
From: Wang Hui <whui@mail.ustc.edu.cn>
X-X-Sender:  <whui@mail>
To: "Lars-Erik Jonsson \(EPL\)" <Lars-Erik.Jonsson@epl.ericsson.se>
cc: <rohc@ietf.org>
Subject: Re: [rohc] Comments appreciated: draft-jonsson-rohc-architecture-00.txt
In-Reply-To: <A943FD84BD9ED41193460008C791805003E32158@ESEALNT419.al.sw.ericsson.se>
Message-ID: <Pine.GSO.4.31L2A.0206191025150.16514-100000@mail>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org


I read through this draft right now, and found it was very useful.
The concept of ROHC is clarified.  Thanks to Jonsson.

Here is my understanding:

A 'network element' can has N 'IP interfaces'.
An 'IP interface' can has N Layer 2 channel.
A layer 2 channel could contain M compressors or K decompressors.
A compressor or decompressor is corresponding to a ROHC channel.
A ROHC channel could be indentified with the CID.

Is it?

best,
Wang

On Tue, 18 Jun 2002, Lars-Erik Jonsson (EPL) wrote:

> Hi all,
>
> As you might have seen, I've submitted a draft about ROHC architectural
> issues, as previously promised. The draft speaks for itself, so I will
> not repeat more than the abstract below. My intension is to submit an
> updated version prior to the ID cut-off on July 1st. Therefore, I would
> appreciate all potential comments not later than a few days before that.
>
> Thanx!
> /L-E
>
>
> > 	Title		: RObust Header Compression (ROHC): The ROHC
> >                           Architecture
> > 	Author(s)	: L-E. Jonsson
> > 	Filename	: draft-jonsson-rohc-architecture-00.txt
> > 	Pages		: 16
> > 	Date		: 14-Jun-02
> >
> > RFC 3095 defines a Proposed Standard framework with profiles for
> > RObust Header Compression (ROHC). Various concepts are introduced
> > within the standard, which might be difficult to understand, and
> > especially how these relate to the surrounding environments where
> > header compression may be used. This document aims at clarifying the
> > architectural aspects of ROHC, discussing terms such as ROHC
> > instances, ROHC channels, ROHC feedback, ROHC contexts, and how these
> > terms relate to other terms like network elements and IP interfaces,
> > commonly used when for example addressing MIB issues.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-jonsson-rohc-architecture-00.txt
>
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
>

--
 Wang Hui
 Next Generation Internet Research Team,
 InfoNet Lab, USTC
 http://mail.ustc.edu.cn/~whui
 Tel: +86-551-3603634



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


From rohc-admin@ietf.org  Wed Jun 19 02:03:06 2002
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 CAA19983
	for <rohc-archive@odin.ietf.org>; Wed, 19 Jun 2002 02:03:06 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA18948;
	Wed, 19 Jun 2002 02:02:32 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA18913
	for <rohc@optimus.ietf.org>; Wed, 19 Jun 2002 02:02:30 -0400 (EDT)
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18280;
	Wed, 19 Jun 2002 02:01:49 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.42])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g5J61MYH017075;
	Wed, 19 Jun 2002 02:01:23 -0400 (EDT)
Message-ID: <3D101E32.6040606@dynamicsoft.com>
Date: Wed, 19 Jun 2002 02:01:22 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
CC: sip <sip@ietf.org>, rohc <rohc@ietf.org>
Subject: Re: [rohc] SigComp and SIP
References: <3CD10F64.D62B1E78@lmf.ericsson.se>
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-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org
Content-Transfer-Encoding: 7bit

more old email. So sue me. Responses inline:

Gonzalo Camarillo wrote:
> Jonathan,

>>> A proxy performing Record-Route inspects the Record-Route and the
>>>   Contact header fields in the response. It looks for the URI of
>> the
>>>   next upstream (closer to the user agent client) hop in the route
>> set.
>>>   If this URI contains the parameter comp=sigcomp, the proxy SHOULD
>>add
>>>   comp=sigcomp to its entry in the Record-Route header field.
>>
>>Why? If the upstream element doesn't support this extension, the
>>sigcomp
>>parameter is ignored, and the message is sent uncompressed. Thats what
>>you want. The decision about whether to insert a URI with the comp
>>parameter should be entirely a local one.
> 
> 
> This covers the following scenario:
> 
> UAC----P1-----P2-----UAS
> 
> The UAC sends an INITE to UAS. P2 records route, but P1 does not.
> When the 200 OK for the INVITE reaches P2, the contact and RR header
> fields will look like this:
> 
> Contact: UAS@domain.com;comp=sigcomp
> RR: P2
> 
> If P2 does not add comp=sigcomp to his entry in the RR, UAC will be able
> to receive compressed traffic (the contact has comp=sigcomp), but will
> be unable to send compress traffic (the RR entry for P2 does not have
> it).

Why doesn't it? If a proxy is sigcomp enabled, it should have 
record-routed with sigcomp parameter in the first place.

-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
Chief Scientist                         First Floor
dynamicsoft                             East Hanover, NJ 07936
jdrosen@dynamicsoft.com                 FAX: (973) 952-5050
http://www.jdrosen.net                  PH:  (973) 952-5000
http://www.dynamicsoft.com


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


From rohc-admin@ietf.org  Wed Jun 19 05:26:32 2002
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 FAA11616
	for <rohc-archive@odin.ietf.org>; Wed, 19 Jun 2002 05:26:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA12149;
	Wed, 19 Jun 2002 05:24:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA12118
	for <rohc@optimus.ietf.org>; Wed, 19 Jun 2002 05:24:01 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.47])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11553
	for <rohc@ietf.org>; Wed, 19 Jun 2002 05:23:21 -0400 (EDT)
Received: from esealnt611.al.sw.ericsson.se (esealnt611.al.sw.ericsson.se [153.88.254.68])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g5J9NiRc021191;
	Wed, 19 Jun 2002 11:23:46 +0200 (MEST)
Received: by esealnt611.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <MZTPRZVG>; Wed, 19 Jun 2002 11:23:44 +0200
Message-ID: <A943FD84BD9ED41193460008C791805003E3215C@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'Wang Hui'" <whui@mail.ustc.edu.cn>,
        "Lars-Erik Jonsson (EPL)"
	 <Lars-Erik.Jonsson@epl.ericsson.se>
Cc: rohc@ietf.org
Subject: RE: [rohc] Comments appreciated: draft-jonsson-rohc-architecture-
	00.txt
Date: Wed, 19 Jun 2002 11:23:42 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

Hi Wang,

This helps me a lot to improve the draft for clarity. I'll respond to
your understandings below (and will take the misunderstandings under
consideration for clarifications):


> Here is my understanding:
> 
> A 'network element' can has N 'IP interfaces'.
Right!

> An 'IP interface' can has N Layer 2 channel.
Right!

> A layer 2 channel could contain M compressors or K decompressors.
Depends on how "ROHC channels" are realized within a layer 2 channel.
Consider the difference between "channels" and "ROHC channels". A ROHC
channel can only correspond to one compressor and one decompressor.

> A compressor or decompressor is corresponding to a ROHC channel.
Yes, to exactly one. There is a 1-1-1 mapping between compressor, ROHC
channel and decompressor.

> A ROHC channel could be indentified with the CID.
Well, not really. A ROHC channel has its own CID identifier space, and
within the channel, contexts are identified by different values for 
that CID.


I'll try to think about what can be improved in the draft to avoid 
misunderstandings, but would of course appreciate input on that, based
on your reactions to my answers above.

Cheers,
/L-E

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


From rohc-admin@ietf.org  Wed Jun 19 07:11:08 2002
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 HAA12961
	for <rohc-archive@odin.ietf.org>; Wed, 19 Jun 2002 07:11:08 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA17667;
	Wed, 19 Jun 2002 07:09:07 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA17632
	for <rohc@optimus.ietf.org>; Wed, 19 Jun 2002 07:09:04 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12927
	for <rohc@ietf.org>; Wed, 19 Jun 2002 07:08:23 -0400 (EDT)
Received: from esealnt611.al.sw.ericsson.se (esealnt611.al.sw.ericsson.se [153.88.254.68])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g5JB92rV029309
	for <rohc@ietf.org>; Wed, 19 Jun 2002 13:09:02 +0200 (MEST)
Received: by esealnt611.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <MZTPTL7H>; Wed, 19 Jun 2002 13:09:01 +0200
Message-ID: <A943FD84BD9ED41193460008C791805003E3215F@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Wed, 19 Jun 2002 13:08:52 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [rohc] SigComp documents approved by the IESG
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

Dear SigComp fellows,

All three SigComp documents were last week approved by the IESG, and
fast-tracked RFC numbers have been provided to 3GPP. The numbers are
not supposed to reach a wider audience before the RFC's get published,
and have therefore not been given to authors or chairs. The RFC-Editor
has gotten quite a bit of bother about previous advance numbers (mail
asking where RFC XXXX is, before it has come out), and we should do
our best to reduce that problem.

We expect the secretariat to issue the protocol action announcement
any day now.

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. 

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


From rohc-admin@ietf.org  Wed Jun 19 07:29:25 2002
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 HAA13816
	for <rohc-archive@odin.ietf.org>; Wed, 19 Jun 2002 07:29:25 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18678;
	Wed, 19 Jun 2002 07:28:12 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18644
	for <rohc@optimus.ietf.org>; Wed, 19 Jun 2002 07:28:09 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13480;
	Wed, 19 Jun 2002 07:27:27 -0400 (EDT)
Message-Id: <200206191127.HAA13480@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: Wed, 19 Jun 2002 07:27:26 -0400
Subject: [rohc] I-D ACTION:draft-liao-rohc-notation-00.txt
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Generic Header Compression Notation for ROHC
	Author(s)	: H. Liao et al.
	Filename	: draft-liao-rohc-notation-00.txt
	Pages		: 21
	Date		: 18-Jun-02
	
This draft describes the framework of the generic header compression 
notation (ROHC-GN).  
The goal of Robust Header Compression (ROHC) is to develop generic 
header compression schemes that perform well over links with high 
error rates and long roundtrip times. ROHC will develop multiple 
compression schemes, for example, ROHC-RTP, ROHC-TCP [ROHC-TCP], 
ROHC-SCTP [ROHC-SCTP], etc.  
Our proposed generic header compression notation will describe the 
header fields that are to be compressed, and the information to be 
transmitted in the compressed header. Using this notation and the 
corresponding encoding methods, we can have a toolbox to standardize 
future ROHC profiles.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-liao-rohc-notation-00.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-liao-rohc-notation-00.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-liao-rohc-notation-00.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:	<20020618132102.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-liao-rohc-notation-00.txt

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

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

--OtherAccess--

--NextPart--



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


From rohc-admin@ietf.org  Fri Jun 21 01:55:49 2002
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 BAA23220
	for <rohc-archive@odin.ietf.org>; Fri, 21 Jun 2002 01:55:49 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA21934;
	Fri, 21 Jun 2002 01:51:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA21902
	for <rohc@optimus.ietf.org>; Fri, 21 Jun 2002 01:51:30 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23131
	for <rohc@ietf.org>; Fri, 21 Jun 2002 01:50:47 -0400 (EDT)
Received: from lt.eth.ericsson.se (lt.eth.ericsson.se [164.48.158.205])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g5L5pRrU021944
	for <rohc@ietf.org>; Fri, 21 Jun 2002 07:51:27 +0200 (MEST)
Received: from seneca.eth.ericsson.se by lt.eth.ericsson.se (8.8.8+Sun/SMI-SVR4)
	id HAA06470; Fri, 21 Jun 2002 07:51:25 +0200 (MET DST)
Received: from seneca (seneca [159.107.197.158])
	by seneca.eth.ericsson.se (8.10.2+Sun/8.8.8) with SMTP id g5L5pNL04717
	for <rohc@ietf.org>; Fri, 21 Jun 2002 07:51:23 +0200 (MEST)
Message-Id: <200206210551.g5L5pNL04717@seneca.eth.ericsson.se>
Date: Fri, 21 Jun 2002 07:51:23 +0200 (MEST)
From: Zoltan Barczikay <Zoltan.Barczikay@eth.ericsson.se>
Reply-To: Zoltan Barczikay <Zoltan.Barczikay@eth.ericsson.se>
To: rohc@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: FmLkNWnpKD3/1zlUJhLHSQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Subject: [rohc] SigComp: input_bit_order question...
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

Hello,
I am working on a SigComp implementation.

I know you have discussed already the new "input_bit_order" register,
but I still have a question:

The P bit is valid for all the three instructions: INPUT-BYTES, INPUT-BITS,
INPUT-HUFFMAN. It is clear how it works in the case of INPUT-BYTES.
But what happens eg with INPUT-BITS? 

Suppose that both the P and F bit are set. Suppose we request 3 bits:
"001". Then first we should reverse the bit order because F=1, so we get
the number "100". Then we should store it at a location in UDVM memory,
as hexa 0004, but we should again reverse each byte because P=1.

So in the end we store the two-byte value 0020. (20 is bit-reversed 04.)
Is this correct? Should we reverse it twice if P=F=1?

It would be much simpler if the P bit influenced only the INPUT-BYTES, 
but its not the case.


Thanks in advance for any help,
Zoltan Barczikay.



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


From rohc-admin@ietf.org  Fri Jun 21 06:13:40 2002
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 GAA06114
	for <rohc-archive@odin.ietf.org>; Fri, 21 Jun 2002 06:13:40 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA01880;
	Fri, 21 Jun 2002 06:09:40 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA01847
	for <rohc@optimus.ietf.org>; Fri, 21 Jun 2002 06:09:38 -0400 (EDT)
Received: from rsys000a.roke.co.uk (rsys000a.roke.co.uk [193.118.201.102])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA06055
	for <rohc@ietf.org>; Fri, 21 Jun 2002 06:08:53 -0400 (EDT)
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <NJTH3Z41>; Fri, 21 Jun 2002 09:13:01 +0100
Received: from roke.co.uk (itn-pool4.roke.co.uk [193.118.194.54]) by rsys002a.roke.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id MWPNLQ1X; Fri, 21 Jun 2002 09:12:58 +0100
From: "West, Mark (ITN)" <mark.a.west@roke.co.uk>
To: Zoltan Barczikay <Zoltan.Barczikay@eth.ericsson.se>
Cc: rohc@ietf.org
Message-ID: <3D12E00A.1080301@roke.co.uk>
Date: Fri, 21 Jun 2002 09:12:58 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
Subject: Re: [rohc] SigComp: input_bit_order question...
References: <200206210551.g5L5pNL04717@seneca.eth.ericsson.se>
Content-Type: multipart/mixed;
	boundary="------------InterScan_NT_MIME_Boundary"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org


This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Hi Zoltan,

Some comments (and hopefully clarifications), inline.

Cheers,

Mark.

> 
> The P bit is valid for all the three instructions: INPUT-BYTES, INPUT-BITS,
> INPUT-HUFFMAN. It is clear how it works in the case of INPUT-BYTES.
> But what happens eg with INPUT-BITS? 
> 
> Suppose that both the P and F bit are set. Suppose we request 3 bits:
> "001". Then first we should reverse the bit order because F=1, so we get
> the number "100". Then we should store it at a location in UDVM memory,
> as hexa 0004, but we should again reverse each byte because P=1.


When you say that the 3-bits are '001', it's not quite clear what you 
mean.  But I'll come back to that.

Personally, I find talking about 'reversing the bit order' confusing. 
F=1 does *not* mean reverse the bit-order.  F=1 means interpret the bits 
received from the dispatcher as in the order LSB -> MSB.

The P-bit affects data passed from the dispatcher to the INPUT 
instruction.  You certainly don't reverse the data again because of the 
P-bit.  (And you wouldn't reverse each byte independently, anyway).

Let me try an example:

If your current input byte is:
	00100000
If you are reading from the left-most bit, with P = 0, the bits 0, 0, 1 
are passed from the dispatcher to the input instruction.

F=0, these are seen as MSB -> LSB, so you get 001 = 1
F=1, these are seen as LSB -> MSB, so you get 100 = 4

With the same input byte, reading from the bit 3rd from the left, with P 
= 1, the bits 1, 0, 0 are passed from the dispatcher to the input 
instruction, so with the F-bit you get:

F=0, MSB->LSB gives 100 = 4
F=1, LSB->MSB gives 001 = 1

Another way of thinking about this is to see that if the next 3 bits to 
be read appear as 001 in the input byte, then these bits will be 
transferred to the UDVM as 001 if P and F are the same.  However, if P 
and F are different, then the bits need to be reversed (giving 100).

This is just how I think of it, however, and I don't know if anyone else 
will find it helpful!

> 
> So in the end we store the two-byte value 0020. (20 is bit-reversed 04.)
> Is this correct? Should we reverse it twice if P=F=1?
> 
> It would be much simpler if the P bit influenced only the INPUT-BYTES, 
> but its not the case.


Well, it would be much simpler if we didn't have to worry about this 
bit-order business at all!  Unfortunately, the designers of compression 
algorithms have used an eclectic selection of bit formats, which the 
UDVM needs to cope with!

> 
> 
> Thanks in advance for any help,
> Zoltan Barczikay.
> 
> 
> 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
> 


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

(Yes, I do know that my disclaimer is in an attachment.  And, no, I 
didn't ask for it to be that way)

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain;
	name="RMRL-Disclaimer.txt"
Content-Disposition: attachment;
	filename="RMRL-Disclaimer.txt"
Content-Transfer-Encoding: 7bit

The information contained in this e-mail and any attachments is confidential to Roke 
Manor Research Ltd and must not be passed to any third party without permission. This 
communication is for information only and shall not create or change any contractual 
relationship.

--------------InterScan_NT_MIME_Boundary--

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


From rohc-admin@ietf.org  Fri Jun 21 06:46:39 2002
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 GAA06848
	for <rohc-archive@odin.ietf.org>; Fri, 21 Jun 2002 06:46:39 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA03893;
	Fri, 21 Jun 2002 06:42:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA03856
	for <rohc@optimus.ietf.org>; Fri, 21 Jun 2002 06:42:53 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.47])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06756
	for <rohc@ietf.org>; Fri, 21 Jun 2002 06:42:11 -0400 (EDT)
Received: from lt.eth.ericsson.se (lt.eth.ericsson.se [164.48.158.205])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g5LAgnRb021006;
	Fri, 21 Jun 2002 12:42:50 +0200 (MEST)
Received: from seneca.eth.ericsson.se by lt.eth.ericsson.se (8.8.8+Sun/SMI-SVR4)
	id MAA19300; Fri, 21 Jun 2002 12:42:46 +0200 (MET DST)
Received: from seneca (seneca [159.107.197.158])
	by seneca.eth.ericsson.se (8.10.2+Sun/8.8.8) with SMTP id g5LAghL05231;
	Fri, 21 Jun 2002 12:42:43 +0200 (MEST)
Message-Id: <200206211042.g5LAghL05231@seneca.eth.ericsson.se>
Date: Fri, 21 Jun 2002 12:42:43 +0200 (MEST)
From: Zoltan Barczikay <Zoltan.Barczikay@eth.ericsson.se>
Reply-To: Zoltan Barczikay <Zoltan.Barczikay@eth.ericsson.se>
Subject: Re: [rohc] SigComp: input_bit_order question...
To: mark.a.west@roke.co.uk
Cc: rohc@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: j+OQdPVsqOYWJCPqwsfK+Q==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

Mark,
thank you for your answer. Most probably you are right about the P=F=1 case:

> If your current input byte is:
> 	00100000

> ... reading from the bit 3rd from the left, with 
> P = 1, the bits 1, 0, 0 are passed from the dispatcher to the input 
> instruction, so with the F-bit you get:
> 
> F=0, MSB->LSB gives 100 = 4
> F=1, LSB->MSB gives 001 = 1

But carefully re-reading the draft, I come to think that possibly we get

  000 

in this case, as P=1 means that the input byte 0010000 should be read 
starting from the LSB, that is, when requesting 3 bits, we get 000:

  "The P-bit controls the order in which bits are passed from the
   dispatcher to the INPUT instructions. If set to 0, it indicates that
   the bits within an individual byte are passed to the INPUT
   instructions in MSB to LSB order. If it is set to 1, the bits are
   passed in LSB to MSB order."
   
So I think P and F dont simply negate each other.

I have the same problem with P and H. When requesting additional bits
at executing an INPUT-HUFFMAN instruction, when should we reverse
the bits and bytes? 

Possibilities:

1.) We could "build" the whole 16-number first, then apply the P-bit, 
    that is, reverse each of the two bytes in place.
    
2.) We could reverse each byte in place in the dispatcher, before
    chopping them into chunks of bits.
    
Of course, if H=1, we should reverse each chunk of bits before using them,
ie, before comparing them to the upper & lower bounds.

What do ye think?

Zoltan.


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


From rohc-admin@ietf.org  Fri Jun 21 08:08:01 2002
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 IAA09093
	for <rohc-archive@odin.ietf.org>; Fri, 21 Jun 2002 08:08:01 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA07923;
	Fri, 21 Jun 2002 08:04:13 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA07890
	for <rohc@optimus.ietf.org>; Fri, 21 Jun 2002 08:04:11 -0400 (EDT)
Received: from rsys000a.roke.co.uk (rsys000a.roke.co.uk [193.118.201.102])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA08986
	for <rohc@ietf.org>; Fri, 21 Jun 2002 08:03:28 -0400 (EDT)
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <NJTH3ZXH>; Fri, 21 Jun 2002 13:04:01 +0100
Received: from roke.co.uk (itn-pool4.roke.co.uk [193.118.194.54]) by rsys002a.roke.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id NLH7BX77; Fri, 21 Jun 2002 13:03:58 +0100
From: "West, Mark (ITN)" <mark.a.west@roke.co.uk>
To: Zoltan Barczikay <Zoltan.Barczikay@eth.ericsson.se>
Cc: rohc@ietf.org
Message-ID: <3D13162E.70509@roke.co.uk>
Date: Fri, 21 Jun 2002 13:03:58 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
Subject: Re: [rohc] SigComp: input_bit_order question...
References: <200206211042.g5LAghL05231@seneca.eth.ericsson.se>
Content-Type: multipart/mixed;
	boundary="------------InterScan_NT_MIME_Boundary"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org


This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Some more comments...

Zoltan Barczikay wrote:

> Mark,
> thank you for your answer. Most probably you are right about the P=F=1 case:
> 
> 
>>If your current input byte is:
>>	00100000
>>
> 
>>... reading from the bit 3rd from the left, with 
>>P = 1, the bits 1, 0, 0 are passed from the dispatcher to the input 
>>instruction, so with the F-bit you get:
>>
>>F=0, MSB->LSB gives 100 = 4
>>F=1, LSB->MSB gives 001 = 1
>>
> 
> But carefully re-reading the draft, I come to think that possibly we get
> 
>   000 
> 
> in this case, as P=1 means that the input byte 0010000 should be read 
> starting from the LSB, that is, when requesting 3 bits, we get 000:


Yes, if you were to read from *the* least significant bit.  However, 
that's why I said 'reading from the bit 3rd from the left' [i.e. the 
'1'], so that I could use the same input byte.

Probably a confusing example -- sorry!

(If you like, think of the input byte being 00100001...)

> 
>   "The P-bit controls the order in which bits are passed from the
>    dispatcher to the INPUT instructions. If set to 0, it indicates that
>    the bits within an individual byte are passed to the INPUT
>    instructions in MSB to LSB order. If it is set to 1, the bits are
>    passed in LSB to MSB order."
>    
> So I think P and F dont simply negate each other.


No, they don't negate each other.  You have 4 cases, which I could 
describe as:
	P=0, F=0
	P=0, F=1
	P=1, F=0
	P=1, F=1

Or, alternatively
	Read bits left to right, bit order is same
	Read bits left to right, bit order is swapped
	Read bits right to left, bit order is swapped
	Read bits right to left, bit order is same

> 
> I have the same problem with P and H. When requesting additional bits
> at executing an INPUT-HUFFMAN instruction, when should we reverse
> the bits and bytes? 
> 


Yes, the HUFFMAN one caught me out a bit as well!  However, it basically 
follows the same rules, and the rule for combining bits to build the 
Huffman token is explicitly written into the algorithm description.


> Possibilities:
> 
> 1.) We could "build" the whole 16-number first, then apply the P-bit, 
>     that is, reverse each of the two bytes in place.
>     


The P bit is applied first.  It controls the order in which bits are 
read.  You never apply the P-bit after reading data.  I don't understand 
why you're talking about a 16-bit number.  When dealing with inputting 
bits, the number of bits that are reversed (if need be) is the number 
that have been read.


> 2.) We could reverse each byte in place in the dispatcher, before
>     chopping them into chunks of bits.
>     


But you don't actually need to reverse the bytes in the dispatcher, 
although I guess that you could think of it that way.

However, that only manages the P-bit, you still need to apply the H-bit.


> Of course, if H=1, we should reverse each chunk of bits before using them,
> ie, before comparing them to the upper & lower bounds.
> 


Be careful here!

Each read that the INPUT-HUFFMAN instruction performs acts like 
INPUT-BITS (except that it uses the H-bit instead of the F-bit).  So 
imagine I have a INPUT-HUFFMAN instruction that reads 2, then 3 bits, 
for a total possible length of 5 bits.

Then the first read is for 2 bits, which is done exactly as described 
for INPUT-BITS before.  Say this gives us the value '00'.

If this doesn't match, the next 3 bits are read; again, as described for 
INPUT-BITS.  So, this might give us, '100'.

Now, regardless of the P and H bits, each new set of bits are always 
added as the least significant bits (as described in steps 2. and 3. of 
the INPUT-HUFFMAN instruction).  So we now get '00100' as our input to 
compare against the bounds.


> What do ye think?
> 
> Zoltan.
> 


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

(Yes, I do know that my disclaimer is in an attachment.  And, no, I 
didn't ask for it to be that way)

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain;
	name="RMRL-Disclaimer.txt"
Content-Disposition: attachment;
	filename="RMRL-Disclaimer.txt"
Content-Transfer-Encoding: 7bit

The information contained in this e-mail and any attachments is confidential to Roke 
Manor Research Ltd and must not be passed to any third party without permission. This 
communication is for information only and shall not create or change any contractual 
relationship.

--------------InterScan_NT_MIME_Boundary--

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


From rohc-admin@ietf.org  Fri Jun 21 12:52:25 2002
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 MAA21852
	for <rohc-archive@odin.ietf.org>; Fri, 21 Jun 2002 12:52:25 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA23967;
	Fri, 21 Jun 2002 12:51:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA23937
	for <rohc@ns.ietf.org>; Fri, 21 Jun 2002 12:51:34 -0400 (EDT)
Received: from mgw-dax2.ext.nokia.com (mgw-dax2.ext.nokia.com [63.78.179.217])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21810
	for <rohc@ietf.org>; Fri, 21 Jun 2002 12:50:53 -0400 (EDT)
From: zhigang.c.liu@nokia.com
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85])
	by mgw-dax2.ext.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g5LGt1j14468
	for <rohc@ietf.org>; Fri, 21 Jun 2002 11:55:01 -0500 (CDT)
Received: from daebh002.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5b9eec06fdac12f255126@davir02nok.americas.nokia.com>;
 Fri, 21 Jun 2002 11:51:32 -0500
Received: from daebe005.NOE.Nokia.com ([172.18.242.203]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Fri, 21 Jun 2002 11:51:32 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_001_01C21943.E52BDE1C"
Subject: RE: [rohc] additions to ROHC Implementer's Guide
Date: Fri, 21 Jun 2002 11:51:31 -0500
Message-ID: <DE0842B293FC4847992F9EDF8D72E1ED229B75@daebe005.NOE.Nokia.com>
X-MS-Has-Attach: yes
Thread-Topic: [rohc] additions to ROHC Implementer's Guide
Thread-Index: AcIG7Tun2SZ4rNFRQPmisQZxadvAJQSQtlGQ
To: <Peter.Kremer@eth.ericsson.se>, <rohc@ietf.org>
X-OriginalArrivalTime: 21 Jun 2002 16:51:32.0359 (UTC) FILETIME=[E57EC970:01C21943]
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C21943.E52BDE1C
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Peter,

(Now my turn to apologize for the long delay.)

I still think it would be good if you can include the text I=20
proposed in March 22 (attached since it is missing from the=20
email archive). Here are the reasons:

a) It would be helpful if you can look at my text as a whole.
For example, in "Packet updating property in R-mode", there
are logical links between the bullets. "Update packet
updates both compressor/decompressor context" + "an update
packet in R-mode updates ALL header fields" =3D=3D> "less bits
are needed to convey a change", especially fields other than
RTP SN, RTP TS, and IP ID.=20

b) As you pointed out, there may be redundancy with RFC 3095 if=20
one reads bullet by bullet. However, what is missing and thus=20
confuses implementers is the link between them. For a implementer's
guide, it is worthwhile sometime to pay a bit redundancy for clarity.

c) RE implicit update, it would not be good to lump R-mode and
UO-mode together. The are quite different in this regard.
R-mode is very simple: you update ALL header fields. For UO-mode,=20
RTP SN, RTP TS and IP-ID are treated differently than other
fields. And also there are some tricky things about extensions
as clarified in section 4.9 in -00.

d) I think "R-1* packets" deserve a separate section just=20
as "Extension-3 in UO-1* packets" deserves its own. Unlike=20
any other packets, R-1* packets do NOT update ANY header fields,=20
not even RTP SN.=20

Additional comments below.

BR,
Zhigang

> -----Original Message-----
> From: ext Peter Kremer (ETH) [mailto:Peter.Kremer@eth.ericsson.se]
> Sent: May 29, 2002 3:41 AM
> To: Liu Zhigang.C (NRC/Dallas); Rohc (E-mail)
> Subject: RE: [rohc] additions to ROHC Implementer's Guide
>=20
>=20
> Hi Zhigang,
>=20
> Sorry for the long delay...
>=20
> > > >=20
> > > > The updating properties of packets in R-mode can be=20
> > crystallized as
> > > > follows:
> > > >=20
> > > > - An update packet is a packet that carries CRC. It updates both
> > > > compressor context and decompressor context.
> > >=20
> > > I think it's already clear. <clip>
> >=20
> > It is to clarify that update packets update compressor context.
> Since "secure reference principle" is both used for=20
> compression and decompression it means that only a packet=20
> carrying a 7 or 8-bit CRC update the compressor and the=20
> decompressor context.
>=20
> Section 5.5.1.2, 4th paragraph:
> "The secure reference principle is enforced in both=20
> compression and decompression logic..."

See a) and b) above.
=20
> > > > - An update packet in R-mode updates ALL header fields.=20
> > > > If the packet carry information about a field X, X is updated
> > > > using that piece of information. For a field Y that is not=20
> > > > explicitly mentioned, Y is updated by the established function
> > > > from RTP SN to Y: Y =3D f_y(SN) (see ROHC section 3.4 and=20
> 5.5.1.2).
> > >=20
> > > It doesn't relate to R-mode only and I think section 4.7. is=20
> > > about the same problem.
> >=20
> > Note the "ALL" in above statement. Section 4.7 talks only about
> > TS and IP-ID. That is incorrect at least from R-mode perspective.
>=20
> I've updated that section in implementer's guide to be more=20
> general. Now, it's not so specific but maybe more clear and=20
> apply to any field, as well.
>=20
> "4.7.  Implicit updates
>=20
> If an updating packet (i.e. R-0-CRC or UO-0) contains=20
> information about a specific field X (compressed RTP sequence=20
> number, typically), then X is updated according to the=20
> content of that packet.  This packet implicitly updates all=20
> other inferred fields (i.e. RTP timestamp) according to the=20
> current mode and the appropriate mapping function of the=20
> updated and the inferred fields.
>=20
> For example, a UO-0 packet contains the compressed RTP=20
> sequence number (SN).  Such a packet also updates RTP=20
> timestamp and IPv4 ID, implicitly."

See c) above

> > > > - A compressor expects the decompressor to follow above rules
> > > > and use the updated fields as references to decompress=20
> subsequent
> > > > packets. This allows the decompressor context follows the=20
> > compressor=20
> > > > context closely and thus improve efficiency (i.e. less bits are
> > > > needed to convey a change)
> > > >=20
> > > > - Specifically, above applies to R-0-CRC.
> > >=20
> > > I'm afraid I don't understand it. What's the problem if a=20
> > > decompressor follows these rules?
> >=20
> > I guess you meant to say what if "a decompressor does not
> > follow these rules"? The answer is that when a non-SN field=20
> > Y changes irregularly, the compressor needs to calculate how=20
> > many bits need to be sent. For that calculation, the compressor
> > has to know whether Y is updated on the decompressor side by=20
> > previous R-0-CRC packets or not.
>=20
> No. I still ask what the problem is if a decompressor follows=20
> these rules. If nothing then we don't have to clarify anything.

Sorry, I don't follow you. I'm proposing to clarify these rules.
Of course, I don't see problems if the rules are followed.=20
(Otherwise, why did I propose them in the first place?)

> If a decompressor doesn't follows these rules then - in my=20
> opinion - that decompressor isn't a correct implementation of=20
> the spec and you shouldn't use it at all. I think the RFC=20
> need not to tell how to reach the highest possible=20
> compresseion rate in case of a misbehaving implementation.
>=20
> > Sorry, I don't follow you. What you said above is not what=20
> > I'm trying to=20
> > clarify here. The example I give is actually about downward=20
> > state transition,=20
> > not upward. My text here is to clarify that R-1* can be sent=20
> > in *any* state=20
> > except IR. That is not clear in RFC 3095 and has triggered=20
> > many questions
> > in the mailing list. Some people think R-1* can only be sent=20
> > in FO state,
> > which is untrue.
> Sorry, you're right about downward transition.
>=20
> You say that R-1* packets can be sent in FO and SO states.
> Then how can you interpret the last sentence of the second=20
> paragraph in Section 5.5.1.2?
> "In the SO state, R-0* packets will be sent."
>=20
> I think what you suggest is not a clarification but an=20
> interpretation of the RFC, which is opposite to the above=20
> referred text.

I don't know what do you call "Enhanced mode transition procedures".
But anyway, this is one of the loose ends in RFC 3095. Since R-1*=20
does not update anything, it has absolute no effect on the context=20
synchronization procedure in R-mode. The compressor can send R-1*=20
in any state since it leaves no "trace" on the decompressor side.
Like many other things described in your draft, this is one thing
we could have done better when rushing RFC 3095.

> > > > Below lists design goals of R-1*, but an implementer may=20
> > find other=20
> > > > usage scenarios:
> > > >=20
> > > > a) to handle a transient change in packet stream (i.e. a field
> > > > changes its value only in current packet but then reverts back=20
> > > > to its normal pattern). E.g. suddenly appeared extension header.
> > > >=20
> > > > b) to handle the case where a header field always=20
> changes without
> > > > fixed pattern, but not randomly either. E.g. RTP=20
> > timestamp for video
> > > > codecs.
> > > >=20
> > > > c) to reduce the feedback traffic in an update procedure which
> > > > is carried over a channel with long RTT (see ROHC=20
> section 5.5.1.2)
> > > >=20
> > > > d) above also reduces the memory consumption (e.g.=20
> > sliding window size)=20
> > > > on compressor and decompressor side.
> > >=20
> > > I think c) applies to R-mode only,=20
> > > the others are true for the other two modes as well.=20
> >=20
> > What do you mean? The text is about R-1*, which is used in=20
> > R-mode only.=20
> You're right the text is about R-1*, and I wasn't clear enough.
>=20
> I think that a), b) and c) is true for other packets or=20
> extensions that don't update the context. For example an=20
> extension-3 in a UO-1 packet can also handle transient changes.

Not exactly. RE a) and b), if the changes are in RTP TS and IP-ID
how will that be handled in UO-mode and by what packet? As I
explained in c) above, R-mode and UO-mode take quite different
approach. Thus, it would be better to describe them separately.

Also, what do you mean c) "is true for other packets ..."?

> I will add a new section "Design goals for packets and=20
> extensions that do not update the context" or something similar.
>=20
> /Peter
>=20
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
>=20

------_=_NextPart_001_01C21943.E52BDE1C
Content-Type: message/rfc822

X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Received:  from daebh002.NOE.Nokia.com ([172.18.242.232]) by daebe005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966); Fri, 22 Mar 2002 20:01:06 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Received:  from esebh002.NOE.Nokia.com ([172.21.138.77]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779); Fri, 22 Mar 2002 20:01:06 -0600
Received:  from esvir05nok.ntc.nokia.com ([172.21.143.37]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779); Sat, 23 Mar 2002 03:41:46 +0200
Received:  from mgw-x3.nokia.com (unverified) by esvir05nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id <T59cd91f463ac158f250b0@esvir05nok.ntc.nokia.com>; Sat, 23 Mar 2002 03:09:43 +0200
Received:  from optimus.ietf.org (ietf.org [132.151.1.19]) by mgw-x3.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g2N1AVA25532; Sat, 23 Mar 2002 03:10:31 +0200 (EET)
Received:  from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA05587; Fri, 22 Mar 2002 20:09:04 -0500 (EST)
Received:  from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA05564 for <rohc@optimus.ietf.org>; Fri, 22 Mar 2002 20:09:03 -0500 (EST)
Received:  from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05137 for <rohc@ietf.org>; Fri, 22 Mar 2002 20:09:01 -0500 (EST)
content-class: urn:content-classes:message
Subject: [rohc] additions to ROHC Implementer's Guide
Date: Fri, 22 Mar 2002 20:08:07 -0500
Message-ID: <DE0842B293FC4847992F9EDF8D72E1ED24A2CA@daebe005.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: additions to ROHC Implementer's Guide
Thread-Index: AcHSBzEO1TJzmz2wEdaaLwAQpIbXLw==
From: <zhigang.c.liu@nokia.com>
To: <rohc@ietf.org>
Content-Transfer-Encoding: quoted-printable

Hi,

I think below are useful texts to be included in the guide. They
came from my coding experience. Most of them have been discussed in
the ROHC list but considered as too detailed to be included in the
already long RFC 3095. They are also among the "FAQs" in ROHC list.

Zhigang

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Packet updating properties in R-mode
-------------------------------------

The updating properties of packets in R-mode can be crystallized as
follows:

- An update packet is a packet that carries CRC. It updates both
compressor context and decompressor context.

- An update packet in R-mode updates ALL header fields.=20
If the packet carry information about a field X, X is updated
using that piece of information. For a field Y that is not=20
explicitly mentioned, Y is updated by the established function
from RTP SN to Y: Y =3D f_y(SN) (see ROHC section 3.4 and 5.5.1.2).

- A compressor expects the decompressor to follow above rules
and use the updated fields as references to decompress subsequent
packets. This allows the decompressor context follows the compressor=20
context closely and thus improve efficiency (i.e. less bits are
needed to convey a change)

- Specifically, above applies to R-0-CRC.

[zliu: section 4.7 in current draft is not accurate about R-0]

R-1* packets
------------

R-1* packets do not update either compressor context or decompressor
context (see ROHC section 5.2.7). I.e., they are not "remembered" by
either compressor or decompressor. Consequently, an R-1* can be sent=20
by a compressor at any state except IR state. Specifically, a compressor =

may send R-1* packets in SO state and that (alone) does not mean the=20
compressor must transit to FO state.=20

Below lists design goals of R-1*, but an implementer may find other=20
usage scenarios:

a) to handle a transient change in packet stream (i.e. a field
changes its value only in current packet but then reverts back=20
to its normal pattern). E.g. suddenly appeared extension header.

b) to handle the case where a header field always changes without
fixed pattern, but not randomly either. E.g. RTP timestamp for video
codecs.

c) to reduce the feedback traffic in an update procedure which
is carried over a channel with long RTT (see ROHC section 5.5.1.2)

d) above also reduces the memory consumption (e.g. sliding window size)=20
on compressor and decompressor side.


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

------_=_NextPart_001_01C21943.E52BDE1C--

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


From rohc-admin@ietf.org  Sun Jun 23 19:28:17 2002
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 TAA06242
	for <rohc-archive@odin.ietf.org>; Sun, 23 Jun 2002 19:28:16 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA28465;
	Sun, 23 Jun 2002 19:23:13 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA28402
	for <rohc@ns.ietf.org>; Sun, 23 Jun 2002 19:23:09 -0400 (EDT)
Received: from rsys000a.roke.co.uk (rsys000a.roke.co.uk [193.118.201.102])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA06181
	for <rohc@ietf.org>; Sun, 23 Jun 2002 19:22:25 -0400 (EDT)
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <NJTH35WB>; Mon, 24 Jun 2002 00:22:45 +0100
Received: from roke.co.uk (ras_fennel2.roke.co.uk [193.118.206.44]) by rsys002a.roke.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id NLH7B7T1; Mon, 24 Jun 2002 00:22:41 +0100
From: "West, Mark (ITN)" <mark.a.west@roke.co.uk>
To: "Hongbin Liao (Intl Staffing)" <i-hbliao@microsoft.com>,
        Qian Zhang
	 <qianzhang00@hotmail.com>, wwzhu@microsoft.com,
        rohc@ietf.org
Message-ID: <3D158BC7.4020400@roke.co.uk>
Date: Sun, 23 Jun 2002 09:50:15 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="------------InterScan_NT_MIME_Boundary"
Subject: [rohc] Comments on ROHC-GN...
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org


This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Hi Hongbin, et al...

I just saw your draft.  It's... interesting!

(I should probably point out that we have been working on a notation 
draft, as agreed at Minneapolis.  [Yes, I'm behind schedule, but that's 
fairly normal for me!]  Since it's just about done, I hope you won't be 
too dismayed when we submit it?  There's a large degree of commonality, 
but also some issues that need to be discussed...)

Anyway, I have (you may be unsurprised to learn) a few comments.  So,
here goes:

Can you clarify the nature of the mathematics that underly ROHC-GN?

I'm not quite sure why there is an example of the description of an IPv6 
header in the 'original' EPIC-lite input language?

Shouldn't most of the references to EPIC-lite be to an arbitrary set of 
'encoding rules' (except as an example)?  My understanding is that the 
notation is supposed to be independent of the encoding rules...

I still don't believe that we've reached any consensus on the separate 
structure/encoding information, as (initially) described in section 4.7. 
  Personally, I find things like having VALUE in the structure and 
encodings section very confusing.

Section 5.1 seems to be entirely about the encoded structure of the 
header and, as such, I don't think belongs in a document about notation.

Regarding the encoding methods:

When you say that the OFFSET method encodes the difference (via the 3rd 
parameter), do you mean that this is treated as LSB encoding of the 
difference?  Could you clarify this?

The 'SCALE-FACTOR' and 'SCALE-REMAINDER' encodings take a scale-factor 
as a parameter.  Where does this parameter come from?

I don't really understand how you can just have an 'INFERRED' encoding; 
surely we would need to define what this actually meanes?

In the SUB-TREE-0 example, the example is a bit odd!  The TCP options 
are bounded by the 'data offset' field.  The options *may* have an end 
flag, but don't rely on it...

I notice that another old favourite of past discussions, FORMAT, has 
gone.  It's not immediately clear to me how you handle the sort of 
scenarios it was designed to cope with: e.g. UDP checksum?

Regarding the example TCP profile:

(I suspect that this needs a bit more tweaking, so I'll confine myself 
to a few of the more obvious points...)

There seems to be a signficant element of repetition in this.  Take for 
example the TCP sequence number.
Let me see if I follow this...
   1/ The seqno is specified as a number of bits in the header
   2/ All the encodings for seqno are listed and given probabilities
      (possibly in combination with other fields)
   3/ All the discrete encoding choices for seqno are listed
      (presumably this is basis on which the encoding choice is made?)
[I assume that the parameters for (2) and (3) have to agree?  i.e. 
LSB(tcp.seqno,20,16384) has to appear in both lists?]
Is that about right?

There seems to be some inconsistency about the position of the 
percentage in the P() method.  (And I'm afraid that I still don't think 
I understand the use of P(x%) on its own..!)

Shouldn't the encodings in the options (e.g. timestamp) have 
probabilities associated with them?  (Only the first bunch of fields in 
the header seem to have probabilities assigned...)

The earlier description of OFFSET gives it 3 parameters?

Personally, I don't believe that the security considerations are 
inherited from ROHC (or rather, ROHC has many more concerns than the 
notation).

Cheers,

Mark.

BTW - I think that it's only fair to add Richard Price's name to the 
acknowledgements at the very least, don't you..?

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

(Yes, I do know that my disclaimer is in an attachment.  And, no, I
didn't ask for it to be that way)


--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain;
	name="RMRL-Disclaimer.txt"
Content-Disposition: attachment;
	filename="RMRL-Disclaimer.txt"
Content-Transfer-Encoding: 7bit

The information contained in this e-mail and any attachments is confidential to Roke 
Manor Research Ltd and must not be passed to any third party without permission. This 
communication is for information only and shall not create or change any contractual 
relationship.

--------------InterScan_NT_MIME_Boundary--

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


From rohc-admin@ietf.org  Sun Jun 23 20:25:33 2002
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 TAA06240
	for <rohc-archive@odin.ietf.org>; Sun, 23 Jun 2002 19:28:16 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA28430;
	Sun, 23 Jun 2002 19:23:11 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA28397
	for <rohc@ns.ietf.org>; Sun, 23 Jun 2002 19:23:09 -0400 (EDT)
Received: from rsys000a.roke.co.uk (rsys000a.roke.co.uk [193.118.201.102])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA06180
	for <rohc@ietf.org>; Sun, 23 Jun 2002 19:22:25 -0400 (EDT)
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <NJTH35WC>; Mon, 24 Jun 2002 00:22:55 +0100
Received: from roke.co.uk (ras_fennel2.roke.co.uk [193.118.206.44]) by rsys002a.roke.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id NLH7B7TF; Mon, 24 Jun 2002 00:22:45 +0100
From: "West, Mark (ITN)" <mark.a.west@roke.co.uk>
To: rohc@ietf.org
Message-ID: <3D15963F.4070000@roke.co.uk>
Date: Sun, 23 Jun 2002 10:34:55 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="------------InterScan_NT_MIME_Boundary"
Subject: [rohc] More notation discussion issues...
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org


This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Hi all,

Here are some more general discussion points raised as a result of my 
own deliberations on notation and from reading Hongbin's notation draft...

So, if you're interested, read on.  If not, don't say you weren't warned!

In Hongbin's ROHC-GN draft, the encoding method HUFFMAN appears.
Now, my immediate reaction was that this makes the notation specific to 
a particular set of encoding rules.  (The draft points out that other 
encodings may be added, but I'm not sure that this is the point).

I thought that the idea was for the notation to describe the behaviour 
of the protocol and then the encoding rules to interpret this and build 
compressed headers out of it.

However, I think that there is an interesting point raised here 
regarding the level of assumptions that can be made about the encoding 
rules.

Ideally, you don't want anything in the notation that is encoding-rule 
specific, but that could be very hard to achieve.  Perhaps we need to 
think about 'classes' of encoding rules, and make sure that the notation 
includes sufficient information that can be ignored, where appropriate, 
by encoding rules that can't make use.

Alternatively, we could try and keep the notation entirely free from 
assumptions about the encoding rules.  This would almost certainly 
require that when mapping from a protocol description to header formats, 
the annotation would have to be augmented by other information required 
by the encoding rules.

Another point concerns the list encodings, which we have discussed before.

Clearly at this point we are simply defining the behaviour of the 
protocol.  We ideally want to assume as little as possible about the 
encoding (as discussed above).

However, when thinking about encoding lists it is natural to think about 
inserting elements in, or deleting elements from a list (c.f. RFC 3095 
list-based encoding and EPIC-lite).  (Otherwise you send the whole list 
when it changes, and that's bad).  Given this I think that you 
inevitably have to have some concept of an 'index'; and this means in 
turn that you aren't going to have a truly unbounded list..?

Practically, I think that this means 'list' encodings should at least 
give some indication of the magnitude of the list, at least as a hint to 
the encoding rules to know how much information is required to 
manipulate the list.

Any thoughts?

Cheers,

Mark.

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

(Yes, I do know that my disclaimer is in an attachment.  And, no, I 
didn't ask for it to be that way)


--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain;
	name="RMRL-Disclaimer.txt"
Content-Disposition: attachment;
	filename="RMRL-Disclaimer.txt"
Content-Transfer-Encoding: 7bit

The information contained in this e-mail and any attachments is confidential to Roke 
Manor Research Ltd and must not be passed to any third party without permission. This 
communication is for information only and shall not create or change any contractual 
relationship.

--------------InterScan_NT_MIME_Boundary--

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


From rohc-admin@ietf.org  Mon Jun 24 01:56:30 2002
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 BAA14078
	for <rohc-archive@odin.ietf.org>; Mon, 24 Jun 2002 01:56:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA21349;
	Mon, 24 Jun 2002 01:52:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA21318
	for <rohc@ns.ietf.org>; Mon, 24 Jun 2002 01:52:33 -0400 (EDT)
Received: from mail-jpn.microsoft.com (mail-jpn.microsoft.com [207.46.71.29])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA13997
	for <rohc@ietf.org>; Mon, 24 Jun 2002 01:51:49 -0400 (EDT)
Received: from jpn-imc-01.fareast.corp.microsoft.com ([157.60.4.29]) by mail-jpn.microsoft.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 24 Jun 2002 14:52:00 +0900
Received: from 157.60.4.29 by jpn-imc-01.fareast.corp.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 24 Jun 2002 14:52:00 +0900
Received: from bjs-msg-01.fareast.corp.microsoft.com ([157.60.72.120]) by jpn-imc-01.fareast.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 24 Jun 2002 14:52:00 +0900
X-MimeOLE: Produced By Microsoft Exchange V6.0.6177.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: [rohc] Comments on ROHC-GN...
Date: Mon, 24 Jun 2002 13:51:58 +0800
Message-ID: <D8B1DF394D228543B41027F0D07F5B1C012661BE@bjs-msg-01.fareast.corp.microsoft.com>
Thread-Topic: [rohc] Comments on ROHC-GN...
Thread-Index: AcIbDRV5qB/q9THtSGmY7WKvuqkwHwAM7UvA
From: "Qian Zhang" <qianz@microsoft.com>
To: "West, Mark (ITN)" <mark.a.west@roke.co.uk>,
        "Hongbin Liao (Intl Staffing)" <i-hbliao@microsoft.com>,
        "Qian Zhang" <qianzhang00@hotmail.com>,
        "Wenwu Zhu" <wwzhu@microsoft.com>, <rohc@ietf.org>
X-OriginalArrivalTime: 24 Jun 2002 05:52:00.0118 (UTC) FILETIME=[41D74160:01C21B43]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id BAA21319
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org
Content-Transfer-Encoding: 8bit

Hi Mark,

Thank you for your comments.
Please find my comments inline as usual...

Regards,
Qian

> 
> (I should probably point out that we have been working on a notation
> draft, as agreed at Minneapolis.  [Yes, I'm behind schedule, but
that's
> fairly normal for me!]  Since it's just about done, I hope you won't
be
> too dismayed when we submit it?  There's a large degree of
commonality,
> but also some issues that need to be discussed...)

[Qian] We do know that you had already been appointed to be the editor
for WG document about generic notation. What we had submitted is only an
individual draft. As I mentioned in the email that I send to you before
this submission, we just want to have a document to clarify the
discussion held in the mailing list, especially the part related to the
notation about the uncompressed packet (the structure of the
uncompressed packet).

As we agreed at the Minneapolis meeting, we will use the generic
notation for various profiles, such as TCP/IP. SCTP/IP, etc. I am now
refining the WG document for ROHC-TCP and plan to deliver a new version
soon. However, seems that it is hard to write the TCP/IP profile without
the basic notation. That is why we submit this draft for generic
notation first. Actually we are looking forward to seeing the notation
you proposed soon.

> Anyway, I have (you may be unsurprised to learn) a few comments.  So,
> here goes:
> 
> Can you clarify the nature of the mathematics that underly ROHC-GN?
> 
> I'm not quite sure why there is an example of the description of an
IPv6
> header in the 'original' EPIC-lite input language?

[Qian] As we agreed in last meeting, the new generic notation will based
on the EPIC-LITE that your group proposed before. Actually, our
individual proposal is also based on you work, as we mentioned in the
draft, 
"Similar as the one proposed in EPIC-LITE [EPIC], the language is
designed to be flexible but at the same time easy to use without
detailed knowledge of the mathematics underlying ROHC-GN." 
The difference is that we want to separate the uncompressed structure
description from the compression notation. In this way, we can obtain
the reference/or label functionality, which was implemented by rather
complex stack management proposed by EPIC-LITE before.


> Shouldn't most of the references to EPIC-lite be to an arbitrary set
of
> 'encoding rules' (except as an example)?  My understanding is that the
> notation is supposed to be independent of the encoding rules...

[Qian] We do agree that notation is independent of encoding rules.
However, it should indicate "how various fields are compressed,
including the encoding methods used for each field, thus the information
to transmit in compressed headers." as Lars-Erik pointed out in the
mailing list.

> I still don't believe that we've reached any consensus on the separate
> structure/encoding information, as (initially) described in section
4.7.
>   Personally, I find things like having VALUE in the structure and
> encodings section very confusing.
> 
> Section 5.1 seems to be entirely about the encoded structure of the
> header and, as such, I don't think belongs in a document about
notation.

[Qian] As I explained in the above and in our draft, "the notation of
uncompressed headers is used to clarify the terms and relations among
different fields in the protocol headers. It also provides the way how
to refer uncompressed fields".

> Regarding the encoding methods:
> 
> When you say that the OFFSET method encodes the difference (via the
3rd
> parameter), do you mean that this is treated as LSB encoding of the
> difference?  Could you clarify this?
> 
> The 'SCALE-FACTOR' and 'SCALE-REMAINDER' encodings take a scale-factor
> as a parameter.  Where does this parameter come from?
> 
> I don't really understand how you can just have an 'INFERRED'
encoding;
> surely we would need to define what this actually meanes?
> 
> In the SUB-TREE-0 example, the example is a bit odd!  The TCP options
> are bounded by the 'data offset' field.  The options *may* have an end
> flag, but don't rely on it...

[Qian] We had noticed that the TCP options can be bounded by the 'data
offset' field. However, as defined in RFC793, "End of Option List: This
option code indicates the end of the option list.  This might not
coincide with the end of the TCP header according to the Data Offset
field.  This is used at the end of all options, not the end of each
option, and need only be used if the end of the options would not
otherwise coincide with the end of the TCP header." That is why we had
introduced three notations, SUB-TREE-0, SUB-TREE-N, and SUB-TREE-LEN to
represent how to compress a sequence of records.

> I notice that another old favourite of past discussions, FORMAT, has
> gone.  It's not immediately clear to me how you handle the sort of
> scenarios it was designed to cope with: e.g. UDP checksum?

[Qian] Thanks for pointing out this. We can add this one. Moreover, we
can add the list notation also, although we can use SUB-TREE-X to
represent the list.

> Regarding the example TCP profile:
> 
> (I suspect that this needs a bit more tweaking, so I'll confine myself
> to a few of the more obvious points...)
> 
> There seems to be a signficant element of repetition in this.  Take
for
> example the TCP sequence number.
> Let me see if I follow this...
>    1/ The seqno is specified as a number of bits in the header
>    2/ All the encodings for seqno are listed and given probabilities
>       (possibly in combination with other fields)
>    3/ All the discrete encoding choices for seqno are listed
>       (presumably this is basis on which the encoding choice is made?)
> [I assume that the parameters for (2) and (3) have to agree?  i.e.
> LSB(tcp.seqno,20,16384) has to appear in both lists?]
> Is that about right?

[Qian] As I clarified before, the seqno is not only specified as a
number of bits in header. The key is to represent the position of the
sequence number field in the TCP/IP header. Using our notation, we can
easily refer to different field in the header, which was implemented by
stack management before.
I am not very quite clear about the question raised in 2/ and 3/. Would
you please clarify this again? 

> There seems to be some inconsistency about the position of the
> percentage in the P() method.  (And I'm afraid that I still don't
think
> I understand the use of P(x%) on its own..!)

[Qian] Good point. Thanks for pointing out this. We will refine this. We
define this notation just to clarify the notation with the indicator
generation methods.
One thing we would like to clarify is that, P(x%) is used to indicate
the probability of other cases which are not listed in the OR-list of
P(<encoding-method>, x%). One can assume the following translation
between P(<e>, x%) | ... | P(?,?) and if-else statements:
	1. P(A,n1%) | P(B,n2%) | P(C,n3%)
		if (A) {		// n1%
		} else if (B) {	// n2%
		} else if (C) {	// n2%
		}
	2. P(A,B,n1%) | P(C,n2%) | P(D,n3%)
		if (A && B) {	// n1%
		} else if (C) {	// n2%
		} else if (D) {	// n3%
		}
	3. P(A,B,n1%) | P(C,n2%) | P(n3%)
		if (A && B) {	// n1%
		} else if (C) {	// n2%
		} else {		// n3%
		}

> Personally, I don't believe that the security considerations are
> inherited from ROHC (or rather, ROHC has many more concerns than the
> notation).

[Qian] Thanks for the comments. I will think it further.

 
> BTW - I think that it's only fair to add Richard Price's name to the
> acknowledgements at the very least, don't you..?

[Qian] Actually our proposal is based on EPIT-LITE. So we acknowledge
all the contributors for EPIC-LITE by default. Here, I would like to
re-emphasize my acknowledgement for all the great work done by EPIC-LITE
again.


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


From rohc-admin@ietf.org  Mon Jun 24 03:44:14 2002
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 DAA24777
	for <rohc-archive@odin.ietf.org>; Mon, 24 Jun 2002 03:44:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA26044;
	Mon, 24 Jun 2002 03:40:09 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA26007
	for <rohc@ns.ietf.org>; Mon, 24 Jun 2002 03:40:07 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.47])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24719;
	Mon, 24 Jun 2002 03:39:24 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g5O7e4Rb009068;
	Mon, 24 Jun 2002 09:40:04 +0200 (MEST)
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.98])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g5O7e3a9026066;
	Mon, 24 Jun 2002 10:40:03 +0300 (EET DST)
Message-ID: <3D16CCD2.909AE477@lmf.ericsson.se>
Date: Mon, 24 Jun 2002 10:40:02 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: sip <sip@ietf.org>, rohc <rohc@ietf.org>
Subject: Re: [rohc] SigComp and SIP
References: <3CD10F64.D62B1E78@lmf.ericsson.se> <3D101E32.6040606@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org
Content-Transfer-Encoding: 7bit

Jonathan,

inline:

Jonathan Rosenberg wrote:
> 
> more old email. So sue me. Responses inline:
> 
> Gonzalo Camarillo wrote:
> > Jonathan,
> 
> >>> A proxy performing Record-Route inspects the Record-Route and the
> >>>   Contact header fields in the response. It looks for the URI of
> >> the
> >>>   next upstream (closer to the user agent client) hop in the route
> >> set.
> >>>   If this URI contains the parameter comp=sigcomp, the proxy SHOULD
> >>add
> >>>   comp=sigcomp to its entry in the Record-Route header field.
> >>
> >>Why? If the upstream element doesn't support this extension, the
> >>sigcomp
> >>parameter is ignored, and the message is sent uncompressed. Thats what
> >>you want. The decision about whether to insert a URI with the comp
> >>parameter should be entirely a local one.
> >
> >
> > This covers the following scenario:
> >
> > UAC----P1-----P2-----UAS
> >
> > The UAC sends an INITE to UAS. P2 records route, but P1 does not.
> > When the 200 OK for the INVITE reaches P2, the contact and RR header
> > fields will look like this:
> >
> > Contact: UAS@domain.com;comp=sigcomp
> > RR: P2
> >
> > If P2 does not add comp=sigcomp to his entry in the RR, UAC will be able
> > to receive compressed traffic (the contact has comp=sigcomp), but will
> > be unable to send compress traffic (the RR entry for P2 does not have
> > it).
> 
> Why doesn't it? If a proxy is sigcomp enabled, it should have
> record-routed with sigcomp parameter in the first place.
> 

If we specified that a proxy that supports SigComp MUST use it,
everything would work as you stated. However, I would like a proxy to
have the possibility of not using SigComp even if it supports it.

Section 7 of:
http://search.ietf.org/internet-drafts/draft-camarillo-sip-compression-01.txt

contains an example about the scenario I was describing in my previous
mail.

Thanks for the comments,

Gonzalo

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


From rohc-admin@ietf.org  Mon Jun 24 03:50:01 2002
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 DAA24871
	for <rohc-archive@odin.ietf.org>; Mon, 24 Jun 2002 03:50:01 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA26246;
	Mon, 24 Jun 2002 03:45:29 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA26217
	for <rohc@ns.ietf.org>; Mon, 24 Jun 2002 03:45:27 -0400 (EDT)
Received: from rsys000a.roke.co.uk (rsys000a.roke.co.uk [193.118.201.102])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA24793
	for <rohc@ietf.org>; Mon, 24 Jun 2002 03:44:41 -0400 (EDT)
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <NJTH3552>; Mon, 24 Jun 2002 08:45:19 +0100
Received: from roke.co.uk (itn-pool4.roke.co.uk [193.118.194.54]) by rsys002a.roke.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id NLH7B8G8; Mon, 24 Jun 2002 08:45:12 +0100
From: "West, Mark (ITN)" <mark.a.west@roke.co.uk>
To: Qian Zhang <qianz@microsoft.com>
Cc: "Hongbin Liao (Intl Staffing)" <i-hbliao@microsoft.com>,
        Qian Zhang
	 <qianzhang00@hotmail.com>,
        Wenwu Zhu <wwzhu@microsoft.com>, rohc@ietf.org
Message-ID: <3D16CE08.7090502@roke.co.uk>
Date: Mon, 24 Jun 2002 08:45:12 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
Subject: Re: [rohc] Comments on ROHC-GN...
References: <D8B1DF394D228543B41027F0D07F5B1C012661BE@bjs-msg-01.fareast.corp.microsoft.com>
Content-Type: multipart/mixed;
	boundary="------------InterScan_NT_MIME_Boundary"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org


This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Hi Qian,

Thanks very much for these clarifications!  Some of my comments were 
clearly based on mistaken assumptions.  A couple more points in-line...

Cheers,

Mark.


 >
 > [Qian] We do know that you had already been appointed to be the
 > editor for WG document about generic notation. What we had
 > submitted is only an individual draft. As I mentioned in the email
 > that I send to you before this submission, we just want to have a
 > document to clarify the discussion held in the mailing list,
 > especially the part related to the notation about the uncompressed
 > packet (the structure of the uncompressed packet).
 >

That makes sense -- certainly this strikes me as one of the unresolved 
questions that we need to address.

 >
 >
 >> Shouldn't most of the references to EPIC-lite be to an arbitrary
 >> set of
 >> 'encoding rules' (except as an example)?  My understanding is that
 >>  the notation is supposed to be independent of the encoding
 >> rules...
 >>
 >
 > [Qian] We do agree that notation is independent of encoding rules. 
However,
 >  it should indicate "how various fields are compressed, including
 > the encoding methods used for each field, thus the information to
 > transmit in compressed headers." as Lars-Erik pointed out in the mailing
 >  list.
 >

I think that I'd like to draw a distinction between how fields are 
compressed (e.g. LSB encoding) and how the bits that result from that 
are represented 'on the wire'.  Maybe this is just a terminology 
problem, but I think of EPIC-lite as being fundamentally about the 
latter.  (Which I guess is partly why we're splitting off the notation 
to avoid confusion!)

 >
 > [Qian] We had noticed that the TCP options can be bounded by the 'data
 > offset' field. However, as defined in RFC793, "End of Option List: This
 > option code indicates the end of the option list.  This might not
 > coincide with the end of the TCP header according to the Data Offset
 > field.  This is used at the end of all options, not the end of each
 > option, and need only be used if the end of the options would not
 > otherwise coincide with the end of the TCP header." That is why we had
 > introduced three notations, SUB-TREE-0, SUB-TREE-N, and SUB-TREE-LEN to
 > represent how to compress a sequence of records.
 >

This isn't really directly relevant to a discussion of the notation, so 
we should probably take this thread elsewhere!  However, I don't think 
that you can bound the option list with the 'End of Option List' code.

 >>
 >>There seems to be a signficant element of repetition in this.  Take
 >>for
 >>example the TCP sequence number.
 >>Let me see if I follow this...
 >>   1/ The seqno is specified as a number of bits in the header
 >>   2/ All the encodings for seqno are listed and given probabilities
 >>      (possibly in combination with other fields)
 >>   3/ All the discrete encoding choices for seqno are listed
 >>      (presumably this is basis on which the encoding choice is made?)
 >>[I assume that the parameters for (2) and (3) have to agree?  i.e.
 >>LSB(tcp.seqno,20,16384) has to appear in both lists?]
 >>Is that about right?
 >>
 >
 > [Qian] As I clarified before, the seqno is not only specified as a
 > number of bits in header. The key is to represent the position of the
 > sequence number field in the TCP/IP header. Using our notation, we can
 > easily refer to different field in the header, which was implemented by
 > stack management before.
 > I am not very quite clear about the question raised in 2/ and 3/. Would
 > you please clarify this again?
 >

I probably ought to go and think about this some more, but:

All I'm really saying is that it appears, from the example, that the 
encodings for the TCP sequence number appear both with and without a P() 
wrapper method.  I was just trying to work out what the difference was 
between these two cases...

 >
 > [Qian] Good point. Thanks for pointing out this. We will refine this. We
 > define this notation just to clarify the notation with the indicator
 > generation methods.
 > One thing we would like to clarify is that, P(x%) is used to indicate
 > the probability of other cases which are not listed in the OR-list of
 > P(<encoding-method>, x%). One can assume the following translation
 > between P(<e>, x%) | ... | P(?,?) and if-else statements:
 >

Ok, thanks for the clarification.

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

(Yes, I do know that my disclaimer is in an attachment.  And, no, I
didn't ask for it to be that way)

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain;
	name="RMRL-Disclaimer.txt"
Content-Disposition: attachment;
	filename="RMRL-Disclaimer.txt"
Content-Transfer-Encoding: 7bit

The information contained in this e-mail and any attachments is confidential to Roke 
Manor Research Ltd and must not be passed to any third party without permission. This 
communication is for information only and shall not create or change any contractual 
relationship.

--------------InterScan_NT_MIME_Boundary--

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


From rohc-admin@ietf.org  Mon Jun 24 08:31:31 2002
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 IAA03343
	for <rohc-archive@odin.ietf.org>; Mon, 24 Jun 2002 08:31:31 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA12844;
	Mon, 24 Jun 2002 08:30:40 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA03144
	for <rohc@ns.ietf.org>; Sun, 23 Jun 2002 21:45:12 -0400 (EDT)
Received: from cwcsun41.cwc.nus.edu.sg (cwcsun41.cwc.nus.edu.sg [137.132.163.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08351
	for <rohc@ietf.org>; Sun, 23 Jun 2002 21:44:22 -0400 (EDT)
Received: from 827300975.icr.a-star.edu.sg (cosmos00601df708d0.cwc.nus.edu.sg [172.16.3.209])
	by cwcsun41.cwc.nus.edu.sg (8.9.3/8.9.3) with ESMTP id JAA29502
	for <rohc@ietf.org>; Mon, 24 Jun 2002 09:43:40 +0800 (SGT)
Message-Id: <4.3.2.7.2.20020624092303.00d095e0@postman.cwc.nus.edu.sg>
X-Sender: chankm@postman.cwc.nus.edu.sg
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 24 Jun 2002 09:54:49 +0800
To: rohc@ietf.org
From: Chan Kwang Mien <chankm@icr.a-star.edu.sg>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [rohc] Queries on SigComp Feedback
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

Hi,

I am currently implementing SigComp.

I have a few queries about the Feedback mechanism as stated in
draft-ietf-rohc-sigcomp-07.txt.

a) I am not sure where the Request Feedback item should be located.
According to the format of the SigComp Message, it does not
show where the Request Feedback item should be in. The SigComp
message format only shows the Returned Feedback item. Moreover,
the 'T' bit shows whether a Returned Feedback item exists or not.


b) In Section 9.4.9 of the draft, it states

"Note that the formats of Figure 12 and Figure 13 are only for local
presentation of the feedback data on the interface between the UDVM
and state handler. The formats do not mandate any bits on the wire;"

Does it mean that the UDVM does not need to follow the format as shown
in Figure 13 when returning the SigComp parameters ? Shouldn't we
have a fixed format for Returned SigComp Parameters for all SigComp
implementation to follow when returning feedback ? Or else, wouldn't there
be interoperability problem ? there should also be a standard format for
the Request Feedback item.


Any help would be much appreciated.

regards,
Kwang Mien








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


From rohc-admin@ietf.org  Mon Jun 24 11:26:44 2002
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 LAA11886
	for <rohc-archive@odin.ietf.org>; Mon, 24 Jun 2002 11:26:44 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21517;
	Mon, 24 Jun 2002 11:25:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21486
	for <rohc@optimus.ietf.org>; Mon, 24 Jun 2002 11:25:39 -0400 (EDT)
Received: from mgw-dax2.ext.nokia.com (mgw-dax2.ext.nokia.com [63.78.179.217])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11825
	for <rohc@ietf.org>; Mon, 24 Jun 2002 11:24:52 -0400 (EDT)
From: EXT-Narendra.Chaparala@nokia.com
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
	by mgw-dax2.ext.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g5OFT5j27557
	for <rohc@ietf.org>; Mon, 24 Jun 2002 10:29:05 -0500 (CDT)
Received: from daebh002.NOE.Nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5bae106177ac12f257126@davir04nok.americas.nokia.com>;
 Mon, 24 Jun 2002 10:25:33 -0500
Received: from daebe008.NOE.Nokia.com ([172.18.242.238]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 24 Jun 2002 10:24:40 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [rohc] Queries on SigComp Feedback
Date: Mon, 24 Jun 2002 10:24:40 -0500
Message-ID: <7CA3477F476D7F4FB82F02960B79CEBD6E8730@daebe008.NOE.Nokia.com>
Thread-Topic: [rohc] Queries on SigComp Feedback
Thread-Index: AcIbexuj+4E5nKIsTZ+ETPZgOdoDXgAFvjjQ
To: <chankm@icr.a-star.edu.sg>, <rohc@ietf.org>
X-OriginalArrivalTime: 24 Jun 2002 15:24:40.0751 (UTC) FILETIME=[425FC3F0:01C21B93]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA21487
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org
Content-Transfer-Encoding: 8bit

Hi,
 requested feed back is sent in the byte code, with END_MESSAGE instruction. the first parameter in END_MESSAGE instruction (requested_feedback_location) will have the address of udvm buffer, where the requested feedback is present. At that locaion, the format of the requested feedback is same as what is described in Fig 12. 

-narendra

-----Original Message-----
From: ext Chan Kwang Mien [mailto:chankm@icr.a-star.edu.sg]
Sent: 23 June, 2002 08:55 PM
To: rohc@ietf.org
Subject: [rohc] Queries on SigComp Feedback


Hi,

I am currently implementing SigComp.

I have a few queries about the Feedback mechanism as stated in
draft-ietf-rohc-sigcomp-07.txt.

a) I am not sure where the Request Feedback item should be located.
According to the format of the SigComp Message, it does not
show where the Request Feedback item should be in. The SigComp
message format only shows the Returned Feedback item. Moreover,
the 'T' bit shows whether a Returned Feedback item exists or not.


b) In Section 9.4.9 of the draft, it states

"Note that the formats of Figure 12 and Figure 13 are only for local
presentation of the feedback data on the interface between the UDVM
and state handler. The formats do not mandate any bits on the wire;"

Does it mean that the UDVM does not need to follow the format as shown
in Figure 13 when returning the SigComp parameters ? Shouldn't we
have a fixed format for Returned SigComp Parameters for all SigComp
implementation to follow when returning feedback ? Or else, wouldn't there
be interoperability problem ? there should also be a standard format for
the Request Feedback item.


Any help would be much appreciated.

regards,
Kwang Mien








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

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


From rohc-admin@ietf.org  Mon Jun 24 16:12:09 2002
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 QAA27922
	for <rohc-archive@odin.ietf.org>; Mon, 24 Jun 2002 16:12:09 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA08301;
	Mon, 24 Jun 2002 16:11:08 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA08261
	for <rohc@optimus.ietf.org>; Mon, 24 Jun 2002 16:11:05 -0400 (EDT)
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27840;
	Mon, 24 Jun 2002 16:10:21 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.192])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g5OKAWYH021658;
	Mon, 24 Jun 2002 16:10:32 -0400 (EDT)
Message-ID: <3D177CB8.7070403@dynamicsoft.com>
Date: Mon, 24 Jun 2002 16:10:32 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
CC: sip <sip@ietf.org>, rohc <rohc@ietf.org>
Subject: Re: [rohc] SigComp and SIP
References: <3D16CCD2.909AE477@lmf.ericsson.se>
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-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org
Content-Transfer-Encoding: 7bit



Gonzalo Camarillo wrote:
> Jonathan,
> 
> inline:
> 
> Jonathan Rosenberg wrote:
> 
>>more old email. So sue me. Responses inline:
>>
>>Gonzalo Camarillo wrote:
>>
>>>Jonathan,
>>
>>>>>A proxy performing Record-Route inspects the Record-Route and the
>>>>>  Contact header fields in the response. It looks for the URI of
>>>>
>>>>the
>>>>
>>>>>  next upstream (closer to the user agent client) hop in the route
>>>>
>>>>set.
>>>>
>>>>>  If this URI contains the parameter comp=sigcomp, the proxy
>>>>
> SHOULD
> 
>>>>add
>>>>
>>>>>  comp=sigcomp to its entry in the Record-Route header field.
>>>>
>>>>Why? If the upstream element doesn't support this extension, the
>>>>sigcomp
>>>>parameter is ignored, and the message is sent uncompressed. Thats
>>>
> what
> 
>>>>you want. The decision about whether to insert a URI with the comp
>>>>parameter should be entirely a local one.
>>>
>>>
>>>This covers the following scenario:
>>>
>>>UAC----P1-----P2-----UAS
>>>
>>>The UAC sends an INITE to UAS. P2 records route, but P1 does not.
>>>When the 200 OK for the INVITE reaches P2, the contact and RR header
>>>fields will look like this:
>>>
>>>Contact: UAS@domain.com;comp=sigcomp
>>>RR: P2
>>>
>>>If P2 does not add comp=sigcomp to his entry in the RR, UAC will be
>>
> able
> 
>>>to receive compressed traffic (the contact has comp=sigcomp), but
>>
> will
> 
>>>be unable to send compress traffic (the RR entry for P2 does not
>>
> have
> 
>>>it).
>>
>>Why doesn't it? If a proxy is sigcomp enabled, it should have
>>record-routed with sigcomp parameter in the first place.
>>
> 
> 
> If we specified that a proxy that supports SigComp MUST use it,
> everything would work as you stated. However, I would like a proxy to
> have the possibility of not using SigComp even if it supports it.
> 
> Section 7 of:
> http://search.ietf.org/internet-drafts/draft-camarillo-sip-compression-0
> 1.txt
> 
> contains an example about the scenario I was describing in my previous
> mail.

Well, you are trying to achieve the (somewhat odd) goal of allowing the 
proxy to indicate that it would prefer not to use sigcomp, unless 
someone around it doesn't record-route, so that sigcomp would be needed 
in order to avoid unidirectional compression. Is there a reason for 
supporting this case? For any individual dialog, either a proxy 
indicates it can do compression, or it doesn't. I don't see the need for 
this case, and it complicates what is otherwise a fairly simple and 
elegant solution.

-Jonathan R.




-- 
Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
Chief Scientist                         First Floor
dynamicsoft                             East Hanover, NJ 07936
jdrosen@dynamicsoft.com                 FAX: (973) 952-5050
http://www.jdrosen.net                  PH:  (973) 952-5000
http://www.dynamicsoft.com


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


From rohc-admin@ietf.org  Mon Jun 24 17:19:19 2002
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 RAA01537
	for <rohc-archive@odin.ietf.org>; Mon, 24 Jun 2002 17:19:18 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA15543;
	Mon, 24 Jun 2002 17:16:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA15515
	for <rohc@optimus.ietf.org>; Mon, 24 Jun 2002 17:16:50 -0400 (EDT)
Received: from tokyo.ccrle.nec.de (tokyo.ccrle.nec.de [195.37.70.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01422
	for <rohc@ietf.org>; Mon, 24 Jun 2002 17:16:05 -0400 (EDT)
Received: from wallace.heidelberg.ccrle.nec.de (root@wallace.heidelberg.ccrle.nec.de [192.168.102.1])
	by tokyo.ccrle.nec.de (8.11.6/8.11.6) with ESMTP id g5OLGGK85887
	for <rohc@ietf.org>; Mon, 24 Jun 2002 23:16:17 +0200 (CEST)
	(envelope-from quittek@ccrle.nec.de)
Received: from [192.168.102.31] ([192.168.102.31])
	by wallace.heidelberg.ccrle.nec.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id XAA20142
	for <rohc@ietf.org>; Mon, 24 Jun 2002 23:11:17 +0200
Date: Mon, 24 Jun 2002 23:11:15 +0200
From: Juergen Quittek <quittek@ccrle.nec.de>
To: rohc@ietf.org
Message-ID: <7125846.1024960275@[192.168.102.31]>
X-Mailer: Mulberry/2.1.2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Subject: [rohc] ROHC statistics
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org
Content-Transfer-Encoding: 7bit

Dear all,

I am still looking for suggestions on the statistics
to be collected for monitoring ROHC systems with the
ROHC MIB module:

  - What statistics do you collect with your
    implementation?
  - What statistics would be desirable to provide for
    ROHC operation and maintenance?
  - What statistics would be helpful for fault analysis?
  - What statistics were useful at ROHC interop events?

Please provide your input!

The current version of the MIB module collects the
following statistics:

Per compressor:
    total number of sent packets
        number of sent packets per header type
    number of received ACKs
    number of received NACKs
    number of received SNACKs
    mean compression ratio over all packets
    mean compression ratio over the last 16 packets

Per decompressor:
    number of received packets
        number of received packets per header type
    number of sent ACKs
    number of sent NACKs
    number of sent SNACKs

Collecting the number of packets per header type might
not be a good idea in some cases. Do you have better
ideas?

    Juergen
-- 
Juergen Quittek     quittek@ccrle.nec.de     Tel: +49 6221 90511-15
NEC Europe Ltd.,    Network Laboratories     Fax: +49 6221 90511-55
Adenauerplatz 6, 69115 Heidelberg, Germany   http://www.ccrle.nec.de

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


From rohc-admin@ietf.org  Mon Jun 24 17:46:28 2002
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 RAA03305
	for <rohc-archive@odin.ietf.org>; Mon, 24 Jun 2002 17:46:28 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA18779;
	Mon, 24 Jun 2002 17:44:20 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA18748
	for <rohc@optimus.ietf.org>; Mon, 24 Jun 2002 17:44:18 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03054;
	Mon, 24 Jun 2002 17:43:31 -0400 (EDT)
Message-Id: <200206242143.RAA03054@ietf.org>
To: IETF-Announce: ;
Cc: RFC Editor <rfc-editor@isi.edu>, Internet Architecture Board <iab@isi.edu>,
        rohc@ietf.org
From: The IESG <iesg-secretary@ietf.org>
Date: Mon, 24 Jun 2002 17:43:31 -0400
Subject: [rohc] Protocol Action: Signaling Compression to Proposed Standard
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org



The IESG has approved the Internet-Draft 'Signaling Compression'
<draft-ietf-rohc-sigcomp-07.txt> as a Proposed Standard.

In the same action, the following Internet-Drafts were approved for
publication as Informational RFCs:

o SigComp - Extended Operations
	<draft-ietf-rohc-sigcomp-extended-04.txt>
o Signaling Compression Requirements & Assumptions
	<draft-ietf-rohc-signaling-req-assump-06.txt>



These documents are the product of the Robust Header Compression
Working Group.  The IESG contact persons are Allison Mankin and Scott
Bradner.

 
Technical Summary
 
      Many application protocols used for multimedia communications are
      text-based and have not been optimized in terms of size. For
      example, typical SIP messages range from a few hundred bytes up
      to two thousand bytes or more.

      With the planned usage of these protocols in wireless handsets as
      part of 2.5G and 3G cellular networks, the large message size is
      problematic, especially because of transmisssion delay concerns.
      Taking into account retransmissions, and the multiplicity
      of messages that are required in some flows, call setup
      and feature invocation are adversely affected. SigComp provides a
      means to eliminate this problem by offering robust, lossless
      compression of application messages.

      The Sigcomp document presents the architecture and pre-requisites of the
      SigComp solution, the format of the SigComp message and the Universal
      Decompressor Virtual Machine (UDVM) that provides decompression
      functionality. Arbitary applications ar supported by transferring
      a well-formed UDVM for the use of a flow or flows from the sender
      to the receiver.

      SigComp is offered to applications as a layer between the application
      and an underlying transport. The service provides is that of the
      underlying transport plus compression. SigComp supports a wide range
      of transports including TCP, UDP and SCTP [RFC-2960].

      The two informational drafts provide background to the design
      (requirements) and a set of optimization techniques for UDVM
      construction (extended operations) that may either be adopted by
      implementations or used as a model for optimizations to be
      added in future.
 
Working Group Summary
 
  The working group had strong agreement to advance these drafts.
 
Protocol Quality

    No problems were found during IETF Last Call. There have been
    two independent prototyping developments of sigcomp, with
    resuls of both the protocol and interoperation tests being
    fed into the working group effort before last call. Allison
    Mankin reviewed the documents for the IESG.

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


From rohc-admin@ietf.org  Tue Jun 25 04:18:10 2002
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 EAA26185
	for <rohc-archive@odin.ietf.org>; Tue, 25 Jun 2002 04:18:10 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA24863;
	Tue, 25 Jun 2002 04:13:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA24830
	for <rohc@optimus.ietf.org>; Tue, 25 Jun 2002 04:13:13 -0400 (EDT)
Received: from rsys000a.roke.co.uk (rsys000a.roke.co.uk [193.118.201.102])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA26111
	for <rohc@ietf.org>; Tue, 25 Jun 2002 04:12:26 -0400 (EDT)
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <NJTH36RH>; Tue, 25 Jun 2002 09:12:49 +0100
Received: from roke.co.uk (itn-pool4.roke.co.uk [193.118.194.54]) by rsys002a.roke.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id NLH7CDHX; Tue, 25 Jun 2002 09:12:42 +0100
From: "West, Mark (ITN)" <mark.a.west@roke.co.uk>
To: Juergen Quittek <quittek@ccrle.nec.de>
Cc: rohc@ietf.org
Message-ID: <3D1825FA.8070504@roke.co.uk>
Date: Tue, 25 Jun 2002 09:12:42 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
Subject: Re: [rohc] ROHC statistics
References: <7125846.1024960275@[192.168.102.31]>
Content-Type: multipart/mixed;
	boundary="------------InterScan_NT_MIME_Boundary"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org


This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Hi Juergen,

At least some partial answers, inline...

Cheers,

Mark.


Juergen Quittek wrote:

> Dear all,
> 
> I am still looking for suggestions on the statistics
> to be collected for monitoring ROHC systems with the
> ROHC MIB module:
> 
>  - What statistics do you collect with your
>    implementation?


Not many!  Packet counts; average compressed packet size; decompression 
failures / context repairs; that sort of thing.  We tend to maintain 
these per-CID, but then for the sort of testing we're doing at the 
moment, we don't tend to have many active CIDs.

>  - What statistics would be desirable to provide for
>    ROHC operation and maintenance?


Probably ought to be something about CID usage -- number of flows and/or 
a high water mark?

I'll think about this one a bit more...

>  - What statistics would be helpful for fault analysis?


Hmmm... I suppose the most obvious one is the number of packets in and 
out (which at least tells you whether or not your ROHC instance is doing 
*something*)!  Counts of failed decompressions / received nacks gives 
some additional information.

I think knowing about failed decompression

Not so much a 'fault', but it might help to know the number of IR/IR-DYN 
packets per flow -- a high number of IR-DYN packets could indicate that 
the wrong profile is being used?

>  - What statistics were useful at ROHC interop events?


To be honest (and I can only spesak for myself, obviously), we haven't 
had the luxury of such abstract notions as statistics!  Generally we've 
been working with log-files; often at the level of individual bits...

If I were to extrapolate from the sorts of things that we look for in a 
logfile (at a relatively high level), then I suppose that this would be 
things like different packet types used (however, I'm not sure that this 
is actually a useful statistic to collect -- plus, see below...)


> 
> Please provide your input!
> 


It's not much, but it's a start...


> The current version of the MIB module collects the
> following statistics:
> 
> Per compressor:
>    total number of sent packets
>        number of sent packets per header type
>    number of received ACKs
>    number of received NACKs
>    number of received SNACKs
>    mean compression ratio over all packets
>    mean compression ratio over the last 16 packets
> 
> Per decompressor:
>    number of received packets
>        number of received packets per header type
>    number of sent ACKs
>    number of sent NACKs
>    number of sent SNACKs
> 
> Collecting the number of packets per header type might
> not be a good idea in some cases. Do you have better
> ideas?
> 


I agree that collecting stats per header-type is probably not a good 
idea (or, at least, could lead to a very large amount of data with 
questionable value).  As suggested above, though, a more coarse-grained 
approach might be useful, e.g. to see how many IR/IR-DYN/CO packets have 
been sent.

At the decompressor, I think that it would useful to information about 
decompression failures (and context repair attempts) as well as the 
counts of acks/nacks/snacks.

I wonder if 'compression ratio' is the most useful statistic? 
Uncompressed headers can be variable length, so it might be hard to tell 
from just the ratio what my actual header overhead was.  Maybe 'mean 
uncompressed size' and 'mean compressed size' would be useful instead of 
/ as well?


>    Juergen


Just my immediate thoughts, to get the ball rolling!

More later...

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

(Yes, I do know that my disclaimer is in an attachment.  And, no, I 
didn't ask for it to be that way)

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain;
	name="RMRL-Disclaimer.txt"
Content-Disposition: attachment;
	filename="RMRL-Disclaimer.txt"
Content-Transfer-Encoding: 7bit

The information contained in this e-mail and any attachments is confidential to Roke 
Manor Research Ltd and must not be passed to any third party without permission. This 
communication is for information only and shall not create or change any contractual 
relationship.

--------------InterScan_NT_MIME_Boundary--

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


From rohc-admin@ietf.org  Tue Jun 25 04:23:40 2002
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 EAA26279
	for <rohc-archive@odin.ietf.org>; Tue, 25 Jun 2002 04:23:39 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA25021;
	Tue, 25 Jun 2002 04:19:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA24987
	for <rohc@optimus.ietf.org>; Tue, 25 Jun 2002 04:19:49 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.47])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26213;
	Tue, 25 Jun 2002 04:19:04 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g5P8JjRb029620;
	Tue, 25 Jun 2002 10:19:45 +0200 (MEST)
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.98])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g5P8Jja9005379;
	Tue, 25 Jun 2002 11:19:45 +0300 (EET DST)
Message-ID: <3D1827A0.3D0AE8C2@lmf.ericsson.se>
Date: Tue, 25 Jun 2002 11:19:44 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: sip <sip@ietf.org>, rohc <rohc@ietf.org>
Subject: Re: [rohc] SigComp and SIP
References: <3D16CCD2.909AE477@lmf.ericsson.se> <3D177CB8.7070403@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org
Content-Transfer-Encoding: 7bit

Hello,

Jonathan Rosenberg wrote:
> Well, you are trying to achieve the (somewhat odd) goal of allowing the
> proxy to indicate that it would prefer not to use sigcomp, unless
> someone around it doesn't record-route, so that sigcomp would be needed
> in order to avoid unidirectional compression. Is there a reason for
> supporting this case? For any individual dialog, either a proxy
> indicates it can do compression, or it doesn't. I don't see the need for
> this case, and it complicates what is otherwise a fairly simple and
> elegant solution.
> 

The trade-off we have is the following:

If we go for the simplest mechanism, every time two adjacent proxies
support SigComp, they will exchange compressed messages. This means that
when two wireless terminals exchange SIP signalling thru a set of
SigComp capable proxies, all the messages will be compressed, even
between proxies.

We can avoid this and make that compression is used only over the air
interface (i.e., not between the proxies in our example), but we have to
have proxies inspect Record-Route header fields.


If folks think that it is OK that two proxies that support SigComp MUST
always exhange compressed messages, I will be glad to simplify the
draft. If people feel that compressing when it is not really needed is
unacceptable, we will keep the current Record-Route inspection
mechanism.

Personally, if nobody has big concerns about performance of precessing
power, I would suggest that we simplify the mechanism and make it
mandatory the use of compression for all entities that support SigComp
(as suggested by Jonathan).

Regards,

Gonzalo

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


From rohc-admin@ietf.org  Tue Jun 25 11:24:08 2002
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 LAA10344
	for <rohc-archive@odin.ietf.org>; Tue, 25 Jun 2002 11:24:08 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA17735;
	Tue, 25 Jun 2002 11:23:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA17680
	for <rohc@optimus.ietf.org>; Tue, 25 Jun 2002 11:23:01 -0400 (EDT)
Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10258;
	Tue, 25 Jun 2002 11:22:17 -0400 (EDT)
Received: from DYN-EXCH-001.dynamicsoft.com (dyn-exch-001 [63.113.44.7])
	by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id g5PFMJN7009988;
	Tue, 25 Jun 2002 11:22:19 -0400 (EDT)
Received: by DYN-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <NDQAWJ70>; Tue, 25 Jun 2002 11:22:26 -0400
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F377A25B@DYN-TX-EXCH-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>,
        Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Cc: sip <sip@ietf.org>, rohc <rohc@ietf.org>
Subject: RE: [rohc] SigComp and SIP
Date: Tue, 25 Jun 2002 11:22:25 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> 
> If folks think that it is OK that two proxies that support 
> SigComp MUST
> always exhange compressed messages, I will be glad to simplify the
> draft. If people feel that compressing when it is not really needed is
> unacceptable, we will keep the current Record-Route inspection
> mechanism.

This is *NOT* acceptable. The performance impacts of any realistic
compression algorithm are substantial. Over the air, the decreased
throughput (and ultimately increased hardware costs) is justified
by decreased latency. Between nodes operating on a wired network,
it's merely a losing proposition.

/a

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


From rohc-admin@ietf.org  Tue Jun 25 15:53:07 2002
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 PAA25605
	for <rohc-archive@odin.ietf.org>; Tue, 25 Jun 2002 15:53:07 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA12289;
	Tue, 25 Jun 2002 15:50:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA12218
	for <rohc@ns.ietf.org>; Tue, 25 Jun 2002 15:50:33 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25088;
	Tue, 25 Jun 2002 15:49:48 -0400 (EDT)
Received: from esealnt610.al.sw.ericsson.se (esealnt610.al.sw.ericsson.se [153.88.254.69])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g5PJoSrU008970;
	Tue, 25 Jun 2002 21:50:28 +0200 (MEST)
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NHKQ1GK3>; Tue, 25 Jun 2002 21:50:27 +0200
Message-ID: <A943FD84BD9ED41193460008C791805003E3216A@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'Adam Roach'" <adam@dynamicsoft.com>,
        "Gonzalo Camarillo Gonzalez (LMF)" <Gonzalo.Camarillo@lmf.ericsson.se>,
        Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Cc: sip <sip@ietf.org>, rohc <rohc@ietf.org>
Subject: RE: [rohc] SigComp and SIP
Date: Tue, 25 Jun 2002 21:49:07 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

> > -----Original Message-----
> > From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> > 
> > If folks think that it is OK that two proxies that support 
> > SigComp MUST always exchange compressed messages, I will be glad
> > to simplify the draft. If people feel that compressing when it
> > is not really needed is unacceptable, we will keep the current
> > Record-Route inspection mechanism.
> 
> -----Original Message-----
> From: Adam Roach [mailto:adam@dynamicsoft.com]
> This is *NOT* acceptable. The performance impacts of any realistic
> compression algorithm are substantial. Over the air, the decreased
> throughput (and ultimately increased hardware costs) is justified
> by decreased latency. Between nodes operating on a wired network,
> it's merely a losing proposition.

I tend to agree with Adam, it should not be mandatory for a proxy to
use compression just because compression is supported.

/L-E 

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


From rohc-admin@ietf.org  Tue Jun 25 15:58:22 2002
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 PAA25910
	for <rohc-archive@odin.ietf.org>; Tue, 25 Jun 2002 15:58:22 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA12681;
	Tue, 25 Jun 2002 15:56:48 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA27233
	for <rohc@optimus.ietf.org>; Tue, 25 Jun 2002 04:48:36 -0400 (EDT)
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26850;
	Tue, 25 Jun 2002 04:47:51 -0400 (EDT)
From: hisham.khartabil@nokia.com
Received: from esvir02nok.ntc.nokia.com (esvir02nokt.ntc.nokia.com [172.21.143.34])
	by mgw-x2.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g5P8n3i03534;
	Tue, 25 Jun 2002 11:49:03 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir02nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5bb382a0f8ac158f22076@esvir02nok.ntc.nokia.com>;
 Tue, 25 Jun 2002 11:48:26 +0300
Received: from esebe011.NOE.Nokia.com ([172.21.138.50]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 25 Jun 2002 11:48:26 +0300
Received: from esebe019.NOE.Nokia.com ([172.21.138.58]) by esebe011.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 25 Jun 2002 11:48:25 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sip] Re: [rohc] SigComp and SIP
Date: Tue, 25 Jun 2002 11:48:24 +0300
Message-ID: <2038BCC78B1AD641891A0D1AE133DBB7C2036B@esebe019.NOE.Nokia.com>
Thread-Topic: [Sip] Re: [rohc] SigComp and SIP
Thread-Index: AcIcIR6cuc+Yk4xITQKVisyE45PRBgAAui0A
To: <Gonzalo.Camarillo@lmf.ericsson.se>, <jdrosen@dynamicsoft.com>
Cc: <sip@ietf.org>, <rohc@ietf.org>
X-OriginalArrivalTime: 25 Jun 2002 08:48:25.0450 (UTC) FILETIME=[119A7CA0:01C21C25]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id EAA27236
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org
Content-Transfer-Encoding: 8bit

Looking at Gonzalo's example:

UAC----P1-----P2-----UAS

If P2 wants to receive compressed requests, then it adds comp=sigcomp in the RR header. If P2 does not want to receive compressed requests, then it does not include the param.

Now, if UAC wants to compress, it looks at the record-route header and finds out if the next hop (P2) wants to receive compressed data or not. In the case above, P2 did not want to receive compressed data, so UAC can't override P2's wish by sending it compressed data.

If you view the param comp=sigcomp and as an indication of willingness rather than capability, then doing it as described above makes sense.

If a UAC refuses to send uncompressed data, then perhaps a proxy-require: sigcomp (or something similar) can be sent.

Regards,
Hisham

> -----Original Message-----
> From: ext Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> Sent: Tuesday, June 25, 2002 11:20 AM
> To: Jonathan Rosenberg
> Cc: sip; rohc
> Subject: [Sip] Re: [rohc] SigComp and SIP
> 
> 
> Hello,
> 
> Jonathan Rosenberg wrote:
> > Well, you are trying to achieve the (somewhat odd) goal of 
> allowing the
> > proxy to indicate that it would prefer not to use sigcomp, unless
> > someone around it doesn't record-route, so that sigcomp 
> would be needed
> > in order to avoid unidirectional compression. Is there a reason for
> > supporting this case? For any individual dialog, either a proxy
> > indicates it can do compression, or it doesn't. I don't see 
> the need for
> > this case, and it complicates what is otherwise a fairly simple and
> > elegant solution.
> > 
> 
> The trade-off we have is the following:
> 
> If we go for the simplest mechanism, every time two adjacent proxies
> support SigComp, they will exchange compressed messages. This 
> means that
> when two wireless terminals exchange SIP signalling thru a set of
> SigComp capable proxies, all the messages will be compressed, even
> between proxies.
> 
> We can avoid this and make that compression is used only over the air
> interface (i.e., not between the proxies in our example), but 
> we have to
> have proxies inspect Record-Route header fields.
> 
> 
> If folks think that it is OK that two proxies that support 
> SigComp MUST
> always exhange compressed messages, I will be glad to simplify the
> draft. If people feel that compressing when it is not really needed is
> unacceptable, we will keep the current Record-Route inspection
> mechanism.
> 
> Personally, if nobody has big concerns about performance of precessing
> power, I would suggest that we simplify the mechanism and make it
> mandatory the use of compression for all entities that support SigComp
> (as suggested by Jonathan).
> 
> Regards,
> 
> Gonzalo
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 


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


From rohc-admin@ietf.org  Tue Jun 25 15:58:24 2002
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 PAA25924
	for <rohc-archive@odin.ietf.org>; Tue, 25 Jun 2002 15:58:24 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA12719;
	Tue, 25 Jun 2002 15:57:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA06451
	for <rohc@optimus.ietf.org>; Tue, 25 Jun 2002 08:12:55 -0400 (EDT)
Received: from imr1.ericy.com (imr1.ericy.com [208.237.135.240])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02000;
	Tue, 25 Jun 2002 08:12:11 -0400 (EDT)
Received: from mr6.exu.ericsson.se (mr6u3.ericy.com [208.237.135.123])
	by imr1.ericy.com (8.11.3/8.11.3) with ESMTP id g5PCCnl24401;
	Tue, 25 Jun 2002 07:12:49 -0500 (CDT)
Received: from noah.lmc.ericsson.se (noah.lmc.ericsson.se [142.133.1.1])
	by mr6.exu.ericsson.se (8.11.3/8.11.3) with ESMTP id g5PCCmc05832;
	Tue, 25 Jun 2002 07:12:48 -0500 (CDT)
Received: from eammlex033.lmc.ericsson.se (eammlex033.lmc.ericsson.se [142.133.1.133])
	by noah.lmc.ericsson.se (8.11.2/8.9.2) with ESMTP id g5PCCmE26733;
	Tue, 25 Jun 2002 08:12:48 -0400 (EDT)
Received: by eammlex033.lmc.ericsson.se with Internet Mail Service (5.5.2655.55)
	id <NR95MH14>; Tue, 25 Jun 2002 08:14:16 -0400
Message-ID: <32CD630F6CBED411AE180008C7894CBC0C0377EE@lmc37.lmc.ericsson.se>
From: "George Foti (LMC)" <George.Foti@ericsson.ca>
To: "Gonzalo Camarillo Gonzalez (LMF)" <Gonzalo.Camarillo@lmf.ericsson.se>,
        Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Cc: sip <sip@ietf.org>, rohc <rohc@ietf.org>
Subject: RE: [Sip] Re: [rohc] SigComp and SIP
Date: Tue, 25 Jun 2002 08:12:46 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

> The trade-off we have is the following:
> 
> If we go for the simplest mechanism, every time two adjacent proxies
> support SigComp, they will exchange compressed messages. This 
> means that
> when two wireless terminals exchange SIP signalling thru a set of
> SigComp capable proxies, all the messages will be compressed, even
> between proxies.
> 
> We can avoid this and make that compression is used only over the air
> interface (i.e., not between the proxies in our example), but 
> we have to
> have proxies inspect Record-Route header fields.
> 
> 
> If folks think that it is OK that two proxies that support 
> SigComp MUST
> always exhange compressed messages, I will be glad to simplify the
> draft. If people feel that compressing when it is not really needed is
> unacceptable, we will keep the current Record-Route inspection
> mechanism.
> 
> Personally, if nobody has big concerns about performance of precessing
> power, I would suggest that we simplify the mechanism and make it
> mandatory the use of compression for all entities that support SigComp
> (as suggested by Jonathan).
> 
> Regards,
> 
> Gonzalo

Compression between proxies that support SIGCOMP cannot be a MUST. 
Not only does the processing power become an issue which will increase the
cost of the equipment without any *real value* added. The call set up delay
can be seriously impacted when you have 5 or 6 proxies to traverse in a
typical 3G-3G call.

Furthermore, when we talk about simplification what are we really
simplifying, the RR needs to be examined anyway for potential rewrites. 

So, I would stick to the original proposal. It must be an option and a local
policy to SIGCOMP or not.

Rggds/gf




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


From rohc-admin@ietf.org  Tue Jun 25 16:32:00 2002
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 QAA27568
	for <rohc-archive@odin.ietf.org>; Tue, 25 Jun 2002 16:32:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA15155;
	Tue, 25 Jun 2002 16:31:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA15094
	for <rohc@ns.ietf.org>; Tue, 25 Jun 2002 16:31:11 -0400 (EDT)
Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27487;
	Tue, 25 Jun 2002 16:30:25 -0400 (EDT)
Received: from DYN-EXCH-001.dynamicsoft.com (dyn-exch-001 [63.113.44.7])
	by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id g5PKURN7012880;
	Tue, 25 Jun 2002 16:30:27 -0400 (EDT)
Received: by DYN-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <NDQAWLM6>; Tue, 25 Jun 2002 16:30:33 -0400
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F377A264@DYN-TX-EXCH-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@lmf.ericsson.se>,
        Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Cc: sip <sip@ietf.org>, rohc <rohc@ietf.org>
Subject: RE: [Sip] Re: [rohc] SigComp and SIP
Date: Tue, 25 Jun 2002 16:30:30 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> 
> This covers the following scenario:
> 
> UAC----P1-----P2-----UAS
> 
> The UAC sends an INITE to UAS. P2 records route, but P1 does not.
> When the 200 OK for the INVITE reaches P2, the contact and RR header
> fields will look like this:
> 
> Contact: UAS@domain.com;comp=sigcomp
> RR: P2
> 
> If P2 does not add comp=sigcomp to his entry in the RR, UAC 
> will be able
> to receive compressed traffic (the contact has comp=sigcomp), but will
> be unable to send compress traffic (the RR entry for P2 does not have
> it).
> 
> Making P2 add comp=sigcomp resolves this asymmetry

I would argue that any network that uses compression like this
will almost certainly have a compression/decompression node (P1
in your example) in the path, and record-routing. I don't beleive
the extra complexity you describe is worth the effort of what
amounts to trying to work around poorly-designed networks.

/a

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


From rohc-admin@ietf.org  Wed Jun 26 12:45:18 2002
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 MAA28455
	for <rohc-archive@odin.ietf.org>; Wed, 26 Jun 2002 12:45:18 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA13545;
	Wed, 26 Jun 2002 12:44:02 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA13507
	for <rohc@ns.ietf.org>; Wed, 26 Jun 2002 12:43:59 -0400 (EDT)
Received: from mgw-dax2.ext.nokia.com (mgw-dax2.ext.nokia.com [63.78.179.217])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28392;
	Wed, 26 Jun 2002 12:43:15 -0400 (EDT)
From: zhigang.c.liu@nokia.com
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85])
	by mgw-dax2.ext.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g5QGlWj08050;
	Wed, 26 Jun 2002 11:47:32 -0500 (CDT)
Received: from daebh001.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5bb8a4dd40ac12f255126@davir02nok.americas.nokia.com>;
 Wed, 26 Jun 2002 11:43:56 -0500
Received: from daebe005.NOE.Nokia.com ([172.18.242.203]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 26 Jun 2002 11:43:17 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [rohc] SigComp and SIP
Date: Wed, 26 Jun 2002 11:43:16 -0500
Message-ID: <DE0842B293FC4847992F9EDF8D72E1ED24A46D@daebe005.NOE.Nokia.com>
Thread-Topic: [rohc] SigComp and SIP
Thread-Index: AcIcIR6SFmZX+VopTTCN8HgIMKP39ABDiD8w
To: <Gonzalo.Camarillo@lmf.ericsson.se>, <jdrosen@dynamicsoft.com>
Cc: <sip@ietf.org>, <rohc@ietf.org>
X-OriginalArrivalTime: 26 Jun 2002 16:43:17.0227 (UTC) FILETIME=[927063B0:01C21D30]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id MAA13510
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org
Content-Transfer-Encoding: 8bit

> If folks think that it is OK that two proxies that support SigComp MUST
> always exhange compressed messages, I will be glad to simplify the
> draft. If people feel that compressing when it is not really needed is
> unacceptable, we will keep the current Record-Route inspection
> mechanism.

I probably missed something here but why do we mix the support of
SigComp with the use of it? Looking at one direction, the sender 
needs to know if the receiver supports SigComp. But beyond that,
it is the sender's choice whether to send compressed message.
In other words, once a receiver says "I support SigComp", it's
out of its control and it must prepare for receiving both 
compressed and uncompressed message.

Zhigang


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


From rohc-admin@ietf.org  Thu Jun 27 03:40:17 2002
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 DAA04851
	for <rohc-archive@odin.ietf.org>; Thu, 27 Jun 2002 03:40:17 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA07994;
	Thu, 27 Jun 2002 03:39:19 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA07955
	for <rohc@optimus.ietf.org>; Thu, 27 Jun 2002 03:39:17 -0400 (EDT)
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04814;
	Thu, 27 Jun 2002 03:38:33 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.192])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g5R7ceYH023453;
	Thu, 27 Jun 2002 03:38:40 -0400 (EDT)
Message-ID: <3D1AC100.500@dynamicsoft.com>
Date: Thu, 27 Jun 2002 03:38:40 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: zhigang.c.liu@nokia.com
CC: Gonzalo.Camarillo@lmf.ericsson.se, sip@ietf.org, rohc@ietf.org
Subject: Re: [rohc] SigComp and SIP
References: <DE0842B293FC4847992F9EDF8D72E1ED24A46D@daebe005.NOE.Nokia.com>
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-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org
Content-Transfer-Encoding: 7bit



zhigang.c.liu@nokia.com wrote:
>>If folks think that it is OK that two proxies that support SigComp
> 
> MUST
> 
>>always exhange compressed messages, I will be glad to simplify the
>>draft.

I agree with others that this cannot be mandated. I was not proposing 
that it be mandated. See below.


>> If people feel that compressing when it is not really needed is
>>unacceptable, we will keep the current Record-Route inspection
>>mechanism.
> 
> 
> I probably missed something here but why do we mix the support of
> SigComp with the use of it? Looking at one direction, the sender 
> needs to know if the receiver supports SigComp. But beyond that,
> it is the sender's choice whether to send compressed message.
> In other words, once a receiver says "I support SigComp", it's
> out of its control and it must prepare for receiving both 
> compressed and uncompressed message.

I agree. This is what I thought the comp=sigcomp parameter meant - "I 
support sigcomp". The sender then has the option of using it. With this 
definition, it makes little sense to have a proxy rewrite the 
record-route to include teh parameter in one direction, and not another.

-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
Chief Scientist                         First Floor
dynamicsoft                             East Hanover, NJ 07936
jdrosen@dynamicsoft.com                 FAX: (973) 952-5050
http://www.jdrosen.net                  PH:  (973) 952-5000
http://www.dynamicsoft.com


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


From rohc-admin@ietf.org  Thu Jun 27 04:38:59 2002
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 EAA06432
	for <rohc-archive@odin.ietf.org>; Thu, 27 Jun 2002 04:38:58 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA12845;
	Thu, 27 Jun 2002 04:38:24 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA12815
	for <rohc@optimus.ietf.org>; Thu, 27 Jun 2002 04:38:22 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06403
	for <rohc@ietf.org>; Thu, 27 Jun 2002 04:37:37 -0400 (EDT)
Received: from esealnt611.al.sw.ericsson.se (esealnt611.al.sw.ericsson.se [153.88.254.68])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g5R8cKrU017151;
	Thu, 27 Jun 2002 10:38:20 +0200 (MEST)
Received: by esealnt611.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NHMS9T71>; Thu, 27 Jun 2002 10:38:17 +0200
Message-ID: <F005CD411D18D3119C8F00508B08748008543632@ehubunt100.eth.ericsson.se>
From: "Peter Kremer (ETH)" <Peter.Kremer@eth.ericsson.se>
To: rohc@ietf.org
Cc: "'zhigang.c.liu@nokia.com'" <zhigang.c.liu@nokia.com>
Subject: RE: [rohc] additions to ROHC Implementer's Guide
Date: Thu, 27 Jun 2002 10:34:06 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

Hi,

I have general problems with your proposed text. You proposed me to include some text about topics (e.g. context updating) that is already defined in RFC 3095. Maybe your text is easier to understand but that part is already clear enough.

I have received some guidelines from Lars-Erik (as a wg co-chair). It says that the imp. guide shouldn't interpret the RFC, the goal is to clarify and not to explain.

Regarding your comment on implicit updates. I don't want to lump modes together. Section 4.7 is about a GENERAL issue, which - of course - has unique treatment in the different modes. And it also gives ONE example...

Anyway, the "Enhanced mode transition procedures" can be found in "ROHC Implementer's Guide" (draft-ietf-rohc-rtp-impl-guide-00.txt), Section 3, page 3.
http://www.ietf.org/internet-drafts/draft-ietf-rohc-rtp-impl-guide-00.txt

Best Regards,
Peter

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


From rohc-admin@ietf.org  Thu Jun 27 12:05:32 2002
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 MAA27500
	for <rohc-archive@odin.ietf.org>; Thu, 27 Jun 2002 12:05:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA22446;
	Thu, 27 Jun 2002 12:04:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA22418
	for <rohc@optimus.ietf.org>; Thu, 27 Jun 2002 12:04:34 -0400 (EDT)
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27257
	for <rohc@ietf.org>; Thu, 27 Jun 2002 12:03:48 -0400 (EDT)
From: zhigang.c.liu@nokia.com
Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84])
	by mgw-dax1.ext.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g5RG52x23478
	for <rohc@ietf.org>; Thu, 27 Jun 2002 11:05:02 -0500 (CDT)
Received: from daebh001.NOE.Nokia.com (unverified) by davir01nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5bbda71b62ac12f25412a@davir01nok.americas.nokia.com>;
 Thu, 27 Jun 2002 11:04:29 -0500
Received: from daebe005.NOE.Nokia.com ([172.18.242.203]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Thu, 27 Jun 2002 11:04:27 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [rohc] additions to ROHC Implementer's Guide
Date: Thu, 27 Jun 2002 11:04:27 -0500
Message-ID: <DE0842B293FC4847992F9EDF8D72E1ED24A472@daebe005.NOE.Nokia.com>
Thread-Topic: [rohc] additions to ROHC Implementer's Guide
Thread-Index: AcIdtf+mtNY6aZcbRMihNx7Gi8yIZgAN0GgQ
To: <Peter.Kremer@eth.ericsson.se>, <rohc@ietf.org>
X-OriginalArrivalTime: 27 Jun 2002 16:04:27.0812 (UTC) FILETIME=[50699E40:01C21DF4]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id MAA22419
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org
Content-Transfer-Encoding: 8bit

Peter,

> Maybe your text is 
> easier to understand but that part is already clear enough.

I don't think so. Actually, your own text speaks for the truth. 
When you wrote the following text, was it clear to *you* that
"An update packet in R-mode updates ALL header fields"?
And "Specifically, above applies to R-0-CRC"?

------------------------------------
4.7.  Implicit TS and IP-ID updates

   Type 0 packets (R-0-CRC, UO-0), which contain the compressed RTP
   sequence number (SN) and a CRC checksum updates not only the RTP
   sequence number.  Such packets also update RTP timestamp and IPv4 ID
   implicitly, unless there are explicit TS and IP-ID fields in the
   packet.
------------------------------------

My general problem with -00 is that it misses some issues related 
to R-mode. This is understandable as you probably are more 
familiar with UO-mode than with R-mode (and me the other way 
around). But the implementation guide should clarify all 
ROHC modes. That is what independent implementers want.
 
> I have received some guidelines from Lars-Erik (as a wg 
> co-chair). It says that the imp. guide shouldn't interpret 
> the RFC, the goal is to clarify and not to explain.

Is it really so? Can you call section 3 "Enhanced mode transition 
procedures" a clarification? And how about section 4.1 "Padding
octet in CRC"? To me, they are modifications, not clarifications.

BTW, Lars-Erik is also a co-author of the draft. Can one person
wear two hats at the same time?

BR,
Zhigang

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


From rohc-admin@ietf.org  Thu Jun 27 12:27:00 2002
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 MAA29102
	for <rohc-archive@odin.ietf.org>; Thu, 27 Jun 2002 12:27:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA23842;
	Thu, 27 Jun 2002 12:25:50 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA23797
	for <rohc@optimus.ietf.org>; Thu, 27 Jun 2002 12:25:47 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.47])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28968
	for <rohc@ietf.org>; Thu, 27 Jun 2002 12:25:01 -0400 (EDT)
Received: from esealnt610.al.sw.ericsson.se (esealnt610.al.sw.ericsson.se [153.88.254.69])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g5RGPjRb014479;
	Thu, 27 Jun 2002 18:25:45 +0200 (MEST)
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NHKQ68VL>; Thu, 27 Jun 2002 18:25:45 +0200
Message-ID: <A943FD84BD9ED41193460008C791805003E3217A@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EAB)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'zhigang.c.liu@nokia.com'" <zhigang.c.liu@nokia.com>,
        "Peter Kremer (ETH)" <Peter.Kremer@eth.ericsson.se>, rohc@ietf.org
Subject: RE: [rohc] additions to ROHC Implementer's Guide
Date: Thu, 27 Jun 2002 18:25:35 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

Peter and Zhigang,

> > Maybe your text is 
> > easier to understand but that part is already clear enough.
> 
> I don't think so. Actually, your own text speaks for the truth. 
> When you wrote the following text, was it clear to *you* that
> "An update packet in R-mode updates ALL header fields"?
> And "Specifically, above applies to R-0-CRC"?
> 
> ------------------------------------
> 4.7.  Implicit TS and IP-ID updates
> 
>    Type 0 packets (R-0-CRC, UO-0), which contain the compressed RTP
>    sequence number (SN) and a CRC checksum updates not only the RTP
>    sequence number.  Such packets also update RTP timestamp 
>    and IPv4 ID implicitly, unless there are explicit TS and IP-ID
>    fields in the packet.
> ------------------------------------
> 
> My general problem with -00 is that it misses some issues related 
> to R-mode. This is understandable as you probably are more 
> familiar with UO-mode than with R-mode (and me the other way 
> around). But the implementation guide should clarify all 
> ROHC modes. That is what independent implementers want.

I assume that Peter is fixing this in -01, right? Peter has received
input on -00 and that should be reflected in -01. If there are still
problems after that, just point out exactly what the problems are. 


> > I have received some guidelines from Lars-Erik (as a wg 
> > co-chair). It says that the imp. guide shouldn't interpret 
> > the RFC, the goal is to clarify and not to explain.

Well, I think my point have always been that we must try not to
go too far with this document. The most important thing is to
clarify what is found to be unclear or missing in 3095. Further,
we can add things that people think should absolutely be added
for other reasons. For example, it was agreed to add the
"Enhanced mode transition procedures", which is not about
clarifying content of the RFC, but was requested after experiences
and discussions at "ROHC in the desert".

What I have been missing in some sections of the draft is 
explanations of why this is in the draft, i.e. what is not
clear or complete in 3095. To have such a motivation should
be a requirement before adding anything to the guide. This
is useful for the guide itself, and it also makes it easier
to judge whether we should really add it or not.

 
/L-E

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


From rohc-admin@ietf.org  Thu Jun 27 17:19:10 2002
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 RAA16615
	for <rohc-archive@odin.ietf.org>; Thu, 27 Jun 2002 17:19:10 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA24511;
	Thu, 27 Jun 2002 17:17:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA24480
	for <rohc@ns.ietf.org>; Thu, 27 Jun 2002 17:17:01 -0400 (EDT)
Received: from tokyo.ccrle.nec.de (tokyo.ccrle.nec.de [195.37.70.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16438
	for <rohc@ietf.org>; Thu, 27 Jun 2002 17:16:16 -0400 (EDT)
Received: from wallace.heidelberg.ccrle.nec.de (root@wallace.heidelberg.ccrle.nec.de [192.168.102.1])
	by tokyo.ccrle.nec.de (8.11.6/8.11.6) with ESMTP id g5RLGRK37811;
	Thu, 27 Jun 2002 23:16:27 +0200 (CEST)
	(envelope-from quittek@ccrle.nec.de)
Received: from [192.168.102.32] ([192.168.102.32])
	by wallace.heidelberg.ccrle.nec.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id XAA27518;
	Thu, 27 Jun 2002 23:11:12 +0200
Date: Thu, 27 Jun 2002 23:11:09 +0200
From: Juergen Quittek <quittek@ccrle.nec.de>
To: "West, Mark (ITN)" <mark.a.west@roke.co.uk>, rohc@ietf.org
Subject: Re: [rohc] ROHC statistics
Message-ID: <2889064.1025219468@[192.168.102.32]>
In-Reply-To: <3D1825FA.8070504@roke.co.uk>
References:  <3D1825FA.8070504@roke.co.uk>
X-Mailer: Mulberry/2.1.2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org
Content-Transfer-Encoding: 7bit

Mark,

Thank you very much for your input. Below please find new suggestion for
the revised set of statistics to be collected by the ROHC RTP MIB module.

If anybody has comments or requests for changes,
please give me your input.

    Juergen
-- 
Juergen Quittek     quittek@ccrle.nec.de     Tel: +49 6221 90511-15
NEC Europe Ltd.,    Network Laboratories     Fax: +49 6221 90511-55
Adenauerplatz 6, 69115 Heidelberg, Germany   http://www.ccrle.nec.de



ROHC MIB RTP statistics

Per channel:
    number of active flows
    total number of flows
    total number of packets coming out of the decompressors
    total number of packets sent to the compressors

Per RTP compressor:
    total number of sent packets
    number of sent IR packets
    number of sent IR-DYN packets
    number of received ACKs
    number of received NACKs
    number of received SNACKs
    mean compression ratio over all packets
    mean compressed packet size over all packets
    mean compression ratio over the last 16 packets
    mean compressed packet size over the last 16 packets

Per RTP decompressor:
    number of received packets
    number of received IR packets
    number of received IR-DYN packets
    number of decompression failures
    number of context repairs
    number of sent ACKs
    number of sent NACKs
    number of sent SNACKs


--On 25 June 2002 09:12 +0100 "West, Mark (ITN)" <mark.a.west@roke.co.uk> wrote:

>
> Hi Juergen,
>
> At least some partial answers, inline...
>
> Cheers,
>
> Mark.
>
>
> Juergen Quittek wrote:
>
>> Dear all,
>>
>> I am still looking for suggestions on the statistics
>> to be collected for monitoring ROHC systems with the
>> ROHC MIB module:
>>
>>  - What statistics do you collect with your
>>    implementation?
>
>
> Not many!  Packet counts; average compressed packet size; decompression failures / context repairs; that sort of thing.  We tend to maintain these per-CID, but then for the sort of testing we're doing at the moment, we don't tend to have many active
> CIDs.
>
>>  - What statistics would be desirable to provide for
>>    ROHC operation and maintenance?
>
>
> Probably ought to be something about CID usage -- number of flows and/or a high water mark?
>
> I'll think about this one a bit more...
>
>>  - What statistics would be helpful for fault analysis?
>
>
> Hmmm... I suppose the most obvious one is the number of packets in and out (which at least tells you whether or not your ROHC instance is doing *something*)!  Counts of failed decompressions / received nacks gives some additional information.
>
> I think knowing about failed decompression
>
> Not so much a 'fault', but it might help to know the number of IR/IR-DYN packets per flow -- a high number of IR-DYN packets could indicate that the wrong profile is being used?
>
>>  - What statistics were useful at ROHC interop events?
>
>
> To be honest (and I can only spesak for myself, obviously), we haven't had the luxury of such abstract notions as statistics!  Generally we've been working with log-files; often at the level of individual bits...
>
> If I were to extrapolate from the sorts of things that we look for in a logfile (at a relatively high level), then I suppose that this would be things like different packet types used (however, I'm not sure that this is actually a useful statistic to
> collect -- plus, see below...)
>
>
>>
>> Please provide your input!
>>
>
>
> It's not much, but it's a start...
>
>
>> The current version of the MIB module collects the
>> following statistics:
>>
>> Per compressor:
>>    total number of sent packets
>>        number of sent packets per header type
>>    number of received ACKs
>>    number of received NACKs
>>    number of received SNACKs
>>    mean compression ratio over all packets
>>    mean compression ratio over the last 16 packets
>>
>> Per decompressor:
>>    number of received packets
>>        number of received packets per header type
>>    number of sent ACKs
>>    number of sent NACKs
>>    number of sent SNACKs
>>
>> Collecting the number of packets per header type might
>> not be a good idea in some cases. Do you have better
>> ideas?
>>
>
>
> I agree that collecting stats per header-type is probably not a good idea (or, at least, could lead to a very large amount of data with questionable value).  As suggested above, though, a more coarse-grained approach might be useful, e.g. to see how
> many IR/IR-DYN/CO packets have been sent.
>
> At the decompressor, I think that it would useful to information about decompression failures (and context repair attempts) as well as the counts of acks/nacks/snacks.
>
> I wonder if 'compression ratio' is the most useful statistic? Uncompressed headers can be variable length, so it might be hard to tell from just the ratio what my actual header overhead was.  Maybe 'mean uncompressed size' and 'mean compressed size'
> would be useful instead of / as well?
>
>
>>    Juergen
>
>
> Just my immediate thoughts, to get the ball rolling!
>
> More later...
>
> --
> Mark A. West, Consultant Engineer
> Roke Manor Research Ltd., Romsey, Hants.  SO51 0ZN
> Phone +44 (0)1794 833311   Fax  +44 (0)1794 833433
>
> (Yes, I do know that my disclaimer is in an attachment.  And, no, I didn't ask for it to be that way)



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


From rohc-admin@ietf.org  Fri Jun 28 06:36:54 2002
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 GAA17512
	for <rohc-archive@odin.ietf.org>; Fri, 28 Jun 2002 06:36:54 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA11709;
	Fri, 28 Jun 2002 06:36:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA11680
	for <rohc@optimus.ietf.org>; Fri, 28 Jun 2002 06:36:16 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17170;
	Fri, 28 Jun 2002 06:35:29 -0400 (EDT)
Message-Id: <200206281035.GAA17170@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, 28 Jun 2002 06:35:28 -0400
Subject: [rohc] I-D ACTION:draft-west-rohc-formal-notation-00.txt
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: A Formal Notation for Header Compression
	Author(s)	: R. Price, A. Surtees, M. West
	Filename	: draft-west-rohc-formal-notation-00.txt
	Pages		: 54
	Date		: 27-Jun-02
	
This draft defines a BNF-based notation for describing the behavior
of protocol stacks with respect to compressing the protocol headers.
The RObust Header Compression ROHC [1] scheme is designed to compress
packet headers over error prone channels.  It is built around an
extensible core framework that can be tailored to compress new
protocol stacks by adding additional ROHC profiles.
The aim of the notation is to simplify the creation of new ROHC [1]
profiles.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-west-rohc-formal-notation-00.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-west-rohc-formal-notation-00.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-west-rohc-formal-notation-00.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:	<20020627132843.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-west-rohc-formal-notation-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-west-rohc-formal-notation-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--



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


From rohc-admin@ietf.org  Fri Jun 28 06:41:15 2002
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 GAA18359
	for <rohc-archive@odin.ietf.org>; Fri, 28 Jun 2002 06:41:15 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA12567;
	Fri, 28 Jun 2002 06:39:46 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA12532
	for <rohc@optimus.ietf.org>; Fri, 28 Jun 2002 06:39:44 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18061;
	Fri, 28 Jun 2002 06:38:56 -0400 (EDT)
Message-Id: <200206281038.GAA18061@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, 28 Jun 2002 06:38:56 -0400
Subject: [rohc] I-D ACTION:draft-price-rohc-sigcomp-user-guide-00.txt
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: SigComp User Guide
	Author(s)	: R. Price, A. Surtees, M. West
	Filename	: draft-price-rohc-sigcomp-user-guide-00.txt
	Pages		: 36
	Date		: 27-Jun-02
	
This document provides an informational guide for users of the 
SigComp protocol. The aim of the document is to assist users when 
making SigComp implementation decisions; for example the choice of 
compression algorithm and the level of robustness against lost or 
misordered packets.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-price-rohc-sigcomp-user-guide-00.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-price-rohc-sigcomp-user-guide-00.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-price-rohc-sigcomp-user-guide-00.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:	<20020627133350.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-price-rohc-sigcomp-user-guide-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-price-rohc-sigcomp-user-guide-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--



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


