From rohc-admin@ietf.org  Sun Feb 17 07:35:53 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 HAA04988
	for <rohc-archive@odin.ietf.org>; Sun, 17 Feb 2002 07:35:53 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA05908;
	Sun, 17 Feb 2002 07:19:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA05877
	for <rohc@optimus.ietf.org>; Sun, 17 Feb 2002 07:19:54 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04857
	for <rohc@ietf.org>; Sun, 17 Feb 2002 07:19:50 -0500 (EST)
Received: from esealnt406.al.sw.ericsson.se (ESEALNT406.al.sw.ericsson.se [153.88.251.29])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g1HCJIhM003610
	for <rohc@ietf.org>; Sun, 17 Feb 2002 13:19:18 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt406.al.sw.ericsson.se ; Sun Feb 17 13:19:17 2002 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <Z1HYPM5F>; Sun, 17 Feb 2002 13:19:17 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E31DEE@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Sun, 17 Feb 2002 13:14:58 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [rohc] ROHC has moved, welcome to rohc@ietf.org
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

ROHCers,

The ROHC mailing list has now been moved, and this mail is sent through the new list. Future
postings should now be directed to "rohc@ietf.org", so please update your address book.
Postings to "rohc@cdt.luth.se" will be forwarded to the new list, but only for a limited period.

All subscribers of "rohc@cdt.luth.se" have been moved to the new list, and you should all have
received a welcome message for the subscription. 

Information about the new list can be found at:
https://www1.ietf.org/mailman/listinfo/rohc
Note that there is also a new archive for ROHC. The old archive will stay where it currently is,
but we will also take a copy of it to ietf.org. However, that will not happen immediately.

The new list gives us new possibilities for moderation, and there are basically two new rules for
postings:
1) Postings are limited to 40 Kb
2) Only subscribers are allowed to post, others will be moderated and all relevant (non spam)
postings will be manually approved

If you are subscribed with multiple addresses, note that the new list has an option for each
subscription to choose whether messages are to be delivered to that address or not.
Subscribers can also choose to get messages in daily digests.

See you on the new list!
/Lars-Erik



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


From rohc-admin@ietf.org  Sun Feb 17 07:43: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 HAA05052
	for <rohc-archive@odin.ietf.org>; Sun, 17 Feb 2002 07:43:00 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA06864;
	Sun, 17 Feb 2002 07:37:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA06790
	for <rohc@optimus.ietf.org>; Sun, 17 Feb 2002 07:36:02 -0500 (EST)
Received: from sm.luth.se (ny.sm.luth.se [130.240.3.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05000
	for <rohc@ietf.org>; Sun, 17 Feb 2002 07:35:58 -0500 (EST)
Received: (from majordomo@localhost)
	by sm.luth.se (8.10.2+Sun/8.10.0) id g1HCZwV03982
	for rohc-outgoing; Sun, 17 Feb 2002 13:35:58 +0100 (MET)
X-Authentication-Warning: ny.sm.luth.se: majordomo set sender to owner-robhc@cdt.luth.se using -f
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.36])
	by sm.luth.se (8.10.2+Sun/8.10.0) with ESMTP id g1HCZHB03822
	for <rohc@cdt.luth.se>; Sun, 17 Feb 2002 13:35:18 +0100 (MET)
Received: from esealnt406.al.sw.ericsson.se (ESEALNT406.al.sw.ericsson.se [153.88.251.29])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g1HCZHhM004886
	for <rohc@cdt.luth.se>; Sun, 17 Feb 2002 13:35:17 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt406.al.sw.ericsson.se ; Sun Feb 17 13:35:16 2002 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKDQCG1>; Sun, 17 Feb 2002 13:25:45 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E31DF0@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'rohc@cdt.luth.se'" <rohc@cdt.luth.se>
Subject: [rohc] When posting to "rohc@cdt.luth.se"
Date: Sun, 17 Feb 2002 13:30:57 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Precedence: bulk
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 mailing list for Robust Header Compression WG is rohc@ietf.org
This mail was sent via the old rohc@cdt.luth.se list
The rohc@cdt.luth.se list will soon be inactive
---
ROHCers,

During a transition period, postings to rohc@cdt.luth.se will be
forwarded in this way to rohc@ietf.org. However, note that this is
a short-term service. Please post only to the new list.

BR
/Lars-Erik
---
Mailing list for Robust Header Compression WG
Archive: http://www.cdt.luth.se/rohc/


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


From rohc-admin@ietf.org  Mon Feb 18 06:46:53 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 GAA00573
	for <rohc-archive@odin.ietf.org>; Mon, 18 Feb 2002 06:46:53 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA15312;
	Mon, 18 Feb 2002 06:41:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA15281
	for <rohc@optimus.ietf.org>; Mon, 18 Feb 2002 06:41:57 -0500 (EST)
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 GAA00526
	for <rohc@ietf.org>; Mon, 18 Feb 2002 06:41:52 -0500 (EST)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <1S9WNHHW>; Mon, 18 Feb 2002 11:40:30 -0000
Message-ID: <76C92FBBFB58D411AE760090271ED418033555EF@rsys002a.roke.co.uk>
From: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
To: "'hans.hannu@epl.ericsson.se'" <hans.hannu@epl.ericsson.se>,
        "'rohc@ietf.org'" <rohc@ietf.org>
Subject: RE: [rohc] default algorithm, redux
Date: Mon, 18 Feb 2002 11:40:29 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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-1"

Hans,

Thanks for these clarifications.

For completeness here are the results for the same files with no dynamic compression and no sharing - just each file compressed independently of everything else.

message		static		dynamic
forward direction
1			587			502
4			457			395
6			434			377
7			216			200
9			249			232
12			227			213

reverse direction
2			223			210
3			685			576
5			227			214
8			266			245
10			216			203
11			239			225

Best Regards,

Abbie

> I think we have been talking (again) about different things.
> What I meant with dynamic compression, regardless of the compression
> algorithm used, is that:
> (Referring to an old expired draft SigComp -02)
> 
> "5.3. Dynamic compression
>    A compressing entity MAY choose to use previously sent messages in
>    the compression process in an attempt to improve the compression
>    efficiency. This is referred to as dynamic compression."
> 
> "5.4. Shared compression
> 
>    Shared compression is referred to the case when a 
> compressor 'A' make
>    use of decompressed messages received by the decompressor 
> located at
>    the same SigComp entity. These decompressed messages MUST originate
>    from the corresponding SigComp entity, which decompressor is
>    controlled by compressor 'A'."
> 
> So, the figures you present in this mail, would be with the above
> definition, compressed using "dynamic" compression, and in 
> your previous
> mail, both "shared" and "dynamic" compression were used.
> 
> BR
> /Hans H
> 
> 

--------------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 Feb 18 07:57: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 HAA01510
	for <rohc-archive@odin.ietf.org>; Mon, 18 Feb 2002 07:57:34 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA17863;
	Mon, 18 Feb 2002 07:54:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA17836
	for <rohc@optimus.ietf.org>; Mon, 18 Feb 2002 07:54:18 -0500 (EST)
Received: from cundall.co.uk (dorfl.roke.co.uk [193.118.205.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA01353
	for <rohc@ietf.org>; Mon, 18 Feb 2002 07:54:13 -0500 (EST)
Received: from [193.118.192.41] ([193.118.192.41] verified) by cundall.co.uk (Stalker SMTP Server 1.7) with ESMTP id S.0000062574; Mon, 18 Feb 2002 12:54:15 +0000
Mime-Version: 1.0
X-Sender: lwc@193.118.192.24 (Unverified)
Message-Id: <p05100300b896a7d0bb91@[193.118.192.80]>
Date: Mon, 18 Feb 2002 12:54:12 +0000
To: richard.price@roke.co.uk, Hans.Hannu@epl.ericsson.se
From: Lawrence Conroy <lwc@roke.co.uk>
Cc: rohc@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Subject: [rohc] non-default capabilities
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 Learned Authors, Folks,
    I note that the new versions of the drafts (extended and the grand 
unified draft
SigComp-04) draft *are* available, via links on the charter page; I didn't see
ietf-announce messages for these, but they are there.

Having had a (very) quick look at the SigComp draft, I don't see how 
the capabilities
for non-default algorithms are supported - these were discussed on 
the list recently,
but how does an end point report the algorithms it supports (i.e. the 
states it has
available) to its peer (remote) entity?

I ASSUME that there will be a default, mandatory unencumbered 
algorithm that is known
to be supported and so this doesn't need to be reported; for the 
others, however...

Thus, a question - why is this not mentioned in the SigComp draft?
(or is it, in which case, where?).

all the best,
   Lawrence
-- 
lwc@roke.co.uk: +44 1794 833666::<my opinions>:

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


From rohc-admin@ietf.org  Mon Feb 18 08:12:23 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 IAA01873
	for <rohc-archive@odin.ietf.org>; Mon, 18 Feb 2002 08:12:23 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA18975;
	Mon, 18 Feb 2002 08:09:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA18897
	for <rohc@optimus.ietf.org>; Mon, 18 Feb 2002 08:08:00 -0500 (EST)
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 IAA01760
	for <rohc@ietf.org>; Mon, 18 Feb 2002 08:07:55 -0500 (EST)
Received: from cabo3 (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with SMTP id g1ID7m426400;
	Mon, 18 Feb 2002 14:07:48 +0100 (MET)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: "Lawrence Conroy" <lwc@roke.co.uk>, <richard.price@roke.co.uk>,
        <Hans.Hannu@epl.ericsson.se>
Cc: <rohc@ietf.org>
Subject: RE: [rohc] non-default capabilities
Date: Mon, 18 Feb 2002 14:07:48 +0100
Message-ID: <NFBBJFHGMCFINEMHAMBGOEGEHHAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <p05100300b896a7d0bb91@[193.118.192.80]>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
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

> I ASSUME that there will be a default, mandatory unencumbered 
> algorithm that is known
> to be supported and so this doesn't need to be reported

After the recent discussion, I'm not sure this is the current 
consensus of the WG.

Gruesse, Carsten



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


From rohc-admin@ietf.org  Mon Feb 18 08:22: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 IAA02127
	for <rohc-archive@odin.ietf.org>; Mon, 18 Feb 2002 08:22:06 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA19316;
	Mon, 18 Feb 2002 08:19:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA19283
	for <rohc@optimus.ietf.org>; Mon, 18 Feb 2002 08:19:16 -0500 (EST)
Received: from cundall.co.uk (dorfl.roke.co.uk [193.118.205.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA02046
	for <rohc@ietf.org>; Mon, 18 Feb 2002 08:19:11 -0500 (EST)
Received: from [193.118.192.41] ([193.118.192.41] verified) by cundall.co.uk (Stalker SMTP Server 1.7) with ESMTP id S.0000062575; Mon, 18 Feb 2002 13:19:12 +0000
Mime-Version: 1.0
X-Sender: lwc@193.118.192.24
Message-Id: <p05100300b896aee16489@[193.118.192.41]>
In-Reply-To: <NFBBJFHGMCFINEMHAMBGOEGEHHAA.cabo@tzi.org>
References: <NFBBJFHGMCFINEMHAMBGOEGEHHAA.cabo@tzi.org>
Date: Mon, 18 Feb 2002 13:19:08 +0000
To: "Dr. Carsten Bormann" <cabo@tzi.org>,
        "Price, Richard" <richard.price@roke.co.uk>,
        Hans.Hannu@epl.ericsson.se
From: Lawrence Conroy <lwc@roke.co.uk>
Subject: RE: [rohc] non-default capabilities
Cc: rohc@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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

At 2:07 pm +0100 18/2/02, Dr. Carsten Bormann wrote:
>  > I ASSUME that there will be a default, mandatory unencumbered
>>  algorithm that is known
>>  to be supported and so this doesn't need to be reported
>
>After the recent discussion, I'm not sure this is the current
>consensus of the WG.
>
>Gruesse, Carsten
To which I reply:

   OK - apologies - I was being imprecise.

In all cases in my previous posting, I was talking only about
->DECOMPRESSION<- algorithm support (default or otherwise).

I had assumed that choosing a default decompression algorithm
was still ongoing - Is there strong disagreement that there
should be one (albeit *which* one is still under consideration)?

best regards,
    Lawrence
-- 
lwc@roke.co.uk: +44 1794 833666::<my opinions>:

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


From rohc-admin@ietf.org  Mon Feb 18 09:27:43 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 JAA03630
	for <rohc-archive@odin.ietf.org>; Mon, 18 Feb 2002 09:27:43 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA21737;
	Mon, 18 Feb 2002 09:23:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA21706
	for <rohc@optimus.ietf.org>; Mon, 18 Feb 2002 09:23:03 -0500 (EST)
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 JAA03525
	for <rohc@ietf.org>; Mon, 18 Feb 2002 09:22:59 -0500 (EST)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <1S9WNH4K>; Mon, 18 Feb 2002 14:21:49 -0000
Message-ID: <76C92FBBFB58D411AE760090271ED4186F9FC6@rsys002a.roke.co.uk>
From: "Price, Richard" <richard.price@roke.co.uk>
To: "Conroy, Lawrence (SMTP)" <lwc@roke.co.uk>, Hans.Hannu@epl.ericsson.se
Cc: rohc@ietf.org
Date: Mon, 18 Feb 2002 14:21:47 -0000
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: non-default capabilities
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,

For the well-known but optional decompression algorithms, we need to assign a certain
identifier to each algorithm and then send a list of these identifiers from the
decompressor to the compressor. The compressor can then pick an algorithm from the list
or choose to download its own.

A mechanism to perform the above task was intended to be part of the SigComp draft, but
had to be deleted due to Hans' IPR concerns. Currently the compressor can only choose
between mandatory default decompression algorithms (supported at all decompressors) and
downloading new algorithms in the form of bytecode.

Hans: Would it be possible to provide some alternative text for the above algorithm
negotiation mechanism, such that your IPR concerns disappear?

Regards,

Richard

> -----Original Message-----
> From: Conroy, Lawrence (SMTP) 
> Sent: Monday, February 18, 2002 12:54 PM
> To: Price, Richard; Hans.Hannu@epl.ericsson.se
> Cc: rohc@ietf.org
> Subject: non-default capabilities
> 
> 
> Hi Learned Authors, Folks,
>     I note that the new versions of the drafts (extended and the grand unified draft
> SigComp-04) draft *are* available, via links on the charter page; I didn't see
> ietf-announce messages for these, but they are there.
> 
> Having had a (very) quick look at the SigComp draft, I don't see how the capabilities
> for non-default algorithms are supported - these were discussed on the list recently,
> but how does an end point report the algorithms it supports (i.e. the states it has
> available) to its peer (remote) entity?
> 
> I ASSUME that there will be a default, mandatory unencumbered algorithm that is known
> to be supported and so this doesn't need to be reported; for the others, however...
> 
> Thus, a question - why is this not mentioned in the SigComp draft?
> (or is it, in which case, where?).
> 
> all the best,
>    Lawrence
> -- 
> lwc@roke.co.uk: +44 1794 833666::<my opinions>:
> 

--------------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 Feb 18 14:54: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 OAA15717
	for <rohc-archive@odin.ietf.org>; Mon, 18 Feb 2002 14:54:09 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA08099;
	Mon, 18 Feb 2002 14:50:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA08069
	for <rohc@optimus.ietf.org>; Mon, 18 Feb 2002 14:50:00 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15622
	for <rohc@ietf.org>; Mon, 18 Feb 2002 14:49:53 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g1IJnQB29676
	for <rohc@ietf.org>; Mon, 18 Feb 2002 20:49:26 +0100 (MET)
Received: from ericsson.com (ppp26.lmf.ericsson.se [131.160.102.26])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g1IJnNr6025382
	for <rohc@ietf.org>; Mon, 18 Feb 2002 21:49:23 +0200 (EET)
Message-ID: <3C715AFA.75E57CBC@ericsson.com>
Date: Mon, 18 Feb 2002 21:50:18 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Organization: OY LM Ericsson AB
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: es,en
MIME-Version: 1.0
To: rohc@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [rohc] draft-ietf-rohc-sigcomp-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
Content-Transfer-Encoding: 7bit

Hi:

I have just read the new SigComp-04,
http://www.ietf.org/internet-drafts/draft-ietf-rohc-sigcomp-04.txt
and I have some questions and comments.


1) Section 1, Introduction, 5th paragraph:

   "However, 
   SigComp is designed to run over both connectionless and connection-
   oriented transports and hence may be applicable to other scenarios 
   with multiple endpoints compressing and decompressing data."

   I don't see the connection of the "conntectionless/connection 
   oriented transport" with the scenario where there is a single proxy
   for inboud/outbound signalling scenario, or when there are multiple
   endpoints sending signalling end-to-end.

   I would suggest to rephrase and split the sentences into different 
   paragraphs, one describing the scenario that SigComp is trying to
   solve (an endpoint - proxy scenario) and the other describing the
   ability of SigComp to run over connectionless and c.o. transports.

2) Section 2, Terminology, definition of Application:

     "c) decides whether state information may be saved by SigComp "

   I believe that the application does not decided to save state
   information, but the application "authorizes to save state 
   information based on a request from the SigComp layer".

3) Section 3, SigComp architecture, 2nd paragraph:

   "SigComp is typically offered to applications as a "shim" layer 
   between the application and the transport. Note however that for 
   certain applications the compressed SigComp message may be passed 
   back to the application itself for additional processing before 
   transmission. For example, the application may wish to apply 
   encryption to the compressed message before handing it to the 
   transport. "

   I don't think this scenario is possible. To my understanding, 
   there are two types of encryption: end-to-end and hop-by-hop.
    
   The end-to-end scenario is solved by the application encrypting
   certain header field values. Note that there is not need to 
   encrypt the whole message (otherwise proxies can't route it).
   Encryption of the certain header field values can be done at 
   the application layer prior to sending the message to the 
   SigComp layer.

   The hop-by-hop encryption is applied to the whole message,
   independently on whether the message is sent uncompressed or
   compressed. Further more, the encryption of the message could 
   be done at the link layer or even through some hardware device.

   I would like to hear comments on the above statements. And 
   certainly clarify what is the relationship between the application
   and SigComp. Particularly it needs to be clarified which layer
   is responsible to forward the message: the SigComp layer or the
   application layer.

4) Section 3, SigComp architecture, Figure 1.

   The figure shows 2 different applications. In my mind, there 
   should be one and only one application, together with a text 
   that describes that there is one SigComp layer instance per
   application.

   This approach allows to demultiplex application messages 
   based on the port number. For instance, SIP/SigComp messages
   should be addressed to port number X, whereas HTTP/SigComp 
   messages should be addressed to port number Y. This approach
   have the following advantages.

   - Allows a clean SigComp discovery mechanism at the application
     layer (e.g., based on SRV of NAPTR records).
   - The SigComp layer does not need to understand and look inside
     the payload (the decompressed message) to find out to which
     application the uncompressed message should be sent.

   At least, I believe that the SIP WG is moving with the assumption
   that the SigComp layer that is listening to a port is dedicated
   to receive SIP compressed messages.

   Therefore, my proposal is to modify figure 1 and paint just a
   single application and add some text explaining the figure:

   "Several applications may want to use the services provided by 
   a SigComp layer. Each application will need its own instance of 
   the SigComp layer. This restriction is introduced for the purpose 
   of describing the SigComp architecture and it does not mandate a 
   particular implementation.

   The SigComp layer is listening to a port number that is allocated 
   exclusively to receive SigComp compressed messages destined to the 
   application making use of the SigComp layer."

5) Section 3.2, first paragraph:

   "The two instances of the 
   application that wish to communicate MUST initially agree on a common 
   set of values for these parameters."

   In order to avoid confusion with two applications running in the
   same local host and making use of SigComp, I would suggest to rephrase:

   "The local and remote applications that wish to communicate MUST 
   initially agree on a common set of values for these parameters."

   Or did I misunderstand??

6) Section 3.2, second paragraph.

   "Note that if a reverse channel is available then SigComp can perform 
   an internal "capability announcement" to indicate that additional 
   memory or CPU cycles are available. This means that it is generally 
   sufficient to set fixed values for each application defined parameter 
   (there is no need to provide an external, application-specific 
   negotiation mechanism). "

   I don't understand this paragraph. Can somebody tell me what is meant?

7) Section 4.1.1, first paragraph:

   "An endpoint that wants to send compressed data to a remote party must 
   initialize a SigComp layer at the local party prior to its use,..."

   I believe that there are two different things to say here:
   a) The local application MUST initialize the local SigComp layer

   b) The local SigComp compressor MUST initialize the remote decompressor.

   As a minimum, the above sentence should be rephrased as:

   "An endpoint that wants to send compressed data to a remote party must 
   initialize a SigComp layer at the remote party prior to its use,..."
    
8) Section 4.2, first paragraph:

   "The basic SigComp message consists of a block of UDVM bytecode, the 
   first n bytes of which are interpreted as a state identifier that 
   accesses some previously stored state information. "

   I think this is inherited from the UDVM draft and it is not valid 
   anymore. The basic SigComp message will NOT consist only of UDVM
   bytecode. Whatever the basic SigComp message is made of, should be
   reflected in the paragraph.

9) Section 4.3, 7th paragraph:

   "Uncompressed data is also outputted by the UDVM using a specific 
   instruction. Depending on the particular application, the dispatcher 
   decides whether to forward a partially decompressed message 
   immediately to the application, or to buffer and wait for a complete 
   message to be successfully decompressed."

   I disagree with the above statement. The decompressor dispatcher I
   have in my mind does not have any application knowledge. It is,
   therefore, not able to distinguish whether the message is complete,
   or partly received. The dispatcher should limit to pass decompressed
   data to the application. The application must be aware of whether the
   received message is complete or not.

   Therefore, I suggest to remove the mentioned paragraph.

10) Section 5.3., last paragraph

   "If a compression failure occurs when compressing a message then the 
   compressor informs the dispatcher and takes no further action. The 
   dispatcher can then report this failure to the application. "

   I think the last sentence should replace a "can" with a "MUST". 
   In case there is a problem to compress a message, it is a MUST that
   the application is informed. The application may try to other things,
   like sending the message in "uncompressed" mode (better to deliver
   uncompressed messages than not delivering anything at all).

   Suggested paragraph:
   "If a compression failure occurs when compressing a message then the 
   compressor informs the dispatcher and takes no further action. The 
   dispatcher MUST report this failure to the application. The application
   may try other methods to deliver the message."

   Note that the "may" in the last sentence is lowercase, as it does not
   contain normative text, because it affects the application.

11) Section 6.3 Capability announcement

    Question: is this section describing the "Capabilities Announcement" 
    already described in section 4.1.1 ??

    Either we say clearly that it is the same, and we synchronize the
    names (singular vs. plural), or we change one of the names to
    make it clear.

12) Section 6.3., figure 5.

    The figure refers to a Capability announcement "block". What is a 
    block??? It is not defined anywhere. We should make the terminology
    consistent, and therefore, speak about messages, compressed messages,
    compressed data, or similar.

13) Section 8.2, first paragraph.

   "The END-MESSAGE instruction indicates that the compressed message has 
    been successfully decompressed and passed to the dispatcher. Note 
    that the actual uncompressed message is outputted beforehand using 
    the OUTPUT instruction; this allows the UDVM to output each part of 
    the message to the dispatcher as soon as it has been decompressed. "

    I think I am missing something with the last sentence, "each part of
    the message". I thought that if use UDP, one application message 
    equals one UDP packet. If we use TCP, we have delimiters, and one
    application message is delimited. Therefore, what is the UDVM going
    to output to the dispatcher that is NOT an application message???
    In other words, I don't see the possibility of the UDVM outputting
    something else that is not a full, complete application message.
 
That's all.

Thanks a lot,

  Miguel
   

-- 
Miguel-Angel Garcia                     Oy LM Ericsson AB
                                        Jorvas, Finland
mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 5140002

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


From rohc-admin@ietf.org  Tue Feb 19 06:24: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 GAA14196
	for <rohc-archive@odin.ietf.org>; Tue, 19 Feb 2002 06:24:29 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA28094;
	Tue, 19 Feb 2002 06:21:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA27286
	for <rohc@optimus.ietf.org>; Mon, 18 Feb 2002 11:12:24 -0500 (EST)
Received: from sm.luth.se (ny.sm.luth.se [130.240.3.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06669
	for <rohc@ietf.org>; Mon, 18 Feb 2002 11:12:19 -0500 (EST)
Received: (from majordomo@localhost)
	by sm.luth.se (8.10.2+Sun/8.10.0) id g1IGCLG00540
	for rohc-outgoing; Mon, 18 Feb 2002 17:12:21 +0100 (MET)
X-Authentication-Warning: ny.sm.luth.se: majordomo set sender to owner-robhc@cdt.luth.se using -f
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by sm.luth.se (8.10.2+Sun/8.10.0) with ESMTP id g1IGBiB00297
	for <rohc@cdt.luth.se>; Mon, 18 Feb 2002 17:11:50 +0100 (MET)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06500;
	Mon, 18 Feb 2002 11:11:39 -0500 (EST)
Message-Id: <200202181611.LAA06500@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rohc@cdt.luth.se
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [rohc] I-D ACTION:draft-ietf-rohc-tcp-requirements-03.txt
Date: Mon, 18 Feb 2002 11:11:38 -0500
Precedence: bulk
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 mailing list for Robust Header Compression WG is rohc@ietf.org
This mail was sent via the old rohc@cdt.luth.se list
The rohc@cdt.luth.se list will soon be inactive
---
--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		: Requirements for ROHC IP/TCP Header Compression
	Author(s)	: L. Jonsson
	Filename	: draft-ietf-rohc-tcp-requirements-03.txt
	Pages		: 9
	Date		: 15-Feb-02
	
This document contains requirements for the IP/TCP header compression
scheme (profile) to be developed by the ROHC WG. The structure of
this document is inherited from the document defining IP/UDP/RTP
requirements for ROHC.

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

ENCODING mime
FILE /internet-drafts/draft-ietf-rohc-tcp-requirements-03.txt

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

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

--OtherAccess--

--NextPart--


---
Mailing list for Robust Header Compression WG
Archive: http://www.cdt.luth.se/rohc/


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


From rohc-admin@ietf.org  Tue Feb 19 06:24:42 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 GAA14213
	for <rohc-archive@odin.ietf.org>; Tue, 19 Feb 2002 06:24:42 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA28163;
	Tue, 19 Feb 2002 06:22:06 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA27354
	for <rohc@optimus.ietf.org>; Mon, 18 Feb 2002 11:12:35 -0500 (EST)
Received: from sm.luth.se (ny.sm.luth.se [130.240.3.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06681
	for <rohc@ietf.org>; Mon, 18 Feb 2002 11:12:29 -0500 (EST)
Received: (from majordomo@localhost)
	by sm.luth.se (8.10.2+Sun/8.10.0) id g1IGCWL00622
	for rohc-outgoing; Mon, 18 Feb 2002 17:12:32 +0100 (MET)
X-Authentication-Warning: ny.sm.luth.se: majordomo set sender to owner-robhc@cdt.luth.se using -f
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by sm.luth.se (8.10.2+Sun/8.10.0) with ESMTP id g1IGBnB00327
	for <rohc@cdt.luth.se>; Mon, 18 Feb 2002 17:11:50 +0100 (MET)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06522;
	Mon, 18 Feb 2002 11:11:44 -0500 (EST)
Message-Id: <200202181611.LAA06522@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rohc@cdt.luth.se
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [rohc] I-D ACTION:draft-ietf-rohc-sigcomp-04.txt
Date: Mon, 18 Feb 2002 11:11:44 -0500
Precedence: bulk
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 mailing list for Robust Header Compression WG is rohc@ietf.org
This mail was sent via the old rohc@cdt.luth.se list
The rohc@cdt.luth.se list will soon be inactive
---
--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 (SigComp)
	Author(s)	: R. Price, H. Hannu et al.
	Filename	: draft-ietf-rohc-sigcomp-04.txt
	Pages		: 51
	Date		: 15-Feb-02
	
This document defines SigComp, a solution for compressing messages 
generated by text-based protocols such as SIP [SIP] and RTSP [RTSP]. 
The architecture and pre-requisites of SigComp are outlined, along 
with the format of the SigComp message.

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

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

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

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

--OtherAccess--

--NextPart--


---
Mailing list for Robust Header Compression WG
Archive: http://www.cdt.luth.se/rohc/


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


From rohc-admin@ietf.org  Tue Feb 19 06:26: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 GAA14241
	for <rohc-archive@odin.ietf.org>; Tue, 19 Feb 2002 06:26:00 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA28251;
	Tue, 19 Feb 2002 06:22:59 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA27398
	for <rohc@optimus.ietf.org>; Mon, 18 Feb 2002 11:13:17 -0500 (EST)
Received: from sm.luth.se (ny.sm.luth.se [130.240.3.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06701
	for <rohc@ietf.org>; Mon, 18 Feb 2002 11:13:11 -0500 (EST)
Received: (from majordomo@localhost)
	by sm.luth.se (8.10.2+Sun/8.10.0) id g1IGDDF00892
	for rohc-outgoing; Mon, 18 Feb 2002 17:13:13 +0100 (MET)
X-Authentication-Warning: ny.sm.luth.se: majordomo set sender to owner-robhc@cdt.luth.se using -f
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by sm.luth.se (8.10.2+Sun/8.10.0) with ESMTP id g1IGCJB00523
	for <rohc@cdt.luth.se>; Mon, 18 Feb 2002 17:12:20 +0100 (MET)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06658;
	Mon, 18 Feb 2002 11:12:14 -0500 (EST)
Message-Id: <200202181612.LAA06658@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rohc@cdt.luth.se
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [rohc] I-D ACTION:draft-ietf-rohc-sigcomp-extended-01.txt
Date: Mon, 18 Feb 2002 11:12:14 -0500
Precedence: bulk
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 mailing list for Robust Header Compression WG is rohc@ietf.org
This mail was sent via the old rohc@cdt.luth.se list
The rohc@cdt.luth.se list will soon be inactive
---
--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-01.txt
	Pages		: 16
	Date		: 15-Feb-02
	
This document defines extended operation mechanisms, explicit
acknowledgements and shared compression, for [SIGCOMP]. When these
extended mechanisms are applied an increase of the compression
efficiency is expected.

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

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

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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--


---
Mailing list for Robust Header Compression WG
Archive: http://www.cdt.luth.se/rohc/


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


From rohc-admin@ietf.org  Tue Feb 19 06:28: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 GAA14281
	for <rohc-archive@odin.ietf.org>; Tue, 19 Feb 2002 06:28:36 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA28466;
	Tue, 19 Feb 2002 06:25:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA26842
	for <rohc@optimus.ietf.org>; Tue, 19 Feb 2002 05:51:41 -0500 (EST)
Received: from sm.luth.se (ny.sm.luth.se [130.240.3.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13949
	for <rohc@ietf.org>; Tue, 19 Feb 2002 05:51:38 -0500 (EST)
Received: (from majordomo@localhost)
	by sm.luth.se (8.10.2+Sun/8.10.0) id g1JApbv26710
	for rohc-outgoing; Tue, 19 Feb 2002 11:51:37 +0100 (MET)
X-Authentication-Warning: ny.sm.luth.se: majordomo set sender to owner-robhc@cdt.luth.se using -f
Received: from marjan.fesb.hr (marjan.fesb.hr [161.53.166.3])
	by sm.luth.se (8.10.2+Sun/8.10.0) with ESMTP id g1JAojB26026
	for <rohc@cdt.luth.se>; Tue, 19 Feb 2002 11:50:48 +0100 (MET)
Received: (from root@localhost)
	by marjan.fesb.hr (8.9.3/8.9.3) id LAA10905
	for rohc@cdt.luth.se; Tue, 19 Feb 2002 11:50:36 +0100 (MET)
Received: from fesb.hr (nobody@localhost [127.0.0.1])
	by marjan.fesb.hr (8.9.3/8.9.3) with SMTP id LAA10897;
	Tue, 19 Feb 2002 11:50:12 +0100 (MET)
From: tijana@fesb.hr
Received: from eins.siemens.at ([193.81.246.11]) (proxying for 141.29.126.52, 158.226.135.107, unknown)
        (SquirrelMail authenticated user tijana)
        by www.fesb.hr with HTTP;
        Tue, 19 Feb 2002 11:50:28 -0100 (MET)
Message-ID: <4790.193.81.246.11.1014115828.squirrel@www.fesb.hr>
Date: Tue, 19 Feb 2002 11:50:28 -0100 (MET)
Subject: RE: [rohc] Invitation to the 3rd ROHC interop test
To: rohc@cdt.luth.se
Cc: graham.williamson@roke.co.uk, julije.ozegovic@fesb.hr,
        Maximilian.Riegel@icn.siemens.de, abigail.surtees@roke.co.uk
X-Mailer: SquirrelMail (version 1.0.6)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: by AMaViS perl-11
Precedence: bulk
Content-Transfer-Encoding: 8bit
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

The mailing list for Robust Header Compression WG is rohc@ietf.org
This mail was sent via the old rohc@cdt.luth.se list
The rohc@cdt.luth.se list will soon be inactive
---
Hi,
is there a possibility of initial TCP header compression 
interoperability being tested during the next interop event?

We are the University team from Split and we are working on a 
implementation of EPIC-LITE as the encoding framework of ROHC. 
Our implementation is now finished and it would be very interesting for us
to participate in interoperability test to get a proof of the validity of 
our work on TCP header compression (and also to meet other people involved
in header compression problematic:-).

Best regards

Tijana & FESB Epic Team

---
Mailing list for Robust Header Compression WG
Archive: http://www.cdt.luth.se/rohc/


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


From rohc-admin@ietf.org  Tue Feb 19 10:28: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 KAA23930
	for <rohc-archive@odin.ietf.org>; Tue, 19 Feb 2002 10:28:55 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA12006;
	Tue, 19 Feb 2002 10:24:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA09594
	for <rohc@optimus.ietf.org>; Tue, 19 Feb 2002 09:46:26 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21355
	for <rohc@ietf.org>; Tue, 19 Feb 2002 09:46:22 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g1JEjrhM025592
	for <rohc@ietf.org>; Tue, 19 Feb 2002 15:45:53 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt461 ; Tue Feb 19 15:45:42 2002 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <Z1HYR8TS>; Tue, 19 Feb 2002 15:45:41 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E9A272@ESEALNT419.al.sw.ericsson.se>
From: "Hans Hannu (EPL)" <Hans.Hannu@epl.ericsson.se>
To: "'Lawrence Conroy'" <lwc@roke.co.uk>
Cc: rohc@ietf.org
Date: Tue, 19 Feb 2002 15:44:42 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [rohc] RE: non-default capabilities
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,

> Having had a (very) quick look at the SigComp draft, I don't see how 
> the capabilities
> for non-default algorithms are supported - these were discussed on 
> the list recently,
> but how does an end point report the algorithms it supports (i.e. the 
> states it has
> available) to its peer (remote) entity?

I think this can be done by using the Requested feedback format as described in draft-ietf-rohc-sigcomp-extended-01.txt.

I have some more issues on how the two drafts (sigcomp and sigcomp-extended) with the mechanisms may interact, e.g. how to perform what is described above. I'll collect those and put them into a separate mail.

BR
/Hans H


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


From rohc-admin@ietf.org  Tue Feb 19 13:38: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 NAA00851
	for <rohc-archive@odin.ietf.org>; Tue, 19 Feb 2002 13:38:32 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA25983;
	Tue, 19 Feb 2002 13:34:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA25953
	for <rohc@optimus.ietf.org>; Tue, 19 Feb 2002 13:34:27 -0500 (EST)
Received: from cundall.co.uk (dorfl.roke.co.uk [193.118.205.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA00637
	for <rohc@ietf.org>; Tue, 19 Feb 2002 13:34:25 -0500 (EST)
Received: from [193.118.192.40] ([193.118.192.40] verified) by cundall.co.uk (Stalker SMTP Server 1.7) with ESMTP id S.0000062610; Tue, 19 Feb 2002 18:34:26 +0000
Mime-Version: 1.0
X-Sender: lwc@193.118.192.24
Message-Id: <p05100300b89841904836@[193.118.192.40]>
In-Reply-To: 
  <A943FD84BD9ED41193460008C791805003E9A272@ESEALNT419.al.sw.ericsson.se>
References: 
  <A943FD84BD9ED41193460008C791805003E9A272@ESEALNT419.al.sw.ericsson.se>
Date: Tue, 19 Feb 2002 18:34:18 +0000
To: "Hans Hannu (EPL)" <Hans.Hannu@epl.ericsson.se>
From: Lawrence Conroy <lwc@roke.co.uk>
Subject: [rohc] RE: non-default capabilities
Cc: rohc@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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,
    Why the heck is sending a list of identifiers of available decompression
algorithms in the extended draft?

Did I miss some comment in the postings (see third extract below), in
which someone mentioned that they thought they had IPR on this?

I am surprised at Richard's comment (see second extract) in which he
says that this has been removed due to Hans's IPR concerns. Is this
correct?

I don't understand how anyone can have IPR on capability announcement.
It's a core feature or many protocols (SDP for example, in which an
end point reports that it is ready and willing to accept data streams
compressed using a codec or set of codecs).

I await some clarification with interest - I suspect that somewhere
the lines have been scrambled.

BR,
    Lawrence

At 3:44 pm +0100 19/2/02, Hans Hannu (EPL) wrote:
>Hi,
>
>>  Having had a (very) quick look at the SigComp draft, I don't see how
>>  the capabilities
>>  for non-default algorithms are supported - these were discussed on
>>  the list recently,
>>  but how does an end point report the algorithms it supports (i.e. the
>>  states it has
>>  available) to its peer (remote) entity?
>
>I think this can be done by using the Requested feedback format as 
>described in draft-ietf-rohc-sigcomp-extended-01.txt.
>
>I have some more issues on how the two drafts (sigcomp and 
>sigcomp-extended) with the mechanisms may interact, e.g. how to 
>perform what is described above. I'll collect those and put them 
>into a separate mail.
>
and...
At 2:21 pm +0000 18/2/02, Price, Richard wrote:
>For the well-known but optional decompression algorithms, we need to 
>assign a certain
>identifier to each algorithm and then send a list of these 
>identifiers from the
>decompressor to the compressor. The compressor can then pick an 
>algorithm from the list
>or choose to download its own.
>
>A mechanism to perform the above task was intended to be part of the 
>SigComp draft, but
>had to be deleted due to Hans' IPR concerns. Currently the 
>compressor can only choose
>between mandatory default decompression algorithms (supported at all 
>decompressors) and
>downloading new algorithms in the form of bytecode.
>
>Hans: Would it be possible to provide some alternative text for the 
>above algorithm
>negotiation mechanism, such that your IPR concerns disappear?

and much earlier....
At 12:57 pm +0000 11/2/02, Hans Hannu wrote:
>Hi Zhigang,
>
>>  In section 5.1, I think we could add the 3rd option as follows:
>>
>>  3. If there are pre-defined UDVM codes for well-known algorithms,
>>  a compressor only needs to send the code_ID (e.g. some
>>  pre-defined index value or the MD5 hash value of the code) to
>>  its peer decompressor. The decompressor can then populate the code
>>  locally.
>
>As the sigcomp messages are preceded with a state identifier this 
>third option seems to be rather straight forward.
>
>BR
>/Hans H

-- 
lwc@roke.co.uk: +44 1794 833666::<my opinions>:

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


From rohc-admin@ietf.org  Wed Feb 20 06:18: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 GAA26855
	for <rohc-archive@odin.ietf.org>; Wed, 20 Feb 2002 06:18:28 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA17022;
	Wed, 20 Feb 2002 06:07:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA16990
	for <rohc@optimus.ietf.org>; Wed, 20 Feb 2002 06:07:30 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26750
	for <rohc@ietf.org>; Wed, 20 Feb 2002 06:07:26 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g1KB6whM006930
	for <rohc@ietf.org>; Wed, 20 Feb 2002 12:06:59 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt461 ; Wed Feb 20 12:06:57 2002 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKDTPZF>; Wed, 20 Feb 2002 11:57:23 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E31E00@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'Lawrence Conroy'" <lwc@roke.co.uk>
Cc: rohc@ietf.org
Subject: RE: [rohc] non-default capabilities
Date: Wed, 20 Feb 2002 12:06:29 +0100
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

> In all cases in my previous posting, I was talking only about
> ->DECOMPRESSION<- algorithm support (default or otherwise).
> 
> I had assumed that choosing a default decompression algorithm
> was still ongoing - Is there strong disagreement that there
> should be one (albeit *which* one is still under consideration)?

Lawrence,

The major argument for defining the UDVM was to avoid this discussion
about decompressor algorithms. By defining the UDVM, we do not need to
standardize the decompression algorithms, but if we start this over
again I think we may start questioning the UDVM approach. Especially
if we start to discuss requiring a "default algorithm", I think we are
once again opening a can of worms.

> Why the heck is sending a list of identifiers of available
> decompression algorithms in the extended draft?

I do not think this is what is there. I agree that the principle you
mention may probably not be an IPR-problem, but if this is done by 
sending acknowledges of established state ("pre-loaded"), I guess there
might be IPR concerns about that. Without having an opinion on that, I
can see a difference between the general principle and how the mechanism
is provided. 

> Did I miss some comment in the postings (see third extract below),
> in which someone mentioned that they thought they had IPR on this?

Note:
When someone indicates that they know of potential IPR, it does not
necessary mean that it is their own IPR. I hope we are all looking for
potential IPR's on the technology we are standardizing, so that we can
indicate this, or avoid the technology when that is desirable.

Rgds,
/L-E

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


From rohc-admin@ietf.org  Wed Feb 20 06:18: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 GAA26868
	for <rohc-archive@odin.ietf.org>; Wed, 20 Feb 2002 06:18:30 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA17148;
	Wed, 20 Feb 2002 06:11:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA17114
	for <rohc@optimus.ietf.org>; Wed, 20 Feb 2002 06:11:44 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26811
	for <rohc@ietf.org>; Wed, 20 Feb 2002 06:11:40 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g1KBBDhM013268
	for <rohc@ietf.org>; Wed, 20 Feb 2002 12:11:13 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt461 ; Wed Feb 20 12:11:10 2002 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <Z1HYS6HV>; Wed, 20 Feb 2002 12:10:21 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E9A27B@ESEALNT419.al.sw.ericsson.se>
From: "Hans Hannu (EPL)" <Hans.Hannu@epl.ericsson.se>
To: "'Lawrence Conroy'" <lwc@roke.co.uk>, rohc@ietf.org
Subject: RE: [rohc] RE: non-default capabilities
Date: Wed, 20 Feb 2002 12:10:44 +0100
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, 

The proposal that is somewhat described in SigComp and SigComp-extended is not exactly like the mechanism in SDP as this proposal can be interpreted as an explicit acknowledgement for an established state, which is one feature described in SigComp extended. Thus, a capability announcement mechanism including the reserved state identifiers for decompression algorithms, may also be used for other mechanisms in SigComp-extended. 

The IPR considerations chapter in SigComp-extended is there to notify that there might possible be IPRs related to the features described in that draft. Then it is up to the people who implement those feature to make the call whether they think that there may or may not be any IPRs on those features. But, please stop trying to convince people what to think about IPRs. If you do not think that there might possible be IPRs on a specific feature why do you not just go ahead and implement it.

>     Why the heck is sending a list of identifiers of 
> available decompression
> algorithms in the extended draft?

Well, that mechanism is not really in any of the drafts. The two drafts are not exactly fully compliant yet, but I'm working on this and will get a suggestion out to the list soon.

BR
/Hans H

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


From rohc-admin@ietf.org  Wed Feb 20 07:54: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 HAA28987
	for <rohc-archive@odin.ietf.org>; Wed, 20 Feb 2002 07:54:29 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA21131;
	Wed, 20 Feb 2002 07:51:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA21097
	for <rohc@optimus.ietf.org>; Wed, 20 Feb 2002 07:51:24 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28922
	for <rohc@ietf.org>; Wed, 20 Feb 2002 07:51:20 -0500 (EST)
Received: from esealnt409.al.sw.ericsson.se (ESEALNT409.al.sw.ericsson.se [153.88.251.32])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g1KCoqhM004308
	for <rohc@ietf.org>; Wed, 20 Feb 2002 13:50:52 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt409.al.sw.ericsson.se ; Wed Feb 20 13:49:57 2002 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <Z1HYTCNJ>; Wed, 20 Feb 2002 13:50:51 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E9A27E@ESEALNT419.al.sw.ericsson.se>
From: "Hans Hannu (EPL)" <Hans.Hannu@epl.ericsson.se>
To: "'Miguel A. Garcia'" <Miguel.A.Garcia@ericsson.com>, rohc@ietf.org
Subject: RE: [rohc] draft-ietf-rohc-sigcomp-04.txt
Date: Wed, 20 Feb 2002 13:49:54 +0100
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 Miguel,

Thanks for your comments. I've tried to provide you with some answers. 

> 1) Section 1, Introduction, 5th paragraph:
>    I would suggest to rephrase and split the sentences into different 
>    paragraphs, one describing the scenario that SigComp is trying to
>    solve (an endpoint - proxy scenario) and the other describing the
>    ability of SigComp to run over connectionless and c.o. transports.

Is it ok if we just split the sentence as:

"This document focuses on the signaling scenario where an endpoint 
 sends and receives data to/from an outbound/inbound proxy. However, SigComp
 may be applicable to other scenarios with multiple endpoints 
 compressing and decompressing data.
 
 SigComp is designed to run over both connectionless and connection-
 oriented transports."

> 2) Section 2, Terminology, definition of Application:
> 
>      "c) decides whether state information may be saved by SigComp "
> 
>    I believe that the application does not decided to save state
>    information, but the application "authorizes to save state 
>    information based on a request from the SigComp layer".

I guess we could make the change as you suggest.

"c) authorizes to save state information based on a request from the SigComp layer"
 
> 3) Section 3, SigComp architecture, 2nd paragraph:
> 
>    "SigComp is typically offered to applications as a "shim" layer 
>    between the application and the transport. Note however that for 
>    certain applications the compressed SigComp message may be passed 
>    back to the application itself for additional processing before 
>    transmission. For example, the application may wish to apply 
>    encryption to the compressed message before handing it to the 
>    transport. "
> 
>    I don't think this scenario is possible. To my understanding, 
>    there are two types of encryption: end-to-end and hop-by-hop.

This roles back to whether SigComp is applied IP end-to-end (Endpoint - first proxy ), or "SIP end-to-end" (SIP endpoint to SIP endpoint). 
     
>    I would like to hear comments on the above statements. And 
>    certainly clarify what is the relationship between the application
>    and SigComp. 

I think this comes back to which scenario we want to solve. If it is the SIP end-to-end scenario with encryption, this may probably make SIP/SigComp require an assigned port number and SigComp would not be regarded as a shim layer to SIP, but the implementation would have to be totally integrated. 

>    Particularly it needs to be clarified which layer
>    is responsible to forward the message: the SigComp layer or the
>    application layer.

With my current understanding of our work and if it is as you say then I think it does not make sense to pass up a compressed message to the application to forward the SigComp message.  
 
> 4) Section 3, SigComp architecture, Figure 1.
> 
>    The figure shows 2 different applications. In my mind, there 
>    should be one and only one application, together with a text 
>    that describes that there is one SigComp layer instance per
>    application.

This approach seems to have some good and valid arguments along with it. 

> 5) Section 3.2, first paragraph:

>    In order to avoid confusion with two applications running in the
>    same local host and making use of SigComp, I would suggest 
> to rephrase:
> 
>    "The local and remote applications that wish to communicate MUST 
>    initially agree on a common set of values for these parameters."
 
I think this is a good suggestion.
 
> 7) Section 4.1.1, first paragraph:
> 
 
>    As a minimum, the above sentence should be rephrased as:
> 
>    "An endpoint that wants to send compressed data to a 
> remote party must 
>    initialize a SigComp layer at the remote party prior to 
> its use,..."

This is good for clarification.

>     
> 8) Section 4.2, first paragraph:
> 
>    "The basic SigComp message consists of a block of UDVM 
> bytecode, the 
>    first n bytes of which are interpreted as a state identifier that 
>    accesses some previously stored state information. "
> 
>    I think this is inherited from the UDVM draft and it is not valid 
>    anymore. The basic SigComp message will NOT consist only of UDVM
>    bytecode. Whatever the basic SigComp message is made of, should be
>    reflected in the paragraph.

There is a note in the draft about solving the identification of different types of messages by reserving state identifiers. However, I now think that this is not possible for the following reason:

* SigComp do not know the length of the state identifier prior to the capability announcement.
- As SigComp does separate flows, SigComp needs to carry the hash length for each message. 

I think this make it valid to introduce some bits to identify the particular message type. Thus, the basic SigComp message format would change to something like this:

     0   1   2   3   4   5   6   7 
   +---+---+---+---+---+---+---+---+ 
   |  MT   |Reserv.|  hash length  | 
   +---+---+---+---+---+---+---+---+ 
   |                               | 
   :   state_identifier (n-bytes)  :  
   |                               | 
   +---+---+---+---+---+---+---+---+ 
   |                               | 
   :    Remaining UDVM bytecode    : 
   |                               | 
   +---+---+---+---+---+---+---+---+ 

The MT, Message Type, would indicate what type of message it is, e.g. SigComp request/announcement, "ordinary" SigComp compressed message.


> 9) Section 4.3, 7th paragraph:
> 
>    "Uncompressed data is also outputted by the UDVM using a specific 
>    instruction. Depending on the particular application, the 
> dispatcher 
>    decides whether to forward a partially decompressed message 
>    immediately to the application, or to buffer and wait for 
> a complete 
>    message to be successfully decompressed."
> 
>    I disagree with the above statement. The decompressor dispatcher I
>    have in my mind does not have any application knowledge. It is,
>    therefore, not able to distinguish whether the message is complete,
>    or partly received. The dispatcher should limit to pass 
> decompressed
>    data to the application. The application must be aware of 
> whether the
>    received message is complete or not.
> 
>    Therefore, I suggest to remove the mentioned paragraph.

I tend to agree with you on this. As a decompression failure/success check is done on the whole decompressed message this statement contradict this.

 > 10) Section 5.3., last paragraph

>    I think the last sentence should replace a "can" with a "MUST". 
>    In case there is a problem to compress a message, it is a MUST that
>    the application is informed. 

I think you're right on this.

> 11) Section 6.3 Capability announcement
> 
>     Question: is this section describing the "Capabilities 
> Announcement" 
>     already described in section 4.1.1 ??

Those sections are related, and we should synchronize the names.

> 12) Section 6.3., figure 5.
> 
>     The figure refers to a Capability announcement "block". 

Yes, we need to define the term "block". What do you think about the following:

"Capability announcement block"
formatted capability announcement information

> 13) Section 8.2, first paragraph.

See my comment to bullet 9).

BR
/Hans H

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


From rohc-admin@ietf.org  Wed Feb 20 10:19: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 KAA03304
	for <rohc-archive@odin.ietf.org>; Wed, 20 Feb 2002 10:19:17 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA28862;
	Wed, 20 Feb 2002 10:13:42 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA28829
	for <rohc@optimus.ietf.org>; Wed, 20 Feb 2002 10:13:40 -0500 (EST)
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 KAA03097
	for <rohc@ietf.org>; Wed, 20 Feb 2002 10:13:36 -0500 (EST)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <1S9WNLHN>; Wed, 20 Feb 2002 15:12:28 -0000
Message-ID: <76C92FBBFB58D411AE760090271ED4186F9FCA@rsys002a.roke.co.uk>
From: "Price, Richard" <richard.price@roke.co.uk>
To: "'Lars-Erik Jonsson (EPL)'" <Lars-Erik.Jonsson@epl.ericsson.se>,
        "Conroy, Lawrence (SMTP)" <lwc@roke.co.uk>
Cc: rohc@ietf.org
Date: Wed, 20 Feb 2002 15:12:25 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="------------InterScan_NT_MIME_Boundary"
Subject: [rohc] Default decompression algorithms
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"

> > In all cases in my previous posting, I was talking only about
> > ->DECOMPRESSION<- algorithm support (default or otherwise).
> > 
> > I had assumed that choosing a default decompression algorithm
> > was still ongoing - Is there strong disagreement that there
> > should be one (albeit *which* one is still under consideration)?

Hi Lars-Erik and Lawrence,

To help us decide whether "default" decompression algorithms should be
included within SigComp, we need to understand the advantages of the UDVM
approach and whether we would be negating them somehow by standardising
default algorithms.

The overall SigComp solution determines which compression algorithm to use
by the following process:

1   Decompressor announces its available resources to the compressor.

2   Compressor makes a choice about how best to use these resources.

In a typical compression scheme the "resources" offered by the decompressor
would be a list of supported algorithms; the compressor could then select
any algorithm supported by both itself and by the decompressor. Clearly a
mandatory default algorithm must be supported at both ends, so that at least
one algorithm is always available for the compressor to use.

With the UDVM approach the "resources" offered by the decompressor are its
available memory and processing power, the minimum acceptable compression
ratio etc. The compressor has freedom to use any algorithm it likes,
provided that it can be downloaded and run at the decompressor using only
the offered resources.

Of course, there is nothing to stop the decompressor from offering both types
of resources to the compressor (memory, processing power and a selection of
well-known algorithms). The compressor can then choose between downloading a
new algorithm and using one of the algorithms already available at the
decompressor.

> By defining the UDVM, we do not need to standardize the decompression
> algorithms, but if we start this over again I think we may start
> questioning the UDVM approach.

Making one or more of these well-known algorithms mandatory at the
decompressor doesn't contradict the UDVM approach because the decision on
which algorithm to use (or whether to download a new one) is still made by
the compressor. So we have a "win-win" situation; the compressor downloads
a new algorithm to the decompressor when it judges the overall performance
to be better than using one of the existing algorithms.

The cost of making an algorithm mandatory is that (read-only) memory needs
to be provided to store the code for the algorithm, plus any additional
IPR claims that are introduced by supporting the algorithm.

> The major argument for defining the UDVM was to avoid this discussion
> about decompressor algorithms.

In my opinion the major argument for the UDVM is its technical performance!
A downloaded UDVM algorithm can be tailored precisely to compress the
output of one particular SIP implementation, which gives a significantly
improved compression ratio compared to even an algorithm designed for
"generic SIP".

I certainly don't want to give the impression that the UDVM approach is a
compromise due to time pressure, or has inferior performance in any way to
the conventional approach of offering a list of well-known algorithms. I
would be very happy to include both approaches in the SigComp solution and
leave the decision on which to use to the compressor.

> Especially if we start to discuss requiring a "default algorithm", I
> think we are once again opening a can of worms.

The term "default decompression algorithm" is probably misleading, because
more than one algorithm can be supported as mandatory. I don't think that
this opens a can of worms since there is no need to favour one algorithm
over any other - the more we support at the decompressor the better.

One final thought: in the current SigComp draft the list of mandatory and
optional well-known algorithms is currently part of the "application-
defined parameters". Therefore we only need to make recommendations about
what this list should contain; the final decision is made by particular
applications such as SIP. So for the wireless environment 3GPP will be
able to choose their own list of mandatory and optional algorithms.

Regards,

Richard

--------------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 Feb 20 11:23: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 LAA05315
	for <rohc-archive@odin.ietf.org>; Wed, 20 Feb 2002 11:23:41 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA02311;
	Wed, 20 Feb 2002 11:20:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA02280
	for <rohc@optimus.ietf.org>; Wed, 20 Feb 2002 11:20:41 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05204
	for <rohc@ietf.org>; Wed, 20 Feb 2002 11:20:37 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g1KGK8h01596;
	Wed, 20 Feb 2002 11:20:09 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g1KGK7C06369;
	Wed, 20 Feb 2002 11:20:07 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <FAMDRP3Z>; Wed, 20 Feb 2002 11:20:07 -0500
Message-ID: <87609AFB433BD5118D5E0002A52CD7540156FA1B@zcard0k6.ca.nortel.com>
From: "Abbie Barbir"<abbieb@nortelnetworks.com>
To: "Price, Richard" <richard.price@roke.co.uk>,
        "'Lars-Erik Jonsson (EPL)'" <Lars-Erik.Jonsson@epl.ericsson.se>,
        "Conroy, Lawrence (SMTP)" <lwc@roke.co.uk>
Cc: rohc@ietf.org
Subject: RE: [rohc] Default decompression algorithms
Date: Wed, 20 Feb 2002 11:20:03 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1BA2A.73E9F5F0"
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 message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1BA2A.73E9F5F0
Content-Type: text/plain;
	charset="iso-8859-1"



> -----Original Message-----
> From: Price, Richard [mailto:richard.price@roke.co.uk]
> Sent: Wednesday, February 20, 2002 10:12 AM
> To: 'Lars-Erik Jonsson (EPL)'; Conroy, Lawrence (SMTP)
> Cc: rohc@ietf.org
> Subject: [rohc] Default decompression algorithms
> 
> 

------------------- SNIP SNIP

> Making one or more of these well-known algorithms mandatory at the
> decompressor doesn't contradict the UDVM approach because the 
> decision on
> which algorithm to use (or whether to download a new one) is 
> still made by
> the compressor. So we have a "win-win" situation; the 
> compressor downloads
> a new algorithm to the decompressor when it judges the 
> overall performance
> to be better than using one of the existing algorithms.
> 

-------------- 
Can you suggest how this would be done (implemented) from the compressor
end.

abbie 

------_=_NextPart_001_01C1BA2A.73E9F5F0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.89">
<TITLE>RE: [rohc] Default decompression algorithms</TITLE>
</HEAD>
<BODY>
<BR>
<BR>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: Price, Richard [<A HREF="mailto:richard.price@roke.co.uk">mailto:richard.price@roke.co.uk</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: Wednesday, February 20, 2002 10:12 AM</FONT>
<BR><FONT SIZE=2>&gt; To: 'Lars-Erik Jonsson (EPL)'; Conroy, Lawrence (SMTP)</FONT>
<BR><FONT SIZE=2>&gt; Cc: rohc@ietf.org</FONT>
<BR><FONT SIZE=2>&gt; Subject: [rohc] Default decompression algorithms</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

<P><FONT SIZE=2>------------------- SNIP SNIP</FONT>
</P>

<P><FONT SIZE=2>&gt; Making one or more of these well-known algorithms mandatory at the</FONT>
<BR><FONT SIZE=2>&gt; decompressor doesn't contradict the UDVM approach because the </FONT>
<BR><FONT SIZE=2>&gt; decision on</FONT>
<BR><FONT SIZE=2>&gt; which algorithm to use (or whether to download a new one) is </FONT>
<BR><FONT SIZE=2>&gt; still made by</FONT>
<BR><FONT SIZE=2>&gt; the compressor. So we have a &quot;win-win&quot; situation; the </FONT>
<BR><FONT SIZE=2>&gt; compressor downloads</FONT>
<BR><FONT SIZE=2>&gt; a new algorithm to the decompressor when it judges the </FONT>
<BR><FONT SIZE=2>&gt; overall performance</FONT>
<BR><FONT SIZE=2>&gt; to be better than using one of the existing algorithms.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

<P><FONT SIZE=2>-------------- </FONT>
<BR><FONT SIZE=2>Can you suggest how this would be done (implemented) from the compressor end.</FONT>
</P>

<P><FONT SIZE=2>abbie </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1BA2A.73E9F5F0--

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


From rohc-admin@ietf.org  Wed Feb 20 12:36: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 MAA10359
	for <rohc-archive@odin.ietf.org>; Wed, 20 Feb 2002 12:36:02 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA09341;
	Wed, 20 Feb 2002 12:33:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA09307
	for <rohc@optimus.ietf.org>; Wed, 20 Feb 2002 12:33:13 -0500 (EST)
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 MAA10130
	for <rohc@ietf.org>; Wed, 20 Feb 2002 12:33:09 -0500 (EST)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <1S9WNLT2>; Wed, 20 Feb 2002 17:32:00 -0000
Message-ID: <76C92FBBFB58D411AE760090271ED4186F9FCC@rsys002a.roke.co.uk>
From: "Price, Richard" <richard.price@roke.co.uk>
To: "'Hans Hannu (EPL)'" <Hans.Hannu@epl.ericsson.se>,
        "Conroy, Lawrence (SMTP)" <lwc@roke.co.uk>,
        "'Lars-Erik Jonsson (EPL)'"
	 <Lars-Erik.Jonsson@epl.ericsson.se>,
        rohc@ietf.org
Date: Wed, 20 Feb 2002 17:31:54 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="------------InterScan_NT_MIME_Boundary"
Subject: [rohc] IPR situation
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,

Some background on the IPR situation:

Based on previous mailing list discussions, I concluded that the IPR issues
on the base SigComp solution were due to the informative description of
how to implement a feedback mechanism rather than the technical content of
the solution. So in release 04 of the SigComp draft I defined the following
list of identifiers as a well-known area of the UDVM memory:

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|        id_length 1        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                           |
:        id_value_1         :
|                           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         :         : 
         :         : 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|        id_length n        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                           |
:        id_value_n         :
|                           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

If a certain identifier is sent from Endpoint A to Endpoint B, then Endpoint
B knows that the corresponding piece of bytecode is available at Endpoint A
and can be retrieved using the appropriate UDVM instruction.

The aim of the above mechanism was not to provide feedback (although it could
feasibly be used as such) but rather to allow an endpoint to announce support
for a selection of well-known decompression algorithms. Each algorithm would
be given its own unique identifier (e.g. 0 for NULL, 1 for DEFLATE etc.).

I also hoped that the mechanism could be used to indicate support for the
extended operations themselves, by reserving a certain identifier for the
sigcomp-extended draft. Without this ability the extended operations would
have to be negotiated externally to SigComp, or else feedback data would be
sent without knowing whether or not it could be understood by the receiver
(potentially very inefficient).

Unfortunately, including the above mechanism raised IPR concerns from Hans,
so to get the draft out on time I deleted it.

[LWC] Why the heck is sending a list of identifiers of available
      decompression algorithms in the extended draft?

It isn't! Currently the ability to send a list of supported decompression
algorithms isn't available in either draft, so it can only be done externally
to SigComp.

[LEJ] I do not think this is what is there. I agree that the principle you
      mention may probably not be an IPR-problem, but if this is done by 
      sending acknowledges of established state ("pre-loaded"), I guess there
      might be IPR concerns about that. Without having an opinion on that, I
      can see a difference between the general principle and how the mechanism
      is provided.

The actual mechanism provided is as described above, with no mention of what
the identifiers are actually for (e.g. they could be used to retrieve well-
known decompression algorithms, dictionaries of SIP phrases, extended
operation mechanisms etc.).

In fact, the draft didn't include the terms "feedback" or "acknowledgement" at
all.

[LWC] Did I miss some comment in the postings (see third extract below),
      in which someone mentioned that they thought they had IPR on this?

This was done offline - I proposed the above list of identifiers for inclusion
in the SigComp draft, but Hans indicated that he had IPR concerns on it so I
didn't bother.

[LEJ] Note:
      When someone indicates that they know of potential IPR, it does not
      necessary mean that it is their own IPR. I hope we are all looking for
      potential IPR's on the technology we are standardizing, so that we can
      indicate this, or avoid the technology when that is desirable.

My understanding of the IETF approach to dealing with IPRs is that an RFC
includes an IPR statement only as a pointer to an official IPR announcement
made at http://www.ietf.org/ipr.html.

The advantage of the above approach is that as authors, we don't need to make
a decision on whether particular patents are applicable to our work or not.
An IPR statement is only required when an official IPR claim is made, so what
we need to find out is whether anyone would put in such a claim on basic
SigComp if the above announcement mechanism were to be included.

[HH]  The proposal that is somewhat described in SigComp and 
      SigComp-extended is not exactly like the mechanism in SDP as 
      this proposal can be interpreted as an explicit 
      acknowledgement for an established state, which is one 
      feature described in SigComp extended.

I think that the above comment is key to the IPR situation. All that SDP can do
is announce a list of algorithms supported at an endpoint, and this is all that
SigComp needs to be able to do as well. Whether the algorithms are predefined
or downloaded on the fly is not specified by either draft.

As far as I can tell, the IPR concerns appear to apply to one possible use for
announcing some identifiers rather than to the concept itself. Whether the
identifiers are used in an IPR-encumbered manner depends on where these identifiers
come from - are they well-known or are they created on the fly? In fact, the
decision on how to use the identifiers (and hence the IPR situation) is made
by the compressor.

Hans: Would the following statement in basic SigComp solve your IPR concerns?

"The capabilities announcement mechanism MUST only be used to announce support
for well-known algorithms."

[HH]  Thus, a capability announcement mechanism including the reserved state 
      identifiers for decompression algorithms, may also be used 
      for other mechanisms in SigComp-extended.

This is certainly the case, but I don't think that it means an IPR statement is
required on the basic SigComp draft even if it includes the ability to send a
list of identifiers from one endpoint to another. After all, the UDVM can run
any algorithm in existence - some encumbered, some not - and the decision on
which algorithms to run is made by the compressor.

--------------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 Feb 20 15:44: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 PAA19478
	for <rohc-archive@odin.ietf.org>; Wed, 20 Feb 2002 15:44:40 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA19968;
	Wed, 20 Feb 2002 15:41:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA19934
	for <rohc@optimus.ietf.org>; Wed, 20 Feb 2002 15:41:23 -0500 (EST)
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 PAA19337
	for <rohc@ietf.org>; Wed, 20 Feb 2002 15:41:19 -0500 (EST)
Received: from cabo3 (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with SMTP id g1KKfB400300;
	Wed, 20 Feb 2002 21:41:11 +0100 (MET)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: "Price, Richard" <richard.price@roke.co.uk>,
        "'Lars-Erik Jonsson \(EPL\)'" <Lars-Erik.Jonsson@epl.ericsson.se>,
        "Conroy, Lawrence \(SMTP\)" <lwc@roke.co.uk>
Cc: <rohc@ietf.org>
Subject: RE: [rohc] Default decompression algorithms
Date: Wed, 20 Feb 2002 21:41:10 +0100
Message-ID: <NFBBJFHGMCFINEMHAMBGAEGOHHAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <76C92FBBFB58D411AE760090271ED4186F9FCA@rsys002a.roke.co.uk>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
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

> I would be very happy to include both approaches in the SigComp solution

Folks,

we seriously need to combat featuritis at this time.

To me it seems the current draft is about twice as complex as it needs to
be.
We need real time to fix all the small details in that complexity.
Complexity grows at least with some polynomial of the feature set.

If we want to finish in time, we need to focus on removing, not about
adding.

Since anybody can "profile" SigComp to include certain state ab initio, I
would like to propose that we end this discussion now.

Gruesse, Carsten

PS.: When we are last-calling stuff, we can go back to generating nice
informational RFCs with example decompressors.


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


From rohc-admin@ietf.org  Thu Feb 21 02:41: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 CAA10255
	for <rohc-archive@odin.ietf.org>; Thu, 21 Feb 2002 02:41:40 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA00441;
	Thu, 21 Feb 2002 02:38:30 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA00411
	for <rohc@optimus.ietf.org>; Thu, 21 Feb 2002 02:38:29 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.46])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10198
	for <rohc@ietf.org>; Thu, 21 Feb 2002 02:38:27 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g1L7bvZc011109
	for <rohc@ietf.org>; Thu, 21 Feb 2002 08:37:57 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt461 ; Thu Feb 21 08:36:45 2002 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKD4SP6>; Thu, 21 Feb 2002 08:28:07 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E9A283@ESEALNT419.al.sw.ericsson.se>
From: "Hans Hannu (EPL)" <Hans.Hannu@epl.ericsson.se>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Thu, 21 Feb 2002 08:37:13 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [rohc] Comments on draft-ietf-rohc-sigcomp-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

Hi,

I've some comments regarding draft-ietf-rohc-sigcomp-04.txt

1) Figure 1, page 7

The arrow between the state handler and Application may cause some confusion, as it is the dispatcher that handles the communication with the application. I think we should update the figure accordingly, i.e. draw the arrow through the dispatcher.

2) Section 3.2, page 9, minimum_compression_ratio

"Note that this parameter can be less than 1"

With my limited knowledge about different data types this would be a floating point value, then it might be a problem with the next thing: "Any value other than 0". 

I think we need to specify data types for SigComp parameters.

Same place, "standalone SigComp message" needs to be defined in the terminology; e.g.
"Standalone SigComp message"
- A SigComp message that does not include any compressed application message.

3)  Section 3.2, page 11, total_cycles
I think we should change this to "maximum_cycles"

4) Section 4.1.1., page 13, 2nd and 3rd paragraph 

Do we need to say something what actions to take if a response to a SigComp request is not received?

5) Section 4.3, page 15, 3rd paragraph

"Therefore, the dispatcher is responsible for buffering each SigComp message and passing the data to the UDVM when it is requested. " 

What happens if there is no data to get from the buffer, but the UDVM still anticipates to receive more data for the current SigComp message?

6) Section 7.3, page 25, Figure 9
Where the parameter types are described it would be nice if the address range for reference types were listed, e.g. the 0nnnnnn parameter can address even addresses between 0 and 254. The same applies for the multitype type when used as a reference.

BR
/Hans H

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


From rohc-admin@ietf.org  Thu Feb 21 02: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 CAA10294
	for <rohc-archive@odin.ietf.org>; Thu, 21 Feb 2002 02:44:29 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA00603;
	Thu, 21 Feb 2002 02:42:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA00574
	for <rohc@optimus.ietf.org>; Thu, 21 Feb 2002 02:42:34 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.46])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10274
	for <rohc@ietf.org>; Thu, 21 Feb 2002 02:42:32 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g1L7g3Zc013857
	for <rohc@ietf.org>; Thu, 21 Feb 2002 08:42:03 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt461 ; Thu Feb 21 08:41:06 2002 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKD4SWK>; Thu, 21 Feb 2002 08:32:28 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E9A284@ESEALNT419.al.sw.ericsson.se>
From: "Hans Hannu (EPL)" <Hans.Hannu@epl.ericsson.se>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Thu, 21 Feb 2002 08:41:59 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [rohc] Comments draft-ietf-rohc-sigcomp-extended-01.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,

Some comments to draft-ietf-rohc-sigcomp-extended-01.txt:

1) Section 2, Terminology.

This should be synchronized with draft-ietf-rohc-sigcomp-04.txt

2) Section 4.1, Available state(s)
I think "Available" should be changed to "Saved" to avoid confusion.

3) Section 5, page 6, paragraph 2.

"Over reliable and ordered transport the most recent state may be
 used, if the compressor has downloaded such a UDVM instruction code
 to its remote decompressor."

I do not think this text is valid anymore, as the UDVM memory is reinitialised for each new sigComp message, due to security risks.

4) Section 6.1, page 9, last paragraph.

"with the support of all extended operation mechanisms"

The word "all" is not right should be changed to "some" or specify exactly what is supported with that example.

BR
/Hans H

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


From rohc-admin@ietf.org  Thu Feb 21 03:06:38 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 DAA10590
	for <rohc-archive@odin.ietf.org>; Thu, 21 Feb 2002 03:06:38 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA01971;
	Thu, 21 Feb 2002 03:04:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA05656
	for <rohc@optimus.ietf.org>; Wed, 20 Feb 2002 20:50:42 -0500 (EST)
Received: from sm.luth.se (ny.sm.luth.se [130.240.3.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25861
	for <rohc@ietf.org>; Wed, 20 Feb 2002 20:50:38 -0500 (EST)
Received: (from majordomo@localhost)
	by sm.luth.se (8.10.2+Sun/8.10.0) id g1L1oek05255
	for rohc-outgoing; Thu, 21 Feb 2002 02:50:40 +0100 (MET)
X-Authentication-Warning: ny.sm.luth.se: majordomo set sender to owner-robhc@cdt.luth.se using -f
Received: from numenor.qualcomm.com (numenor.qualcomm.com [129.46.51.58])
	by sm.luth.se (8.10.2+Sun/8.10.0) with ESMTP id g1L1ntB05058
	for <rohc@cdt.luth.se>; Thu, 21 Feb 2002 02:49:59 +0100 (MET)
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.12.1/8.12.1/1.0) with ESMTP id g1L1nekQ024838
	for <rohc@cdt.luth.se>; Wed, 20 Feb 2002 17:49:40 -0800 (PST)
Received: from MAHENDRA.qualcomm.com (mahendra.qualcomm.com [129.46.75.104])
	by magus.qualcomm.com (8.12.1/8.12.1/1.0) with ESMTP id g1L1ncLo025111
	for <rohc@cdt.luth.se>; Wed, 20 Feb 2002 17:49:38 -0800 (PST)
Message-Id: <5.1.0.14.2.20020220161431.00a7bcc0@clea.qualcomm.com>
X-Sender: mahendra@clea.qualcomm.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 20 Feb 2002 17:49:31 -0800
To: rohc@cdt.luth.se
From: AC Mahendran <mahendra@qualcomm.com>
Subject: [rohc] Compression Algorithms
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Precedence: bulk
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 mailing list for Robust Header Compression WG is rohc@ietf.org
This mail was sent via the old rohc@cdt.luth.se list
The rohc@cdt.luth.se list will soon be inactive
---

Hi,

Is the ROHC working on any encoder algorithms ? I read the sig-comp and the 
associated UDVM draft, but they don't talk about any encoders.

Can someone point to a list of encoders that are available today ?

thanks,
AC


---
Mailing list for Robust Header Compression WG
Archive: http://www.cdt.luth.se/rohc/


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


From rohc-admin@ietf.org  Thu Feb 21 04:42: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 EAA12028
	for <rohc-archive@odin.ietf.org>; Thu, 21 Feb 2002 04:42:24 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA08226;
	Thu, 21 Feb 2002 04:39:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA08196
	for <rohc@optimus.ietf.org>; Thu, 21 Feb 2002 04:39:23 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11975
	for <rohc@ietf.org>; Thu, 21 Feb 2002 04:39:19 -0500 (EST)
Received: from esealnt406.al.sw.ericsson.se (ESEALNT406.al.sw.ericsson.se [153.88.251.29])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g1L9PMB16007
	for <rohc@ietf.org>; Thu, 21 Feb 2002 10:25:22 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt406.al.sw.ericsson.se ; Thu Feb 21 10:25:19 2002 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKD4ZB4>; Thu, 21 Feb 2002 10:15:44 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E31E02@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'Price, Richard'" <richard.price@roke.co.uk>
Cc: rohc@ietf.org
Date: Thu, 21 Feb 2002 10:25:07 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [rohc] RE: Default decompression algorithms
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

Richard,

> So for the wireless environment 3GPP will be
> able to choose their own list of mandatory and optional algorithms.

Yes, they use to do it that way, but why should WE make any algorithm
mandatory at the decompressor. As you say yourself, the decompressor
can announce what resources it has, and the compressor decides what to
use based on that, but the decompressor does not have to announce any
available algorithms. If it does not, the compressor just do not have
any other choice than to download its own algorithm.

> I would be very happy to include both approaches in the SigComp
> solution and leave the decision on which to use to the compressor.

Simple and well defined solutions with few options are usually
preferable when making standards, at least in the IETF. 

/L-E

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


From rohc-admin@ietf.org  Thu Feb 21 05:32: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 FAA12784
	for <rohc-archive@odin.ietf.org>; Thu, 21 Feb 2002 05:32:21 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA11343;
	Thu, 21 Feb 2002 05:29:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA11314
	for <rohc@optimus.ietf.org>; Thu, 21 Feb 2002 05:29:48 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.46])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12732
	for <rohc@ietf.org>; Thu, 21 Feb 2002 05:29:43 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g1LATFZc000556
	for <rohc@ietf.org>; Thu, 21 Feb 2002 11:29:15 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt461 ; Thu Feb 21 11:28:18 2002 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <Z1HY42KW>; Thu, 21 Feb 2002 11:29:14 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E9A288@ESEALNT419.al.sw.ericsson.se>
From: "Hans Hannu (EPL)" <Hans.Hannu@epl.ericsson.se>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Thu, 21 Feb 2002 11:29:05 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [rohc] SigComp Message and (extended) Returned 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,

As I indicated in a previous mail the two drafts are not fully compliant yet. This is a proposal for solving this.

In my comments to Miguel I explained why we need to signaling the state identifier length (ID length) in each SigComp message, and how the remaining bits can be used for a new basic SigComp message format. 

The reasons for having the ID-length in each SigComp message are the following:
* SigComp do not know the length of the state identifier prior to the capability announcement.
* As SigComp does not separate flows, SigComp needs to carry the hash length (ID length) for each SigComp message.  

The remaining 4-bits can be used for something else, and below is a proposal for the new SigComp basic Message format:

  0   1   2   3   4   5   6   7 
+---+---+---+---+---+---+---+---+ 
|  MT   |Reserv.|    ID length  | 
+---+---+---+---+---+---+---+---+ 
|                               | 
:   state_identifier (n-bytes)  :  
|                               | 
+---+---+---+---+---+---+---+---+ 
|                               | 
:    Remaining UDVM bytecode    : 
|                               | 
+---+---+---+---+---+---+---+---+ 

Instead of reserving a state_identifier for indication of what type of message this is, a Message Type is included. 

To avoid making changes to the UDVM instructions according to message:
http://www.cdt.luth.se/rohc/msg03674.html
and to make use of shared compression it is necessary for an endpoint to know whether its remote endpoint understands the format of the Returned feedback as depicted in Figure 7 of draft-ietf-rohc-sigcomp-extended-01.txt or not. 

Therefore I propose the following changes to the two sigcomp-drafts.

******** changes to draft-ietf-rohc-sigcomp-04.txt *******

Section 4.2. 

The basic SigComp message format is changed to the format above.

* Message Type
MT = '00' --- "ordinary compressed message"
MT = '01' --- "SigComp request message"
MT = '10' --- "SigComp Capability announcement message"
MT = '11' --- "Reserved"

* Reserv.
Bits 2 and 3 is reserved and is set to '00'

* Id length
The length of the state_identifier for this SigComp message
'0000' - 1 byte state_identifier
'0001' - 2 bytes state_identifier
...
'1111' - 16 bytes state_identifier

******** Changes to draft-ietf-rohc-sigcomp-extended-01.txt *******

Section 6.1.

The basic SigComp message format is changed to the format above.

The reserved bit 2, is used to indicate to the remote endpoint the understanding of the Returned feedback format as depicted in Figure 7.  Thus, an endpoint sets bit 2, in every sent SigComp message to indicate the understanding of the Returned feedback format. If two communicating end-points both sets bit 2. They MUST use the Returned feedback format as depicted in Figure 7. In any other case must no assumption be drawn about the format of the Returned feedback format.

Note: Setting bit 2 does not mandate an endpoint to use SigComp-extended, but only that it understands the Returned feedback format and will use the 'r' and 'b' etc. bits accordingly.
 
Figure 7, is changed to:

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |r|b|        n              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |        id_length 1        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                           |
   :        id_value_1         :
   |                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |        id_length 2        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                           |
   :        id_value_2         :
   |                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
            :         :
            :         :
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |        id_length n        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                           |
   :        id_value_n         :
   |                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                           |
   :    Additional feedback    :
   |                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The Additional feedback is an item of feedback data that has successfully returned from the remote endpoint.

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

BR
/Hans H

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


From rohc-admin@ietf.org  Thu Feb 21 07:23:12 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 HAA14802
	for <rohc-archive@odin.ietf.org>; Thu, 21 Feb 2002 07:23:12 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA16413;
	Thu, 21 Feb 2002 07:20:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA15545
	for <rohc@optimus.ietf.org>; Thu, 21 Feb 2002 07:02:14 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14225;
	Thu, 21 Feb 2002 07:02:11 -0500 (EST)
Message-Id: <200202211202.HAA14225@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: Thu, 21 Feb 2002 07:02:11 -0500
Subject: [rohc] I-D ACTION:draft-ietf-rohc-sctp-requirements-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.
This draft is a work item of the Robust Header Compression Working Group of the IETF.

	Title		: Requirements for RoHC IP/SCTP Robust Header 
                          Compression (01)
	Author(s)	: C. Schmidt, M. Tuexen
	Filename	: draft-ietf-rohc-sctp-requirements-00.txt
	Pages		: 8
	Date		: 20-Feb-02
	
This document contains requirements for the IP/SCTP header compression
scheme (profile) to be developed by the ROHC WG. The structure of this
document is inherited from the document defining IP/TCP requirements for
ROHC.

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

ENCODING mime
FILE /internet-drafts/draft-ietf-rohc-sctp-requirements-00.txt

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

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

--OtherAccess--

--NextPart--




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


From rohc-admin@ietf.org  Thu Feb 21 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 HAA15268
	for <rohc-archive@odin.ietf.org>; Thu, 21 Feb 2002 07:46:20 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA17780;
	Thu, 21 Feb 2002 07:42:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA17753
	for <rohc@optimus.ietf.org>; Thu, 21 Feb 2002 07:42:39 -0500 (EST)
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 HAA15161
	for <rohc@ietf.org>; Thu, 21 Feb 2002 07:42:32 -0500 (EST)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <1S9WNM5J>; Thu, 21 Feb 2002 12:41:16 -0000
Message-ID: <76C92FBBFB58D411AE760090271ED4186F9FCD@rsys002a.roke.co.uk>
From: "Price, Richard" <richard.price@roke.co.uk>
To: "'Hans Hannu (EPL)'" <Hans.Hannu@epl.ericsson.se>,
        "'rohc@ietf.org'"
	 <rohc@ietf.org>
Subject: RE: [rohc] SigComp Message and (extended) Returned feedback.
Date: Thu, 21 Feb 2002 12:41:15 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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-1"

Hi Hans,

I must confess, from an IPR perspective I can't see the difference
between your proposal and the proposal I made in
http://www1.ietf.org/mail-archive/working-groups/rohc/current/msg00020.html.

The 'reserved' bits in your proposed header can be set to indicate
support for certain optional mechanisms, for example the mechanisms
proposed in sigcomp-extended. A separate bit or bit pattern is
reserved for each mechanism (e.g. you propose to reserve bit 2 for
sigcomp-extended).

However, this is precisely the function of the "identifier list" that
I proposed in my previous email. Different identifiers are reserved
for each optional mechanism (one per well-known decompression algorithm,
one for sigcomp-extended and so on). By sending an identifier an endpoint
indicates support for the corresponding mechanism.

The only difference I can see is that the identifier list has support for
variable-length identifiers of up to 16 bytes rather than a fixed 2-bit
identifier as you currently propose. However I can't believe that merely
reducing the size of each identifier removes the IPR concerns.

This situation worries me because we currently don't have any way of
switching on support for sigcomp-extended at all. In your opinion my
proposal for adding support has IPR concerns, and in my opinion your
alternative proposal suffers from these same IPR concerns. If we can't
resolve this issue then we'll be forced to rely on downloading sigcomp-
extended as bytecode.

Regards,

Richard

> -----Original Message-----
> From: Hans Hannu (EPL) [mailto:Hans.Hannu@epl.ericsson.se]
> Sent: Thursday, February 21, 2002 10:29 AM
> To: 'rohc@ietf.org'
> Subject: [rohc] SigComp Message and (extended) Returned feedback.
> 
> 
> Hi,
> 
> As I indicated in a previous mail the two drafts are not 
> fully compliant yet. This is a proposal for solving this.
> 
> In my comments to Miguel I explained why we need to signaling 
> the state identifier length (ID length) in each SigComp 
> message, and how the remaining bits can be used for a new 
> basic SigComp message format. 
> 
> The reasons for having the ID-length in each SigComp message 
> are the following:
> * SigComp do not know the length of the state identifier 
> prior to the capability announcement.
> * As SigComp does not separate flows, SigComp needs to carry 
> the hash length (ID length) for each SigComp message.  
> 
> The remaining 4-bits can be used for something else, and 
> below is a proposal for the new SigComp basic Message format:
> 
>   0   1   2   3   4   5   6   7 
> +---+---+---+---+---+---+---+---+ 
> |  MT   |Reserv.|    ID length  | 
> +---+---+---+---+---+---+---+---+ 
> |                               | 
> :   state_identifier (n-bytes)  :  
> |                               | 
> +---+---+---+---+---+---+---+---+ 
> |                               | 
> :    Remaining UDVM bytecode    : 
> |                               | 
> +---+---+---+---+---+---+---+---+ 
> 
> Instead of reserving a state_identifier for indication of 
> what type of message this is, a Message Type is included. 
> 
> To avoid making changes to the UDVM instructions according to message:
> http://www.cdt.luth.se/rohc/msg03674.html
> and to make use of shared compression it is necessary for an 
> endpoint to know whether its remote endpoint understands the 
> format of the Returned feedback as depicted in Figure 7 of 
> draft-ietf-rohc-sigcomp-extended-01.txt or not. 
> 
> Therefore I propose the following changes to the two sigcomp-drafts.
> 
> ******** changes to draft-ietf-rohc-sigcomp-04.txt *******
> 
> Section 4.2. 
> 
> The basic SigComp message format is changed to the format above.
> 
> * Message Type
> MT = '00' --- "ordinary compressed message"
> MT = '01' --- "SigComp request message"
> MT = '10' --- "SigComp Capability announcement message"
> MT = '11' --- "Reserved"
> 
> * Reserv.
> Bits 2 and 3 is reserved and is set to '00'
> 
> * Id length
> The length of the state_identifier for this SigComp message
> '0000' - 1 byte state_identifier
> '0001' - 2 bytes state_identifier
> ...
> '1111' - 16 bytes state_identifier
> 
> ******** Changes to draft-ietf-rohc-sigcomp-extended-01.txt *******
> 
> Section 6.1.
> 
> The basic SigComp message format is changed to the format above.
> 
> The reserved bit 2, is used to indicate to the remote 
> endpoint the understanding of the Returned feedback format as 
> depicted in Figure 7.  Thus, an endpoint sets bit 2, in every 
> sent SigComp message to indicate the understanding of the 
> Returned feedback format. If two communicating end-points 
> both sets bit 2. They MUST use the Returned feedback format 
> as depicted in Figure 7. In any other case must no assumption 
> be drawn about the format of the Returned feedback format.
> 
> Note: Setting bit 2 does not mandate an endpoint to use 
> SigComp-extended, but only that it understands the Returned 
> feedback format and will use the 'r' and 'b' etc. bits accordingly.
>  
> Figure 7, is changed to:
> 
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |r|b|        n              |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |        id_length 1        |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                           |
>    :        id_value_1         :
>    |                           |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |        id_length 2        |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                           |
>    :        id_value_2         :
>    |                           |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>             :         :
>             :         :
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |        id_length n        |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                           |
>    :        id_value_n         :
>    |                           |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                           |
>    :    Additional feedback    :
>    |                           |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
> The Additional feedback is an item of feedback data that has 
> successfully returned from the remote endpoint.
> 
> ****************
> 
> BR
> /Hans H
> 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
> 

--------------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 Feb 21 07:48: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 HAA15341
	for <rohc-archive@odin.ietf.org>; Thu, 21 Feb 2002 07:48:53 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA17942;
	Thu, 21 Feb 2002 07:46:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA17907
	for <rohc@optimus.ietf.org>; Thu, 21 Feb 2002 07:46:13 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.46])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15265
	for <rohc@ietf.org>; Thu, 21 Feb 2002 07:46:09 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g1LCjeZc006576
	for <rohc@ietf.org>; Thu, 21 Feb 2002 13:45:40 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt461 ; Thu Feb 21 13:44:42 2002 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <Z1HY4P50>; Thu, 21 Feb 2002 13:45:39 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E31E11@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "Rohc (E-mail)" <rohc@ietf.org>
Date: Thu, 21 Feb 2002 13:45:01 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [rohc] TCP requirements ready for freeze?
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,

An updated version of the TCP requirements is now available, 
incorporating comments from the SLC meeting and the list, 
especially comments from Gorry. 

draft-ietf-rohc-tcp-requirements-03.txt

Please take a look at this document and let me know if we need
to make any additional adjustments and resubmit it next week. In
any case, we would like to freeze-call this soon.

Cheers,
/L-E


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


From rohc-admin@ietf.org  Thu Feb 21 09:28: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 JAA18223
	for <rohc-archive@odin.ietf.org>; Thu, 21 Feb 2002 09:28:27 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA24438;
	Thu, 21 Feb 2002 09:23:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA24400
	for <rohc@optimus.ietf.org>; Thu, 21 Feb 2002 09:23:36 -0500 (EST)
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 JAA18109
	for <rohc@ietf.org>; Thu, 21 Feb 2002 09:23:31 -0500 (EST)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <1S9WNNBC>; Thu, 21 Feb 2002 14:21:43 -0000
Message-ID: <76C92FBBFB58D411AE760090271ED4186F9FCE@rsys002a.roke.co.uk>
From: "Price, Richard" <richard.price@roke.co.uk>
To: "'Dr. Carsten Bormann'" <cabo@tzi.org>,
        "'Lars-Erik Jonsson (EPL)'"
	 <Lars-Erik.Jonsson@epl.ericsson.se>,
        "Conroy, Lawrence (SMTP)"
	 <lwc@roke.co.uk>
Cc: rohc@ietf.org
Subject: RE: [rohc] Default decompression algorithms
Date: Thu, 21 Feb 2002 14:21:42 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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-1"

> To me it seems the current draft is about twice as complex as it needs to be.
> We need real time to fix all the small details in that complexity.
> Complexity grows at least with some polynomial of the feature set.

Hi Carsten,

Is the additional complexity that you are worried about mainly due to the
technical mechanisms of the draft, or the informative explanation of how the
mechanisms can be used? There is quite a bit of the latter, and whilst it is
very useful for implementers it is non-normative and could easily be omitted
from the RFC.

Perhaps we could shrink the size of the SigComp RFC by moving some of the text
into a "SigComp implementer's guide" draft? This text could remain at draft
status for now; we could put it into the SigComp RFC at a later stage (perhaps
when we reach Draft Standard).

If you believe that any technical mechanism could be omitted from SigComp
without reducing the performance too badly then please let us know!

> If we want to finish in time, we need to focus on removing, not about
> adding.
> 
> Since anybody can "profile" SigComp to include certain state ab initio, I
> would like to propose that we end this discussion now.

As you mention above, the mechanisms needed to provide algorithm negotiation
are available already as part of the state reference mechanism. However, the
reason that Lawrence began this discussion in the first place is as follows:

[LWC]  We have the facilities within SigComp to minimise or even remove the need
for downloads, so the whacky contrib or three to the CN1 meeting is just a case
of this group and CN1 being slightly out of phase.

The "wacky contributions" were in fact proposals to add a separate algorithm
negotiation mechanism externally to SigComp, despite the fact that one is already
available within SigComp itself. More text is required somewhere to make this
clear, although it is an implementation issue only and so does not need to be
standardised as part of the base RFC for now.

Regards,

Richard

--------------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 Feb 21 10:27: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 KAA20304
	for <rohc-archive@odin.ietf.org>; Thu, 21 Feb 2002 10:27:33 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA28173;
	Thu, 21 Feb 2002 10:23:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA28141
	for <rohc@optimus.ietf.org>; Thu, 21 Feb 2002 10:23:13 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.46])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20155
	for <rohc@ietf.org>; Thu, 21 Feb 2002 10:23:08 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g1LFMdZc020577
	for <rohc@ietf.org>; Thu, 21 Feb 2002 16:22:39 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt461 ; Thu Feb 21 16:22:39 2002 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKDVP4F>; Thu, 21 Feb 2002 16:13:04 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E31E19@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'Price, Richard'" <richard.price@roke.co.uk>, rohc@ietf.org
Date: Thu, 21 Feb 2002 16:21:59 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [rohc] RE: IPR situation
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

Richard,

> RP: Based on previous mailing list discussions, I concluded that 
> the IPR issues on the base SigComp solution were due to the
> informative description of how to implement a feedback mechanism
> rather than the technical content of the solution. 

Was it not rather the described mechanisms for acknowledging
state generated based on received messages that there were IPR
concerns on. I do not believe we have to bother if anyone has
tried to protect the use of a feedback mechanism in general.

> So in release 04 of the SigComp draft I defined the following
> list of identifiers as a well-known area of the UDVM memory:
>
<snip>
> 
> The aim of the above mechanism was not to provide feedback 
> (although it could feasibly be used as such) but rather to
> allow an endpoint to announce support for a selection of
> well-known decompression algorithms. Each algorithm would
> be given its own unique identifier (e.g. 0 for NULL, 1 for 
> DEFLATE etc.).

Was this ever discussed on the mailing list? I may have missed
it, and in that case I apologize. However, we must try to keep
the technical development of new mechanisms, and especially
agree on the need for new things, on the mailing list. Working
group documents should be updated based on what has been 
agreed on the list, not the opposite.

> I also hoped that the mechanism could be used to indicate 
> support for the extended operations themselves, by reserving
> a certain identifier for the sigcomp-extended draft. Without
> this ability the extended operations would have to be
> negotiated externally to SigComp, or else feedback data would
> be sent without knowing whether or not it could be understood 
> by the receiver (potentially very inefficient).

Do you mean that this is the only way to provide a hook for
extended operations without negotiation?


> [LEJ] Note:
>       When someone indicates that they know of potential IPR,
>       it does not necessary mean that it is their own IPR. I
>       hope we are all looking for potential IPR's on the
>       technology we are standardizing, so that we can indicate
>       this, or avoid the technology when that is desirable.
> 
> My understanding of the IETF approach to dealing with IPRs is 
> that an RFC includes an IPR statement only as a pointer to an
> official IPR announcement made at http://www.ietf.org/ipr.html.

RFC2026 says the following about Standards Track documents:

: 10.3.2. Standards Track Documents
:
:   (A)  Where any patents, patent applications, or other proprietary
:      rights are known, or claimed, with respect to any specification on
:      the standards track, and brought to the attention of the IESG, the
:      IESG shall not advance the specification without including in the
:      document a note indicating the existence of such rights, or
:      claimed rights.  

This is therefore not only about official IPR announcements on the web,
but about whether there are known IPR's. Patents are public information,
so one can know about others patents. 

RFC2026 states the following for all contributions, which affects 
all of us who write internet drafts:

: 10.3.1.  All Contributions
:
:   By submission of a contribution, each person actually submitting the
:   contribution is deemed to agree to the following terms and conditions
:   on his own behalf, on behalf of the organization (if any) he
:   represents and on behalf of the owners of any propriety rights in the
:   contribution..  Where a submission identifies contributors in
:   addition to the contributor(s) who provide the actual submission, the
:   actual submitter(s) represent that each other named contributor was
:   made aware of and agreed to accept the same terms and conditions on
:   his own behalf, on behalf of any organization he may represent and
:   any known owner of any proprietary rights in the contribution.
:
:   6. The contributor represents that he has disclosed the existence of
:      any proprietary or intellectual property rights in the
:      contribution that are reasonably and personally known to the
:      contributor.  The contributor does not represent that he
:      personally knows of all potentially pertinent proprietary and
:      intellectual property rights owned or claimed by the organization
:      he represents (if any) or third parties.

As an author of a draft, you therefore MUST tell if YOU know of any
IPR on the technology described.
 

> The advantage of the above approach is that as authors, we 
> don't need to make a decision on whether particular patents are
> applicable to our work or not.

This is wrong. You MUST (as an author) indicate if you are aware of any
patent on the technology.

Rgds,
/L-E

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


From rohc-admin@ietf.org  Thu Feb 21 12:29: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 MAA25542
	for <rohc-archive@odin.ietf.org>; Thu, 21 Feb 2002 12:29:30 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA09892;
	Thu, 21 Feb 2002 12:25:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA09863
	for <rohc@optimus.ietf.org>; Thu, 21 Feb 2002 12:25:24 -0500 (EST)
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 MAA25421
	for <rohc@ietf.org>; Thu, 21 Feb 2002 12:25:19 -0500 (EST)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <1S9WNNP3>; Thu, 21 Feb 2002 17:24:11 -0000
Message-ID: <76C92FBBFB58D411AE760090271ED4186F9FD2@rsys002a.roke.co.uk>
From: "Price, Richard" <richard.price@roke.co.uk>
To: "'Lars-Erik Jonsson (EPL)'" <Lars-Erik.Jonsson@epl.ericsson.se>
Cc: rohc@ietf.org
Date: Thu, 21 Feb 2002 17:24:11 -0000
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: IPR situation
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"

> > RP: Based on previous mailing list discussions, I concluded that 
> > the IPR issues on the base SigComp solution were due to the
> > informative description of how to implement a feedback mechanism
> > rather than the technical content of the solution. 
> 
> Was it not rather the described mechanisms for acknowledging
> state generated based on received messages that there were IPR
> concerns on.

I deleted all of the above mechanisms in an attempt to resolve the
IPR issues on the base SigComp solution. It didn't work!

> I do not believe we have to bother if anyone has
> tried to protect the use of a feedback mechanism in general.

This is what I find so confusing about the current IPR debate. The
mechanism I proposed just sends a list of identifiers from one
endpoint to another - this could be used to implement a feedback
mechanism, but equally it could be used to announce support for a
list of well-known decompression algorithms.

In my opinion, an IPR claim on the above would cover not only the
use of a feedback mechanism in general, but also the use of a
capability announcement mechanism as well.

> > So in release 04 of the SigComp draft I defined the following
> > list of identifiers as a well-known area of the UDVM memory:
> >
> <snip>
> > 
> > The aim of the above mechanism was not to provide feedback 
> > (although it could feasibly be used as such) but rather to
> > allow an endpoint to announce support for a selection of
> > well-known decompression algorithms. Each algorithm would
> > be given its own unique identifier (e.g. 0 for NULL, 1 for 
> > DEFLATE etc.).
> 
> Was this ever discussed on the mailing list? I may have missed
> it, and in that case I apologize. However, we must try to keep
> the technical development of new mechanisms, and especially
> agree on the need for new things, on the mailing list. Working
> group documents should be updated based on what has been 
> agreed on the list, not the opposite.

Yes, this was discussed in some detail on the mailing list (see
http://www.cdt.luth.se/rohc/msg03631.html and related messages).

> > I also hoped that the mechanism could be used to indicate 
> > support for the extended operations themselves, by reserving
> > a certain identifier for the sigcomp-extended draft. Without
> > this ability the extended operations would have to be
> > negotiated externally to SigComp, or else feedback data would
> > be sent without knowing whether or not it could be understood 
> > by the receiver (potentially very inefficient).
> 
> Do you mean that this is the only way to provide a hook for
> extended operations without negotiation?

Unfortunately, if Hans' IPR concerns on my proposed "hook" are valid
then I believe that they cover the concept of capability announcement
itself. The mechanism I wanted to include in the draft simply
transmitted a list of identifiers from Endpoint A to Endpoint B -
specific identifiers could then be reserved to indicate support for
various well-known algorithms, extended operations and so on.

How can a capability announcement mechanism be implemented without
reserving an identifier (any flag or bit pattern) for each optional
mechanism, and then transmitting a list of the supported mechanisms
from one endpoint to another?

> > [LEJ] Note:
> >       When someone indicates that they know of potential IPR,
> >       it does not necessary mean that it is their own IPR. I
> >       hope we are all looking for potential IPR's on the
> >       technology we are standardizing, so that we can indicate
> >       this, or avoid the technology when that is desirable.
> > 
> > My understanding of the IETF approach to dealing with IPRs is 
> > that an RFC includes an IPR statement only as a pointer to an
> > official IPR announcement made at http://www.ietf.org/ipr.html.
> 
> RFC2026 says the following about Standards Track documents:
> 
> : 10.3.2. Standards Track Documents
> :
> :   (A)  Where any patents, patent applications, or other proprietary
> :      rights are known, or claimed, with respect to any specification on
> :      the standards track, and brought to the attention of the IESG, the
> :      IESG shall not advance the specification without including in the
> :      document a note indicating the existence of such rights, or
> :      claimed rights.  
> 
> This is therefore not only about official IPR announcements on the web,
> but about whether there are known IPR's. Patents are public information,
> so one can know about others patents.

I believe that knowledge of 3rd party patents is also placed on the IETF
website; for example http://www.ietf.org/ietf/IPR/CHRISTENSEN-MAGMA-SNOOP.txt.

> RFC2026 states the following for all contributions, which affects 
> all of us who write internet drafts:
> 
> : 10.3.1.  All Contributions
> :
> :   By submission of a contribution, each person actually submitting the
> :   contribution is deemed to agree to the following terms and conditions
> :   on his own behalf, on behalf of the organization (if any) he
> :   represents and on behalf of the owners of any propriety rights in the
> :   contribution..  Where a submission identifies contributors in
> :   addition to the contributor(s) who provide the actual submission, the
> :   actual submitter(s) represent that each other named contributor was
> :   made aware of and agreed to accept the same terms and conditions on
> :   his own behalf, on behalf of any organization he may represent and
> :   any known owner of any proprietary rights in the contribution.
> :
> :   6. The contributor represents that he has disclosed the existence of
> :      any proprietary or intellectual property rights in the
> :      contribution that are reasonably and personally known to the
> :      contributor.  The contributor does not represent that he
> :      personally knows of all potentially pertinent proprietary and
> :      intellectual property rights owned or claimed by the organization
> :      he represents (if any) or third parties.
> 
> As an author of a draft, you therefore MUST tell if YOU know of any
> IPR on the technology described.
>  
> 
> > The advantage of the above approach is that as authors, we 
> > don't need to make a decision on whether particular patents are
> > applicable to our work or not.
> 
> This is wrong. You MUST (as an author) indicate if you are aware of any
> patent on the technology.

The above statement seems to contradict the following, quoted from the
previous discussion on IPRs between Scott Bradner and yourself:

"You have no obligation to send in an IPR notice for other parties IPR's, and
you might also have an NDA that prevents you from doing so. However, since
it is beneficial for the community to know about all potential IPR's, if you
can you should of course share your knowledge with the WG and the community."

Which of the above statements is correct? It's important for us to get this
right, particularly if Hans' IPR concerns stem from a patent similar to the
Motorola patent WO9110289 that tries to cover the general concept of a feedback
mechanism.

(As an aside, I don't believe that even the Motorola patent covers the more
general concept of a capability announcement mechanism, so I'm not worried
about it from the perspective of my proposed text for the SigComp draft).

--------------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 Feb 21 12:47:53 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 MAA26214
	for <rohc-archive@odin.ietf.org>; Thu, 21 Feb 2002 12:47:53 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA14311;
	Thu, 21 Feb 2002 12:44:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA14280
	for <rohc@optimus.ietf.org>; Thu, 21 Feb 2002 12:44:31 -0500 (EST)
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 MAA26104
	for <rohc@ietf.org>; Thu, 21 Feb 2002 12:44:28 -0500 (EST)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <1S9WNNRA>; Thu, 21 Feb 2002 17:43:19 -0000
Message-ID: <76C92FBBFB58D411AE760090271ED4186F9FD3@rsys002a.roke.co.uk>
From: "Price, Richard" <richard.price@roke.co.uk>
To: "'Lars-Erik Jonsson (EPL)'" <Lars-Erik.Jonsson@epl.ericsson.se>
Cc: rohc@ietf.org
Date: Thu, 21 Feb 2002 17:43:18 -0000
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: Default decompression algorithms
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"

> > So for the wireless environment 3GPP will be
> > able to choose their own list of mandatory and optional algorithms.
> 
> Yes, they use to do it that way, but why should WE make any algorithm
> mandatory at the decompressor.

We shouldn't - in my opinion it would be a mistake for the ROHC Working
Group to do more than standardise the algorithms themselves. The final
decision on whether algorithms are mandatory or optional should be made
in the context of a particular application.

The ability to make certain algorithms mandatory is available "for free"
as part of the secure state reference mechanism, so no additional
standardisation is required on our part.

> As you say yourself, the decompressor can announce what resources it has,
> and the compressor decides what to use based on that, but the decompressor
> does not have to announce any available algorithms. If it does not, the
> compressor just do not have any other choice than to download its own
> algorithm.

We should leave the decision as to whether or not mandatory algorithms are
required to particular applications (e.g. 3GPP can decide this for SIP in
the mobile environment).

> > I would be very happy to include both approaches in the SigComp
> > solution and leave the decision on which to use to the compressor.
> 
> Simple and well defined solutions with few options are usually
> preferable when making standards, at least in the IETF. 

With the UDVM approach the SigComp solution can certainly be simple and
well-defined, but few options is one thing that we won't have! A compressor
with the ability to download bytecode already has complete flexibility to
choose any algorithm it likes; in my opinion this is a strength of SigComp
rather than a weakness.

The ability to announce a list of supported algorithms at the decompressor
does not introduce more flexibility but instead just saves downloading the
chosen algorithm when it is already available at the decompressor.

Regards,

Richard

--------------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 Feb 21 13:01: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 NAA26872
	for <rohc-archive@odin.ietf.org>; Thu, 21 Feb 2002 13:01:30 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA15249;
	Thu, 21 Feb 2002 12:58:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA15222
	for <rohc@optimus.ietf.org>; Thu, 21 Feb 2002 12:58:49 -0500 (EST)
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 MAA26704
	for <rohc@ietf.org>; Thu, 21 Feb 2002 12:58:47 -0500 (EST)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <1S9WNNRX>; Thu, 21 Feb 2002 17:56:51 -0000
Message-ID: <76C92FBBFB58D411AE760090271ED4186F9FD4@rsys002a.roke.co.uk>
From: "Price, Richard" <richard.price@roke.co.uk>
To: "'Abbie Barbir'" <abbieb@nortelnetworks.com>,
        "'Lars-Erik Jonsson (EPL)'" <Lars-Erik.Jonsson@epl.ericsson.se>,
        "Conroy, Lawrence (SMTP)" <lwc@roke.co.uk>
Cc: rohc@ietf.org
Subject: RE: [rohc] Default decompression algorithms
Date: Thu, 21 Feb 2002 17:56:50 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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-1"

------------------- SNIP SNIP 
> Making one or more of these well-known algorithms mandatory at the 
> decompressor doesn't contradict the UDVM approach because the decision on 
> which algorithm to use (or whether to download a new one) is still made by 
> the compressor. So we have a "win-win" situation; the compressor downloads 
> a new algorithm to the decompressor when it judges the overall performance 
> to be better than using one of the existing algorithms. 
> 
-------------- 
> Can you suggest how this would be done (implemented) from the compressor end. 
> abbie

Hi,

There are quite a few issues that the compressor will need to consider when
judging overall performance, including some or all of the following metrics:

1   Compression ratio

2   Processing efficiency

3   Memory efficiency

4   Implementation effort

5   IPR considerations

The IPR considerations are particularly important, since encumbered algorithms
tend to substantially outperform unencumbered algorithms in terms of metrics
1, 2, and 3.

So if a compressor has licensed the bytecode for an encumbered algorithm, it
is usually preferable to download this bytecode to a decompressor that does
not support the encumbered algorithm, rather than picking one of the weaker
unencumbered algorithms already available at the decompressor.

Regards,

Richard Price

--------------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 Feb 21 13:31: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 NAA28346
	for <rohc-archive@odin.ietf.org>; Thu, 21 Feb 2002 13:31:44 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA17478;
	Thu, 21 Feb 2002 13:26:48 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA17450
	for <rohc@optimus.ietf.org>; Thu, 21 Feb 2002 13:26:47 -0500 (EST)
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28106
	for <rohc@ietf.org>; Thu, 21 Feb 2002 13:26:44 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.10.2/8.10.2) id g1LIQkG27741
	for rohc@ietf.org; Thu, 21 Feb 2002 13:26:46 -0500 (EST)
Date: Thu, 21 Feb 2002 13:26:46 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200202211826.g1LIQkG27741@newdev.harvard.edu>
To: rohc@ietf.org
Subject: RE: [rohc] Default decompression algorithms
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 IPR considerations are particularly important

note that RFCs do not contain specific IPR information - just a pointer
to the on-line repository

the basic reason is that the RFC is forever but the IPR information 
can (and will) change over time - an IPR snapshot in a RFC could be
quite misleading as to the actual IPR state at the time that someone
was reading the RFC

Scott

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


From rohc-admin@ietf.org  Thu Feb 21 13:35: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 NAA28495
	for <rohc-archive@odin.ietf.org>; Thu, 21 Feb 2002 13:35:15 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA18232;
	Thu, 21 Feb 2002 13:32:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA18193
	for <rohc@optimus.ietf.org>; Thu, 21 Feb 2002 13:31:58 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28366
	for <rohc@ietf.org>; Thu, 21 Feb 2002 13:31:55 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g1LIVOM18975;
	Thu, 21 Feb 2002 13:31:24 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g1LIVM325419;
	Thu, 21 Feb 2002 13:31:23 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <FAMDS23Q>; Thu, 21 Feb 2002 13:31:24 -0500
Message-ID: <87609AFB433BD5118D5E0002A52CD754015D5C0C@zcard0k6.ca.nortel.com>
From: "Abbie Barbir"<abbieb@nortelnetworks.com>
To: "Price, Richard" <richard.price@roke.co.uk>,
        "'Lars-Erik Jonsson (EPL)'" <Lars-Erik.Jonsson@epl.ericsson.se>,
        "Conroy, Lawrence (SMTP)" <lwc@roke.co.uk>
Cc: rohc@ietf.org
Subject: RE: [rohc] Default decompression algorithms
Date: Thu, 21 Feb 2002 13:31:22 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1BB05.F61534A0"
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 message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1BB05.F61534A0
Content-Type: text/plain;
	charset="iso-8859-1"


Richard,

Thanks for the responce.
I am aware of what the compressor need to do. However, your remark states

"the compressor downloads a new algorithm to the decompressor when it 
judges the overall performance to be better than using one of the existing 
algorithms"

>From an implementation point of view, 
1. are you saying that the compressor must/should keep a list that relates
 a device's algorithm with the compression ratio etc that it could achieve?
2. Or the compressor will first attempt to compress using the algorithm that
is avilable at the decompressor and then it realize that i can get better
compression if this xyz algorithm is used, so what will do 
  - try to remember that for the next message
  - decide to go ahead with this message and then download a new algorithm 
    to the UDVM

Definitly other options could be used. The point here, is that the above
statement
can be hard to implement in the field.

abbie


> -----Original Message-----
> From: Price, Richard [mailto:richard.price@roke.co.uk]
> Sent: Thursday, February 21, 2002 12:57 PM
> To: Barbir, Abbie [CAR:1A00:EXCH]; 'Lars-Erik Jonsson (EPL)'; Conroy,
> Lawrence (SMTP)
> Cc: rohc@ietf.org
> Subject: RE: [rohc] Default decompression algorithms
> 
> 
> ------------------- SNIP SNIP 
> > Making one or more of these well-known algorithms mandatory at the 
> > decompressor doesn't contradict the UDVM approach because 
> the decision on 
> > which algorithm to use (or whether to download a new one) 
> is still made by 
> > the compressor. So we have a "win-win" situation; the 
> compressor downloads 
> > a new algorithm to the decompressor when it judges the 
> overall performance 
> > to be better than using one of the existing algorithms. 
> > 
> -------------- 
> > Can you suggest how this would be done (implemented) from 
> the compressor end. 
> > abbie
> 
> Hi,
> 
> There are quite a few issues that the compressor will need to 
> consider when
> judging overall performance, including some or all of the 
> following metrics:
> 
> 1   Compression ratio
> 
> 2   Processing efficiency
> 
> 3   Memory efficiency
> 
> 4   Implementation effort
> 
> 5   IPR considerations
> 
> The IPR considerations are particularly important, since 
> encumbered algorithms
> tend to substantially outperform unencumbered algorithms in 
> terms of metrics
> 1, 2, and 3.
> 
> So if a compressor has licensed the bytecode for an 
> encumbered algorithm, it
> is usually preferable to download this bytecode to a 
> decompressor that does
> not support the encumbered algorithm, rather than picking one 
> of the weaker
> unencumbered algorithms already available at the decompressor.
> 
> Regards,
> 
> Richard Price
> 

------_=_NextPart_001_01C1BB05.F61534A0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [rohc] Default decompression algorithms</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>Richard,</FONT>
</P>

<P><FONT SIZE=3D2>Thanks for the responce.</FONT>
<BR><FONT SIZE=3D2>I am aware of what the compressor need to do. =
However, your remark states</FONT>
</P>

<P><FONT SIZE=3D2>&quot;the compressor downloads a new algorithm to the =
decompressor when it </FONT>
<BR><FONT SIZE=3D2>judges the overall performance to be better than =
using one of the existing </FONT>
<BR><FONT SIZE=3D2>algorithms&quot;</FONT>
</P>

<P><FONT SIZE=3D2>From an implementation point of view, </FONT>
<BR><FONT SIZE=3D2>1. are you saying that the compressor must/should =
keep a list that relates</FONT>
<BR><FONT SIZE=3D2>&nbsp;a device's algorithm with the compression =
ratio etc that it could achieve?</FONT>
<BR><FONT SIZE=3D2>2. Or the compressor will first attempt to compress =
using the algorithm that is avilable at the decompressor and then it =
realize that i can get better compression if this xyz algorithm is =
used, so what will do </FONT></P>

<P><FONT SIZE=3D2>&nbsp; - try to remember that for the next =
message</FONT>
<BR><FONT SIZE=3D2>&nbsp; - decide to go ahead with this message and =
then download a new algorithm </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; to the UDVM</FONT>
</P>

<P><FONT SIZE=3D2>Definitly other options could be used. The point =
here, is that the above statement</FONT>
<BR><FONT SIZE=3D2>can be hard to implement in the field.</FONT>
</P>

<P><FONT SIZE=3D2>abbie</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Price, Richard [<A =
HREF=3D"mailto:richard.price@roke.co.uk">mailto:richard.price@roke.co.uk=
</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Thursday, February 21, 2002 12:57 =
PM</FONT>
<BR><FONT SIZE=3D2>&gt; To: Barbir, Abbie [CAR:1A00:EXCH]; 'Lars-Erik =
Jonsson (EPL)'; Conroy,</FONT>
<BR><FONT SIZE=3D2>&gt; Lawrence (SMTP)</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: rohc@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [rohc] Default decompression =
algorithms</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; ------------------- SNIP SNIP </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Making one or more of these well-known =
algorithms mandatory at the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; decompressor doesn't contradict the UDVM =
approach because </FONT>
<BR><FONT SIZE=3D2>&gt; the decision on </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; which algorithm to use (or whether to =
download a new one) </FONT>
<BR><FONT SIZE=3D2>&gt; is still made by </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the compressor. So we have a =
&quot;win-win&quot; situation; the </FONT>
<BR><FONT SIZE=3D2>&gt; compressor downloads </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; a new algorithm to the decompressor when =
it judges the </FONT>
<BR><FONT SIZE=3D2>&gt; overall performance </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; to be better than using one of the =
existing algorithms. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -------------- </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Can you suggest how this would be done =
(implemented) from </FONT>
<BR><FONT SIZE=3D2>&gt; the compressor end. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; abbie</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Hi,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; There are quite a few issues that the =
compressor will need to </FONT>
<BR><FONT SIZE=3D2>&gt; consider when</FONT>
<BR><FONT SIZE=3D2>&gt; judging overall performance, including some or =
all of the </FONT>
<BR><FONT SIZE=3D2>&gt; following metrics:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 1&nbsp;&nbsp; Compression ratio</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 2&nbsp;&nbsp; Processing efficiency</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 3&nbsp;&nbsp; Memory efficiency</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 4&nbsp;&nbsp; Implementation effort</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 5&nbsp;&nbsp; IPR considerations</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The IPR considerations are particularly =
important, since </FONT>
<BR><FONT SIZE=3D2>&gt; encumbered algorithms</FONT>
<BR><FONT SIZE=3D2>&gt; tend to substantially outperform unencumbered =
algorithms in </FONT>
<BR><FONT SIZE=3D2>&gt; terms of metrics</FONT>
<BR><FONT SIZE=3D2>&gt; 1, 2, and 3.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; So if a compressor has licensed the bytecode =
for an </FONT>
<BR><FONT SIZE=3D2>&gt; encumbered algorithm, it</FONT>
<BR><FONT SIZE=3D2>&gt; is usually preferable to download this bytecode =
to a </FONT>
<BR><FONT SIZE=3D2>&gt; decompressor that does</FONT>
<BR><FONT SIZE=3D2>&gt; not support the encumbered algorithm, rather =
than picking one </FONT>
<BR><FONT SIZE=3D2>&gt; of the weaker</FONT>
<BR><FONT SIZE=3D2>&gt; unencumbered algorithms already available at =
the decompressor.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Regards,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Richard Price</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1BB05.F61534A0--

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


From rohc-admin@ietf.org  Thu Feb 21 16:48: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 QAA05376
	for <rohc-archive@odin.ietf.org>; Thu, 21 Feb 2002 16:48:18 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA28295;
	Thu, 21 Feb 2002 16:45:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA28264
	for <rohc@optimus.ietf.org>; Thu, 21 Feb 2002 16:45:12 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.46])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05273
	for <rohc@ietf.org>; Thu, 21 Feb 2002 16:45:06 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g1LLibZc019655;
	Thu, 21 Feb 2002 22:44:37 +0100 (MET)
Received: from ericsson.com (ppp2.lmf.ericsson.se [131.160.102.2])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g1LLiYr6005338;
	Thu, 21 Feb 2002 23:44:35 +0200 (EET)
Message-ID: <3C756A80.B39A5D57@ericsson.com>
Date: Thu, 21 Feb 2002 23:45:36 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Organization: OY LM Ericsson AB
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: es,en
MIME-Version: 1.0
To: "Hans Hannu (EPL)" <Hans.Hannu@epl.ericsson.se>
CC: rohc@ietf.org
Subject: Re: [rohc] draft-ietf-rohc-sigcomp-04.txt
References: <A943FD84BD9ED41193460008C791805003E9A27E@ESEALNT419.al.sw.ericsson.se>
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

Hi Hans and the rest of the rochers:

I think Hans already agreed on some of the points, so I will comment only
on those that I think we didn't get an agreement yet. 

"Hans Hannu (EPL)" wrote:
> 
> Hi Miguel,
> 
> > 3) Section 3, SigComp architecture, 2nd paragraph:
> >
> >    "SigComp is typically offered to applications as a "shim" layer
> >    between the application and the transport. Note however that for
> >    certain applications the compressed SigComp message may be passed
> >    back to the application itself for additional processing before
> >    transmission. For example, the application may wish to apply
> >    encryption to the compressed message before handing it to the
> >    transport. "
> >
> >    I don't think this scenario is possible. To my understanding,
> >    there are two types of encryption: end-to-end and hop-by-hop.
> 
> This roles back to whether SigComp is applied IP end-to-end (Endpoint - first proxy ), or "SIP end-to-end" (SIP endpoint to SIP endpoint).
> 
> >    I would like to hear comments on the above statements. And
> >    certainly clarify what is the relationship between the application
> >    and SigComp.
> 
> I think this comes back to which scenario we want to solve. If it is the SIP end-to-end scenario with encryption, this may probably make SIP/SigComp require an assigned port number and SigComp would not be regarded as a shim layer to SIP, but the implementation would have to be totally integrated.

<Miguel> I think that still is not clear to me the relation or problems with
the encryption. Let's imagine the typical SIP trapezoid, that is, two endpoints
A and B communicating with two other proxies (P1, P2) in the middle. So the
chain is A - P1 - P2 - B

Lets assume that SigComp is running between A and P1.

The SIP layer in A builds a SIP message. As the end receiver is B, and A wants to send
some very secret information that only B is able to read, A decides to encrypt that 
information with some secret key so that the information is only decoded by B. Note 
that those SIP header field values that are sensitive to be used by proxies during
routing MUST not be encrypted, otherwise, P1 and P2 can't route the message. 

So A has a SIP message destined to B (through P1 and P2) where certain header field
values are encrypted. This message is passed to the local SigComp shim layer. Sigcomp
compresses the message. After that, there may be other encryption mechanism that run
between A and P1, such as TLS or some other encryption layer. SigComp passes the 
message to the "hop-by-hop encryption layer", whatever that is.

This what I was thinking all about. This mechanism allows end-to-end encryption of
certain values, and hop-by-hop encryption of the whole message. And it does not
require to return a compressed message back to the application (as I understood in
the original text).

I believe this covers all the requirements for encryption.

</Miguel>

> 
> >    Particularly it needs to be clarified which layer
> >    is responsible to forward the message: the SigComp layer or the
> >    application layer.
> 
> With my current understanding of our work and if it is as you say then I think it does not make sense to pass up a compressed message to the application to forward the SigComp message.

<Miguel> I agree. Imagine that the SIP layer receives a SIP compressed message. It will fail to
parse the message. That is for sure. There is nothing SIP can do with a compressed message.

</Miguel>

> 
> > 8) Section 4.2, first paragraph:
> >
> >    "The basic SigComp message consists of a block of UDVM
> > bytecode, the
> >    first n bytes of which are interpreted as a state identifier that
> >    accesses some previously stored state information. "
> >
> >    I think this is inherited from the UDVM draft and it is not valid
> >    anymore. The basic SigComp message will NOT consist only of UDVM
> >    bytecode. Whatever the basic SigComp message is made of, should be
> >    reflected in the paragraph.
> 
> There is a note in the draft about solving the identification of different types of messages by reserving state identifiers. However, I now think that this is not possible for the following reason:
> 
> * SigComp do not know the length of the state identifier prior to the capability announcement.
> - As SigComp does separate flows, SigComp needs to carry the hash length for each message.
> 
> I think this make it valid to introduce some bits to identify the particular message type. Thus, the basic SigComp message format would change to something like this:
> 
>      0   1   2   3   4   5   6   7
>    +---+---+---+---+---+---+---+---+
>    |  MT   |Reserv.|  hash length  |
>    +---+---+---+---+---+---+---+---+
>    |                               |
>    :   state_identifier (n-bytes)  :
>    |                               |
>    +---+---+---+---+---+---+---+---+
>    |                               |
>    :    Remaining UDVM bytecode    :
>    |                               |
>    +---+---+---+---+---+---+---+---+
> 
> The MT, Message Type, would indicate what type of message it is, e.g. SigComp request/announcement, "ordinary" SigComp compressed message.

<Miguel> I was thinking that you would need a Message Type as you were pointing
out. If we would agree on this, I would say that 2 bits seems to be a little
bit constraining... It allows for a maximum of 4 message types. That seems to 
be very limiting. Perhaps you need 3 bits as a minimum.
</Miguel>


> 
> > 12) Section 6.3., figure 5.
> >
> >     The figure refers to a Capability announcement "block".
> 
> Yes, we need to define the term "block". What do you think about the following:
> 
> "Capability announcement block"
> formatted capability announcement information
> 

<Miguel> My question is: do we need to introduce a new concept "block" in the
draft? If there is a need or it clarifies something to the reader, it is fine.
But it seems difficult to justify that you don't need the "block" concept until
section 6.3, but you needed afterwards.
</Miguel>

Regards,

    Miguel

-- 
Miguel-Angel Garcia                     Oy LM Ericsson AB
                                        Jorvas, Finland
mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 5140002

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


From rohc-admin@ietf.org  Fri Feb 22 03:01:43 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 DAA24001
	for <rohc-archive@odin.ietf.org>; Fri, 22 Feb 2002 03:01:43 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA02804;
	Fri, 22 Feb 2002 02:56:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA02773
	for <rohc@ns.ietf.org>; Fri, 22 Feb 2002 02:56:06 -0500 (EST)
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 CAA23929
	for <rohc@ietf.org>; Fri, 22 Feb 2002 02:56:03 -0500 (EST)
Received: from cabo3 (nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with SMTP id g1M7tvC06819;
	Fri, 22 Feb 2002 08:55:57 +0100 (MET)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: "Price, Richard" <richard.price@roke.co.uk>,
        "'Lars-Erik Jonsson \(EPL\)'" <Lars-Erik.Jonsson@epl.ericsson.se>
Cc: <rohc@ietf.org>
Subject: Options   (was: RE: [rohc] RE: Default decompression algorithms)
Date: Fri, 22 Feb 2002 08:55:56 +0100
Message-ID: <NFBBJFHGMCFINEMHAMBGGEHFHHAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <76C92FBBFB58D411AE760090271ED4186F9FD3@rsys002a.roke.co.uk>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
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

> > Simple and well defined solutions with few options are usually
> > preferable when making standards, at least in the IETF.
>
> With the UDVM approach the SigComp solution can certainly be simple and
> well-defined, but few options is one thing that we won't have! A
> compressor
> with the ability to download bytecode already has complete flexibility to
> choose any algorithm it likes; in my opinion this is a strength of SigComp
> rather than a weakness.

Richard,

when we talk about "options" at the IETF we talk about additional code
that configures in or configures out particular logic based on some
negotiation or other agreement.
The general observation after decades of protocol design is that options
often cost more than just making logic mandatory in the first place.
Even if they don't just from an implementation point of view, they reduce
the usefulness of the protocol:
If it is likely that different implementations implement different sets of
options, interoperability becomes unlikely (unless there is a base
configuration as in PPP).
Finally, interoperability testing an implementation with lots of options is
nearly impossible.

So what we need to avoid is negotiation that causes implementations to
behave
different.

Let me give you an example:
The X11 protocol allows to choose whether fields are sent MSB first or LSB
first, ostensibly because it is more efficient to send them LSB first if
both sides use LSB first natively.
This is not the Internet way, we always use MSB first, removing one
potential
"option".

Options != flexibility.
I believe the UDVM concept removes a lot of potential options and gives
implementors lots of flexibility, which is good.
Let's stick with that path.

Now on to the subject of avoiding options in Sigcomp:
I'm not sure that the current set of implementation parameters is a good
idea.
I'd rather freeze most of these at a single value.
This does remove flexibility, but I think in most cases this is unwanted
flexibility (= "options").

We just need to be decisive enough to leave out things.
One of the more serious OSI diseases was to standardize lots of options,
and then later generate "profiles" that would reduce these options to
(more or less) manageable proportions.  Of course, then there are "PICS"
(profile implementation conformance statements), so you find out which of
the options someone has done from a nice little tome of paper.

Why standardize stuff that is never going to be used anyway?
In many cases, this is just an expression of lack of technical direction
in a standardization body.

> The ability to announce a list of supported algorithms at the decompressor
> does not introduce more flexibility but instead just saves downloading the
> chosen algorithm when it is already available at the decompressor.

Right.  I still don't know why this cannot be done using state claims
(please explain).
And I haven't caught what this business about "standardizing compression
algorithms" is about.
We don't.

One final observation: Negotiation takes time.
It is the objective of Sigcomp to save time.
Can we define Sigcomp in such a way that we don't need to expend that time?
(I know, it might be mitigated by moving it to the registration phase, but
it's still latency that will be perceived by the user.)

Gruesse, Carsten


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


From rohc-admin@ietf.org  Fri Feb 22 03:19: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 DAA24177
	for <rohc-archive@odin.ietf.org>; Fri, 22 Feb 2002 03:19:41 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA03784;
	Fri, 22 Feb 2002 03:14: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 DAA03753
	for <rohc@ns.ietf.org>; Fri, 22 Feb 2002 03:14:02 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.46])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24133
	for <rohc@ietf.org>; Fri, 22 Feb 2002 03:13:59 -0500 (EST)
Received: from esealnt409.al.sw.ericsson.se (ESEALNT409.al.sw.ericsson.se [153.88.251.32])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g1M8DUZc019685
	for <rohc@ietf.org>; Fri, 22 Feb 2002 09:13:30 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt409.al.sw.ericsson.se ; Fri Feb 22 09:13:30 2002 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <YHKDWARS>; Fri, 22 Feb 2002 09:03:54 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E31E1A@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'Price, Richard'" <richard.price@roke.co.uk>
Cc: rohc@ietf.org
Date: Fri, 22 Feb 2002 08:55:03 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [rohc] RE: Default decompression algorithms
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

Richard,

> > LEJ: why should WE make any algorithm
> >      mandatory at the decompressor.
> 
> RP: We shouldn't - in my opinion it would be a mistake for the 
>     ROHC Working Group to do more than standardise the algorithms
>     themselves. The final decision on whether algorithms are
>     mandatory or optional should be made in the context of a
>     particular application.

OK, then we do not have a disagreement. This was not clear from
your previous posting:

> > > RP: Clearly a mandatory default algorithm must be supported
> > >     at both ends, so that at least one algorithm is always
> > >     available for the compressor to use.
> > >
> > > RP: Making one or more of these well-known algorithms
> > >     mandatory at the decompressor doesn't contradict the
> > >     UDVM approach because the decision on which algorithm
> > >     to use (or whether to download a new one) is still made
> > >     by the compressor. 

I guess you meant that for specific applications of SigComp, e.g.
a 3GPPP SIP proxy decompressor, one or several algorithms could
be made mandatory, and that is true. However, that is irrelevant
for our work here and therefore the above statements confused me
since I assumed you talked about what WE are defining. It is not
necessary to ever have any mandatory algorithms, but external
users may of course decide to require that.
 
Cheers,
/L-E

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


From rohc-admin@ietf.org  Fri Feb 22 03:31: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 DAA24414
	for <rohc-archive@odin.ietf.org>; Fri, 22 Feb 2002 03:31:48 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA04192;
	Fri, 22 Feb 2002 03:24:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA04160
	for <rohc@ns.ietf.org>; Fri, 22 Feb 2002 03:24:20 -0500 (EST)
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 DAA24265
	for <rohc@ietf.org>; Fri, 22 Feb 2002 03:24:17 -0500 (EST)
Received: from cabo3 (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with SMTP id g1M8O4C10925;
	Fri, 22 Feb 2002 09:24:05 +0100 (MET)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: "Lars-Erik Jonsson \(EPL\)" <Lars-Erik.Jonsson@epl.ericsson.se>,
        "'Price, Richard'" <richard.price@roke.co.uk>
Cc: <rohc@ietf.org>
Subject: RE: [rohc] RE: Default decompression algorithms
Date: Fri, 22 Feb 2002 09:24:04 +0100
Message-ID: <NFBBJFHGMCFINEMHAMBGOEHFHHAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <A943FD84BD9ED41193460008C791805003E31E1A@ESEALNT419.al.sw.ericsson.se>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
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

One question about the compression algorithm negotiation:
Given that there are algorithms that take on the order of 50 bytes to send
over, why is it a win to spend maybe 100 bytes of overhead and a round trip
to negotiate that away?

Gruesse, Carsten


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


From rohc-admin@ietf.org  Fri Feb 22 07:33: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 HAA29617
	for <rohc-archive@odin.ietf.org>; Fri, 22 Feb 2002 07:33:41 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18394;
	Fri, 22 Feb 2002 07:27:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18363
	for <rohc@optimus.ietf.org>; Fri, 22 Feb 2002 07:27:24 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29368
	for <rohc@ietf.org>; Fri, 22 Feb 2002 07:27:21 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g1MCQoh05147;
	Fri, 22 Feb 2002 07:26:50 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g1MCQmK18621;
	Fri, 22 Feb 2002 07:26:48 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <FAMDST0K>; Fri, 22 Feb 2002 07:26:50 -0500
Message-ID: <87609AFB433BD5118D5E0002A52CD754015D60EE@zcard0k6.ca.nortel.com>
From: "Abbie Barbir"<abbieb@nortelnetworks.com>
To: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>,
        "'Price, Richard'" <richard.price@roke.co.uk>
Cc: rohc@ietf.org
Subject: RE: [rohc] RE: Default decompression algorithms
Date: Fri, 22 Feb 2002 07:26:54 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1BB9C.367F4FD0"
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 message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1BB9C.367F4FD0
Content-Type: text/plain;
	charset="iso-8859-1"



> -----Original Message-----
> From: Lars-Erik Jonsson (EPL) 
> [mailto:Lars-Erik.Jonsson@epl.ericsson.se]
> Sent: Friday, February 22, 2002 2:55 AM
> To: 'Price, Richard'
> Cc: rohc@ietf.org
> Subject: [rohc] RE: Default decompression algorithms
> 
> 
> Richard,
> 
> > > LEJ: why should WE make any algorithm
> > >      mandatory at the decompressor.
> > 
> > RP: We shouldn't - in my opinion it would be a mistake for the 
> >     ROHC Working Group to do more than standardise the algorithms
> >     themselves. The final decision on whether algorithms are
> >     mandatory or optional should be made in the context of a
> >     particular application.
> 
> OK, then we do not have a disagreement. This was not clear from
> your previous posting:
> 
sounds good, standadise the algorithm themselevs and let the application
specify the default one.

ps: what would this imply in terms of interoperability testing and
compliance from this WG. This include:
1. UDVM compliance
2. Actual algorithm compliance

abbie

------_=_NextPart_001_01C1BB9C.367F4FD0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.89">
<TITLE>RE: [rohc] RE: Default decompression algorithms</TITLE>
</HEAD>
<BODY>
<BR>
<BR>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: Lars-Erik Jonsson (EPL) </FONT>
<BR><FONT SIZE=2>&gt; [<A HREF="mailto:Lars-Erik.Jonsson@epl.ericsson.se">mailto:Lars-Erik.Jonsson@epl.ericsson.se</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: Friday, February 22, 2002 2:55 AM</FONT>
<BR><FONT SIZE=2>&gt; To: 'Price, Richard'</FONT>
<BR><FONT SIZE=2>&gt; Cc: rohc@ietf.org</FONT>
<BR><FONT SIZE=2>&gt; Subject: [rohc] RE: Default decompression algorithms</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Richard,</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; LEJ: why should WE make any algorithm</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mandatory at the decompressor.</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; RP: We shouldn't - in my opinion it would be a mistake for the </FONT>
<BR><FONT SIZE=2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; ROHC Working Group to do more than standardise the algorithms</FONT>
<BR><FONT SIZE=2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; themselves. The final decision on whether algorithms are</FONT>
<BR><FONT SIZE=2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; mandatory or optional should be made in the context of a</FONT>
<BR><FONT SIZE=2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; particular application.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; OK, then we do not have a disagreement. This was not clear from</FONT>
<BR><FONT SIZE=2>&gt; your previous posting:</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>sounds good, standadise the algorithm themselevs and let the application specify the default one.</FONT>
</P>

<P><FONT SIZE=2>ps: what would this imply in terms of interoperability testing and compliance from this WG. This include:</FONT>
<BR><FONT SIZE=2>1. UDVM compliance</FONT>
<BR><FONT SIZE=2>2. Actual algorithm compliance</FONT>
</P>

<P><FONT SIZE=2>abbie</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1BB9C.367F4FD0--

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


From rohc-admin@ietf.org  Fri Feb 22 10:16:58 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 KAA05289
	for <rohc-archive@odin.ietf.org>; Fri, 22 Feb 2002 10:16:58 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA28339;
	Fri, 22 Feb 2002 10:10:30 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA28303
	for <rohc@optimus.ietf.org>; Fri, 22 Feb 2002 10:10:26 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.46])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05082
	for <rohc@ietf.org>; Fri, 22 Feb 2002 10:10:21 -0500 (EST)
Received: from esealnt406.al.sw.ericsson.se (ESEALNT406.al.sw.ericsson.se [153.88.251.29])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g1MFALZc025315
	for <rohc@ietf.org>; Fri, 22 Feb 2002 16:10:21 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt406.al.sw.ericsson.se ; Fri Feb 22 16:10:21 2002 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <Z1HYWC5S>; Fri, 22 Feb 2002 16:10:20 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E9A292@ESEALNT419.al.sw.ericsson.se>
From: "Hans Hannu (EPL)" <Hans.Hannu@epl.ericsson.se>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Subject:  RE: [rohc] SigComp Message and (extended) Returned feedback.
Date: Fri, 22 Feb 2002 16:09:22 +0100
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 Richard and others,

To support shared compression I agree with you that we need to announce its support at some time instance. For explicit acknowledgements on the other hand we could add the State Create instruction as I explained in http://www.cdt.luth.se/rohc/msg03674.html . 
However, it may be simpler to allow for this to be announced in a capability announcement message, as we need to do that for shared compression anyhow.

So, the issue relates to announcement of supported features, e.g. a SigComp endpoint may announce that it supports a decompression algorithm without that the compression needs to upload the corresponding UDVM bytecode.
Depending on how we write the text, this might raise some IPR considerations. If we can make it absolutely clear that this capability announcement mechanisms with identifiers is only used to advertise the support of well known features, e.g. a well-known UDVM decompression algorithm. Thus, what may be in this capability announcement block is pre-defined identifiers and not any identifiers for state(s) that are created during the SigComp "session". Then I think this solves at least my IPR concerns. 

I therefore suggest the following changes to the drafts to make the sigcomp drafts synchronized. I think also this would make  shared compression and explicit acknowledgements possible even if the announcement is not done before the compression actually starts.

********** SigComp-04 *****
Section 6.3, Figure 5.

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+  
      |         Length            |  
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+  
      |       UDVM_version        |  
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+  
      |    overall_memory_size    |  
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+  
      |      cycles_per_bit       |  
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+  
      |    cycles_per_message     |  
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+  
      |            n              |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |        id_length 1        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                           |
      :        id_value_1         :
      |                           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
            :         :
            :         :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |        id_length n        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                           |
      :        id_value_n         :
      |                           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   Figure 5: Capability announcement block

"The 'Length' field specifies the length of the entire capability announcement block. The 'n' field indicates how many identifiers that are present in the block. The 'id_length x' field specifies the length of the 'id_value_x' field. The identifiers, which are reserved numbers for well-known features, may be used to announce support for the well-known features, e.g. UDVM decompression algorithms that are supported by the SigComp endpoint which this capability announcement block originates from. Thus, a compressor may choose to use one of the already supported UDVM decompression algorithms to avoid a UDVM decompressor algorithm upload."

- The text in section 6.3 regarding Requested and Returned feedback are removed.

********** SigComp-extended *****

- Figure 5 in Sigcomp extended is also changed accordingly to the figure above. 
- Figure 6 in SigComp extended is removed.
- Figure 7 in SigComp extended is changed to the figure below.
  
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+  
      |         Length            |  
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+  
      |       UDVM_version        |  
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+  
      |    overall_memory_size    |  
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+  
      |      cycles_per_bit       |  
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+  
      |    cycles_per_message     |  
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+  
      |            n              |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |        id_length 1        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                           |
      :        id_value_1         :
      |                           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
            :         :
            :         :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |        id_length n        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                           |
      :        id_value_n         :
      |                           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+     
      |r|b|       Reserved        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 

  Figure 7. Extended operations feedback format.  

"When a SigComp message is not regarded as a capability announcement message, the END-MESSAGE instruction does not actually point to the capability announcement location but rather to a feedback location with the feedback format block as depicted in Figure 7. The id_length(s) and id_value(s) corresponds to the hash_length and hash_value for state(s) that have been established at the remote end-point due to received SigComp messages and may be used for compression, i.e. these are acknowledgements for established state. "

- The 'r' and 'b' are to be interpreted as in sigcomp-extended-01.txt
- An identifier value for explicit acknowledgements/shared compression should also be reserved.
*********************

I hope this will solve our major issues so that we can update the draft once more before the IETF-meeting.

BR
/Hans H



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


From rohc-admin@ietf.org  Mon Feb 25 02:52:05 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 CAA01760
	for <rohc-archive@odin.ietf.org>; Mon, 25 Feb 2002 02:52:05 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA02089;
	Mon, 25 Feb 2002 02:48:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA02060
	for <rohc@optimus.ietf.org>; Mon, 25 Feb 2002 02:48:25 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01733
	for <rohc@ietf.org>; Mon, 25 Feb 2002 02:48:21 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g1P7mMB24713
	for <rohc@ietf.org>; Mon, 25 Feb 2002 08:48:22 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt461 ; Mon Feb 25 08:48:15 2002 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <Z1HYXD06>; Mon, 25 Feb 2002 08:48:15 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E31E1D@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'Abbie Barbir'" <abbieb@nortelnetworks.com>
Cc: rohc@ietf.org
Subject: RE: [rohc] RE: Default decompression algorithms
Date: Mon, 25 Feb 2002 08:47:31 +0100
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

> > > > LEJ: why should WE make any algorithm 
> > > >      mandatory at the decompressor. 
> > > 
> > > RP: We shouldn't - in my opinion it would be a mistake for the 
> > >     ROHC Working Group to do more than standardize the algorithms 
> > >     themselves. The final decision on whether algorithms are 
> > >     mandatory or optional should be made in the context of a 
> > >     particular application. 
> > 
> > OK, then we do not have a disagreement. This was not clear from 
> > your previous posting: 
> >
> AB: sounds good, standardize the algorithm themselves and let the
> application specify the default one. 

[LEJ: ] By defining the UDVM-solution, we do not have to standardize any algorithms. We may describe example UDVM algorithms, but from our point of
view the algorithms themselves do not have to be standardized.

/L-E

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


From rohc-admin@ietf.org  Mon Feb 25 04:02:13 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 EAA02936
	for <rohc-archive@odin.ietf.org>; Mon, 25 Feb 2002 04:02:13 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA04905;
	Mon, 25 Feb 2002 03:59:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA04399
	for <rohc@ns.ietf.org>; Fri, 22 Feb 2002 11:34:48 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09226;
	Fri, 22 Feb 2002 11:34:45 -0500 (EST)
Message-Id: <200202221634.LAA09226@ietf.org>
To: IETF-Announce: ;
Cc: rohc@ietf.org
From: The IESG <iesg-secretary@ietf.org>
Reply-to: iesg@ietf.org
Date: Fri, 22 Feb 2002 11:34:44 -0500
Subject: [rohc] Last Call: 0-byte Support for R-mode in Link-Layer Assisted ROHC
 Profile 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 received a request Robust Header Compression to consider
0-byte Support for R-mode in Link-Layer Assisted ROHC Profile
<draft-ietf-rohc-rtp-lla-r-mode-02.txt> as a Proposed Standard.

The IESG will also consider publication of Lower Layer Guidelines for
Robust RTP/UDP/IP Header Compression
<draft-ietf-rohc-rtp-lower-layer-guidelines-03.txt> as an Informational
RFC.

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

Files can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-rohc-rtp-lla-r-mode-02.txt
http://www.ietf.org/internet-drafts/draft-ietf-rohc-rtp-lower-layer-guidelines-03.txt


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


From rohc-admin@ietf.org  Mon Feb 25 05:17: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 FAA03845
	for <rohc-archive@odin.ietf.org>; Mon, 25 Feb 2002 05:17:54 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA08927;
	Mon, 25 Feb 2002 05:13:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA08551
	for <rohc@optimus.ietf.org>; Mon, 25 Feb 2002 05:04:13 -0500 (EST)
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 FAA03743
	for <rohc@ietf.org>; Mon, 25 Feb 2002 05:04:06 -0500 (EST)
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <1XV804P0>; Mon, 25 Feb 2002 10:03:31 -0000
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 1S9WNQHQ; Mon, 25 Feb 2002 10:03:29 -0000
From: "West, Mark (ITN)" <mark.a.west@roke.co.uk>
To: rohc@ietf.org
Cc: Juergen Quittek <quittek@ccrle.nec.de>
Message-ID: <3C7A0BF1.2030805@roke.co.uk>
Date: Mon, 25 Feb 2002 10:03:29 +0000
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="------------InterScan_NT_MIME_Boundary"
Subject: [rohc] Questions about the MIB!
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 ROHC-ers,

If you haven't been put off by my use of 'MIB' in the subject line, then 
read on!

Having just read through the draft MIB, a couple of questions have 
arisen which I think may benefit from a wider audience...

Firstly, I'm curious to know how many fellow implementors have done 
anything with the packet-size / payload-size restrictions?  (I know we 
haven't ;-)

Secondly, the more general issue is this: there is a quantity of 
information about contexts which is based on the profiles defined in 
RFC-3095.  (For example, referring to the modes as U, O and R and states 
as IR/FO/SO).  This makes absolute sense with regard to RFC 3095.  I am 
interested to know what anyone thinks about the impact of splitting 
3095, however!  How much of the MIB can/should be based on specific 
profile details, rather than 'generic' framework?  (Clearly in the cases 
mentioned above, opaque numeric identifiers could be used)
Anyway, it's a general issue that it would be nice to have some input on...

On a related note, there are a number of configuration parameters which 
only really have 'per profile' significance (for example 'k_1' and 
'n_1').  These parameters are specific to certain profiles .  'k and n' 
also make a useful example, in that k_1 and n_1 are likely to be chosen 
based on the link characteristics.  So, we have values that are 
per-profile and should be configurable (at least) per-interface.  (I 
suppose it makes sense, anyway, to know which profiles are supported on 
any given interface...)

Where a context is using a particular profile, it is not clear to me 
whether or not it is desirable to be able to 'tweak' these values on a 
per-context basis.  Again, 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 Feb 25 05:36:53 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 FAA04036
	for <rohc-archive@odin.ietf.org>; Mon, 25 Feb 2002 05:36:53 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA09978;
	Mon, 25 Feb 2002 05:34:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA09396
	for <rohc@optimus.ietf.org>; Mon, 25 Feb 2002 05:29:27 -0500 (EST)
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 FAA03967
	for <rohc@ietf.org>; Mon, 25 Feb 2002 05:29:22 -0500 (EST)
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <1XV8044B>; Mon, 25 Feb 2002 10:28:07 -0000
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 1S9WNQKA; Mon, 25 Feb 2002 10:28:00 -0000
From: "West, Mark (ITN)" <mark.a.west@roke.co.uk>
To: "Peter Kremer (ETH)" <Peter.Kremer@eth.ericsson.se>
Cc: rohc <rohc@ietf.org>
Message-ID: <3C7A11B0.7030303@roke.co.uk>
Date: Mon, 25 Feb 2002 10:28:00 +0000
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
Subject: Re: [rohc] Invitation to the 3rd ROHC interop test
References: <F005CD411D18D3119C8F00508B08748008543564@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=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 7bit


Hi Peter,

(Having now hopefully re-arranged my subscription to ROHC so that 
e-mails don't have to get filtered by the moderator...)

We're interested!  (I'm sure that there will be questions, but for now 
let us express our interest)

In response to a query on the list, we'll also bring our EPIC-lite 
implementation along, if anyone else wants to play (sorry -- 
interoperate) with that...

Cheers,

Mark.



Peter Kremer (ETH) wrote:

> Hi,
> 
> This is an invitation to the 3rd ROHC interop test, called Arctic ROHC. The event will take place in Lulea, Sweden from 17 to 23 of April, 2002.
> 
> Regarding the technical details we propose to test:
>  * robustness (packet losses, bit errors),
>  * primarily profile 1,
>  * ROHC over PPP.
> 
> Please note that basic features will also be tested besides these challenging ones. If you have an implementation and have never gone to an interop test event, then take this opportunity. We encourage everyone who has a ROHC implementation to participate and make it a successful event.
> 
> Here are some interesting links about Lulea:
> This is a webcamera: http://www.lulea.se/lulea/Web-camera/webbkamera.asp
> 
> Weather forecast - think twice before you check it!!! (in german only): http://www.wetteronline.de/Schweden/Lulea.htm
> 
> If you don't know where Lulea is, check this out: http://plasma.nationalgeographic.com/mapmachine/index.html?id=362&size=medium&left=22.07&bottom=65.51&right=22.22&top=65.66&point=22.15,65.5833&text=Lule%e5
> 
> Please contact me (Peter.Kremer@ericsson.com) if you plan to participate on this event or if you have any questions.
> 
> 


-- 
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 Feb 25 06:27:04 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 GAA05402
	for <rohc-archive@odin.ietf.org>; Mon, 25 Feb 2002 06:27:04 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA12022;
	Mon, 25 Feb 2002 06:23:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA11986
	for <rohc@optimus.ietf.org>; Mon, 25 Feb 2002 06:23:52 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05091;
	Mon, 25 Feb 2002 06:23:49 -0500 (EST)
Message-Id: <200202251123.GAA05091@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: sip@ietf.org, rohc@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Mon, 25 Feb 2002 06:23:48 -0500
Subject: [rohc] I-D ACTION:draft-camarillo-sip-sigcomp-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 discovery for SIP
	Author(s)	: G. Camarillo, M. Garcia
	Filename	: draft-camarillo-sip-sigcomp-00.txt
	Pages		: 6
	Date		: 22-Feb-02
	
This document defines a mechanism for SIP clients to discover SIP
servers that support signalling compression. DNS NAPTR records are
used for this purpose.

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

ENCODING mime
FILE /internet-drafts/draft-camarillo-sip-sigcomp-00.txt

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

Content-Type: text/plain
Content-ID:	<20020222110759.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 Feb 25 07:58:04 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 HAA07992
	for <rohc-archive@odin.ietf.org>; Mon, 25 Feb 2002 07:58:04 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA17226;
	Mon, 25 Feb 2002 07:55:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA17194
	for <rohc@optimus.ietf.org>; Mon, 25 Feb 2002 07:55:22 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07873
	for <rohc@ietf.org>; Mon, 25 Feb 2002 07:55:17 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g1PCtJB27247
	for <rohc@ietf.org>; Mon, 25 Feb 2002 13:55:19 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt461 ; Mon Feb 25 13:51:35 2002 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <F4G2D0ZR>; Mon, 25 Feb 2002 13:41:57 +0100
Message-ID: <F005CD411D18D3119C8F00508B08748008543576@ehubunt100.eth.ericsson.se>
From: "Peter Kremer (ETH)" <Peter.Kremer@eth.ericsson.se>
To: "'tijana@fesb.hr'" <tijana@fesb.hr>
Cc: "Rohc (E-mail)" <rohc@ietf.org>
Subject: RE: [rohc] Invitation to the 3rd ROHC interop test
Date: Mon, 25 Feb 2002 13:50:32 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-2"
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,

> is there a possibility of initial TCP header compression 
> interoperability being tested during the next interop event?
Well, TCP header compression is not the purpose of the next interoperability test. Moreover, there's no standard to test, yet. So, I suggest to save TCP comp. for the next time and focus on IP/UDP/RTP only.

/Peter

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


From rohc-admin@ietf.org  Mon Feb 25 11:50: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 LAA18020
	for <rohc-archive@odin.ietf.org>; Mon, 25 Feb 2002 11:50:14 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA01590;
	Mon, 25 Feb 2002 11:46:48 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA01561
	for <rohc@optimus.ietf.org>; Mon, 25 Feb 2002 11:46:46 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17725
	for <rohc@ietf.org>; Mon, 25 Feb 2002 11:46:41 -0500 (EST)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g1PGkiB04551
	for <rohc@ietf.org>; Mon, 25 Feb 2002 17:46:44 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Mon Feb 25 17:46:43 2002 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <F4G21NQV>; Mon, 25 Feb 2002 17:37:04 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E31E32@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'Price, Richard'" <richard.price@roke.co.uk>
Cc: rohc@ietf.org
Date: Mon, 25 Feb 2002 17:46:09 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [rohc] RE: IPR situation
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

Richard,

> > > So in release 04 of the SigComp draft I defined the following
> > > list of identifiers as a well-known area of the UDVM memory:
> > >
> > <snip>
> > > 
> > > The aim of the above mechanism was not to provide feedback 
> > > (although it could feasibly be used as such) but rather to
> > > allow an endpoint to announce support for a selection of
> > > well-known decompression algorithms. Each algorithm would
> > > be given its own unique identifier (e.g. 0 for NULL, 1 for 
> > > DEFLATE etc.).
> > 
> > Was this ever discussed on the mailing list? I may have missed
> > it, and in that case I apologize. However, we must try to keep
> > the technical development of new mechanisms, and especially
> > agree on the need for new things, on the mailing list. Working
> > group documents should be updated based on what has been 
> > agreed on the list, not the opposite.
> 
> Yes, this was discussed in some detail on the mailing list (see
> http://www.cdt.luth.se/rohc/msg03631.html and related messages).

Well, in that message you describe the mechanism, but the purpose
you later described (see above) was not at all mentioned. At that
time, the only purpose explained was to use it for explicit acking
of received state. My point was basically that we should explain,
justify and agree on what we want to achieve, and then start to
develop technical solutions.


> > Do you mean that this is the only way to provide a hook for
> > extended operations without negotiation?
> 
> How can a capability announcement mechanism be implemented without
> reserving an identifier (any flag or bit pattern) for each optional
> mechanism, and then transmitting a list of the supported mechanisms
> from one endpoint to another?

I would not immediately conclude that we obviously need a capability
announcement to support extended operations. I am not saying that we
can support everything without capability exchange, but I think this
should be discussed on a high level. Let's take the example with 
explicit acks, which is one kind of feedback. If we defined a generic
feedback mechanism to be used from the decompressor (incl. the UDVM)
to its peer compressor (who controls the UDVM). I can then see at
least two different principles for how this could be used for explicit
acks:
1) The compressor (who controls its peer UDVM) makes the UDVM send
feedback for received state through the feedback channel. If this is
possible, it would simply be an implementation issue. 
2) We could define feedback with a feedback type and only some
types are defined in SigComp. Others are left as reserved. New feedback
types must then be defined only for enhanced operation, so that a
compressor receiving feedback of "unknown" types could just discard it.
An explicit state-ack feedbcak type could then be defined in an
additional document. With such an approach, the enhancements would
be additional standards (new defined messages).

Please convince me that the above discussion is missing something
fundamental that invalidates the high-level principles described.

 
> > > [LEJ] Note:
> > >       When someone indicates that they know of potential IPR,
> > >       it does not necessary mean that it is their own IPR. I
> > >       hope we are all looking for potential IPR's on the
> > >       technology we are standardizing, so that we can indicate
> > >       this, or avoid the technology when that is desirable.
> > > 
> > > My understanding of the IETF approach to dealing with IPRs is 
> > > that an RFC includes an IPR statement only as a pointer to an
> > > official IPR announcement made at http://www.ietf.org/ipr.html.
> > 
> > RFC2026 states the following for all contributions, which affects 
> > all of us who write internet drafts:
> > 
> > : 10.3.1.  All Contributions
> > :
> > :   By submission of a contribution, each person actually 
> > :   submitting the contribution is deemed to agree to the
> > :   following terms and conditions on his own behalf, on
> > :   behalf of the organization (if any) he represents and
> > :   on behalf of the owners of any propriety rights in the
> > :   contribution. Where a submission identifies contributors
> > :   in addition to the contributor(s) who provide the actual 
> > :   submission, the actual submitter(s) represent that each
> > :   other named contributor was made aware of and agreed to
> > :   accept the same terms and conditions on his own behalf,
> > :   on behalf of any organization he may represent and any
> > :   known owner of any proprietary rights in the contribution.
> > :
> > :   6. The contributor represents that he has disclosed the
> > :      existence of any proprietary or intellectual property
> > :      rights in the contribution that are reasonably and
> > :      personally known to the contributor. The contributor
> > :      does not represent that he personally knows of all
> > :      potentially pertinent proprietary and intellectual
> > :      property rights owned or claimed by the organization
> > :      he represents (if any) or third parties.
> > 
> > As an author of a draft, you therefore MUST tell if YOU know of any
> > IPR on the technology described.
> >  
> > 
> > > The advantage of the above approach is that as authors, we 
> > > don't need to make a decision on whether particular patents are
> > > applicable to our work or not.
> > 
> > This is wrong. You MUST (as an author) indicate if you are 
> > aware of any patent on the technology.
> 
> The above statement seems to contradict the following, quoted from the
> previous discussion on IPRs between Scott Bradner and yourself:
> 
> "You have no obligation to send in an IPR notice for other 
> parties IPR's, and you might also have an NDA that prevents
> you from doing so. However, since it is beneficial for the
> community to know about all potential IPR's, if you can you
> should of course share your knowledge with the WG and the
> community."

I do not see the contradiction.
The above quote only discusses other parties IPR's, and it
is also captured in the RFC2026 text, which says "...rights in
the contribution that are reasonably and personally known to
the contributor". It is thus not expected that you should be
able to have knowledge and indicate presence of any IPR, but
at least those that are "reasonably and personally known". It
is therefore not true that you as an author do not need to have
opinions about patents, but the opposite. You are responsible to
make that judgment regarding those IPR's you are expected to
know about, and indicate "IPR risk" if you believe there is one.

Rgds, 
/L-E

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


From rohc-admin@ietf.org  Mon Feb 25 12:25: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 MAA19865
	for <rohc-archive@odin.ietf.org>; Mon, 25 Feb 2002 12:25:57 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA04859;
	Mon, 25 Feb 2002 12:14:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA04826
	for <rohc@optimus.ietf.org>; Mon, 25 Feb 2002 12:13:57 -0500 (EST)
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 MAA19272
	for <rohc@ietf.org>; Mon, 25 Feb 2002 12:13:51 -0500 (EST)
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 g1PHDOQ06107;
	Mon, 25 Feb 2002 18:13:24 +0100 (CET)
	(envelope-from Martin.Stiemerling@ccrle.nec.de)
Received: from imap.heidelberg.ccrle.nec.de (imap.heidelberg.ccrle.nec.de [192.168.102.11])
	by wallace.heidelberg.ccrle.nec.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id SAA28137;
	Mon, 25 Feb 2002 18:13:23 +0100
Received: from elgar (elgar.heidelberg.ccrle.nec.de [192.168.102.180])
	by imap.heidelberg.ccrle.nec.de (Postfix on SuSE Linux eMail Server 3.0) with ESMTP
	id 73177138A7; Mon, 25 Feb 2002 18:13:23 +0100 (CET)
Date: Mon, 25 Feb 2002 18:13:22 +0100
From: Martin Stiemerling <Martin.Stiemerling@ccrle.nec.de>
To: "West, Mark (ITN)" <mark.a.west@roke.co.uk>, rohc@ietf.org
Cc: Juergen Quittek <quittek@ccrle.nec.de>
Subject: Re: [rohc] Questions about the MIB!
Message-ID: <5400000.1014657202@elgar>
In-Reply-To: <3C7A0BF1.2030805@roke.co.uk>
References:  <3C7A0BF1.2030805@roke.co.uk>
X-Mailer: Mulberry/2.1.1 (Linux/x86)
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

Hi,

since Juergen is off for the next days I'll take the thread to handle the 
comments/thoughts.

Looking forward for a lot of comments!

Cheers
Martin


--On Montag, Februar 25, 2002 10:03:29 +0000 "West, Mark (ITN)" 
<mark.a.west@roke.co.uk> wrote:

>
> Hi ROHC-ers,
>
> If you haven't been put off by my use of 'MIB' in the subject line, then
> read on!
>
> Having just read through the draft MIB, a couple of questions have arisen
> which I think may benefit from a wider audience...
>
> Firstly, I'm curious to know how many fellow implementors have done
> anything with the packet-size / payload-size restrictions?  (I know we
> haven't ;-)
>
> Secondly, the more general issue is this: there is a quantity of
> information about contexts which is based on the profiles defined in
> RFC-3095.  (For example, referring to the modes as U, O and R and states
> as IR/FO/SO).  This makes absolute sense with regard to RFC 3095.  I am
> interested to know what anyone thinks about the impact of splitting 3095,
> however!  How much of the MIB can/should be based on specific profile
> details, rather than 'generic' framework?  (Clearly in the cases
> mentioned above, opaque numeric identifiers could be used) Anyway, it's a
> general issue that it would be nice to have some input on...
>
> On a related note, there are a number of configuration parameters which
> only really have 'per profile' significance (for example 'k_1' and
> 'n_1').  These parameters are specific to certain profiles .  'k and n'
> also make a useful example, in that k_1 and n_1 are likely to be chosen
> based on the link characteristics.  So, we have values that are
> per-profile and should be configurable (at least) per-interface.  (I
> suppose it makes sense, anyway, to know which profiles are supported on
> any given interface...)
>
> Where a context is using a particular profile, it is not clear to me
> whether or not it is desirable to be able to 'tweak' these values on a
> per-context basis.  Again, 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)



Martin Stiemerling

NEC Europe Ltd. -- Network Laboratories      Martin.Stiemerling@ccrle.nec.de
IPv4: http://www.ccrle.nec.de             IPv6: http://www.ipv6.ccrle.nec.de

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


From rohc-admin@ietf.org  Mon Feb 25 20:12:43 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 UAA05391
	for <rohc-archive@odin.ietf.org>; Mon, 25 Feb 2002 20:12:43 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA29127;
	Mon, 25 Feb 2002 20:09:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA29098
	for <rohc@optimus.ietf.org>; Mon, 25 Feb 2002 20:09:22 -0500 (EST)
Received: from mgw-x3.nokia.com (mgw-x3.nokia.com [131.228.20.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05364
	for <rohc@ietf.org>; Mon, 25 Feb 2002 20:09:18 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x3.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g1Q19qi20190
	for <rohc@ietf.org>; Tue, 26 Feb 2002 03:09:52 +0200 (EET)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T594cd295beac158f21082@esvir01nok.ntc.nokia.com> for <rohc@ietf.org>;
 Tue, 26 Feb 2002 03:09:18 +0200
Received: from daebh001.NOE.Nokia.com ([172.18.242.231]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779);
	 Tue, 26 Feb 2002 03:09:18 +0200
Received: from daebe005.NOE.Nokia.com ([172.18.242.203]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 25 Feb 2002 19:09:16 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [rohc] RE: Default decompression algorithms
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Date: Mon, 25 Feb 2002 19:09:16 -0600
Message-ID: <DE0842B293FC4847992F9EDF8D72E1ED24A262@daebe005.NOE.Nokia.com>
Thread-Topic: [rohc] RE: Default decompression algorithms
Thread-Index: AcG90O+SWvkb5uBqQ3qXOfXurMuOygAjRf5A
To: <rohc@ietf.org>
X-OriginalArrivalTime: 26 Feb 2002 01:09:16.0909 (UTC) FILETIME=[363C79D0:01C1BE62]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id UAA29099
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

Folks,

Let's conclude this issue. We've spent too much time on this.

- We need a mechanism to allow the decompressor to announce the
decompression code it can locally generate or it already
has (see below). It seems most people agree with my proposal: http://www.cdt.luth.se/robhc/msg03642.html. That's all we need.

- Let's not call them "default" or "mandatory", at least not here
in IETF. The choice is the compressor's. If its choice happens
to be popular, then it can avoid sending it over the air using
above mechanism. But that's it. Nothing more.

- Documentation of "well-known" decompression code is second 
priority to other things. It can be done either in IETF or 3GPP. 
But let's finish other more important things (e.g. security, state
management) first in this WG.

- The issue is not even about documented code. The above mechanism
is useful when multiple mobiles use the same code. Once the
decompressor acquire one copy of the code from one mobile, there 
is no need to download the code later when another mobiles talk to 
the same decompressor in the network. 

BR,
Zhigang



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


From rohc-admin@ietf.org  Mon Feb 25 20:35: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 UAA05689
	for <rohc-archive@odin.ietf.org>; Mon, 25 Feb 2002 20:35:34 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA29680;
	Mon, 25 Feb 2002 20:29:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA29632
	for <rohc@optimus.ietf.org>; Mon, 25 Feb 2002 20:29:36 -0500 (EST)
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 UAA05554
	for <rohc@ietf.org>; Mon, 25 Feb 2002 20:29:09 -0500 (EST)
Received: from cabo3 (nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with SMTP id g1Q1T4C10691
	for <rohc@ietf.org>; Tue, 26 Feb 2002 02:29:04 +0100 (MET)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: <rohc@ietf.org>
Subject: [rohc] Making SigComp recognizable
Date: Tue, 26 Feb 2002 02:29:03 +0100
Message-ID: <NFBBJFHGMCFINEMHAMBGCEIBHHAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
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

In a phone conversation today, it occurred to us that it would be a good
idea to make SigComp packets clearly distinguishable from uncompressed
packets.
For SIP, this is easy, as all methods and reply codes are ASCII, so setting
the MSB in the first byte of all packets would suffice.
However, it's probably a good idea not to trigger the link-layer RTP ROHC
heuristics, which tend to look for 10xxxxxx in the first byte (RTP V=2) of
UDP packets.
More generally, I think we want to cater for general UTF-8-based signalling
protocols. Looking at RFC2044, we have:

   UCS-4 range (hex.)           UTF-8 octet sequence (binary)
   0000 0000-0000 007F   0xxxxxxx
   0000 0080-0000 07FF   110xxxxx 10xxxxxx
   0000 0800-0000 FFFF   1110xxxx 10xxxxxx 10xxxxxx

   0001 0000-001F FFFF   11110xxx 10xxxxxx 10xxxxxx 10xxxxxx
   0020 0000-03FF FFFF   111110xx 10xxxxxx 10xxxxxx 10xxxxxx 10xxxxxx
   0400 0000-7FFF FFFF   1111110x 10xxxxxx ... 10xxxxxx

Now, since RFC2044 (October 1996), Unicode has been decided to stop at 0010
FFFF, so the code combinations

   0020 0000-03FF FFFF   111110xx 10xxxxxx 10xxxxxx 10xxxxxx 10xxxxxx
   0400 0000-7FFF FFFF   1111110x 10xxxxxx ... 10xxxxxx

never can appear in real UTF-8.

Leaping to a conclusion, it seems a SigComp/UDP packet should start with

	11111xxx

Sigcomp-04 uses 0xFF as an escape character, so xxx=111 should probably also
be avoided.
Alternatively, we could simply define a single byte distinguisher for UDP
and start all TCP streams with the escape sequence (and not use the UDP
distinguisher here).

Any other things we should avoid?  General comments on the whole approach?
(I just wish UDP had a protocol field.)

Gruesse, Carsten

PS.: Anyone for defining an RFC2246 (TLS) CompressionMethod value for
SigComp?
Should be fun, and would save the 0xFFFFs.
Can't even find an IANA registry for TLS, though.

PPS.: RFC2817 section 1 (motivation) is interesting reading.
Has anyone implemented that spec?
Could be done for SIP, too.




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


From rohc-admin@ietf.org  Mon Feb 25 20:42: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 UAA05792
	for <rohc-archive@odin.ietf.org>; Mon, 25 Feb 2002 20:42:23 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA00436;
	Mon, 25 Feb 2002 20:40:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA00406
	for <rohc@optimus.ietf.org>; Mon, 25 Feb 2002 20:40:03 -0500 (EST)
Received: from minotaur.nge.isi.edu (minotaur.nge.isi.edu [65.114.169.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05740
	for <rohc@ietf.org>; Mon, 25 Feb 2002 20:39:59 -0500 (EST)
Received: from minotaur (mankin@localhost)
	by minotaur.nge.isi.edu (8.11.6/8.11.6) with ESMTP id g1Q1e0k08723;
	Mon, 25 Feb 2002 20:40:00 -0500
Message-Id: <200202260140.g1Q1e0k08723@minotaur.nge.isi.edu>
To: "Dr. Carsten Bormann" <cabo@tzi.org>
cc: rohc@ietf.org
Reply-To: mankin@isi.edu
Subject: Re: [rohc] Making SigComp recognizable 
In-reply-to: Your message of Tue, 26 Feb 2002 02:29:03 +0100.
             <NFBBJFHGMCFINEMHAMBGCEIBHHAA.cabo@tzi.org> 
Mime-Version: 1.0 (generated by tm-edit 1.7)
Content-Type: text/plain; charset=US-ASCII
Date: Mon, 25 Feb 2002 20:40:00 -0500
From: Allison Mankin <mankin@isi.edu>
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

> PS.: Anyone for defining an RFC2246 (TLS) CompressionMethod value for 
> SigComp? 
> Should be fun, and would save the 0xFFFFs. 
> Can't even find an IANA registry for TLS, though. 

There isn't one now, but the IESG discussed it, and I think
perhaps it is a subject for RFC2246bis, of which an i-d has
just come out.

Allison

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


From rohc-admin@ietf.org  Mon Feb 25 20:43: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 UAA05810
	for <rohc-archive@odin.ietf.org>; Mon, 25 Feb 2002 20:43:16 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA00498;
	Mon, 25 Feb 2002 20:41:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA00471
	for <rohc@optimus.ietf.org>; Mon, 25 Feb 2002 20:41:20 -0500 (EST)
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 UAA05757
	for <rohc@ietf.org>; Mon, 25 Feb 2002 20:41:16 -0500 (EST)
Received: from cabo3 (nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with SMTP id g1Q1f7C12412;
	Tue, 26 Feb 2002 02:41:08 +0100 (MET)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: <zhigang.c.liu@nokia.com>, <rohc@ietf.org>
Subject: RE: [rohc] RE: Default decompression algorithms
Date: Tue, 26 Feb 2002 02:41:06 +0100
Message-ID: <NFBBJFHGMCFINEMHAMBGKEIBHHAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-reply-to: <DE0842B293FC4847992F9EDF8D72E1ED24A262@daebe005.NOE.Nokia.com>
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

> Let's conclude this issue. We've spent too much time on this.

Good point.

> - We need a mechanism to allow the decompressor to announce the
> decompression code it can locally generate or it already
> has (see below). It seems most people agree with my proposal:
> http://www.cdt.luth.se/robhc/msg03642.html. That's all we need.

I'm not sure it is exactly clear what this message proposes.
Who is going to write this up?

> - Let's not call them "default" or "mandatory", at least not here
> in IETF. The choice is the compressor's. If its choice happens
> to be popular, then it can avoid sending it over the air using
> above mechanism. But that's it. Nothing more.

If it somehow gets a message from the decompressor first.
I don't think we have agreement on the need for this additional expensive
round trip yet.
(Of course, in a specific environment, that knowledge may come from a
different protocol.)

> - Documentation of "well-known" decompression code is second
> priority to other things. It can be done either in IETF or 3GPP.
> But let's finish other more important things (e.g. security, state
> management) first in this WG.

I think we do have consensus on this point.
This work is not standards-track, we don't have to (nor should) agree on
anything.
(Work on specific decompressors is needed for validation, though.)

> - The issue is not even about documented code. The above mechanism
> is useful when multiple mobiles use the same code. Once the
> decompressor acquire one copy of the code from one mobile, there
> is no need to download the code later when another mobiles talk to
> the same decompressor in the network.

If the mobile somehow gets a message from the decompressor first.

Gruesse, Carsten


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


From rohc-admin@ietf.org  Tue Feb 26 05:56: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 FAA22850
	for <rohc-archive@odin.ietf.org>; Tue, 26 Feb 2002 05:56:50 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA04160;
	Tue, 26 Feb 2002 05:43:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA04129
	for <rohc@optimus.ietf.org>; Tue, 26 Feb 2002 05:43:47 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22761
	for <rohc@ietf.org>; Tue, 26 Feb 2002 05:43:42 -0500 (EST)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g1QAhiB19787
	for <rohc@ietf.org>; Tue, 26 Feb 2002 11:43:45 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Tue Feb 26 11:43:40 2002 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <F4G4THDG>; Tue, 26 Feb 2002 11:43:41 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E31E3A@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Subject: Closed: [rohc] When posting to "rohc@cdt.luth.se"
Date: Tue, 26 Feb 2002 11:43:01 +0100
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

Only two "real" messages have been posted to the old mail list
since the new list was activated, and this happened early the
week after the transition was executed. The ROHC WG page has
also now been updated and points to the new list. 

Therefore, we have now decided to close "rohc@cdt.luth.se".

The old archive stays where it is and a copy will also be placed
close to the new archive at ietf.org. More on that later.

/L-E



> -----Original Message-----
> From: Lars-Erik Jonsson (EPL) 
> [mailto:Lars-Erik.Jonsson@epl.ericsson.se]
> Sent: den 17 februari 2002 13:31
> To: 'rohc@cdt.luth.se'
> Subject: [rohc] When posting to "rohc@cdt.luth.se"
> 
> 
> The mailing list for Robust Header Compression WG is rohc@ietf.org
> This mail was sent via the old rohc@cdt.luth.se list
> The rohc@cdt.luth.se list will soon be inactive
> ---
> ROHCers,
> 
> During a transition period, postings to rohc@cdt.luth.se will be
> forwarded in this way to rohc@ietf.org. However, note that this is
> a short-term service. Please post only to the new list.
> 
> BR
> /Lars-Erik
> ---
> Mailing list for Robust Header Compression WG
> Archive: http://www.cdt.luth.se/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  Tue Feb 26 07:06: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 HAA24764
	for <rohc-archive@odin.ietf.org>; Tue, 26 Feb 2002 07:06:18 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA08399;
	Tue, 26 Feb 2002 07:03:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA08372
	for <rohc@optimus.ietf.org>; Tue, 26 Feb 2002 07:03:08 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24124;
	Tue, 26 Feb 2002 07:03:05 -0500 (EST)
Message-Id: <200202261203.HAA24124@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, 26 Feb 2002 07:03:05 -0500
Subject: [rohc] I-D ACTION:draft-pelletier-rohc-udplite-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):Profiles for UDP Lite
	Author(s)	: G. Pelletier
	Filename	: draft-pelletier-rohc-udplite-00.txt
	Pages		: 14
	Date		: 25-Feb-02
	
This document defines ROHC (Robust Header Compression) profiles for
compression of IP/UDP Lite/RTP packets (Internet Protocol, User
Datagram Protocol Lite, Real-Time Transport Protocol) and IP/UDP
Lite. These profiles are defined based on their differences with the
profiles specified in [RFC-3095] for the classic UDP [RFC-768].

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

ENCODING mime
FILE /internet-drafts/draft-pelletier-rohc-udplite-00.txt

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

Content-Type: text/plain
Content-ID:	<20020225142810.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 Feb 26 07:07: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 HAA24834
	for <rohc-archive@odin.ietf.org>; Tue, 26 Feb 2002 07:07:39 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA08450;
	Tue, 26 Feb 2002 07:03:42 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA08416
	for <rohc@optimus.ietf.org>; Tue, 26 Feb 2002 07:03:40 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24305;
	Tue, 26 Feb 2002 07:03:36 -0500 (EST)
Message-Id: <200202261203.HAA24305@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, 26 Feb 2002 07:03:36 -0500
Subject: [rohc] I-D ACTION:draft-west-sctp-epic-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		: SCTP Profile for EPIC
	Author(s)	: M. West, A. Surtees
	Filename	: draft-west-sctp-epic-00.txt
	Pages		: 30
	Date		: 25-Feb-02
	
This draft describes a profile for compressing SCTP/IP using the
Efficient Protocol Independent Compression (EPIC) [2] scheme.
The RObust Header Compression [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.
This profile describes a new profile for ROHC which will allow SCTP/
IP headers to be compressed.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-west-sctp-epic-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-sctp-epic-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-sctp-epic-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:	<20020225142922.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-west-sctp-epic-00.txt

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

Content-Type: text/plain
Content-ID:	<20020225142922.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 Feb 26 08:27:11 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 IAA28137
	for <rohc-archive@odin.ietf.org>; Tue, 26 Feb 2002 08:27:10 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA11828;
	Tue, 26 Feb 2002 08:18:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA11795
	for <rohc@optimus.ietf.org>; Tue, 26 Feb 2002 08:18:12 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.46])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27633
	for <rohc@ietf.org>; Tue, 26 Feb 2002 08:18:08 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g1QDIAZc027461
	for <rohc@ietf.org>; Tue, 26 Feb 2002 14:18:10 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt461 ; Tue Feb 26 14:18:10 2002 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <F4G2F3V3>; Tue, 26 Feb 2002 14:08:30 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E31E43@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "Rohc (E-mail)" <rohc@ietf.org>
Date: Tue, 26 Feb 2002 14:17:28 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [rohc] Old ROHC archive
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 ROHCers,

The old ROHC mail list archive will also in the future 
be available at:
http://www.cdt.luth.se/rohc

I have created alternative index files to the archive,
from which I have removed all spam messages. However,
the original index files are also available. 

With this action, the mail list and archive transfer is
completed at the cdt.luth.se side, with the old list
closed and the archive frozen in its current form with
a spam-free alternative to the original. On the ietf.org
side, what is still missing is a copy of the old archive
and a pointer to it somewhere. Apart from that, we are
done.

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  Tue Feb 26 10:31:42 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 KAA03507
	for <rohc-archive@odin.ietf.org>; Tue, 26 Feb 2002 10:31:42 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA18100;
	Tue, 26 Feb 2002 10:29:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA18072
	for <rohc@optimus.ietf.org>; Tue, 26 Feb 2002 10:29:16 -0500 (EST)
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 KAA03381
	for <rohc@ietf.org>; Tue, 26 Feb 2002 10:29:13 -0500 (EST)
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.1.0/Switch-2.1.0) with ESMTP id g1QFVKx10940
	for <rohc@ietf.org>; Tue, 26 Feb 2002 09:31:20 -0600 (CST)
Received: from daebh002.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T594e2e6cdbac12f25507a@davir02nok.americas.nokia.com>;
 Tue, 26 Feb 2002 09:29:14 -0600
Received: from daebe005.NOE.Nokia.com ([172.18.242.203]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Tue, 26 Feb 2002 09:28:35 -0600
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] RE: Default decompression algorithms
Date: Tue, 26 Feb 2002 09:28:34 -0600
Message-ID: <DE0842B293FC4847992F9EDF8D72E1ED24A264@daebe005.NOE.Nokia.com>
Thread-Topic: [rohc] RE: Default decompression algorithms
Thread-Index: AcG+ZrHAuwW3bQxzR+OY+jmgr9m1YgAcqh0g
To: <cabo@tzi.org>, <rohc@ietf.org>
X-OriginalArrivalTime: 26 Feb 2002 15:28:35.0736 (UTC) FILETIME=[41B12180:01C1BEDA]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA18073
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

> > - We need a mechanism to allow the decompressor to announce the
> > decompression code it can locally generate or it already
> > has (see below). It seems most people agree with my proposal:
> > http://www.cdt.luth.se/robhc/msg03642.html. That's all we need.
> 
> I'm not sure it is exactly clear what this message proposes.
> Who is going to write this up?

I'll write it up.

Zhigang

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


From rohc-admin@ietf.org  Tue Feb 26 11:16: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 LAA05722
	for <rohc-archive@odin.ietf.org>; Tue, 26 Feb 2002 11:16:40 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA20404;
	Tue, 26 Feb 2002 11:13:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA20371
	for <rohc@optimus.ietf.org>; Tue, 26 Feb 2002 11:13:55 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05535
	for <rohc@ietf.org>; Tue, 26 Feb 2002 11:13:51 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g1QGDsB26849;
	Tue, 26 Feb 2002 17:13:54 +0100 (MET)
Received: from ericsson.com (3NJPI0013L1IJOG.lmf.ericsson.se [131.160.30.42])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g1QGDrmK020913;
	Tue, 26 Feb 2002 18:13:53 +0200 (EET)
Message-ID: <3C7BB47C.F03E93FD@ericsson.com>
Date: Tue, 26 Feb 2002 18:14:52 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Organization: OY LM Ericsson AB
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: es,en
MIME-Version: 1.0
To: zhigang.c.liu@nokia.com
CC: rohc@ietf.org
Subject: Re: [rohc] RE: Default decompression algorithms
References: <DE0842B293FC4847992F9EDF8D72E1ED24A262@daebe005.NOE.Nokia.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

Hi:

I am aligned with Zhigang. I believe there is not need to define
a "default" or "mandatory" algorythm. If other organizations, 
like 3GPP, want to define such an algorythm, that is fine, but
please, don't do it here in the IETF.

I also agree with the requirement whereby a decompressor informs
the compressor of the algorythms that are already uploaded, and
therefore, don't need to be uploaded again. This is just to 
save bandwidth over the air interface and avoid unneeded uploads. 
I think this is a very valid requirement.

/Miguel

zhigang.c.liu@nokia.com wrote:
> 
> Folks,
> 
> Let's conclude this issue. We've spent too much time on this.
> 
> - We need a mechanism to allow the decompressor to announce the
> decompression code it can locally generate or it already
> has (see below). It seems most people agree with my proposal: http://www.cdt.luth.se/robhc/msg03642.html. That's all we need.
> 
> - Let's not call them "default" or "mandatory", at least not here
> in IETF. The choice is the compressor's. If its choice happens
> to be popular, then it can avoid sending it over the air using
> above mechanism. But that's it. Nothing more.
> 
> - Documentation of "well-known" decompression code is second
> priority to other things. It can be done either in IETF or 3GPP.
> But let's finish other more important things (e.g. security, state
> management) first in this WG.
> 
> - The issue is not even about documented code. The above mechanism
> is useful when multiple mobiles use the same code. Once the
> decompressor acquire one copy of the code from one mobile, there
> is no need to download the code later when another mobiles talk to
> the same decompressor in the network.
> 
> BR,
> Zhigang
> 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc

-- 
Miguel-Angel Garcia                     Oy LM Ericsson AB
                                        Jorvas, Finland
mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 5140002

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


From rohc-admin@ietf.org  Tue Feb 26 11:31:13 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 LAA06478
	for <rohc-archive@odin.ietf.org>; Tue, 26 Feb 2002 11:31:09 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21575;
	Tue, 26 Feb 2002 11:28:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21538
	for <rohc@optimus.ietf.org>; Tue, 26 Feb 2002 11:28:36 -0500 (EST)
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 LAA06368
	for <rohc@ietf.org>; Tue, 26 Feb 2002 11:28:32 -0500 (EST)
Received: from cabo3 (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with SMTP id g1QGSOC21659;
	Tue, 26 Feb 2002 17:28:24 +0100 (MET)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>,
        <zhigang.c.liu@nokia.com>
Cc: <rohc@ietf.org>
Subject: RE: [rohc] RE: Default decompression algorithms
Date: Tue, 26 Feb 2002 17:28:21 +0100
Message-ID: <NFBBJFHGMCFINEMHAMBGAEIGHHAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-reply-to: <3C7BB47C.F03E93FD@ericsson.com>
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

> I also agree with the requirement whereby a decompressor informs
> the compressor of the algorythms that are already uploaded, and
> therefore, don't need to be uploaded again. This is just to
> save bandwidth over the air interface and avoid unneeded uploads.
> I think this is a very valid requirement.

How many algorithms are there going to be in the cache of a typical
decompressor?
What is the cost of supplying this information?
Explain how this computes.

Gruesse, Carsten


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


From rohc-admin@ietf.org  Tue Feb 26 11:57: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 LAA10067
	for <rohc-archive@odin.ietf.org>; Tue, 26 Feb 2002 11:57:50 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA23325;
	Tue, 26 Feb 2002 11:52:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA23294
	for <rohc@optimus.ietf.org>; Tue, 26 Feb 2002 11:51:58 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.46])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09774
	for <rohc@ietf.org>; Tue, 26 Feb 2002 11:51:49 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g1QGpnZc004351;
	Tue, 26 Feb 2002 17:51:49 +0100 (MET)
Received: from ericsson.com (3NJPI0013L1IJOG.lmf.ericsson.se [131.160.30.42])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g1QGpmmK022604;
	Tue, 26 Feb 2002 18:51:48 +0200 (EET)
Message-ID: <3C7BBD5F.A44B6916@ericsson.com>
Date: Tue, 26 Feb 2002 18:52:47 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Organization: OY LM Ericsson AB
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: es,en
MIME-Version: 1.0
To: "Dr. Carsten Bormann" <cabo@tzi.org>
CC: zhigang.c.liu@nokia.com, rohc@ietf.org
Subject: Re: [rohc] RE: Default decompression algorithms
References: <NFBBJFHGMCFINEMHAMBGAEIGHHAA.cabo@tzi.org>
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

Hi:

I will try to explain the scenario I am thinking of, and then try
to answer your questions.

Typically a proxy will be serving many users, let's say, thousands.
As such, when a terminal starts the SigComp procedures towards the
proxy, it might happen that the proxy has got a copy of the algorithm,
because the same algorithm was already uploaded by another terminal.

If this is the case, the decompressor at the proxy should announce that
those algorithms that are already uploaded, and therefore, don't require
to be uploaded once more.

If it happens that the terminal wants to use a different algorithm that
is not already in use at that proxy, then the terminal will know that
the algorithm is not uploaded and the terminal needs to uploaded.

You asked how many algorithms are going to be in the cache of a 
typical decompressor, and that question is related to how many users
a proxy can support simultaneously, and how many different algorithms.
In other words, it is implementation dependent, and the answer to the
question does not have an impact on the standardization in Rohc.

The cost of supplying the information: I don't have a strong opinion
on how this can be done, but I will refer to examples that are working
today in other protocols. For instance, RTP decided to use a profile
for Audio/Video codecs (RFC 1890). Known codecs are assigned a Payload
Type in RTP. So Payload Type 0 means PCM u-law codec, Payload 8 means 
PCM A-law codec. 

In SigComp, we could take the same approach, in a way that we define
a standard way to refer to known algorithms. The decompressor, in
the SigComp Capabilities Announcements would indicate the list of 
algorithms that are already uploaded (in a similar way of how SDP,
RFC 2327 negotiates codecs).

If there are other opinions how to fulfill the requirement, I would 
like to listen to them.

/Miguel

"Dr. Carsten Bormann" wrote:
> 
> > I also agree with the requirement whereby a decompressor informs
> > the compressor of the algorythms that are already uploaded, and
> > therefore, don't need to be uploaded again. This is just to
> > save bandwidth over the air interface and avoid unneeded uploads.
> > I think this is a very valid requirement.
> 
> How many algorithms are there going to be in the cache of a typical
> decompressor?
> What is the cost of supplying this information?
> Explain how this computes.
> 
> Gruesse, Carsten

-- 
Miguel-Angel Garcia                     Oy LM Ericsson AB
                                        Jorvas, Finland
mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 5140002

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


From rohc-admin@ietf.org  Tue Feb 26 12:02:52 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 MAA10411
	for <rohc-archive@odin.ietf.org>; Tue, 26 Feb 2002 12:02:52 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA23585;
	Tue, 26 Feb 2002 11:57:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA23555
	for <rohc@optimus.ietf.org>; Tue, 26 Feb 2002 11:57:32 -0500 (EST)
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 LAA10060
	for <rohc@ietf.org>; Tue, 26 Feb 2002 11:57:27 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from esvir02nok.ntc.nokia.com (esvir02nokt.ntc.nokia.com [172.21.143.34])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g1QGveZ04823
	for <rohc@ietf.org>; Tue, 26 Feb 2002 18:57:40 +0200 (EET)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir02nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T595036b140ac158f22076@esvir02nok.ntc.nokia.com>;
 Tue, 26 Feb 2002 18:57:30 +0200
Received: from daebh002.NOE.Nokia.com ([172.18.242.232]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779);
	 Tue, 26 Feb 2002 18:57:30 +0200
Received: from daebe005.NOE.Nokia.com ([172.18.242.203]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Tue, 26 Feb 2002 10:57:26 -0600
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] RE: Default decompression algorithms
Date: Tue, 26 Feb 2002 10:57:26 -0600
Message-ID: <DE0842B293FC4847992F9EDF8D72E1ED24A266@daebe005.NOE.Nokia.com>
Thread-Topic: [rohc] RE: Default decompression algorithms
Thread-Index: AcG+4qIyaxVUJRCuTsqCtsHuRm5myAAAGUOA
To: <cabo@tzi.org>, <Miguel.A.Garcia@ericsson.com>
Cc: <rohc@ietf.org>
X-OriginalArrivalTime: 26 Feb 2002 16:57:26.0961 (UTC) FILETIME=[AB598210:01C1BEE6]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA23556
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

> -----Original Message-----
> From: ext Dr. Carsten Bormann [mailto:cabo@tzi.org]
> Sent: February 26, 2002 10:28 AM
> To: Miguel A. Garcia; Liu Zhigang.C (NRC/Dallas)
> Cc: rohc@ietf.org
> Subject: RE: [rohc] RE: Default decompression algorithms
> 
> 
> > I also agree with the requirement whereby a decompressor informs
> > the compressor of the algorythms that are already uploaded, and
> > therefore, don't need to be uploaded again. This is just to
> > save bandwidth over the air interface and avoid unneeded uploads.
> > I think this is a very valid requirement.
> 
> How many algorithms are there going to be in the cache of a typical
> decompressor?

That depends on the cache size. For a mobile, it should be a 
small number. For the network-side decompressor, it anyway has
to store decompression codes corresponding to each active compressor
(in mobiles). So, it may has a large number of codes.

> What is the cost of supplying this information?

The announcement message overhead = n * 6, where n is the number 
of decompression codes and 6 is the number of bytes for a hash. 
Let s be the average code size and p(n) be the probability of 
a hit. Then the savings = (s - 6n) * p(n).

Of course, the RTT as you mentioned is also a cost. But if the
announcement can be piggybacked on the reply from the decompressor
during the negotiation of the use of SigComp, it is not an extra
cost anymore. (But I don't know if the message sequence Hans 
outlined sometime ago is still valid.)

BR,
Zhigang


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


From rohc-admin@ietf.org  Tue Feb 26 13:32: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 NAA15042
	for <rohc-archive@odin.ietf.org>; Tue, 26 Feb 2002 13:32:49 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA09638;
	Tue, 26 Feb 2002 13:26:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA09607
	for <rohc@optimus.ietf.org>; Tue, 26 Feb 2002 13:26:41 -0500 (EST)
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 NAA14772
	for <rohc@ietf.org>; Tue, 26 Feb 2002 13:26:38 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from esvir02nok.ntc.nokia.com (esvir02nokt.ntc.nokia.com [172.21.143.34])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g1QIQnZ05352
	for <rohc@ietf.org>; Tue, 26 Feb 2002 20:26:49 +0200 (EET)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir02nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5950884fc8ac158f22076@esvir02nok.ntc.nokia.com> for <rohc@ietf.org>;
 Tue, 26 Feb 2002 20:26:39 +0200
Received: from daebh001.NOE.Nokia.com ([172.18.242.231]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779);
	 Tue, 26 Feb 2002 20:26:39 +0200
Received: from daebe005.NOE.Nokia.com ([172.18.242.203]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Tue, 26 Feb 2002 12:25:37 -0600
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"
Date: Tue, 26 Feb 2002 12:25:36 -0600
Message-ID: <DE0842B293FC4847992F9EDF8D72E1ED24A267@daebe005.NOE.Nokia.com>
Thread-Topic: decompression code announcement (was  RE: Default decompression algorithms)
Thread-Index: AcG+8vwcEFQ8fyqjEdaaLwAQpIbXLw==
To: <rohc@ietf.org>
X-OriginalArrivalTime: 26 Feb 2002 18:25:37.0213 (UTC) FILETIME=[FC95E6D0:01C1BEF2]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id NAA09608
Subject: [rohc] decompression code announcement (was  RE: Default decompression algorithms)
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,

Below is a quick write-up I promised earlier. Comments welcome.

BR,
Zhigang

=============================================================

Decompression code announcement
-------------------------------

During normal SigComp operation, a compressor needs to
send the decompression code consisting of UDVM instructions
to its peer decompressor before any message can be decompressed.
The overhead of sending the code may be undesirable in wireless
environment, which is the major application of SigComp.
Following outlines an optimization that reduces such overhead.

1) It is assumed that a compressor (or application) contacts 
its peer decompressor (or application) before applying SigComp
to compress messages, e.g., during negotiation of the use of
SigComp. (See note c).)

2) When the decompressor (or application) replies to the compressor,
it can piggyback in the message a list of hash values of the 
decompression codes it already has (see note b) below).

3) Upon receiving such a list, the compressor compares the hash
values in the list with the one of the decompression code it wants
the decompressor to use. If a match is found (i.e. it's a hit), the 
compressor no longer needs to upload the code to the decompressor. 
If no match is found or the compressor would rather use a different 
decompression code, it will upload the code to the decompressor.

4) The decompression code announcement may contain empty list. 

Notes:

a) The decompressor may have a piece of decompression code in different
ways. Case 1 is that a decompressor supports a set of well-know 
algorithms whose decompression codes are documented. It can store the 
codes locally hoping the peer compressor is likely to use one of them. 
Case 2 is that a decompressor (e.g. in P-CSCF in 3GPP) may actively engaged
with multiple compressors (e.g. in mobiles) that use the same decompression 
code. Therefore, once the decompressor acquires one copy of the code
from one compressor, it can use the code announcement to avoid redundant
code uploading from other compressors later.

b) The hash value could be the constructed using the first n bytes of
MD5 hash over the decompression code. n should be large enough so that
collision probability is negligible in practice.

c) For step 2 above, the decompression code announcement could be done
in other ways, e.g. out-of-band or in a pre-configured way. Basically, 
it can be bundled together with the SigComp negotiation/discovery 
mechanism to avoid additional round trip delay.

d) In any case, if compressor does not expect a message from its
peer decompressor as it is assumed in step 1, it should always 
follow the default procedure to upload the decompression code. 

e) Obviously, the mechanism gives benefits only when the hit probability
is high. If a decompressor is not confident about that, it can always
send empty list in the announcement or does not send the announcement
at all if the compressor does not expect its message.
=====================================================================

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


From rohc-admin@ietf.org  Tue Feb 26 16:08:45 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 QAA21702
	for <rohc-archive@odin.ietf.org>; Tue, 26 Feb 2002 16:08:44 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA19280;
	Tue, 26 Feb 2002 15:55:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA19249
	for <rohc@optimus.ietf.org>; Tue, 26 Feb 2002 15:54:57 -0500 (EST)
Received: from marjan.fesb.hr (root@marjan.fesb.hr [161.53.166.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21275
	for <rohc@ietf.org>; Tue, 26 Feb 2002 15:54:45 -0500 (EST)
Received: (from root@localhost)
	by marjan.fesb.hr (8.9.3/8.9.3) id VAA03774
	for rohc@ietf.org; Tue, 26 Feb 2002 21:54:39 +0100 (MET)
Received: from fesb.hr (demorgan.bit.fesb.hr [161.53.169.245])
	by marjan.fesb.hr (8.9.3/8.9.3) with ESMTP id VAA03765
	for <rohc@ietf.org>; Tue, 26 Feb 2002 21:54:31 +0100 (MET)
Message-ID: <3C7BF6E0.9070307@fesb.hr>
Date: Tue, 26 Feb 2002 21:58:08 +0100
From: Julije Ozegovic <julije@fesb.hr>
Organization: FESB Split
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1
X-Accept-Language: en, hr
MIME-Version: 1.0
To: rohc <rohc@ietf.org>
Content-Type: multipart/mixed;
 boundary="------------060302020000080400000603"
X-Virus-Scanned: by AMaViS perl-11
Subject: [rohc] TCP/IP EPIC profile
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.
--------------060302020000080400000603
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Dear ROHCers,

here we include "expanded" TCP/IP profile as published in

TCP/IP Header Compression for ROHC (ROHC-TCP)
<draft-ietf-rohc-tcp-00.txt>

The purpose of this posting is to point out the complexity of 
whole thing, regarding the fact that almost every line of 
profile ends up with (at least) one data structure in end user 
application.

The questions are:
    do we really want this?
    do we really need this?
    is it worth the effort?
    is it applicable to target machine (GSM)?
    do we really need (48+2)*60=3000 formats?

Besides this, comments about inconsistencies of the profile are 
listed inline.

We also want to raise discussion about usage of FORMAT method.

The questions are:

    - what about difference in FORMAT structure
      between CO and IR/DYN packets,
      shouldn't they be the same (by EPIC draft)?

    - what about usage of IRREGULAR method in all sets
      (except last one where it should be used),
      this way first set will always be selected

    - what about syntax and usage of FORMAT SELECTOR,
      it is actually not needed (can be identified from
      ID-bits of IR/DYN packet)

Best regards,
Julije Ozegovic

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

TCP-IP EPIC-LITE profile expanded according to
TCP/IP Header Compression for ROHC (ROHC-TCP) 
<draft-ietf-rohc-tcp-00.txt>


;**uses much more, but need be digged out :)
only uses the following toolbox methods:  
 - STATIC-KNOWN  
 - STATIC-UNKNOWN  
 - STATIC  
 - IRREGULAR  
 - LSB  
 - VALUE  
 - C  
       
   
 profile_identifier      0xFFFF  
 max_formats             60 
 max_sets                48 
 bit_alignment           8  
 npatterns               224  
 CO_packet               TCP-IP-CO 
 IR_packet               TCP-IP-IR 
 IR-DYN_packet           TCP-IP-DYN 



TCP-IP-CO       =      

;**IP checksum treated later anyway
;**not in current EPIC-lite toolbox
  INFERRED-IP-CHECKSUM(IPv4-co-header) 
    IPv4-co-header  =
      version         =  VALUE(4,4,100%) 
      header_len      =  VALUE(4,5,100%) 
      tos-co          =  STATIC(99%) | IRREGULAR(6,1%)
      ecn             =  STACK-TO-CONTROL(2) 
      length          =  INFERRED-SIZE(16,128) 
      ip-id-co        =
;**NBO not in EPIC-lite toolbox
        NBO(16) ; check byte-order 
        FORMAT(ip-id-seq-co, ip-id-rnd) 
;**130% ??
          ip-id-seq-co    =  LSB(4,3,70%) | LSB(6,8,15%) | 
                             LSB(8,8,15%) | IRREGULAR(16,30%) 
          ip-id-rnd       =  IRREGULAR(16,100%) 
;**compiler should read comments or what ?
        STATIC(100%) ; nbo flag 
      rf_flag         =  STACK-TO-CONTROL(1) 
      df_flag-co      =  STATIC(80%) | IRREGULAR(20%) 
      mf_flag         =  VALUE(1,0,100%) 
      offset          =  VALUE(13,0,100%) 
      ttl-co          =  STATIC(99%) | IRREGULAR(8,1%)  
      protocol        =  VALUE(8,6,100%)  
      ip_chksum       =  VALUE(16,0,100%) 
      src_address-co  =  STATIC(100%) 
      dst_address-co  =  STATIC(100%) 

;**TCP-co-header assumed same as TCP-header-co
  TCP-co-header   =
    source_port-co  =  STATIC(100%) 
    dest_port-co    =  STATIC(100%) 
;**seqno assumed to be seqno-co
;**get-seq-ack not used, expanded later for reference
    seqno-co        =  LSB(8,63,5%) | LSB(14,4096,80%) |  
                       LSB(20,16384,10%) | IRREGULAR(32,5%)  
;**ackno assumed to be ackno-co
;**get-seq-ack not used, expanded later for reference
    ackno-co        =  LSB(8,0,10%) | LSB(14,0,80%) |  
                       LSB(20,0,5%) | IRREGULAR(32,5%)  
    data_offset     =  STACK-TO-CONTTROL(4) 
    flags-co        =    
      reserved-co  =    
        get-rf    =    ROTATE(4,1) 
                       STACK-FROM-CONTROL(1) 
        FORMAT(reserved-unused, reserved-used) 
          reserved-unused =    VALUE(5,0,100%) 
          reserved-used   =
            reserved-flag   =    IRREGULAR(1,100%) 
            reserved-flag   =    IRREGULAR(1,100%) 
            reserved-flag   =    IRREGULAR(1,100%) 
            reserved-flag   =    IRREGULAR(1,100%) 
            reserved-flag   =    IRREGULAR(1,100%) 
            reserved-flag   =    IRREGULAR(1,100%) 
;**compiler should read comments or what ?
;**format selector in CO packet ??!!
        STATIC(100%) ; format selector 
      cwr        =  IRREGULAR(1,100%) 
      ece        =  IRREGULAR(1,100%) 
      urg        =  STACK-TO-CONTROL(1) 
;**ack assumed to be ack-co
;**ack STACK-TO-CONTROL not defined
      ack-co     =  VALUE(1,1,99.9%) | VALUE(1,0,0.1%) 
;++psh assumed to be psh-co
;**psh STACK-TO-CONTROL not defined
      psh-co     =  
        FORMAT(reg-psh-co, irreg-psh) 
;**108% ??
          reg-psh-co      =  STATIC(90%) | N(IRREGULAR(1,9%) | IRREGULAR(1,9%) 
          irreg-psh       =  IRREGULAR(1,100%) 
;**compiler should read comments or what ?
;**format selector in CO packet ??!!
        STATIC(100%) ; format selector 
      rst-syn-fin-co  =    no-flag(98%) | rst-only(1%) | fin-only(1%) 
        no-flag         =    VALUE(3,0x0,100%) 
        rst-only        =    VALUE(3,0x4,100%) 
        fin-only        =    VALUE(3,0x1,100%) 
;**syn-only defined, but not used
    window-co  =  STATIC(80%) | LSB(12,63,10%) | IRREGULAR(16,10%)  
    tcp_chksum =  IRREGULAR(16,100%)  
;**urg-ptr defined, but not used
    urg_ptr-co =  STATIC(99%) | IRREGULAR(16,1%)  

;**options not referenced in TCP-CO header, but included here
;**change in syntax, field_name = METHOD abandoned, field names in comments!!
;**experimental, need further discussion
  tcp-options-co = 
    ROTATE(3,1) ; get TCP data offset 
    LIST(4,1,32,-160,8, 
      U(OPTIONAL(tcp-sack-co)),
        tcp-sack-co = 
          VALUE(8,5,100%) ; type
          STACK-TO-CONTROL(8) ; length 
          LIST(8,1,8,-16,0, 
            OPTIONAL(sack-block-co), 
              sack-block-co = 
;**assumed sack-element-co = sack-element
                sack-element-co
                  sack-element-co = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    STATIC(50%) | LSB(16,32768,30%) | LSB(24,1048576,20%)
                sack-element-co 
                  sack-element-co = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    STATIC(50%) | LSB(16,32768,30%) | LSB(24,1048576,20%)
            OPTIONAL(sack-block-co), 
              sack-block-co = 
                sack-element-co
                  sack-element-co = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    STATIC(50%) | LSB(16,32768,30%) | LSB(24,1048576,20%)
                sack-element-co 
                  sack-element-co = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    STATIC(50%) | LSB(16,32768,30%) | LSB(24,1048576,20%)
            OPTIONAL(sack-block-co), 
              sack-block-co = 
                sack-element-co
                  sack-element-co = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    STATIC(50%) | LSB(16,32768,30%) | LSB(24,1048576,20%)
                sack-element-co 
                  sack-element-co = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    STATIC(50%) | LSB(16,32768,30%) | LSB(24,1048576,20%)
            OPTIONAL(sack-block-co))
              sack-block-co = 
                sack-element-co
                  sack-element-co = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    STATIC(50%) | LSB(16,32768,30%) | LSB(24,1048576,20%)
                sack-element-co 
                  sack-element-co = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    STATIC(50%) | LSB(16,32768,30%) | LSB(24,1048576,20%)
                  sack-element-co = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    STATIC(50%) | LSB(16,32768,30%) | LSB(24,1048576,20%)
            STATIC(90%) | IRREGULAR(8,10%) ; order 
            sack-block-presence = VALUE(1,1,100%)
                      VALUE(1,1,50%) | VALUE(1,0,50%)
                      VALUE(1,1,20%) | VALUE(1,0,80%)
                      VALUE(1,1,5%) | VALUE(1,0,95%)
      U(OPTIONAL(tcp-timestamp-co)),
          tcp-timestamp-co = 
            VALUE(8,8,100%)  ; type
            VALUE(8,10,100%) ; length
;**ts-entry assumed to be ts-entry-co
            ts-entry
              ts-entry-co = LSB(12,0,60%) | LSB(16,0,30%) |IRREGULAR(32,10%)
            ts-entry
              ts-entry-co = LSB(12,0,60%) | LSB(16,0,30%) |IRREGULAR(32,10%)
      U(OPTIONAL(tcp-mss)),
          tcp-mss = 
            VALUE(8,2,100%) ; type
            VALUE(8,4,100%) ; length
            IRREGULAR-PADDED(16,11,99%) | IRREGULAR(16,1%)
      U(OPTIONAL(tcp-end)), 
          tcp-end = VALUE(8,0,100%) ; type 
      U(OPTIONAL(tcp-wscale)), 
          tcp-wscale = 
            VALUE(8,3,100%) ; type
            VALUE(8,3,100%) ; length 
            IRREGULAR-PADDED(8,4,100%) ; scale
      U(OPTIONAL(sack-permitted)), 
          tcp-sack-permitted = 
            VALUE(8,4,100%) ; type
            VALUE(8,2,100%) ; length
      U(OPTIONAL(tcp-generic-co)), 
          tcp-generic-co = 
            STATIC(100%) ; type 
            STACK-TO-CONTROL(8) ; length
            UNCOMPRESSED(8,1,8,-16) ; value
      U(OPTIONAL(tcp-generic-co)), 
          tcp-generic-co = 
            STATIC(100%) ; type 
            STACK-TO-CONTROL(8) ; length
            UNCOMPRESSED(8,1,8,-16) ; value
      5,8,2,0,3,4) 
    STATIC(100%) ; option order 
    STATIC(95%) | IRREGULAR(8,5%) ; option presence

;**not defined, but self-explanatory :)
  skip-msn 

  CRC(3,80%) | CRC(7,20%) 


;**get-seq-ack not used, expanded here for reference
   get-seq-ack      =   
     ROTATE(2,1)
     STACK-FROM-CONTROL(2) ; cwr/ece
     ROTATE(4,1)
     STACK-FROM-CONTROL(2) ; ecn
     STACK-FROM-CONTROL(32) ; ack
     STACK-FROM-CONTROL(32) ; seq

;**seqno-and-ackno-co not used, expanded here for reference
   seqno-and-ackno-co = 
     FORMAT(bulk-data-co, bulk-ack-co, interactive-co)
       bulk-data-co     =    
         data-seqno-co    =    LSB(14,0,50%) | LSB(16,32768,30%) |LSB(20,65536,20%)
         data-ackno-co    =    STATIC(50%) | LSB(10,0,30%) | LSB(16,0,20%)
         ecn-co           =    
           FORMAT(no-ecn-co, use-ecn-co) 
             no-ecn-co        =    VALUE(2,0,100%)
                                   VALUE(2,0,100%)
             use-ecn-co       =    IRREGULAR(4,100%) 
       bulk-ack-co      =    
         ack-seqno-co     =    STATIC(50%) | LSB(10,0,30%) | LSB(16,0,20%)
         ack-ackno-co     =    LSB(14,0,50%) | LSB(16,0,30%) | LSB(20,0,20%) 
         ecn-co           =    
           FORMAT(no-ecn-co, use-ecn-co) 
             no-ecn-co        =    VALUE(2,0,100%)
                                   VALUE(2,0,100%)
             use-ecn-co       =    IRREGULAR(4,100%) 
       interactive-co   =    
         interact-seqno-co =   LSB(10,256,35%) | LSB(14,2048,50%) | LSB(18,4096,15%)
         interact-ackno-co =   LSB(10,0,35%) | LSB(14,0,50%) | LSB(18,0,15%) 
         ecn-co           =    
           FORMAT(no-ecn-co, use-ecn-co) 
             no-ecn-co        =    VALUE(2,0,100%)
                                   VALUE(2,0,100%)
             use-ecn-co       =    IRREGULAR(4,100%) 
     STATIC(100%) ; format selector



TCP-IP-IR       =    

;**IP checksum treated later anyway
;**not in current EPIC-lite toolbox
  INFERRED-IP-CHECKSUM(IPv4-ir-header)
    IPv4-ir-header  =  
      version         =  VALUE(4,4,100%) 
      header_len      =  VALUE(4,5,100%) 
      tos-dyn         =  IRREGULAR(6,100%) 
      ecn             =  STACK-TO-CONTROL(2) 
      length          =  INFERRED-SIZE(16,128) 
      ip-id-dyn       =  
;**NBO not in EPIC-lite toolbox
        NBO(16) ; check byte-order 
        FORMAT(ip-id-seq-dyn, ip-id-rnd)
          ip-id-seq-dyn  =  IRREGULAR(16,100%) 
          ip-id-rnd      =  IRREGULAR(16,100%) 
;**what is this meant for??
        IRREGULAR(16,100%) 
;**compiler should read comments or what ?
        IRREGULAR(1,100%) ; nbo flag 
      rf_flag         =  STACK-TO-CONTROL(1) 
      df-flag-dyn     =  IRREGULAR(1,100%) 
      mf_flag         =  VALUE(1,0,100%) 
      offset          =  VALUE(13,0,100%) 
      ttl-dyn         =  IRREGULAR(8,100%) 
      protocol        =  VALUE(8,6,100%)  
      ip_chksum       =  VALUE(16,0,100%) 
      src_address-ir  =  IRREGULAR(32,100%) 
      dst_address-ir  =  IRREGULAR(32,100%) 

;**TCP-ir-header assumed to be TCP-header IR
  TCP-header-ir   =  
    source_port-ir  =  IRREGULAR(16,100%) 
    dest_port-ir    =  IRREGULAR(16,100%) 
;**seqno assumed to be seqno-dyn
;**get-seq-ack not used, expanded later
    seqno-dyn       =  IRREGULAR(32,100%) 
;**ackno assumed to be ackno-dyn
;**get-seq-ack not used, expanded later
    ackno-dyn       =  IRREGULAR(32,100%) 
    data_offset     =  STACK-TO-CONTROL(4) 
    flags-dyn       =  
      reserved-dyn    =  
        get-rf          =  
          ROTATE(4,1) 
          STACK-FROM-CONTROL(1) 
        FORMAT(reserved-unused, reserved-used) 
          reserved-unused =    VALUE(5,0,100%) 
          reserved-used   =
            reserved-flag   =    IRREGULAR(1,100%) 
            reserved-flag   =    IRREGULAR(1,100%) 
            reserved-flag   =    IRREGULAR(1,100%) 
            reserved-flag   =    IRREGULAR(1,100%) 
            reserved-flag   =    IRREGULAR(1,100%) 
            reserved-flag   =    IRREGULAR(1,100%) 
;**compiler should read comments or what ?
        IRREGULAR(1,100%) ; format selector 
;**what is this??, possibly cwr, ece
      IRREGULAR(2,100%) 
      urg             =  STACK-TO-CONTROL(1) 
;**what is this??, possibly ack
      IRREGULAR(1,100%) 
      psh-dyn         =  
        FORMAT(reg-psh-dyn, irreg-psh) 
          reg-psh-dyn     =  IRREGULAR(1,100%) 
          irreg-psh       =  IRREGULAR(1,100%) 
        IRREGULAR(1,100%) ; format selector 
      rst-syn-fin-dyn =  IRREGULAR(3,100%) 
    window-dyn      =  IRREGULAR(16,100%) 
    tcp_chksum      =  IRREGULAR(16,100%)  
    urg_ptr-dyn     =  IRREGULAR(16,100%)  

;**options not referenced in TCP-IR header, but included here
;**tcp-options IR not defined, tcp-options dyn used instead
;**change in syntax, field_name = METHOD abandoned, field names in comments!!
;**experimental, need further discussion
  tcp-options-dyn = 
    ROTATE(3,1) ; get TCP data offset
    LIST(4,1,32,-160,8, 
      U(OPTIONAL(tcp-sack-dyn)),
        tcp-sack-dyn = 
          VALUE(8,5,100%) ; type
          STACK-TO-CONTROL(8) ; length
          LIST(8,1,8,-16,0, 
            OPTIONAL(sack-block-dyn),
              sack-block-dyn = 
                sack-element-dyn
                  sack-element-dyn = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    IRREGULAR(32,100%)
                sack-element-dyn
                  sack-element-dyn = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    IRREGULAR(32,100%)
            OPTIONAL(sack-block-dyn),
              sack-block-dyn = 
                sack-element-dyn
                  sack-element-dyn = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    IRREGULAR(32,100%)
                sack-element-dyn
                  sack-element-dyn = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    IRREGULAR(32,100%)
            OPTIONAL(sack-block-dyn),
              sack-block-dyn = 
                sack-element-dyn
                  sack-element-dyn = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    IRREGULAR(32,100%)
                sack-element-dyn
                  sack-element-dyn = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    IRREGULAR(32,100%)
            OPTIONAL(sack-block-dyn),
              sack-block-dyn = 
                sack-element-dyn
                  sack-element-dyn = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    IRREGULAR(32,100%)
                sack-element-dyn
                  sack-element-dyn = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    IRREGULAR(32,100%)
;**should it be 100%
          IRREGULAR(8,10%) ; order
               sack-block-presence-dyn  = 
                 IRREGULAR(1,100%)
                 IRREGULAR(1,100%)
                 IRREGULAR(1,100%)
                 IRREGULAR(1,100%)
      U(OPTIONAL(tcp-timestamp-dyn)), 
;** tcp-timestamp-dyn not defined, possibly uses ts-entry-dyn
        tcp-timestamp-dyn = 
      U(OPTIONAL(tcp-mss)),
        tcp-mss = 
          VALUE(8,2,100%) ; type
          VALUE(8,4,100%) ; length
          IRREGULAR-PADDED(16,11,99%) | IRREGULAR(16,1%)
      U(OPTIONAL(tcp-end)), 
        tcp-end = VALUE(8,0,100%) ; type 
      U(OPTIONAL(tcp-wscale)), 
        tcp-wscale = VALUE(8,3,100%) ; type
        VALUE(8,3,100%) ; length 
        IRREGULAR-PADDED(8,4,100%) ; scale
      U(OPTIONAL(sack-permitted)), 
        tcp-sack-permitted = 
          VALUE(8,4,100%) ; type
          VALUE(8,2,100%) ; length
      U(OPTIONAL(tcp-generic-dyn)), 
        tcp-generic-dyn = 
          IRREGULAR(8,100%) ; type
          STACK-TO-CONTROL(8) ; length 
          UNCOMPRESSED(8,1,8,-16) ; value
      U(OPTIONAL(tcp-generic-dyn)), 
        tcp-generic-dyn = 
          IRREGULAR(8,100%) ; type
          STACK-TO-CONTROL(8) ; length 
          UNCOMPRESSED(8,1,8,-16) ; value
      5,8,2,0,3,4) 
    IRREGULAR(24,100%) ; option order 
    IRREGULAR(8,100%) ; option presence 

  msn-ir          =  MSN-IRREGULAR(16,10%) 

  CRC(8,100%) 



TCP-IP-DYN      =    

;**IP checksum treated later anyway
;**not in current EPIC-lite toolbox
    IPv4-dyn-header =    
      version         =  VALUE(4,4,100%) 
      header_len      =  VALUE(4,5,100%)
      tos-dyn         =  IRREGULAR(6,100%) 
      ecn             =  STACK-TO-CONTROL(2) 
      length          =  INFERRED-SIZE(16,128)
      ip-id-dyn       =  
;**NBO not in EPIC-lite toolbox
        NBO(16) ; check byte-order 
        FORMAT(ip-id-seq-dyn, ip-id-rnd)
          ip-id-seq-dyn  =  IRREGULAR(16,100%) 
          ip-id-rnd      =  IRREGULAR(16,100%) 
;**what is this meant for??
        IRREGULAR(16,100%) 
;**compiler should read comments or what ?
        IRREGULAR(1,100%) ; nbo flag 
      rf_flag         =  STACK-TO-CONTROL(1)
      df_flag-dyn     =  IRREGULAR(1,100%)
      mf_flag         =  VALUE(1,0,100%)
      offset          =  VALUE(13,0,100%)   
      ttl-dyn         =  IRREGULAR(8,100%)   
      protocol        =  VALUE(8,6,100%)  
      ip_chksum       =  VALUE(16,0,100%) 
      src_address-co  =  STATIC(100%)
      dst_address-co  =  STATIC(100%) 

;**assumed TCP-dyn-header = TCP-header-dyn
  TCP-dyn-header  =
    source_port-co  = STATIC(100%) 
    dest_port-co    = STATIC(100%) 
;**seqno assumed to be seqno-dyn
;**get-seq-ack not used
    seqno-dyn       =  IRREGULAR(32,100%) 
;**ackno assumed to be ackno-dyn
;**get-seq-ack not used
    ackno-dyn       =  IRREGULAR(32,100%) 
    data_offset     =  STACK-TO-CONTROL(4) 
    flags-dyn       =  
      reserved-dyn    =  
        get-rf          =  
          ROTATE(4,1) 
          STACK-FROM-CONTROL(1) 
        FORMAT(reserved-unused, reserved-used) 
          reserved-unused =    VALUE(5,0,100%) 
          reserved-used   =
            reserved-flag   =    IRREGULAR(1,100%) 
            reserved-flag   =    IRREGULAR(1,100%) 
            reserved-flag   =    IRREGULAR(1,100%) 
            reserved-flag   =    IRREGULAR(1,100%) 
            reserved-flag   =    IRREGULAR(1,100%) 
            reserved-flag   =    IRREGULAR(1,100%) 
;**compiler should read comments or what ?
        IRREGULAR(1,100%) ; format selector 
;**what is this?? possibly cwr, ece 
      IRREGULAR(2,100%) 
      urg             =  STACK-TO-CONTROL(1) 
;**what is this?? possibly ack
      IRREGULAR(1,100%) 
      psh-dyn         =  
        FORMAT(reg-psh-dyn, irreg-psh) 
          reg-psh-dyn     =  IRREGULAR(1,100%) 
          irreg-psh       =  IRREGULAR(1,100%) 
        IRREGULAR(1,100%) ; format selector 
      rst-syn-fin-dyn =  IRREGULAR(3,100%) 
    window-dyn      =  IRREGULAR(16,100%) 
    tcp_chksum      =  IRREGULAR(16,100%)  
    urg_ptr-dyn     =  IRREGULAR(16,100%)  

;**options not referenced in TCP-DYN header, but included here
;**change in syntax, field_name = METHOD abandoned, field names in comments!!
;**experimental, need further discussion
  tcp-options-dyn = 
    ROTATE(3,1) ; get TCP data offset
    LIST(4,1,32,-160,8, 
      U(OPTIONAL(tcp-sack-dyn)),
        tcp-sack-dyn = 
          VALUE(8,5,100%) ; type
          STACK-TO-CONTROL(8) ; length
          LIST(8,1,8,-16,0, 
            OPTIONAL(sack-block-dyn),
              sack-block-dyn = 
                sack-element-dyn
                  sack-element-dyn = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    IRREGULAR(32,100%)
                sack-element-dyn
                  sack-element-dyn = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    IRREGULAR(32,100%)
            OPTIONAL(sack-block-dyn),
              sack-block-dyn = 
                sack-element-dyn
                  sack-element-dyn = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    IRREGULAR(32,100%)
                sack-element-dyn
                  sack-element-dyn = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    IRREGULAR(32,100%)
            OPTIONAL(sack-block-dyn),
              sack-block-dyn = 
                sack-element-dyn
                  sack-element-dyn = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    IRREGULAR(32,100%)
                sack-element-dyn
                  sack-element-dyn = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    IRREGULAR(32,100%)
            OPTIONAL(sack-block-dyn),
              sack-block-dyn = 
                sack-element-dyn
                  sack-element-dyn = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    IRREGULAR(32,100%)
                sack-element-dyn
                  sack-element-dyn = 
                    INFERRED-OFFSET-LIST(32) ; offset from base
                    STACK-TO-CONTROL(32) ; preserve new base
                    IRREGULAR(32,100%)
;**should it be 100%
          IRREGULAR(8,10%) ; order
               sack-block-presence-dyn  = 
                 IRREGULAR(1,100%)
                 IRREGULAR(1,100%)
                 IRREGULAR(1,100%)
                 IRREGULAR(1,100%)
      U(OPTIONAL(tcp-timestamp-dyn)), 
;** tcp-timestamp-dyn not defined, possibly uses ts-entry-dyn
        tcp-timestamp-dyn = 
      U(OPTIONAL(tcp-mss)),
        tcp-mss = 
          VALUE(8,2,100%) ; type
          VALUE(8,4,100%) ; length
          IRREGULAR-PADDED(16,11,99%) | IRREGULAR(16,1%)
      U(OPTIONAL(tcp-end)), 
        tcp-end = VALUE(8,0,100%) ; type 
      U(OPTIONAL(tcp-wscale)), 
        tcp-wscale = VALUE(8,3,100%) ; type
        VALUE(8,3,100%) ; length 
        IRREGULAR-PADDED(8,4,100%) ; scale
      U(OPTIONAL(sack-permitted)), 
        tcp-sack-permitted = 
          VALUE(8,4,100%) ; type
          VALUE(8,2,100%) ; length
      U(OPTIONAL(tcp-generic-dyn)), 
        tcp-generic-dyn = 
          IRREGULAR(8,100%) ; type
          STACK-TO-CONTROL(8) ; length 
          UNCOMPRESSED(8,1,8,-16) ; value
      U(OPTIONAL(tcp-generic-dyn)), 
        tcp-generic-dyn = 
          IRREGULAR(8,100%) ; type
          STACK-TO-CONTROL(8) ; length 
          UNCOMPRESSED(8,1,8,-16) ; value
      5,8,2,0,3,4) 
    IRREGULAR(24,100%) ; option order 
    IRREGULAR(8,100%) ; option presence 

  msn-dyn        =  MSN-LSB(3,0,90%) | MSN-LSB(7,0,9%) | MSN-IRREGULAR(16,1%) 

  CRC(8,100%) 

;**seqno-and-ackno-dyn expanded here for reference
   seqno-and-ackno-dyn = 
     FORMAT(bulk-data-dyn, bulk-ack-dyn, interactive-dyn)
       bulk-data-dyn    =
         seqno-dyn        =    IRREGULAR(32,100%)
         ackno-dyn        =    IRREGULAR(32,100%)
         ecn-dyn          =
           FORMAT(no-ecn-dyn, use-ecn-dyn)
             no-ecn-dyn       =
               VALUE(2,0,100%) 
               VALUE(2,0,100%) 
             use-ecn-dyn      =
               IRREGULAR(2,100%) 
               IRREGULAR(2,100%) 
           IRREGULAR(1,100%) ; format selector 
       bulk-ack-dyn     =
         seqno-dyn        =    IRREGULAR(32,100%)
         ackno-dyn        =    IRREGULAR(32,100%)
         ecn-dyn          =
           FORMAT(no-ecn-dyn, use-ecn-dyn)
             no-ecn-dyn       =
               VALUE(2,0,100%) 
               VALUE(2,0,100%) 
             use-ecn-dyn      =
               IRREGULAR(2,100%) 
               IRREGULAR(2,100%) 
           IRREGULAR(1,100%) ; format selector 
       interactive-dyn  =
         seqno-dyn        =    IRREGULAR(32,100%)
         ackno-dyn        =    IRREGULAR(32,100%)
         ecn-dyn          =
           FORMAT(no-ecn-dyn, use-ecn-dyn)
             no-ecn-dyn       =
               VALUE(2,0,100%) 
               VALUE(2,0,100%) 
             use-ecn-dyn      =
               IRREGULAR(2,100%) 
               IRREGULAR(2,100%) 
           IRREGULAR(1,100%) ; format selector 
    IRREGULAR(2,100%) ; format-selector

--------------060302020000080400000603--


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


From rohc-admin@ietf.org  Tue Feb 26 16:56: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 QAA22977
	for <rohc-archive@odin.ietf.org>; Tue, 26 Feb 2002 16:56:07 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA23057;
	Tue, 26 Feb 2002 16:47:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA23028
	for <rohc@optimus.ietf.org>; Tue, 26 Feb 2002 16:47:42 -0500 (EST)
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 QAA22822
	for <rohc@ietf.org>; Tue, 26 Feb 2002 16:47:36 -0500 (EST)
Received: from cabo3 (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with SMTP id g1QLlYC19800;
	Tue, 26 Feb 2002 22:47:34 +0100 (MET)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Cc: <zhigang.c.liu@nokia.com>, <rohc@ietf.org>
Subject: RE: [rohc] RE: Default decompression algorithms
Date: Tue, 26 Feb 2002 22:47:32 +0100
Message-ID: <NFBBJFHGMCFINEMHAMBGEEIHHHAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-reply-to: <3C7BBD5F.A44B6916@ericsson.com>
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

Miguel,

thanks for the detailed explanation.

> You asked how many algorithms are going to be in the cache of a
> typical decompressor, and that question is related to how many users
> a proxy can support simultaneously, and how many different algorithms.
> In other words, it is implementation dependent, and the answer to the
> question does not have an impact on the standardization in Rohc.

Well, the technical parameters in the expected operating range typically do
have an influence on standardization, in particular for a standard the only
purpose of which is optimization.

BTW, I don't believe there is an appreciable technical limit to the number
of algorithms a decompressor can support, apart from the overall limit in
state capacity.
So the more interesting question is, how many algorithms are likely to be in
actual use at any point in time.
Counting all generations of equipment out there, of course, multiplied by
the number of manufacturers.
It may look nice three weeks from now...

> The cost of supplying the information: I don't have a strong opinion
> on how this can be done, but I will refer to examples that are working
> today in other protocols. For instance, RTP decided to use a profile
> for Audio/Video codecs (RFC 1890). Known codecs are assigned a Payload
> Type in RTP. So Payload Type 0 means PCM u-law codec, Payload 8 means
> PCM A-law codec.

It seemed like a good idea at the time, in 1996.
AVT has long since stopped to assign fixed payload types -- there are just
way too many of them for a small field.
(And it's way more expensive to invent a new payload type than a new
decompressor, I might surmise.)

> In SigComp, we could take the same approach, in a way that we define
> a standard way to refer to known algorithms. The decompressor, in
> the SigComp Capabilities Announcements would indicate the list of
> algorithms that are already uploaded (in a similar way of how SDP,
> RFC 2327 negotiates codecs).

Would you trust UE A to upload algorithm X for UE B?

I don't think the dynamic version of this can be made to work without secure
state identifiers.
These need to be at least 6 bytes (probably more; 12 is secure, we are still
investigating whether less can work).
Let's say 8 bytes, times maybe 20 algorithms out there.  Not a big win.
Oh, and you *still* need to upload any user dictionaries.

What you could do for a static solution is to actually tightly manage a
small number space (e.g., 16-bit numbers), by registering algorithms.
Now the problem is that you have to wait for the register updates to
percolate to both UE and fixed network equipment before you can take
advantage of them.

The reason I insist on discussing this seemingly small issue is that I
believe we can eliminate a lot of mechanism by just not doing it.

Or to put it another way, I have the impression we have a psychological
problem ("we can't exchange those bytes all the time, so let's do something
about it") instead of a technical one.  Of course, given that the UDVM
approach is new, this is understandable.  However, we are talking about
probably fewer bytes than the typical HTTP headers for a single web page hit
here.  Once, for registration.

Of course, my analysis may be completely broken.
If I'm right, the only remaining issue for me is whether not having an
ostensible solution for this alleged problem is going to hinder acceptance
of the UDVM.
This is a level 9 decision, not a technical one.

Gruesse, Carsten


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


From rohc-admin@ietf.org  Wed Feb 27 03:06: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 DAA13396
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 03:06:54 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA00911;
	Wed, 27 Feb 2002 03:00:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA00829
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 03:00:49 -0500 (EST)
Received: from h3gshmsw1.hutchison3g.com (mail.hutchison3g.com [63.137.144.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13272
	for <rohc@ietf.org>; Wed, 27 Feb 2002 03:00:45 -0500 (EST)
Received: from andromeda.h3guk.com (unverified) by h3gshmsw1.hutchison3g.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5953045f0e0af80e8271c@h3gshmsw1.hutchison3g.com> for <rohc@ietf.org>;
 Wed, 27 Feb 2002 08:01:24 +0000
Received: by andromeda.h3guk.com with Internet Mail Service (5.5.2653.19)
	id <FN9HTHTV>; Wed, 27 Feb 2002 08:01:30 -0000
Message-ID: <F3035F172B472247AED58C867616D0AB384799@RETICULUM.h3guk.com>
From: Kevan Hobbis <Kevan.Hobbis@hutchison3g.com>
To: rohc@ietf.org
Subject: [rohc] Default Compression Algorithms
Date: Wed, 27 Feb 2002 08:01:05 -0000
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

Folks

I have been following this conversation and am not clear what the conclusion
was, but as one of the people who would like to see an ability to use a
default algorithm then I would like ask the following questions

1. An organisation could make their own decision on what the default
algorithm should be. It is not necessary to define it as part of sigcomp -
in fact my understanding is that sigcomp has no compression algorithms
defined within it anyway ?

2. Is there a compression algorithm that is not encumbered with IPR that
could be used as default ? Albeit that it might be simple and not as
effective as others.

3. 3GPP operators want to reduce the on-air traffic, and so acceptance of a
default algorithm would aid this, specifically if it required no negotiation
signalling i.e. a compressor can send a message compressed with the default
algorithm and indicate this in a header (or maybe if no indication is
received then the default is assumed) - the decompressor can then decompress
using the default. No negotiation or capability exchange is required. This
is how it would be a win for the radio interface. I got the impression that
this is possible within sigcomp, but it is not clear to me how it is done ?

4. If this is possible with the current specification then it is not clear -
at least not to me. In this respect, I think I saw a suggestion for a draft
that was an implementers guide that would explain such operation. This would
be very useful to me to aid my understanding, and wonder if it is something
that has merits for other reasons as well as default algorithm support ?

Thanks

Kevan Hobbis




_______________________________________________________________

If this email isn't for you then we'd be grateful if you could let our
helpdesk know there's been a mistake by putting 'received in 
error' in the subject box and sending it to helpdesk@hutchison3g.com. 
If it isn't for you, we're sure you'll understand that you're not 
allowed to copy, disclose or distribute any of its contents.  
This email is private and confidential and may also be privileged,
so if you shouldn't have received it, we'd be grateful if you could delete it.
Thanks.
________________________________________________________________


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


From rohc-admin@ietf.org  Wed Feb 27 03:42: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 DAA13884
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 03:42:15 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA03085;
	Wed, 27 Feb 2002 03:39:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA03060
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 03:39:25 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13836
	for <rohc@ietf.org>; Wed, 27 Feb 2002 03:39:22 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g1R8dLB29718;
	Wed, 27 Feb 2002 09:39:21 +0100 (MET)
Received: from ericsson.com (3NJPI0013L1IJOG.lmf.ericsson.se [131.160.30.42])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g1R8dLmK003980;
	Wed, 27 Feb 2002 10:39:21 +0200 (EET)
Message-ID: <3C7C9B74.D5049D3F@ericsson.com>
Date: Wed, 27 Feb 2002 10:40:20 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Organization: OY LM Ericsson AB
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: es,en
MIME-Version: 1.0
To: "Dr. Carsten Bormann" <cabo@tzi.org>
CC: rohc@ietf.org
Subject: Re: [rohc] Making SigComp recognizable
References: <NFBBJFHGMCFINEMHAMBGCEIBHHAA.cabo@tzi.org>
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

Hi Caster:

So, if I understand correctly, the discussion here is about two possibilities:

a) SigComp is listening to the same port number than the application (e.g., 5060 for SIP)
b) SigComp is listening to a different port number than the application.

So far, my understanding is that SigComp is a shim layer that is reused by 
many applications that are running on the same host. As such, the SigComp
layer software is used by SIP, HTTP, RTSP, etc.

Therefore, I see that if the SigComp layer should not be aware of the 
parsing rules of any protocol running on top. I wouldn't like to see
SigComp parsing message to distinguish whether they are SIP, HTTP or RTSP.
And I would like to use a shim layer that I can instantiate per application.
That's why my assumption was always that SIP/SigComp will be listening to
a determined port number, HTTP/SigComp will be listening to another, and so on.
Those port numbers are different than the respective non compressed applications.

Further more: SigComp-04 specifies a SigComp negotiation mechanism and UDVM
upload. These are SigComp related mechanisms that have nothing to do with 
the compressed protocol carried in the payload.

Option a above is a very bad design choice. Multiplexing two different
protocols into the same port number, just because it happens that one of
the protocols carries payload of the other, it is IMHO, a bad design
decision. It implicitly requires that the "shim" layer is heavily integrated
into the application. This prevents me to design a shim layer that is reusable
by many application protocols.

As an example, somebody could argue that why don't we send SIP messages to
port number 25 (SMTP). They are all both text messages, so, why do we need
port numbers to differentiate the protocol???

I would like to have a deterministic way to trace messages in a network,
and see by the destination port number whether the message is compressed
or not, and whether the message is syntactically correct or not.

My suggestion, humble though, is to keep the assumption that SigComp is a 
protocol by itself, and it has to be identified by a port number, different
from the port number of the application that is carried within SigComp 
(option b). Note that there is not need to standardize a well know port
number for SigComp. We can rely on NAPTR/SRV in DNS to do this job.

/Miguel


"Dr. Carsten Bormann" wrote:
> 
> In a phone conversation today, it occurred to us that it would be a good
> idea to make SigComp packets clearly distinguishable from uncompressed
> packets.
> For SIP, this is easy, as all methods and reply codes are ASCII, so setting
> the MSB in the first byte of all packets would suffice.
> However, it's probably a good idea not to trigger the link-layer RTP ROHC
> heuristics, which tend to look for 10xxxxxx in the first byte (RTP V=2) of
> UDP packets.
> More generally, I think we want to cater for general UTF-8-based signalling
> protocols. Looking at RFC2044, we have:
> 
>    UCS-4 range (hex.)           UTF-8 octet sequence (binary)
>    0000 0000-0000 007F   0xxxxxxx
>    0000 0080-0000 07FF   110xxxxx 10xxxxxx
>    0000 0800-0000 FFFF   1110xxxx 10xxxxxx 10xxxxxx
> 
>    0001 0000-001F FFFF   11110xxx 10xxxxxx 10xxxxxx 10xxxxxx
>    0020 0000-03FF FFFF   111110xx 10xxxxxx 10xxxxxx 10xxxxxx 10xxxxxx
>    0400 0000-7FFF FFFF   1111110x 10xxxxxx ... 10xxxxxx
> 
> Now, since RFC2044 (October 1996), Unicode has been decided to stop at 0010
> FFFF, so the code combinations
> 
>    0020 0000-03FF FFFF   111110xx 10xxxxxx 10xxxxxx 10xxxxxx 10xxxxxx
>    0400 0000-7FFF FFFF   1111110x 10xxxxxx ... 10xxxxxx
> 
> never can appear in real UTF-8.
> 
> Leaping to a conclusion, it seems a SigComp/UDP packet should start with
> 
>         11111xxx
> 
> Sigcomp-04 uses 0xFF as an escape character, so xxx=111 should probably also
> be avoided.
> Alternatively, we could simply define a single byte distinguisher for UDP
> and start all TCP streams with the escape sequence (and not use the UDP
> distinguisher here).
> 
> Any other things we should avoid?  General comments on the whole approach?
> (I just wish UDP had a protocol field.)
> 
> Gruesse, Carsten
> 
> PS.: Anyone for defining an RFC2246 (TLS) CompressionMethod value for
> SigComp?
> Should be fun, and would save the 0xFFFFs.
> Can't even find an IANA registry for TLS, though.
> 
> PPS.: RFC2817 section 1 (motivation) is interesting reading.
> Has anyone implemented that spec?
> Could be done for SIP, too.
> 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc

-- 
Miguel-Angel Garcia                     Oy LM Ericsson AB
                                        Jorvas, Finland
mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 5140002

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


From rohc-admin@ietf.org  Wed Feb 27 03:58: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 DAA14105
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 03:58:44 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA03863;
	Wed, 27 Feb 2002 03:56:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA03830
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 03:56:37 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14068
	for <rohc@ietf.org>; Wed, 27 Feb 2002 03:56:33 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g1R8uVB11078;
	Wed, 27 Feb 2002 09:56:31 +0100 (MET)
Received: from ericsson.com (3NJPI0013L1IJOG.lmf.ericsson.se [131.160.30.42])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g1R8uVmK005017;
	Wed, 27 Feb 2002 10:56:31 +0200 (EET)
Message-ID: <3C7C9F7A.3B9EC769@ericsson.com>
Date: Wed, 27 Feb 2002 10:57:30 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Organization: OY LM Ericsson AB
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: es,en
MIME-Version: 1.0
To: "Dr. Carsten Bormann" <cabo@tzi.org>
CC: zhigang.c.liu@nokia.com, rohc@ietf.org
Subject: Re: [rohc] RE: Default decompression algorithms
References: <NFBBJFHGMCFINEMHAMBGEEIHHHAA.cabo@tzi.org>
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

Hi Caster:

See my comments inline.

"Dr. Carsten Bormann" wrote:
> 
> Miguel,
> 
> thanks for the detailed explanation.
> 
> > You asked how many algorithms are going to be in the cache of a
> > typical decompressor, and that question is related to how many users
> > a proxy can support simultaneously, and how many different algorithms.
> > In other words, it is implementation dependent, and the answer to the
> > question does not have an impact on the standardization in Rohc.
> 
> Well, the technical parameters in the expected operating range typically do
> have an influence on standardization, in particular for a standard the only
> purpose of which is optimization.

I believe we are speaking about the Capabilities Announcement message in
SigComp. This message, as you said, will carry the range of parameters
that will constrain the algorithm selection at the compressor. What I was
suggesting is that the decompressor already includes a list of algorithms
that, in case one of the them is chosen by the compressor, does not need
to be uploaded to the decompressor.

> 
> BTW, I don't believe there is an appreciable technical limit to the number
> of algorithms a decompressor can support, apart from the overall limit in
> state capacity.

Agree.

> So the more interesting question is, how many algorithms are likely to be in
> actual use at any point in time.
> Counting all generations of equipment out there, of course, multiplied by
> the number of manufacturers.
> It may look nice three weeks from now...

Yes, but that does not impact standardization. Whether the decompressor 
contains already the code for 1 or for 1,000 algorithms is not affecting
the performance nor the standard. In a similar example, when my SIP 
terminal publishes support for certain codecs, I may support a big
number of codecs, whereas another terminal not. So what?
 

> 
> > The cost of supplying the information: I don't have a strong opinion
> > on how this can be done, but I will refer to examples that are working
> > today in other protocols. For instance, RTP decided to use a profile
> > for Audio/Video codecs (RFC 1890). Known codecs are assigned a Payload
> > Type in RTP. So Payload Type 0 means PCM u-law codec, Payload 8 means
> > PCM A-law codec.
> 
> It seemed like a good idea at the time, in 1996.
> AVT has long since stopped to assign fixed payload types -- there are just
> way too many of them for a small field.
> (And it's way more expensive to invent a new payload type than a new
> decompressor, I might surmise.)

Certainly static payload types are not assigned nor recommended to use.
However, dynamic payload types are. The point here in the comparison
with SDP was that, there should be a mechanism whereby the decompressor
informs the compressor about already uploaded algorithms. Whether the 
actual mechanism includes static or dynamic payload types, I don't care.
The important thing is to fulfill the requirement to avoid unnecessary
air interface traffic. 

One way to fulfill the requirement is to define a similar mechanism
as in RTP, even with dynamic payload types if you want. 

But in order to progress this, first we need to understand whether the
requirement is reasonable or not. If it is, we can start the discussion
on how to solve the problem.


> 
> > In SigComp, we could take the same approach, in a way that we define
> > a standard way to refer to known algorithms. The decompressor, in
> > the SigComp Capabilities Announcements would indicate the list of
> > algorithms that are already uploaded (in a similar way of how SDP,
> > RFC 2327 negotiates codecs).
> 
> Would you trust UE A to upload algorithm X for UE B?

Aren't we doing it now??? Don't we have a UDVM upload whereby an endpoint
uploads the algorithm X to another endpoint?

 
> I don't think the dynamic version of this can be made to work without secure
> state identifiers.
> These need to be at least 6 bytes (probably more; 12 is secure, we are still
> investigating whether less can work).
> Let's say 8 bytes, times maybe 20 algorithms out there.  Not a big win.
> Oh, and you *still* need to upload any user dictionaries.

Like I said before. Do we agree on the requirement? If Yes, we can discuss
technical proposals. If Not, we should stop the discussion.

If the requirement is agreed, my suggestion may not be the best one. I don't
have any problem with that. If you think it is not agreeable, let's look 
for other solutions.

> What you could do for a static solution is to actually tightly manage a
> small number space (e.g., 16-bit numbers), by registering algorithms.
> Now the problem is that you have to wait for the register updates to
> percolate to both UE and fixed network equipment before you can take
> advantage of them.

Agree.

> The reason I insist on discussing this seemingly small issue is that I
> believe we can eliminate a lot of mechanism by just not doing it.

So you don't honor the requirement? Then, I doubt SigComp can ever be
used in real life.
 
> Or to put it another way, I have the impression we have a psychological
> problem ("we can't exchange those bytes all the time, so let's do something
> about it") instead of a technical one.  Of course, given that the UDVM
> approach is new, this is understandable.  However, we are talking about
> probably fewer bytes than the typical HTTP headers for a single web page hit
> here.  Once, for registration.
> 
> Of course, my analysis may be completely broken.
> If I'm right, the only remaining issue for me is whether not having an
> ostensible solution for this alleged problem is going to hinder acceptance
> of the UDVM.
> This is a level 9 decision, not a technical one.

Well, it is not a level 9 decision. There are several organizations waiting
for the SigComp to be finalized and ready to use it (3GPP being one of them).
We need to understand the requirements and honor them, otherwise we may 
take the risk to deliver something that the customer does not want. That is
not a level 9 decision.

/Miguel

> 
> Gruesse, Carsten

-- 
Miguel-Angel Garcia                     Oy LM Ericsson AB
                                        Jorvas, Finland
mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 5140002

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


From rohc-admin@ietf.org  Wed Feb 27 05:20: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 FAA15639
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 05:20:14 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA08289;
	Wed, 27 Feb 2002 05:15:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA08262
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 05:15:40 -0500 (EST)
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 FAA15552
	for <rohc@ietf.org>; Wed, 27 Feb 2002 05:15:31 -0500 (EST)
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <1XV808KX>; Wed, 27 Feb 2002 10:07:24 -0000
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 1S9WNT45; Wed, 27 Feb 2002 10:07:13 -0000
From: "West, Mark (ITN)" <mark.a.west@roke.co.uk>
To: Julije Ozegovic <julije@fesb.hr>
Cc: rohc <rohc@ietf.org>
Message-ID: <3C7CAFD1.9060801@roke.co.uk>
Date: Wed, 27 Feb 2002 10:07:13 +0000
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
Subject: Re: [rohc] TCP/IP EPIC profile
References: <3C7BF6E0.9070307@fesb.hr>
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 Julije,

Some brief comments inline...

Cheers,

Mark.


> 
> The purpose of this posting is to point out the complexity of whole 
> thing, regarding the fact that almost every line of profile ends up with 
> (at least) one data structure in end user application.


Yes, it is quite complex.  So is RFC 3095 ;-)
I would agree that it is more 'dense' than RFC 3095, for example, as 
most of the information is packed into the profile.

Certainly every field (or meta-field) requires a data-structure.  Again, 
I'm not sure how this is different from any other header compression scheme?

> 
> The questions are:
>    do we really want this?


I won't answer this one -- I guess you could say I'm biased!


>    do we really need this?


That depends what you want.  Don't forget that the profile contains 
sufficient information to compress TCP/IP.  Given that, I would say it 
is quite compact.
Or, rather, if you don't have the information in this structure then, 
*yes*, you *absolutely* need to capture it in some way.

(I should point out that it isn't complicated enough yet ;-) as we still 
need to add the IPv6/extension header handling...)


>    is it worth the effort?


Again, that's a judgement call.  Also, don't forget that you can 
trade-off the effort against the efficiency.

And I'm not quite sure what you are referring to by 'effort'.  It's hard 
to write the profile, I'm not going to deny that.  But a lot of this is 
about understanding how the protocol works and should be compressed. 
Then you have to work out how to express this in an EPIC profile.  It's 
clear that, for example, it would be helpful to have more comments in 
the profile.  But it's not actually that complex.

Also (given the set of encoding methods defined in the EPIC(-lite) 
framework, there doesn't seem to be any more effort involved in using a 
'complex' profile over a 'simple' one.  The basic structure of the 
processing is exactly the same.

If you don't care too much about efficiency and only want to write a 
simple profile, then you can!


>    is it applicable to target machine (GSM)?


I haven't compared the size of our RFC 3095 implementation with our EPIC 
implementation recently, but neither of them are 'trivial' pieces of 
code!  Also, I think we're looking at this more for 2.5G / 3G (or, 
indeed, other arbitrary wireless links) than GSM .

Also, staying with the 'write-a-new-chunk-of-code-for-every-profile' 
approach is likely to add as least as much as the data for an EPIC profile.


>    do we really need (48+2)*60=3000 formats?


I don't know!  I think this is a matter for experimentation and 
selection.  The number of different format sets and packets per format 
set is clearly important, but it's hard to have a final view on this at 
the moment.  However, formats can (and should) be stored efficiently. 
3000 formats is a big number.  But it's not a lot of memory.


> 
> Besides this, comments about inconsistencies of the profile are listed 
> inline.


Ok, I'll reply to these later when I've had a chance to go through them


> 
> We also want to raise discussion about usage of FORMAT method.
> 


Ok!


> The questions are:
> 
>    - what about difference in FORMAT structure
>      between CO and IR/DYN packets,
>      shouldn't they be the same (by EPIC draft)?
> 


I'm not sure that I understand the question.

The intent (unless I've really messed up the profile!) is that a FORMAT 
encoding occurs at the same point in the profile for each of CO, IR, and 
IR-DYN.  This is, of course, important as the profile needs to have a 
consistent structure.
Is that what you mean?


>    - what about usage of IRREGULAR method in all sets
>      (except last one where it should be used),
>      this way first set will always be selected
> 


Well, if you read the pseudo-code you will see that the FORMAT encoding 
uses the form 'choose' to pick the format set.  This is 'defined' as an 
implementation dependent selection process -- it can use any criteria 
you want.

There is no rule that says that, when using FORMAT, each format set 
should be an exact match for only one case.  The important point here is 
that if encoding succeeds, then the compressed packet can be 
tranparently decompressed.  This is a critical requirement.  If there 
are multiple possible encodings that can fulfill this, then that's not a 
problem.

So, the simplest, most naive implementation of FORMAT just says 'pick 
the first format set that successfully encodes the packet'.  This will 
work fine.  However, it will also not be as efficienct as a more complex 
implementation.  Hopefully you can see, though, that this doesn't affect 
interoperability.  It's a free choice at the compressor and you can make 
it as good or as bad as you like!


>    - what about syntax and usage of FORMAT SELECTOR,
>      it is actually not needed (can be identified from
>      ID-bits of IR/DYN packet)


That's a good question and one that we've been discussing a bit 
ourselves.  Rest assured that the update of the EPIC-lite draft (which 
will be submitted this week) will contain an updated FORMAT encoding.


> 
> Best regards,
> Julije Ozegovic
> 
> 


-- 
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  Wed Feb 27 07:30:38 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 HAA19028
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 07:30:38 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA15484;
	Wed, 27 Feb 2002 07:26:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA15456
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 07:26:11 -0500 (EST)
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 HAA18493
	for <rohc@ietf.org>; Wed, 27 Feb 2002 07:26:06 -0500 (EST)
Received: from cabo3 (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with SMTP id g1RCPhI16513;
	Wed, 27 Feb 2002 13:25:43 +0100 (MET)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Cc: <zhigang.c.liu@nokia.com>, <rohc@ietf.org>
Subject: RE: [rohc] RE: Default decompression algorithms
Date: Wed, 27 Feb 2002 13:25:42 +0100
Message-ID: <NFBBJFHGMCFINEMHAMBGMEIJHHAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-reply-to: <3C7C9F7A.3B9EC769@ericsson.com>
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

Miguel,

> Yes, but that does not impact standardization. Whether the decompressor
> contains already the code for 1 or for 1,000 algorithms is not affecting
> the performance nor the standard.

Well, it does, if the idea is that a decompressor announces the algorithms
it has.
Sending 1000 algorithm identifiers is more expensive than sending the
algorithm for most representations of these that I can think of.

> Certainly static payload types are not assigned nor recommended to use.
> However, dynamic payload types are. The point here in the comparison
> with SDP was that, there should be a mechanism whereby the decompressor
> informs the compressor about already uploaded algorithms.

OK, I see.  SDP uses MIME-style identifiers to indicate the codecs that the
application actually wishes to use.

In SDP, this makes sense, as both parties must have implementations of the
codec, or they can't interoperate.
So expending significant effort (often several hundreds of bytes) to find
that lowest common denominator is the right thing to do.

In Sigcomp, the effort to just mandate one algorithm (by simply sending its
decompressor) is in the same ballpark as interchanging the capability
information.
Why bother?  I'd like some numbers, please.

> > Would you trust UE A to upload algorithm X for UE B?
>
> Aren't we doing it now??? Don't we have a UDVM upload whereby an endpoint
> uploads the algorithm X to another endpoint?

Yes, but in the form of state that will only influence the decompression of
its own packets.

> Like I said before. Do we agree on the requirement? If Yes, we can discuss
> technical proposals. If Not, we should stop the discussion.

The requirement is to reduce the signaling latency.
I believe we are discussing certain details of the solution right now, which
will influence its performance in one way or the other.
I'm trying to argue that the performance win of a specific approach that
increases complexity is negative or at least not very positive.

(Of course, the approach still remains possible if there is something as
simple as state claims in the protocol, so implementers can go ahead and
make use of these.  I'd still advise them not to bother.)

> So you don't honor the requirement? Then, I doubt SigComp can ever be
> used in real life.

Right now, I know of only one technical requirement, the one I cited.
(Well, actually, we have a whole document that essentially details that
technical requirement, draft-ietf-rohc-signaling-req-assump-04.txt; maybe we
have to amend that.)There also is a level 9 requirement to stay clear of
IPR, which I fully support.

Gruesse, Carsten


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


From rohc-admin@ietf.org  Wed Feb 27 07:42:04 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 HAA19538
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 07:42:04 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA16757;
	Wed, 27 Feb 2002 07:38:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA16727
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 07:37:57 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19325
	for <rohc@ietf.org>; Wed, 27 Feb 2002 07:37:53 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g1RCbpB06391;
	Wed, 27 Feb 2002 13:37:51 +0100 (MET)
Received: from ericsson.com (3NJPI0013L1IJOG.lmf.ericsson.se [131.160.30.42])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g1RCbomK021051;
	Wed, 27 Feb 2002 14:37:50 +0200 (EET)
Message-ID: <3C7CD359.551A0607@ericsson.com>
Date: Wed, 27 Feb 2002 14:38:49 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Organization: OY LM Ericsson AB
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: es,en
MIME-Version: 1.0
To: "Dr. Carsten Bormann" <cabo@tzi.org>
CC: zhigang.c.liu@nokia.com, rohc@ietf.org
Subject: SigComp Requirements (was Re: [rohc] RE: Default decompression 
 algorithms)
References: <NFBBJFHGMCFINEMHAMBGMEIJHHAA.cabo@tzi.org>
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

Hi Carsten:

I changed the subject of the discussion, just to focus in this e-mail on 
requirements.

A group of individuals collected the 3GPP requirements related to SIP and
write them down in an Internet Draft,

http://search.ietf.org/internet-drafts/draft-garcia-sipping-3gpp-reqs-02.txt

Version -03 is on its way and will be submitted before the deadline to MN.

I will encourage to read the actual section 6.5 in that document. There are
several requirements affecting compression.

I will also recommend to read requirements 6.1.1 and 6.1.2. Although these
are general requirements, they are applicable to all the rest of the 
requirements and possible solutions.

/Miguel

"Dr. Carsten Bormann" wrote:
> 
> Miguel,
> 
> > Yes, but that does not impact standardization. Whether the decompressor
> > contains already the code for 1 or for 1,000 algorithms is not affecting
> > the performance nor the standard.
> 
> Well, it does, if the idea is that a decompressor announces the algorithms
> it has.
> Sending 1000 algorithm identifiers is more expensive than sending the
> algorithm for most representations of these that I can think of.
> 
> > Certainly static payload types are not assigned nor recommended to use.
> > However, dynamic payload types are. The point here in the comparison
> > with SDP was that, there should be a mechanism whereby the decompressor
> > informs the compressor about already uploaded algorithms.
> 
> OK, I see.  SDP uses MIME-style identifiers to indicate the codecs that the
> application actually wishes to use.
> 
> In SDP, this makes sense, as both parties must have implementations of the
> codec, or they can't interoperate.
> So expending significant effort (often several hundreds of bytes) to find
> that lowest common denominator is the right thing to do.
> 
> In Sigcomp, the effort to just mandate one algorithm (by simply sending its
> decompressor) is in the same ballpark as interchanging the capability
> information.
> Why bother?  I'd like some numbers, please.
> 
> > > Would you trust UE A to upload algorithm X for UE B?
> >
> > Aren't we doing it now??? Don't we have a UDVM upload whereby an endpoint
> > uploads the algorithm X to another endpoint?
> 
> Yes, but in the form of state that will only influence the decompression of
> its own packets.
> 
> > Like I said before. Do we agree on the requirement? If Yes, we can discuss
> > technical proposals. If Not, we should stop the discussion.
> 
> The requirement is to reduce the signaling latency.
> I believe we are discussing certain details of the solution right now, which
> will influence its performance in one way or the other.
> I'm trying to argue that the performance win of a specific approach that
> increases complexity is negative or at least not very positive.
> 
> (Of course, the approach still remains possible if there is something as
> simple as state claims in the protocol, so implementers can go ahead and
> make use of these.  I'd still advise them not to bother.)
> 
> > So you don't honor the requirement? Then, I doubt SigComp can ever be
> > used in real life.
> 
> Right now, I know of only one technical requirement, the one I cited.
> (Well, actually, we have a whole document that essentially details that
> technical requirement, draft-ietf-rohc-signaling-req-assump-04.txt; maybe we
> have to amend that.)There also is a level 9 requirement to stay clear of
> IPR, which I fully support.
> 
> Gruesse, Carsten

-- 
Miguel-Angel Garcia                     Oy LM Ericsson AB
                                        Jorvas, Finland
mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 5140002

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


From rohc-admin@ietf.org  Wed Feb 27 08:50: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 IAA22148
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 08:50:51 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA20342;
	Wed, 27 Feb 2002 08:47:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA20311
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 08:47:00 -0500 (EST)
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 IAA21979
	for <rohc@ietf.org>; Wed, 27 Feb 2002 08:46:55 -0500 (EST)
Received: from cabo3 (nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with SMTP id g1RDkmI07518;
	Wed, 27 Feb 2002 14:46:48 +0100 (MET)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Cc: <zhigang.c.liu@nokia.com>, <rohc@ietf.org>
Subject: RE: SigComp Requirements (was Re: [rohc] RE: Default decompression  algorithms)
Date: Wed, 27 Feb 2002 14:46:48 +0100
Message-ID: <NFBBJFHGMCFINEMHAMBGKEIKHHAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-reply-to: <3C7CD359.551A0607@ericsson.com>
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

Miguel,

does this list of requirements take into account the UDVM approach?
It does seem to predate its adoption.

Gruesse, Carsten


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


From rohc-admin@ietf.org  Wed Feb 27 08:56: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 IAA22497
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 08:56:08 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA20567;
	Wed, 27 Feb 2002 08:52:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA20540
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 08:52:20 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22373
	for <rohc@ietf.org>; Wed, 27 Feb 2002 08:52:15 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g1RDqEB12088;
	Wed, 27 Feb 2002 14:52:15 +0100 (MET)
Received: from ericsson.com (3NJPI0013L1IJOG.lmf.ericsson.se [131.160.30.42])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g1RDqDmK026862;
	Wed, 27 Feb 2002 15:52:13 +0200 (EET)
Message-ID: <3C7CE4C8.75960BF3@ericsson.com>
Date: Wed, 27 Feb 2002 15:53:12 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Organization: OY LM Ericsson AB
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: es,en
MIME-Version: 1.0
To: "Dr. Carsten Bormann" <cabo@tzi.org>
CC: zhigang.c.liu@nokia.com, rohc@ietf.org
Subject: Re: SigComp Requirements (was Re: [rohc] RE: Default decompression  
 algorithms)
References: <NFBBJFHGMCFINEMHAMBGKEIKHHAA.cabo@tzi.org>
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

Hi:

No, these requirements were discussed prior to the UDVM approach.

As I said, a new version of this draft will be shortly submitted.
I need to discuss with the rest of the co-authors some better wording
that reflects the latest assumptions in Rohc and 3GPP.

I will announce the draft in this mailing list as well.

/Miguel

"Dr. Carsten Bormann" wrote:
> 
> Miguel,
> 
> does this list of requirements take into account the UDVM approach?
> It does seem to predate its adoption.
> 
> Gruesse, Carsten

-- 
Miguel-Angel Garcia                     Oy LM Ericsson AB
                                        Jorvas, Finland
mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 5140002

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


From rohc-admin@ietf.org  Wed Feb 27 09:01: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 JAA22778
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 09:01:51 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA20749;
	Wed, 27 Feb 2002 08:57:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA20716
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 08:57:02 -0500 (EST)
Received: from h3gshmsw1.hutchison3g.com (mail.hutchison3g.com [63.137.144.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22535
	for <rohc@ietf.org>; Wed, 27 Feb 2002 08:56:57 -0500 (EST)
Received: from andromeda.h3guk.com (unverified) by h3gshmsw1.hutchison3g.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T59544a7cd50af80e8271c@h3gshmsw1.hutchison3g.com>;
 Wed, 27 Feb 2002 13:57:37 +0000
Received: by andromeda.h3guk.com with Internet Mail Service (5.5.2653.19)
	id <FN9HTV29>; Wed, 27 Feb 2002 13:57:43 -0000
Message-ID: <F3035F172B472247AED58C867616D0AB4FD49D@RETICULUM.h3guk.com>
From: Kevan Hobbis <Kevan.Hobbis@hutchison3g.com>
To: "'Dr. Carsten Bormann'" <cabo@tzi.org>,
        "Miguel A. Garcia"
	 <Miguel.A.Garcia@ericsson.com>
Cc: zhigang.c.liu@nokia.com, rohc@ietf.org
Subject: RE: SigComp Requirements (was Re: [rohc] RE: Default decompressio
	n  algorithms)
Date: Wed, 27 Feb 2002 13:57:17 -0000
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

Carsten

High-level requirements should not be affected by a particular proposed
implementation or solution, hence they ought to pre-date any proposed
solution. 

Thanks

Kevan Hobbis

-----Original Message-----
From: Dr. Carsten Bormann [mailto:cabo@tzi.org]
Sent: 27 February 2002 13:47
To: Miguel A. Garcia
Cc: zhigang.c.liu@nokia.com; rohc@ietf.org
Subject: RE: SigComp Requirements (was Re: [rohc] RE: Default
decompression algorithms)


Miguel,

does this list of requirements take into account the UDVM approach?
It does seem to predate its adoption.

Gruesse, Carsten


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


_______________________________________________________________

If this email isn't for you then we'd be grateful if you could let our
helpdesk know there's been a mistake by putting 'received in 
error' in the subject box and sending it to helpdesk@hutchison3g.com. 
If it isn't for you, we're sure you'll understand that you're not 
allowed to copy, disclose or distribute any of its contents.  
This email is private and confidential and may also be privileged,
so if you shouldn't have received it, we'd be grateful if you could delete it.
Thanks.
________________________________________________________________


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


From rohc-admin@ietf.org  Wed Feb 27 09:22:12 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 JAA23649
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 09:22:12 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA21791;
	Wed, 27 Feb 2002 09:15:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA21742
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 09:15:17 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23377
	for <rohc@ietf.org>; Wed, 27 Feb 2002 09:15:11 -0500 (EST)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g1REFEB29536
	for <rohc@ietf.org>; Wed, 27 Feb 2002 15:15:14 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Wed Feb 27 14:04:50 2002 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <F4G2G60Z>; Wed, 27 Feb 2002 13:55:09 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E31E4F@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'Miguel A. Garcia'" <Miguel.A.Garcia@ericsson.com>
Cc: rohc@ietf.org
Subject: RE: SigComp Requirements (was Re: [rohc] RE: Default decompressio
	n  algorithms)
Date: Wed, 27 Feb 2002 14:04:03 +0100
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

Miguel,

Here are some immediate comments on these requirements.

Cheers,
/L-E



6.5 Compression of SIP signaling 
    
   As the radio interface is a scarce resource, the transport of SIP 
   messages over the radio interface must be done efficiently. 
    
   Therefore, there must be a mechanism to efficiently transport SIP 
   signaling packets over the radio interface, by compressing the SIP 
   signaling messages between the UA and the SIP outbound proxy, and by 
   compressing the IP and transport layer protocol headers that carry 
   these SIP messages. 
   
-> LEJ: Yes, this is why we do SigComp, in addition to link-layer
   IP/UDP header compression.
    

6.5.1 Extensibility of the SIP compression 
    
   The chosen solution(s) must be extensible to facilitate the 
   incorporation of new and improved compression algorithms in a backward 
   compatible way, as they become available.

-> LEJ: The UDVM approach should fully meet this requirement. 
    
    
6.5.2 SIP compression and roaming 
    
   The chosen solution(s) for SIP compression must work in roaming 
   scenarios. 
    
-> LEJ: This was one of the reasons we decided to do compression end2end (not per link).
    

6.5.3 Minimal impact of SIP compression on the network 
    
   Application specific compression must minimize impacts on existing 
   3GPP network, e.g. the compression must be defined between the UA at 
   the SIP terminal and the outbound SIP Proxy in the visited network.

-> LEJ: Luckily, there were also technical arguments for placing SigComp at
   the application layer (UA<->Proxy). 
    
    
6.5.4 Optionality of SIP compression 
    
   It must be possible to leave the usage of compression for SIP 
   signaling optional. 

-> LEJ: No problem, we do not expect everyone to suddenly use compressed SIP.
    
    
6.5.5 Default algorithm for SIP compression 
    
   If SIP signaling compression is used, a default algorithm must be 
   supported by the UA and the network elements involved for compression. 
    
-> LEJ: Why?? We are currently having a discussion about this on the list, 
   and we will see what the outcome will be. ROHC is not at all discussing
   algorithms, and will therefore not define any default algorithm. What is
   still under consideration is whether we should provide mechanisms to
   announce decompressor-supported algorithms. However, the usefulness of
   this is still not clearly proven, and if we want to support this we must
   consider the security aspects of it and the added complexity of the 
   solution. 

    
6.5.6 Compression Negotiation 
    
   There must be a mechanism to negotiate between the UA and the first 
   SIP outbound proxy the compression algorithm to be used. The type of 
   negotiation mechanism that should be implemented is that the UAC 
   includes a list of compression algorithms and the first SIP outbound 
   proxy responds with the selected one. Subsequent SIP messages are 
   compressed based on the agreed algorithm.

-> LEJ: This is not a requirement, its is a proposed solution/mechanism.
   Further, only the Proxy->UA traffic direction is addressed above.



> 
> A group of individuals collected the 3GPP requirements 
> related to SIP and
> write them down in an Internet Draft,
> 
> http://search.ietf.org/internet-drafts/draft-garcia-sipping-3g
> pp-reqs-02.txt
> 
> Version -03 is on its way and will be submitted before the 
> deadline to MN.
> 
> I will encourage to read the actual section 6.5 in that 
> document. There are
> several requirements affecting compression.
> 
> I will also recommend to read requirements 6.1.1 and 6.1.2. 
> Although these
> are general requirements, they are applicable to all the rest of the 
> requirements and possible solutions.
> 
> /Miguel

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


From rohc-admin@ietf.org  Wed Feb 27 09:56: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 JAA25626
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 09:56:40 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA24103;
	Wed, 27 Feb 2002 09:53:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA24074
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 09:53:47 -0500 (EST)
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 JAA25362
	for <rohc@ietf.org>; Wed, 27 Feb 2002 09:53:29 -0500 (EST)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <1S9WN4H0>; Wed, 27 Feb 2002 14:50:14 -0000
Message-ID: <76C92FBBFB58D411AE760090271ED4186F9FD9@rsys002a.roke.co.uk>
From: "Price, Richard" <richard.price@roke.co.uk>
To: "'Miguel A. Garcia'" <Miguel.A.Garcia@ericsson.com>,
        "Dr. Carsten Bormann" <cabo@tzi.org>
Cc: zhigang.c.liu@nokia.com,
        "'Lars-Erik Jonsson (EPL)'"
	 <Lars-Erik.Jonsson@epl.ericsson.se>,
        rohc@ietf.org
Subject: RE: SigComp Requirements (was Re: [rohc] RE: Default decompressio
	n algorithms)
Date: Wed, 27 Feb 2002 14:50:13 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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-1"

Hi Miguel and Carsten,

Just got back from holiday - mind if I join in this interesting
discussion? I'd be grateful for an answer to the following two
questions:

Miguel: Is it important from a technical perspective for 3GPP to
have an algorithm negotiation mechanism?

Section 6.5.6 of the 3GPP requirements draft seems to specify a
solution rather than a requirement, in the sense that entities
external to SigComp don't know (or care) whether a negotiation
mechanism is being employed. Surely what is more important is the
technical performance of the solution, measured using some or all
of the following:

*   Call setup time
*   Processing requirements
*   Memory requirements
*   Standardisation effort
*   Implementation effort
*   IPR concerns
*   Future-proofing
*   Any others I've forgotten?

If the ROHC WG can beat the algorithm negotiation approach in terms
of all of the above, is it still necessary to provide an algorithm
negotiation mechanism within SigComp?

Carsten: Do you have any objections to including an algorithm
negotiation mechanism, other than the additional standardisation
effort?

The reason I ask is that SigComp already has the ability to negotiate
algorithms - it comes for free as part of the "state claim" mechanism
that we provided to support explicit acks. So no additional effort is
needed to include algorithm negotiation.

Is it OK to provide both the UDVM approach and the algorithm
negotiation approach, and leave it to implementers to choose which to
adopt?

Regards,

Richard

> -----Original Message-----
> From: Miguel A. Garcia [mailto:Miguel.A.Garcia@ericsson.com]
> Sent: Wednesday, February 27, 2002 1:53 PM
> To: Dr. Carsten Bormann
> Cc: zhigang.c.liu@nokia.com; rohc@ietf.org
> Subject: Re: SigComp Requirements (was Re: [rohc] RE: Default
> decompression algorithms)
> 
> 
> Hi:
> 
> No, these requirements were discussed prior to the UDVM approach.
> 
> As I said, a new version of this draft will be shortly submitted.
> I need to discuss with the rest of the co-authors some better wording
> that reflects the latest assumptions in Rohc and 3GPP.
> 
> I will announce the draft in this mailing list as well.
> 
> /Miguel
> 
> "Dr. Carsten Bormann" wrote:
> > 
> > Miguel,
> > 
> > does this list of requirements take into account the UDVM approach?
> > It does seem to predate its adoption.
> > 
> > Gruesse, Carsten
> 
> -- 
> Miguel-Angel Garcia                     Oy LM Ericsson AB
>                                         Jorvas, Finland
> mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
> mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 5140002
> 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
> 

--------------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 Feb 27 10:04:46 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 KAA25988
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 10:04:46 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA24941;
	Wed, 27 Feb 2002 10:02:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA24913
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 10:02:39 -0500 (EST)
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 KAA25920
	for <rohc@ietf.org>; Wed, 27 Feb 2002 10:02:35 -0500 (EST)
Received: from cabo3 (nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with SMTP id g1RF2XI26740
	for <rohc@ietf.org>; Wed, 27 Feb 2002 16:02:34 +0100 (MET)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: <rohc@ietf.org>
Subject: [rohc] Sigcomp: UDVM security issues
Date: Wed, 27 Feb 2002 16:02:33 +0100
Message-ID: <NFBBJFHGMCFINEMHAMBGAEILHHAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
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

Sigcompers,

I've just had a 30-minute chat about the UDVM with Karsten Sohr (if
you don't immediately recognize that name, it's quite googleable).

While I don't believe in 30-minute security analyses, there were two
notable results of this discussion:

1) 6 bytes (48 bits) is too little.  If we assume that a busy proxy
   can hold a million states, it looks like we need 9 bytes (72 bits)
   for a reasonable collision (im)probability.

2) One significant aspect of the DoS invulnerability of the UDVM is
   the assignment of effort values for the instructions.  We have to
   make sure that the complexity of the implementation of each
   instruction is at least in the right class with respect to the
   nominal effort.  While this is trivial for most of the
   instructions, we should have another close look at the table.

Karsten will continue to look at the UDVM and its security issues; he
hopes to have a more serious security analysis done within the next
two weeks or so.

Gruesse, Carsten

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


From rohc-admin@ietf.org  Wed Feb 27 10:10:27 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 KAA26294
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 10:10:27 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA25193;
	Wed, 27 Feb 2002 10:08:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA25158
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 10:07:57 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.46])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26164
	for <rohc@ietf.org>; Wed, 27 Feb 2002 10:07:53 -0500 (EST)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g1RF7tZc001007
	for <rohc@ietf.org>; Wed, 27 Feb 2002 16:07:55 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Wed Feb 27 14:50:32 2002 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <FY38SAAT>; Wed, 27 Feb 2002 14:50:37 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E31E50@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'Miguel A. Garcia'" <Miguel.A.Garcia@ericsson.com>
Cc: "'rohc@ietf.org'" <rohc@ietf.org>
Subject: RE: SigComp Requirements (was Re: [rohc] RE: Default decompressio
	n  algorithms)
Date: Wed, 27 Feb 2002 14:50:27 +0100
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

Miguel,

Here are some immediate comments on these requirements.

Cheers,
/L-E



6.5 Compression of SIP signaling 
    
   As the radio interface is a scarce resource, the transport of SIP 
   messages over the radio interface must be done efficiently. 
    
   Therefore, there must be a mechanism to efficiently transport SIP 
   signaling packets over the radio interface, by compressing the SIP 
   signaling messages between the UA and the SIP outbound proxy, and by 
   compressing the IP and transport layer protocol headers that carry 
   these SIP messages. 
   
-> LEJ: Yes, this is why we do SigComp, in addition to link-layer
   IP/UDP header compression.
    

6.5.1 Extensibility of the SIP compression 
    
   The chosen solution(s) must be extensible to facilitate the 
   incorporation of new and improved compression algorithms in a backward 
   compatible way, as they become available.

-> LEJ: The UDVM approach should fully meet this requirement. 
    
    
6.5.2 SIP compression and roaming 
    
   The chosen solution(s) for SIP compression must work in roaming 
   scenarios. 
    
-> LEJ: This was one of the reasons we decided to do compression end2end (not per link).
    

6.5.3 Minimal impact of SIP compression on the network 
    
   Application specific compression must minimize impacts on existing 
   3GPP network, e.g. the compression must be defined between the UA at 
   the SIP terminal and the outbound SIP Proxy in the visited network.

-> LEJ: Luckily, there were also technical arguments for placing SigComp at
   the application layer (UA<->Proxy). 
    
    
6.5.4 Optionality of SIP compression 
    
   It must be possible to leave the usage of compression for SIP 
   signaling optional. 

-> LEJ: No problem, we do not expect everyone to suddenly use compressed SIP.
    
    
6.5.5 Default algorithm for SIP compression 
    
   If SIP signaling compression is used, a default algorithm must be 
   supported by the UA and the network elements involved for compression. 
    
-> LEJ: Why?? We are currently having a discussion about this on the list, 
   and we will see what the outcome will be. ROHC is not at all discussing
   algorithms, and will therefore not define any default algorithm. What is
   still under consideration is whether we should provide mechanisms to
   announce decompressor-supported algorithms. However, the usefulness of
   this is still not clearly proven, and if we want to support this we must
   consider the security aspects of it and the added complexity of the 
   solution. 

    
6.5.6 Compression Negotiation 
    
   There must be a mechanism to negotiate between the UA and the first 
   SIP outbound proxy the compression algorithm to be used. The type of 
   negotiation mechanism that should be implemented is that the UAC 
   includes a list of compression algorithms and the first SIP outbound 
   proxy responds with the selected one. Subsequent SIP messages are 
   compressed based on the agreed algorithm.

-> LEJ: This is not a requirement, its is a proposed solution/mechanism.
   Further, only the Proxy->UA traffic direction is addressed above.



> 
> A group of individuals collected the 3GPP requirements 
> related to SIP and
> write them down in an Internet Draft,
> 
> http://search.ietf.org/internet-drafts/draft-garcia-sipping-3g
> pp-reqs-02.txt
> 
> Version -03 is on its way and will be submitted before the 
> deadline to MN.
> 
> I will encourage to read the actual section 6.5 in that 
> document. There are
> several requirements affecting compression.
> 
> I will also recommend to read requirements 6.1.1 and 6.1.2. 
> Although these
> are general requirements, they are applicable to all the rest of the 
> requirements and possible solutions.
> 
> /Miguel

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


From rohc-admin@ietf.org  Wed Feb 27 10:59: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 KAA28961
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 10:59:39 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA27353;
	Wed, 27 Feb 2002 10:55:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA27302
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 10:55:55 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28780
	for <rohc@ietf.org>; Wed, 27 Feb 2002 10:55:51 -0500 (EST)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g1RFtrB22233
	for <rohc@ietf.org>; Wed, 27 Feb 2002 16:55:53 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Wed Feb 27 15:49:58 2002 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <FY38S1B5>; Wed, 27 Feb 2002 15:50:03 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E31E53@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'West, Mark (ITN)'" <mark.a.west@roke.co.uk>
Cc: "'rohc@ietf.org'" <rohc@ietf.org>
Subject: RE: [rohc] Questions about the MIB!
Date: Wed, 27 Feb 2002 15:49:53 +0100
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: West, Mark (ITN) [mailto:mark.a.west@roke.co.uk]
> Sent: den 25 februari 2002 11:03
> To: rohc@ietf.org
> Cc: Juergen Quittek
> Subject: [rohc] Questions about the MIB!
> 
> 
> There is a quantity of 
> information about contexts which is based on the profiles defined in 
> RFC-3095.  (For example, referring to the modes as U, O and R 
> and states 
> as IR/FO/SO).  This makes absolute sense with regard to RFC 
> 3095.  I am 
> interested to know what anyone thinks about the impact of splitting 
> 3095, however!  How much of the MIB can/should be based on specific 
> profile details, rather than 'generic' framework?  (Clearly 
> in the cases 
> mentioned above, opaque numeric identifiers could be used)
> Anyway, it's a general issue that it would be nice to have 
> some input on...

I agree that this must be considered, and the details will of course 
be clearer when we start the Framework/Profile split. However, most
things can clearly be identified as Framework or RTP, and the MIB
should probably separate what is general ROHC Framework properties
from what is RTP specific details.

/L-E 


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


From rohc-admin@ietf.org  Wed Feb 27 11:06: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 LAA29392
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 11:06:57 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA28398;
	Wed, 27 Feb 2002 11:03:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA28369
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 11:03:51 -0500 (EST)
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 LAA29239
	for <rohc@ietf.org>; Wed, 27 Feb 2002 11:03:46 -0500 (EST)
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <1XV80982>; Wed, 27 Feb 2002 16:03:14 -0000
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 1S9WN4NX; Wed, 27 Feb 2002 16:03:06 -0000
From: "West, Mark (ITN)" <mark.a.west@roke.co.uk>
To: rohc <rohc@ietf.org>
Message-ID: <3C7D033A.7090203@roke.co.uk>
Date: Wed, 27 Feb 2002 16:03:06 +0000
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="------------InterScan_NT_MIME_Boundary"
Subject: [rohc] Sorted?!
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,

First of all, this is *not* about default algorithms.  Honest ;-)

However, from the recent discussion about 'deflate' there were questions 
regarding the use of dynamic Huffman trees rather than static ones.

If you look at how RFC 1951 defines the storage of the dynamic Huffman 
tree information (a compressed list of the code length for each value), 
this is at odds with the definition of the HUFFMAN instruction (which 
requires the code-lengths to be in increasing order).

To solve this, it is necessary to construct a mapping from one 
representation to the other.  This can be easily done by sorting the 
list.  Clearly a sort could be written in UDVM byte-code, although I 
suspect this to be a rather painful process, with a non-trivial overhead.

The alternative (and it has been suggested that this might make sense 
from the perspective of other compression algorithms) is to introduce a 
'SORT' instruction.

At its simplest, this would sort an 'r' row by 'c' column table of 
2-byte entries (where the start address, 'r' and 'c' are the parameters).

Of course, the biggest concern with such an instruction (I would think) 
is with the DoS security implication.
Following on from Carsten's security e-mail, if we set the 'cost' of 
SORT to be 'O(n.log(n))' we are constraining the implementation.
If we set it to 'O(n^2)' you would need to make many cycles available to 
be able to perform any kind of sort (which generally opens up a DoS 
vulnerability).
(Of course, these issues are essentially the same regardless of whether 
the sort is implemented as a single instruction or in byte-code)

So, if we feel that sorting is a useful operation (and I contend that it 
just might be, if you want to support to the full range of 'deflate' 
compressed formats), should we have a SORT instruction?

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  Wed Feb 27 11:27: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 LAA00439
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 11:27:32 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA29753;
	Wed, 27 Feb 2002 11:24:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA29717
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 11:24:31 -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 LAA00301
	for <rohc@ietf.org>; Wed, 27 Feb 2002 11:24:22 -0500 (EST)
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.1.0/Switch-2.1.0) with ESMTP id g1RGOfG22235
	for <rohc@ietf.org>; Wed, 27 Feb 2002 10:24:41 -0600 (CST)
Received: from daebh001.NOE.Nokia.com (unverified) by davir01nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5953874cc1ac12f25407a@davir01nok.americas.nokia.com>;
 Wed, 27 Feb 2002 10:24:25 -0600
Received: from daebe005.NOE.Nokia.com ([172.18.242.203]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Wed, 27 Feb 2002 10:23:55 -0600
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: SigComp Requirements (was Re: [rohc] RE: Default decompression algorithms)
Date: Wed, 27 Feb 2002 10:23:54 -0600
Message-ID: <DE0842B293FC4847992F9EDF8D72E1ED24A269@daebe005.NOE.Nokia.com>
Thread-Topic: SigComp Requirements (was Re: [rohc] RE: Default decompression algorithms)
Thread-Index: AcG/nlwwFFDiB8I3SKOyqTj17QpVGwACeTOQ
To: <richard.price@roke.co.uk>, <Miguel.A.Garcia@ericsson.com>, <cabo@tzi.org>
Cc: <Lars-Erik.Jonsson@epl.ericsson.se>, <rohc@ietf.org>
X-OriginalArrivalTime: 27 Feb 2002 16:23:55.0271 (UTC) FILETIME=[26B3B970:01C1BFAB]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA29718
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,

Just try to make things simple:

1) The major (if not only one) requirement of SigComp 
is to reduce latency. I agree with Carsten. 

2) Here we are talking about a simple optimization to
reduce the latency. Does anyone has comment on it?
http://www1.ietf.org/mail-archive/working-groups/rohc/current/msg00065.html

3) Now, the question is cost/gain evaluation. I've
made some attempt in
http://www1.ietf.org/mail-archive/working-groups/rohc/current/msg00064.html.
Comment? The hash size might be increased to 9 bytes (?).

4) Also, what about security? I don't see it is a problem
as long as the use of feedback (capability announcement)
does not create new risk. But do I missed something?

BR,
Zhigang

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


From rohc-admin@ietf.org  Wed Feb 27 12:38: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 MAA05270
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 12:38:15 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA05153;
	Wed, 27 Feb 2002 12:33:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA05119
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 12:33:39 -0500 (EST)
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 MAA05056
	for <rohc@ietf.org>; Wed, 27 Feb 2002 12:33:34 -0500 (EST)
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <1XV800MS>; Wed, 27 Feb 2002 17:32:24 -0000
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 1S9WN44B; Wed, 27 Feb 2002 17:32:19 -0000
From: "West, Mark (ITN)" <mark.a.west@roke.co.uk>
To: Julije Ozegovic <julije@fesb.hr>
Cc: rohc <rohc@ietf.org>
Message-ID: <3C7D1823.7070003@roke.co.uk>
Date: Wed, 27 Feb 2002 17:32:19 +0000
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
Subject: Re: [rohc] TCP/IP EPIC profile
References: <3C7BF6E0.9070307@fesb.hr>
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 Julije,

I've just waded through your comments on the 'expanded' profile, and 
I'll try and summarise the points you raise and make some comments...

- IP checksum treated later / INFERRED-IP-CHECKSUM not defined

The current draft does not define INFERRED-IP-CHECKSUM.  (It was defined 
in an older 'EPIC for TCP' draft, but I realise that's not much help!) 
It is in the new version that will be submitted this week, though.
When you see how this works, you will appreciate that the IP checksum is 
not actually treated later, but simply ignored.  (On compression, 
INFERRED-IP-CHECKSUM sets the checksum bits to 0; on decompression is 
fills them in with the computed checksum).


- NBO not in the toolbox

Again, true.  We have removed INFERRED-SCALED and replaced it with NBO 
and SCALE operations, which gives more flexibility.  Again, these are 
described in the draft that will be submitted.  (I agree that it might 
have been nice to synchronise things a little better...)


- Some percentages don't add up to 100%

That's what we profile writers refer to as a 'mistake' ;-)
Actually, it shouldn't matter - but it should be fixed!


- Compiler should read comments or what?

Well, the compiler is free to read the comments.  But it probably ought 
to ignore what they say...


- Various mis-named method names

Sorry - these are typos and need to be fixed.


- Various unused methods

Again, they should be referenced so this is an error in the profile.


- FORMAT appears in 'CO' packet

Yes, it certainly does.  Otherwise, how would you know what different 
formats to build?  I don't quite see the problem here...


- ack STACK-TO-CONTROL not defined
- psh STACK-TO-CONTROL not defined

I don't understand the comments.


- skip-msn is not defined (but self-explanatory)

Tend to agree!  (This is, of course, a TCP specific method and should be 
defined along with the profile).


- An IRREGULAR(16,100%) is used to encode a format selector

This should be IRREGULAR(1,100%) - it's a typo...


- Not clear what is being encoded at each point

This could be overcome by better commenting (whether or not the compiler 
reads them) or splitting up the methods to a finer granularity.  This 
should be taken care of in the profile, though, I agree.

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  Wed Feb 27 13:00:47 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 NAA06719
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 13:00:47 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA06693;
	Wed, 27 Feb 2002 12:58:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA06665
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 12:58:38 -0500 (EST)
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 MAA06579
	for <rohc@ietf.org>; Wed, 27 Feb 2002 12:58:34 -0500 (EST)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <1S9WN446>; Wed, 27 Feb 2002 17:55:23 -0000
Message-ID: <76C92FBBFB58D411AE760090271ED4186F9FDB@rsys002a.roke.co.uk>
From: "Price, Richard" <richard.price@roke.co.uk>
To: "'zhigang.c.liu@nokia.com'" <zhigang.c.liu@nokia.com>,
        Miguel.A.Garcia@ericsson.com, cabo@tzi.org
Cc: Lars-Erik.Jonsson@epl.ericsson.se, rohc@ietf.org
Subject: RE: SigComp Requirements (was Re: [rohc] RE: Default decompressio
	n algorithms)
Date: Wed, 27 Feb 2002 17:55:23 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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-1"

Hi,

Just a few comments on your summary of the "algorithm announcement" debate.

Regards,

Richard


> Just try to make things simple:
> 
> 1) The major (if not only one) requirement of SigComp 
> is to reduce latency. I agree with Carsten.
>
> 2) Here we are talking about a simple optimization to
> reduce the latency. Does anyone has comment on it?
> http://www1.ietf.org/mail-archive/working-groups/rohc/current/msg00065.html

My only comment is that since the mechanisms needed for "algorithm announcement"
are already built into SigComp, I can't see any reason *not* to make this
functionality available to implementers.

Should the above text be placed in the SigComp draft itself, or should a
separate "Implementer's Guide" draft be considered? The latter approach might be
very useful for getting SigComp standardised more quickly. The draft already
contains a lot of text that explains how the technical mechanisms might be used;
this is valuable for implementers but doesn't need to be standardised per se.

I think that it would be OK to have an implementer's guide in Internet Draft
form for now, and then publish it later when there's less time pressure (perhaps
as an Informational RFC, or perhaps by folding it into the SigComp RFC when it
reaches Draft Standard).

> 3) Now, the question is cost/gain evaluation. I've made some attempt in
> http://www1.ietf.org/mail-archive/working-groups/rohc/current/msg00064.html.
> Comment? The hash size might be increased to 9 bytes (?).

The minimum hash size of 9 bytes only applies to algorithms (and other kinds of
state information) that are downloaded to the UDVM and stored on the fly. In
the case of well-known algorithms that have been documented somewhere the
state identifier for the algorithm can be any length and any value - after all
there's no point keeping an algorithm secret if it's in an Internet Draft!

For example, the following list of 1-byte state identifiers might be reserved:

ID    Corresponding algorithm

0          UNCOMPRESSED
1          DEFLATE
2          LZO
3          LZJH
4          EPIC
:            :

The IETF doesn't need to define the above list - the task can be left to 3GPP,
if they believe the effort to be worthwhile.

> 4) Also, what about security? I don't see it is a problem
> as long as the use of feedback (capability announcement)
> does not create new risk. But do I missed something?

Since the needed mechanisms are already provided by SigComp, the use of
"algorithm announcement" doesn't create any new security risks that we
don't already have.

--------------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 Feb 27 14:29:12 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 OAA12296
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 14:29:12 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA22751;
	Wed, 27 Feb 2002 14:26:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA22720
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 14:26:48 -0500 (EST)
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 OAA12136
	for <rohc@ietf.org>; Wed, 27 Feb 2002 14:26:39 -0500 (EST)
Received: from cabo3 (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with SMTP id g1RJQVI22242;
	Wed, 27 Feb 2002 20:26:32 +0100 (MET)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: "Price, Richard" <richard.price@roke.co.uk>, <zhigang.c.liu@nokia.com>,
        <Miguel.A.Garcia@ericsson.com>
Cc: <Lars-Erik.Jonsson@epl.ericsson.se>, <rohc@ietf.org>
Subject: RE: SigComp Requirements (was Re: [rohc] RE: Default decompression algorithms)
Date: Wed, 27 Feb 2002 20:26:31 +0100
Message-ID: <NFBBJFHGMCFINEMHAMBGGEIMHHAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-reply-to: <76C92FBBFB58D411AE760090271ED4186F9FDB@rsys002a.roke.co.uk>
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

> The minimum hash size of 9 bytes only applies to algorithms (and other
kinds of
> state information) that are downloaded to the UDVM and stored on the fly.
In
> the case of well-known algorithms that have been documented somewhere the
> state identifier for the algorithm can be any length and any value - after
all
> there's no point keeping an algorithm secret if it's in an Internet Draft!
>
> For example, the following list of 1-byte state identifiers might be
reserved:
>
> ID    Corresponding algorithm
>
> 0          UNCOMPRESSED
> 1          DEFLATE
> 2          LZO
> 3          LZJH
> 4          EPIC
> :            :
>
> The IETF doesn't need to define the above list - the task can be left to
3GPP,
> if they believe the effort to be worthwhile.

Richard,

this is not state referencing in the sense it is being used in the UDVM
draft.
(It's not a hash, either.)
I'm not quite sure I understand your mechanism, but it seems to be the
worst-of-worlds between the existing state identifier mechanism and a
registration-based mechanism, in the sense that it inherits all problems of
both and then some more.

I'm strongly opposed to adding new mechanisms of this kind at this stage.
(I also have a lot of problems with the approach, which I already have
detailed on this list, but this does not matter at this point.)

Gruesse, Carsten

PS.: As with all messages on Sigcomp this week, the above was written with
my WG member hat on; as I'm getting involved in the details, I'll have to
leave the WG hat to Lars-Erik on this.


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


From rohc-admin@ietf.org  Wed Feb 27 15:41: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 PAA16765
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 15:41:32 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA27414;
	Wed, 27 Feb 2002 15:36:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA27383
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 15:36:31 -0500 (EST)
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 PAA16448
	for <rohc@ietf.org>; Wed, 27 Feb 2002 15:36:26 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g1RKabZ29828
	for <rohc@ietf.org>; Wed, 27 Feb 2002 22:36:38 +0200 (EET)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T595625887eac158f24077@esvir04nok.ntc.nokia.com>;
 Wed, 27 Feb 2002 22:36:29 +0200
Received: from daebh001.NOE.Nokia.com ([172.18.242.231]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779);
	 Wed, 27 Feb 2002 22:36:28 +0200
Received: from daebe005.NOE.Nokia.com ([172.18.242.203]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Wed, 27 Feb 2002 14:35:47 -0600
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: SigComp Requirements (was Re: [rohc] RE: Default decompression algorithms)
Date: Wed, 27 Feb 2002 14:35:46 -0600
Message-ID: <DE0842B293FC4847992F9EDF8D72E1ED24A26A@daebe005.NOE.Nokia.com>
Thread-Topic: SigComp Requirements (was Re: [rohc] RE: Default decompression algorithms)
Thread-Index: AcG/uAT6dN6462GmR3a7iOHSfwDE6wAEVQiw
To: <richard.price@roke.co.uk>, <Miguel.A.Garcia@ericsson.com>, <cabo@tzi.org>
Cc: <Lars-Erik.Jonsson@epl.ericsson.se>, <rohc@ietf.org>
X-OriginalArrivalTime: 27 Feb 2002 20:35:47.0019 (UTC) FILETIME=[560179B0:01C1BFCE]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id PAA27384
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

Richard,

Re your comments on where to put the text, I don't think
adding it to the SigComp draft will slow things down. 
Technically, it is simple (adding two fields to the 
capability announcement block). What we need to agree
is if it is useful.

Re the "1-byte state identifiers", I would rather prefer
using hash as in my original proposal. Carsten already
commented on this. Below are detailed reasons from me:

- Statically assigned ID needs to be standardized somewhere
(either 3GPP or IETF). Hash does not.

- Hash is more generic and "algorithm blind". It does not 
matter how the decompression code is obtained by the decompressor,
whether it is documented somewhere (case 1) or it is 
previously uploaded from a compressor (case 2).

- Hash is virtually a CRC on the decompression code so that
both ends can be confident they hold the same piece of code.
Any corruption in the hash value (e.g. due to transmission
errors) or code itself can be detected.

BR,
Zhigang

> -----Original Message-----
> From: ext Price, Richard [mailto:richard.price@roke.co.uk]
> Sent: February 27, 2002 11:55 AM
> To: Liu Zhigang.C (NRC/Dallas); Miguel.A.Garcia@ericsson.com;
> cabo@tzi.org
> Cc: Lars-Erik.Jonsson@epl.ericsson.se; rohc@ietf.org
> Subject: RE: SigComp Requirements (was Re: [rohc] RE: Default
> decompression algorithms)
> 
> 
> Hi,
> 
> Just a few comments on your summary of the "algorithm 
> announcement" debate.
> 
> Regards,
> 
> Richard
> 
> 
> > Just try to make things simple:
> > 
> > 1) The major (if not only one) requirement of SigComp 
> > is to reduce latency. I agree with Carsten.
> >
> > 2) Here we are talking about a simple optimization to
> > reduce the latency. Does anyone has comment on it?
> > 
> http://www1.ietf.org/mail-archive/working-groups/rohc/current/
> msg00065.html
> 
> My only comment is that since the mechanisms needed for 
> "algorithm announcement"
> are already built into SigComp, I can't see any reason *not* 
> to make this
> functionality available to implementers.
> 
> Should the above text be placed in the SigComp draft itself, 
> or should a
> separate "Implementer's Guide" draft be considered? The 
> latter approach might be
> very useful for getting SigComp standardised more quickly. 
> The draft already
> contains a lot of text that explains how the technical 
> mechanisms might be used;
> this is valuable for implementers but doesn't need to be 
> standardised per se.
> 
> I think that it would be OK to have an implementer's guide in 
> Internet Draft
> form for now, and then publish it later when there's less 
> time pressure (perhaps
> as an Informational RFC, or perhaps by folding it into the 
> SigComp RFC when it
> reaches Draft Standard).
> 
> > 3) Now, the question is cost/gain evaluation. I've made 
> some attempt in
> > 
http://www1.ietf.org/mail-archive/working-groups/rohc/current/msg00064.html.
> Comment? The hash size might be increased to 9 bytes (?).

The minimum hash size of 9 bytes only applies to algorithms (and other kinds of
state information) that are downloaded to the UDVM and stored on the fly. In
the case of well-known algorithms that have been documented somewhere the
state identifier for the algorithm can be any length and any value - after all
there's no point keeping an algorithm secret if it's in an Internet Draft!

For example, the following list of 1-byte state identifiers might be reserved:

ID    Corresponding algorithm

0          UNCOMPRESSED
1          DEFLATE
2          LZO
3          LZJH
4          EPIC
:            :

The IETF doesn't need to define the above list - the task can be left to 3GPP,
if they believe the effort to be worthwhile.

> 4) Also, what about security? I don't see it is a problem
> as long as the use of feedback (capability announcement)
> does not create new risk. But do I missed something?

Since the needed mechanisms are already provided by SigComp, the use of
"algorithm announcement" doesn't create any new security risks that we
don't already have.

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


From rohc-admin@ietf.org  Wed Feb 27 18:18: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 SAA23853
	for <rohc-archive@odin.ietf.org>; Wed, 27 Feb 2002 18:18:29 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA06962;
	Wed, 27 Feb 2002 18:05:30 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA06931
	for <rohc@optimus.ietf.org>; Wed, 27 Feb 2002 18:05:28 -0500 (EST)
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 SAA23587
	for <rohc@ietf.org>; Wed, 27 Feb 2002 18:05:24 -0500 (EST)
Received: from cabo3 (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with SMTP id g1RN5NI06918;
	Thu, 28 Feb 2002 00:05:23 +0100 (MET)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Cc: <rohc@ietf.org>
Subject: RE: [rohc] Making SigComp recognizable
Date: Thu, 28 Feb 2002 00:05:21 +0100
Message-ID: <NFBBJFHGMCFINEMHAMBGOEIOHHAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-reply-to: <3C7C9B74.D5049D3F@ericsson.com>
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

Miguel,

I wasn't even talking about port numbers.
Making compressed packets recognizable might be used in lieu of other
multiplexing, but it does not preclude using other multiplexing.

> So far, my understanding is that SigComp is a shim layer that is
> reused by
> many applications that are running on the same host. As such, the SigComp
> layer software is used by SIP, HTTP, RTSP, etc.

I believe this is the general consensus in the WG (although HTTP may be
stretching "signaling" a bit).

> Therefore, I see that if the SigComp layer should not be aware of the
> parsing rules of any protocol running on top. I wouldn't like to see
> SigComp parsing message to distinguish whether they are SIP, HTTP or RTSP.

I believe that compressors and/or user dictionaries might well want to be
aware of the specific protocol being used.
SigComp the protocol (and the decompressor UDVM) should not have to, I
agree.

> And I would like to use a shim layer that I can instantiate per
> application.

I'm not sure if you are saying this on a conceptual level or on an
implementation level.
On an implementation level, you do need a little help from the application
to decide whether to grant state establishment requests or not.
So there already is a slightly tighter coupling between SigComp and
application than we originally thought.

> That's why my assumption was always that SIP/SigComp will be listening to
> a determined port number, HTTP/SigComp will be listening to
> another, and so on.
> Those port numbers are different than the respective non
> compressed applications.

This is one way of doing the multiplexing.
SigComp is currently neither precluding nor specifically supporting this
way.

> Option a above [sharing a port] is a very bad design choice. Multiplexing
two different
> protocols into the same port number, just because it happens that one of
> the protocols carries payload of the other, it is IMHO, a bad design
> decision. It implicitly requires that the "shim" layer is heavily
> integrated
> into the application. This prevents me to design a shim layer
> that is reusable
> by many application protocols.

I'm sure there are ways for a modular implementation even in the absence of
port number multiplexing.
SigComp could be a library; it could be a separate process ("proxy"-style).

> As an example, somebody could argue that why don't we send SIP messages to
> port number 25 (SMTP). They are all both text messages, so, why do we need
> port numbers to differentiate the protocol???

SIP messages and SMTP messages go to different applications.
SIP-uncompressed and SIP-compressed messages go to the same app.

> I would like to have a deterministic way to trace messages in a network,
> and see by the destination port number whether the message is compressed
> or not, and whether the message is syntactically correct or not.

I'm all for self-describing packets [insert my usual lament about UDP not
having protocol identifiers here].
As you don't necessarily know the port usage of an end-system in a monitor,
this is one more reason to make SigComp packets recognizable from
uncompressed packets.
(For a monitor, you would want to have a more distinguishing signature.  I
was not arguing for that simply to save bytes.)

> My suggestion, humble though, is to keep the assumption that SigComp is a
> protocol by itself, and it has to be identified by a port number,
> different
> from the port number of the application that is carried within SigComp
> (option b). Note that there is not need to standardize a well know port
> number for SigComp. We can rely on NAPTR/SRV in DNS to do this job.

Now this is actually an interesting discussion, which is going beyond the
charter of ROHC alone.
Remember that compressed vs. uncompressed is not the only parameter here, we
also have secure vs. non-secured.
I don't believe we can completely solve the general SIP variant discovery
problem in time for 3GPP R5, so it seems prudent to cater for as many
possible outcomes as possible.

Making SigComp packets recognizable comes at a cost of 5 bits (if my
proposal works right).
A small price to pay for more future flexibility.

Gruesse, Carsten


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


From rohc-admin@ietf.org  Thu Feb 28 02:22: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 CAA13455
	for <rohc-archive@odin.ietf.org>; Thu, 28 Feb 2002 02:22:48 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA09204;
	Thu, 28 Feb 2002 02:17:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA09170
	for <rohc@ns.ietf.org>; Thu, 28 Feb 2002 02:17:27 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.46])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13422
	for <rohc@ietf.org>; Thu, 28 Feb 2002 02:17:24 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g1S7HOZc007145;
	Thu, 28 Feb 2002 08:17:24 +0100 (MET)
Received: from ericsson.com (3NJPI0013L1IJOG.lmf.ericsson.se [131.160.30.42])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g1S7HDmK013933;
	Thu, 28 Feb 2002 09:17:24 +0200 (EET)
Message-ID: <3C7DD9B5.368FF65F@ericsson.com>
Date: Thu, 28 Feb 2002 09:18:13 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Organization: OY LM Ericsson AB
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: es,en
MIME-Version: 1.0
To: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
CC: rohc@ietf.org
Subject: Re: SigComp Requirements (was Re: [rohc] RE: Default decompression  
 algorithms)
References: <A943FD84BD9ED41193460008C791805003E31E4F@ESEALNT419.al.sw.ericsson.se>
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

"Lars-Erik Jonsson (EPL)" wrote:
> 
> Miguel,
> 
> Here are some immediate comments on these requirements.
> 
[snip]

> 6.5.5 Default algorithm for SIP compression
> 
>    If SIP signaling compression is used, a default algorithm must be
>    supported by the UA and the network elements involved for compression.
> 
> -> LEJ: Why?? We are currently having a discussion about this on the list,
>    and we will see what the outcome will be. ROHC is not at all discussing
>    algorithms, and will therefore not define any default algorithm. What is
>    still under consideration is whether we should provide mechanisms to
>    announce decompressor-supported algorithms. However, the usefulness of
>    this is still not clearly proven, and if we want to support this we must
>    consider the security aspects of it and the added complexity of the
>    solution.

<miguel>
Yes, I fully agree with you. This is not a requirement. It is a solution to
a requirement that is not stated, and I don't know which one is that.

However, not all the authors of this I-D are able to differentiate a 
requirement from a solution. This is the reason why the text in there 
remains.

Just for your information, this is not the only place in the document where
we are mixing requirements with solutions. I have been trying to convince 
the others that requiring a solution without stating the requirement has
no sense... But I need to keep on trying.

As a short term solution, I would recommend the ROHC WG to answer to this
requirement: "In IETF we have taken the decision to not standardize a 
default algorithm. If other organizations, such as 3GPP want to standardize
a default algorithm in their networks, that's fine".
</miguel>

> 
> 
> 6.5.6 Compression Negotiation
> 
>    There must be a mechanism to negotiate between the UA and the first
>    SIP outbound proxy the compression algorithm to be used. The type of
>    negotiation mechanism that should be implemented is that the UAC
>    includes a list of compression algorithms and the first SIP outbound
>    proxy responds with the selected one. Subsequent SIP messages are
>    compressed based on the agreed algorithm.
> 
> -> LEJ: This is not a requirement, its is a proposed solution/mechanism.
>    Further, only the Proxy->UA traffic direction is addressed above.

<miguel>
The first sentence is a requirement. The rest is just additional information
or suggestions. I understand that "The type of negotiation mechanism that 
should be implemented is that the UAC includes a list of compression ..."
it is a solution, not a requirement.

I agree with you that this paragraph is considering only the case of the UA
to the Proxy, and not viceversa. Perhaps when these requriments were written
most people were thinking of a bidirectional case, so negotiation and compression
in one direction will imply the same results in the reverse direction.
</miguel>

/Miguel


> 
> >
> > A group of individuals collected the 3GPP requirements
> > related to SIP and
> > write them down in an Internet Draft,
> >
> > http://search.ietf.org/internet-drafts/draft-garcia-sipping-3g
> > pp-reqs-02.txt
> >
> > Version -03 is on its way and will be submitted before the
> > deadline to MN.
> >
> > I will encourage to read the actual section 6.5 in that
> > document. There are
> > several requirements affecting compression.
> >
> > I will also recommend to read requirements 6.1.1 and 6.1.2.
> > Although these
> > are general requirements, they are applicable to all the rest of the
> > requirements and possible solutions.
> >
> > /Miguel

-- 
Miguel-Angel Garcia                     Oy LM Ericsson AB
                                        Jorvas, Finland
mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 5140002

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


From rohc-admin@ietf.org  Thu Feb 28 02:31: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 CAA13594
	for <rohc-archive@odin.ietf.org>; Thu, 28 Feb 2002 02:31:33 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA09589;
	Thu, 28 Feb 2002 02:29:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA09561
	for <rohc@ns.ietf.org>; Thu, 28 Feb 2002 02:29:08 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13535
	for <rohc@ietf.org>; Thu, 28 Feb 2002 02:29:04 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g1S7T0B16825;
	Thu, 28 Feb 2002 08:29:00 +0100 (MET)
Received: from ericsson.com (3NJPI0013L1IJOG.lmf.ericsson.se [131.160.30.42])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g1S7SxmK015911;
	Thu, 28 Feb 2002 09:29:00 +0200 (EET)
Message-ID: <3C7DDC77.6611CCD@ericsson.com>
Date: Thu, 28 Feb 2002 09:29:59 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Organization: OY LM Ericsson AB
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: es,en
MIME-Version: 1.0
To: "Price, Richard" <richard.price@roke.co.uk>
CC: "Dr. Carsten Bormann" <cabo@tzi.org>, zhigang.c.liu@nokia.com,
        "'Lars-Erik Jonsson (EPL)'" <Lars-Erik.Jonsson@epl.ericsson.se>,
        rohc@ietf.org
Subject: Re: SigComp Requirements (was Re: [rohc] RE: Default decompression 
 algorithms)
References: <76C92FBBFB58D411AE760090271ED4186F9FD9@rsys002a.roke.co.uk>
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

"Price, Richard" wrote:
> 
> Hi Miguel and Carsten,
> 
> Just got back from holiday - mind if I join in this interesting
> discussion? I'd be grateful for an answer to the following two
> questions:
> 
> Miguel: Is it important from a technical perspective for 3GPP to
> have an algorithm negotiation mechanism?

Yes, it is important. Definitely. We don't want to stick to a 
single algorythm that is deployed to millions of terminals forever.
The software in those terminals are not easy to upgrade.
Further more, my personal opinion is that 3GPP should not enter the
battle of standardizing a default algorythm, and that should be left
open for the mobile manufactures. Sigcomp-04 is a nice framework,
as it allows the negotiation of the algorithm.

> 
> Section 6.5.6 of the 3GPP requirements draft seems to specify a
> solution rather than a requirement, in the sense that entities
> external to SigComp don't know (or care) whether a negotiation
> mechanism is being employed. Surely what is more important is the
> technical performance of the solution, measured using some or all
> of the following:
> 
> *   Call setup time
> *   Processing requirements
> *   Memory requirements
> *   Standardisation effort
> *   Implementation effort
> *   IPR concerns
> *   Future-proofing
> *   Any others I've forgotten?


Yes, I commented also in a previous mail about section 6.5.6. I forgot
to mention, thouth, that yesterday all the authors decided to keep only
the first sentence: "There must be a mechanism to negotiate between the 
UA and the first SIP outbound proxy the compression algorithm to be used"

Regarding your concerns about Call Setup Time... I belive that in 3GPP
we will end up negotiating the compression during the time the mobile 
is registered/connected to the network. Therefore, that would be done
prior to setting up any call. So don't worry about Call Setup Time.

> 
> If the ROHC WG can beat the algorithm negotiation approach in terms
> of all of the above, is it still necessary to provide an algorithm
> negotiation mechanism within SigComp?

Yes, as I said before, Yes, it is a requirement. Mobile operators don't
want to restrict to a single algorythm in the network, they want
extensibility.

Removing the negotiation mechanism in SigComp is like removing the
codec negotiation in SIP.

/Miguel

> 
> Carsten: Do you have any objections to including an algorithm
> negotiation mechanism, other than the additional standardisation
> effort?
> 
> The reason I ask is that SigComp already has the ability to negotiate
> algorithms - it comes for free as part of the "state claim" mechanism
> that we provided to support explicit acks. So no additional effort is
> needed to include algorithm negotiation.
> 
> Is it OK to provide both the UDVM approach and the algorithm
> negotiation approach, and leave it to implementers to choose which to
> adopt?
> 
> Regards,
> 
> Richard
> 
> > -----Original Message-----
> > From: Miguel A. Garcia [mailto:Miguel.A.Garcia@ericsson.com]
> > Sent: Wednesday, February 27, 2002 1:53 PM
> > To: Dr. Carsten Bormann
> > Cc: zhigang.c.liu@nokia.com; rohc@ietf.org
> > Subject: Re: SigComp Requirements (was Re: [rohc] RE: Default
> > decompression algorithms)
> >
> >
> > Hi:
> >
> > No, these requirements were discussed prior to the UDVM approach.
> >
> > As I said, a new version of this draft will be shortly submitted.
> > I need to discuss with the rest of the co-authors some better wording
> > that reflects the latest assumptions in Rohc and 3GPP.
> >
> > I will announce the draft in this mailing list as well.
> >
> > /Miguel
> >
> > "Dr. Carsten Bormann" wrote:
> > >
> > > Miguel,
> > >
> > > does this list of requirements take into account the UDVM approach?
> > > It does seem to predate its adoption.
> > >
> > > Gruesse, Carsten
> >
> > --
> > Miguel-Angel Garcia                     Oy LM Ericsson AB
> >                                         Jorvas, Finland
> > mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
> > mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 5140002
> >
> > _______________________________________________
> > Rohc mailing list
> > Rohc@ietf.org
> > https://www1.ietf.org/mailman/listinfo/rohc
> >
> 
>                                                   ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>                           Name: RMRL-Disclaimer.txt
>    RMRL-Disclaimer.txt    Type: Plain Text (text/plain)
>                       Encoding: 7bit

-- 
Miguel-Angel Garcia                     Oy LM Ericsson AB
                                        Jorvas, Finland
mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 5140002

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


From rohc-admin@ietf.org  Thu Feb 28 02:43: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 CAA13789
	for <rohc-archive@odin.ietf.org>; Thu, 28 Feb 2002 02:43:17 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA10444;
	Thu, 28 Feb 2002 02:41:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA10411
	for <rohc@ns.ietf.org>; Thu, 28 Feb 2002 02:41:33 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13759
	for <rohc@ietf.org>; Thu, 28 Feb 2002 02:41:29 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g1S7fQB26287;
	Thu, 28 Feb 2002 08:41:27 +0100 (MET)
Received: from ericsson.com (3NJPI0013L1IJOG.lmf.ericsson.se [131.160.30.42])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g1S7fMmK017803;
	Thu, 28 Feb 2002 09:41:26 +0200 (EET)
Message-ID: <3C7DDF5E.E0AB8A3A@ericsson.com>
Date: Thu, 28 Feb 2002 09:42:22 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Organization: OY LM Ericsson AB
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: es,en
MIME-Version: 1.0
To: zhigang.c.liu@nokia.com
CC: richard.price@roke.co.uk, cabo@tzi.org, Lars-Erik.Jonsson@epl.ericsson.se,
        rohc@ietf.org
Subject: Re: SigComp Requirements (was Re: [rohc] RE: Default decompression 
 algorithms)
References: <DE0842B293FC4847992F9EDF8D72E1ED24A269@daebe005.NOE.Nokia.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

zhigang.c.liu@nokia.com wrote:
> 
> Hi,
> 
> Just try to make things simple:
> 
> 1) The major (if not only one) requirement of SigComp
> is to reduce latency. I agree with Carsten.

I agree. But you need to be very carefull to not cause
an extra overhead when you implement the mechanisms to
dismiss that latency. 

I am referring to the algorithm upload. If every time 
I switch a mobile phone it has to send 500 bytes of 
algorithm to its proxy, and the proxy has to do the same
in the reverse side, even in the case that both the proxy
and the terminal already contain the algorithm, then we
are doing something wrong. We are generating a lot of 
unneeded traffic over the scarce air interface.

> 
> 2) Here we are talking about a simple optimization to
> reduce the latency. Does anyone has comment on it?
> http://www1.ietf.org/mail-archive/working-groups/rohc/current/msg00065.html

I like this text, and I think it should be covered somewhere
in the next version of the Sigcomp draft.

There is a minor thing for discussion though. In step 3 you
are assuming that the compressor selects the algorithm prior
to contacint the decompressor. However, I can envision another
model where the compressor selects the algorithm to upload
once it gets the list of algorithms from the decompressor.

An example: Terminal T contacts proxy P. P sends the list of
algorithms already uploaded, let's say, 1, 2 and 7. T supports
algorithms 2 and 8. 8 is preferred for the terminal, but 
because the compression performance in 2 and 8 are similar,
and because 2 is already uploaded in P, T decides to use 2.

 
> 3) Now, the question is cost/gain evaluation. I've
> made some attempt in
> http://www1.ietf.org/mail-archive/working-groups/rohc/current/msg00064.html.
> Comment? The hash size might be increased to 9 bytes (?).

That is Ok. Obviously, anything that requires a roundtrip is 
not for free. Still, if the algorithm cost is 500 bytes, there
is a saving in bandwidth if the number of algorithms already
uploaded are not extremely high.

> 
> 4) Also, what about security? I don't see it is a problem
> as long as the use of feedback (capability announcement)
> does not create new risk. But do I missed something?

I have no opinion on this subjec.

/Miguel


> 
> BR,
> Zhigang

-- 
Miguel-Angel Garcia                     Oy LM Ericsson AB
                                        Jorvas, Finland
mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 5140002

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


From rohc-admin@ietf.org  Thu Feb 28 02:49: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 CAA13904
	for <rohc-archive@odin.ietf.org>; Thu, 28 Feb 2002 02:49:56 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA10569;
	Thu, 28 Feb 2002 02:44:59 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA10536
	for <rohc@ns.ietf.org>; Thu, 28 Feb 2002 02:44:57 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13822
	for <rohc@ietf.org>; Thu, 28 Feb 2002 02:44:53 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g1S7ioB28289;
	Thu, 28 Feb 2002 08:44:51 +0100 (MET)
Received: from ericsson.com (3NJPI0013L1IJOG.lmf.ericsson.se [131.160.30.42])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g1S7ihmK018133;
	Thu, 28 Feb 2002 09:44:43 +0200 (EET)
Message-ID: <3C7DE027.74972D22@ericsson.com>
Date: Thu, 28 Feb 2002 09:45:43 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Organization: OY LM Ericsson AB
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: es,en
MIME-Version: 1.0
To: "Price, Richard" <richard.price@roke.co.uk>
CC: "'zhigang.c.liu@nokia.com'" <zhigang.c.liu@nokia.com>, cabo@tzi.org,
        Lars-Erik.Jonsson@epl.ericsson.se, rohc@ietf.org
Subject: Re: SigComp Requirements (was Re: [rohc] RE: Default decompression 
 algorithms)
References: <76C92FBBFB58D411AE760090271ED4186F9FDB@rsys002a.roke.co.uk>
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

Richard:

Just one comment.

I understand the effort you are doing on the 1-byte state identifiers to 
identify algorithms. I trend to like it. But I am not sure if this list
should be standardize in 3GPP or in IETF. I was thinking that it should 
be in IETF. I would like to understand why IETF can't typify certain
well-known algorithms.

/Miguel

"Price, Richard" wrote:
> 
> Hi,
> 
> Just a few comments on your summary of the "algorithm announcement" debate.
> 
> Regards,
> 
> Richard
> 
> > Just try to make things simple:
> >
> > 1) The major (if not only one) requirement of SigComp
> > is to reduce latency. I agree with Carsten.
> >
> > 2) Here we are talking about a simple optimization to
> > reduce the latency. Does anyone has comment on it?
> > http://www1.ietf.org/mail-archive/working-groups/rohc/current/msg00065.html
> 
> My only comment is that since the mechanisms needed for "algorithm announcement"
> are already built into SigComp, I can't see any reason *not* to make this
> functionality available to implementers.
> 
> Should the above text be placed in the SigComp draft itself, or should a
> separate "Implementer's Guide" draft be considered? The latter approach might be
> very useful for getting SigComp standardised more quickly. The draft already
> contains a lot of text that explains how the technical mechanisms might be used;
> this is valuable for implementers but doesn't need to be standardised per se.
> 
> I think that it would be OK to have an implementer's guide in Internet Draft
> form for now, and then publish it later when there's less time pressure (perhaps
> as an Informational RFC, or perhaps by folding it into the SigComp RFC when it
> reaches Draft Standard).
> 
> > 3) Now, the question is cost/gain evaluation. I've made some attempt in
> > http://www1.ietf.org/mail-archive/working-groups/rohc/current/msg00064.html.
> > Comment? The hash size might be increased to 9 bytes (?).
> 
> The minimum hash size of 9 bytes only applies to algorithms (and other kinds of
> state information) that are downloaded to the UDVM and stored on the fly. In
> the case of well-known algorithms that have been documented somewhere the
> state identifier for the algorithm can be any length and any value - after all
> there's no point keeping an algorithm secret if it's in an Internet Draft!
> 
> For example, the following list of 1-byte state identifiers might be reserved:
> 
> ID    Corresponding algorithm
> 
> 0          UNCOMPRESSED
> 1          DEFLATE
> 2          LZO
> 3          LZJH
> 4          EPIC
> :            :
> 
> The IETF doesn't need to define the above list - the task can be left to 3GPP,
> if they believe the effort to be worthwhile.
> 
> > 4) Also, what about security? I don't see it is a problem
> > as long as the use of feedback (capability announcement)
> > does not create new risk. But do I missed something?
> 
> Since the needed mechanisms are already provided by SigComp, the use of
> "algorithm announcement" doesn't create any new security risks that we
> don't already have.
> 
>                                                   ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>                           Name: RMRL-Disclaimer.txt
>    RMRL-Disclaimer.txt    Type: Plain Text (text/plain)
>                       Encoding: 7bit

-- 
Miguel-Angel Garcia                     Oy LM Ericsson AB
                                        Jorvas, Finland
mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 5140002

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


From rohc-admin@ietf.org  Thu Feb 28 03:09:47 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 DAA14224
	for <rohc-archive@odin.ietf.org>; Thu, 28 Feb 2002 03:09:47 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA11924;
	Thu, 28 Feb 2002 03:06:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA11888
	for <rohc@ns.ietf.org>; Thu, 28 Feb 2002 03:06:20 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14184
	for <rohc@ietf.org>; Thu, 28 Feb 2002 03:06:16 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g1S86EB15613;
	Thu, 28 Feb 2002 09:06:15 +0100 (MET)
Received: from ericsson.com (3NJPI0013L1IJOG.lmf.ericsson.se [131.160.30.42])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g1S86DmK019806;
	Thu, 28 Feb 2002 10:06:13 +0200 (EET)
Message-ID: <3C7DE531.9E53FB45@ericsson.com>
Date: Thu, 28 Feb 2002 10:07:13 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Organization: OY LM Ericsson AB
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: es,en
MIME-Version: 1.0
To: "Dr. Carsten Bormann" <cabo@tzi.org>
CC: rohc@ietf.org
Subject: Re: [rohc] Making SigComp recognizable
References: <NFBBJFHGMCFINEMHAMBGOEIOHHAA.cabo@tzi.org>
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

"Dr. Carsten Bormann" wrote:
> 
> Miguel,
> 
> I wasn't even talking about port numbers.
> Making compressed packets recognizable might be used in lieu of other
> multiplexing, but it does not preclude using other multiplexing.

<miguel>

So why do you want to make packets recognizable?

</miguel>

> 
> > So far, my understanding is that SigComp is a shim layer that is
> > reused by
> > many applications that are running on the same host. As such, the SigComp
> > layer software is used by SIP, HTTP, RTSP, etc.
> 
> I believe this is the general consensus in the WG (although HTTP may be
> stretching "signaling" a bit).
> 
> > Therefore, I see that if the SigComp layer should not be aware of the
> > parsing rules of any protocol running on top. I wouldn't like to see
> > SigComp parsing message to distinguish whether they are SIP, HTTP or RTSP.
> 
> I believe that compressors and/or user dictionaries might well want to be
> aware of the specific protocol being used.
> SigComp the protocol (and the decompressor UDVM) should not have to, I
> agree.
> 
> > And I would like to use a shim layer that I can instantiate per
> > application.
> 
> I'm not sure if you are saying this on a conceptual level or on an
> implementation level.
> On an implementation level, you do need a little help from the application
> to decide whether to grant state establishment requests or not.
> So there already is a slightly tighter coupling between SigComp and
> application than we originally thought.

<miguel>
I was thinking of an application that instantiates a SigComp layer 
optimized (e.g., dictionaries loaded) for that particular application.
The SigComp code is still the same. It is just invoked with certain
parameters to load certain dictionaries.

I agree with you that there is a need for an API between the SigComp
layer and the application. That is an internal API and we don't need
to mention here in ROHC, although somebody could write an informational
internet draft with a suggested API (like it happened with SCTP).

</miguel>

> 
> > That's why my assumption was always that SIP/SigComp will be listening to
> > a determined port number, HTTP/SigComp will be listening to
> > another, and so on.
> > Those port numbers are different than the respective non
> > compressed applications.
> 
> This is one way of doing the multiplexing.
> SigComp is currently neither precluding nor specifically supporting this
> way.

<miguel>

Ok, so then my question comes back, why is there a need to differentiate
the SigComp messages from others, if we can differentiate them by the port
number?

</miguel>

> 
> > Option a above [sharing a port] is a very bad design choice. Multiplexing
> two different
> > protocols into the same port number, just because it happens that one of
> > the protocols carries payload of the other, it is IMHO, a bad design
> > decision. It implicitly requires that the "shim" layer is heavily
> > integrated
> > into the application. This prevents me to design a shim layer
> > that is reusable
> > by many application protocols.
> 
> I'm sure there are ways for a modular implementation even in the absence of
> port number multiplexing.
> SigComp could be a library; it could be a separate process ("proxy"-style).
> 
> > As an example, somebody could argue that why don't we send SIP messages to
> > port number 25 (SMTP). They are all both text messages, so, why do we need
> > port numbers to differentiate the protocol???
> 
> SIP messages and SMTP messages go to different applications.
> SIP-uncompressed and SIP-compressed messages go to the same app.

<miguel>
I disagree. This is a fundamental difference between our visions. SIP uncompressed
and SIP compressed EVENTUALLY reach the same application. But, just eventually.
SIP-Compressed messages can't be treated by the SIP layer without any help from
the SigComp layer. It does not matter whether the message is, at the end of the
day, received by the same applicaiton layer. If it was compressed, that layer 
is not able to do anything with it.

SigComp also defines some negotiation mechanisms that have nothing to do with
the application layer. SigComp is a protocol per se.
</miguel>

> 
> > I would like to have a deterministic way to trace messages in a network,
> > and see by the destination port number whether the message is compressed
> > or not, and whether the message is syntactically correct or not.
> 
> I'm all for self-describing packets [insert my usual lament about UDP not
> having protocol identifiers here].
> As you don't necessarily know the port usage of an end-system in a monitor,
> this is one more reason to make SigComp packets recognizable from
> uncompressed packets.
> (For a monitor, you would want to have a more distinguishing signature.  I
> was not arguing for that simply to save bytes.)
> 
> > My suggestion, humble though, is to keep the assumption that SigComp is a
> > protocol by itself, and it has to be identified by a port number,
> > different
> > from the port number of the application that is carried within SigComp
> > (option b). Note that there is not need to standardize a well know port
> > number for SigComp. We can rely on NAPTR/SRV in DNS to do this job.
> 
> Now this is actually an interesting discussion, which is going beyond the
> charter of ROHC alone.
> Remember that compressed vs. uncompressed is not the only parameter here, we
> also have secure vs. non-secured.
> I don't believe we can completely solve the general SIP variant discovery
> problem in time for 3GPP R5, so it seems prudent to cater for as many
> possible outcomes as possible.
> 
> Making SigComp packets recognizable comes at a cost of 5 bits (if my
> proposal works right).
> A small price to pay for more future flexibility.
> 
> Gruesse, Carsten

-- 
Miguel-Angel Garcia                     Oy LM Ericsson AB
                                        Jorvas, Finland
mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 5140002

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


From rohc-admin@ietf.org  Thu Feb 28 03:45: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 DAA14660
	for <rohc-archive@odin.ietf.org>; Thu, 28 Feb 2002 03:45:00 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA13508;
	Thu, 28 Feb 2002 03:37:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA13481
	for <rohc@ns.ietf.org>; Thu, 28 Feb 2002 03:37:32 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14537
	for <rohc@ietf.org>; Thu, 28 Feb 2002 03:37:28 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g1S8bVB10808
	for <rohc@ietf.org>; Thu, 28 Feb 2002 09:37:31 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt461 ; Thu Feb 28 09:35:55 2002 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <F4G2H5KT>; Thu, 28 Feb 2002 09:26:13 +0100
Message-ID: <A943FD84BD9ED41193460008C791805003E31E54@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (EPL)" <Lars-Erik.Jonsson@epl.ericsson.se>
To: "'Miguel A. Garcia'" <Miguel.A.Garcia@ericsson.com>
Cc: rohc@ietf.org
Subject: RE: SigComp Requirements (was Re: [rohc] RE: Default decompressio
	n  algorithms)
Date: Thu, 28 Feb 2002 09:12:13 +0100
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

> > RP: Is it important from a technical perspective for 3GPP to
> > have an algorithm negotiation mechanism?
> 
> MG: Yes, it is important. Definitely. We don't want to stick to a 
> single algorithm that is deployed to millions of terminals forever.

OK, and with the UDVM-approach, you can use any algorithm at any time.


> > RP: If the ROHC WG can beat the algorithm negotiation approach in terms
> > of all of the above, is it still necessary to provide an algorithm
> > negotiation mechanism within SigComp?
> 
> MG: Yes, as I said before, Yes, it is a requirement. Mobile 
> operators don't want to restrict to a single algorithm in
> the network, they want extensibility
> 
> Removing the negotiation mechanism in SigComp is like removing the
> codec negotiation in SIP.

The UDVM provides you with total flexibility regarding compression
algorithm, and you do not necessary need an explicit negotiation 
mechanism.

/L-E
 

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


From rohc-admin@ietf.org  Thu Feb 28 08:27: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 IAA21831
	for <rohc-archive@odin.ietf.org>; Thu, 28 Feb 2002 08:27:49 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA28387;
	Thu, 28 Feb 2002 08:24:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA28355
	for <rohc@ns.ietf.org>; Thu, 28 Feb 2002 08:24:53 -0500 (EST)
Received: from marjan.fesb.hr (root@marjan.fesb.hr [161.53.166.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21687
	for <rohc@ietf.org>; Thu, 28 Feb 2002 08:24:40 -0500 (EST)
Received: (from root@localhost)
	by marjan.fesb.hr (8.9.3/8.9.3) id OAA12511
	for rohc@ietf.org; Thu, 28 Feb 2002 14:24:25 +0100 (MET)
Received: from fesb.hr (demorgan.bit.fesb.hr [161.53.169.245])
	by marjan.fesb.hr (8.9.3/8.9.3) with ESMTP id OAA12466;
	Thu, 28 Feb 2002 14:23:22 +0100 (MET)
Message-ID: <3C7E2FA3.4050608@fesb.hr>
Date: Thu, 28 Feb 2002 14:24:51 +0100
From: Julije Ozegovic <julije@fesb.hr>
Organization: FESB Split
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1
X-Accept-Language: en, hr
MIME-Version: 1.0
To: "West, Mark (ITN)" <mark.a.west@roke.co.uk>
CC: rohc <rohc@ietf.org>
Subject: Re: [rohc] TCP/IP EPIC profile
References: <3C7BF6E0.9070307@fesb.hr> <3C7D1823.7070003@roke.co.uk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS perl-11
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 Mark,

thank you for comments. Here I want to clarify some of my questions.

First of all, I think that TCP/IP header compression is needed. 
Also I think that EPIC(-lite) high level "compression definition 
language" is right approach. Also, I support EPIC "protocol 
independence". However, all this did motivate me for profile 
'expansion'.

EPIC provides total freedom of profile writing, when profile 
author has possibility to deal with header on bit-by-bit basis.

Detailed profiles tend to result in complex applications/protocols.

Just to remember, Internet is major technology today because of 
its simplicity: IP routers are more efficient than X.25 or ATM 
ones (for the same technology).

In my opinion, central point is to write profiles that will give 
optimal trade-off between complexity and compression efficiency. 
I think that profile in <draft-ietf-rohc-tcp-00.txt> is not one 
of that kind.

When writing profiles, authors should keep in mind that headers 
to be compressed are just lists of fields, and that 
compressor/decomressor actually treat them as such. This can 
provide simple and computation efficient profiles.

Now about some questions/answers:

** NBO:

can we introduce something like SWAP-LSB in the toolbox and let 
normal method choice take place, e.g.:

    IP_ID = LSB(80%,x,y) | SWAP-LSB(20%,x,y)

** Comments:

in the proposed profile, some important information is contained 
in comments. That implies that syntax is not stable yet. Since 
we try to implement EPIC-lite TCP/IP compression, input syntax 
changes force us to change "profile compiler" on weekly basis - 
lot of frustration results :)

** FORMAT in CO:
    actually was FORMAT SELECTOR in CO:

When transmitting CO packet, compressor is using the same format 
set that has already been communicated to decompressor through 
the IR/DYN packet. It is obsolete to send this selector in CO 
packet, because decompressor should be informed in forward, to 
be able to decompress the header... STATIC test is obsolete too, 
because it will fail on multiple contexts, so compressor must 
erase all previous contexts (if any) when changing to another 
format set.

** difference in FORMAT between CO/IR/DYN:

by draft, all methods in format should be available for IR/DYN 
processing. This means that:

field = FORMAT((method1 | method2);(method3 | method4))

should be in IR/DYN interpreted as:

field = (method1 | method2 | method3 | method4)

Consequences are:
   - FORMAT should be the same in all three profiles (CO/IR/DYN)
   - NO format selector is needed, i.e. "method3" when selected
     in IR/DYN implies second format set
   - since "choose" in most applications simply tries one by one
     method from the list, IRREGULAR should not be included
     before the last method (i.e. only "method4" can be
     IRREGULAR), otherwise methods after IRREGULAR
     will newer be chosen

** ack STACK-TO-CONTROL not defined

since following exists in the profile (although not used):

    get-seq-ack      =   ROTATE(2,1)
                         STACK-FROM-CONTROL(2) ; cwr/ece
                         ROTATE(4,1)
                         STACK-FROM-CONTROL(2) ; ecn
                         STACK-FROM-CONTROL(32) ; ack
                         STACK-FROM-CONTROL(32) ; seq

ack and sack should be pushed before :)

Cheers,
Julije



West, Mark (ITN) wrote:

> 
> Hi Julije,
> 
> I've just waded through your comments on the 'expanded' profile, and 
> I'll try and summarise the points you raise and make some comments...
> 
> - IP checksum treated later / INFERRED-IP-CHECKSUM not defined
> 
> The current draft does not define INFERRED-IP-CHECKSUM.  (It was defined 
> in an older 'EPIC for TCP' draft, but I realise that's not much help!) 
> It is in the new version that will be submitted this week, though.
> When you see how this works, you will appreciate that the IP checksum is 
> not actually treated later, but simply ignored.  (On compression, 
> INFERRED-IP-CHECKSUM sets the checksum bits to 0; on decompression is 
> fills them in with the computed checksum).
> 
> 
> - NBO not in the toolbox
> 
> Again, true.  We have removed INFERRED-SCALED and replaced it with NBO 
> and SCALE operations, which gives more flexibility.  Again, these are 
> described in the draft that will be submitted.  (I agree that it might 
> have been nice to synchronise things a little better...)
> 
> 
> - Some percentages don't add up to 100%
> 
> That's what we profile writers refer to as a 'mistake' ;-)
> Actually, it shouldn't matter - but it should be fixed!
> 
> 
> - Compiler should read comments or what?
> 
> Well, the compiler is free to read the comments.  But it probably ought 
> to ignore what they say...
> 
> 
> - Various mis-named method names
> 
> Sorry - these are typos and need to be fixed.
> 
> 
> - Various unused methods
> 
> Again, they should be referenced so this is an error in the profile.
> 
> 
> - FORMAT appears in 'CO' packet
> 
> Yes, it certainly does.  Otherwise, how would you know what different 
> formats to build?  I don't quite see the problem here...
> 
> 
> - ack STACK-TO-CONTROL not defined
> - psh STACK-TO-CONTROL not defined
> 
> I don't understand the comments.
> 
> 
> - skip-msn is not defined (but self-explanatory)
> 
> Tend to agree!  (This is, of course, a TCP specific method and should be 
> defined along with the profile).
> 
> 
> - An IRREGULAR(16,100%) is used to encode a format selector
> 
> This should be IRREGULAR(1,100%) - it's a typo...
> 
> 
> - Not clear what is being encoded at each point
> 
> This could be overcome by better commenting (whether or not the compiler 
> reads them) or splitting up the methods to a finer granularity.  This 
> should be taken care of in the profile, though, I agree.
> 
> Cheers,
> 
> Mark.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> 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.
> 
> RMRL-Disclaimer.txt
> 
> Content-Type:
> 
> text/plain
> Content-Encoding:
> 
> 7bit
> 
> 



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


From rohc-admin@ietf.org  Thu Feb 28 10:01: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 KAA26772
	for <rohc-archive@odin.ietf.org>; Thu, 28 Feb 2002 10:01:29 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA04232;
	Thu, 28 Feb 2002 09:58:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA04205
	for <rohc@optimus.ietf.org>; Thu, 28 Feb 2002 09:58:20 -0500 (EST)
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 JAA26527
	for <rohc@ietf.org>; Thu, 28 Feb 2002 09:58:16 -0500 (EST)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <1S9WNV8C>; Thu, 28 Feb 2002 14:55:08 -0000
Message-ID: <76C92FBBFB58D411AE760090271ED4186F9FDD@rsys002a.roke.co.uk>
From: "Price, Richard" <richard.price@roke.co.uk>
To: "'Dr. Carsten Bormann'" <cabo@tzi.org>, zhigang.c.liu@nokia.com,
        Miguel.A.Garcia@ericsson.com
Cc: Lars-Erik.Jonsson@epl.ericsson.se, rohc@ietf.org
Subject: RE: SigComp Requirements (was Re: [rohc] RE: Default decompressio
	n algorithms)
Date: Thu, 28 Feb 2002 14:55:04 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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-1"

> this is not state referencing in the sense it is being used in the UDVM draft.
> (It's not a hash, either.)

Carsten,

I don't understand - what did I propose that contradicts the current SigComp/UDVM
draft?

The key point of my suggestion for how to do algorithm negotiation is that it
only uses mechanisms that are already contained in SigComp (namely "state
referencing" and "state claim"). In fact the mechanisms were originally introduced
for other reasons, but if we can use them to provide algorithm negotiation as well
then so much the better.

> I'm not quite sure I understand your mechanism, but it seems to be the
> worst-of-worlds between the existing state identifier mechanism and a
> registration-based mechanism, in the sense that it inherits all problems of
> both and then some more.

I'm not proposing a new mechanism per se; I'm simply configuring SigComp to
support algorithm negotiation by setting the application-defined parameters of
Section 3.2. In particular, this means that the final decision on whether to use
algorithm negotiation is made by 3GPP.

I make no statement as to whether algorithm negotiation is a good idea or a bad
idea. However, it's important to point out that algorithm negotiation can already
be done within the existing SigComp framework, so that we avoid a debate on
whether we need to add it or not.

> I'm strongly opposed to adding new mechanisms of this kind at this stage.

Nothing needs to be added to SigComp in order to support my proposal.

> (I also have a lot of problems with the approach, which I already have
> detailed on this list, but this does not matter at this point.)

Agreed. Algorithm negotiation is a controversial issue within the ROHC WG, and
we'll end up delaying SigComp if we debate its merits at this late stage.

Regards,

Richard

--------------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 Feb 28 10:04: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 KAA26940
	for <rohc-archive@odin.ietf.org>; Thu, 28 Feb 2002 10:04:55 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04918;
	Thu, 28 Feb 2002 10:02:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04885
	for <rohc@optimus.ietf.org>; Thu, 28 Feb 2002 10:02:32 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26831
	for <rohc@ietf.org>; Thu, 28 Feb 2002 10:02:25 -0500 (EST)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id g1SF2NB07926;
	Thu, 28 Feb 2002 16:02:23 +0100 (MET)
Received: from ericsson.com (3NJPI0013L1IJOG.lmf.ericsson.se [131.160.30.42])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g1SF2NmK018695;
	Thu, 28 Feb 2002 17:02:23 +0200 (EET)
Message-ID: <3C7E46BA.E4490D28@ericsson.com>
Date: Thu, 28 Feb 2002 17:03:22 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Organization: OY LM Ericsson AB
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: es,en
MIME-Version: 1.0
To: "Price, Richard" <richard.price@roke.co.uk>
CC: "'Dr. Carsten Bormann'" <cabo@tzi.org>, zhigang.c.liu@nokia.com,
        Lars-Erik.Jonsson@epl.ericsson.se, rohc@ietf.org
Subject: Re: SigComp Requirements (was Re: [rohc] RE: Default decompression 
 algorithms)
References: <76C92FBBFB58D411AE760090271ED4186F9FDD@rsys002a.roke.co.uk>
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

Richard:

As I have been involved in these discussions, I noticed that I made a small 
mistake with the terminology.

At least, I have been always thinking of "algorithm announcement", rather than
"algorithm negotiation".

I am not sure if you mean "negotiation" or "announcement". At least, in my 
previous e-mails I meant that the decompressor should be able to announce 
the algorithms that are already uploaded, and therefore, don't require
a "UDVM upload" message. There is not negotiation between two parties.

/Miguel

"Price, Richard" wrote:
> 
> > this is not state referencing in the sense it is being used in the UDVM draft.
> > (It's not a hash, either.)
> 
> Carsten,
> 
> I don't understand - what did I propose that contradicts the current SigComp/UDVM
> draft?
> 
> The key point of my suggestion for how to do algorithm negotiation is that it
> only uses mechanisms that are already contained in SigComp (namely "state
> referencing" and "state claim"). In fact the mechanisms were originally introduced
> for other reasons, but if we can use them to provide algorithm negotiation as well
> then so much the better.
> 
> > I'm not quite sure I understand your mechanism, but it seems to be the
> > worst-of-worlds between the existing state identifier mechanism and a
> > registration-based mechanism, in the sense that it inherits all problems of
> > both and then some more.
> 
> I'm not proposing a new mechanism per se; I'm simply configuring SigComp to
> support algorithm negotiation by setting the application-defined parameters of
> Section 3.2. In particular, this means that the final decision on whether to use
> algorithm negotiation is made by 3GPP.
> 
> I make no statement as to whether algorithm negotiation is a good idea or a bad
> idea. However, it's important to point out that algorithm negotiation can already
> be done within the existing SigComp framework, so that we avoid a debate on
> whether we need to add it or not.
> 
> > I'm strongly opposed to adding new mechanisms of this kind at this stage.
> 
> Nothing needs to be added to SigComp in order to support my proposal.
> 
> > (I also have a lot of problems with the approach, which I already have
> > detailed on this list, but this does not matter at this point.)
> 
> Agreed. Algorithm negotiation is a controversial issue within the ROHC WG, and
> we'll end up delaying SigComp if we debate its merits at this late stage.
> 
> Regards,
> 
> Richard
> 
>                                                   ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>                           Name: RMRL-Disclaimer.txt
>    RMRL-Disclaimer.txt    Type: Plain Text (text/plain)
>                       Encoding: 7bit

-- 
Miguel-Angel Garcia                     Oy LM Ericsson AB
                                        Jorvas, Finland
mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 5140002

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


From rohc-admin@ietf.org  Thu Feb 28 10:20: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 KAA27907
	for <rohc-archive@odin.ietf.org>; Thu, 28 Feb 2002 10:20:29 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA05633;
	Thu, 28 Feb 2002 10:16:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA05599
	for <rohc@optimus.ietf.org>; Thu, 28 Feb 2002 10:16:25 -0500 (EST)
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 KAA27575
	for <rohc@ietf.org>; Thu, 28 Feb 2002 10:16:21 -0500 (EST)
Received: from cabo3 (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with SMTP id g1SFGHI00686;
	Thu, 28 Feb 2002 16:16:18 +0100 (MET)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: "Price, Richard" <richard.price@roke.co.uk>
Cc: <rohc@ietf.org>
Subject: RE: SigComp Requirements (was Re: [rohc] RE: Default decompression algorithms)
Date: Thu, 28 Feb 2002 16:16:17 +0100
Message-ID: <NFBBJFHGMCFINEMHAMBGCEJBHHAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-reply-to: <76C92FBBFB58D411AE760090271ED4186F9FDD@rsys002a.roke.co.uk>
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

> I don't understand - what did I propose that contradicts the
> current SigComp/UDVM draft?

UDVM uses state identifiers that uniquely identify state.
In UDVM, there is no need for a central organization registering state
identifiers.

I agree that the UDVM scheme already contains the mechanism that would be
needed for state announcements.
I didn't think there was a need for new mechanism, regardless of whether you
think state announcements of the "I know this and I know that" style make
sense or not.

The final decision whether to use state announcements is made by the
implementation.
This is not new, and has been part of the UDVM concept for a while.

What is new is that you are proposing to introduce a new kind of state
identifier that is inefficient from a deployment point of view as it is
based on registries.

> Nothing needs to be added to SigComp in order to support my proposal.

Not true, your new kind of state identifier has properties that differ from
UDVM state identifiers.
They are not adding capability.  Why bother?

I'd rather work on finishing the document.

Gruesse, Carsten


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


From rohc-admin@ietf.org  Thu Feb 28 11:10: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 LAA00691
	for <rohc-archive@odin.ietf.org>; Thu, 28 Feb 2002 11:10:34 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA08896;
	Thu, 28 Feb 2002 11:08:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA08864
	for <rohc@optimus.ietf.org>; Thu, 28 Feb 2002 11:08:15 -0500 (EST)
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 LAA00505
	for <rohc@ietf.org>; Thu, 28 Feb 2002 11:08:10 -0500 (EST)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <1S9WNWCP>; Thu, 28 Feb 2002 16:07:01 -0000
Message-ID: <76C92FBBFB58D411AE760090271ED4186F9FDE@rsys002a.roke.co.uk>
From: "Price, Richard" <richard.price@roke.co.uk>
To: "'Dr. Carsten Bormann'" <cabo@tzi.org>
Cc: rohc@ietf.org
Subject: RE: SigComp Requirements (was Re: [rohc] RE: Default decompressio
	n algorithms)
Date: Thu, 28 Feb 2002 16:06:53 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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-1"

> > I don't understand - what did I propose that contradicts the
> > current SigComp/UDVM draft?
> 
> UDVM uses state identifiers that uniquely identify state.
> In UDVM, there is no need for a central organization registering state
> identifiers.

For security reasons the UDVM always creates new state identifiers to be a
hash of the relevant item of state. However, when state is accessed the state
identifier is simply used as a key to retrieve the corresponding state. The
UDVM instruction for retrieving state doesn't check that the state identifier
is actually a hash of the state being retrieved - and why should it? Evaluating
the MD5 hash twice would throw away processing resources for no gain.

An implication of only evaluating the MD5 hash when the UDVM creates new
state is that if the state happens to be created externally, there is no need
for the state identifier to be a hash of the state at all. The collision
problem needs to be solved of course; having "a central organization
registering state identifiers" is one way to do this.

> > Nothing needs to be added to SigComp in order to support my proposal.
> 
> Not true, your new kind of state identifier has properties that differ from
> UDVM state identifiers. They are not adding capability.  Why bother?

As far as I can tell, the current SigComp draft does in fact allow my proposal
with no need for any modifications. Whether it *should* or not is another
matter entirely.

> I'd rather work on finishing the document.

Agreed. But since the current SigComp draft allows my proposal to be
implemented, we need to decide whether this is OK or not. Are there any
technical reasons for enforcing that application-defined state should always
be referenced by a hash?

Regards,

Richard

--------------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 Feb 28 11:22: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 LAA01455
	for <rohc-archive@odin.ietf.org>; Thu, 28 Feb 2002 11:22:51 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA09408;
	Thu, 28 Feb 2002 11:17:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA09357
	for <rohc@optimus.ietf.org>; Thu, 28 Feb 2002 11:17:40 -0500 (EST)
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 LAA01085
	for <rohc@ietf.org>; Thu, 28 Feb 2002 11:17:35 -0500 (EST)
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.1.0/Switch-2.1.0) with ESMTP id g1SGJjx26271
	for <rohc@ietf.org>; Thu, 28 Feb 2002 10:19:45 -0600 (CST)
Received: from daebh001.NOE.Nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5958a76783ac12f257079@davir04nok.americas.nokia.com>;
 Thu, 28 Feb 2002 10:17:35 -0600
Received: from daebe005.NOE.Nokia.com ([172.18.242.203]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Thu, 28 Feb 2002 10:16:47 -0600
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: SigComp Requirements (was Re: [rohc] RE: Default decompression algorithms)
Date: Thu, 28 Feb 2002 10:16:46 -0600
Message-ID: <DE0842B293FC4847992F9EDF8D72E1ED24A26B@daebe005.NOE.Nokia.com>
Thread-Topic: SigComp Requirements (was Re: [rohc] RE: Default decompression algorithms)
Thread-Index: AcHAK1m46zkuqSWUSE6AAHG8eOOc8gARu0gg
To: <Miguel.A.Garcia@ericsson.com>
Cc: <richard.price@roke.co.uk>, <cabo@tzi.org>,
        <Lars-Erik.Jonsson@epl.ericsson.se>, <rohc@ietf.org>
X-OriginalArrivalTime: 28 Feb 2002 16:16:47.0278 (UTC) FILETIME=[5202ECE0:01C1C073]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA09378
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

> > 2) Here we are talking about a simple optimization to
> > reduce the latency. Does anyone has comment on it?
> > 
> http://www1.ietf.org/mail-archive/working-groups/rohc/current/
> msg00065.html
> 
> I like this text, and I think it should be covered somewhere
> in the next version of the Sigcomp draft.
> 
> There is a minor thing for discussion though. In step 3 you
> are assuming that the compressor selects the algorithm prior
> to contacint the decompressor. 

No, that's not my assumption. In step 3, all the compressor
does is to see if there is a match and then make a decision.
I rushed the text so it may not be clear on that. I can 
reword it. Your example certainly makes sense to me.

BR,
Zhigang

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


From rohc-admin@ietf.org  Thu Feb 28 11:41: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 LAA02933
	for <rohc-archive@odin.ietf.org>; Thu, 28 Feb 2002 11:41:40 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA11335;
	Thu, 28 Feb 2002 11:39: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 LAA11302
	for <rohc@optimus.ietf.org>; Thu, 28 Feb 2002 11:39:02 -0500 (EST)
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 LAA02720
	for <rohc@ietf.org>; Thu, 28 Feb 2002 11:38:57 -0500 (EST)
Received: from cabo3 (root@nmh.informatik.uni-bremen.de [134.102.224.3])
	by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with SMTP id g1SGcpI20101;
	Thu, 28 Feb 2002 17:38:51 +0100 (MET)
From: "Dr. Carsten Bormann" <cabo@tzi.org>
To: "Price, Richard" <richard.price@roke.co.uk>
Cc: <rohc@ietf.org>
Subject: RE: SigComp Requirements (was Re: [rohc] RE: Default decompression algorithms)
Date: Thu, 28 Feb 2002 17:38:51 +0100
Message-ID: <NFBBJFHGMCFINEMHAMBGIEJDHHAA.cabo@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-reply-to: <76C92FBBFB58D411AE760090271ED4186F9FDE@rsys002a.roke.co.uk>
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

> Agreed. But since the current SigComp draft allows my proposal to be
> implemented, we need to decide whether this is OK or not. Are there any
> technical reasons for enforcing that application-defined state
> should always
> be referenced by a hash?

Not really.  We just have to add some text to the security considerations.
Currently a decompressor can rely*) that the state it references is correct,
as it actually hashes correctly (because there is no other way to create
it); with your addition, it can't.
*) Of course, if the UDVM is malicious, it can't, but then, this is
equivalent to the recipient system being malicious, and there is no way to
ensure packet integrity in this case, either.

What's wrong about hashes, btw?

We may want to restrict the size of the identifiers to a sensible range,
though (6 to 12, with 9 as the "general Internet" default).

To add some technical substance, here are some real work items (with
identifiers on them):

cabo-1) We need to decide what hash to use; people have pointed out that
SHA-1 may be a better choice than MD5.

cabo-2) We need to decide how to do the truncation -- I believe it should be
done uniformly (i.e., the identifier size should be a UDVM parameter); if
not, it should be possible to use different state identifier sizes to
reference the same state (substring match).

cabo-3) We need to add security analysis for the capability announcement
(hard!); again, I'd rather get rid of it by just setting values.

Gruesse, Carsten


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


From rohc-admin@ietf.org  Thu Feb 28 11:58: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 LAA04024
	for <rohc-archive@odin.ietf.org>; Thu, 28 Feb 2002 11:58:40 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA12511;
	Thu, 28 Feb 2002 11:54:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA12483
	for <rohc@optimus.ietf.org>; Thu, 28 Feb 2002 11:54:45 -0500 (EST)
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 LAA03767
	for <rohc@ietf.org>; Thu, 28 Feb 2002 11:54:40 -0500 (EST)
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2653.19)
	id <1XV9AD46>; Thu, 28 Feb 2002 16:53:27 -0000
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 1S9WNWGH; Thu, 28 Feb 2002 16:53:25 -0000
From: "West, Mark (ITN)" <mark.a.west@roke.co.uk>
To: Julije Ozegovic <julije@fesb.hr>
Cc: rohc <rohc@ietf.org>
Message-ID: <3C7E6085.6030703@roke.co.uk>
Date: Thu, 28 Feb 2002 16:53:25 +0000
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
Subject: Re: [rohc] TCP/IP EPIC profile
References: <3C7BF6E0.9070307@fesb.hr> <3C7D1823.7070003@roke.co.uk> <3C7E2FA3.4050608@fesb.hr>
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 Julije,

More comments, inline...

Cheers,

Mark.


Julije Ozegovic wrote:

> Hi Mark,
> 
> thank you for comments. Here I want to clarify some of my questions.
> 
> First of all, I think that TCP/IP header compression is needed. Also I 
> think that EPIC(-lite) high level "compression definition language" is 
> right approach. Also, I support EPIC "protocol independence". However, 
> all this did motivate me for profile 'expansion'.


So far, so good ;-)


> 
> EPIC provides total freedom of profile writing, when profile author has 
> possibility to deal with header on bit-by-bit basis.

> 
> Detailed profiles tend to result in complex applications/protocols.


I'd have put that the other way around (complex protocols => detailed 
profiles), but I think I agree...

> 
> Just to remember, Internet is major technology today because of its 
> simplicity: IP routers are more efficient than X.25 or ATM ones (for the 
> same technology).
> 
> In my opinion, central point is to write profiles that will give optimal 
> trade-off between complexity and compression efficiency. I think that 
> profile in <draft-ietf-rohc-tcp-00.txt> is not one of that kind.


Well, ok, it looks like we're going to disagree about this one.  Believe 
me when I say that I could make the TCP profile a whole lot more 
complicated.  Or, rather, detailed.  However, I am making the assumption 
(and, at the moment, it *is* an assumption) that if the profile were 
much more complex it would be a case of 'diminishing returns'.  That is, 
the effort of writing/verifying/maintaining/executing the profile would 
increase far faster than any compression gain.

It may be that the profile could be simplified from the current form 
without (noticably) sacrificing efficiency.  That, though, requires some 
experimentation.  As it stands, I don't believe that the protocol is 
excessively complex and I believe that it is a reasonable description of 
TCP.  Like I say, when I get a chance to experiment with the profile, I 
may change my mind.

Unless you've got some comparative figures from different variants of a 
profile, I don't think you can make that judgement.  Specifically, you 
can give a measure of the complexity of the profile but, without running 
it, by what metric are you measuring efficiency?

> 
> When writing profiles, authors should keep in mind that headers to be 
> compressed are just lists of fields, and that compressor/decomressor 
> actually treat them as such. This can provide simple and computation 
> efficient profiles.


I'm curious to know where I've deviated from treating the header as a 
list of fields.  (In fact, I'm curious to know how it's even possible to 
deviate from treating the header as a list of fields!)


> 
> Now about some questions/answers:


ok...


> 
> ** NBO:
> 
> can we introduce something like SWAP-LSB in the toolbox and let normal 
> method choice take place, e.g.:
> 
>    IP_ID = LSB(80%,x,y) | SWAP-LSB(20%,x,y)


Are you saying that you would like to have a 'SWAP-' version of *every* 
method in the toolbox?  Isn't this adding just a little more complexity 
than a simple, in-place transformation?  The whole point is that the 
byte-swappedness of a field is orthogonal to the encoding method. 
That's why it got split from the INFERRED-SCALED method in the first place.

In fact, your example perfectly illustrates that orthogonality.  It is 
clear that the IP ID is going to use LSB encoding.  However, you are 
saying that (a priori) you know that 20% of the IP ID values will be 
byte swapped and 80% will be in NBO.  My crystal-ball gazing just isn't 
that good at predicting what's going to appear as input ;-)

Contrast this with our current suggestion:
	foo = byte-swap
	      encode-foo
               encode-swap-flag

	byte-swap = NBO(16)
	encode-foo = LSB(...)
	encode-swap-flag = STATIC(99%) | IRREGULAR(1,1%)

What I am saying here is that the field is put into NBO.  Then I encode 
the (NBO'd) field with LSB (or whatever).  Then I encode the swap-flag. 
  Now, what I saying here is that the probability that the byte-swap 
state *changes* is 1%.  This is very different from saying that the 
probability of byte-swapping *is* 1%, for example.

I can be confident that the byte-swap state won't change frequently.  I 
have no idea what the ratio of byte-swapped to non-byte-swapped values 
will be...


> 
> ** Comments:
> 
> in the proposed profile, some important information is contained in 
> comments. That implies that syntax is not stable yet. Since we try to 
> implement EPIC-lite TCP/IP compression, input syntax changes force us to 
> change "profile compiler" on weekly basis - lot of frustration results :)
> 


There is *no*, repeat *no* 'important information' in the comments. 
(Excepting making the profile more human readable.  Which I admit I may 
have failed to do!)

The input syntax in the current draft looks like BNF.  The input syntax 
in the draft we'll release on Friday looks like BNF.  I don't think that 
anything of consequence has changed.

I apologise for adding/removing methods - unfortunately as we look at 
writing 'real' profiles, we are working out which methods are useful and 
how they are employed.  However, this has no change on the syntax.


> ** FORMAT in CO:
>    actually was FORMAT SELECTOR in CO:
> 
> When transmitting CO packet, compressor is using the same format set 
> that has already been communicated to decompressor through the IR/DYN 
> packet. It is obsolete to send this selector in CO packet, because 
> decompressor should be informed in forward, to be able to decompress the 
> header... STATIC test is obsolete too, because it will fail on multiple 
> contexts, so compressor must erase all previous contexts (if any) when 
> changing to another format set.


The format selector is there to avoid mucking up the context. 
(Although, of course, you could do the context in a more complex fashion).

[There are still some details about FORMAT that we're working out, but...]

FORMAT has to be in the CO packet, for the reasons I explained in the 
last e-mail.  FORMAT generates a format selector.  It is important that 
every time that FORMAT is encountered it generates the meta-value, which 
must itself be compressed in order to keep the context aligned.  This is 
essentially the case because of the sequential context indexing.

However, the whole point is that the STATIC test is also a way of saying 
that the FORMAT cannot change within the compressed packet.

The compressor does not need to erase contexts when it changes FORMAT 
(if the profile has been written properly), as the context histories 
should still align.  Only the sets of encoding methods used change.


> 
> ** difference in FORMAT between CO/IR/DYN:
> 
> by draft, all methods in format should be available for IR/DYN 
> processing. This means that:
> 
> field = FORMAT((method1 | method2);(method3 | method4))
> 
> should be in IR/DYN interpreted as:
> 
> field = (method1 | method2 | method3 | method4)
> 
> Consequences are:
>   - FORMAT should be the same in all three profiles (CO/IR/DYN)
>   - NO format selector is needed, i.e. "method3" when selected
>     in IR/DYN implies second format set
>   - since "choose" in most applications simply tries one by one
>     method from the list, IRREGULAR should not be included
>     before the last method (i.e. only "method4" can be
>     IRREGULAR), otherwise methods after IRREGULAR
>     will newer be chosen
> 


These are good points - and, as I say, we are currently discussing them. 
  We will have an answer before the draft gets issued..!


> ** ack STACK-TO-CONTROL not defined
> 
> since following exists in the profile (although not used):
> 
>    get-seq-ack      =   ROTATE(2,1)
>                         STACK-FROM-CONTROL(2) ; cwr/ece
>                         ROTATE(4,1)
>                         STACK-FROM-CONTROL(2) ; ecn
>                         STACK-FROM-CONTROL(32) ; ack
>                         STACK-FROM-CONTROL(32) ; seq
> 
> ack and sack should be pushed before :)
> 


Ah, ok, I see what you mean.  Yes!  If I want to pull something off the 
stack, I should have pushed it first...  Oh well, another bug to fix ;-)


> Cheers,
> Julije
> 
> 


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


