From mailman-bounces@ietf.org  Mon Nov  1 05:58:07 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16020
	for <rohc-web-archive@ietf.org>; Mon, 1 Nov 2004 05:58:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COa7w-0004Ie-F5
	for rohc-web-archive@ietf.org; Mon, 01 Nov 2004 06:13:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COZIR-0003rI-8p
	for rohc-web-archive@ietf.org; Mon, 01 Nov 2004 05:20:19 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: rohc-web-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.7799.1099303582.20557.mailman@lists.ietf.org>
Date: Mon, 01 Nov 2004 05:06:22 -0500
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit

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

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

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

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

NOTE WELL:

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

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

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

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

Please consult RFC 3667 for details.

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


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

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

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


From rohc-bounces@ietf.org  Tue Nov  2 03:24:04 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25597
	for <rohc-web-archive@ietf.org>; Tue, 2 Nov 2004 03:24:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1COuCO-0003ES-RE
	for rohc-web-archive@ietf.org; Tue, 02 Nov 2004 03:39:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COtw2-0006Qu-55; Tue, 02 Nov 2004 03:22:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COtjn-00026c-2O
	for rohc@megatron.ietf.org; Tue, 02 Nov 2004 03:09:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24695
	for <rohc@ietf.org>; Tue, 2 Nov 2004 03:09:53 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COtyh-0002yj-8s
	for rohc@ietf.org; Tue, 02 Nov 2004 03:25:29 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iA289gWR024792
	for <rohc@ietf.org>; Tue, 2 Nov 2004 09:09:42 +0100 (MET)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 2 Nov 2004 09:09:40 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <VJSNCBZF>; Tue, 2 Nov 2004 09:09:37 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E9892@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Tue, 2 Nov 2004 09:09:32 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 02 Nov 2004 08:09:40.0842 (UTC)
	FILETIME=[4DB234A0:01C4C0B3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Subject: [rohc] Agenda for the ROHC WG @ IETF61
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243

Robust Header Compression WG (rohc)

Monday, November 8 at 09:00-11:30
=================================

CHAIRS: Carsten Bormann <cabo@tzi.org>
        Lars-Erik Jonsson <lars-erik.jonsson@ericsson.com>


AGENDA:

0900  Chair admonishments and agenda bashing          (Jonsson)   10
  - NOTE: It is assumed that people have read all drafts


0910  WG and document status update                   (Jonsson)   20
  - Published:
         RFC 3095, RTP
         RFC 3096, RTP requirements
         RFC 3241, ROHC over PPP             
         RFC 3242, LLA                       
         RFC 3243, 0-byte RTP requirements   
         RFC 3408, LLA R-mode                       
         RFC 3409, ROHC RTP lower layer guidelines   
         RFC 3320, Signaling Compression (SigComp)
         RFC 3321, SigComp - Extended Operations
         RFC 3322, SigComp Req's & Assumptions
         RFC 3485, SigComp SIP/SDP static dictionary
         RFC 3486, Compressing SIP with SigComp      
         RFC 3759, ROHC Terminology & channel mapping examples
         RFC 3816, Definitions of managed objects for ROHC
         RFC 3843, A ROHC profile for IP 
         
  - Approved/in RFC editor queue:
         draft-ietf-rohc-udp-lite-04.txt (Proposed Standard)

  - Submitted to IESG:
         draft-ietf-rohc-sigcomp-nack-02 (Proposed Standard)
         draft-ietf-rohc-context-replication-06.txt (Proposed Standard)
         draft-ietf-rohc-tcp-requirements-08.txt (Informational)
         draft-ietf-rohc-tcp-field-behavior-04.txt (Informational)

  - Passed WGLC:
         None!

  - Current WG drafts:
         RTP/Framework: 2 (impl.guide/LLA impl.guide/interop.status)
         TCP profile: 2 (profile/notation)
         SigComp: 2 (sigcomp-sip/impl.guide) 
         ROHC-General: 1 (reordering)


0930  SigComp towards Draft Standard                 (Bormann)    15  
  * Documents:
         RFC 3320, RFC 3321
         draft-ietf-rohc-sigcomp-impl-guide-03.txt


0945  ROHC TCP & Formal Notation            (Pelletier et al.)    30
  * Documents:
         draft-ietf-rohc-tcp-08.txt
         draft-ietf-rohc-formal-notation-04.txt


1015  ROHC RTP towards Draft Standard                             30
  * Documents:
         draft-ietf-rohc-rtp-impl-guide-08.txt
         draft-ietf-rohc-rtp-rfc3095-interoperability-03.txt
         draft-brinkmann-rohc-3095-fn-00.txt
  - Introduction                                     (Jonsson)   (5)
  - Implementer's Guide                              (Jonsson)  (10)
  - RFC 3095 in Formal Notation                      (Bormann)  (15)


1045  LLA ROHC RTP Implementer's guide              (Sandlund)    10
  * Documents:
         draft-ietf-rohc-rtp-lla-impl-guide-00.txt


1055  ROHC over channels that can reorder packets  (Pelletier)     5
  * Documents:
         draft-ietf-rohc-over-reordering-00.txt


1100  ROHC over 802 networks                         (Bormann)    30
  * Documents:
         draft-bormann-rohc-over-802-00.txt


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

DRAFT SUMMARY:

Approved for publication:
RTP: draft-ietf-rohc-udp-lite-04.txt (PS)

Submitted to IESG:
SIG: draft-ietf-rohc-sigcomp-nack-02.txt (PS)
TCP: draft-ietf-rohc-context-replication-06.txt (PS)
TCP: draft-ietf-rohc-tcp-requirements-08.txt (I)
TCP: draft-ietf-rohc-tcp-field-behavior-04.txt (I)

Passed WGLC:
None!

Current WG drafts:
RTP: draft-ietf-rohc-rtp-impl-guide-08.txt
RTP: draft-ietf-rohc-rtp-rfc3095-interoperability-03.txt
RTP: draft-ietf-rohc-rtp-lla-impl-guide-00.txt
TCP: draft-ietf-rohc-tcp-08.txt
TCP: draft-ietf-rohc-formal-notation-04.txt
SIG: draft-ietf-rohc-sigcomp-sip-01.txt (EXPIRED)
SIG: draft-ietf-rohc-sigcomp-impl-guide-03.txt
GEN: draft-ietf-rohc-over-reordering-00.txt

Individual submissions:
GEN: draft-bormann-rohc-over-802-00.txt
RTP: draft-brinkmann-rohc-3095-fn-00.txt

Legend:
RTP: ROHC RTP, including IP, UDP, ESP, LLA, UDP-Lite
SIG: ROHC Signaling Compression
TCP: ROHC TCP
GEN: General ROHC issues

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


From rohc-bounces@ietf.org  Tue Nov  2 12:56:07 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17801
	for <rohc-web-archive@ietf.org>; Tue, 2 Nov 2004 12:56:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CP38G-00007y-El
	for rohc-web-archive@ietf.org; Tue, 02 Nov 2004 13:11:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CP2bM-00009A-KW; Tue, 02 Nov 2004 12:37:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CP2Pn-0001Yk-7f
	for rohc@megatron.ietf.org; Tue, 02 Nov 2004 12:25:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14542
	for <rohc@ietf.org>; Tue, 2 Nov 2004 12:25:48 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CP2et-0007hO-GR
	for rohc@ietf.org; Tue, 02 Nov 2004 12:41:30 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FAW98>; Tue, 2 Nov 2004 17:26:28 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8803D58B0@rsys004a.roke.co.uk>
From: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
To: rohc@ietf.org
Date: Tue, 2 Nov 2004 17:26:19 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Subject: [rohc] Shared mode
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465

Hi All,

Before and at San Diego there was some discussion about a potential problem
with shared mode as it's currently defined in 3321.  For the gory details of
the discussion see
<http://www1.ietf.org/mail-archive/web/rohc/current/msg02384.html> and
subsequent messages.

In summary, if compressor A creates a second piece of shared mode state
there is potential for loss of synchronisation between endpoints A and B
(e.g. if the second shared mode state pushes the first piece of shared mode
state out but the message that does this does not reach B).

Our proposed solution is that the creation of only one piece of shared mode
state is allowed by any compressor (and the corresponding decompressor at
the other endpoint).  However, this has to be agreed by all SigComp
endpoints otherwise there is still possibility for loss of synchronisation
(see earlier messages).

Do others agree 

a) that there is a problem,
b) that allowing only one piece of shared mode state is a suitable solution,
c) that some text for this solution should be put in the implementer's
guide?

I understand that most of the above was agreed in San Diego, however, we
require consensus on the list in order to put the text in the implementer's
guide.

All comments are appreciated.  If I don't hear anything by Nov 19th (1 week
after Washington) then I'll take this as consensus and propose some text for
the implementer's guide.

Best regards,

Abbie

Abbie Surtees
Senior Engineer
Roke Manor Research Ltd
Old Salisbury Lane
Romsey, SO51 0ZN
Tel:   +44 (0) 1794 833131


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


From rohc-bounces@ietf.org  Tue Nov  2 14:04:23 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29272
	for <rohc-web-archive@ietf.org>; Tue, 2 Nov 2004 14:04:23 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CP4CL-0002Ts-9G
	for rohc-web-archive@ietf.org; Tue, 02 Nov 2004 14:20:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CP3lt-00049y-Jb; Tue, 02 Nov 2004 13:52:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CP3eC-0007t3-8T
	for rohc@megatron.ietf.org; Tue, 02 Nov 2004 13:44:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27303
	for <rohc@ietf.org>; Tue, 2 Nov 2004 13:44:47 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CP3tC-0001w6-2j
	for rohc@ietf.org; Tue, 02 Nov 2004 14:00:28 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iA2IiRp8002557; Tue, 2 Nov 2004 19:44:29 +0100 (MET)
In-Reply-To: <3F2E01E1D7B04F4EBEC92D3FA324D8803D58B0@rsys004a.roke.co.uk>
References: <3F2E01E1D7B04F4EBEC92D3FA324D8803D58B0@rsys004a.roke.co.uk>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <391842C8-2CFF-11D9-AD81-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] Shared mode
Date: Tue, 2 Nov 2004 19:44:27 +0100
To: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit

On Nov 02 2004, at 18:26 Uhr, Surtees, Abigail wrote:

> allowed

I have a small problem with this word -- 3321 is not normative, and 
neither is the implementer's guide.
A compressor may have other means to ascertain it can place more than 
one piece of shared mode state, so I wouldn't "prohibit" this.
Apart from that, I agree that "don't do that" 
[http://www.jargon.net/jargonfile/d/Dontdothatthen.html] was the 
resolution of the discussion.

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Tue Nov  2 18:17:27 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29083
	for <rohc-web-archive@ietf.org>; Tue, 2 Nov 2004 18:17:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CP89G-0001VU-PL
	for rohc-web-archive@ietf.org; Tue, 02 Nov 2004 18:33:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CP7lH-0000jq-61; Tue, 02 Nov 2004 18:08:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CP7W5-0005ca-Qj
	for rohc@megatron.ietf.org; Tue, 02 Nov 2004 17:52:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25917
	for <rohc@ietf.org>; Tue, 2 Nov 2004 17:52:39 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CP7lG-0000pX-MF
	for rohc@ietf.org; Tue, 02 Nov 2004 18:08:24 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FAZYR>; Tue, 2 Nov 2004 22:53:27 -0000
Received: from localhost (orion.roke.co.uk [193.118.192.66]) by
	rsys002a.roke.co.uk with SMTP (Microsoft Exchange Internet Mail
	Service Version 5.5.2657.72)
	id V2Q3RPTH; Tue, 2 Nov 2004 22:53:13 -0000
From: "West, Mark" <mark.a.west@roke.co.uk>
To: Carsten Bormann <cabo@tzi.org>
Date: Tue, 2 Nov 2004 22:51:59 +0000 (GMT Standard Time)
Subject: Re: [rohc] Shared mode
In-Reply-To: <391842C8-2CFF-11D9-AD81-000A95DC4DB6@tzi.org>
Message-ID: <Pine.WNT.4.56.0411022241090.1760@maw-laptop.comm.ad.roke.co.uk>
References: <3F2E01E1D7B04F4EBEC92D3FA324D8803D58B0@rsys004a.roke.co.uk>
	<391842C8-2CFF-11D9-AD81-000A95DC4DB6@tzi.org>
X-X-Sender: maw1@maw-laptop.comm.ad.roke.co.uk
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: "Surtees, Abigail" <abigail.surtees@roke.co.uk>, rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab


Hi Carsten,

Given that you must be on at least your third cup of coffee by now... :-)

Insofar as this issue relates to 3321, then it is clear that we cannot
'prohibit' this usage.  However, there is a slight twist to this, isn't
there?  3320 is the minimal, clean, normative bit.  All the messy
remainder went into 3321 or elsewhere.  But the '65535' priority was
motivated, basically, by shared-mode.  (This is not saying that there
mightn't be other games that one could play with such a state-priority;
just that shared-mode exists because of this contrivance).  The problem
that exists, then, is actually caused by the interaction of the altered
state-creation rules for state of this priority.  As defined in 3320...

Honestly, though, this is probably just Devil's advocacy on my part.

So long as, when a message fails to decompress, we've documented a
possible cause that would otherwise have been thought to be implausible
(i.e. an action by the peer compressor), I'm happy!

Cheers,

Mark.


On Tue, 2 Nov 2004, Carsten Bormann wrote:

> Date: Tue, 2 Nov 2004 19:44:27 +0100
> From: Carsten Bormann <cabo@tzi.org>
> To: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
> Cc: Carsten Bormann <cabo@tzi.org>, rohc@ietf.org
> Subject: Re: [rohc] Shared mode
>
> On Nov 02 2004, at 18:26 Uhr, Surtees, Abigail wrote:
>
> > allowed
>
> I have a small problem with this word -- 3321 is not normative, and
> neither is the implementer's guide.
> A compressor may have other means to ascertain it can place more than
> one piece of shared mode state, so I wouldn't "prohibit" this.
> Apart from that, I agree that "don't do that"
> [http://www.jargon.net/jargonfile/d/Dontdothatthen.html] was the
> resolution of the discussion.
>
> Gruesse, Carsten
>
>
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
>

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


From rohc-bounces@ietf.org  Wed Nov  3 02:17:37 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22852
	for <rohc-web-archive@ietf.org>; Wed, 3 Nov 2004 02:17:37 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPFdr-0004BV-95
	for rohc-web-archive@ietf.org; Wed, 03 Nov 2004 02:33:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPFNN-0007AB-Lf; Wed, 03 Nov 2004 02:16:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPFLO-0005Sc-Sq
	for rohc@megatron.ietf.org; Wed, 03 Nov 2004 02:14:11 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19998
	for <rohc@ietf.org>; Wed, 3 Nov 2004 02:14:09 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPFaf-00046H-7y
	for rohc@ietf.org; Wed, 03 Nov 2004 02:29:58 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iA37E8R2001072 for <rohc@ietf.org>; Wed, 3 Nov 2004 08:14:08 +0100
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 3 Nov 2004 08:14:08 +0100
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <VJQG7PVZ>; Wed, 3 Nov 2004 08:14:07 +0100
Message-ID: <F005CD411D18D3119C8F00508B0874800DC40425@ehubunt100.eth.ericsson.se>
From: "Lajos Zaccomer (IJ/ETH)" <lajos.zaccomer@ericsson.com>
To: "'Surtees, Abigail'" <abigail.surtees@roke.co.uk>, rohc@ietf.org
Subject: RE: [rohc] Shared mode
Date: Wed, 3 Nov 2004 08:13:56 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 03 Nov 2004 07:14:08.0277 (UTC)
	FILETIME=[B5BEE450:01C4C174]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5

Hi,

I completely agree with bullets a and c, on the other hand, with the proposed solution, SigComp will make fun of itself. Dying from the first lost message will prove to the potential customers that this is a week protocol.
To make it a bit clearer for possible newcomers: the problem is not that a second shared state pushes out the first one when the compressor of A saves it. It is that B saves a dynamic state on A, which would push out the first shared state. Now, if the message advertising the second shared state is lost, B is in trouble not knowing the first shared state is gone.
Note that compressor A is not allowed to save a new shared state if another state should be deleted as it is pointed out in RFC 3321 5.2:
  "Note that new shared state items must not be created
   unless the compressor has made enough state memory available (as
   decompression failure could occur if the shared state pushed existing
   state out of the state memory buffer)."
So, what is the problem here? I don't think it's the shared compression, but the state handling algorithm used by endpoint B. If an endpoint will not mix shared and dynamic compression, this will not happen. Basically, it is an endpoint responsibility not to use it, so in my opinion, there should be nothing but a warning in one of the guides that this mixed mode should be used with much care or avoided if possible.

br/Zacco




-----Original Message-----
From: rohc-bounces@ietf.org [mailto:rohc-bounces@ietf.org]On Behalf Of Surtees, Abigail
Sent: Tuesday, November 02, 2004 6:26 PM
To: rohc@ietf.org
Subject: [rohc] Shared mode


Hi All,

Before and at San Diego there was some discussion about a potential problem
with shared mode as it's currently defined in 3321.  For the gory details of
the discussion see
<http://www1.ietf.org/mail-archive/web/rohc/current/msg02384.html> and
subsequent messages.

In summary, if compressor A creates a second piece of shared mode state
there is potential for loss of synchronisation between endpoints A and B
(e.g. if the second shared mode state pushes the first piece of shared mode
state out but the message that does this does not reach B).

Our proposed solution is that the creation of only one piece of shared mode
state is allowed by any compressor (and the corresponding decompressor at
the other endpoint).  However, this has to be agreed by all SigComp
endpoints otherwise there is still possibility for loss of synchronisation
(see earlier messages).

Do others agree 

a) that there is a problem,
b) that allowing only one piece of shared mode state is a suitable solution,
c) that some text for this solution should be put in the implementer's
guide?

I understand that most of the above was agreed in San Diego, however, we
require consensus on the list in order to put the text in the implementer's
guide.

All comments are appreciated.  If I don't hear anything by Nov 19th (1 week
after Washington) then I'll take this as consensus and propose some text for
the implementer's guide.

Best regards,

Abbie

Abbie Surtees
Senior Engineer
Roke Manor Research Ltd
Old Salisbury Lane
Romsey, SO51 0ZN
Tel:   +44 (0) 1794 833131


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

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


From rohc-bounces@ietf.org  Wed Nov  3 12:32:18 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00233
	for <rohc-web-archive@ietf.org>; Wed, 3 Nov 2004 12:32:18 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPPEz-0002Fl-Rw
	for rohc-web-archive@ietf.org; Wed, 03 Nov 2004 12:48:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPOqv-0007Gt-1i; Wed, 03 Nov 2004 12:23:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPOXY-00027B-2v
	for rohc@megatron.ietf.org; Wed, 03 Nov 2004 12:03:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27365
	for <rohc@ietf.org>; Wed, 3 Nov 2004 12:03:18 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPOms-0001Xc-KD
	for rohc@ietf.org; Wed, 03 Nov 2004 12:19:13 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FB1D7>; Wed, 3 Nov 2004 17:04:05 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8803D58C5@rsys004a.roke.co.uk>
From: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
To: "'Lajos Zaccomer (IJ/ETH)'" <lajos.zaccomer@ericsson.com>, rohc@ietf.org
Subject: RE: [rohc] Shared mode
Date: Wed, 3 Nov 2004 17:03:45 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87

Hi Zacco, All,

Thanks for your feedback:
> 
> I completely agree with bullets a and c, on the other hand, 
> with the proposed solution, SigComp will make fun of itself. 
> Dying from the first lost message will prove to the potential 
> customers that this is a week protocol.
> To make it a bit clearer for possible newcomers: the problem 
> is not that a second shared state pushes out the first one 
> when the compressor of A saves it. It is that B saves a 
> dynamic state on A, which would push out the first shared 
> state. Now, if the message advertising the second shared 
> state is lost, B is in trouble not knowing the first shared 
> state is gone.
> Note that compressor A is not allowed to save a new shared 
> state if another state should be deleted as it is pointed out 
> in RFC 3321 5.2:
>   "Note that new shared state items must not be created
>    unless the compressor has made enough state memory available (as
>    decompression failure could occur if the shared state 
> pushed existing
>    state out of the state memory buffer)."

You are right, apologies for my confusing summary.  (There are some message
flows in previous mails on this subject which are clearer than words - for
more details see these
<http://www1.ietf.org/mail-archive/web/rohc/current/msg02384.html>)

> So, what is the problem here? I don't think it's the shared 
> compression, but the state handling algorithm used by 
> endpoint B. If an endpoint will not mix shared and dynamic 
> compression, this will not happen. Basically, it is an 
> endpoint responsibility not to use it, so in my opinion, 
> there should be nothing but a warning in one of the guides 
> that this mixed mode should be used with much care or avoided 
> if possible.
> 
> br/Zacco
> 

Adding a restriction to only use one of dynamic or shared mode could be a
solution, however, I think it is much more restrictive than the 'only store
one piece of shared state solution'.  If you only ever stored shared state,
you couldn't download bytecode at all and consequently the compression ratio
would suffer.

If you allow the two modes to be mixed then I think you need the restriction
we are suggesting (which I don't think implies that the protocol is weak).

In most protocols, if there is a problem, then it is obvious from looking at
the message flows which end has caused the problem.

For SigComp, looking at the flow would show that endpoint B has 'got it
wrong' because it has referenced a piece of state that is not present.
However, it is the behaviour of endpoint A (creating multiple pieces of
shared state which is currently allowed) that has caused endpoint B to
unknowingly reference state that is no longer available.  Consequently, in
this case, the safest thing for the a compressor to do is disable shared
mode.

The state handling algorithm in endpoint B in the example complies with the
state handling rules of RFC 3320.  However, RFC3320 also states that an
endpoint referencing state must be sure that it exists at the remote end.
The only ways in which B could be sure that the state exists are:

to only reference shared state in the direct response to the message that
advertised it (i.e. only in the first of the two messages B sends in the
example, the second would have to be sent without any state reference),

or

if B can be sure that endpoint A will only create one piece of shared state.

Consequently, if the restriction to one piece of shared state is not added,
then shared mode would only be usable in a very restricted case (direct
reply).

Adding the 'only one piece of shared mode state' rule still allows
shared-mode to be usable and useful and highlights that there is an issue
with state at priority 65535 and that if there a problem, that it may not be
the obvious endpoint (B) that has actually caused it.

Having said all this, we've been referring to shared-mode state as this is
the only use (that I know of, so far) of state with retention priority
65535; however, I think it should actually be a restriction to only create
one piece of state with that priority rather than restricting it to
shared-mode.

What do you think?

Best regards,

Abbie

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


From rohc-bounces@ietf.org  Wed Nov  3 13:02:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03297
	for <rohc-web-archive@ietf.org>; Wed, 3 Nov 2004 13:02:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPPi5-00031r-P9
	for rohc-web-archive@ietf.org; Wed, 03 Nov 2004 13:18:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPPNU-0000so-GN; Wed, 03 Nov 2004 12:57:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPPI6-0005TH-Ql
	for rohc@megatron.ietf.org; Wed, 03 Nov 2004 12:51:26 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02256
	for <rohc@ietf.org>; Wed, 3 Nov 2004 12:51:23 -0500 (EST)
Received: from magus.nostrum.com ([69.5.195.2] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPPXS-0002mO-Lc
	for rohc@ietf.org; Wed, 03 Nov 2004 13:07:19 -0500
Received: from [10.1.11.198] (inetgate.teknekron.com [192.138.162.245] (may be
	forged)) (authenticated bits=0)
	by magus.nostrum.com (8.12.11/8.12.11) with ESMTP id iA3Hp3Ik019280
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 3 Nov 2004 11:51:05 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <41891A86.8010802@nostrum.com>
Date: Wed, 03 Nov 2004 11:51:02 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Lajos Zaccomer (IJ/ETH)" <lajos.zaccomer@ericsson.com>
Subject: Re: [rohc] Shared mode
References: <F005CD411D18D3119C8F00508B0874800DC40425@ehubunt100.eth.ericsson.se>
In-Reply-To: <F005CD411D18D3119C8F00508B0874800DC40425@ehubunt100.eth.ericsson.se>
X-Enigmail-Version: 0.86.1.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit
Cc: "'Surtees, Abigail'" <abigail.surtees@roke.co.uk>, rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit

Lajos Zaccomer (IJ/ETH) wrote:

>I completely agree with bullets a and c, on the other hand, with the proposed solution, SigComp will make fun of itself. Dying from the first lost message will prove to the potential customers that this is a week protocol.
>  
>


By the way, the ability to recover from these kind of situations was one 
of the strong motivations for the NACK document. If this is a truly rare 
occurrence, then I think the current situation combined with the use of 
NACKs is probably a suitable solution.

/a

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


From rohc-bounces@ietf.org  Wed Nov  3 19:00:57 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05088
	for <rohc-web-archive@ietf.org>; Wed, 3 Nov 2004 19:00:57 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPVJB-0003Jj-2v
	for rohc-web-archive@ietf.org; Wed, 03 Nov 2004 19:16:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPV1f-0002vn-JA; Wed, 03 Nov 2004 18:58:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPUxr-00024K-Ar
	for rohc@megatron.ietf.org; Wed, 03 Nov 2004 18:54:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04681
	for <rohc@ietf.org>; Wed, 3 Nov 2004 18:54:52 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPVDG-0003Aw-RC
	for rohc@ietf.org; Wed, 03 Nov 2004 19:10:51 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FBHWC>; Wed, 3 Nov 2004 23:55:42 -0000
Received: from mjw-pc.roke.co.uk ([193.118.194.159]) by rsys002a.roke.co.uk
	with SMTP (Microsoft Exchange Internet Mail Service Version
	5.5.2657.72) id V2Q3RQHN; Wed, 3 Nov 2004 23:55:28 -0000
From: "West, Mark" <mark.a.west@roke.co.uk>
To: Adam Roach <adam@nostrum.com>
Date: Thu, 4 Nov 2004 01:28:11 +0000 (GMT)
X-X-Sender: maw@mjw-pc.roke.co.uk
Subject: Re: [rohc] Shared mode
In-Reply-To: <41891A86.8010802@nostrum.com>
Message-ID: <Pine.LNX.4.44.0411040113580.1024-100000@mjw-pc.roke.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: rohc@ietf.org, "Surtees, Abigail" <abigail.surtees@roke.co.uk>,
        "Lajos Zaccomer \(IJ/ETH\)" <lajos.zaccomer@ericsson.com>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4


Adam,

We probably should have brought NACK into this sooner...  you're quite
right in suggesting that NACK is a way of recovering in the event of this
problem occuring.

A few comments, though:

- it's still worth (I think) documenting that a NACK based on failing to
find shared-mode state *probably* indicates a confusion of the form
described [for a well-behaved compressor].  (and, as a consequence,
shared-mode should no longer be used in this compartment)

- a communication involving a SigComp 'v1' endpoint will not be able to
take advantage of the NACK mechanism, so it would be nice to offer some
explanation of how to behave?

I still have a nagging doubt, though (and I'm sure you'll tell me if you
just think I'm being paranoid!) -- even with NACK, it is up to *my*
compressor to determine its risk level.  If I'm feeling conservative, then
I'll act in a way that tries to avoid NACKs.  This problem kind of
undermines that, I think.  If I don't know how your endpoint will behave,
my only prudent course of action is to not use shared-mode, except in
direct response to a received message.  If I can believe that your
endpoint will be more circumspect, then I can be more relaxed about using
shared-mode.

Having written and re-read this, I guess what I'm saying is that we need
to make a decision about what model we want for shared-mode.  There seem
to be two choices:
- 'full-speed ahead, and damn the torpedoes'; or
- only create one piece of shared-mode state

Depending upon which basic model we agree on, the trade-off for
compressors and the implementation choices that they need to make will
naturally follow.

FWIW, if we go with the first approach, my personal opinion would be to
disable shared-mode, because it's too risky.

However, in this case, I think that the WG needs to choose its risks..!
And I would agree that NACK makes it possible for either way to be
reasonably chosen.

Cheers,

Mark.

>
> By the way, the ability to recover from these kind of situations was one
> of the strong motivations for the NACK document. If this is a truly rare
> occurrence, then I think the current situation combined with the use of
> NACKs is probably a suitable solution.
>
> /a
>
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
>

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


From rohc-bounces@ietf.org  Thu Nov  4 02:04:15 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09296
	for <rohc-web-archive@ietf.org>; Thu, 4 Nov 2004 02:04:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPbuq-0003ZE-2M
	for rohc-web-archive@ietf.org; Thu, 04 Nov 2004 02:20:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPbQr-0003Mf-FU; Thu, 04 Nov 2004 01:49:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPbOw-0002nH-E7
	for rohc@megatron.ietf.org; Thu, 04 Nov 2004 01:47:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04003
	for <rohc@ietf.org>; Thu, 4 Nov 2004 01:47:17 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPbeP-0003GB-R9
	for rohc@ietf.org; Thu, 04 Nov 2004 02:03:18 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iA46l1LC016545; Thu, 4 Nov 2004 07:47:03 +0100 (MET)
In-Reply-To: <Pine.LNX.4.44.0411040113580.1024-100000@mjw-pc.roke.co.uk>
References: <Pine.LNX.4.44.0411040113580.1024-100000@mjw-pc.roke.co.uk>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <53B9E230-2E2D-11D9-AD81-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] Shared mode
Date: Thu, 4 Nov 2004 07:46:59 +0100
To: "West, Mark" <mark.a.west@roke.co.uk>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7bit
Cc: "Surtees, Abigail" <abigail.surtees@roke.co.uk>,
        Carsten Bormann <cabo@tzi.org>, rohc@ietf.org,
        Adam Roach <adam@nostrum.com>,
        "Lajos Zaccomer \(IJ/ETH\)" <lajos.zaccomer@ericsson.com>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit

Mark,

your message confuses me.

When you say "the WG needs to choose" -- are you talking about changes 
to normative documents, or are you talking about the recommendations we 
are making for compressor implementers?

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Thu Nov  4 02:38:47 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22426
	for <rohc-web-archive@ietf.org>; Thu, 4 Nov 2004 02:38:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPcS6-0004N7-M4
	for rohc-web-archive@ietf.org; Thu, 04 Nov 2004 02:54:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPc5Q-0000RQ-WF; Thu, 04 Nov 2004 02:31:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPc2B-00080y-K8
	for rohc@megatron.ietf.org; Thu, 04 Nov 2004 02:27:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21415
	for <rohc@ietf.org>; Thu, 4 Nov 2004 02:27:50 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPcHT-000473-TT
	for rohc@ietf.org; Thu, 04 Nov 2004 02:43:51 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iA47RcR2023884 for <rohc@ietf.org>; Thu, 4 Nov 2004 08:27:38 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 4 Nov 2004 08:27:38 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <VJSNYQQS>; Thu, 4 Nov 2004 08:27:38 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E98A3@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'Carsten Bormann'" <cabo@tzi.org>, "West, Mark" <mark.a.west@roke.co.uk>
Subject: RE: [rohc] Shared mode
Date: Thu, 4 Nov 2004 08:27:35 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 04 Nov 2004 07:27:38.0445 (UTC)
	FILETIME=[C30E77D0:01C4C23F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: "Surtees, Abigail" <abigail.surtees@roke.co.uk>, rohc@ietf.org,
        Adam Roach <adam@nostrum.com>,
        "Lajos Zaccomer \(IJ/ETH\)" <lajos.zaccomer@ericsson.com>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9

Carsten and others,

I think we are all aware we are talking about functionality
defined in an informative document. However, since we have now
provided non-normative suggestions for how to implement, we
should also provide clarifications to what might be misleading
in that informative document, as well as recommendations for
how to actually implement. Personally I believe the impl.
guide is the right place to put such clarifying text, and of
course the WG will have to decide what we think are the proper
suggestions to put there.

/L-E


> -----Original Message-----
> From: rohc-bounces@ietf.org [mailto:rohc-bounces@ietf.org]On Behalf Of
> Carsten Bormann
> Sent: den 4 november 2004 07:47
> To: West, Mark
> Cc: Surtees, Abigail; Carsten Bormann; rohc@ietf.org; Adam 
> Roach; Lajos
> Zaccomer (IJ/ETH)
> Subject: Re: [rohc] Shared mode
> 
> 
> Mark,
> 
> your message confuses me.
> 
> When you say "the WG needs to choose" -- are you talking 
> about changes 
> to normative documents, or are you talking about the 
> recommendations we 
> are making for compressor implementers?
> 
> Gruesse, Carsten
>

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


From rohc-bounces@ietf.org  Thu Nov  4 05:52:15 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08230
	for <rohc-web-archive@ietf.org>; Thu, 4 Nov 2004 05:52:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPfTX-0000YG-Ek
	for rohc-web-archive@ietf.org; Thu, 04 Nov 2004 06:08:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPfCH-0004ue-TW; Thu, 04 Nov 2004 05:50:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPf49-0003D0-QF
	for rohc@megatron.ietf.org; Thu, 04 Nov 2004 05:42:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07501
	for <rohc@ietf.org>; Thu, 4 Nov 2004 05:42:03 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPfJU-0000K5-Tm
	for rohc@ietf.org; Thu, 04 Nov 2004 05:58:07 -0500
Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iA4AfrvD028898
	for <rohc@ietf.org>; Thu, 4 Nov 2004 11:41:53 +0100 (MET)
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 4 Nov 2004 11:41:49 +0100
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <WFZGZCR5>; Thu, 4 Nov 2004 11:41:48 +0100
Message-ID: <F005CD411D18D3119C8F00508B0874800DC40432@ehubunt100.eth.ericsson.se>
From: "Lajos Zaccomer (IJ/ETH)" <lajos.zaccomer@ericsson.com>
To: "'Surtees, Abigail'" <abigail.surtees@roke.co.uk>, rohc@ietf.org
Subject: RE: [rohc] Shared mode
Date: Thu, 4 Nov 2004 11:41:47 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 04 Nov 2004 10:41:49.0878 (UTC)
	FILETIME=[E3DA0D60:01C4C25A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd3fc8e909678b38737fc606dec187f0

Hi Abbie,

see my comments inline ...

> -----Original Message-----
> From: Surtees, Abigail [mailto:abigail.surtees@roke.co.uk]
> Sent: Wednesday, November 03, 2004 6:04 PM
> To: Lajos Zaccomer (IJ/ETH); rohc@ietf.org
> Subject: RE: [rohc] Shared mode
> 
> 
> Hi Zacco, All,
> 
> Thanks for your feedback:
> > 
> > I completely agree with bullets a and c, on the other hand, 
> > with the proposed solution, SigComp will make fun of itself. 
> > Dying from the first lost message will prove to the potential 
> > customers that this is a week protocol.
> > To make it a bit clearer for possible newcomers: the problem 
> > is not that a second shared state pushes out the first one 
> > when the compressor of A saves it. It is that B saves a 
> > dynamic state on A, which would push out the first shared 
> > state. Now, if the message advertising the second shared 
> > state is lost, B is in trouble not knowing the first shared 
> > state is gone.
> > Note that compressor A is not allowed to save a new shared 
> > state if another state should be deleted as it is pointed out 
> > in RFC 3321 5.2:
> >   "Note that new shared state items must not be created
> >    unless the compressor has made enough state memory available (as
> >    decompression failure could occur if the shared state 
> > pushed existing
> >    state out of the state memory buffer)."
> 
> You are right, apologies for my confusing summary.  (There 
> are some message
> flows in previous mails on this subject which are clearer 
> than words - for
> more details see these
> <http://www1.ietf.org/mail-archive/web/rohc/current/msg02384.html>)
> 
> > So, what is the problem here? I don't think it's the shared 
> > compression, but the state handling algorithm used by 
> > endpoint B. If an endpoint will not mix shared and dynamic 
> > compression, this will not happen. Basically, it is an 
> > endpoint responsibility not to use it, so in my opinion, 
> > there should be nothing but a warning in one of the guides 
> > that this mixed mode should be used with much care or avoided 
> > if possible.
> > 
> > br/Zacco
> > 
> 
> Adding a restriction to only use one of dynamic or shared 
> mode could be a
> solution, however, I think it is much more restrictive than 
> the 'only store
> one piece of shared state solution'.  If you only ever stored 
> shared state,
> you couldn't download bytecode at all and consequently the 
> compression ratio
> would suffer.
> 

Yes, you're right. However, I didn't say "restriction". I said "warning in one of the guides". This is a consequence of the protocol. What I said still applies. As the bytecode is generally very small, the risk of accidental state removal is also much smaller.
One must also take the upper layer protocol into consideration. May this situation happen at all? Well, as far as I am informed, in PoC/SIP, this would never happen: after the client sent the initial REGISTER there must be an OK response. Even if the REGISTER message should be retransmitted, it would be done without recompression, lacking an answer. In this case, I can safely upload the bytecode (which is indeed mixed mode), and thereafter I could stick to either shared or dynamic compression in the server (in which case I also have the advantage to choose between them according to the first message).
In brief, I wouldn't like to see any kind of restriction in the guide (nither one shared state, nor dynamic XOR shared). I'd like to see some warnings what not to do some cases, illustrated with message sequences.

> If you allow the two modes to be mixed then I think you need 
> the restriction
> we are suggesting (which I don't think implies that the 
> protocol is weak).
> 
> In most protocols, if there is a problem, then it is obvious 
> from looking at
> the message flows which end has caused the problem.
> 
> For SigComp, looking at the flow would show that endpoint B 
> has 'got it
> wrong' because it has referenced a piece of state that is not present.
> However, it is the behaviour of endpoint A (creating multiple 
> pieces of
> shared state which is currently allowed) that has caused endpoint B to
> unknowingly reference state that is no longer available.  

No, it was B that deleted the first shared state by saving its first dynamic state. So, I believe it is up to B to be prepared for such an event. But, this question is rather philosophical. The point is that we have a problem in the protocol, which the users of the protocol must be aware of, and they have to use it with much care. This is what the guide could help.

> Consequently, in
> this case, the safest thing for the a compressor to do is 
> disable shared
> mode.
> 
> The state handling algorithm in endpoint B in the example 
> complies with the
> state handling rules of RFC 3320.  However, RFC3320 also 
> states that an
> endpoint referencing state must be sure that it exists at the 
> remote end.
> The only ways in which B could be sure that the state exists are:
> 
> to only reference shared state in the direct response to the 
> message that
> advertised it (i.e. only in the first of the two messages B 
> sends in the
> example, the second would have to be sent without any state 
> reference),
> 
> or
> 
> if B can be sure that endpoint A will only create one piece 
> of shared state.
> 

There is another possible solution, we have not considered, yet (just in case a simple warning would not fit the taste of our community ;-): compressor A should not save a second shared state until the first is freed by compressor B. This is basically the same as the one shared state solution, but we still have a chance to save new ones.

> Consequently, if the restriction to one piece of shared state 
> is not added,
> then shared mode would only be usable in a very restricted 
> case (direct
> reply).
> 
> Adding the 'only one piece of shared mode state' rule still allows
> shared-mode to be usable and useful and highlights that there 
> is an issue
> with state at priority 65535 and that if there a problem, 
> that it may not be
> the obvious endpoint (B) that has actually caused it.
> 
> Having said all this, we've been referring to shared-mode 
> state as this is
> the only use (that I know of, so far) of state with retention priority
> 65535; however, I think it should actually be a restriction 
> to only create
> one piece of state with that priority rather than restricting it to
> shared-mode.
> 
> What do you think?
> 
> Best regards,
> 
> Abbie
> 
> -- 
> 
> Visit our website at www.roke.co.uk
> 
> Roke Manor Research Ltd, Roke Manor, Romsey, Hampshire SO51 0ZN, UK.
> 
> 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.
> 

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


From rohc-bounces@ietf.org  Fri Nov  5 06:43:15 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03016
	for <rohc-web-archive@ietf.org>; Fri, 5 Nov 2004 06:43:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQ2kf-0000gx-PK
	for rohc-web-archive@ietf.org; Fri, 05 Nov 2004 06:59:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQ2Mv-0004xZ-Nk; Fri, 05 Nov 2004 06:35:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ2Lp-0004lv-Vg
	for rohc@megatron.ietf.org; Fri, 05 Nov 2004 06:33:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02243
	for <rohc@ietf.org>; Fri, 5 Nov 2004 06:33:51 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ2bY-0000Wo-AB
	for rohc@ietf.org; Fri, 05 Nov 2004 06:50:09 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FB64M>; Fri, 5 Nov 2004 11:34:38 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8801A2233@rsys004a.roke.co.uk>
From: "Finking, Robert" <robert.finking@roke.co.uk>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Fri, 5 Nov 2004 11:34:27 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Subject: [rohc] ROHC-FN uncompressed field encodings list
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87

Hi Guys,

just doing a bit of catching up. I just read the following new paragraph (in
section 4.11.1.2 uncompressed_format):

An uncompressed format may contain a field encodings list. Encoding methods
specified therein are used whenever a packet with this uncompressed format
is being encoded, regardless of the selected compressed format. If an
uncompressed format contains let-statements, the encoding of a packet with
this uncompressed format can only succeed if the specified expressions
evaluate to true (see Section [TBA]).

So I guess this means you can have structures like this:

  foo ===
  {
    uncompressed_format_1 = field_1,
                            field_2
    {
      let(some condition);
      field2 ::= some encoding method;
    }

    uncompressed_format_2 = field_1,
                            field_3
    {
      let(some condition);
      field3 ::= some encoding method;
    }

    default_encodings =
    {
      field_1 ::= some encoding method;
    }
  }

I quite like this, but I'm not sure I get it entirely! I guess the idea is
that you can specify e.g. that a version field has a set value, by
specifying an uncompressed_value encoding for that field? It's probably
worth adding at this point that I think the last sentence of 4.11.1.2 is too
weak. We need to make the same statements about uncompressed format
encodings as we do compressed format encodings - that the whole format fails
if any of it's component parts fail - whether they are let statements or
encoding methods.

There's something that troubles me here. It's about the way these encodings
interact with the compressed format encodings and also the default
encodings. (I'm also a bit nervous about what exactly is allowed inside the
uncompressed field encodings list. For example you could easily encode
field_2 in the example above using compressed_value encoding, which wouldn't
make any sense would it?)

Anyway, here's the issue. You could easily do something like this:

  foo ===
  {
    uncompressed_format_1 = version,
                            field_1
                            field_2
    {
      let(version:uncomp_value == 3);
    }

    uncompressed_format_2 = version,
                            field_2,
                            field_3,
                            field_4
    {
      let(version:uncomp_value == 4);
    }

    :
    :
    :
  }

But there's a big problem here: the value of the version field depends on
its length, which in this case, is not defined by the uncompressed field
encodings. The choice of which compressed formats can be used is obviously
going to depend on which uncompressed format is selected, so you end up with
a mutual dependency between the compressed and uncompressed formats. This is
just an example that springs to mind immediately, but the root of the
problem is allowing the two simultaneous definitions of the field encodings.
It's more explicit that the way we already had of doing this, which is good,
but also more dangerous I think.

Out of interest, what was wrong with the old way of doing it?

Cheers

Raffles

PS I've purposely not read the TCP profile yet to avoid getting
preconceptions in my mind!

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


From rohc-bounces@ietf.org  Fri Nov  5 09:28:07 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15938
	for <rohc-web-archive@ietf.org>; Fri, 5 Nov 2004 09:28:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQ5KD-0004M4-Lg
	for rohc-web-archive@ietf.org; Fri, 05 Nov 2004 09:44:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQ53a-0007X4-O6; Fri, 05 Nov 2004 09:27:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ4ud-0005me-Au
	for rohc@megatron.ietf.org; Fri, 05 Nov 2004 09:17:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15194
	for <rohc@ietf.org>; Fri, 5 Nov 2004 09:17:57 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ5AN-00047n-Dp
	for rohc@ietf.org; Fri, 05 Nov 2004 09:34:16 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FB8SM>; Fri, 5 Nov 2004 14:18:50 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8803D58E1@rsys004a.roke.co.uk>
From: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
To: "'Lajos Zaccomer (IJ/ETH)'" <lajos.zaccomer@ericsson.com>, rohc@ietf.org
Subject: RE: [rohc] Shared mode
Date: Fri, 5 Nov 2004 14:18:39 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d

Hi Zacco,


> There is another possible solution, we have not considered, 
> yet (just in case a simple warning would not fit the taste of 
> our community ;-): compressor A should not save a second 
> shared state until the first is freed by compressor B. This 
> is basically the same as the one shared state solution, but 
> we still have a chance to save new ones.
> 

Yes, this is a good suggestion.  It is creation of a second piece of minimum
priority state that causes a problem so freeing the old one first also
solves the problem.

We seem to be converging on potential solutions, so I've written some
proposed text for the implementer's guide.  This is more than a warning, but
hopefully it is also unrestrictive enough that you will be happy with it too
and we can reach WG consensus.

Let me know what you think:

"Retention Priority 65535 (or -1)

   There is potentially a problem with storing multiple pieces of state
   with the minimum retention priority (65535) as defined in SigComp
   [1].  This can be shown by considering the following examples, which
   are of shared mode SigComp Extended [2] .

   Example 1:

       Endpoint A                  Endpoint B
       [decomp cpt]                [comp cpt]

       [SM1]
       ------------------------------->
                                   [SM1]

       [SM1, SM2]
       --------------------X (message lost)

                                   [SM1, BC, BF1]
       <------------ref SM1------------
       [SM2, BC, BF1]
                                   endpoint B still believes SM1
                                   is at endpoint A

                                   [BC, BF1, BF2]
       <------------ref SM1------------

       decompression failure at A
       because SM1 has already been deleted

   Example 2:

       Endpoint A                  Endpoint B
       [decomp cpt]                [comp cpt]

       [SM1]
       ------------------------------->
                                   [SM1]

                                   [SM1, BC, BF1]
       (message lost)X------ref SM1-----

       [SM1, SM2]
       ------------------------------->
                                   endpoint B does not create SM2
                                   because there is no space
                                   [SM1, BC, BF1]

                                   [SM1, BC, BF1, BF2]
       <------------ref SM1------------
       [SM2, BC, BF2]
                                   endpoint B still believes SM1
                                   is at endpoint A

                                   [BC, BF1, BF2, BF3]
       <------------ref SM1------------

       decompression failure at A
       because SM1 has already been deleted

              Figure 2: Retention priority 65535 examples

   Once there is more than one piece of state of minimum priority state
   created in a decompressor compartment, the corresponding compressor
   cannot be certain about which pieces of state are present in that
   (decompressor) compartment.  If there is only one piece of state,
   then no such ambiguity exists.  The problem is a consequence of the
   different rules for the creation of minimum priority state.  In
   particular, the creation of the second piece of state without the
   knowledge of the compressor may mean that the first piece is pushed
   out earlier than the compressor expects (despite the fact that the
   state processing rules from SigComp [1] are being implemented
   correctly).

   SigComp [1] also states that a compressor MUST be certain that all of
   the data needed to decompress a SigComp message is available at the
   receiving endpoint.  Thus it should not reference any state unless it
   can be sure that the state exists.  The fact that the compressor at B
   has no way of knowing how much state has been created at A can lead
   to loss of synchronisation between the endpoints which is not
   acceptable.

   One observation is that it is always safe to reference a piece of 
   minimum priority state following receipt of the advertisement of the
state.

   If it is known that both endpoints are running SigComp version 2 as
   defined in NACK [4], then it may be reasonable to assume that the
   likelihood of loss of synchronisation is very small and rely on the
   NACK mechanism for recovery.

   However, for a compressor to try and avoid generating NACKs, it has
   to be able to make some assumptions about the behaviour of the peer
   compressor.  Also if one of the endpoints does not support NACK, then
   some other solution is needed.

   Consequently, the recommendation is that only one piece of minimum
   priority should be present in a compartment at any one time.  If both
   endpoints support NACK [4], then this may be relaxed, but
   implementers should think carefully about the consequences of
   creating multiple pieces of minimum priority state.

   Note that if a compressor wishes the remote endpoint to be able to
   create a new piece of minimum priority state, it can use the
   SIGCOMP-FREE instruction to remove the existing piece of state."

Best regards,

Abbie

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


From rohc-bounces@ietf.org  Fri Nov  5 10:46:55 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22654
	for <rohc-web-archive@ietf.org>; Fri, 5 Nov 2004 10:46:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQ6YV-0005v2-2i
	for rohc-web-archive@ietf.org; Fri, 05 Nov 2004 11:03:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQ6I5-0006Bi-1l; Fri, 05 Nov 2004 10:46:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ65t-0007io-3D
	for rohc@megatron.ietf.org; Fri, 05 Nov 2004 10:33:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21906
	for <rohc@ietf.org>; Fri, 5 Nov 2004 10:33:38 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ6LT-0005e5-Mm
	for rohc@ietf.org; Fri, 05 Nov 2004 10:49:58 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iA5FXSh5028818
	for <rohc@ietf.org>; Fri, 5 Nov 2004 16:33:28 +0100 (MET)
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 5 Nov 2004 16:33:28 +0100
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <WFZHGLQY>; Fri, 5 Nov 2004 16:33:28 +0100
Message-ID: <F005CD411D18D3119C8F00508B0874800DC40446@ehubunt100.eth.ericsson.se>
From: "Lajos Zaccomer (IJ/ETH)" <lajos.zaccomer@ericsson.com>
To: "'Surtees, Abigail'" <abigail.surtees@roke.co.uk>, rohc@ietf.org
Subject: RE: [rohc] Shared mode
Date: Fri, 5 Nov 2004 16:33:19 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="ISO-8859-1"
X-OriginalArrivalTime: 05 Nov 2004 15:33:28.0533 (UTC)
	FILETIME=[CC46A850:01C4C34C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 995b2e24d23b953c94bac5288c432399
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9af087f15dbdd4c64ae6bbcdbc5b1d44

Hi Abbie,

It's quite OK for me, but I'd really like to have something about the possible specific relation to the higher layer protocol some features of it may pose less constraints for implementors. One example was given in my previous mail. Neither POC nor SIP should be mentioned in the guide, of course, only a general message sequence just as you did with a short explanation. Is this all right?

Best regards,

Zacco

> -----Original Message-----
> From: Surtees, Abigail [mailto:abigail.surtees@roke.co.uk]
> Sent: Friday, November 05, 2004 3:19 PM
> To: Lajos Zaccomer (IJ/ETH); rohc@ietf.org
> Subject: RE: [rohc] Shared mode
> 
> 
> Hi Zacco,
> 
> 
> > There is another possible solution, we have not considered, 
> > yet (just in case a simple warning would not fit the taste of 
> > our community ;-): compressor A should not save a second 
> > shared state until the first is freed by compressor B. This 
> > is basically the same as the one shared state solution, but 
> > we still have a chance to save new ones.
> > 
> 
> Yes, this is a good suggestion.  It is creation of a second 
> piece of minimum
> priority state that causes a problem so freeing the old one first also
> solves the problem.
> 
> We seem to be converging on potential solutions, so I've written some
> proposed text for the implementer's guide.  This is more than 
> a warning, but
> hopefully it is also unrestrictive enough that you will be 
> happy with it too
> and we can reach WG consensus.
> 
> Let me know what you think:
> 
> "Retention Priority 65535 (or -1)
> 
>    There is potentially a problem with storing multiple 
> pieces of state
>    with the minimum retention priority (65535) as defined in SigComp
>    [1].  This can be shown by considering the following 
> examples, which
>    are of shared mode SigComp Extended [2] .
> 
>    Example 1:
> 
>        Endpoint A                  Endpoint B
>        [decomp cpt]                [comp cpt]
> 
>        [SM1]
>        ------------------------------->
>                                    [SM1]
> 
>        [SM1, SM2]
>        --------------------X (message lost)
> 
>                                    [SM1, BC, BF1]
>        <------------ref SM1------------
>        [SM2, BC, BF1]
>                                    endpoint B still believes SM1
>                                    is at endpoint A
> 
>                                    [BC, BF1, BF2]
>        <------------ref SM1------------
> 
>        decompression failure at A
>        because SM1 has already been deleted
> 
>    Example 2:
> 
>        Endpoint A                  Endpoint B
>        [decomp cpt]                [comp cpt]
> 
>        [SM1]
>        ------------------------------->
>                                    [SM1]
> 
>                                    [SM1, BC, BF1]
>        (message lost)X------ref SM1-----
> 
>        [SM1, SM2]
>        ------------------------------->
>                                    endpoint B does not create SM2
>                                    because there is no space
>                                    [SM1, BC, BF1]
> 
>                                    [SM1, BC, BF1, BF2]
>        <------------ref SM1------------
>        [SM2, BC, BF2]
>                                    endpoint B still believes SM1
>                                    is at endpoint A
> 
>                                    [BC, BF1, BF2, BF3]
>        <------------ref SM1------------
> 
>        decompression failure at A
>        because SM1 has already been deleted
> 
>               Figure 2: Retention priority 65535 examples
> 
>    Once there is more than one piece of state of minimum 
> priority state
>    created in a decompressor compartment, the corresponding compressor
>    cannot be certain about which pieces of state are present in that
>    (decompressor) compartment.  If there is only one piece of state,
>    then no such ambiguity exists.  The problem is a consequence of the
>    different rules for the creation of minimum priority state.  In
>    particular, the creation of the second piece of state without the
>    knowledge of the compressor may mean that the first piece is pushed
>    out earlier than the compressor expects (despite the fact that the
>    state processing rules from SigComp [1] are being implemented
>    correctly).
> 
>    SigComp [1] also states that a compressor MUST be certain 
> that all of
>    the data needed to decompress a SigComp message is available at the
>    receiving endpoint.  Thus it should not reference any 
> state unless it
>    can be sure that the state exists.  The fact that the 
> compressor at B
>    has no way of knowing how much state has been created at A can lead
>    to loss of synchronisation between the endpoints which is not
>    acceptable.
> 
>    One observation is that it is always safe to reference a piece of 
>    minimum priority state following receipt of the 
> advertisement of the
> state.
> 
>    If it is known that both endpoints are running SigComp version 2 as
>    defined in NACK [4], then it may be reasonable to assume that the
>    likelihood of loss of synchronisation is very small and rely on the
>    NACK mechanism for recovery.
> 
>    However, for a compressor to try and avoid generating NACKs, it has
>    to be able to make some assumptions about the behaviour of the peer
>    compressor.  Also if one of the endpoints does not support 
> NACK, then
>    some other solution is needed.
> 
>    Consequently, the recommendation is that only one piece of minimum
>    priority should be present in a compartment at any one 
> time.  If both
>    endpoints support NACK [4], then this may be relaxed, but
>    implementers should think carefully about the consequences of
>    creating multiple pieces of minimum priority state.
> 
>    Note that if a compressor wishes the remote endpoint to be able to
>    create a new piece of minimum priority state, it can use the
>    SIGCOMP-FREE instruction to remove the existing piece of state."
> 
> Best regards,
> 
> Abbie
> 
> -- 
> 
> Visit our website at www.roke.co.uk
> 
> Roke Manor Research Ltd, Roke Manor, Romsey, Hampshire SO51 0ZN, UK.
> 
> 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.
> 

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


From rohc-bounces@ietf.org  Fri Nov  5 11:09:27 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24390
	for <rohc-web-archive@ietf.org>; Fri, 5 Nov 2004 11:09:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQ6uG-0006OW-PK
	for rohc-web-archive@ietf.org; Fri, 05 Nov 2004 11:25:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQ6UP-0000Yw-SL; Fri, 05 Nov 2004 10:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ6Qw-0008At-S7
	for rohc@megatron.ietf.org; Fri, 05 Nov 2004 10:55:26 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23441
	for <rohc@ietf.org>; Fri, 5 Nov 2004 10:55:24 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ6gh-000678-Te
	for rohc@ietf.org; Fri, 05 Nov 2004 11:11:44 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FB950>; Fri, 5 Nov 2004 15:56:13 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8801A2236@rsys004a.roke.co.uk>
From: "Finking, Robert" <robert.finking@roke.co.uk>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Fri, 5 Nov 2004 15:56:02 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: [rohc] TCP profile - use of compressed_value
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793

Hi Guys,

OK, so I've started looking at the TCP profile now, one thing that's come up
a couple of time is an odd use of compressed_value encoding. It's not wrong
per se, it's just odd (though strictly speaking it's currently ambiguous -
more below). I'm referring to cases where compressed_value is used to
indicate "this field is absent from the uncompressed header". For example:

   optional_checksum (flag_value) ===
   {
           uncompressed_format = value,     % 0 or 16 bits
                                 reserved1; % 0 or 16 bits

           format_cs_present = value,     %[ 16 ]
                               reserved1, %[ 0 ]
           {
              let (flag_value == 1);
              value     ::= irregular (16);
              reserved1 ::= uncompressed_value (16, 0);
           };

           format_not_present = value,     %[ 0 ]
                                reserved1, %[ 0 ]
           {
              let (flag_value == 0);
              value     ::= compressed_value (0, 0);
              reserved1 ::= compressed_value (0, 0);
           };
   };

"format_not_present" states that in the *compressed* header, the field has a
value and length of zero. It says *nothing* explicit about its length or
value in the uncompressed header. If we want to say something about the
length of a field in the uncompressed header, I think we need to make it
clear by sticking to uncompressed_value encoding.

The thing that makes this particularly important at present, is that the FN
draft does not define formally what attributes either of the value encoding
methods bind in terms of the "other" format (i.e. compressed attributes for
"uncompressed_value" encoding and vice versa).

I guess this is only a minor point, but thought I may as well flag it up
seeing as I spotted it. It's a good sign that we're getting down to this
level of detail now!

Cheers

Raffles

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


From rohc-bounces@ietf.org  Sat Nov  6 08:12:45 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05856
	for <rohc-web-archive@ietf.org>; Sat, 6 Nov 2004 08:12:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQQND-0006TV-5J
	for rohc-web-archive@ietf.org; Sat, 06 Nov 2004 08:12:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQQGe-0005sE-Ls; Sat, 06 Nov 2004 08:06:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQQBv-00053x-Fm
	for rohc@megatron.ietf.org; Sat, 06 Nov 2004 08:01:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05003
	for <rohc@ietf.org>; Sat, 6 Nov 2004 08:01:13 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQQBt-0006CI-9a
	for rohc@ietf.org; Sat, 06 Nov 2004 08:01:23 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iA6D0gwu026232; Sat, 6 Nov 2004 14:00:48 +0100 (MET)
In-Reply-To: <3F2E01E1D7B04F4EBEC92D3FA324D8801A2236@rsys004a.roke.co.uk>
References: <3F2E01E1D7B04F4EBEC92D3FA324D8801A2236@rsys004a.roke.co.uk>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <DCF3909F-2FF3-11D9-BB95-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] TCP profile - use of compressed_value
Date: Sat, 6 Nov 2004 14:00:41 +0100
To: "Finking, Robert" <robert.finking@roke.co.uk>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, "'rohc@ietf.org'" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit

On Nov 05 2004, at 16:56 Uhr, Finking, Robert wrote:

> "format_not_present" states that in the *compressed* header, the field 
> has a
> value and length of zero. It says *nothing* explicit about its length 
> or
> value in the uncompressed header.

Actually, a while ago we decided that compressed_value defines the 
uncompressed aspect as zero length and uncompressed_value defines the 
compressed aspect as zero length.
Therefore, the following three lines are exactly equivalent in 
semantics:

foo ::= irregular(0);
foo ::= compressed_value(0,0);
foo ::= uncompressed_value(0,0);

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Sat Nov  6 12:23:39 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22180
	for <rohc-web-archive@ietf.org>; Sat, 6 Nov 2004 12:23:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQUI4-0002We-E0
	for rohc-web-archive@ietf.org; Sat, 06 Nov 2004 12:23:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQUCe-0005Hq-FZ; Sat, 06 Nov 2004 12:18:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQU6C-0002r5-En
	for rohc@megatron.ietf.org; Sat, 06 Nov 2004 12:11:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21488
	for <rohc@ietf.org>; Sat, 6 Nov 2004 12:11:33 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQU6M-0002Ju-GM
	for rohc@ietf.org; Sat, 06 Nov 2004 12:11:47 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iA6HBKDk007856; Sat, 6 Nov 2004 18:11:26 +0100 (MET)
In-Reply-To: <3F2E01E1D7B04F4EBEC92D3FA324D8801A2233@rsys004a.roke.co.uk>
References: <3F2E01E1D7B04F4EBEC92D3FA324D8801A2233@rsys004a.roke.co.uk>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <DFB61891-3016-11D9-BB95-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] ROHC-FN uncompressed field encodings list
Date: Sat, 6 Nov 2004 12:11:18 -0500
To: "Finking, Robert" <robert.finking@roke.co.uk>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, "'rohc@ietf.org'" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Content-Transfer-Encoding: 7bit


On Nov 05 2004, at 12:34 Uhr, Finking, Robert wrote:

> Hi Guys,
>
> just doing a bit of catching up. I just read the following new 
> paragraph (in
> section 4.11.1.2 uncompressed_format):
>
> An uncompressed format may contain a field encodings list. Encoding 
> methods
> specified therein are used whenever a packet with this uncompressed 
> format
> is being encoded, regardless of the selected compressed format. If an
> uncompressed format contains let-statements, the encoding of a packet 
> with
> this uncompressed format can only succeed if the specified expressions
> evaluate to true (see Section [TBA]).
>
> So I guess this means you can have structures like this:

There is no compressed_format, so this can never succeed.
The compressed_format could reduce to a simple field list in this case.

>   foo ===
>   {
>     uncompressed_format_1 = field_1,
>                             field_2
>     {
>       let(some condition);
>       field2 ::= some encoding method;
>     }
>
>     uncompressed_format_2 = field_1,
>                             field_3
>     {
>       let(some condition);
>       field3 ::= some encoding method;
>     }
>
>     default_encodings =
>     {
>       field_1 ::= some encoding method;
>     }
>   }
>
> I quite like this, but I'm not sure I get it entirely! I guess the 
> idea is
> that you can specify e.g. that a version field has a set value, by
> specifying an uncompressed_value encoding for that field? It's probably
> worth adding at this point that I think the last sentence of 4.11.1.2 
> is too
> weak. We need to make the same statements about uncompressed format
> encodings as we do compressed format encodings - that the whole format 
> fails
> if any of it's component parts fail - whether they are let statements 
> or
> encoding methods.

True.

> There's something that troubles me here. It's about the way these 
> encodings
> interact with the compressed format encodings and also the default
> encodings. (I'm also a bit nervous about what exactly is allowed 
> inside the
> uncompressed field encodings list. For example you could easily encode
> field_2 in the example above using compressed_value encoding, which 
> wouldn't
> make any sense would it?)

Well, it would mean you have a discriminator that is being determined 
from the uncompressed_format.
(As the field is zero length on the uncompressed side, it doesn't 
influence the uncompressed side too much.)
Not really senseless at all.

> Anyway, here's the issue. You could easily do something like this:
>
>   foo ===
>   {
>     uncompressed_format_1 = version,
>                             field_1
>                             field_2
>     {
>       let(version:uncomp_value == 3);
>     }
>
>     uncompressed_format_2 = version,
>                             field_2,
>                             field_3,
>                             field_4
>     {
>       let(version:uncomp_value == 4);
>     }
>
>     :
>     :
>     :
>   }
>
> But there's a big problem here: the value of the version field depends 
> on
> its length, which in this case, is not defined by the uncompressed 
> field
> encodings. The choice of which compressed formats can be used is 
> obviously
> going to depend on which uncompressed format is selected, so you end 
> up with
> a mutual dependency between the compressed and uncompressed formats. 
> This is
> just an example that springs to mind immediately, but the root of the
> problem is allowing the two simultaneous definitions of the field 
> encodings.
> It's more explicit that the way we already had of doing this, which is 
> good,
> but also more dangerous I think.

I don't see a problem with dependencies.
Conceptually, a structure is an alternative between all possible 
combinations of uncompressed and compressed formats.
Whether something (field definition or let-statement) is written down 
in an uncompressed_format or a compressed_format is just an issue of 
convenience.

> Out of interest, what was wrong with the old way of doing it?

Convenience.  The specs are long enough at they are.
(But then, I have no idea what "old way" you have in mind.)

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Sat Nov  6 12:32:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22665
	for <rohc-web-archive@ietf.org>; Sat, 6 Nov 2004 12:32:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CQUQQ-0002gx-Db
	for rohc-web-archive@ietf.org; Sat, 06 Nov 2004 12:32:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQUKu-0006Tk-8g; Sat, 06 Nov 2004 12:26:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQUEh-0005mF-3b
	for rohc@megatron.ietf.org; Sat, 06 Nov 2004 12:20:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21932
	for <rohc@ietf.org>; Sat, 6 Nov 2004 12:20:20 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQUEh-0002T1-AV
	for rohc@ietf.org; Sat, 06 Nov 2004 12:20:33 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iA6HJsd0011734; Sat, 6 Nov 2004 18:20:00 +0100 (MET)
In-Reply-To: <3F2E01E1D7B04F4EBEC92D3FA324D8803D58E1@rsys004a.roke.co.uk>
References: <3F2E01E1D7B04F4EBEC92D3FA324D8803D58E1@rsys004a.roke.co.uk>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <12162273-3018-11D9-BB95-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] Shared mode
Date: Sat, 6 Nov 2004 12:19:52 -0500
To: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Cc: rohc@ietf.org, Carsten Bormann <cabo@tzi.org>,
        "'Lajos Zaccomer \(IJ/ETH\)'" <lajos.zaccomer@ericsson.com>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit

Hi Abbie,

two more little wording proposals:

On Nov 05 2004, at 09:18 Uhr, Surtees, Abigail wrote:

> However, for a compressor to try and avoid generating NACKs

s/generating/causing the generation of/

Also, please make sure that in the recommendation paragraph, you again 
say what the presumptions are -- this is bound to be cited out of 
context.

Gruesse, Carsten.


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


From rohc-bounces@ietf.org  Mon Nov  8 04:03:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12528
	for <rohc-web-archive@ietf.org>; Mon, 8 Nov 2004 04:03:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CR5Rr-0002ny-AQ
	for rohc-web-archive@ietf.org; Mon, 08 Nov 2004 04:04:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CR5Ig-0005Qf-KT; Mon, 08 Nov 2004 03:54:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CR5IC-0005Jl-CB
	for rohc@megatron.ietf.org; Mon, 08 Nov 2004 03:54:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11889
	for <rohc@ietf.org>; Mon, 8 Nov 2004 03:54:24 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CR5Ig-0002Us-6K
	for rohc@ietf.org; Mon, 08 Nov 2004 03:54:58 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FCXWS>; Mon, 8 Nov 2004 08:55:19 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8801A223D@rsys004a.roke.co.uk>
From: "Finking, Robert" <robert.finking@roke.co.uk>
To: "'Carsten Bormann'" <cabo@tzi.org>
Subject: RE: [rohc] TCP profile - use of compressed_value
Date: Mon, 8 Nov 2004 08:55:00 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: "'rohc@ietf.org'" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b

OK, sounds good, so we need to update the FN draft to reflect this. We did
talk a while back about defining some (or all?!) of the encoding methods in
the FN - this would nail issues like this.

On the TCP profile side of things, I still thing it would be easier to read
if we were explicit and used uncompressed value both times, first time to
say it's 16 bits long second time to say it's zero bits long. It's just more
obvious to the reader. But like I said it's fairly minor so I'm not going to
get all bothered about it!

Cheers

Raffles

> -----Original Message-----
> From: Carsten Bormann [mailto:cabo@tzi.org] 
> Sent: Saturday, November 06, 2004 1:01 PM
> To: Finking, Robert
> Cc: Carsten Bormann; 'rohc@ietf.org'
> Subject: Re: [rohc] TCP profile - use of compressed_value
> 
> <snip> 
>
> Actually, a while ago we decided that compressed_value defines the 
> uncompressed aspect as zero length and uncompressed_value defines the 
> compressed aspect as zero length.
> Therefore, the following three lines are exactly equivalent in 
> semantics:
> 
> foo ::= irregular(0);
> foo ::= compressed_value(0,0);
> foo ::= uncompressed_value(0,0);
> 
> Gruesse, Carsten
> 

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


From rohc-bounces@ietf.org  Mon Nov  8 04:07:11 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12767
	for <rohc-web-archive@ietf.org>; Mon, 8 Nov 2004 04:07:11 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CR5V3-0002sX-BQ
	for rohc-web-archive@ietf.org; Mon, 08 Nov 2004 04:07:45 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CR5SQ-0006OM-5H; Mon, 08 Nov 2004 04:05:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CR5R4-00062Z-70
	for rohc@megatron.ietf.org; Mon, 08 Nov 2004 04:03:38 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12439
	for <rohc@ietf.org>; Mon, 8 Nov 2004 04:03:36 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CR5RZ-0002n1-O9
	for rohc@ietf.org; Mon, 08 Nov 2004 04:04:10 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FCXZ0>; Mon, 8 Nov 2004 09:04:33 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8801A223E@rsys004a.roke.co.uk>
From: "Finking, Robert" <robert.finking@roke.co.uk>
To: "'Carsten Bormann'" <cabo@tzi.org>
Subject: RE: [rohc] ROHC-FN uncompressed field encodings list
Date: Mon, 8 Nov 2004 09:04:17 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: "'rohc@ietf.org'" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5

> 
> > Out of interest, what was wrong with the old way of doing it?
> 
> Convenience.  The specs are long enough at they are.
> (But then, I have no idea what "old way" you have in mind.)
> 

OK, fair point! This is what I meant (using the same example as previously):


  foo ===
  {
    uncompressed_format_1 = field_1,
                            field_2;

    uncompressed_format_2 = field_1,
                            field_3;

    default_encodings =
    {
      field_1 ::= some encoding method;
    }

    compressed_format_1 = field_1,
                          field_2
    {
       let(some_condition);
       field_2 ::= some encoding method;
    };

    compressed_format_2 = field_1,
                          field_3
    {
       let(some_condition);
       field_3 ::= some encoding method;
    };
  }


Which I think is negligibly less verbose that the new suggestion, but
certainly no more so, and I think clearer (though of course others may
differ).

So, my question is, what was wrong with the above? If nothing is wrong with
that, then can you give me a minimal example that demonstrates the problem.
Thanks.

Regards

Raffles

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


From rohc-bounces@ietf.org  Mon Nov  8 06:47:58 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA24472
	for <rohc-web-archive@ietf.org>; Mon, 8 Nov 2004 06:47:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CR80g-00060N-HX
	for rohc-web-archive@ietf.org; Mon, 08 Nov 2004 06:48:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CR7yy-0003M6-Qc; Mon, 08 Nov 2004 06:46:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CR7vz-00037D-7Y
	for rohc@megatron.ietf.org; Mon, 08 Nov 2004 06:43:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA24235
	for <rohc@ietf.org>; Mon, 8 Nov 2004 06:43:40 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CR7wM-0005uy-5w
	for rohc@ietf.org; Mon, 08 Nov 2004 06:44:16 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iA8BhG3N027073; Mon, 8 Nov 2004 12:43:23 +0100 (MET)
In-Reply-To: <3F2E01E1D7B04F4EBEC92D3FA324D8801A223E@rsys004a.roke.co.uk>
References: <3F2E01E1D7B04F4EBEC92D3FA324D8801A223E@rsys004a.roke.co.uk>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <617BB245-317B-11D9-BB95-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] ROHC-FN uncompressed field encodings list
Date: Mon, 8 Nov 2004 06:43:17 -0500
To: "Finking, Robert" <robert.finking@roke.co.uk>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, "'rohc@ietf.org'" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit

>   foo ===
>   {
>     uncompressed_format_1 = field_1,
>                             field_2;
>
>     uncompressed_format_2 = field_1,
>                             field_3;
>
>     default_encodings =
>     {
>       field_1 ::= some encoding method;
>     }
>
>     compressed_format_1 = field_1,
>                           field_2
>     {
>        let(some_condition);
>        field_2 ::= some encoding method;
>     };
>
>     compressed_format_2 = field_1,
>                           field_3
>     {
>        let(some_condition);
>        field_3 ::= some encoding method;
>     };
>   }

This gives you four combinations, of which two are ill-defined (no 
encoding method has been given for one of the fields).

Of course, you could propose to have combinations simply fail where 
there are undefined encoding methods.
This, of course, hinges on having an appropriate field name that you 
can make this decision on.  Hard to read, too (in typical complex 
cases).

Allowing field definitions in uncompressed formats strikes me as 
simpler, because it removes an unnecessary asymmetry, by the way.

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Mon Nov  8 11:59:38 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01201
	for <rohc-web-archive@ietf.org>; Mon, 8 Nov 2004 11:59:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRCsK-000739-W3
	for rohc-web-archive@ietf.org; Mon, 08 Nov 2004 12:00:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRCW3-0005EE-7c; Mon, 08 Nov 2004 11:37:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRCPn-0003h9-K4
	for rohc@megatron.ietf.org; Mon, 08 Nov 2004 11:30:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27406
	for <rohc@ietf.org>; Mon, 8 Nov 2004 11:30:44 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRCQK-00063P-Iv
	for rohc@ietf.org; Mon, 08 Nov 2004 11:31:23 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FC785>; Mon, 8 Nov 2004 16:31:30 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8803D58FB@rsys004a.roke.co.uk>
From: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
To: "'Lajos Zaccomer (IJ/ETH)'" <lajos.zaccomer@ericsson.com>, rohc@ietf.org
Subject: RE: [rohc] Shared mode
Date: Mon, 8 Nov 2004 16:31:12 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f0b5a4216bfa030ed8a6f68d1833f8ae
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 65bc4909d78e8b10349def623cf7a1d1

Hi Zacco,

Without specifying a particular application protocol behaviour (which I
agree we shouldn't do), I'm not sure that the bytecode storage example will
help.  This is because in a lot of scenarios where it could be safe, I think
it's possible to construct a similar scenario where there is a problem.
Consequently, I feel that adding another message flow may add confusion.

For example, with 2K SMS and appropriate sizes of SM1, SM2 and BC (e.g. 900
bytes, 800 bytes and 500 bytes respectively):

[SM1]
	-----------------------------> 
						[SM1]

<-----response sent uncomp/no state created--


[SM1, SM2]
	------------------------>lost
						
						[SM1, BC]
	<-------------ref SM1------------
[SM2, BC]

						[SM1, BC]
	<-------------ref SM1----------					
State access failure

We could add the sentence '(In cases where the behaviour of the application
restricts the message flow, this could be exploited to allow safe creation
of multiple minimum priority states; however, care must still be taken.)' to
the end of the recommendation paragraph.

What do you think?

Best regards,

Abbie

> -----Original Message-----
> From: Lajos Zaccomer (IJ/ETH) [mailto:lajos.zaccomer@ericsson.com] 
> Sent: Friday, November 05, 2004 3:33 PM
> To: Surtees, Abigail; rohc@ietf.org
> Subject: RE: [rohc] Shared mode
> 
> 
> Hi Abbie,
> 
> It's quite OK for me, but I'd really like to have something 
> about the possible specific relation to the higher layer 
> protocol some features of it may pose less constraints for 
> implementors. One example was given in my previous mail. 
> Neither POC nor SIP should be mentioned in the guide, of 
> course, only a general message sequence just as you did with 
> a short explanation. Is this all right?
> 
> Best regards,
> 
> Zacco
> 
> > -----Original Message-----
> > From: Surtees, Abigail [mailto:abigail.surtees@roke.co.uk]
> > Sent: Friday, November 05, 2004 3:19 PM
> > To: Lajos Zaccomer (IJ/ETH); rohc@ietf.org
> > Subject: RE: [rohc] Shared mode
> > 
> > 
> > Hi Zacco,
> > 
> > 
> > > There is another possible solution, we have not considered, 
> > > yet (just in case a simple warning would not fit the taste of 
> > > our community ;-): compressor A should not save a second 
> > > shared state until the first is freed by compressor B. This 
> > > is basically the same as the one shared state solution, but 
> > > we still have a chance to save new ones.
> > > 
> > 
> > Yes, this is a good suggestion.  It is creation of a second 
> > piece of minimum
> > priority state that causes a problem so freeing the old one 
> first also
> > solves the problem.
> > 
> > We seem to be converging on potential solutions, so I've 
> written some
> > proposed text for the implementer's guide.  This is more than 
> > a warning, but
> > hopefully it is also unrestrictive enough that you will be 
> > happy with it too
> > and we can reach WG consensus.
> > 
> > Let me know what you think:
> > 
> > "Retention Priority 65535 (or -1)
> > 
> >    There is potentially a problem with storing multiple 
> > pieces of state
> >    with the minimum retention priority (65535) as defined in SigComp
> >    [1].  This can be shown by considering the following 
> > examples, which
> >    are of shared mode SigComp Extended [2] .
> > 
> >    Example 1:
> > 
> >        Endpoint A                  Endpoint B
> >        [decomp cpt]                [comp cpt]
> > 
> >        [SM1]
> >        ------------------------------->
> >                                    [SM1]
> > 
> >        [SM1, SM2]
> >        --------------------X (message lost)
> > 
> >                                    [SM1, BC, BF1]
> >        <------------ref SM1------------
> >        [SM2, BC, BF1]
> >                                    endpoint B still believes SM1
> >                                    is at endpoint A
> > 
> >                                    [BC, BF1, BF2]
> >        <------------ref SM1------------
> > 
> >        decompression failure at A
> >        because SM1 has already been deleted
> > 
> >    Example 2:
> > 
> >        Endpoint A                  Endpoint B
> >        [decomp cpt]                [comp cpt]
> > 
> >        [SM1]
> >        ------------------------------->
> >                                    [SM1]
> > 
> >                                    [SM1, BC, BF1]
> >        (message lost)X------ref SM1-----
> > 
> >        [SM1, SM2]
> >        ------------------------------->
> >                                    endpoint B does not create SM2
> >                                    because there is no space
> >                                    [SM1, BC, BF1]
> > 
> >                                    [SM1, BC, BF1, BF2]
> >        <------------ref SM1------------
> >        [SM2, BC, BF2]
> >                                    endpoint B still believes SM1
> >                                    is at endpoint A
> > 
> >                                    [BC, BF1, BF2, BF3]
> >        <------------ref SM1------------
> > 
> >        decompression failure at A
> >        because SM1 has already been deleted
> > 
> >               Figure 2: Retention priority 65535 examples
> > 
> >    Once there is more than one piece of state of minimum 
> > priority state
> >    created in a decompressor compartment, the corresponding 
> compressor
> >    cannot be certain about which pieces of state are present in that
> >    (decompressor) compartment.  If there is only one piece of state,
> >    then no such ambiguity exists.  The problem is a 
> consequence of the
> >    different rules for the creation of minimum priority state.  In
> >    particular, the creation of the second piece of state without the
> >    knowledge of the compressor may mean that the first 
> piece is pushed
> >    out earlier than the compressor expects (despite the 
> fact that the
> >    state processing rules from SigComp [1] are being implemented
> >    correctly).
> > 
> >    SigComp [1] also states that a compressor MUST be certain 
> > that all of
> >    the data needed to decompress a SigComp message is 
> available at the
> >    receiving endpoint.  Thus it should not reference any 
> > state unless it
> >    can be sure that the state exists.  The fact that the 
> > compressor at B
> >    has no way of knowing how much state has been created at 
> A can lead
> >    to loss of synchronisation between the endpoints which is not
> >    acceptable.
> > 
> >    One observation is that it is always safe to reference a 
> piece of 
> >    minimum priority state following receipt of the 
> > advertisement of the
> > state.
> > 
> >    If it is known that both endpoints are running SigComp 
> version 2 as
> >    defined in NACK [4], then it may be reasonable to assume that the
> >    likelihood of loss of synchronisation is very small and 
> rely on the
> >    NACK mechanism for recovery.
> > 
> >    However, for a compressor to try and avoid generating 
> NACKs, it has
> >    to be able to make some assumptions about the behaviour 
> of the peer
> >    compressor.  Also if one of the endpoints does not support 
> > NACK, then
> >    some other solution is needed.
> > 
> >    Consequently, the recommendation is that only one piece 
> of minimum
> >    priority should be present in a compartment at any one 
> > time.  If both
> >    endpoints support NACK [4], then this may be relaxed, but
> >    implementers should think carefully about the consequences of
> >    creating multiple pieces of minimum priority state.
> > 
> >    Note that if a compressor wishes the remote endpoint to 
> be able to
> >    create a new piece of minimum priority state, it can use the
> >    SIGCOMP-FREE instruction to remove the existing piece of state."
> > 
> > Best regards,
> > 
> > Abbie
> > 
> > -- 
> > 
> > Visit our website at www.roke.co.uk
> > 
> > Roke Manor Research Ltd, Roke Manor, Romsey, Hampshire SO51 0ZN, UK.
> > 
> > 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.
> > 
> 

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


From rohc-bounces@ietf.org  Mon Nov  8 12:42:14 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05558
	for <rohc-web-archive@ietf.org>; Mon, 8 Nov 2004 12:42:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRDXY-0008D1-8W
	for rohc-web-archive@ietf.org; Mon, 08 Nov 2004 12:42:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRDJO-0007Df-Kr; Mon, 08 Nov 2004 12:28:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRD9x-0004Rt-V0
	for rohc@megatron.ietf.org; Mon, 08 Nov 2004 12:18:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03213
	for <rohc@ietf.org>; Mon, 8 Nov 2004 12:18:27 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRDAX-0007Zz-Qo
	for rohc@ietf.org; Mon, 08 Nov 2004 12:19:06 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FC8QQ>; Mon, 8 Nov 2004 17:19:25 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8803D58FC@rsys004a.roke.co.uk>
From: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
To: "'Carsten Bormann'" <cabo@tzi.org>
Subject: RE: [rohc] Shared mode
Date: Mon, 8 Nov 2004 17:19:07 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: rohc@ietf.org, "'Lajos Zaccomer \(IJ/ETH\)'" <lajos.zaccomer@ericsson.com>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352

Hi Carsten,

Thanks for these comments.  I've changed the first sentence of the
recommendation paragraph to:

'Consequently, where NACK is not supported or for NACK averse compressors,
the recommendation is ...'.

Is this what you meant?  I'm open to further suggestions of text.

Best regards,

Abbie

> -----Original Message-----
> From: Carsten Bormann [mailto:cabo@tzi.org] 
> Sent: Saturday, November 06, 2004 5:20 PM
> To: Surtees, Abigail
> Cc: 'Lajos Zaccomer (IJ/ETH)'; Carsten Bormann; rohc@ietf.org
> Subject: Re: [rohc] Shared mode
> 
> 
> Hi Abbie,
> 
> two more little wording proposals:
> 
> On Nov 05 2004, at 09:18 Uhr, Surtees, Abigail wrote:
> 
> > However, for a compressor to try and avoid generating NACKs
> 
> s/generating/causing the generation of/
> 
> Also, please make sure that in the recommendation paragraph, 
> you again 
> say what the presumptions are -- this is bound to be cited out of 
> context.
> 
> Gruesse, Carsten.
> 

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


From rohc-bounces@ietf.org  Mon Nov  8 23:20:08 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23837
	for <rohc-web-archive@ietf.org>; Mon, 8 Nov 2004 23:20:08 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRNUx-0007nv-UD
	for rohc-web-archive@ietf.org; Mon, 08 Nov 2004 23:20:53 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRNJR-0005g0-5Z; Mon, 08 Nov 2004 23:08:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRNCZ-0004kr-6Q
	for rohc@megatron.ietf.org; Mon, 08 Nov 2004 23:01:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22200
	for <rohc@ietf.org>; Mon, 8 Nov 2004 23:01:48 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRNDB-0007S6-Ey
	for rohc@ietf.org; Mon, 08 Nov 2004 23:02:33 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iA941eli014876; Tue, 9 Nov 2004 05:01:42 +0100 (MET)
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <109F91EC-3204-11D9-90F3-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Date: Mon, 8 Nov 2004 23:01:42 -0500
To: "'rohc@ietf.org'" <rohc@ietf.org>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>
Subject: [rohc] IETF61 slides now available
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit

ROHCers,

the slides from today's meeting are now available from the ROHC 
secondary website, http://www.dmn.tzi.org/ietf/rohc/ -- please enjoy.
Thanks to all the presenters.

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Tue Nov  9 02:15:54 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21103
	for <rohc-web-archive@ietf.org>; Tue, 9 Nov 2004 02:15:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRQEu-0002v1-M8
	for rohc-web-archive@ietf.org; Tue, 09 Nov 2004 02:16:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRQCh-0004vi-PX; Tue, 09 Nov 2004 02:14:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRQ9X-0003a5-ND
	for rohc@megatron.ietf.org; Tue, 09 Nov 2004 02:10:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16882
	for <rohc@ietf.org>; Tue, 9 Nov 2004 02:10:53 -0500 (EST)
Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRQAC-0002mC-DX
	for rohc@ietf.org; Tue, 09 Nov 2004 02:11:39 -0500
Received: from albatross.ericsson.se ([193.180.251.49])
	by mx2.foretec.com with esmtp (Exim 4.24) id 1CRPqU-00012c-T0
	for rohc@ietf.org; Tue, 09 Nov 2004 01:51:15 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iA96oXvD029518
	for <rohc@ietf.org>; Tue, 9 Nov 2004 07:50:33 +0100 (MET)
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 9 Nov 2004 07:50:31 +0100
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <WFZ2A0NA>; Tue, 9 Nov 2004 07:50:31 +0100
Message-ID: <F005CD411D18D3119C8F00508B0874800DC40456@ehubunt100.eth.ericsson.se>
From: "Lajos Zaccomer (IJ/ETH)" <lajos.zaccomer@ericsson.com>
To: "'Surtees, Abigail'" <abigail.surtees@roke.co.uk>, rohc@ietf.org
Subject: RE: [rohc] Shared mode
Date: Tue, 9 Nov 2004 07:50:28 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 09 Nov 2004 06:50:31.0795 (UTC)
	FILETIME=[67EF6430:01C4C628]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7c1a129dc3801d79d40c5ca8dee767eb
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cbb41f2dbf0f142369614756642005e3

Hi Abbie,

Nice sentence, I like it! :-) If one really needs it, they would probably not miss the message flow.

br/Zacco

> -----Original Message-----
> From: Surtees, Abigail [mailto:abigail.surtees@roke.co.uk]
> Sent: Monday, November 08, 2004 5:31 PM
> To: Lajos Zaccomer (IJ/ETH); rohc@ietf.org
> Subject: RE: [rohc] Shared mode
> 
> 
> Hi Zacco,
> 
> Without specifying a particular application protocol 
> behaviour (which I
> agree we shouldn't do), I'm not sure that the bytecode 
> storage example will
> help.  This is because in a lot of scenarios where it could 
> be safe, I think
> it's possible to construct a similar scenario where there is 
> a problem.
> Consequently, I feel that adding another message flow may add 
> confusion.
> 
> For example, with 2K SMS and appropriate sizes of SM1, SM2 
> and BC (e.g. 900
> bytes, 800 bytes and 500 bytes respectively):
> 
> [SM1]
> 	-----------------------------> 
> 						[SM1]
> 
> <-----response sent uncomp/no state created--
> 
> 
> [SM1, SM2]
> 	------------------------>lost
> 						
> 						[SM1, BC]
> 	<-------------ref SM1------------
> [SM2, BC]
> 
> 						[SM1, BC]
> 	<-------------ref SM1----------					
> State access failure
> 
> We could add the sentence '(In cases where the behaviour of 
> the application
> restricts the message flow, this could be exploited to allow 
> safe creation
> of multiple minimum priority states; however, care must still 
> be taken.)' to
> the end of the recommendation paragraph.
> 
> What do you think?
> 
> Best regards,
> 
> Abbie
> 
> > -----Original Message-----
> > From: Lajos Zaccomer (IJ/ETH) [mailto:lajos.zaccomer@ericsson.com] 
> > Sent: Friday, November 05, 2004 3:33 PM
> > To: Surtees, Abigail; rohc@ietf.org
> > Subject: RE: [rohc] Shared mode
> > 
> > 
> > Hi Abbie,
> > 
> > It's quite OK for me, but I'd really like to have something 
> > about the possible specific relation to the higher layer 
> > protocol some features of it may pose less constraints for 
> > implementors. One example was given in my previous mail. 
> > Neither POC nor SIP should be mentioned in the guide, of 
> > course, only a general message sequence just as you did with 
> > a short explanation. Is this all right?
> > 
> > Best regards,
> > 
> > Zacco
> > 
> > > -----Original Message-----
> > > From: Surtees, Abigail [mailto:abigail.surtees@roke.co.uk]
> > > Sent: Friday, November 05, 2004 3:19 PM
> > > To: Lajos Zaccomer (IJ/ETH); rohc@ietf.org
> > > Subject: RE: [rohc] Shared mode
> > > 
> > > 
> > > Hi Zacco,
> > > 
> > > 
> > > > There is another possible solution, we have not considered, 
> > > > yet (just in case a simple warning would not fit the taste of 
> > > > our community ;-): compressor A should not save a second 
> > > > shared state until the first is freed by compressor B. This 
> > > > is basically the same as the one shared state solution, but 
> > > > we still have a chance to save new ones.
> > > > 
> > > 
> > > Yes, this is a good suggestion.  It is creation of a second 
> > > piece of minimum
> > > priority state that causes a problem so freeing the old one 
> > first also
> > > solves the problem.
> > > 
> > > We seem to be converging on potential solutions, so I've 
> > written some
> > > proposed text for the implementer's guide.  This is more than 
> > > a warning, but
> > > hopefully it is also unrestrictive enough that you will be 
> > > happy with it too
> > > and we can reach WG consensus.
> > > 
> > > Let me know what you think:
> > > 
> > > "Retention Priority 65535 (or -1)
> > > 
> > >    There is potentially a problem with storing multiple 
> > > pieces of state
> > >    with the minimum retention priority (65535) as defined 
> in SigComp
> > >    [1].  This can be shown by considering the following 
> > > examples, which
> > >    are of shared mode SigComp Extended [2] .
> > > 
> > >    Example 1:
> > > 
> > >        Endpoint A                  Endpoint B
> > >        [decomp cpt]                [comp cpt]
> > > 
> > >        [SM1]
> > >        ------------------------------->
> > >                                    [SM1]
> > > 
> > >        [SM1, SM2]
> > >        --------------------X (message lost)
> > > 
> > >                                    [SM1, BC, BF1]
> > >        <------------ref SM1------------
> > >        [SM2, BC, BF1]
> > >                                    endpoint B still believes SM1
> > >                                    is at endpoint A
> > > 
> > >                                    [BC, BF1, BF2]
> > >        <------------ref SM1------------
> > > 
> > >        decompression failure at A
> > >        because SM1 has already been deleted
> > > 
> > >    Example 2:
> > > 
> > >        Endpoint A                  Endpoint B
> > >        [decomp cpt]                [comp cpt]
> > > 
> > >        [SM1]
> > >        ------------------------------->
> > >                                    [SM1]
> > > 
> > >                                    [SM1, BC, BF1]
> > >        (message lost)X------ref SM1-----
> > > 
> > >        [SM1, SM2]
> > >        ------------------------------->
> > >                                    endpoint B does not create SM2
> > >                                    because there is no space
> > >                                    [SM1, BC, BF1]
> > > 
> > >                                    [SM1, BC, BF1, BF2]
> > >        <------------ref SM1------------
> > >        [SM2, BC, BF2]
> > >                                    endpoint B still believes SM1
> > >                                    is at endpoint A
> > > 
> > >                                    [BC, BF1, BF2, BF3]
> > >        <------------ref SM1------------
> > > 
> > >        decompression failure at A
> > >        because SM1 has already been deleted
> > > 
> > >               Figure 2: Retention priority 65535 examples
> > > 
> > >    Once there is more than one piece of state of minimum 
> > > priority state
> > >    created in a decompressor compartment, the corresponding 
> > compressor
> > >    cannot be certain about which pieces of state are 
> present in that
> > >    (decompressor) compartment.  If there is only one 
> piece of state,
> > >    then no such ambiguity exists.  The problem is a 
> > consequence of the
> > >    different rules for the creation of minimum priority state.  In
> > >    particular, the creation of the second piece of state 
> without the
> > >    knowledge of the compressor may mean that the first 
> > piece is pushed
> > >    out earlier than the compressor expects (despite the 
> > fact that the
> > >    state processing rules from SigComp [1] are being implemented
> > >    correctly).
> > > 
> > >    SigComp [1] also states that a compressor MUST be certain 
> > > that all of
> > >    the data needed to decompress a SigComp message is 
> > available at the
> > >    receiving endpoint.  Thus it should not reference any 
> > > state unless it
> > >    can be sure that the state exists.  The fact that the 
> > > compressor at B
> > >    has no way of knowing how much state has been created at 
> > A can lead
> > >    to loss of synchronisation between the endpoints which is not
> > >    acceptable.
> > > 
> > >    One observation is that it is always safe to reference a 
> > piece of 
> > >    minimum priority state following receipt of the 
> > > advertisement of the
> > > state.
> > > 
> > >    If it is known that both endpoints are running SigComp 
> > version 2 as
> > >    defined in NACK [4], then it may be reasonable to 
> assume that the
> > >    likelihood of loss of synchronisation is very small and 
> > rely on the
> > >    NACK mechanism for recovery.
> > > 
> > >    However, for a compressor to try and avoid generating 
> > NACKs, it has
> > >    to be able to make some assumptions about the behaviour 
> > of the peer
> > >    compressor.  Also if one of the endpoints does not support 
> > > NACK, then
> > >    some other solution is needed.
> > > 
> > >    Consequently, the recommendation is that only one piece 
> > of minimum
> > >    priority should be present in a compartment at any one 
> > > time.  If both
> > >    endpoints support NACK [4], then this may be relaxed, but
> > >    implementers should think carefully about the consequences of
> > >    creating multiple pieces of minimum priority state.
> > > 
> > >    Note that if a compressor wishes the remote endpoint to 
> > be able to
> > >    create a new piece of minimum priority state, it can use the
> > >    SIGCOMP-FREE instruction to remove the existing piece 
> of state."
> > > 
> > > Best regards,
> > > 
> > > Abbie
> > > 
> > > -- 
> > > 
> > > Visit our website at www.roke.co.uk
> > > 
> > > Roke Manor Research Ltd, Roke Manor, Romsey, Hampshire 
> SO51 0ZN, UK.
> > > 
> > > 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.
> > > 
> > 
> 
> -- 
> 
> Visit our website at www.roke.co.uk
> 
> Roke Manor Research Ltd, Roke Manor, Romsey, Hampshire SO51 0ZN, UK.
> 
> 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.
> 

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


From rohc-bounces@ietf.org  Tue Nov  9 06:52:47 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15261
	for <rohc-web-archive@ietf.org>; Tue, 9 Nov 2004 06:52:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRUZ6-0000hS-Tm
	for rohc-web-archive@ietf.org; Tue, 09 Nov 2004 06:53:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRUXb-000606-EP; Tue, 09 Nov 2004 06:52:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRUS5-00056i-Ih
	for rohc@megatron.ietf.org; Tue, 09 Nov 2004 06:46:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14789
	for <rohc@ietf.org>; Tue, 9 Nov 2004 06:46:18 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRUSm-0000Wo-2J
	for rohc@ietf.org; Tue, 09 Nov 2004 06:47:07 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FDGC5>; Tue, 9 Nov 2004 11:46:53 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8801A2256@rsys004a.roke.co.uk>
From: "Finking, Robert" <robert.finking@roke.co.uk>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Tue, 9 Nov 2004 11:46:52 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Subject: [rohc] RoHC-FN List encoding question
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64

I was just reading through the slides Carsten posted (thanks Carsten, and
also those who prepared them), and a little flag came up in my mind about an
unanswered question I had on type 0 list encoding, but don't think I ever
got to ask about it before I got dragged off onto other things.

In the XI list, you have a list of either four or eight bit fields, the most
significant bit of which is a flag, X. I had previously been under the
impression that this flag gave an indication of whether or not this item was
  1. either a new table item or an update to an existing item, and so had no
context available, or
  2. already present in the table and so did have context available

The description of list encoding in the current FN draft is based on the
above understanding, which I recall is incorrect. So my question is this:
what does the X bit mean?

I have a vague recollection that it indicates whether or not an item is
present in the list, but that can't be right. What would be the difference
between this XI list:

   X   Index
   1   001
   1   010
   1   100
   1   101

...and this one:

   X   Index
   1   001
   1   010
   0   011
   1   100
   1   101
   0   110

What I'm saying is, what is the point of having a bit to indicate that an
item is present or absent, when you can already indicate presence or absence
by having the item in the list (or not)?

I'm sure there is something basic I have misunderstood here. Can somebody
help me out? I'm hoping to be able to produce a revised list section as a
result of this.

Hope you're all enjoying IETF61!

Thanks in advance

Raffles

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


From rohc-bounces@ietf.org  Tue Nov  9 09:24:37 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01208
	for <rohc-web-archive@ietf.org>; Tue, 9 Nov 2004 09:24:37 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRWvz-0004sQ-3n
	for rohc-web-archive@ietf.org; Tue, 09 Nov 2004 09:25:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRWjG-00024o-FF; Tue, 09 Nov 2004 09:12:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRWe9-0006T0-S4
	for rohc@megatron.ietf.org; Tue, 09 Nov 2004 09:06:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28986
	for <rohc@ietf.org>; Tue, 9 Nov 2004 09:06:55 -0500 (EST)
Received: from [194.237.235.30] (helo=effnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRWet-0004M5-VG
	for rohc@ietf.org; Tue, 09 Nov 2004 09:07:44 -0500
Received: from [130.129.135.32] ([130.129.135.32]) (authenticated bits=0)
	by effnet.com (8.12.3/8.12.3) with ESMTP id iA9D5uLh012783
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Tue, 9 Nov 2004 14:05:57 +0100
Message-ID: <4190DCF4.4000703@effnet.com>
Date: Tue, 09 Nov 2004 16:06:28 +0100
From: Kristofer Sandlund <kristofer.sandlund@effnet.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20041030
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Finking, Robert" <robert.finking@roke.co.uk>
Subject: Re: [rohc] RoHC-FN List encoding question
References: <3F2E01E1D7B04F4EBEC92D3FA324D8801A2256@rsys004a.roke.co.uk>
In-Reply-To: <3F2E01E1D7B04F4EBEC92D3FA324D8801A2256@rsys004a.roke.co.uk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Content-Transfer-Encoding: 7bit
Cc: "'rohc@ietf.org'" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Content-Transfer-Encoding: 7bit

Hi Robert,

we reworked parts of the list compression yesterday evening, so hold off 
on updating things for now. We'll send you the results when we have 
something a bit more stable.

For your questions, see inline.

Finking, Robert wrote:
> I was just reading through the slides Carsten posted (thanks Carsten, and
> also those who prepared them), and a little flag came up in my mind about an
> unanswered question I had on type 0 list encoding, but don't think I ever
> got to ask about it before I got dragged off onto other things.
> 
> In the XI list, you have a list of either four or eight bit fields, the most
> significant bit of which is a flag, X. I had previously been under the
> impression that this flag gave an indication of whether or not this item was
>   1. either a new table item or an update to an existing item, and so had no
> context available, or
>   2. already present in the table and so did have context available
> 

X=1 simply means that this index is being sent in the item field of this 
  list. It does not mean that this is present in the table or not. A 
compressor could choose to send all items with X=1 even if the items 
never change (it would not be very smart, but...)

X=0 the means that the item is not sent in this list packet, but it is 
still present in the decompressed list. Sending X=0 is only allowed if 
the compressor has confidence that the decompressor has this item in its 
table.

> The description of list encoding in the current FN draft is based on the
> above understanding, which I recall is incorrect. So my question is this:
> what does the X bit mean?
> 
> I have a vague recollection that it indicates whether or not an item is
> present in the list, but that can't be right. What would be the difference
> between this XI list:
> 
>    X   Index
>    1   001
>    1   010
>    1   100
>    1   101
>

This would say that the item field of the type 0 list would contain 
items [1, 2, 4, 5], and the decompressed list would contain [1, 2, 4, 5] 
(identical)


> ...and this one:
> 
>    X   Index
>    1   001
>    1   010
>    0   011
>    1   100
>    1   101
>    0   110
>

Here, the item field would be [1, 2, 4, 5] and the decompressed list 
would contain [1, 2, 3, 4, 5, 6].

So, the item field of the type 0 list would be identical, but not the 
decompressed list. You're confusing the compressed and uncomrpessed parts.

Hope that explains it.

/Kristofer

> What I'm saying is, what is the point of having a bit to indicate that an
> item is present or absent, when you can already indicate presence or absence
> by having the item in the list (or not)?
> 
> I'm sure there is something basic I have misunderstood here. Can somebody
> help me out? I'm hoping to be able to produce a revised list section as a
> result of this.
> 
> Hope you're all enjoying IETF61!
> 
> Thanks in advance
> 
> Raffles
> 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc

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


From rohc-bounces@ietf.org  Tue Nov  9 12:23:41 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22011
	for <rohc-web-archive@ietf.org>; Tue, 9 Nov 2004 12:23:41 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRZjM-0001Hi-LQ
	for rohc-web-archive@ietf.org; Tue, 09 Nov 2004 12:24:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRZOQ-0007ib-5X; Tue, 09 Nov 2004 12:02:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRZEb-0006Ao-Rl
	for rohc@megatron.ietf.org; Tue, 09 Nov 2004 11:52:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19267
	for <rohc@ietf.org>; Tue, 9 Nov 2004 11:52:42 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRZFN-0000Tl-6U
	for rohc@ietf.org; Tue, 09 Nov 2004 11:53:34 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FDJL5>; Tue, 9 Nov 2004 16:53:26 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8801A2257@rsys004a.roke.co.uk>
From: "Finking, Robert" <robert.finking@roke.co.uk>
To: "'Kristofer Sandlund'" <kristofer.sandlund@effnet.com>
Subject: RE: [rohc] RoHC-FN List encoding question
Date: Tue, 9 Nov 2004 16:53:25 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: "'rohc@ietf.org'" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d

Kris,

Many thanks - as always you are the man when it comes to type 0 list
encoding =) 

Responses in line.

Regards

Raffles

> -----Original Message-----
> From: Kristofer Sandlund [mailto:kristofer.sandlund@effnet.com] 
> Sent: Tuesday, November 09, 2004 3:06 PM
> To: Finking, Robert
> Cc: 'rohc@ietf.org'
> Subject: Re: [rohc] RoHC-FN List encoding question
> 
> 
> Hi Robert,
> 
> we reworked parts of the list compression yesterday evening, 
> so hold off 
> on updating things for now. We'll send you the results when we have 
> something a bit more stable.

Great - thanks =)

> <snip>
> > significant bit of which is a flag, X. I had previously 
> been under the
> > impression that this flag gave an indication of whether or 
> not this item was
> >   1. either a new table item or an update to an existing 
> item, and so had no
> > context available, or
> >   2. already present in the table and so did have context available
> > 
> 
> X=1 simply means that this index is being sent in the item 
> field of this 
>   list. It does not mean that this is present in the table or not. A 
> compressor could choose to send all items with X=1 even if the items 
> never change (it would not be very smart, but...)
> 
> X=0 the means that the item is not sent in this list packet, 
> but it is 
> still present in the decompressed list. Sending X=0 is only 
> allowed if 
> the compressor has confidence that the decompressor has this 
> item in its 
> table.
> 
OK, great, So, if I have understood correctly, my original understanding was
very close to the truth, with the exception that a non-optimal compressor
may choose to set the X bit, and send the item when it doesn't need to,
(conversely I guess an erroneous compressor could leave the bit clear, and
not send the item, when it should have).

In that case I don't see what is missing from the existing list compression
syntax? Or is there yet another level of misunderstanding on my part ;-) I
wish I could be there to join in with the discussions.

<snip>
> 
> Hope that explains it.

Yes, very well - thanks. My original understanding was very close to the
truth, my recollection that I'd got it wrong was obviously flawed! Thanks
for clearing it up.

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


From rohc-bounces@ietf.org  Tue Nov  9 19:52:39 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04282
	for <rohc-web-archive@ietf.org>; Tue, 9 Nov 2004 19:52:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRgjv-0003LV-EX
	for rohc-web-archive@ietf.org; Tue, 09 Nov 2004 19:53:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRgda-0005Qk-6L; Tue, 09 Nov 2004 19:47:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRgWB-0003g4-8y
	for rohc@megatron.ietf.org; Tue, 09 Nov 2004 19:39:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03221
	for <rohc@ietf.org>; Tue, 9 Nov 2004 19:39:19 -0500 (EST)
Received: from mavis.erg.abdn.ac.uk ([139.133.204.77] helo=erg.abdn.ac.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRgX1-00035U-Ol
	for rohc@ietf.org; Tue, 09 Nov 2004 19:40:16 -0500
Received: from [130.129.134.197] ([130.129.134.197]) (authenticated bits=0)
	by erg.abdn.ac.uk (8.12.11/8.12.11) with ESMTP id iAA0cAdw026862
	(version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT);
	Wed, 10 Nov 2004 00:38:11 GMT
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Tue, 09 Nov 2004 19:38:02 -0500
From: Gorry Fairhurst <gf@erg.abdn.ac.uk>
To: <rohc@ietf.org>
Message-ID: <BDB6CD1A.17DA%gf@erg.abdn.ac.uk>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gf@erg.abdn.ac.uk
X-ERG-MailScanner-To: gorry@erg.abdn.ac.uk, rohc@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Subject: [rohc] Does ROHC break PMTU?
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit


This issue was raised in PMTUD WG by Magnus Westerlund, and I've expanded it
with a few thoughts below:

1) ROHC by its nature can produce a variable-sized network-layer packet
overhead, given a fixed sized link frame (or segmentation/reassembly payload
if you are using transparent fragmentation), this appears to result in  a
variable size Link MTU. Carsten pointed out that ROHC can expand headers
also in some cases, not just compress them.

2) Path MTU discovery (typically with TCP, but we could talk about UDP, etc)
probes for bandwidth. If it probes over a path with varying MTU the effects
are likely to have undesirable side-effects with PMTUD.

3) Is this an issue?
This depends on how (where) you perform Link MTU checks when a link (header)
compression scheme is used. Two options come to mind:

* If the Link were to check the Link MTU of each packet to be forwarded
based on the actual limit of the compressed size (see 1 above), then the
link MTU could vary from packet to packet within a flow.

* If the Link instead checked the minimum uncompressed size that was
guaranteed, and represented this as the Link MTU, there would be no problem.

I vote for the second one - any thoughts from others on the list, about what
should be done (or what is done)?

-----

Is this written anywhere in a ROHC document?

- My recollection was only the TCP Behaviour document talked about MTU, and
I don't recall this provided any guidance on this.


Gorry 



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


From rohc-bounces@ietf.org  Tue Nov  9 23:31:33 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21495
	for <rohc-web-archive@ietf.org>; Tue, 9 Nov 2004 23:31:33 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRk9n-0007ao-7c
	for rohc-web-archive@ietf.org; Tue, 09 Nov 2004 23:32:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRk7q-0002lM-G6; Tue, 09 Nov 2004 23:30:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRk1W-0001aX-Bp
	for rohc@megatron.ietf.org; Tue, 09 Nov 2004 23:23:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20880
	for <rohc@ietf.org>; Tue, 9 Nov 2004 23:23:55 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRk2F-0007Sf-4r
	for rohc@ietf.org; Tue, 09 Nov 2004 23:24:53 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iAA4NNXp001206; Wed, 10 Nov 2004 05:23:29 +0100 (MET)
In-Reply-To: <BDB6CD1A.17DA%gf@erg.abdn.ac.uk>
References: <BDB6CD1A.17DA%gf@erg.abdn.ac.uk>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <43110FF7-32D0-11D9-90F3-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] Does ROHC break PMTU?
Date: Tue, 9 Nov 2004 23:23:24 -0500
To: Gorry Fairhurst <gf@erg.abdn.ac.uk>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Carsten Bormann <cabo@tzi.org>,
        rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit

On Nov 09 2004, at 19:38 Uhr, Gorry Fairhurst wrote:

> * If the Link were to check the Link MTU of each packet to be forwarded
> based on the actual limit of the compressed size (see 1 above), then 
> the
> link MTU could vary from packet to packet within a flow.
>
> * If the Link instead checked the minimum uncompressed size that was
> guaranteed, and represented this as the Link MTU, there would be no 
> problem.

I think the fun issue here comes up with tunnels, where ROHC itself 
would have to do PMTU discovery to do 2.
Most non-tunnel ROHC links have link MTUs in excess of the "Internet 
MTU" (1500--).
(802 will provide new challenges, but still will have a predictable 
link MTU.)
Note also that ROHC does have a segmentation protocol, so if all else 
fails, a packet can be segmented to avoid an ICMP too big.

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Wed Nov 10 14:22:01 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15782
	for <rohc-web-archive@ietf.org>; Wed, 10 Nov 2004 14:22:01 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRy3d-0002ZQ-SQ
	for rohc-web-archive@ietf.org; Wed, 10 Nov 2004 14:23:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRxvH-0003Af-FV; Wed, 10 Nov 2004 14:14:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRxqu-0002EI-A3
	for rohc@megatron.ietf.org; Wed, 10 Nov 2004 14:09:56 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14505
	for <rohc@ietf.org>; Wed, 10 Nov 2004 14:09:54 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRxrl-0002F8-2A
	for rohc@ietf.org; Wed, 10 Nov 2004 14:10:59 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iAAJ9G5n012429; Wed, 10 Nov 2004 20:09:36 +0100 (MET)
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <04ED103E-334C-11D9-90F3-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Date: Wed, 10 Nov 2004 14:09:17 -0500
To: "'rohc@ietf.org'" <rohc@ietf.org>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>
Subject: [rohc] ROHC issues list
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit

ROHCers,

I have started cleaning up the ROHC issues list.
We should strive to have the remaining open issues in tcp-08 and the 
supporting formal-notation-04 in this list.

Please refer to

	http://nsis.srmr.co.uk/cgi-bin/roundup.cgi/rohc-issues/

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Thu Nov 11 05:18:59 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21471
	for <rohc-web-archive@ietf.org>; Thu, 11 Nov 2004 05:18:59 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSC3o-00066Q-Il
	for rohc-web-archive@ietf.org; Thu, 11 Nov 2004 05:20:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSC13-0007Iy-Ln; Thu, 11 Nov 2004 05:17:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSBve-00069f-HW
	for rohc@megatron.ietf.org; Thu, 11 Nov 2004 05:11:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20897
	for <rohc@ietf.org>; Thu, 11 Nov 2004 05:11:44 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSBwn-0005vj-BP
	for rohc@ietf.org; Thu, 11 Nov 2004 05:12:57 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FD91N>; Thu, 11 Nov 2004 10:12:28 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8801A2268@rsys004a.roke.co.uk>
From: "Finking, Robert" <robert.finking@roke.co.uk>
To: "'Carsten Bormann'" <cabo@tzi.org>
Subject: RE: IMPORTANT: RE: [rohc] RoHC-FN List encoding question
Date: Thu, 11 Nov 2004 10:12:20 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: "'rohc@ietf.org'" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5



From: Carsten Bormann [mailto:cabo@tzi.org] 
Sent: Wednesday, November 10, 2004 2:52 PM
> 
> 
> On Nov 10 2004, at 05:56 Uhr, Finking, Robert wrote:
> 
> > The whole point of the list notation is to
> > avoid having all that extra junk! All the notator should have to 
> > specify is
> > what items can appear in the list.
> 
> We were trying to get rid of any special list notation because it is 
> harder for the notator to understand both the strange things list 
> notation does and the specification in this notation than just the 
> things that need to be said in (normal) FN notation.
> 
> I believe we have succeeded in simplifying things considerably.

You have succeeded in simplifying the notation considerably, but not the
profile - you have made that more complicated - and let's not forget that
the profile is the focus of our development here ;-) For the profile to be
simple to read and understand, the notation must take on the complexity.
Otherwise the profile will be impenetrable. (I would like to suggest at this
point that the box/English notation is an extreme example of this - very
simple notation = very complicated profile)

Cheers

Raffles

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


From rohc-bounces@ietf.org  Thu Nov 11 05:25:09 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21989
	for <rohc-web-archive@ietf.org>; Thu, 11 Nov 2004 05:25:08 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSC9i-0006Dm-V6
	for rohc-web-archive@ietf.org; Thu, 11 Nov 2004 05:26:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSC6y-0008FQ-7g; Thu, 11 Nov 2004 05:23:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSC2D-0007TQ-Vc
	for rohc@megatron.ietf.org; Thu, 11 Nov 2004 05:18:34 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21453
	for <rohc@ietf.org>; Thu, 11 Nov 2004 05:18:32 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSC3M-00064y-UT
	for rohc@ietf.org; Thu, 11 Nov 2004 05:19:45 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FD92A>; Thu, 11 Nov 2004 10:19:18 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8801A2269@rsys004a.roke.co.uk>
From: "Finking, Robert" <robert.finking@roke.co.uk>
To: "'Lars-Erik Jonsson (LU/EAB)'" <lars-erik.jonsson@ericsson.com>
Subject: RE: IMPORTANT: RE: [rohc] RoHC-FN List encoding question
Date: Thu, 11 Nov 2004 10:19:11 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: "'rohc@ietf.org'" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4

Answers inline.

Regards

Raffles

PS I've posted this to the list since this is a major issue which others may
be interested in - I hope that's OK!

> > 
> > So, my suggestion would be to go to box notation and drop the 
> > entire FN, but I know that both Carsten and you still like
> > this. But I'm getting sick of never being able tro agree on
> > anything and depending on who's got the token we revise what
> > the last guy wrote (not putting more blame on anyone, I think
> > we've all been equally bad). 
> 
> I agree we've reached the point when we should really give up
> the FN experiment and let the TCP profile be completed, which
> we know we can do with traditional box notation and english
> text.
> 
> As a Swedish pessimism consultant use to say, "It's never too
> late to give up"...=)

Eeek!

Here's my tuppence: now is a crazy time to give up on the FN TCP profile.
It's almost there! If we were going to gain any benefit on abandoning the
FN, we should have done it years ago. As is always the case with these
things, you get the biggest benefit by making a decision early in the day.
However I'm glad you didn't abandon it, because the benefit the notation
brings IMHO far outweighs the benefit you'd have had by abandoning it.

I put it to you that going over to the box notation at this stage would take
longer than finishing off the "almost there" FN TCP profile. Meantime you
will end up with all the problems that the box notation/English description
brings.

I put it to you that the bits that are difficult from a notational point of
view are not difficult because of the notation, they're just inherently
complex. Therefore there will be the same difficulties describing these in
English/ASCII art as we're having in the formal notation, only you've lost
the formality. To me, these are the parts of the profile that most need to
be defined formally, since they're the parts which are most likely to be
misunderstood/misimplemented.


> 
> > We've not had ANY focus whatsoever on the packet formats
> > themselves, I think it's only me and Mark that have actually
> > tried to see what's in them! And with a situation like that
> > I think we NEED to throw out the FN from ROHC-TCP and do it
> > NOW!
> 
> YES!
> Getting focus back to the TCP profile and it's packet format
> details is essential to ever be able to complete this work.
> 
> /L-E
> 

Well that's not *quite* fair, I've made a couple of postings about the TCP
profile! Still I take your point =)

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


From rohc-bounces@ietf.org  Thu Nov 11 07:17:12 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01828
	for <rohc-web-archive@ietf.org>; Thu, 11 Nov 2004 07:17:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSDuE-00006S-Pl
	for rohc-web-archive@ietf.org; Thu, 11 Nov 2004 07:18:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSDq5-00085U-Cu; Thu, 11 Nov 2004 07:14:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSDmj-0007Gk-M7
	for rohc@megatron.ietf.org; Thu, 11 Nov 2004 07:10:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01401
	for <rohc@ietf.org>; Thu, 11 Nov 2004 07:10:39 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSDnj-0008PY-CO
	for rohc@ietf.org; Thu, 11 Nov 2004 07:11:53 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iABCAAhK000356; Thu, 11 Nov 2004 13:10:17 +0100 (MET)
In-Reply-To: <3F2E01E1D7B04F4EBEC92D3FA324D8801A2268@rsys004a.roke.co.uk>
References: <3F2E01E1D7B04F4EBEC92D3FA324D8801A2268@rsys004a.roke.co.uk>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <A4BBB45C-33DA-11D9-90F3-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: IMPORTANT: RE: [rohc] RoHC-FN List encoding question
Date: Thu, 11 Nov 2004 07:10:14 -0500
To: "Finking, Robert" <robert.finking@roke.co.uk>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, "'rohc@ietf.org'" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit

On Nov 11 2004, at 05:12 Uhr, Finking, Robert wrote:

> You have succeeded in simplifying the notation considerably, but not 
> the
> profile - you have made that more complicated - and let's not forget 
> that
> the profile is the focus of our development here ;-) For the profile 
> to be
> simple to read and understand, the notation must take on the 
> complexity.

In the end, the reader needs to understand both.  If the interfacing 
between the "simpler" list notation and the text in the FN 
specification is becoming too complex, this is counterproductive.
Besides, the FN spec is really barely more complicated the way we have 
done it now.

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Thu Nov 11 09:56:48 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17683
	for <rohc-web-archive@ietf.org>; Thu, 11 Nov 2004 09:56:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSGOW-0003yg-QW
	for rohc-web-archive@ietf.org; Thu, 11 Nov 2004 09:58:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSGLk-0003CR-It; Thu, 11 Nov 2004 09:55:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSGJA-0002TC-2j
	for rohc@megatron.ietf.org; Thu, 11 Nov 2004 09:52:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17030
	for <rohc@ietf.org>; Thu, 11 Nov 2004 09:52:18 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSGKB-0003pg-4S
	for rohc@ietf.org; Thu, 11 Nov 2004 09:53:33 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iABEq7vD001303
	for <rohc@ietf.org>; Thu, 11 Nov 2004 15:52:08 +0100 (MET)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 11 Nov 2004 15:52:06 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <WRVV4QH9>; Thu, 11 Nov 2004 15:52:06 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E98F2@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Thu, 11 Nov 2004 15:52:02 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="ISO-8859-1"
X-OriginalArrivalTime: 11 Nov 2004 14:52:06.0321 (UTC)
	FILETIME=[033DAA10:01C4C7FE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Subject: [rohc] ROHC TCP PF discussion (was: RE: IMPORTANT)
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433

ROHCers,

Some of you might be surprised by this discussion popping up. As
you probably have understood, we had some offline discussions
between the draft authors yesterday and one of the mails from 
the middle of that discussion went to the list, potentially
causing some confusion.

Anyway, the discussion was about the fact that we have been
sidetracked by the Formal Notation issues for so long, and
almost forgotten that our work is actually about creating
compressed packet formats for ROHC TCP. In this discussion, we
also noticed that if we can not manage to create formats based
on the Formal Notation, nothing prevents us from going back to
traditional box notation. We want the Formal Notation to be a
helpful tool in profile definition and documentation, not an 
obstacle.

Now, we are hopefully back on track finishing the packet 
formats, focusing on content. Whether we will then be able to
finally document these in FN or if we turn back to box notation
is a rather minor issue, as long as we can finalize this work.
It has been more than a year now when we have said that we are
"almost there" with the FN. It is a fact that we had been done
with the TCP profile long ago if it had not been for our desire
to get it FN-based. It is never fun to give up on something you
have spent significant efforts on, but sometimes one has to take
tough decisions. Anyway, focus is now on packet format contents,
then we'll see what documentation method that can deliver.

Cheers,
/L-E


> -----Original Message-----
> From: Finking, Robert [mailto:robert.finking@roke.co.uk]
> Sent: den 11 november 2004 11:19
> To: Lars-Erik Jonsson (LU/EAB)
> Cc: 'rohc@ietf.org'
> Subject: RE: IMPORTANT: RE: [rohc] RoHC-FN List encoding question
> 
> 
> Answers inline.
> 
> Regards
> 
> Raffles
> 
> PS I've posted this to the list since this is a major issue 
> which others may
> be interested in - I hope that's OK!
> 
> > > 
> > > So, my suggestion would be to go to box notation and drop the 
> > > entire FN, but I know that both Carsten and you still like
> > > this. But I'm getting sick of never being able tro agree on
> > > anything and depending on who's got the token we revise what
> > > the last guy wrote (not putting more blame on anyone, I think
> > > we've all been equally bad). 
> > 
> > I agree we've reached the point when we should really give up
> > the FN experiment and let the TCP profile be completed, which
> > we know we can do with traditional box notation and english
> > text.
> > 
> > As a Swedish pessimism consultant use to say, "It's never too
> > late to give up"...=)
> 
> Eeek!
> 
> Here's my tuppence: now is a crazy time to give up on the FN 
> TCP profile.
> It's almost there! If we were going to gain any benefit on 
> abandoning the
> FN, we should have done it years ago. As is always the case with these
> things, you get the biggest benefit by making a decision 
> early in the day.
> However I'm glad you didn't abandon it, because the benefit 
> the notation
> brings IMHO far outweighs the benefit you'd have had by abandoning it.
> 
> I put it to you that going over to the box notation at this 
> stage would take
> longer than finishing off the "almost there" FN TCP profile. 
> Meantime you
> will end up with all the problems that the box 
> notation/English description
> brings.
> 
> I put it to you that the bits that are difficult from a 
> notational point of
> view are not difficult because of the notation, they're just 
> inherently
> complex. Therefore there will be the same difficulties 
> describing these in
> English/ASCII art as we're having in the formal notation, 
> only you've lost
> the formality. To me, these are the parts of the profile that 
> most need to
> be defined formally, since they're the parts which are most 
> likely to be
> misunderstood/misimplemented.
> 
> 
> > 
> > > We've not had ANY focus whatsoever on the packet formats
> > > themselves, I think it's only me and Mark that have actually
> > > tried to see what's in them! And with a situation like that
> > > I think we NEED to throw out the FN from ROHC-TCP and do it
> > > NOW!
> > 
> > YES!
> > Getting focus back to the TCP profile and it's packet format
> > details is essential to ever be able to complete this work.
> > 
> > /L-E
> > 

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


From rohc-bounces@ietf.org  Fri Nov 12 11:50:28 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19541
	for <rohc-web-archive@ietf.org>; Fri, 12 Nov 2004 11:50:28 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSeeI-0004a8-25
	for rohc-web-archive@ietf.org; Fri, 12 Nov 2004 11:51:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSeY6-0003R2-4f; Fri, 12 Nov 2004 11:45:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSeWG-0002Zc-P4
	for rohc@megatron.ietf.org; Fri, 12 Nov 2004 11:43:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18733
	for <rohc@ietf.org>; Fri, 12 Nov 2004 11:43:26 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSeXg-0004OT-1r
	for rohc@ietf.org; Fri, 12 Nov 2004 11:44:56 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iACGhRR2024359 for <rohc@ietf.org>; Fri, 12 Nov 2004 17:43:27 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 12 Nov 2004 17:43:27 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <WRVV0FYR>; Fri, 12 Nov 2004 17:42:43 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E98FC@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Fri, 12 Nov 2004 17:42:39 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="ISO-8859-1"
X-OriginalArrivalTime: 12 Nov 2004 16:43:27.0141 (UTC)
	FILETIME=[BBBBA550:01C4C8D6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ccfb4541e989aa743998098cd315d0fd
Subject: [rohc] Preliminary minutes from ROHC@IETF61, Part 1
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93df555cbdbcdae9621e5b95d44b301e

ROHCers,

Here is a preliminary version of the minutes from the first
half of the ROHC session in Washington DC. Feedback is as
always appreciated.

BR
/L-E





Minutes of the ROHC WG session at IETF 61
=========================================

Hilton Washington, Washington DC, USA
Monday Morning, 2004-11-08

Chairs: Carsten Bormann & Lars-Erik Jonsson

Reported by: Lars-Erik Jonsson
Note taker: Christian Schmidt
Jabber scribe: Gorry Fairhurst


Morning session, 09:00-11:30
----------------------------

* WG admonishments (Jonsson)

Meeting time will be used to advance difficult issues, not
for presentation of material that can be read from drafts. We
assume that people have read the drafts, and what we decide 
in meetings must be confirmed on the mailing list. Also, all
contributors must be aware of the IPR principles, as stated by
RFC 3668.


* Agenda bashing (Jonsson)

Lars-Erik presented the proposed agenda, which was accepted without
modifications.

Agenda:
 - Chair admonishments and agenda bashing   
 - WG and document status update
 - Signaling compression towards Draft Standard
 - ROHC TCP and Formal Notation
 - ROHC RTP towards Draft Standard
    + Various ways to go forward
    + ROHC implementer's guide 
    + RFC 3095 in Formal Notation
 - LLA ROHC RTP Implementer's guide
 - ROHC over channels that can reorder packets
 - ROHC over 802 networks


* WG and document status (Jonsson)

Lars-Erik reviewed WG goals, milestones and document status. The
WG has 13 published RFC's, but no new publications have been made
since San Diego. The UDP-Lite profiles draft has passed IANA and
is expected to be published within a month or two. Four drafts
have been submitted to the IESG, the SigComp NACK draft and three
drafts related to ROHC-TCP. In San Diego, we said that we were 
about to update the milestones, but we had hoped to get the TCP
profile completed and submitted first, which we have still not
managed to do. The milestone update is thus still pending.


* Signaling compression issues

 - Applying SigComp to SIP (Bormann)
 
Carsten gave a summary of the three open issues for SIP over
SigComp. SigComp defines a default state memory size of 0, while it
has been suggested to mandate more for SIP, as it has been observed
that stateless compression for SIP/SDP does not give much gain. The
current proposal is thus to have 2K per state compartment, and 
require NACK support for a compressor that wants to make use of the
state memory. There were no SIP implementers in the room that had
any comments on this proposal.

Second issue is about the definition of compartments, as they need
to be well-defined to avoid accidental push-outs. The original
proposal was to use SIP dialogs, but another idea is to have three
different compartments for; registration related messages (R),
dialog-related messages (D), and subscription-related messages (S).
Question is, can this be clearly defined, and is (nr*R+nd*D+ns*S) in
any way worse than (n*D)? No comments were received from the 
audience.

Third issue left is the question on "TCP step-up", i.e. whether it
should be possible to start SigComp compression in the middle of a
SIP TCP connection? In many architectures, this requires a SigComp
shim layer to add SIP parser, which is a non-desirable requirement.
The solution would thus be to open another TCP connection to start
SigComp.

There is a pressing need to make this document available to 3GPP in
an updated form, and Carsten promised to make sure an update will
be available by the middle of next week, at latest.

Draft: draft-ietf-rohc-sigcomp-sip-01.txt

 - SigComp towards Draft Standard (Bormann)
 
Interoperability test events for SigComp have been held at SIPit.
Now we need to collect interoperability test status and create a
matrix document with all "features" we can identify, and endure 
there are at least two independent interoperable implementations for 
every feature. After that, we are ready to bring SigComp, RFC 3320,
forward to Draft Standard. An ancillary document that might go with
this is of course the implementer's guide, but potentially also the
User Guide (draft-ietf-rohc-sigcomp-user-guide-00), as well as the
Torture Test Guide (draft-price-rohc-sigcomp-torture-tests-02),
which are both expired individual drafts, expected to provide useful
material for implementers. These two should thus be resurrected, if
we find people interested, as original author is not active in the
WG anymore. Mark West expressed potential interest in doing this,
and we should continue discussion on the list.
 
RFC: RFC 3320
Draft: draft-ietf-rohc-sigcomp-impl-guide-03.txt


* ROHC TCP & Formal Notation (Pelletier)

Three of our five drafts related to ROHC TCP, requirements, TCP
behavior, and Context Replication, have been submitted to the IESG.
However, the actual specification, consisting of the TCP profile
draft and the Formal Notation, are still not finalized, although we
are getting closer to completion. In latest update, packet formats
have been redefined based on an updated and simplified FN. We need
somewhat to start doing a thorough review of the packet formats 
themselves. In the FN, external coding methods (using underscore 
syntax) are gone and Profile Specific Encoding Methods are instead
defined. Further has the formal meaning of annotations been removed
and replaced by a note in the ROHC-TCP profile. The encoding methods
for crc's have also been combined into one general method with
arguments, and the environment of the let statement has been
clarified. There are now mainly two issues left, about the 
definition and use of control fields, and how to completely capture
list encoding in FN.

The problem with list compression as it currently stands is that if
one option is not present the entire list compression fails. Carsten
noted that there are many ways to solve this, and suggested to try
to keep the mechanisms simple. Ghyslain asked whether we should
simply use English language, as we do for header chaining, although
that is not formal notation. The concern with this approach is that
we seem to be removing many things from the FN just because we can
not manage to make it work, which makes the value of the FN clearly
questionable. Carsten suggested that we could make use of the 
recursion we have in the FN, which Ghyslain commented would not look
very good. Carsten agreed but thought it might be a fast way to get
to a resolution.

The control field concept currently used in the FN and TCP profile
has been questioned. Carsten means this goes against the core FN
principle of only defining packet formats and encoding between
uncompressed and compressed values, as control fields are rather 
functionality for interacting with the contexts. The alternative
approach suggested is to provide control field data to packet
formats as parameters. Others argued that control fields are very
similar to other fields, it is just that they do not appear in any
uncompressed header. Carsten went through an example with the two
different approaches, and the conclusion was that the current way
with control fields should be kept, but their meaning must be more
precisely defined. 

Ghyslain then talked about the way forward with ROHC-TCP. Work on
the FN has kept us away from the actual work on TCP compression, and
still do. WG resources are also at a minimal level to get any work
at all done. We should ask ourselves whether we really think we can
manage to get a workable FN-based solution, and how much time we can
spend before we start reconsidering Box Notation. Anyway, in any
case we still need 2 committed reviewers for each document. We hope
it is still possible to issue WGLC by the end of November. Carsten
raised a couple of issues that he believed might still lack complete
resolutions. Ghyslain answered that these should all be resolved by
the latest update, but encouraged review of the details.

Drafts: draft-ietf-rohc-tcp-08.txt
        draft-ietf-rohc-formal-notation-04.txt

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


From rohc-bounces@ietf.org  Fri Nov 12 15:58:20 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21618
	for <rohc-web-archive@ietf.org>; Fri, 12 Nov 2004 15:58:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSiWO-00057g-IF
	for rohc-web-archive@ietf.org; Fri, 12 Nov 2004 15:59:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSi0T-0004im-05; Fri, 12 Nov 2004 15:26:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CShhd-0007iu-9S; Fri, 12 Nov 2004 15:07:25 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08269;
	Fri, 12 Nov 2004 15:07:23 -0500 (EST)
Message-Id: <200411122007.PAA08269@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 12 Nov 2004 15:07:23 -0500
Cc: rohc@ietf.org
Subject: [rohc] I-D ACTION:draft-ietf-rohc-over-reordering-01.txt
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4

--NextPart

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

	Title		: RObust Header Compression (ROHC): ROHC over Channels that can Reorder Packets
	Author(s)	: G. Pelletier, et al.
	Filename	: draft-ietf-rohc-over-reordering-01.txt
	Pages		: 21
	Date		: 2004-11-12
	
RObust Header Compression (ROHC), RFC 3095, defines a framework for
   header compression, along with a number of compression protocols
   (profiles). One operating assumption for the profiles defined in RFC
   3095 is that the channel between compressor and decompressor is
   required to maintain packet ordering. This document discusses aspects
   of using ROHC over channels that can reorder packets. It provides
   guidelines on how to implement existing profiles over such channels,
   as well as suggestions for the design of new profiles.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-over-reordering-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-over-reordering-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: <2004-11-12134755.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rohc-over-reordering-01.txt

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

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


--OtherAccess--

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

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

--NextPart--





From rohc-bounces@ietf.org  Fri Nov 12 16:59:52 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05317
	for <rohc-web-archive@ietf.org>; Fri, 12 Nov 2004 16:59:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSjNf-0001ni-8h
	for rohc-web-archive@ietf.org; Fri, 12 Nov 2004 16:54:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSjKa-00083n-V5; Fri, 12 Nov 2004 16:51:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSjCo-0004Wx-Kk
	for rohc@megatron.ietf.org; Fri, 12 Nov 2004 16:43:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03730
	for <rohc@ietf.org>; Fri, 12 Nov 2004 16:43:39 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSjE1-00013y-Ny
	for rohc@ietf.org; Fri, 12 Nov 2004 16:45:01 -0500
Received: from esdks003.ntc.nokia.com (esdks003.ntc.nokia.com [172.21.138.158])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iACLhEv02966; Fri, 12 Nov 2004 23:43:14 +0200 (EET)
X-Scanned: Fri, 12 Nov 2004 23:43:10 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks003.ntc.nokia.com (8.12.9/8.12.9) id iACLhAIL022805;
	Fri, 12 Nov 2004 23:43:10 +0200
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks003.ntc.nokia.com 00TiDt6v; Fri, 12 Nov 2004 23:43:08 EET
Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com
	[10.241.35.122])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iACLh7S11955; Fri, 12 Nov 2004 23:43:08 +0200 (EET)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by
	daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Fri, 12 Nov 2004 15:43:05 -0600
content-class: urn:content-classes:message
Subject: RE: [rohc] Re: multiplexing SigComp and non-SigComp messages
	onthesame TCP connection
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Fri, 12 Nov 2004 16:43:03 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B8153A3C@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] Re: multiplexing SigComp and non-SigComp messages
	onthesame TCP connection
Thread-Index: AcR+X3EwpG11mHmgRkiPOJ7hbyZVhQGy6IyQBSjRVjALy37OwA==
To: <cabo@tzi.org>
X-OriginalArrivalTime: 12 Nov 2004 21:43:05.0983 (UTC)
	FILETIME=[97F538F0:01C4C900]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Content-Transfer-Encoding: quoted-printable
Cc: mark.a.west@roke.co.uk, Robert.Sugar@nokia.com, rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Content-Transfer-Encoding: quoted-printable

Hi Carsten,

I wasn't be able to attend the IETF-61 this week (couldn't=20
find ROHC session time in the IETF agenda before I left for
a long vacation in October).

I just saw your slides on applying SigComp to SIP and
the meeting minutes from Lars-Erik. I guess those are=20
based on the meeting you mentioned below during last IETF?=20

The minutes say you promised to make sure an update will=20
be available by the middle of next week. Does that mean
you will send some text with more details? It's good to=20
resume the progress after a long pause since the last IETF.

BR, Zhigang

> -----Original Message-----
> From: rohc-bounces@ietf.org [mailto:rohc-bounces@ietf.org]On Behalf Of
> ext zhigang.c.liu@nokia.com
> Sent: 13 September, 2004 03:16 PM
> To: cabo@tzi.org
> Cc: mark.a.west@roke.co.uk; Sugar Robert (Nokia-NET/Budapest);
> rohc@ietf.org
> Subject: RE: [rohc] Re: multiplexing SigComp and non-SigComp messages
> onthesame TCP connection
>=20
>=20
> Hi Carsten,
>=20
> Still wondering about the meeting summary ...
>=20
> BR, Zhigang
>=20
> > -----Original Message-----
> > From: rohc-bounces@ietf.org=20
> [mailto:rohc-bounces@ietf.org]On Behalf Of
> > ext zhigang.c.liu@nokia.com
> > Sent: 18 August, 2004 08:59 AM
> > To: cabo@tzi.org
> > Cc: mark.a.west@roke.co.uk; Sugar Robert (Nokia-NET/Budapest);
> > rohc@ietf.org
> > Subject: RE: [rohc] Re: multiplexing SigComp and non-SigComp=20
> > messages on
> > thesame TCP connection
> >=20
> >=20
> > Carsten,
> >=20
> > Just a gentle reminder: did you have a chance writing up=20
> the summary?
> >=20
> > Br, Zhigang
> >=20
> > > -----Original Message-----
> > > From: ext Carsten Bormann [mailto:cabo@tzi.org]
> > > Sent: 09 August, 2004 05:22 PM
> > > To: Liu Zhigang.C (Nokia-NRC/Dallas)
> > > Cc: rohc@ietf.org; Sugar Robert (Nokia-NET/Budapest);=20
> > Carsten Bormann;
> > > mark.a.west@roke.co.uk
> > > Subject: Re: [rohc] Re: multiplexing SigComp and non-SigComp=20
> > > messages on
> > > the same TCP connection
> > >=20
> > >=20
> > > Zhigang,
> > >=20
> > > after you had to leave, we managed to schedule an=20
> extended hallway=20
> > > discussion with some SIP types in San Diego about this and other=20
> > > sigcomp-sip issues.
> > > The conclusions are somewhat different.
> > > I expect to write this up in the next couple of days.
> > > Please defer editing and re-submitting the draft until I=20
> have made=20
> > > available the summary.
> > > Thanks!
> > >=20
> > > Gruesse, Carsten
> > >=20
> > >=20
> >=20
> > _______________________________________________
> > Rohc mailing list
> > Rohc@ietf.org
> > https://www1.ietf.org/mailman/listinfo/rohc
> >=20
>=20
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
>=20

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


From rohc-bounces@ietf.org  Fri Nov 12 20:02:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17419
	for <rohc-web-archive@ietf.org>; Fri, 12 Nov 2004 20:02:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CSmL7-0002Fe-JJ
	for rohc-web-archive@ietf.org; Fri, 12 Nov 2004 20:04:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSmI4-00061R-HC; Fri, 12 Nov 2004 20:01:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSmG7-000559-I3
	for rohc@megatron.ietf.org; Fri, 12 Nov 2004 19:59:19 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17164
	for <rohc@ietf.org>; Fri, 12 Nov 2004 19:59:17 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSmHb-000255-0K
	for rohc@ietf.org; Fri, 12 Nov 2004 20:00:51 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0F1TRF>; Sat, 13 Nov 2004 01:00:02 -0000
Received: from [127.0.0.1] (orion.roke.co.uk [193.118.192.66]) by
	rsys002a.roke.co.uk with SMTP (Microsoft Exchange Internet Mail
	Service Version 5.5.2657.72)
	id V2Q3RV27; Sat, 13 Nov 2004 01:00:05 -0000
From: "Conroy, Lawrence (SMTP)" <lwc@roke.co.uk>
To: zhigang.c.liu@nokia.com
In-Reply-To: <7B5AF06E216CB74DA8A5960A3181B5B8153A3C@ajebe001.americas.nokia.com>
References: <7B5AF06E216CB74DA8A5960A3181B5B8153A3C@ajebe001.americas.nokia.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <27184AC8-350F-11D9-B6CD-000393A70BB2@roke.co.uk>
Content-Transfer-Encoding: 7bit
Subject: Re: [rohc] Re: multiplexing SigComp and non-SigComp messages on the
	same TCP connection
Date: Sat, 13 Nov 2004 00:58:38 +0000
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Content-Transfer-Encoding: 7bit
Cc: "West, Mark" <mark.a.west@roke.co.uk>, Robert.Sugar@nokia.com,
        cabo@tzi.org, rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Content-Transfer-Encoding: 7bit

Hi Folks,
  Speaking as an outsider (who has not spent the last month on Holiday:<
I hadn't noticed a pause since the last IETF.
Much thought has gone on at our end, and I know there has been
a lot of consideration of this elsewhere as well.
However, I fear now we may be back to progress again.

all the best,
   Lawrence

On 12 Nov 2004, at 21:43, zhigang.c.liu@nokia.com wrote:
> Hi Carsten,
>
> I wasn't be able to attend the IETF-61 this week (couldn't
> find ROHC session time in the IETF agenda before I left for
> a long vacation in October).
>
> I just saw your slides on applying SigComp to SIP and
> the meeting minutes from Lars-Erik. I guess those are
> based on the meeting you mentioned below during last IETF?
>
> The minutes say you promised to make sure an update will
> be available by the middle of next week. Does that mean
> you will send some text with more details? It's good to
> resume the progress after a long pause since the last IETF.
>
> BR, Zhigang
>
>> -----Original Message-----
>> From: rohc-bounces@ietf.org [mailto:rohc-bounces@ietf.org]On Behalf Of
>> ext zhigang.c.liu@nokia.com
>> Sent: 13 September, 2004 03:16 PM
>> To: cabo@tzi.org
>> Cc: mark.a.west@roke.co.uk; Sugar Robert (Nokia-NET/Budapest);
>> rohc@ietf.org
>> Subject: RE: [rohc] Re: multiplexing SigComp and non-SigComp messages
>> onthesame TCP connection
>>
>>
>> Hi Carsten,
>>
>> Still wondering about the meeting summary ...
>>
>> BR, Zhigang
>>
>>> -----Original Message-----
>>> From: rohc-bounces@ietf.org
>> [mailto:rohc-bounces@ietf.org]On Behalf Of
>>> ext zhigang.c.liu@nokia.com
>>> Sent: 18 August, 2004 08:59 AM
>>> To: cabo@tzi.org
>>> Cc: mark.a.west@roke.co.uk; Sugar Robert (Nokia-NET/Budapest);
>>> rohc@ietf.org
>>> Subject: RE: [rohc] Re: multiplexing SigComp and non-SigComp
>>> messages on
>>> thesame TCP connection
>>>
>>>
>>> Carsten,
>>>
>>> Just a gentle reminder: did you have a chance writing up
>> the summary?
>>>
>>> Br, Zhigang
>>>
>>>> -----Original Message-----
>>>> From: ext Carsten Bormann [mailto:cabo@tzi.org]
>>>> Sent: 09 August, 2004 05:22 PM
>>>> To: Liu Zhigang.C (Nokia-NRC/Dallas)
>>>> Cc: rohc@ietf.org; Sugar Robert (Nokia-NET/Budapest);
>>> Carsten Bormann;
>>>> mark.a.west@roke.co.uk
>>>> Subject: Re: [rohc] Re: multiplexing SigComp and non-SigComp
>>>> messages on
>>>> the same TCP connection
>>>>
>>>>
>>>> Zhigang,
>>>>
>>>> after you had to leave, we managed to schedule an
>> extended hallway
>>>> discussion with some SIP types in San Diego about this and other
>>>> sigcomp-sip issues.
>>>> The conclusions are somewhat different.
>>>> I expect to write this up in the next couple of days.
>>>> Please defer editing and re-submitting the draft until I
>> have made
>>>> available the summary.
>>>> Thanks!
>>>>
>>>> Gruesse, Carsten
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Rohc mailing list
>>> Rohc@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/rohc
>>>
>>
>> _______________________________________________
>> Rohc mailing list
>> Rohc@ietf.org
>> https://www1.ietf.org/mailman/listinfo/rohc
>>
>
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
>

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


From rohc-bounces@ietf.org  Mon Nov 15 11:03:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05107
	for <rohc-web-archive@ietf.org>; Mon, 15 Nov 2004 11:03:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CTjMA-0001Vt-NC
	for rohc-web-archive@ietf.org; Mon, 15 Nov 2004 11:05:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CTjIz-0000d6-KA; Mon, 15 Nov 2004 11:02:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CTjIR-0000YY-1Y
	for rohc@megatron.ietf.org; Mon, 15 Nov 2004 11:01:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05020
	for <rohc@ietf.org>; Mon, 15 Nov 2004 11:01:36 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTjKS-0001Ti-EF
	for rohc@ietf.org; Mon, 15 Nov 2004 11:03:44 -0500
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAFG1QW08727; Mon, 15 Nov 2004 18:01:27 +0200 (EET)
X-Scanned: Mon, 15 Nov 2004 18:01:13 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id iAFG1Dfq008762;
	Mon, 15 Nov 2004 18:01:13 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks002.ntc.nokia.com 00MfqCVA; Mon, 15 Nov 2004 18:01:11 EET
Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com
	[10.241.35.122])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAFG18a28177; Mon, 15 Nov 2004 18:01:09 +0200 (EET)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by
	daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Mon, 15 Nov 2004 10:00:18 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] Re: multiplexing SigComp and non-SigComp messages on the
	same TCP connection
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Mon, 15 Nov 2004 11:00:06 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B8153A3F@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] Re: multiplexing SigComp and non-SigComp messages on the
	same TCP connection
Thread-Index: AcTJHAmwfFmD/4apS6KjiLLMJa0chwCDu2gA
To: <lwc@roke.co.uk>
X-OriginalArrivalTime: 15 Nov 2004 16:00:18.0730 (UTC)
	FILETIME=[3428B8A0:01C4CB2C]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f
Content-Transfer-Encoding: quoted-printable
Cc: mark.a.west@roke.co.uk, Robert.Sugar@nokia.com, cabo@tzi.org,
        rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: d16ce744298aacf98517bc7c108bd198
Content-Transfer-Encoding: quoted-printable

That's good. Please share your thoughts. I have been placed into
a waiting mode on sigcomp-sip since IETF-60. That's what I meant
a pause, at least from my perspective.

Br, Zhigang


> -----Original Message-----
> From: ext Conroy, Lawrence (SMTP) [mailto:lwc@roke.co.uk]
> Sent: 12 November, 2004 06:59 PM
> To: Liu Zhigang.C (Nokia-NRC/Dallas)
> Cc: Sugar Robert (Nokia-NET/Budapest); cabo@tzi.org; West, Mark;
> rohc@ietf.org
> Subject: Re: [rohc] Re: multiplexing SigComp and non-SigComp=20
> messages on
> the same TCP connection
>=20
>=20
> Hi Folks,
>   Speaking as an outsider (who has not spent the last month=20
> on Holiday:<
> I hadn't noticed a pause since the last IETF.
> Much thought has gone on at our end, and I know there has been
> a lot of consideration of this elsewhere as well.
> However, I fear now we may be back to progress again.
>=20
> all the best,
>    Lawrence
>=20
> On 12 Nov 2004, at 21:43, zhigang.c.liu@nokia.com wrote:
> > Hi Carsten,
> >
> > I wasn't be able to attend the IETF-61 this week (couldn't
> > find ROHC session time in the IETF agenda before I left for
> > a long vacation in October).
> >
> > I just saw your slides on applying SigComp to SIP and
> > the meeting minutes from Lars-Erik. I guess those are
> > based on the meeting you mentioned below during last IETF?
> >
> > The minutes say you promised to make sure an update will
> > be available by the middle of next week. Does that mean
> > you will send some text with more details? It's good to
> > resume the progress after a long pause since the last IETF.
> >
> > BR, Zhigang
> >
> >> -----Original Message-----
> >> From: rohc-bounces@ietf.org=20
> [mailto:rohc-bounces@ietf.org]On Behalf Of
> >> ext zhigang.c.liu@nokia.com
> >> Sent: 13 September, 2004 03:16 PM
> >> To: cabo@tzi.org
> >> Cc: mark.a.west@roke.co.uk; Sugar Robert (Nokia-NET/Budapest);
> >> rohc@ietf.org
> >> Subject: RE: [rohc] Re: multiplexing SigComp and=20
> non-SigComp messages
> >> onthesame TCP connection
> >>
> >>
> >> Hi Carsten,
> >>
> >> Still wondering about the meeting summary ...
> >>
> >> BR, Zhigang
> >>
> >>> -----Original Message-----
> >>> From: rohc-bounces@ietf.org
> >> [mailto:rohc-bounces@ietf.org]On Behalf Of
> >>> ext zhigang.c.liu@nokia.com
> >>> Sent: 18 August, 2004 08:59 AM
> >>> To: cabo@tzi.org
> >>> Cc: mark.a.west@roke.co.uk; Sugar Robert (Nokia-NET/Budapest);
> >>> rohc@ietf.org
> >>> Subject: RE: [rohc] Re: multiplexing SigComp and non-SigComp
> >>> messages on
> >>> thesame TCP connection
> >>>
> >>>
> >>> Carsten,
> >>>
> >>> Just a gentle reminder: did you have a chance writing up
> >> the summary?
> >>>
> >>> Br, Zhigang
> >>>
> >>>> -----Original Message-----
> >>>> From: ext Carsten Bormann [mailto:cabo@tzi.org]
> >>>> Sent: 09 August, 2004 05:22 PM
> >>>> To: Liu Zhigang.C (Nokia-NRC/Dallas)
> >>>> Cc: rohc@ietf.org; Sugar Robert (Nokia-NET/Budapest);
> >>> Carsten Bormann;
> >>>> mark.a.west@roke.co.uk
> >>>> Subject: Re: [rohc] Re: multiplexing SigComp and non-SigComp
> >>>> messages on
> >>>> the same TCP connection
> >>>>
> >>>>
> >>>> Zhigang,
> >>>>
> >>>> after you had to leave, we managed to schedule an
> >> extended hallway
> >>>> discussion with some SIP types in San Diego about this and other
> >>>> sigcomp-sip issues.
> >>>> The conclusions are somewhat different.
> >>>> I expect to write this up in the next couple of days.
> >>>> Please defer editing and re-submitting the draft until I
> >> have made
> >>>> available the summary.
> >>>> Thanks!
> >>>>
> >>>> Gruesse, Carsten
> >>>>
> >>>>
> >>>
> >>> _______________________________________________
> >>> Rohc mailing list
> >>> Rohc@ietf.org
> >>> https://www1.ietf.org/mailman/listinfo/rohc
> >>>
> >>
> >> _______________________________________________
> >> Rohc mailing list
> >> Rohc@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/rohc
> >>
> >
> > _______________________________________________
> > Rohc mailing list
> > Rohc@ietf.org
> > https://www1.ietf.org/mailman/listinfo/rohc
> >
>=20
> --=20
>=20
> Visit our website at www.roke.co.uk
>=20
> Roke Manor Research Ltd, Roke Manor, Romsey, Hampshire SO51 0ZN, UK.
>=20
> The information contained in this e-mail and any attachments=20
> is confidential to
> Roke Manor Research Ltd and must not be passed to any third=20
> party without
> permission. This communication is for information only and=20
> shall not create or
> change any contractual relationship.
>=20
>=20

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


From rohc-bounces@ietf.org  Mon Nov 15 11:30:03 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07684
	for <rohc-web-archive@ietf.org>; Mon, 15 Nov 2004 11:30:03 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CTjlp-00025S-9D
	for rohc-web-archive@ietf.org; Mon, 15 Nov 2004 11:32:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CTjiV-0004Ee-6x; Mon, 15 Nov 2004 11:28:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CTjgV-00043G-JX
	for rohc@megatron.ietf.org; Mon, 15 Nov 2004 11:26:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07275
	for <rohc@ietf.org>; Mon, 15 Nov 2004 11:26:29 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTjiW-00020n-Ne
	for rohc@ietf.org; Mon, 15 Nov 2004 11:28:37 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAFGQTvD012946
	for <rohc@ietf.org>; Mon, 15 Nov 2004 17:26:29 +0100 (MET)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 15 Nov 2004 17:26:27 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <WRVWPRLP>; Mon, 15 Nov 2004 17:26:27 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E9903@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Mon, 15 Nov 2004 17:26:21 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="ISO-8859-1"
X-OriginalArrivalTime: 15 Nov 2004 16:26:27.0641 (UTC)
	FILETIME=[DB4D8A90:01C4CB2F]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by albatross.ericsson.se
	id iAFGQTvD012946
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 07e9b4af03a165a413ec6e4d37ae537b
Content-Transfer-Encoding: quoted-printable
Subject: [rohc] Preliminary minutes from ROHC@IETF61
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 55503977758b6a5197d8a2b5141eae86
Content-Transfer-Encoding: quoted-printable

Minutes of the ROHC WG session at IETF 61
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Hilton Washington, Washington DC, USA
Monday Morning, 2004-11-08

Chairs: Carsten Bormann & Lars-Erik Jonsson

Reported by: Lars-Erik Jonsson
Note taker: Christian Schmidt
Jabber scribe: Gorry Fairhurst


Morning session, 09:00-11:30
----------------------------

* WG admonishments (Jonsson)

Meeting time will be used to advance difficult issues, not
for presentation of material that can be read from drafts. We
assume that people have read the drafts, and what we decide=20
in meetings must be confirmed on the mailing list. Also, all
contributors must be aware of the IPR principles, as stated by
RFC 3668.


* Agenda bashing (Jonsson)

Lars-Erik presented the proposed agenda, which was accepted without
modifications.

Agenda:
 - Chair admonishments and agenda bashing  =20
 - WG and document status update
 - Signaling compression towards Draft Standard
 - ROHC TCP and Formal Notation
 - ROHC RTP towards Draft Standard
    + Various ways to go forward
    + ROHC implementer's guide=20
    + RFC 3095 in Formal Notation
 - LLA ROHC RTP Implementer's guide
 - ROHC over channels that can reorder packets
 - ROHC over 802 networks


* WG and document status (Jonsson)

Lars-Erik reviewed WG goals, milestones and document status. The
WG has 13 published RFC's, but no new publications have been made
since San Diego. The UDP-Lite profiles draft has passed IANA and
is expected to be published within a month or two. Four drafts
have been submitted to the IESG, the SigComp NACK draft and three
drafts related to ROHC-TCP. In San Diego, we said that we were=20
about to update the milestones, but we had hoped to get the TCP
profile completed and submitted first, which we have still not
managed to do. The milestone update is thus still pending.


* Signaling compression issues

 - Applying SigComp to SIP (Bormann)
=20
Carsten gave a summary of the three open issues for SIP over
SigComp. SigComp defines a default state memory size of 0, while it
has been suggested to mandate more for SIP, as it has been observed
that stateless compression for SIP/SDP does not give much gain. The
current proposal is thus to have 2K per state compartment, and=20
require NACK support for a compressor that wants to make use of the
state memory. There were no SIP implementers in the room that had
any comments on this proposal.

Second issue is about the definition of compartments, as they need
to be well-defined to avoid accidental push-outs. The original
proposal was to use SIP dialogs, but another idea is to have three
different compartments for; registration related messages (R),
dialog-related messages (D), and subscription-related messages (S).
Question is, can this be clearly defined, and is (nr*R+nd*D+ns*S) in
any way worse than (n*D)? No comments were received from the=20
audience.

Third issue left is the question on "TCP step-up", i.e. whether it
should be possible to start SigComp compression in the middle of a
SIP TCP connection? In many architectures, this requires a SigComp
shim layer to add SIP parser, which is a non-desirable requirement.
The solution would thus be to open another TCP connection to start
SigComp.

There is a pressing need to make this document available to 3GPP in
an updated form, and Carsten promised to make sure an update will
be available by the middle of next week, at latest.

Draft: draft-ietf-rohc-sigcomp-sip-01.txt

 - SigComp towards Draft Standard (Bormann)
=20
Interoperability test events for SigComp have been held at SIPit.
Now we need to collect interoperability test status and create a
matrix document with all "features" we can identify, and endure=20
there are at least two independent interoperable implementations for=20
every feature. After that, we are ready to bring SigComp, RFC 3320,
forward to Draft Standard. An ancillary document that might go with
this is of course the implementer's guide, but potentially also the
User Guide (draft-ietf-rohc-sigcomp-user-guide-00), as well as the
Torture Test Guide (draft-price-rohc-sigcomp-torture-tests-02),
which are both expired individual drafts, expected to provide useful
material for implementers. These two should thus be resurrected, if
we find people interested, as original author is not active in the
WG anymore. Mark West expressed potential interest in doing this,
and we should continue discussion on the list.
=20
RFC: RFC 3320
Draft: draft-ietf-rohc-sigcomp-impl-guide-03.txt


* ROHC TCP & Formal Notation (Pelletier)

Three of our five drafts related to ROHC TCP, requirements, TCP
behavior, and Context Replication, have been submitted to the IESG.
However, the actual specification, consisting of the TCP profile
draft and the Formal Notation, are still not finalized, although we
are getting closer to completion. In latest update, packet formats
have been redefined based on an updated and simplified FN. We need
somewhat to start doing a thorough review of the packet formats=20
themselves. In the FN, external coding methods (using underscore=20
syntax) are gone and Profile Specific Encoding Methods are instead
defined. Further has the formal meaning of annotations been removed
and replaced by a note in the ROHC-TCP profile. The encoding methods
for crc's have also been combined into one general method with
arguments, and the environment of the let statement has been
clarified. There are now mainly two issues left, about the=20
definition and use of control fields, and how to completely capture
list encoding in FN.

The problem with list compression as it currently stands is that if
one option is not present the entire list compression fails. Carsten
noted that there are many ways to solve this, and suggested to try
to keep the mechanisms simple. Ghyslain asked whether we should
simply use English language, as we do for header chaining, although
that is not formal notation. The concern with this approach is that
we seem to be removing many things from the FN just because we can
not manage to make it work, which makes the value of the FN clearly
questionable. Carsten suggested that we could make use of the=20
recursion we have in the FN, which Ghyslain commented would not look
very good. Carsten agreed but thought it might be a fast way to get
to a resolution.

The control field concept currently used in the FN and TCP profile
has been questioned. Carsten means this goes against the core FN
principle of only defining packet formats and encoding between
uncompressed and compressed values, as control fields are rather=20
functionality for interacting with the contexts. The alternative
approach suggested is to provide control field data to packet
formats as parameters. Others argued that control fields are very
similar to other fields, it is just that they do not appear in any
uncompressed header. Carsten went through an example with the two
different approaches, and the conclusion was that the current way
with control fields should be kept, but their meaning must be more
precisely defined.=20

Ghyslain then talked about the way forward with ROHC-TCP. Work on
the FN has kept us away from the actual work on TCP compression, and
still do. WG resources are also at a minimal level to get any work
at all done. We should ask ourselves whether we really think we can
manage to get a workable FN-based solution, and how much time we can
spend before we start reconsidering Box Notation. Anyway, in any
case we still need 2 committed reviewers for each document. We hope
it is still possible to issue WGLC by the end of November. Carsten
raised a couple of issues that he believed might still lack complete
resolutions. Ghyslain answered that these should all be resolved by
the latest update, but encouraged review of the details.

Drafts: draft-ietf-rohc-tcp-08.txt
        draft-ietf-rohc-formal-notation-04.txt


* ROHC RTP towards Draft Standard

 - Introduction (Jonsson)
=20
Lars-Erik gave an overview of the various approaches available for
taking RFC 3095 further to Draft Standard. At an early point we saw
that it would be a good idea to split the current document into two
separate parts, framework and profiles, and this was thus our
original plan. However, during implementation we have identified a
number of more or less complicated ambiguities, which so far have
been documented in the implementer's guide. These issues will have
to be incorporated when going through the update process for 3095,
and it is then not clear whether we can go directly to DS, as the
changes might be seen as non-trivial. We also know that implementers
have expressed real concerns about the complexity of RFC 3095, and=20
we know by now that if we had done it today we would simplify things
significantly. When discussing the way forward with 3095, another
potential option is to actually redefine the 3095 profiles based on
our experience and standardise simplified profiles, which will then
be given new profile numbers. If we go this path, there are several
aspects to consider. Will we be able to go to DS with these new
profiles? What happens with the current profiles, which are used by
other bodies like 3GPP. With this approach, we will actually produce
a new standard set that is not interoperable with the current one.=20
Carsten noted that if we only use existing solutions from 3095, i.e.
stick to simplifications, we should be able to get to DS as we will
have tested interoperability for all features. There was a comment=20
from the audience that the 3GPP reference to 3095 would not be a
problem as 3095 will stay as it is. Lars-Erik noted that 3095 do has
errors, which means we should ensure we provide error-fix documents
for 3095. It was suggested that could be done as an appendix to the
new profiles, but after discussion it was agreed it would make more
sense to keep that as a separate document. Lars-Erik concluded that
the sense of the room was to focus our effort on getting things
right and say this is what goes to DS, instead of spending resources
on fixing the old stuff. Someone in the audience asked for examples
of what can be simplified. Examples mentioned were list compression,
some other rather complex packet type combinations, and other=20
redundancy in functionality that only gives minimal compression=20
gains. The concept of modes could potentially also be simplified.
Many of these simplified solutions are currently being used for the
TCP profile, which means we have a rather good knowledge of both=20
what should be made simpler and how it can be achieved.

RFC: RFC 3095
Drafts: draft-ietf-rohc-rtp-rfc3095-interoperability-03.txt

 - Implementer's Guide (Jonsson)

The implementer's guide has been updated three times since the last
IETF. A new chapter 7 has been added on Context management and CID
re-use, as discussed and agreed on the mail list. A new section 8.12
on ack usage in O-mode has also been added as a response to=20
questions from implementers, based on the outcome of the discussions
that followed from that question.=20

There is still no conclusion on the question about the potential use
of an implicit slope to compress and decompress timestamps. This is
an important issue that must be resolved to ensure interoperability.
Ghyslain noted that RFC 3095 does not define the concept of slopes,
one has to really over-interpret the document to get to this. Carsten
asked whether anyone believes we have enough material in 3095 to
even get slopes working, and expressed some doubts. Ghyslain asked
for more chair support in this discussion, as we should ask the list
to prove both that the slope concept exists in 3094, that it in=20
needed, and that it works. We could of course spend significant
efforts on writing a document to summarize all aspects of slope
versus non-slope operation, but Ghyslain suggested we might not have
to do that if chairs get more involved in the discussion.

Draft: draft-ietf-rohc-rtp-impl-guide-08.txt

 - RFC 3095 in Formal Notation (Bormann)
=20
Carsten gave a quick presentation on an ongoing work he is doing on
defining packet formats for the profiles in RFC 3095 with formal
notation. The goal is to get semantic checker for ROHC-FN to find
typos, inconsistencies, and missing pieces, as well having a more
formalized and consistent way of defining packet formats. Ghyslain
commented that although this effort is good, it has a tendency to
take focus away from the actual work, and so far formal notation has
mainly made the work harder. Carsten responded that 3095 took a lot
of work to complete too, and box notation is not always very
accessible either. Existing implementers are comfortable with box
notation, but new and simpler profiles could attract new
implementers. This is work that is currently done outside of the
ROHC WG, we will consider it when there is more results to look at.
=20
Draft: draft-brinkmann-rohc-3095-fn-00.txt
=20

* LLA ROHC RTP Implementer's guide (Sandlund)

During implementation, a bug was identified in RFC 3242 that makes
the CSP packet interoperable. The ROHC CRC is calculated over the
whole uncompressed packet, including length fields, which are=20
normally inferred from the packet length. However, with CSP the
payload is dropped and the packet length can therefore not be
inferred anymore. Through discussions on the mail list, it was
agreed to add a two-octet payload length field to the CSP, as the
overhead should not be a problem, considering the expected use of
the CSP. This has been described in the new LLA implementer's guide,
along with a clarification that CCP verification needs inferred=20
length fields to be stored in context. One additional clarification
should be added in an updated version, correcting a confusing cross-
reference to RFC 3095, which might be interpreted to include more
than was actually intended.

Carsten  asked about the implementation status of LLA, and Kristofer
answered that he has a complete implementation, but he is not aware
of any other implementations.=20

Allison Mankin pointed out that this does looks more like a bug fix
than an implementer's guide, and should be published with a proper
label. Chairs will discuss the further handling of this with Allison.=20

Draft: draft-ietf-rohc-rtp-lla-impl-guide-00.txt


* ROHC over channels that can reorder packets (Pelletier)

Ghyslain just wanted to remind people of the existence and purpose
of this document. The goal at this point is to produce an
Informational document, not to update any standard. If we want to do
some actual standardization work later on, we will be able to use=20
this document as a reference and problem analysis. We know now that
ROHC has good potential to be used also if reordering can happen,
although there are a number of issues to consider. Carsten asked
about how ECRTP differs in its ability to handle reordering.=20
Ghyslain answered that the situation is similar for ROHC and ECRTP.
ECRTP can handle some reordering if properly implemented, but there
is nothing in the standard that explains how to do that, and the
compression efficiency will be significantly affected. There is a
master theses to be published at Lule=E5 University on the subject of
ECRTP over reordering channels. Allison reminded people of the
ongoing work on header compression over MPLS, where they are meant
to look at both ROHC and ECRTP. Lars-Erik asked about the status of
that work, and where it is supposed to be carried out. Allison said
it is mainly an AVT activity, with some MPLS involvement. The
requirements are done, and now it is time to start working on
solutions, based on existing IETF solutions. Someone in the audience
asked whether ROHC would be a possible candidate, and Allison=20
responded she believed that would be a reasonable assumption. It
could be a good idea to write up a similar document as the ROHC over
reordering analysis also for ECRTP, making it easier to compare the
two and go further. Allison said she will feedback this to AVT, and
she also encouraged people from ROHC to take part in the AVT work on
header compression.

Draft: draft-ietf-rohc-over-reordering-00.txt
 =20
=20
* ROHC over 802 networks (Bormann)

Carsten Bormann gave an overview of his individual draft submission
on ROHC over 802 networks. We have seen interest in this before, and
now there are several new forms of 802 networks that could make use
of header compression. In general, being able to do ROHC over any
link technology requires two things to be defined, encapsulation and
negotiation. Carsten claimed that although it is not obvious how to
do negotiation, the challenge is to find a proper encapsulation=20
solution, as that is the key both to ensure one can get any gain at
all from header compression, as well as to make the solution=20
deployable. A proper encapsulation should provide length information
and try to minimize overhead, and most encapsulations that exist
fail at least when it comes to overhead. In most of these systems,=20
there is a little bit over Ethernet, requiring a minimal packet
length of 46 bytes of payload. Considering that we would like to
compress over a chain of bridged links where the bridges are not
aware of compression, we must find a way to get the bridges not to
insert padding, and encapsulation must be robust to padding. To get
length information into the packets, Carsten suggest to use 802.2
LLC, with "Length field" instead of "Ethertype". Demultiplexing must
then be handled in the payload, with an SSAP/DSAP identifier. Gorry
noticed that IEEE claims to control these identifiers. Ghyslain asked
whether this work really belongs in ROHC, which Carsten agreed is a
very good question to ask ourselves. Gabriel Montenegro recommended
interested ROHCers to come to the "IP over low-power WPAN" BOF.

The draft currently focuses on the encapsulation part of the problem,
but will of course have to address also negotiation if we manage to
get a proper encapsulation defined. We also have to consider
multicast and broadcast scenarios, where negotiation could be made
in form of announcements and/or pre-configuration. Gorry asked how=20
ROHC itself would work in such scenarios, and Carsten responded that
we already have the U-mode operation.

Draft: draft-bormann-rohc-over-802-00.txt

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


From rohc-bounces@ietf.org  Tue Nov 16 09:36:18 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02689
	for <rohc-web-archive@ietf.org>; Tue, 16 Nov 2004 09:36:18 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CU4Td-0006ko-Rl
	for rohc-web-archive@ietf.org; Tue, 16 Nov 2004 09:38:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CU4JU-0003hS-V2; Tue, 16 Nov 2004 09:28:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CU4F6-0002uY-90
	for rohc@megatron.ietf.org; Tue, 16 Nov 2004 09:23:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02009
	for <rohc@ietf.org>; Tue, 16 Nov 2004 09:23:35 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU4HJ-0006X7-MS
	for rohc@ietf.org; Tue, 16 Nov 2004 09:25:54 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FFWM6>; Tue, 16 Nov 2004 14:24:22 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8803D5974@rsys004a.roke.co.uk>
From: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
To: "'Lars-Erik Jonsson (LU/EAB)'" <lars-erik.jonsson@ericsson.com>,
        "'rohc@ietf.org'" <rohc@ietf.org>
Subject: RE: [rohc] Preliminary minutes from ROHC@IETF61
Date: Tue, 16 Nov 2004 14:24:27 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: "West, Mark" <mark.a.west@roke.co.uk>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69

Hi All,

As Mark said at the meeting, we are interested in resurrecting these drafts.

Should the torture tests draft remain an individual submission or should it
become a working group draft?

Any comments on the old versions (URLs below) and additional contributions
(particularly of missing torture tests) are welcome.

The drafts are available from:

http://sigcomp.srmr.co.uk/~ahs/draft-price-rohc-sigcomp-torture-tests-02.txt
http://sigcomp.srmr.co.uk/~ahs/draft-ietf-rohc-sigcomp-user-guide-00.txt

Best regards,

Abbie

>  - SigComp towards Draft Standard (Bormann)
>  
> Interoperability test events for SigComp have been held at SIPit.
> Now we need to collect interoperability test status and create a
> matrix document with all "features" we can identify, and endure 
> there are at least two independent interoperable implementations for 
> every feature. After that, we are ready to bring SigComp, RFC 3320,
> forward to Draft Standard. An ancillary document that might go with
> this is of course the implementer's guide, but potentially also the
> User Guide (draft-ietf-rohc-sigcomp-user-guide-00), as well as the
> Torture Test Guide (draft-price-rohc-sigcomp-torture-tests-02),
> which are both expired individual drafts, expected to provide useful
> material for implementers. These two should thus be resurrected, if
> we find people interested, as original author is not active in the
> WG anymore. Mark West expressed potential interest in doing this,
> and we should continue discussion on the list.
>  
> RFC: RFC 3320
> Draft: draft-ietf-rohc-sigcomp-impl-guide-03.txt
> 
> 

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


From rohc-bounces@ietf.org  Tue Nov 16 09:39:41 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02997
	for <rohc-web-archive@ietf.org>; Tue, 16 Nov 2004 09:39:41 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CU4Wj-0006qQ-VS
	for rohc-web-archive@ietf.org; Tue, 16 Nov 2004 09:42:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CU4KI-0003vo-FM; Tue, 16 Nov 2004 09:28:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CU4GV-000335-QO
	for rohc@megatron.ietf.org; Tue, 16 Nov 2004 09:25:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02075
	for <rohc@ietf.org>; Tue, 16 Nov 2004 09:25:02 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU4IY-0006ZH-41
	for rohc@ietf.org; Tue, 16 Nov 2004 09:27:21 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAGEOoR2015426 for <rohc@ietf.org>; Tue, 16 Nov 2004 15:24:50 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 16 Nov 2004 15:24:49 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <WRVWXTMP>; Tue, 16 Nov 2004 15:24:49 +0100
Message-ID: <A943FD84BD9ED41193460008C79180500C57062A@ESEALNT419.al.sw.ericsson.se>
From: "Ghyslain Pelletier (LU/EAB)" <ghyslain.pelletier@ericsson.com>
To: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>,
        "'rohc@ietf.org'" <rohc@ietf.org>
Subject: RE: [rohc] Preliminary minutes from ROHC@IETF61
Date: Tue, 16 Nov 2004 15:24:49 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="ISO-8859-1"
X-OriginalArrivalTime: 16 Nov 2004 14:24:49.0932 (UTC)
	FILETIME=[07F144C0:01C4CBE8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464

I found the following rather striking/amusing...

Bug = bad, Interoperable = good => Bug = interoperable!!! ; )

> * LLA ROHC RTP Implementer's guide (Sandlund)
>
> During implementation, a bug was identified in RFC 3242 that
> makes the CSP packet interoperable.

s/interoperable/non-interoperable/

/Ghyslain

> -----Original Message-----
> From: rohc-bounces@ietf.org [mailto:rohc-bounces@ietf.org]On Behalf Of
> Lars-Erik Jonsson (LU/EAB)
> Sent: den 15 november 2004 17:26
> To: 'rohc@ietf.org'
> Subject: [rohc] Preliminary minutes from ROHC@IETF61
> 
> 
> Minutes of the ROHC WG session at IETF 61
> =========================================
> 
> Hilton Washington, Washington DC, USA
> Monday Morning, 2004-11-08
> 

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


From rohc-bounces@ietf.org  Tue Nov 16 09:40:28 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03074
	for <rohc-web-archive@ietf.org>; Tue, 16 Nov 2004 09:40:28 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CU4XV-0006rS-CC
	for rohc-web-archive@ietf.org; Tue, 16 Nov 2004 09:42:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CU4KK-0003wh-Oc; Tue, 16 Nov 2004 09:29:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CU4HC-00036C-E9
	for rohc@megatron.ietf.org; Tue, 16 Nov 2004 09:25:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02112
	for <rohc@ietf.org>; Tue, 16 Nov 2004 09:25:45 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU4JF-0006Zt-PM
	for rohc@ietf.org; Tue, 16 Nov 2004 09:28:04 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAGEPYR2015733 for <rohc@ietf.org>; Tue, 16 Nov 2004 15:25:34 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 16 Nov 2004 15:25:34 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <WRVWXTSB>; Tue, 16 Nov 2004 15:25:34 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E990D@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "Ghyslain Pelletier (LU/EAB)" <ghyslain.pelletier@ericsson.com>,
        "'rohc@ietf.org'" <rohc@ietf.org>
Subject: RE: [rohc] Preliminary minutes from ROHC@IETF61
Date: Tue, 16 Nov 2004 15:25:32 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="ISO-8859-1"
X-OriginalArrivalTime: 16 Nov 2004 14:25:34.0775 (UTC)
	FILETIME=[22ABC470:01C4CBE8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69

ooops...

/L-E

> -----Original Message-----
> From: Ghyslain Pelletier (LU/EAB) 
> Sent: den 16 november 2004 15:25
> To: Lars-Erik Jonsson (LU/EAB); 'rohc@ietf.org'
> Subject: RE: [rohc] Preliminary minutes from ROHC@IETF61
> 
> 
> I found the following rather striking/amusing...
> 
> Bug = bad, Interoperable = good => Bug = interoperable!!! ; )
> 
> > * LLA ROHC RTP Implementer's guide (Sandlund)
> >
> > During implementation, a bug was identified in RFC 3242 that
> > makes the CSP packet interoperable.
> 
> s/interoperable/non-interoperable/
> 
> /Ghyslain
> 
> > -----Original Message-----
> > From: rohc-bounces@ietf.org 
> [mailto:rohc-bounces@ietf.org]On Behalf Of
> > Lars-Erik Jonsson (LU/EAB)
> > Sent: den 15 november 2004 17:26
> > To: 'rohc@ietf.org'
> > Subject: [rohc] Preliminary minutes from ROHC@IETF61
> > 
> > 
> > Minutes of the ROHC WG session at IETF 61
> > =========================================
> > 
> > Hilton Washington, Washington DC, USA
> > Monday Morning, 2004-11-08
> > 
> 

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


From rohc-bounces@ietf.org  Tue Nov 16 10:41:27 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10980
	for <rohc-web-archive@ietf.org>; Tue, 16 Nov 2004 10:41:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CU5Ue-0008Pi-Eo
	for rohc-web-archive@ietf.org; Tue, 16 Nov 2004 10:43:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CU5Nj-0004pd-R1; Tue, 16 Nov 2004 10:36:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CU5Aj-0002g6-Cv
	for rohc@megatron.ietf.org; Tue, 16 Nov 2004 10:23:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07879
	for <rohc@ietf.org>; Tue, 16 Nov 2004 10:23:07 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU5Cw-0007yQ-84
	for rohc@ietf.org; Tue, 16 Nov 2004 10:25:27 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FFXKT>; Tue, 16 Nov 2004 15:23:57 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8803D5977@rsys004a.roke.co.uk>
From: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
To: "'zhigang.c.liu@nokia.com'" <zhigang.c.liu@nokia.com>,
        "Conroy, Lawrence (SMTP)" <lwc@roke.co.uk>
Subject: RE: [rohc] Re: multiplexing SigComp and non-SigComp messages on t
	he same TCP connection
Date: Tue, 16 Nov 2004 15:23:54 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: "West, Mark" <mark.a.west@roke.co.uk>, Robert.Sugar@nokia.com,
        cabo@tzi.org, rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64

Hi All,

Just a short mail to share my understanding.

As far as I know, there was discussion about the multiplexing issue in San
Diego, but hasn't been much discussion on the RoHC mailing list since.

I have, however, talked to some 3GPP people about the issues of 3GPP
security associations, registration of multiple 'Public User Identities' and
multiplexing SigComp and SIP.

So far no-one that I've spoken to has been able to give me an example (even
taking into account the fixed ports) of a situation where there would be a
need to multiplex SIP and SigComp on the same TCP connection.  (The
'uncompressed SigComp header' can be used to solve all the cases I've been
given.)  Is there such an example?  I'd be interested to know if there is
one.

Best regards,

Abbie


> -----Original Message-----
> From: zhigang.c.liu@nokia.com [mailto:zhigang.c.liu@nokia.com] 
> Sent: Monday, November 15, 2004 4:00 PM
> To: Conroy, Lawrence (SMTP)
> Cc: West, Mark; Robert.Sugar@nokia.com; cabo@tzi.org; rohc@ietf.org
> Subject: RE: [rohc] Re: multiplexing SigComp and non-SigComp 
> messages on the same TCP connection
> 
> 
> That's good. Please share your thoughts. I have been placed into
> a waiting mode on sigcomp-sip since IETF-60. That's what I meant
> a pause, at least from my perspective.
> 
> Br, Zhigang
> 
> 
> > -----Original Message-----
> > From: ext Conroy, Lawrence (SMTP) [mailto:lwc@roke.co.uk]
> > Sent: 12 November, 2004 06:59 PM
> > To: Liu Zhigang.C (Nokia-NRC/Dallas)
> > Cc: Sugar Robert (Nokia-NET/Budapest); cabo@tzi.org; West, Mark;
> > rohc@ietf.org
> > Subject: Re: [rohc] Re: multiplexing SigComp and non-SigComp 
> > messages on
> > the same TCP connection
> > 

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


From rohc-bounces@ietf.org  Tue Nov 16 10:44:30 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11308
	for <rohc-web-archive@ietf.org>; Tue, 16 Nov 2004 10:44:30 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CU5Xe-0008VE-2g
	for rohc-web-archive@ietf.org; Tue, 16 Nov 2004 10:46:50 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CU5ON-00054o-Bn; Tue, 16 Nov 2004 10:37:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CU5IJ-0003lF-6j
	for rohc@megatron.ietf.org; Tue, 16 Nov 2004 10:30:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09997
	for <rohc@ietf.org>; Tue, 16 Nov 2004 10:30:57 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU5KX-0008Db-6R
	for rohc@ietf.org; Tue, 16 Nov 2004 10:33:17 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iAGFUjSO014309; Tue, 16 Nov 2004 16:30:47 +0100 (MET)
In-Reply-To: <3F2E01E1D7B04F4EBEC92D3FA324D8803D5977@rsys004a.roke.co.uk>
References: <3F2E01E1D7B04F4EBEC92D3FA324D8803D5977@rsys004a.roke.co.uk>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <7BD02E5E-37E4-11D9-811E-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] Re: multiplexing SigComp and non-SigComp messages on t he
	same TCP connection
Date: Tue, 16 Nov 2004 16:30:45 +0100
To: "Surtees, Abigail" <abigail.surtees@ROKE.CO.UK>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
Cc: "West, Mark" <mark.a.west@ROKE.CO.UK>, Robert.Sugar@nokia.com,
        "'zhigang.c.liu@nokia.com'" <zhigang.c.liu@nokia.com>, rohc@ietf.org,
        "Conroy, Lawrence \(SMTP\)" <lwc@ROKE.CO.UK>,
        Carsten Bormann <cabo@tzi.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit

Abbie,

3GPP submission S2-043577 says:

> For TCP, none of the existing standards mandates whether or not 
> endpoints must be able to multiplex SIP and SigComp messages on the 
> same TCP connection however, the IETF currently see no need to 
> multiplex and would like to mandate that it must not be done. We note 
> that with the IMS security architecture there are some constraints 
> with regards to the usage of ports on the P-CSCF and the UE. During 
> the establishment of the IPSec security association the UE and the 
> P-CSCF negotiate 2 ports on each side. These ports are used as the 
> selector for the corresponding security association and are fixed for 
> the duration of the security association. Consequently, if there is a 
> need to send both SIP and SigComp messages over TCP, they would have 
> to be on the same connection.
>
> It seems, however, that the issue is not a real issue for IMS and PoC, 
> as it is mandated that terminals and networks will support SigComp 
> (though its use is not mandatory). Consequently a terminal can decide 
> on the first message whether or not it is going to use SigComp and not 
> change. In this case, if there is a need to send an uncompressed 
> message (e.g. due to loss of sync between compressor and decompressor, 
> or to reduce processing load) when SigComp is in use, the 
> 'uncompressed SigComp header' can be used. This is a set of 13 well 
> known bytes that are prepended to the SIP message to make it a SigComp 
> message and are removed as a block at the decompressor.

This fits pretty well with what was said in the San Diego WG meeting 
and hallway discussions, and this is what was intended by my slide in 
Washington.

(Sorry if I'm incoherent -- I'm wrestling with my usual post-IETF 
aircon-induced fever.)

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Wed Nov 17 02:51:39 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23362
	for <rohc-web-archive@ietf.org>; Wed, 17 Nov 2004 02:51:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CUKdi-0001P1-Ot
	for rohc-web-archive@ietf.org; Wed, 17 Nov 2004 02:54:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUKXj-0002iK-IP; Wed, 17 Nov 2004 02:47:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUKC5-0004Tb-0o
	for rohc@megatron.ietf.org; Wed, 17 Nov 2004 02:25:33 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11601
	for <rohc@ietf.org>; Wed, 17 Nov 2004 02:25:31 -0500 (EST)
Received: from wire.cs.nthu.edu.tw ([140.114.79.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUKEM-0000t2-Vj
	for rohc@ietf.org; Wed, 17 Nov 2004 02:27:59 -0500
Received: from wire.cs.nthu.edu.tw (localhost.localdomain [127.0.0.1])
	by wire.cs.nthu.edu.tw (Postfix) with ESMTP id D9CAB17EF2
	for <rohc@ietf.org>; Wed, 17 Nov 2004 15:23:53 +0800 (CST)
From: "wool" <wool@wire.cs.nthu.edu.tw>
To: rohc@ietf.org
Subject: [rohc]How to implement W-LSB in ROHC?
Date: Wed, 17 Nov 2004 15:23:53 +0800
Message-Id: <20041117071435.M26006@wire.cs.nthu.edu.tw>
In-Reply-To: <20041115152527.M96737@wire.cs.nthu.edu.tw>
References: <20041115152527.M96737@wire.cs.nthu.edu.tw>
X-Mailer: Open WebMail 2.20 20031014
X-OriginatingIP: 140.114.63.35 (wool)
MIME-Version: 1.0
Content-Type: text/plain;
	charset=big5
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
X-Mailman-Approved-At: Wed, 17 Nov 2004 02:47:53 -0500
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4

ROHCers,
when i implement rohc,i didn't understand how to do RFC3095 rohc 4.5.2 W-LSB 
encoding,
May someone give me some examples? ex: how to use W-LSB encoding 
to do RTP SN?

for example:
SN=51=110011  SN=52=110100  SN=53=110101  SN=54=110110
UO_0_SN=0011  UO_0_SN=0100  UO_0_SN=0101  UO_0_SN=0110
but in UO_0 packet, it will "update current context of SN"
and in 5.3.2.2.5
if use ref_0 decompress SN LSB to get SN curr1,then decompressed packet
pass CRC
--> ref_-1 = ref_0, ref_0 = SN_curr1
in our emample:
assume ref_0 is 110000(SN = 48)
SN_curr1 = ref_0 + 0011 = 51
so, in 5.3.2.2.5,we will get ref_0 = SN_curr1 = 51
is it right?
if is not
how to use UO_0 in 5.3.2.2.5?
thanks....


(2)if compressor in Second Order state and in R-MODE,update packet is lost
(or ACK is lost),how the compressor to do?
because in U/O-MODE,compressor must be confident...
what to do can let compressor be confident...?

--
Open WebMail Project (http://openwebmail.org)
------- End of Forwarded Message -------


--
Open WebMail Project (http://openwebmail.org)


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


From rohc-bounces@ietf.org  Wed Nov 17 12:01:27 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19433
	for <rohc-web-archive@ietf.org>; Wed, 17 Nov 2004 12:01:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CUTDr-0006GX-B6
	for rohc-web-archive@ietf.org; Wed, 17 Nov 2004 12:04:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUSxv-0005hj-ES; Wed, 17 Nov 2004 11:47:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUStO-0004Ct-Kt
	for rohc@megatron.ietf.org; Wed, 17 Nov 2004 11:42:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17327
	for <rohc@ietf.org>; Wed, 17 Nov 2004 11:42:48 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUSvq-0005ff-9f
	for rohc@ietf.org; Wed, 17 Nov 2004 11:45:22 -0500
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAHGgYE24939; Wed, 17 Nov 2004 18:42:34 +0200 (EET)
X-Scanned: Wed, 17 Nov 2004 18:42:28 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id iAHGgSJx024335;
	Wed, 17 Nov 2004 18:42:28 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks002.ntc.nokia.com 00JZYqN8; Wed, 17 Nov 2004 18:42:26 EET
Received: from daebh001.NOE.Nokia.com (daebh001.americas.nokia.com
	[10.241.35.121])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAHGgOa07122; Wed, 17 Nov 2004 18:42:25 +0200 (EET)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by
	daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 17 Nov 2004 10:41:41 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc]How to implement W-LSB in ROHC?
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Wed, 17 Nov 2004 11:41:40 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B8153A4F@ajebe001.americas.nokia.com>
Thread-Topic: [rohc]How to implement W-LSB in ROHC?
Thread-Index: AcTMep9kCTyNwRd9QXWYo01IZ/XENQASAhTg
To: <wool@wire.cs.nthu.edu.tw>, <rohc@ietf.org>
X-OriginalArrivalTime: 17 Nov 2004 16:41:41.0585 (UTC)
	FILETIME=[50E1D410:01C4CCC4]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Content-Transfer-Encoding: quoted-printable
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Content-Transfer-Encoding: quoted-printable

Hi,

I cannot remember the details of U-mode decode logic from the top of my =
head. Someone else can probably give a good answer.

RE R-mode, I'm not sure which case you're asking. So I just give a broad =
answer and hopefully it's what you asked.
- If the header pattern remains the same, the compressor will remain in =
SO state and will not send update packet. One exception is when the RTP =
SN is close to wrap-around, i.e. close to 64 R-0 packets have been sent =
since last update. Please see section 5.5.1.2 for detail.
- If the header pattern changes, then the compressor will transit to FO =
state and send update packets.=20

In either case, the compressor in R-mode will handle loss of update =
packets and ACKs according to secure reference principle, described in =
section 5.5.

BR, Zhigang

> -----Original Message-----
> From: rohc-bounces@ietf.org [mailto:rohc-bounces@ietf.org]On=20
> Behalf Of ext wool
> Sent: 17 November, 2004 01:24 AM
> To: rohc@ietf.org
> Subject: [rohc]How to implement W-LSB in ROHC?
>=20
>=20
> ROHCers,
> when i implement rohc,i didn't understand how to do RFC3095=20
> rohc 4.5.2 W-LSB=20
> encoding,
> May someone give me some examples? ex: how to use W-LSB encoding=20
> to do RTP SN?
>=20
> for example:
> SN=3D51=3D110011  SN=3D52=3D110100  SN=3D53=3D110101  SN=3D54=3D110110
> UO_0_SN=3D0011  UO_0_SN=3D0100  UO_0_SN=3D0101  UO_0_SN=3D0110
> but in UO_0 packet, it will "update current context of SN"
> and in 5.3.2.2.5
> if use ref_0 decompress SN LSB to get SN curr1,then=20
> decompressed packet
> pass CRC
> --> ref_-1 =3D ref_0, ref_0 =3D SN_curr1
> in our emample:
> assume ref_0 is 110000(SN =3D 48)
> SN_curr1 =3D ref_0 + 0011 =3D 51
> so, in 5.3.2.2.5,we will get ref_0 =3D SN_curr1 =3D 51
> is it right?
> if is not
> how to use UO_0 in 5.3.2.2.5?
> thanks....
>=20
>=20
> (2)if compressor in Second Order state and in R-MODE,update=20
> packet is lost
> (or ACK is lost),how the compressor to do?
> because in U/O-MODE,compressor must be confident...
> what to do can let compressor be confident...?
>=20
> --
> Open WebMail Project (http://openwebmail.org)
> ------- End of Forwarded Message -------
>=20
>=20
> --
> Open WebMail Project (http://openwebmail.org)
>=20
>=20
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
>=20

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


From rohc-bounces@ietf.org  Thu Nov 18 05:58:21 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12496
	for <rohc-web-archive@ietf.org>; Thu, 18 Nov 2004 05:58:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CUk2D-0006XL-J1
	for rohc-web-archive@ietf.org; Thu, 18 Nov 2004 06:01:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUjyC-0006wD-8H; Thu, 18 Nov 2004 05:56:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUjwy-0006ho-Kc
	for rohc@megatron.ietf.org; Thu, 18 Nov 2004 05:55:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12293
	for <rohc@ietf.org>; Thu, 18 Nov 2004 05:55:37 -0500 (EST)
Received: from bay21-f8.bay21.hotmail.com ([65.54.233.97] helo=hotmail.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUjzX-0006RH-1H
	for rohc@ietf.org; Thu, 18 Nov 2004 05:58:22 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Thu, 18 Nov 2004 02:55:04 -0800
Message-ID: <BAY21-F8FB6855D34405583F317785C20@phx.gbl>
Received: from 194.218.191.2 by by21fd.bay21.hotmail.msn.com with HTTP;
	Thu, 18 Nov 2004 10:54:43 GMT
X-Originating-IP: [194.218.191.2]
X-Originating-Email: [gustav_kung@hotmail.com]
X-Sender: gustav_kung@hotmail.com
In-Reply-To: <7B5AF06E216CB74DA8A5960A3181B5B8153A4F@ajebe001.americas.nokia.com>
From: "Gustav E" <gustav_kung@hotmail.com>
To: rohc@ietf.org
Date: Thu, 18 Nov 2004 11:54:43 +0100
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
X-OriginalArrivalTime: 18 Nov 2004 10:55:04.0826 (UTC)
	FILETIME=[0F75FDA0:01C4CD5D]
X-Spam-Score: 0.8 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: [rohc] SigComp for Simple?
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab

Hi all!

I have a question regarding Simple (Session Initiation Protocol (SIP) 
Extension for Instant Messaging), RFC3428. Is SigComp supposed to be 
mandadory in a Simple implementation? Is SigComp the one and only 
compression idea when talking about Simple?

I've only just started browsing the Simple documents, but haven't been able 
get a clear answer.

Best Regards,
/Gustav E

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/


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


From rohc-bounces@ietf.org  Thu Nov 18 07:09:25 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17906
	for <rohc-web-archive@ietf.org>; Thu, 18 Nov 2004 07:09:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CUl90-0007wi-KI
	for rohc-web-archive@ietf.org; Thu, 18 Nov 2004 07:12:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUl49-0005ik-KK; Thu, 18 Nov 2004 07:07:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUl26-0005Bw-Bb
	for rohc@megatron.ietf.org; Thu, 18 Nov 2004 07:05:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17601
	for <rohc@ietf.org>; Thu, 18 Nov 2004 07:04:59 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUl4h-0007r5-Fv
	for rohc@ietf.org; Thu, 18 Nov 2004 07:07:44 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iAIC4ogA026012; Thu, 18 Nov 2004 13:04:51 +0100 (MET)
In-Reply-To: <BAY21-F8FB6855D34405583F317785C20@phx.gbl>
References: <BAY21-F8FB6855D34405583F317785C20@phx.gbl>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <0BCE066A-395A-11D9-811E-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] SigComp for Simple?
Date: Thu, 18 Nov 2004 13:04:49 +0100
To: "Gustav E" <gustav_kung@hotmail.com>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, "'rohc@ietf.org'" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit

On Nov 18 2004, at 11:54 Uhr, Gustav E wrote:

> Hi all!
>
> I have a question regarding Simple (Session Initiation Protocol (SIP) 
> Extension for Instant Messaging), RFC3428. Is SigComp supposed to be 
> mandadory in a Simple implementation? Is SigComp the one and only 
> compression idea when talking about Simple?

SigComp is certainly applicable to SIMPLE (both the SIP and the MSRP 
parts).
Whether it is mandatory (or the only compression idea) is probably not 
something that the ROHC working group can answer -- this is for SIMPLE 
(and the organizations applying the SIMPLE specifications) to decide.

If widespread use of compressed SIMPLE is foreseen, it would probably 
make sense to at some point do a variant of RFC3485 that includes MSRP, 
PIDF, RPIDF, etc.

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Thu Nov 18 10:36:58 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04213
	for <rohc-web-archive@ietf.org>; Thu, 18 Nov 2004 10:36:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CUoNt-0003vR-Bw
	for rohc-web-archive@ietf.org; Thu, 18 Nov 2004 10:39:45 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUoFe-0003Wv-De; Thu, 18 Nov 2004 10:31:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUnyb-0005xi-HM
	for rohc@megatron.ietf.org; Thu, 18 Nov 2004 10:13:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02275
	for <rohc@ietf.org>; Thu, 18 Nov 2004 10:13:35 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUo1E-0003UV-9i
	for rohc@ietf.org; Thu, 18 Nov 2004 10:16:21 -0500
Received: from sj-core-3.cisco.com (171.68.223.137)
	by sj-iport-5.cisco.com with ESMTP; 18 Nov 2004 07:13:12 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id iAIFCxYr028719;
	Thu, 18 Nov 2004 07:13:00 -0800 (PST)
Received: from [161.44.55.95] (dhcp-161-44-55-95.cisco.com [161.44.55.95])
	by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id AFV21783;
	Thu, 18 Nov 2004 07:12:59 -0800 (PST)
Message-ID: <419CBBFB.60102@cisco.com>
Date: Thu, 18 Nov 2004 10:12:59 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] SigComp for Simple?
References: <BAY21-F8FB6855D34405583F317785C20@phx.gbl>
	<0BCE066A-395A-11D9-811E-000A95DC4DB6@tzi.org>
In-Reply-To: <0BCE066A-395A-11D9-811E-000A95DC4DB6@tzi.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit
Cc: "'rohc@ietf.org'" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit

Nothing in any of the simple specifications mandates the usage of 
sigcomp, nor do I think it should.

-Jonathan R.

Carsten Bormann wrote:

> On Nov 18 2004, at 11:54 Uhr, Gustav E wrote:
> 
>> Hi all!
>>
>> I have a question regarding Simple (Session Initiation Protocol (SIP) 
>> Extension for Instant Messaging), RFC3428. Is SigComp supposed to be 
>> mandadory in a Simple implementation? Is SigComp the one and only 
>> compression idea when talking about Simple?
> 
> 
> SigComp is certainly applicable to SIMPLE (both the SIP and the MSRP 
> parts).
> Whether it is mandatory (or the only compression idea) is probably not 
> something that the ROHC working group can answer -- this is for SIMPLE 
> (and the organizations applying the SIMPLE specifications) to decide.
> 
> If widespread use of compressed SIMPLE is foreseen, it would probably 
> make sense to at some point do a variant of RFC3485 that includes MSRP, 
> PIDF, RPIDF, etc.
> 
> Gruesse, Carsten
> 
> 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

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


From rohc-bounces@ietf.org  Thu Nov 18 19:08:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07255
	for <rohc-web-archive@ietf.org>; Thu, 18 Nov 2004 19:08:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CUwNP-0003Vm-Ux
	for rohc-web-archive@ietf.org; Thu, 18 Nov 2004 19:11:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUwGE-0007J7-2s; Thu, 18 Nov 2004 19:04:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUw8S-0004vl-EU
	for rohc@megatron.ietf.org; Thu, 18 Nov 2004 18:56:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06011
	for <rohc@ietf.org>; Thu, 18 Nov 2004 18:56:16 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUwB9-000395-Og
	for rohc@ietf.org; Thu, 18 Nov 2004 18:59:09 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FGV2S>; Thu, 18 Nov 2004 23:57:12 -0000
Received: from mjw-pc.roke.co.uk ([193.118.194.159]) by rsys002a.roke.co.uk
	with SMTP (Microsoft Exchange Internet Mail Service Version
	5.5.2657.72) id V2Q3RYFQ; Thu, 18 Nov 2004 23:57:18 -0000
From: "West, Mark" <mark.a.west@roke.co.uk>
To: rohc@ietf.org
Date: Fri, 19 Nov 2004 01:30:53 +0000 (GMT)
X-X-Sender: maw@mjw-pc.roke.co.uk
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8806C415D-100000@rsys004a.roke.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Subject: [rohc] ROHC-TCP, ack number compression
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be


Hi all,

I've been doing a little bit more thinking about 'ack compression' --
currently we're just handling it as a 'normal' LSB encoding (compared with
seqno, where we allow for scaling by the payload size when that remains
stable).

There appear to be three possible things to do:

1/ stay as we are;

2/ do some sort of generic ack optimisation (a la Carsten's thought); or

2/ do some sort of bi-directional ack optimisation.

In no particular order... ;-)


(1) has the advantage that it's simple and we know it'll work.  However,
it is clear that it is going to cost some bits in, for example, the
reverse-path of a bulk data download:
	Ethernet MTU assumed ~  1460 octets
	Ack ratio assumed == 2
	Resilience to loss assumed ~ 4 packets
		=> 14 bits of Ack Number

Whatever happens, we need to support this case -- it's the one that'll
work regardless of anything else!


(2) relies upon the fact that payload sizes tend to be multiples of powers
of 2 (4, 8, 16, ...) which does appear to be the case (and, for small
multiples, makes sense from an implementation perspective).  If a run of
packets with payload sizes of a multiple of (say) 16, we could scale the
ack.
	Scaling of 16 -> 4 bits saved
		=> 10 bits of Ack Number

But... I can't see anyway of doing this without explicitly sending an 'ack
scale' value to the decompressor: I'm not convinced that this is the sort
of thing that you want to derive on the fly?  (You *could*, but...)

Also, NB, if we do think about doing this for ackno, then you could do it
for seqno as well (although I think that the general 'stable payload size
scaling' is plenty good enough!)


(3) relies upon the fact that, whilst it need not be the case, it is
highly likely that an ack value in the reverse path is directly acking a
packet in the forward path (i.e. it contains seq_no + payload_len). Thus,
if you know that the other endpoint has seen the packet in the forward
direction [you have decompressed the packet!], then you can identify an
ack by indicating which packet is being acked (by the MSN).

If you assume that the ack flow more-or-less moves in step (i.e.
increasing MSNs), then you get:
	Ack ratio assumed == 2
	Resilience to loss assumed ~ 4 packets
		=> 3+ bits of Ack Number (actually would need to allow
                                          for more of a window)
The advantage, then, is the potential saving.
The disadvantages are:

- it only works when the compressor/decompressor can share data;

- the endpoints have to store histories of 'expected' ack numbers and the
compressor and decompressor have to manage this shared state such that it
doesn't get out of synchronisation [this is single biggest complexity
issue, for me];

- the issue of switching between 'MSN-based' and 'raw-ackno-based'
compression (which, if we assume only happens rarely, shouldn't be too
much of an issue).


Comments?


Cheers,

Mark.


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


From rohc-bounces@ietf.org  Fri Nov 19 02:25:18 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28434
	for <rohc-web-archive@ietf.org>; Fri, 19 Nov 2004 02:25:18 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CV3Ba-0004av-7W
	for rohc-web-archive@ietf.org; Fri, 19 Nov 2004 02:28:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CV33z-00074P-NP; Fri, 19 Nov 2004 02:20:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CV333-0006Oh-Th
	for rohc@megatron.ietf.org; Fri, 19 Nov 2004 02:19:14 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27269
	for <rohc@ietf.org>; Fri, 19 Nov 2004 02:19:13 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV35f-0004RB-CI
	for rohc@ietf.org; Fri, 19 Nov 2004 02:22:06 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAJ7J0h5012200
	for <rohc@ietf.org>; Fri, 19 Nov 2004 08:19:01 +0100 (MET)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 19 Nov 2004 08:19:00 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <WRVX3NA2>; Fri, 19 Nov 2004 08:19:00 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E9936@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Subject: RE: [rohc] ROHC-TCP, ack number compression
Date: Fri, 19 Nov 2004 08:18:57 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="ISO-8859-1"
X-OriginalArrivalTime: 19 Nov 2004 07:19:00.0955 (UTC)
	FILETIME=[0ACE02B0:01C4CE08]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3

> (3) relies upon the fact that, whilst it need not be the 
> case, it is highly
> likely that an ack value in the reverse path is directly 
> acking a packet in
> the forward path (i.e. it contains seq_no + payload_len).  
> Thus, if you know
> that the other endpoint has seen the packet in the forward 
> direction [you
> have decompressed the packet!], then you can identify an ack 
> by indicating
> which packet is being acked (by the MSN).
> 
> If you assume that the ack flow more-or-less moves in step 
> (i.e. increasing
> MSNs), then you get:
> 	Ack ratio assumed == 2
> 	Resilience to loss assumed ~ 4 packets
> 		=> 3+ bits of Ack Number (actually would need 
> to allow for
> more of a window)
> The advantage is, therefore, pretty clear in terms of 
> potential savings.
> 
> The disadvantages of this approach are:
> 
> - it only works when the compressor/decompressor can share data;
> 
> - the remote compressor (decompressor) has to store a history 
> of 'expected' ACK numbers (and the other end has to know how
> long this is!) [this is single biggest complexity issue, for me];

Long in what regard? I have not thought much about this yet, just get
the feeling we will have to do so. As Carsten noted, we will have to
be robust to losses, with e.g. a generation number. How much will we
save in the end? 


> - the issue of switching between 'MSN-based' and 'raw-ackno-based'
> compression (which, if we assume only happens rarely, shouldn't
> be too much of an issue).

I would rather ask:
1) How do two corresponding rohc pairs agree to use "bi-dir compr"?
2) Is the association between co-located compressor/decompressor
   used for this the same association used for piggybacked feedback?
2) Should it be possible to enable/disable this during operation?

I would not say enabling "bi-dir compr" is not much of an issue.


/L-E

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


From rohc-bounces@ietf.org  Fri Nov 19 03:05:18 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02376
	for <rohc-web-archive@ietf.org>; Fri, 19 Nov 2004 03:05:18 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CV3oI-0005OD-Df
	for rohc-web-archive@ietf.org; Fri, 19 Nov 2004 03:08:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CV3gu-00026w-FB; Fri, 19 Nov 2004 03:00:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CV3ed-0001OM-Ir
	for rohc@megatron.ietf.org; Fri, 19 Nov 2004 02:58:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01541
	for <rohc@ietf.org>; Fri, 19 Nov 2004 02:58:02 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV3hM-0005Ck-42
	for rohc@ietf.org; Fri, 19 Nov 2004 03:00:53 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAJ7vvR2028919 for <rohc@ietf.org>; Fri, 19 Nov 2004 08:57:57 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 19 Nov 2004 08:57:57 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <WRVX3W45>; Fri, 19 Nov 2004 08:57:56 +0100
Message-ID: <A943FD84BD9ED41193460008C79180500BABAFAA@ESEALNT419.al.sw.ericsson.se>
From: "Jan Christoffersson (LU/EAB)" <jan.christoffersson@ericsson.com>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Fri, 19 Nov 2004 08:57:51 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="ISO-8859-1"
X-OriginalArrivalTime: 19 Nov 2004 07:57:57.0718 (UTC)
	FILETIME=[7B9FBF60:01C4CE0D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Subject: [rohc] sigcomp compartments
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8

Hi,
read in the meeting minutes about the discussions of possible compartment definitions for sigcomp. 

"Second issue is about the definition of compartments, as they need
to be well-defined to avoid accidental push-outs. The original
proposal was to use SIP dialogs, but another idea is to have three
different compartments for; registration related messages (R),
dialog-related messages (D), and subscription-related messages (S)."

I'm curious to know why this would be needed. Of course you need to know how long a compartment lasts, but why the need for different compartment types? Wouldn't a compartment that lasts throughout the users registration be sufficient?

Best regards,
Jan



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


From rohc-bounces@ietf.org  Fri Nov 19 04:03:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06756
	for <rohc-web-archive@ietf.org>; Fri, 19 Nov 2004 04:03:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CV4iZ-0006q4-BK
	for rohc-web-archive@ietf.org; Fri, 19 Nov 2004 04:06:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CV4Yt-0003eP-Ia; Fri, 19 Nov 2004 03:56:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CV4UW-0002w8-BA
	for rohc@megatron.ietf.org; Fri, 19 Nov 2004 03:51:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05867
	for <rohc@ietf.org>; Fri, 19 Nov 2004 03:51:38 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV4X9-0006F6-Gx
	for rohc@ietf.org; Fri, 19 Nov 2004 03:54:33 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iAJ8pMaZ026579; Fri, 19 Nov 2004 09:51:23 +0100 (MET)
In-Reply-To: <A943FD84BD9ED41193460008C79180500BABAFAA@ESEALNT419.al.sw.ericsson.se>
References: <A943FD84BD9ED41193460008C79180500BABAFAA@ESEALNT419.al.sw.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <2EF471A2-3A08-11D9-811E-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] sigcomp compartments
Date: Fri, 19 Nov 2004 09:51:20 +0100
To: "Jan Christoffersson (LU/EAB)" <jan.christoffersson@ericsson.com>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, "'rohc@ietf.org'" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit

> "Second issue is about the definition of compartments, as they need
> to be well-defined to avoid accidental push-outs. The original
> proposal was to use SIP dialogs, but another idea is to have three
> different compartments for; registration related messages (R),
> dialog-related messages (D), and subscription-related messages (S)."
>
> I'm curious to know why this would be needed. Of course you need to 
> know how long a compartment lasts, but why the need for different 
> compartment types? Wouldn't a compartment that lasts throughout the 
> users registration be sufficient?

For IMS, yes, this is the way it (IMS) is defined.

For SIP in the general Internet, there might not be a registration.
In general, compartments should be attached to the pieces of state kept 
by the SIP speakers.
So far, we have identified calls (generalized in SIP as dialogs), 
subscriptions, and registrations.

Note that the term "compartment" is a bit misleading: If two SIP 
speakers engage in messages that are allocated to more than one 
compartment at a decompressor, the compressor can actually make use of 
the state from all these compartments in any of the messages.  So 
allocating additional (from the point of view of IMS) compartments to 
dialogs and subscriptions just means that less state will be pushed out 
of the registration compartment defined by IMS.
In other words, a general Internet SigComp/SIP decompressor is 
interoperable (if not maximallyy efficient) with an IMS SigComp/SIP 
compressor.
A general Internet SigComp/SIP compressor will assume the existence of 
more compartments at the decompressor than defined by IMS.
With NACK (which everybody should be implementing by now) and some 
generous caching of expired state at the decompressor, this will 
probably not hurt too much (assuming that it is even sensible to think 
about a general Internet SIP speaker talking to an IMS SIP speaker).

I've been spending my copious free time the last couple of days trying 
to nail down the SIPspeak terminology for this compartment allocation 
strategy; I hope to finish that today and submit 
draft-ietf-rohc-sigcomp-sip-02.txt based on the above deliberations and 
my findings.
This will include language that allows private agreements about 
compartment allocation (as in IMS).

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Mon Nov 22 06:42:21 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20605
	for <rohc-web-archive@ietf.org>; Mon, 22 Nov 2004 06:42:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWCdp-0006dG-5K
	for rohc-web-archive@ietf.org; Mon, 22 Nov 2004 06:45:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWCYU-0000nr-IZ; Mon, 22 Nov 2004 06:40:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWCTY-0000CO-Ig
	for rohc@megatron.ietf.org; Mon, 22 Nov 2004 06:35:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19734
	for <rohc@ietf.org>; Mon, 22 Nov 2004 06:35:18 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWCWz-0006Aj-M9
	for rohc@ietf.org; Mon, 22 Nov 2004 06:38:54 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FHZHV>; Mon, 22 Nov 2004 11:36:14 -0000
Received: from mjw-pc.roke.co.uk ([193.118.194.159]) by rsys002a.roke.co.uk
	with SMTP (Microsoft Exchange Internet Mail Service Version
	5.5.2657.72) id V2Q3RZ93; Mon, 22 Nov 2004 11:36:16 -0000
From: "West, Mark" <mark.a.west@roke.co.uk>
To: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
Date: Mon, 22 Nov 2004 11:34:39 +0000 (GMT)
X-X-Sender: maw@mjw-pc.roke.co.uk
Subject: RE: [rohc] ROHC-TCP, ack number compression
In-Reply-To: <A943FD84BD9ED41193460008C7918050072E9936@ESEALNT419.al.sw.ericsson.se>
Message-ID: <Pine.LNX.4.44.0411221115030.32526-100000@mjw-pc.roke.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: "'rohc@ietf.org'" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17



> > - the remote compressor (decompressor) has to store a history
> > of 'expected' ACK numbers (and the other end has to know how
> > long this is!) [this is single biggest complexity issue, for me];
>
> Long in what regard? I have not thought much about this yet, just get
> the feeling we will have to do so. As Carsten noted, we will have to
> be robust to losses, with e.g. a generation number. How much will we
> save in the end?
>

I hadn't thought about it much at the time, but have done a bit more
thinking now (and hopefully untangled my brain in the process!)

So... the basic observation is that (for many links) a packet sent from
A -> B with msn_A, seqno_A, and payload_size_A can be used to derive an
acknowledgement value in the reverse direction.  That is, there may be a
packet with ackno_B == (seqno_A + payload_size_A).

First of all, the compressor at A must indicate to B that it is storing
tuples (msn_A, seqno_A + payload_size_A) and that B may use these to
compress ack numbers.  A will store these tuples in a list of bounded
size.  (There isn't a 'generation number' per se -- we use the msn as the
index).

B, on correct decompression, maintains its own list (assuming that it
wants to do this -- it should be possible for B to signal A that it
doesn't want to, so A can avoid storing the tuples unnecessarily).  When B
wants to compress an ack value, it looks it up in the list.  If it finds a
match, then it needs to signal (robustly) the value of msn_A to A.

This, though, is just a general initialise value + LSB encoding problem.
(i.e. B may encode msn_a as irregular in the first n packets it sends,
followed by suitable LSB encoding)

To manage the length of the list of tuples, B will only ever refer to
msn_a values that stay the same or increase.  So, for example, once B has
referenced msn_A of 238, it will never refer to an msn_A < 238; so A can
discard these from its history.  A, in its turn, needs to be able to
signal an error if it would ever overflow its tuple-storage (i.e. it would
have to discard something that B believes to be available for reference).
Each tuple is <= 8 octets [depending upon how much msn is kept], so
storage shouldn't be a major issue...

It clearly has to be optional at both ends to do this.  If A's storage is
insufficent for a link, it will discover this (by overflowing its buffer);
if B's storage is insufficient it will realise (by not being able to find
ack numbers in its history).

In terms of saving, if we expect an ack ratio of 2, then every other
packet in the forward direction will be referenced (and the typical
'interval' in msn_A is 2, rather than 1400+ for the actual ackno).  This
is quite a saving.

Retransmissions may cause some inefficiency (and I haven't thought through
all of the cases yet), but I *think* only where multiple, non-contiguous
packets are lost.

It sort of feels like it ought to work, in a fairly simple way.  But I
might just be missing something glaringly obvious :-)

Cheers,

Mark.


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


From rohc-bounces@ietf.org  Mon Nov 22 07:04:12 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22136
	for <rohc-web-archive@ietf.org>; Mon, 22 Nov 2004 07:04:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWCyy-0007jj-MF
	for rohc-web-archive@ietf.org; Mon, 22 Nov 2004 07:07:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWCqw-0003tW-Pr; Mon, 22 Nov 2004 06:59:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWCjY-0003D7-9C
	for rohc@megatron.ietf.org; Mon, 22 Nov 2004 06:51:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21519
	for <rohc@ietf.org>; Mon, 22 Nov 2004 06:51:49 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWCmp-00077c-Dj
	for rohc@ietf.org; Mon, 22 Nov 2004 06:55:26 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAMBpZR2032557 for <rohc@ietf.org>; Mon, 22 Nov 2004 12:51:35 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 22 Nov 2004 12:51:35 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <WRVYCAHA>; Mon, 22 Nov 2004 12:51:35 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E994C@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'West, Mark'" <mark.a.west@roke.co.uk>
Subject: RE: [rohc] ROHC-TCP, ack number compression
Date: Mon, 22 Nov 2004 12:51:33 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="ISO-8859-1"
X-OriginalArrivalTime: 22 Nov 2004 11:51:35.0609 (UTC)
	FILETIME=[9E2D6A90:01C4D089]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f
Cc: "'rohc@ietf.org'" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93e7fb8fef2e780414389440f367c879

Mark,

I know you tried in your previous mail to give numbers on what 
savings we could expect, but I would like to get that clearer.

We need to look at the overall savings, i.e.:

* Compare uncompressed with compressed not using shared compression,
  and then add shared compression to that.

* When comparing shared versus not-shared, the not-shared case
  should be with the best possible alternative for ack optimization
  that we can come up with. 

As I still believe adding shared compression is an ugly solution
that is conceptually different than what we have ever done in
ROHC, I really want to understand how much it will actually give
us in terms of compression gains, and I want to see alternatives
carefully investigated before I'm willing to consider supporting
shared compression. If there are alternatives that can give us
almost as much, I would prefer not to go with shared operation.

/L-E


> -----Original Message-----
> From: West, Mark [mailto:mark.a.west@roke.co.uk]
> Sent: den 22 november 2004 12:35
> To: Lars-Erik Jonsson (LU/EAB)
> Cc: 'rohc@ietf.org'
> Subject: RE: [rohc] ROHC-TCP, ack number compression
> 
> 
> 
> 
> > > - the remote compressor (decompressor) has to store a history
> > > of 'expected' ACK numbers (and the other end has to know how
> > > long this is!) [this is single biggest complexity issue, for me];
> >
> > Long in what regard? I have not thought much about this 
> yet, just get
> > the feeling we will have to do so. As Carsten noted, we will have to
> > be robust to losses, with e.g. a generation number. How much will we
> > save in the end?
> >
> 
> I hadn't thought about it much at the time, but have done a bit more
> thinking now (and hopefully untangled my brain in the process!)
> 
> So... the basic observation is that (for many links) a packet 
> sent from
> A -> B with msn_A, seqno_A, and payload_size_A can be used to 
> derive an
> acknowledgement value in the reverse direction.  That is, 
> there may be a
> packet with ackno_B == (seqno_A + payload_size_A).
> 
> First of all, the compressor at A must indicate to B that it 
> is storing
> tuples (msn_A, seqno_A + payload_size_A) and that B may use these to
> compress ack numbers.  A will store these tuples in a list of bounded
> size.  (There isn't a 'generation number' per se -- we use 
> the msn as the
> index).
> 
> B, on correct decompression, maintains its own list (assuming that it
> wants to do this -- it should be possible for B to signal A that it
> doesn't want to, so A can avoid storing the tuples 
> unnecessarily).  When B
> wants to compress an ack value, it looks it up in the list.  
> If it finds a
> match, then it needs to signal (robustly) the value of msn_A to A.
> 
> This, though, is just a general initialise value + LSB 
> encoding problem.
> (i.e. B may encode msn_a as irregular in the first n packets it sends,
> followed by suitable LSB encoding)
> 
> To manage the length of the list of tuples, B will only ever refer to
> msn_a values that stay the same or increase.  So, for 
> example, once B has
> referenced msn_A of 238, it will never refer to an msn_A < 
> 238; so A can
> discard these from its history.  A, in its turn, needs to be able to
> signal an error if it would ever overflow its tuple-storage 
> (i.e. it would
> have to discard something that B believes to be available for 
> reference).
> Each tuple is <= 8 octets [depending upon how much msn is kept], so
> storage shouldn't be a major issue...
> 
> It clearly has to be optional at both ends to do this.  If 
> A's storage is
> insufficent for a link, it will discover this (by overflowing 
> its buffer);
> if B's storage is insufficient it will realise (by not being 
> able to find
> ack numbers in its history).
> 
> In terms of saving, if we expect an ack ratio of 2, then every other
> packet in the forward direction will be referenced (and the typical
> 'interval' in msn_A is 2, rather than 1400+ for the actual 
> ackno).  This
> is quite a saving.
> 
> Retransmissions may cause some inefficiency (and I haven't 
> thought through
> all of the cases yet), but I *think* only where multiple, 
> non-contiguous
> packets are lost.
> 
> It sort of feels like it ought to work, in a fairly simple way.  But I
> might just be missing something glaringly obvious :-)
> 
> Cheers,
> 
> Mark.
> 
> 
> -- 
> 
> Visit our website at www.roke.co.uk
> 
> Roke Manor Research Ltd, Roke Manor, Romsey, Hampshire SO51 0ZN, UK.
> 
> 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.
> 

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


From rohc-bounces@ietf.org  Mon Nov 22 07:07:13 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22481
	for <rohc-web-archive@ietf.org>; Mon, 22 Nov 2004 07:07:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWD1t-0007uk-Kw
	for rohc-web-archive@ietf.org; Mon, 22 Nov 2004 07:10:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWCtT-0004Ha-Ab; Mon, 22 Nov 2004 07:02:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWCqP-0003lU-MO
	for rohc@megatron.ietf.org; Mon, 22 Nov 2004 06:58:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21882
	for <rohc@ietf.org>; Mon, 22 Nov 2004 06:58:55 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWCtq-0007Ro-Ac
	for rohc@ietf.org; Mon, 22 Nov 2004 07:02:31 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FHZRT>; Mon, 22 Nov 2004 11:59:54 -0000
Received: from mjw-pc.roke.co.uk ([193.118.194.159]) by rsys002a.roke.co.uk
	with SMTP (Microsoft Exchange Internet Mail Service Version
	5.5.2657.72) id V2Q3RZ0G; Mon, 22 Nov 2004 12:00:00 -0000
From: "West, Mark" <mark.a.west@roke.co.uk>
To: rohc@ietf.org
Date: Mon, 22 Nov 2004 11:58:22 +0000 (GMT)
X-X-Sender: maw@mjw-pc.roke.co.uk
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8806C4160-100000@rsys004a.roke.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Subject: [rohc] TCP sequence number encoding
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d


Hi all,

Having rambled on enough about ack numbers, here are some thoughts about
sequence number encoding...

In general, sequence numbers increase (this should not come as a great
surprise to anyone); but we obviously have to handle retransmissions.

The point is that I would expect retransmissions to involve a small number
of packets deviating from the general trend of increasing.  In that case,
it may be preferable for the backward jumps to not update the context at
the decompressor.  If they *do* update the context, then when the
retransmission has completed and the sequence number picks up its general
increase, we have to count the current high water-mark + the
retransmission in the LSB window.

On the assumption that the compressor is seeing all of the traffic (ok,
there are scenarios where this isn't the case -- we can't rely upon it),
the compressor may be able to work out whether it's expecting single or
multiple packet retransmits and manage context updating accordingly.

I don't know how significant this is in terms of the overall efficiency
gain (if any!), but thought that it was an issue that we ought to consider
and agree on; even if we're happy to leave the formats as they are...

Cheers,

Mark.

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

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


From rohc-bounces@ietf.org  Mon Nov 22 07:57:12 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25640
	for <rohc-web-archive@ietf.org>; Mon, 22 Nov 2004 07:57:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWDoF-0001tX-5H
	for rohc-web-archive@ietf.org; Mon, 22 Nov 2004 08:00:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWDjo-00047D-Un; Mon, 22 Nov 2004 07:56:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWDjB-00041I-ED
	for rohc@megatron.ietf.org; Mon, 22 Nov 2004 07:55:33 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25550
	for <rohc@ietf.org>; Mon, 22 Nov 2004 07:55:32 -0500 (EST)
Received: from [194.237.235.30] (helo=effnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWDmc-0001kn-O4
	for rohc@ietf.org; Mon, 22 Nov 2004 07:59:07 -0500
Received: from effnet.com (c-b97c71d5.04-205-6c756c1.cust.bredbandsbolaget.se
	[213.113.124.185]) (authenticated bits=0)
	by effnet.com (8.12.3/8.12.3) with ESMTP id iAMBsSLh003033
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Mon, 22 Nov 2004 12:54:28 +0100
Message-ID: <41A1E260.3080304@effnet.com>
Date: Mon, 22 Nov 2004 13:58:08 +0100
From: Kristofer Sandlund <kristofer.sandlund@effnet.com>
Organization: Effnet
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "West, Mark" <mark.a.west@roke.co.uk>
Subject: Re: [rohc] ROHC-TCP, ack number compression
References: <Pine.LNX.4.44.0411221115030.32526-100000@mjw-pc.roke.co.uk>
In-Reply-To: <Pine.LNX.4.44.0411221115030.32526-100000@mjw-pc.roke.co.uk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Content-Transfer-Encoding: 7bit
Cc: "'rohc@ietf.org'" <rohc@ietf.org>,
        "Lars-Erik Jonsson \(LU/EAB\)" <lars-erik.jonsson@ericsson.com>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Content-Transfer-Encoding: 7bit

Hi Mark,

This seems like a really complex scheme. Wouldn't explicit signaling of 
ACK_stride be a simpler and _almost_ as efficient a solution to this? Then, the 
decompressor at B could infer this value with or without the help of the 
co-located compressor without the spec having to go into this messy area.

With the scheme you suggest, compressor B has to "(robustly) signal msn_a to A", 
so why not send an explicit scale value instead? If the compressor at B is 
implemented to use the co-located decompressor's info, it should seldom have to 
send the SEQ_scale more than once and manage scaling on "many" packets. Then we 
also get out of having to have some feature negotiation (or feature rejection as 
you suggest).

/Kristofer Sandlund, Effnet AB

West, Mark wrote:
> 
>>>- the remote compressor (decompressor) has to store a history
>>>of 'expected' ACK numbers (and the other end has to know how
>>>long this is!) [this is single biggest complexity issue, for me];
>>
>>Long in what regard? I have not thought much about this yet, just get
>>the feeling we will have to do so. As Carsten noted, we will have to
>>be robust to losses, with e.g. a generation number. How much will we
>>save in the end?
>>
> 
> 
> I hadn't thought about it much at the time, but have done a bit more
> thinking now (and hopefully untangled my brain in the process!)
> 
> So... the basic observation is that (for many links) a packet sent from
> A -> B with msn_A, seqno_A, and payload_size_A can be used to derive an
> acknowledgement value in the reverse direction.  That is, there may be a
> packet with ackno_B == (seqno_A + payload_size_A).
> 
> First of all, the compressor at A must indicate to B that it is storing
> tuples (msn_A, seqno_A + payload_size_A) and that B may use these to
> compress ack numbers.  A will store these tuples in a list of bounded
> size.  (There isn't a 'generation number' per se -- we use the msn as the
> index).
> 
> B, on correct decompression, maintains its own list (assuming that it
> wants to do this -- it should be possible for B to signal A that it
> doesn't want to, so A can avoid storing the tuples unnecessarily).  When B
> wants to compress an ack value, it looks it up in the list.  If it finds a
> match, then it needs to signal (robustly) the value of msn_A to A.
> 
> This, though, is just a general initialise value + LSB encoding problem.
> (i.e. B may encode msn_a as irregular in the first n packets it sends,
> followed by suitable LSB encoding)
> 
> To manage the length of the list of tuples, B will only ever refer to
> msn_a values that stay the same or increase.  So, for example, once B has
> referenced msn_A of 238, it will never refer to an msn_A < 238; so A can
> discard these from its history.  A, in its turn, needs to be able to
> signal an error if it would ever overflow its tuple-storage (i.e. it would
> have to discard something that B believes to be available for reference).
> Each tuple is <= 8 octets [depending upon how much msn is kept], so
> storage shouldn't be a major issue...
> 
> It clearly has to be optional at both ends to do this.  If A's storage is
> insufficent for a link, it will discover this (by overflowing its buffer);
> if B's storage is insufficient it will realise (by not being able to find
> ack numbers in its history).
> 
> In terms of saving, if we expect an ack ratio of 2, then every other
> packet in the forward direction will be referenced (and the typical
> 'interval' in msn_A is 2, rather than 1400+ for the actual ackno).  This
> is quite a saving.
> 
> Retransmissions may cause some inefficiency (and I haven't thought through
> all of the cases yet), but I *think* only where multiple, non-contiguous
> packets are lost.
> 
> It sort of feels like it ought to work, in a fairly simple way.  But I
> might just be missing something glaringly obvious :-)
> 
> Cheers,
> 
> Mark.
> 
> 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc

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


From rohc-bounces@ietf.org  Mon Nov 22 08:37:43 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28778
	for <rohc-web-archive@ietf.org>; Mon, 22 Nov 2004 08:37:43 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWERS-00045o-K4
	for rohc-web-archive@ietf.org; Mon, 22 Nov 2004 08:41:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWEMh-00010w-F8; Mon, 22 Nov 2004 08:36:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWEHg-00007t-6S
	for rohc@megatron.ietf.org; Mon, 22 Nov 2004 08:31:12 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28419
	for <rohc@ietf.org>; Mon, 22 Nov 2004 08:31:11 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWEL6-0003n7-4O
	for rohc@ietf.org; Mon, 22 Nov 2004 08:34:47 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FH54B>; Mon, 22 Nov 2004 13:32:01 -0000
Received: from mjw-pc.roke.co.uk ([193.118.194.159]) by rsys002a.roke.co.uk
	with SMTP (Microsoft Exchange Internet Mail Service Version
	5.5.2657.72) id V2Q3R5BP; Mon, 22 Nov 2004 13:32:06 -0000
From: "West, Mark" <mark.a.west@roke.co.uk>
To: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
Date: Mon, 22 Nov 2004 13:30:28 +0000 (GMT)
X-X-Sender: maw@mjw-pc.roke.co.uk
Subject: RE: [rohc] ROHC-TCP, ack number compression
In-Reply-To: <A943FD84BD9ED41193460008C7918050072E994C@ESEALNT419.al.sw.ericsson.se>
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8806C4161-100000@rsys004a.roke.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 140baa79ca42e6b0e2b4504291346186
Cc: "'rohc@ietf.org'" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a492040269d440726bfd84680622cee7


Hmmm... it's often hard to put accurate numbers on these things without
acutally implementing it... :-)

However, let me try and discuss the numbers a bit more and see if that
clarifies things (there's always a first time!)

Uncompressed ack number = 32 bits (that one, at least, is easy)

Now, for this bit, I'm going to have to make some assumptions:

- MSS is ~1460 octets;
- robust to moderate loss / re-ordering -- allowing 3 bits for this;
- ack ratio == 2;
- this is a simple case without particular note of retransmissions

Expected compressed ack value with 'basic' LSB encoding is based on the
MSS and the ack ratio -- so we expect the 'average' stride to be ~2920.
This translates into 12 bits without any robustness; so we'd expect 15
bits once we've accounted for loss and re-ordering.

With a reverse-path ack compression scheme, I need to track changes in the
msn.  With an ack ratio of 2, this would require 1 bit.  The robustness
tax takes me up to around 4 bits.

With an 'implicit' ack 'stride' compression scheme (i.e. the decompressor
infers the stride from successive acks and the msn), you should be able to
achieve similar performance to reverse-path compression *if* the payload
size in the forward path remains fixed (dropping back to 'normal'
compression where it changes).  So, the expected size is somewhere between
4 and 15 bits -- it's quite hard to suggest where it might fall...
... plus it feels a bit fragile, but that might be because I haven't
thought through all the options.

With an 'explicit' ack 'stride' compression, you need first of all to make
assumptions about (i) the number of different strides you want to support;
and (ii) the range of strides (in terms of bit-reduction).  I'm assuming
that signalling the ack stride only takes a few bits (in terms of some
cost in indicator and 2 bits [say] to indicate the scaling factor) and
would need to be done relatively frequently.  However, this should add
less than 1 bit to the expected ack encoding.  The reduction that you
would get depends upon the scaling factor that you'd be able to use.
Maybe you could get 5 bits?

Summary:

- uncompressed ack           : 32 bits
- 'vanilla' ack compression  : 15 bits
- bi-directional compression :  4 bits
- implicit ack stride        : ?? bits
- explicit ack stride        : 10 bits ?

If I've made some dodgy assumptions or screwed up any of the calculations,
then I'm sure that folks will correct me... :-)

Cheers,

Mark.

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

On Mon, 22 Nov 2004, Lars-Erik Jonsson (LU/EAB) wrote:

> Date: Mon, 22 Nov 2004 12:51:33 +0100
> From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
> To: "'West, Mark'" <mark.a.west@roke.co.uk>
> Cc: "'rohc@ietf.org'" <rohc@ietf.org>
> Subject: RE: [rohc] ROHC-TCP, ack number compression
>
> Mark,
>
> I know you tried in your previous mail to give numbers on what
> savings we could expect, but I would like to get that clearer.
>
> We need to look at the overall savings, i.e.:
>
> * Compare uncompressed with compressed not using shared compression,
>   and then add shared compression to that.
>
> * When comparing shared versus not-shared, the not-shared case
>   should be with the best possible alternative for ack optimization
>   that we can come up with.
>
> As I still believe adding shared compression is an ugly solution
> that is conceptually different than what we have ever done in
> ROHC, I really want to understand how much it will actually give
> us in terms of compression gains, and I want to see alternatives
> carefully investigated before I'm willing to consider supporting
> shared compression. If there are alternatives that can give us
> almost as much, I would prefer not to go with shared operation.
>
> /L-E
>
>
> > -----Original Message-----
> > From: West, Mark [mailto:mark.a.west@roke.co.uk]
> > Sent: den 22 november 2004 12:35
> > To: Lars-Erik Jonsson (LU/EAB)
> > Cc: 'rohc@ietf.org'
> > Subject: RE: [rohc] ROHC-TCP, ack number compression
> >
> >
> >
> >
> > > > - the remote compressor (decompressor) has to store a history
> > > > of 'expected' ACK numbers (and the other end has to know how
> > > > long this is!) [this is single biggest complexity issue, for me];
> > >
> > > Long in what regard? I have not thought much about this
> > yet, just get
> > > the feeling we will have to do so. As Carsten noted, we will have to
> > > be robust to losses, with e.g. a generation number. How much will we
> > > save in the end?
> > >
> >
> > I hadn't thought about it much at the time, but have done a bit more
> > thinking now (and hopefully untangled my brain in the process!)
> >
> > So... the basic observation is that (for many links) a packet
> > sent from
> > A -> B with msn_A, seqno_A, and payload_size_A can be used to
> > derive an
> > acknowledgement value in the reverse direction.  That is,
> > there may be a
> > packet with ackno_B == (seqno_A + payload_size_A).
> >
> > First of all, the compressor at A must indicate to B that it
> > is storing
> > tuples (msn_A, seqno_A + payload_size_A) and that B may use these to
> > compress ack numbers.  A will store these tuples in a list of bounded
> > size.  (There isn't a 'generation number' per se -- we use
> > the msn as the
> > index).
> >
> > B, on correct decompression, maintains its own list (assuming that it
> > wants to do this -- it should be possible for B to signal A that it
> > doesn't want to, so A can avoid storing the tuples
> > unnecessarily).  When B
> > wants to compress an ack value, it looks it up in the list.
> > If it finds a
> > match, then it needs to signal (robustly) the value of msn_A to A.
> >
> > This, though, is just a general initialise value + LSB
> > encoding problem.
> > (i.e. B may encode msn_a as irregular in the first n packets it sends,
> > followed by suitable LSB encoding)
> >
> > To manage the length of the list of tuples, B will only ever refer to
> > msn_a values that stay the same or increase.  So, for
> > example, once B has
> > referenced msn_A of 238, it will never refer to an msn_A <
> > 238; so A can
> > discard these from its history.  A, in its turn, needs to be able to
> > signal an error if it would ever overflow its tuple-storage
> > (i.e. it would
> > have to discard something that B believes to be available for
> > reference).
> > Each tuple is <= 8 octets [depending upon how much msn is kept], so
> > storage shouldn't be a major issue...
> >
> > It clearly has to be optional at both ends to do this.  If
> > A's storage is
> > insufficent for a link, it will discover this (by overflowing
> > its buffer);
> > if B's storage is insufficient it will realise (by not being
> > able to find
> > ack numbers in its history).
> >
> > In terms of saving, if we expect an ack ratio of 2, then every other
> > packet in the forward direction will be referenced (and the typical
> > 'interval' in msn_A is 2, rather than 1400+ for the actual
> > ackno).  This
> > is quite a saving.
> >
> > Retransmissions may cause some inefficiency (and I haven't
> > thought through
> > all of the cases yet), but I *think* only where multiple,
> > non-contiguous
> > packets are lost.
> >
> > It sort of feels like it ought to work, in a fairly simple way.  But I
> > might just be missing something glaringly obvious :-)
> >
> > Cheers,
> >
> > Mark.
> >
> >
> > --
> >
> > Visit our website at www.roke.co.uk
> >
> > Roke Manor Research Ltd, Roke Manor, Romsey, Hampshire SO51 0ZN, UK.
> >
> > 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.
> >
>

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


From rohc-bounces@ietf.org  Mon Nov 22 08:45:19 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29102
	for <rohc-web-archive@ietf.org>; Mon, 22 Nov 2004 08:45:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWEYp-0004U7-5X
	for rohc-web-archive@ietf.org; Mon, 22 Nov 2004 08:48:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWESI-0001n1-Sh; Mon, 22 Nov 2004 08:42:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWEQe-0001PU-MP
	for rohc@megatron.ietf.org; Mon, 22 Nov 2004 08:40:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28891
	for <rohc@ietf.org>; Mon, 22 Nov 2004 08:40:27 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWEU7-0004DM-31
	for rohc@ietf.org; Mon, 22 Nov 2004 08:44:03 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FH5Y1>; Mon, 22 Nov 2004 13:41:26 -0000
Received: from mjw-pc.roke.co.uk ([193.118.194.159]) by rsys002a.roke.co.uk
	with SMTP (Microsoft Exchange Internet Mail Service Version
	5.5.2657.72) id V2Q3R5BY; Mon, 22 Nov 2004 13:41:29 -0000
From: "West, Mark" <mark.a.west@roke.co.uk>
To: Kristofer Sandlund <kristofer.sandlund@effnet.com>
Date: Mon, 22 Nov 2004 13:39:52 +0000 (GMT)
X-X-Sender: maw@mjw-pc.roke.co.uk
Subject: Re: [rohc] ROHC-TCP, ack number compression
In-Reply-To: <41A1E260.3080304@effnet.com>
Message-ID: <Pine.LNX.4.44.0411221330510.32526-100000@mjw-pc.roke.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: "'rohc@ietf.org'" <rohc@ietf.org>,
        "Lars-Erik Jonsson \(LU/EAB\)" <lars-erik.jonsson@ericsson.com>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64


Hi Kristofer,

>
> This seems like a really complex scheme. Wouldn't explicit signaling of
> ACK_stride be a simpler and _almost_ as efficient a solution to this? Then, the
> decompressor at B could infer this value with or without the help of the
> co-located compressor without the spec having to go into this messy area.
>

I don't feel that this is particularly complex (but that may just be me!)

The problem with explicit signaling is that (i) you have to take the
overhead of signalling it; and (ii) if you simplify this signalling (to a
small number of powers-of-two, for example) you reduce the efficacy of the
scaling.

However, if no-one feels that reverse-path compression of acks is worth
the effort, then I guess we don't do it...  I just want to make sure that
we discuss it!

> With the scheme you suggest, compressor B has to "(robustly) signal msn_a to A",
> so why not send an explicit scale value instead? If the compressor at B is
> implemented to use the co-located decompressor's info, it should seldom have to
> send the SEQ_scale more than once and manage scaling on "many" packets. Then we
> also get out of having to have some feature negotiation (or feature rejection as
> you suggest).
>

note that the 'robust signalling' is no different from anything else that
we do.  And, in the main, it reduces to signalling a 'packet index' rather
than a 'byte index', which is less prone to variability.

And I don't think it's a complex 'negotiation': the compressor *does* need
to signal that it is storing ack numbers (in order for the other end-point
to know that it can use them).  If there's a way for the peer to say, 'I'm
not going to use them' it would potentially optimise storage needs, but it
doesn't affect the correctness/interoperability.

My view is also that explicit scaling will need to be sent relatively
regularly (assuming that it's a large enough value to give a sensible
reduction).  Which certainly doesn't mean that it isn't worth the effort!

Comments?

Cheers,

Mark.


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


From rohc-bounces@ietf.org  Mon Nov 22 08:58:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00104
	for <rohc-web-archive@ietf.org>; Mon, 22 Nov 2004 08:58:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWElB-00058l-Gb
	for rohc-web-archive@ietf.org; Mon, 22 Nov 2004 09:01:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWEfz-0003gC-9X; Mon, 22 Nov 2004 08:56:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWEeK-0003RA-UU
	for rohc@megatron.ietf.org; Mon, 22 Nov 2004 08:54:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29826
	for <rohc@ietf.org>; Mon, 22 Nov 2004 08:54:35 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWEhd-0004wz-1C
	for rohc@ietf.org; Mon, 22 Nov 2004 08:58:12 -0500
Received: from esealmw142.al.sw.ericsson.se ([153.88.254.119])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAMDsPR2011047 for <rohc@ietf.org>; Mon, 22 Nov 2004 14:54:25 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw142.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 22 Nov 2004 14:54:24 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <WRVYDJP3>; Mon, 22 Nov 2004 14:54:24 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E994F@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'West, Mark'" <mark.a.west@roke.co.uk>
Subject: RE: [rohc] ROHC-TCP, ack number compression
Date: Mon, 22 Nov 2004 14:54:20 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="ISO-8859-1"
X-OriginalArrivalTime: 22 Nov 2004 13:54:24.0952 (UTC)
	FILETIME=[C6A5EB80:01C4D09A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: "'rohc@ietf.org'" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d

> Summary:
> 
> - uncompressed ack           : 32 bits
> - 'vanilla' ack compression  : 15 bits
> - bi-directional compression :  4 bits
> - implicit ack stride        : ?? bits
> - explicit ack stride        : 10 bits ?

Mark,

Your discussions are reasonable, and my conclusion from
this is that the extra savings we can get from bi-dir
compression is less than an octet, and that is in the
case where the pre-assumptions for bi-directional
compression are met. If we then consider that the ack
field is only one part of the whole story, where we
actually look at the complete IP/TCP header, I do not
see that it is worth the conceptual complexity cost.

The reasons for me opposing bidirectional compression
are clearly based on two aspects, the fact that I do
not like the concept in principal (which is for sure an
argument that can't easily be measured in numbers =),
and my conclusion that the gain would not be 
"significant" (i.e. another parameter that is clearly
a matter of subjective "feelings") compared to the cost.
Previous experience from doing fancy optimizations
tells me we should be really careful, but I do not have
any additional detail arguments to bring at this point.

/L-E




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


From rohc-bounces@ietf.org  Mon Nov 22 09:19:33 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01729
	for <rohc-web-archive@ietf.org>; Mon, 22 Nov 2004 09:19:33 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWF5w-0006Fs-BA
	for rohc-web-archive@ietf.org; Mon, 22 Nov 2004 09:23:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWEyx-0006EM-DD; Mon, 22 Nov 2004 09:15:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWEuq-0005TQ-Pg
	for rohc@megatron.ietf.org; Mon, 22 Nov 2004 09:11:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01045
	for <rohc@ietf.org>; Mon, 22 Nov 2004 09:11:39 -0500 (EST)
Received: from [194.237.235.30] (helo=effnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWEyJ-0005pH-8F
	for rohc@ietf.org; Mon, 22 Nov 2004 09:15:15 -0500
Received: from effnet.com (c-b97c71d5.04-205-6c756c1.cust.bredbandsbolaget.se
	[213.113.124.185]) (authenticated bits=0)
	by effnet.com (8.12.3/8.12.3) with ESMTP id iAMDAeLh003428
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Mon, 22 Nov 2004 14:10:41 +0100
Message-ID: <41A1F43E.3040702@effnet.com>
Date: Mon, 22 Nov 2004 15:14:22 +0100
From: Kristofer Sandlund <kristofer.sandlund@effnet.com>
Organization: Effnet
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "West, Mark" <mark.a.west@roke.co.uk>
Subject: Re: [rohc] TCP sequence number encoding
References: <3F2E01E1D7B04F4EBEC92D3FA324D8806C4160-100000@rsys004a.roke.co.uk>
In-Reply-To: <3F2E01E1D7B04F4EBEC92D3FA324D8806C4160-100000@rsys004a.roke.co.uk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit
Cc: rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit

Hi Mark,

I am not a friend of partially-context-updating packets after the 
UO-1-ID-ext3-packet fiasco in 3095, so I'm going to be sceptic about this.

I agree with the general problem description that it would be nice to let 
backward jumps somehow be non-updating, but how big is the gain really?

Let's say the backwards jump is X*payload size, then we have to send log2(X) 
bits for this jump, and if we update the context, the next packet is likely to 
be (X+1)*payload size, meaning we'll have to send log2(X+1) bits (i.e. probably 
one more bit than for the backwards jump).

If we did not update the context, we could send just "minimum number of bits of 
SEQ in one of our packet formats" (k_min) in the forward jump. From the packet 
formats have have now, I doubt that this will actually gain us any bits, since I 
guess that for most cases log2(X+1) will be equal to k_min. Or is my math off?

And if the gain is large enough, I need to understand _how_ you mean that this 
should work.
Do you wish to add a couple of new packet formats for non-updating SEQ or are 
you saying that "every time the decompressor receives a sequence number located 
to the 'left of the reference' in the interpretation interval, the context 
should not be updated with this value"? If the latter, will things such as 
reordering cause problems?

Also, could this cause inefficiency on streams where both SEQ and ACK change? 
(do we have to send the SEQ in ACK-only changes if this occurs right after a 
non-updating SEQ change?)

/Kristofer Sandlund, Effnet AB

West, Mark wrote:
> Hi all,
> 
> Having rambled on enough about ack numbers, here are some thoughts about
> sequence number encoding...
> 
> In general, sequence numbers increase (this should not come as a great
> surprise to anyone); but we obviously have to handle retransmissions.
> 
> The point is that I would expect retransmissions to involve a small number
> of packets deviating from the general trend of increasing.  In that case,
> it may be preferable for the backward jumps to not update the context at
> the decompressor.  If they *do* update the context, then when the
> retransmission has completed and the sequence number picks up its general
> increase, we have to count the current high water-mark + the
> retransmission in the LSB window.
> 
> On the assumption that the compressor is seeing all of the traffic (ok,
> there are scenarios where this isn't the case -- we can't rely upon it),
> the compressor may be able to work out whether it's expecting single or
> multiple packet retransmits and manage context updating accordingly.
> 
> I don't know how significant this is in terms of the overall efficiency
> gain (if any!), but thought that it was an issue that we ought to consider
> and agree on; even if we're happy to leave the formats as they are...
> 
> Cheers,
> 
> Mark.
> 
> --
> Mark A. West, Senior Consultant Engineer
> Roke Manor Research Ltd., Romsey, Hants.  SO51 0ZN
> Phone +44 (0)1794 833311   Fax  +44 (0)1794 833433
> 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc

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


From rohc-bounces@ietf.org  Mon Nov 22 10:15:04 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06550
	for <rohc-web-archive@ietf.org>; Mon, 22 Nov 2004 10:15:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWFxg-0000nM-Rp
	for rohc-web-archive@ietf.org; Mon, 22 Nov 2004 10:18:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWFqQ-0003mm-Nx; Mon, 22 Nov 2004 10:11:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWFj3-0000gq-Iq
	for rohc@megatron.ietf.org; Mon, 22 Nov 2004 10:03:33 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04904
	for <rohc@ietf.org>; Mon, 22 Nov 2004 10:03:31 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWFmW-0000CT-KT
	for rohc@ietf.org; Mon, 22 Nov 2004 10:07:09 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iAMF3Ita015836; Mon, 22 Nov 2004 16:03:19 +0100 (MET)
In-Reply-To: <Pine.LNX.4.44.0411221330510.32526-100000@mjw-pc.roke.co.uk>
References: <Pine.LNX.4.44.0411221330510.32526-100000@mjw-pc.roke.co.uk>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <A3EDEBD4-3C97-11D9-811E-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] ROHC-TCP, ack number compression
Date: Mon, 22 Nov 2004 16:03:17 +0100
To: "West, Mark" <mark.a.west@roke.co.uk>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, "'rohc@ietf.org'" <rohc@ietf.org>,
        Kristofer Sandlund <kristofer.sandlund@effnet.com>,
        "Lars-Erik Jonsson \(LU/EAB\)" <lars-erik.jonsson@ericsson.com>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit

On Nov 22 2004, at 14:39 Uhr, West, Mark wrote:

> And I don't think it's a complex 'negotiation': the compressor *does* 
> need
> to signal that it is storing ack numbers

Also, we need some way to bind the forward and reverse channels, as 
well as the CIDs.
This may be interesting on some channels.
(There was a reason we did the state ID dance for SigComp...)

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Mon Nov 22 10:25:25 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07873
	for <rohc-web-archive@ietf.org>; Mon, 22 Nov 2004 10:25:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWG7e-0001IZ-O6
	for rohc-web-archive@ietf.org; Mon, 22 Nov 2004 10:29:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWFs2-0004kA-5k; Mon, 22 Nov 2004 10:12:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWFoW-0002yK-SF
	for rohc@megatron.ietf.org; Mon, 22 Nov 2004 10:09:12 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05816
	for <rohc@ietf.org>; Mon, 22 Nov 2004 10:09:11 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWFry-0000Uj-WF
	for rohc@ietf.org; Mon, 22 Nov 2004 10:12:48 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iAMF93kD018791; Mon, 22 Nov 2004 16:09:04 +0100 (MET)
In-Reply-To: <41A1F43E.3040702@effnet.com>
References: <3F2E01E1D7B04F4EBEC92D3FA324D8806C4160-100000@rsys004a.roke.co.uk>
	<41A1F43E.3040702@effnet.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <7211B61D-3C98-11D9-811E-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] TCP sequence number encoding
Date: Mon, 22 Nov 2004 16:09:03 +0100
To: Kristofer Sandlund <kristofer.sandlund@effnet.com>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Cc: "West, Mark" <mark.a.west@roke.co.uk>, Carsten Bormann <cabo@tzi.org>,
        rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit

On Nov 22 2004, at 15:14 Uhr, Kristofer Sandlund wrote:

> I am not a friend of partially-context-updating packets after the 
> UO-1-ID-ext3-packet fiasco in 3095, so I'm going to be sceptic about 
> this.

I think that fiasco was a bit different -- using the same complex 
subheader format (ext3) in two different contexts with two different 
semantics clearly was a mistake.
We don't need to do that again.

My gut feeling is that the non-updating thing is interesting, but I'm 
not sure yet (I have the same questions you have).

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Mon Nov 22 19:40:27 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12388
	for <rohc-web-archive@ietf.org>; Mon, 22 Nov 2004 19:40:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWOmw-0000HE-VR
	for rohc-web-archive@ietf.org; Mon, 22 Nov 2004 19:44:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWOew-0002dq-Li; Mon, 22 Nov 2004 19:35:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWOcj-0001Ly-RK
	for rohc@megatron.ietf.org; Mon, 22 Nov 2004 19:33:38 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11372
	for <rohc@ietf.org>; Mon, 22 Nov 2004 19:33:35 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWOgI-0007qz-4Z
	for rohc@ietf.org; Mon, 22 Nov 2004 19:37:18 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0F2BS2>; Tue, 23 Nov 2004 00:34:30 -0000
Received: from mjw-pc.roke.co.uk ([193.118.194.159]) by rsys002a.roke.co.uk
	with SMTP (Microsoft Exchange Internet Mail Service Version
	5.5.2657.72) id V2Q3R54R; Tue, 23 Nov 2004 00:34:34 -0000
From: "West, Mark" <mark.a.west@roke.co.uk>
To: Kristofer Sandlund <kristofer.sandlund@effnet.com>
Date: Tue, 23 Nov 2004 00:32:57 +0000 (GMT)
X-X-Sender: maw@mjw-pc.roke.co.uk
Subject: Re: [rohc] TCP sequence number encoding
In-Reply-To: <41A1F43E.3040702@effnet.com>
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8806C4163-100000@rsys004a.roke.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Cc: rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f


Hi Kristofer,

>
> I am not a friend of partially-context-updating packets after the
> UO-1-ID-ext3-packet fiasco in 3095, so I'm going to be sceptic about this.

I admit that this was very much in my mind when thinking about this :-)
However, I would suggest [I think agreeing with Carsten] that the idea of
non-context updating things need not unleash the full horror of 3095...

... if you want to, of course, why not just make the whole packet
non-context updating?!

>
> I agree with the general problem description that it would be nice to let
> backward jumps somehow be non-updating, but how big is the gain really?
>

That's the $64000 question.  And I don't know.

> Let's say the backwards jump is X*payload size, then we have to send log2(X)
> bits for this jump, and if we update the context, the next packet is likely to
> be (X+1)*payload size, meaning we'll have to send log2(X+1) bits (i.e. probably
> one more bit than for the backwards jump).
>

Do you really mean log2(X) or log2(X*payload_size)..?  (i.e. this may
depend upon whether or not SEQ is being scaled at the point at which
retransmission is signalled)

I haven't looked (I confess) at possibly values for X (this is probably a
non-trivial question).  Let's assume, though, that a retransmission
happens based on 3 dupacks.  Then (taking an artificially small MSS for
simplicity of example) we might see a sequence of SEQ:
	1000 2000 4000 5000 6000 3000 7000 8000 9000 10000 11000...

If we assume robustness against a degree of loss and re-ordering that is
based on 3-bits of information, and a history of 3 packets at the
compressor then we have, in terms of [best] bit-costs:
	15   15   15   15   15   15   15   16   16   15    15

[using unscaled SEQ values, and assuming that the LSB window is optimally
aligned]

On this basis, yes, it is true -- all that the non-context updating
approach saves is (conceptually) 1 bit from the '8000' and '9000' packets.



> If we did not update the context, we could send just "minimum number of bits of
> SEQ in one of our packet formats" (k_min) in the forward jump. From the packet
> formats have have now, I doubt that this will actually gain us any bits, since I
> guess that for most cases log2(X+1) will be equal to k_min. Or is my math off?
>
> And if the gain is large enough, I need to understand _how_ you mean that this
> should work.
> Do you wish to add a couple of new packet formats for non-updating SEQ or are
> you saying that "every time the decompressor receives a sequence number located
> to the 'left of the reference' in the interpretation interval, the context
> should not be updated with this value"? If the latter, will things such as
> reordering cause problems?
>

I doubt that your math is off...

One thing that has occurred to me, though, in this discussion is how hard
it is to assess the benefit (or lack thereof) in any particular scheme.
We talk about 'saving a bit' or 'costing a bit' and whether or not this
matters.  I don't think that it's that simple: if I can save 1 bit of SEQ,
4 bits of ACK, and 1 bit of IP ID then that's 7 bits and, if I can find an
appropriate indicator, then maybe I can shave a byte off of a compressed
packet format...

I agree wholeheartedly with the dictum of not spending 80% of the effort
to get 20% of the compression gain.  But saying 'it's only 2 bits of
saving' needs to be set in the context of (i) how that compares to other
means of compressing the field; and (ii) what actual impact this has on
the average compressed packet size -- in some cases, saving a single bit
could translate into a byte saved from a packet format.

Anway, I think that, if this were to be done, then it would have to be
done explicitly (by packet format or some other indicator bit).


> Also, could this cause inefficiency on streams where both SEQ and ACK change?
> (do we have to send the SEQ in ACK-only changes if this occurs right after a
> non-updating SEQ change?)
>

I'm not sure that I understand this point.  If we have a window of n
packets (i.e. sending updates n times for robustness), then a change in
SEQ will impact the next n packets (n can be truncated through acks, of
course)..?  The only case (I think?!) where non-updating SEQ has any
effect is where, after the retransmission, SEQ reverts to a stable value
(i.e. has been sending a bunch of acks), in which case
non-context-updating is better.  But I may be missing the point...

Cheers,

Mark.


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


From rohc-bounces@ietf.org  Mon Nov 22 19:44:15 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12694
	for <rohc-web-archive@ietf.org>; Mon, 22 Nov 2004 19:44:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWOqc-000117-H6
	for rohc-web-archive@ietf.org; Mon, 22 Nov 2004 19:47:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWOlY-000491-CU; Mon, 22 Nov 2004 19:42:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWOgv-0003DT-Po
	for rohc@megatron.ietf.org; Mon, 22 Nov 2004 19:37:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12001
	for <rohc@ietf.org>; Mon, 22 Nov 2004 19:37:54 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWOkT-0008Jc-D5
	for rohc@ietf.org; Mon, 22 Nov 2004 19:41:38 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0F2BT2>; Tue, 23 Nov 2004 00:38:55 -0000
Received: from mjw-pc.roke.co.uk ([193.118.194.159]) by rsys002a.roke.co.uk
	with SMTP (Microsoft Exchange Internet Mail Service Version
	5.5.2657.72) id V2Q3R54V; Tue, 23 Nov 2004 00:38:58 -0000
From: "West, Mark" <mark.a.west@roke.co.uk>
To: Carsten Bormann <cabo@tzi.org>
Date: Tue, 23 Nov 2004 00:37:20 +0000 (GMT)
X-X-Sender: maw@mjw-pc.roke.co.uk
Subject: Re: [rohc] ROHC-TCP, ack number compression
In-Reply-To: <A3EDEBD4-3C97-11D9-811E-000A95DC4DB6@tzi.org>
Message-ID: <Pine.LNX.4.44.0411230034030.2177-100000@mjw-pc.roke.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: "'rohc@ietf.org'" <rohc@ietf.org>,
        Kristofer Sandlund <kristofer.sandlund@effnet.com>,
        "Lars-Erik Jonsson \(LU/EAB\)" <lars-erik.jonsson@ericsson.com>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22


> > And I don't think it's a complex 'negotiation': the compressor *does*
> > need
> > to signal that it is storing ack numbers
>
> Also, we need some way to bind the forward and reverse channels, as
> well as the CIDs.

True -- something that I had managed to ignore... :-)

> This may be interesting on some channels.
> (There was a reason we did the state ID dance for SigComp...)
>

Good point: I'd managed to overlook flow separation issues (for example).
But do you really think that this is as messy as SigComp..?  We have a
little more control over the endpoints.  And so I don't think that the
SigComp state model is directly applicable.  (But I've still probably been
guilty of over simplifying...)

Cheers,

Mark.

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


From rohc-bounces@ietf.org  Tue Nov 23 02:42:53 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09639
	for <rohc-web-archive@ietf.org>; Tue, 23 Nov 2004 02:42:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWVNm-00051k-TK
	for rohc-web-archive@ietf.org; Tue, 23 Nov 2004 02:46:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWVFn-0003bS-I6; Tue, 23 Nov 2004 02:38:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWVDV-000364-83
	for rohc@megatron.ietf.org; Tue, 23 Nov 2004 02:36:01 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09250
	for <rohc@ietf.org>; Tue, 23 Nov 2004 02:35:57 -0500 (EST)
Received: from [194.237.235.30] (helo=effnet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWVH4-0004EM-Ul
	for rohc@ietf.org; Tue, 23 Nov 2004 02:39:43 -0500
Received: from effnet.com (c-b97c71d5.04-205-6c756c1.cust.bredbandsbolaget.se
	[213.113.124.185]) (authenticated bits=0)
	by effnet.com (8.12.3/8.12.3) with ESMTP id iAN6YsLh006455
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Tue, 23 Nov 2004 07:34:59 +0100
Message-ID: <41A2E907.3060500@effnet.com>
Date: Tue, 23 Nov 2004 08:38:47 +0100
From: Kristofer Sandlund <kristofer.sandlund@effnet.com>
Organization: Effnet
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "West, Mark" <mark.a.west@roke.co.uk>
Subject: Re: [rohc] TCP sequence number encoding
References: <3F2E01E1D7B04F4EBEC92D3FA324D8806C4163-100000@rsys004a.roke.co.uk>
In-Reply-To: <3F2E01E1D7B04F4EBEC92D3FA324D8806C4163-100000@rsys004a.roke.co.uk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Content-Transfer-Encoding: 7bit
Cc: rohc@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Content-Transfer-Encoding: 7bit

> 
>>Let's say the backwards jump is X*payload size, then we have to send log2(X)
>>bits for this jump, and if we update the context, the next packet is likely to
>>be (X+1)*payload size, meaning we'll have to send log2(X+1) bits (i.e. probably
>>one more bit than for the backwards jump).
>>
> 
> 
> Do you really mean log2(X) or log2(X*payload_size)..?  (i.e. this may
> depend upon whether or not SEQ is being scaled at the point at which
> retransmission is signalled)
> 
> I haven't looked (I confess) at possibly values for X (this is probably a
> non-trivial question).  Let's assume, though, that a retransmission
> happens based on 3 dupacks.  Then (taking an artificially small MSS for
> simplicity of example) we might see a sequence of SEQ:
> 	1000 2000 4000 5000 6000 3000 7000 8000 9000 10000 11000...
> 
> If we assume robustness against a degree of loss and re-ordering that is
> based on 3-bits of information, and a history of 3 packets at the
> compressor then we have, in terms of [best] bit-costs:
> 	15   15   15   15   15   15   15   16   16   15    15
> 
> [using unscaled SEQ values, and assuming that the LSB window is optimally
> aligned]
> 
> On this basis, yes, it is true -- all that the non-context updating
> approach saves is (conceptually) 1 bit from the '8000' and '9000' packets.
> 

So, for now, we see an extremely marginal win on this. And this win will only 
happen if we have one packet format where the seq-bits exactly matched 15 in the 
example above. So, unless we can find an example where this seems to make more 
sense, I'd vote for having all packets update context.

> 
>>If we did not update the context, we could send just "minimum number of bits of
>>SEQ in one of our packet formats" (k_min) in the forward jump. From the packet
>>formats have have now, I doubt that this will actually gain us any bits, since I
>>guess that for most cases log2(X+1) will be equal to k_min. Or is my math off?
>>
>>And if the gain is large enough, I need to understand _how_ you mean that this
>>should work.
>>Do you wish to add a couple of new packet formats for non-updating SEQ or are
>>you saying that "every time the decompressor receives a sequence number located
>>to the 'left of the reference' in the interpretation interval, the context
>>should not be updated with this value"? If the latter, will things such as
>>reordering cause problems?
>>
> 
> 
> I doubt that your math is off...
> 
> One thing that has occurred to me, though, in this discussion is how hard
> it is to assess the benefit (or lack thereof) in any particular scheme.
> We talk about 'saving a bit' or 'costing a bit' and whether or not this
> matters.  I don't think that it's that simple: if I can save 1 bit of SEQ,
> 4 bits of ACK, and 1 bit of IP ID then that's 7 bits and, if I can find an
> appropriate indicator, then maybe I can shave a byte off of a compressed
> packet format...

Yes, I agree that we cannot just look at each issue separately. But with that 
kind of discussion, we can at least weigh "bits gained vs complexity" for each 
solution so that we more easily can decide which solutions we should spend most 
effort on.

> 
> I agree wholeheartedly with the dictum of not spending 80% of the effort
> to get 20% of the compression gain.  But saying 'it's only 2 bits of
> saving' needs to be set in the context of (i) how that compares to other
> means of compressing the field; and (ii) what actual impact this has on
> the average compressed packet size -- in some cases, saving a single bit
> could translate into a byte saved from a packet format.
> 
> Anway, I think that, if this were to be done, then it would have to be
> done explicitly (by packet format or some other indicator bit).
> 

So, just to be picky: if we add an indicator bit to a current packet format, we 
_seem_ to lose the only bit that we saved above, and if we were to add new 
packet formats, then I guess we'd have to add up to four new packet formats 
(sequential-unscaled, sequential-scaled, random-unscaled, random-scaled), and to 
motivate that I think we would need to see a bigger gain.

> 
> 
>>Also, could this cause inefficiency on streams where both SEQ and ACK change?
>>(do we have to send the SEQ in ACK-only changes if this occurs right after a
>>non-updating SEQ change?)
>>
> 
> 
> I'm not sure that I understand this point.  If we have a window of n
> packets (i.e. sending updates n times for robustness), then a change in
> SEQ will impact the next n packets (n can be truncated through acks, of
> course)..?  The only case (I think?!) where non-updating SEQ has any
> effect is where, after the retransmission, SEQ reverts to a stable value
> (i.e. has been sending a bunch of acks), in which case
> non-context-updating is better.  But I may be missing the point...
> 

I think I confused even myself with that point, so let's leave it at that :)

BR,
	Kristofer

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


From rohc-bounces@ietf.org  Tue Nov 23 06:28:38 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28653
	for <rohc-web-archive@ietf.org>; Tue, 23 Nov 2004 06:28:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CWYu9-0000jb-RQ
	for rohc-web-archive@ietf.org; Tue, 23 Nov 2004 06:32:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWYoO-0007ba-6o; Tue, 23 Nov 2004 06:26:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWYly-0007Cc-HJ
	for rohc@megatron.ietf.org; Tue, 23 Nov 2004 06:23:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28330
	for <rohc@ietf.org>; Tue, 23 Nov 2004 06:23:47 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWYpZ-0000J8-B5
	for rohc@ietf.org; Tue, 23 Nov 2004 06:27:37 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iANBNjvD008891
	for <rohc@ietf.org>; Tue, 23 Nov 2004 12:23:45 +0100 (MET)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 23 Nov 2004 12:23:43 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <WRVYK83G>; Tue, 23 Nov 2004 12:23:43 +0100
Message-ID: <A943FD84BD9ED41193460008C79180500C57065F@ESEALNT419.al.sw.ericsson.se>
From: "Ghyslain Pelletier (LU/EAB)" <ghyslain.pelletier@ericsson.com>
To: "'West, Mark'" <mark.a.west@roke.co.uk>, Carsten Bormann
	 <cabo@tzi.org>
Subject: RE: [rohc] ROHC-TCP, ack number compression
Date: Tue, 23 Nov 2004 12:23:39 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="ISO-8859-1"
X-OriginalArrivalTime: 23 Nov 2004 11:23:43.0693 (UTC)
	FILETIME=[E40D07D0:01C4D14E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: "'rohc@ietf.org'" <rohc@ietf.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8

Hi all,

At first I thought it could be good to consider some kind of bidirectional compression, and thanks for information that was sent regarding this.

However, it now seems to me that this thread is converging towards keeping ack compression as it is.
After reading the thread carefully, this is at least what I am in favor of right now.

I.e. let's keep 'vanilla' ack compression as it currently is.

/Ghyslain

> -----Original Message-----
> From: rohc-bounces@ietf.org [mailto:rohc-bounces@ietf.org]On Behalf Of
> West, Mark
> Sent: den 23 november 2004 01:37
> To: Carsten Bormann
> Cc: 'rohc@ietf.org'; Kristofer Sandlund; Lars-Erik Jonsson (LU/EAB)
> Subject: Re: [rohc] ROHC-TCP, ack number compression
> 
> 
> 
> > > And I don't think it's a complex 'negotiation': the 
> compressor *does*
> > > need
> > > to signal that it is storing ack numbers
> >
> > Also, we need some way to bind the forward and reverse channels, as
> > well as the CIDs.
> 
> True -- something that I had managed to ignore... :-)
> 
> > This may be interesting on some channels.
> > (There was a reason we did the state ID dance for SigComp...)
> >
> 
> Good point: I'd managed to overlook flow separation issues 
> (for example).
> But do you really think that this is as messy as SigComp..?  We have a
> little more control over the endpoints.  And so I don't think that the
> SigComp state model is directly applicable.  (But I've still 
> probably been
> guilty of over simplifying...)
> 
> Cheers,
> 
> Mark.
> 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
> 

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


From rohc-bounces@ietf.org  Wed Nov 24 13:18:00 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17589
	for <rohc-web-archive@ietf.org>; Wed, 24 Nov 2004 13:18:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CX1mH-0002Jc-Qj
	for rohc-web-archive@ietf.org; Wed, 24 Nov 2004 13:22:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CX1gf-0007J0-DN; Wed, 24 Nov 2004 13:16:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CX1Rv-0002oQ-Rm
	for rohc@megatron.ietf.org; Wed, 24 Nov 2004 13:01:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16364
	for <rohc@ietf.org>; Wed, 24 Nov 2004 13:01:00 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CX1Vq-0001kH-En
	for rohc@ietf.org; Wed, 24 Nov 2004 13:05:06 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0F2584>; Wed, 24 Nov 2004 18:02:00 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8803D5A05@rsys004a.roke.co.uk>
From: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
To: rohc@ietf.org
Date: Wed, 24 Nov 2004 18:01:55 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Subject: [rohc] SigComp implementer's guide
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5

Hi All,

Since the last version I think it has been agreed that the following should
be added to the implementer's guide:

The shared-mode/minimum priority issue (text already discussed on the list)
SigComp shim uncompressed bytecode
Discussion of the frequency of state identifier clashes (as presented by
Mark in San Diego)
Note about the minor bugs in 3485 (incorrect priorities).

Are there any other issues that I've missed?

As these 4 actually amount to a fair amount of text, I won't include it here
but have uploaded a proposed version of the draft to
<http://sigcomp.srmr.co.uk/~ahs/draft-ietf-rohc-sigcomp-impl-guide-04.txt>.
All comments and alteration suggestions to the text are appreciated.  In
particular, the sections above are  5.3, 11, 7 and 12, respectively.

Best regards,

Abbie


Abbie Surtees
Senior Engineer
Roke Manor Research Ltd
Old Salisbury Lane
Romsey, SO51 0ZN
Tel:   +44 (0) 1794 833131


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


From rohc-bounces@ietf.org  Wed Nov 24 23:29:04 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08725
	for <rohc-web-archive@ietf.org>; Wed, 24 Nov 2004 23:29:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CXBJj-0007YU-It
	for rohc-web-archive@ietf.org; Wed, 24 Nov 2004 23:33:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CXBEP-0006Xw-Nq; Wed, 24 Nov 2004 23:27:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CXBDN-0005tb-22; Wed, 24 Nov 2004 23:26:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08558;
	Wed, 24 Nov 2004 23:26:38 -0500 (EST)
From: hkgupta@hssworld.com
Received: from spark.hss.co.in ([203.200.71.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CXBHM-0007U7-31; Wed, 24 Nov 2004 23:30:49 -0500
Received: from spark.hss.co.in (localhost [127.0.0.1])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iAP4N96n024636;
	Thu, 25 Nov 2004 09:53:09 +0530 (IST)
Received: from sandesh.hss.hns.com (sandesh [172.16.32.19])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iAP4N8xX024624;
	Thu, 25 Nov 2004 09:53:08 +0530 (IST)
In-Reply-To: <3F2E01E1D7B04F4EBEC92D3FA324D8803D5A05@rsys004a.roke.co.uk>
To: rohc@ietf.org, rohc-bounces@ietf.org
Cc: rohc@ietf.org, rohc-bounces@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OFFDD4CE7D.D4DBFACE-ON65256F57.0012EC68-65256F57.0018875F@hssworld.com>
Date: Thu, 25 Nov 2004 09:53:53 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26,
	2002) at 25/11/2004 10:13:31 AM,
	Serialize complete at 25/11/2004 10:13:31 AM
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Subject: [rohc] Problem in deflate code available at zlib.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0926958104=="
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027

This is a multipart message in MIME format.
--===============0926958104==
Content-Type: multipart/alternative;
	boundary="=_alternative 0018873D65256F57_="

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


Hi All,
        I have picked up deflate code from zlib.org. I have observed 
following problems in it.
              1.        I set the static dictionary before calling 
deflate. function calling sequence is
         deflateInit(&objZstream, 8);
         deflateSetDictionary(&objZstream, .................)
         deflate(&objZstream, Z_FINISH);

         The problem is that I get 6 extra characters in compressed 
packet. To get rid of the problem I remove first 6 characters from the 
compressed packet and send it to decompressor. Decompressor is able to 
decompress the compressed message only after removing first 6 characters.
 
           2.  while debugging using Valgrind tool I found that one 
function in deflate code is using un-initialized variable.

 I am suspecting that 1st problem might be because of 2nd problem.

 Please give me any pointer if any of you have faced this kind of problem.


Thanks
Harish

***********************  HSS-Private   ***********************

"Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain  privileged or 
confidential information and should not be circulated or used for any purpose other than for 
what it is intended. If you have received this message in error, please notify the originator 
immediately. If you are not the intended recipient, you are notified that you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
accepts no responsibility for loss or damage arising from the use of the information transmitted 
by this email including damage from virus."
--=_alternative 0018873D65256F57_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi All,</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; I
have picked up deflate code from zlib.org. I have observed following problems
in it.</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; 1. &nbsp; &nbsp; &nbsp; &nbsp;I set the static dictionary before
calling deflate. function calling sequence is</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;deflateInit(&amp;objZstream,
8);</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;deflateSetDictionary(&amp;objZstream,
.................)</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;deflate(&amp;objZstream,
Z_FINISH);</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;The
problem is that I get 6 extra characters in compressed packet. To get rid
of the problem I remove first 6 characters from the compressed packet and
send it to decompressor. Decompressor is able to decompress the compressed
message only after removing first 6 characters.</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2.
&nbsp;while debugging using Valgrind tool I found that one function in
deflate code is using un-initialized variable.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp;I am suspecting that 1st problem
might be because of 2nd problem.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp;Please give me any pointer if
any of you have faced this kind of problem.</font>
<br>
<br>
<br><font size=2 face="sans-serif">Thanks</font>
<br><font size=2 face="sans-serif">Harish<br>
<br>
*********************** &nbsp;HSS-Private &nbsp; ***********************</font>
<table><tr><td bgcolor=#ffffff><font color=#000000><pre>"Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain  privileged or 
confidential information and should not be circulated or used for any purpose other than for 
what it is intended. If you have received this message in error, please notify the originator 
immediately. If you are not the intended recipient, you are notified that you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
accepts no responsibility for loss or damage arising from the use of the information transmitted 
by this email including damage from virus."
</pre></font></td></tr></table>
--=_alternative 0018873D65256F57_=--


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

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

--===============0926958104==--



From rohc-bounces@ietf.org  Thu Nov 25 06:10:18 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29249
	for <rohc-web-archive@ietf.org>; Thu, 25 Nov 2004 06:10:18 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CXHZu-0000BK-KP
	for rohc-web-archive@ietf.org; Thu, 25 Nov 2004 06:14:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CXHUA-0006vh-Qd; Thu, 25 Nov 2004 06:08:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CXHTo-0006kp-BZ
	for rohc@megatron.ietf.org; Thu, 25 Nov 2004 06:08:04 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29152
	for <rohc@ietf.org>; Thu, 25 Nov 2004 06:08:01 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXHXh-00009E-UK
	for rohc@ietf.org; Thu, 25 Nov 2004 06:12:16 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAPB7ph5009767
	for <rohc@ietf.org>; Thu, 25 Nov 2004 12:07:51 +0100 (MET)
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 25 Nov 2004 12:07:51 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <WRVY0B3D>; Thu, 25 Nov 2004 12:07:51 +0100
Message-ID: <A943FD84BD9ED41193460008C7918050072E996F@ESEALNT419.al.sw.ericsson.se>
From: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>
To: "'rohc@ietf.org'" <rohc@ietf.org>
Date: Thu, 25 Nov 2004 12:07:41 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-OriginalArrivalTime: 25 Nov 2004 11:07:51.0733 (UTC)
	FILETIME=[0176F650:01C4D2DF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: quoted-printable
Subject: [rohc] The discussion on slope(s)
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: quoted-printable

ROHCers,

In Washington DC, we had a discussion about the 3095 slope
problem, which still is an open issue for the implementer's
guide to clarify, if we want to ensure interoperability. My
initial opinion was that the previous discussions on the list
indicated we would have to do a careful study of this to be
able to get consensus, and write a draft explaining both
operations (with and without implicit slopes). However, the
sense of the room I got was that we should not waste too
much effort on this, but actually declare implicit slopes as=20
not to be part of 3095, and in the implementer's guide just
point out the text parts of 3095 that caused this confusion
and clarify accordingly. Although I personally agree with
this approach and believe it is the only reasonable way to
go, I will not propose any text for the implementer's guide
before there is consensus to go with the proposed approach.

Therefore, I ask for opinions on this, more or less
elaborated. See it as a HUM, with possibility to provide
more details.=20

To find the previous ROHC list discussion on slopes, please
refer to the archives from March 17 to April 16 this year.

This is currently the only open issue for the implementer's
guide and I need your help to get this resolved.

Thanks!
/L-E

-----------------------------------
Lars-Erik Jonsson, M.Sc.
Senior Research Engineer
Wireless IP Optimizations
AWARE - Advanced Wireless Algorithm Research
Ericsson Research, Corporate Unit
Ericsson AB
Box 920, S-971 28 Lule=E5, Sweden
E-mail: lars-erik.jonsson@ericsson.com                      /"\
Phone: +46 8 404 29 61                                      \ /
Fax: +46 920 996 21               ASCII Ribbon Campaign      X
Home: +46 920 999 57           against HTML email & vCards  / \

My opinions are my personal opinions and should not be considered
as the opinions of my employer, if not explicitly stated.

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


From rohc-bounces@ietf.org  Thu Nov 25 06:56:39 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03947
	for <rohc-web-archive@ietf.org>; Thu, 25 Nov 2004 06:56:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CXIIm-0001Lh-4q
	for rohc-web-archive@ietf.org; Thu, 25 Nov 2004 07:00:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CXIC1-0000P5-23; Thu, 25 Nov 2004 06:53:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CXI7L-0007dS-LP
	for rohc@megatron.ietf.org; Thu, 25 Nov 2004 06:48:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01819
	for <rohc@ietf.org>; Thu, 25 Nov 2004 06:48:52 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXIBF-0000y3-Jf
	for rohc@ietf.org; Thu, 25 Nov 2004 06:53:08 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAPBmhh5018851
	for <rohc@ietf.org>; Thu, 25 Nov 2004 12:48:43 +0100 (MET)
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 25 Nov 2004 12:48:43 +0100
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <XRD50SXT>; Thu, 25 Nov 2004 12:48:36 +0100
Message-ID: <F005CD411D18D3119C8F00508B0874800DC404B1@ehubunt100.eth.ericsson.se>
From: "Lajos Zaccomer (IJ/ETH)" <lajos.zaccomer@ericsson.com>
To: "'Surtees, Abigail'" <abigail.surtees@roke.co.uk>, rohc@ietf.org
Subject: RE: [rohc] SigComp implementer's guide
Date: Thu, 25 Nov 2004 12:48:28 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 25 Nov 2004 11:48:43.0686 (UTC)
	FILETIME=[B6F14C60:01C4D2E4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a

Hi Abbie,

Could you please relocate the "nice sentence"? ("In cases where
   the behaviour of the application restricts the message flow ...") My only problem is that it looks as though it is connected with NACK, but it is definitely not.

br/Zacco

> -----Original Message-----
> From: rohc-bounces@ietf.org [mailto:rohc-bounces@ietf.org]On 
> Behalf Of Surtees, Abigail
> Sent: Wednesday, November 24, 2004 7:02 PM
> To: rohc@ietf.org
> Subject: [rohc] SigComp implementer's guide
> 
> 
> Hi All,
> 
> Since the last version I think it has been agreed that the 
> following should
> be added to the implementer's guide:
> 
> The shared-mode/minimum priority issue (text already 
> discussed on the list)
> SigComp shim uncompressed bytecode
> Discussion of the frequency of state identifier clashes (as 
> presented by
> Mark in San Diego)
> Note about the minor bugs in 3485 (incorrect priorities).
> 
> Are there any other issues that I've missed?
> 
> As these 4 actually amount to a fair amount of text, I won't 
> include it here
> but have uploaded a proposed version of the draft to
> <http://sigcomp.srmr.co.uk/~ahs/draft-ietf-rohc-sigcomp-impl-g
uide-04.txt>.
All comments and alteration suggestions to the text are appreciated.  In
particular, the sections above are  5.3, 11, 7 and 12, respectively.

Best regards,

Abbie


Abbie Surtees
Senior Engineer
Roke Manor Research Ltd
Old Salisbury Lane
Romsey, SO51 0ZN
Tel:   +44 (0) 1794 833131


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

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


From rohc-bounces@ietf.org  Thu Nov 25 08:51:07 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12871
	for <rohc-web-archive@ietf.org>; Thu, 25 Nov 2004 08:51:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CXK5i-00044U-JU
	for rohc-web-archive@ietf.org; Thu, 25 Nov 2004 08:55:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CXJwp-0008H0-5I; Thu, 25 Nov 2004 08:46:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CXJtu-0007R6-01
	for rohc@megatron.ietf.org; Thu, 25 Nov 2004 08:43:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11990
	for <rohc@ietf.org>; Thu, 25 Nov 2004 08:43:08 -0500 (EST)
Received: from rsys001a.roke.co.uk ([193.118.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXJxy-0003pz-E9
	for rohc@ietf.org; Thu, 25 Nov 2004 08:47:22 -0500
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <TW0FJH2M>; Thu, 25 Nov 2004 13:44:02 -0000
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8803D5A17@rsys004a.roke.co.uk>
From: "Surtees, Abigail" <abigail.surtees@roke.co.uk>
To: "'Lajos Zaccomer (IJ/ETH)'" <lajos.zaccomer@ericsson.com>, rohc@ietf.org
Subject: RE: [rohc] SigComp implementer's guide
Date: Thu, 25 Nov 2004 13:43:59 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86

Hi Zacco,

This paragraph is the overall recommendations paragraph so I'd prefer to
keep the "nice sentence" in it.  However, I see that it could be interpreted
as relating to only the second sentence in the paragraph which is, as you
say, not the intention.  How about changing it slightly to the following?

"   Consequently, where NACK is not supported or for NACK averse
   compressors, the recommendation is that only one piece of minimum
   priority state should be present in a compartment at any one time.
   If both endpoints support NACK [3], then this recommendation may be
   relaxed, but implementers should think carefully about the
   consequences of creating multiple pieces of minimum priority state.
   In either case, if the behaviour of the application restricts the
   message flow, this fact could be exploited to allow safe creation of
   multiple minimum priority states; however, care must still be taken."


Best regards,

Abbie

> -----Original Message-----
> From: Lajos Zaccomer (IJ/ETH) [mailto:lajos.zaccomer@ericsson.com] 
> Sent: Thursday, November 25, 2004 11:48 AM
> To: Surtees, Abigail; rohc@ietf.org
> Subject: RE: [rohc] SigComp implementer's guide
> 
> 
> Hi Abbie,
> 
> Could you please relocate the "nice sentence"? ("In cases where
>    the behaviour of the application restricts the message 
> flow ...") My only problem is that it looks as though it is 
> connected with NACK, but it is definitely not.
> 
> br/Zacco
> 
> > -----Original Message-----
> > From: rohc-bounces@ietf.org [mailto:rohc-bounces@ietf.org]On 
> > Behalf Of Surtees, Abigail
> > Sent: Wednesday, November 24, 2004 7:02 PM
> > To: rohc@ietf.org
> > Subject: [rohc] SigComp implementer's guide
> > 
> > 
> > Hi All,
> > 
> > Since the last version I think it has been agreed that the 
> > following should
> > be added to the implementer's guide:
> > 
> > The shared-mode/minimum priority issue (text already 
> > discussed on the list)
> > SigComp shim uncompressed bytecode
> > Discussion of the frequency of state identifier clashes (as 
> > presented by
> > Mark in San Diego)
> > Note about the minor bugs in 3485 (incorrect priorities).
> > 
> > Are there any other issues that I've missed?
> > 
> > As these 4 actually amount to a fair amount of text, I won't 
> > include it here
> > but have uploaded a proposed version of the draft to
> > <http://sigcomp.srmr.co.uk/~ahs/draft-ietf-rohc-sigcomp-impl-g
> uide-04.txt>.
> All comments and alteration suggestions to the text are 
> appreciated.  In
> particular, the sections above are  5.3, 11, 7 and 12, respectively.
> 
> Best regards,
> 
> Abbie
> 
> 
> Abbie Surtees
> Senior Engineer
> Roke Manor Research Ltd
> Old Salisbury Lane
> Romsey, SO51 0ZN
> Tel:   +44 (0) 1794 833131
> 
> 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
> 

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


From rohc-bounces@ietf.org  Thu Nov 25 09:54:21 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17880
	for <rohc-web-archive@ietf.org>; Thu, 25 Nov 2004 09:54:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CXL4v-0005cK-D1
	for rohc-web-archive@ietf.org; Thu, 25 Nov 2004 09:58:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CXKsg-0007AL-Od; Thu, 25 Nov 2004 09:45:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CXKon-0005lA-QD
	for rohc@megatron.ietf.org; Thu, 25 Nov 2004 09:41:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17038
	for <rohc@ietf.org>; Thu, 25 Nov 2004 09:41:56 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXKst-0005LH-AA
	for rohc@ietf.org; Thu, 25 Nov 2004 09:46:11 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAPEfth5027592
	for <rohc@ietf.org>; Thu, 25 Nov 2004 15:41:55 +0100 (MET)
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 25 Nov 2004 15:41:55 +0100
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <XRD6A7HJ>; Thu, 25 Nov 2004 15:41:55 +0100
Message-ID: <F005CD411D18D3119C8F00508B0874800DC404BD@ehubunt100.eth.ericsson.se>
From: "Lajos Zaccomer (IJ/ETH)" <lajos.zaccomer@ericsson.com>
To: "'Surtees, Abigail'" <abigail.surtees@roke.co.uk>, rohc@ietf.org
Subject: RE: [rohc] SigComp implementer's guide
Date: Thu, 25 Nov 2004 15:41:53 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 25 Nov 2004 14:41:55.0624 (UTC)
	FILETIME=[E9053280:01C4D2FC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1

Hi Abbie,

Wonderful! Thanx.

Zacco

> -----Original Message-----
> From: Surtees, Abigail [mailto:abigail.surtees@roke.co.uk]
> Sent: Thursday, November 25, 2004 2:44 PM
> To: Lajos Zaccomer (IJ/ETH); rohc@ietf.org
> Subject: RE: [rohc] SigComp implementer's guide
> 
> 
> Hi Zacco,
> 
> This paragraph is the overall recommendations paragraph so 
> I'd prefer to
> keep the "nice sentence" in it.  However, I see that it could 
> be interpreted
> as relating to only the second sentence in the paragraph 
> which is, as you
> say, not the intention.  How about changing it slightly to 
> the following?
> 
> "   Consequently, where NACK is not supported or for NACK averse
>    compressors, the recommendation is that only one piece of minimum
>    priority state should be present in a compartment at any one time.
>    If both endpoints support NACK [3], then this recommendation may be
>    relaxed, but implementers should think carefully about the
>    consequences of creating multiple pieces of minimum priority state.
>    In either case, if the behaviour of the application restricts the
>    message flow, this fact could be exploited to allow safe 
> creation of
>    multiple minimum priority states; however, care must still 
> be taken."
> 
> 
> Best regards,
> 
> Abbie
> 
> > -----Original Message-----
> > From: Lajos Zaccomer (IJ/ETH) [mailto:lajos.zaccomer@ericsson.com] 
> > Sent: Thursday, November 25, 2004 11:48 AM
> > To: Surtees, Abigail; rohc@ietf.org
> > Subject: RE: [rohc] SigComp implementer's guide
> > 
> > 
> > Hi Abbie,
> > 
> > Could you please relocate the "nice sentence"? ("In cases where
> >    the behaviour of the application restricts the message 
> > flow ...") My only problem is that it looks as though it is 
> > connected with NACK, but it is definitely not.
> > 
> > br/Zacco
> > 
> > > -----Original Message-----
> > > From: rohc-bounces@ietf.org [mailto:rohc-bounces@ietf.org]On 
> > > Behalf Of Surtees, Abigail
> > > Sent: Wednesday, November 24, 2004 7:02 PM
> > > To: rohc@ietf.org
> > > Subject: [rohc] SigComp implementer's guide
> > > 
> > > 
> > > Hi All,
> > > 
> > > Since the last version I think it has been agreed that the 
> > > following should
> > > be added to the implementer's guide:
> > > 
> > > The shared-mode/minimum priority issue (text already 
> > > discussed on the list)
> > > SigComp shim uncompressed bytecode
> > > Discussion of the frequency of state identifier clashes (as 
> > > presented by
> > > Mark in San Diego)
> > > Note about the minor bugs in 3485 (incorrect priorities).
> > > 
> > > Are there any other issues that I've missed?
> > > 
> > > As these 4 actually amount to a fair amount of text, I won't 
> > > include it here
> > > but have uploaded a proposed version of the draft to
> > > <http://sigcomp.srmr.co.uk/~ahs/draft-ietf-rohc-sigcomp-impl-g
> > uide-04.txt>.
> > All comments and alteration suggestions to the text are 
> > appreciated.  In
> > particular, the sections above are  5.3, 11, 7 and 12, respectively.
> > 
> > Best regards,
> > 
> > Abbie
> > 
> > 
> > Abbie Surtees
> > Senior Engineer
> > Roke Manor Research Ltd
> > Old Salisbury Lane
> > Romsey, SO51 0ZN
> > Tel:   +44 (0) 1794 833131
> > 
> > 
> > _______________________________________________
> > Rohc mailing list
> > Rohc@ietf.org
> > https://www1.ietf.org/mailman/listinfo/rohc
> > 
> 
> -- 
> 
> Visit our website at www.roke.co.uk
> 
> Roke Manor Research Ltd, Roke Manor, Romsey, Hampshire SO51 0ZN, UK.
> 
> The information contained in this e-mail and any attachments 
> is proprietary 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.
> 

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


From rohc-bounces@ietf.org  Mon Nov 29 07:56:00 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15291
	for <rohc-web-archive@ietf.org>; Mon, 29 Nov 2004 07:56:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYl9N-0008Sm-8V
	for rohc-web-archive@ietf.org; Mon, 29 Nov 2004 08:01:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYkoK-0002ck-LC; Mon, 29 Nov 2004 07:39:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CXqy3-0004lK-5E
	for rohc@megatron.ietf.org; Fri, 26 Nov 2004 20:01:39 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14629
	for <rohc@ietf.org>; Fri, 26 Nov 2004 20:01:37 -0500 (EST)
Received: from outbound.mailhop.org ([63.208.196.171] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXr2Q-0008Eo-Hq
	for rohc@ietf.org; Fri, 26 Nov 2004 20:06:11 -0500
Received: from c-67-182-139-247.client.comcast.net ([67.182.139.247]
	helo=internaut.com) by outbound.mailhop.org with esmtpa (Exim 4.42)
	id 1CXqxv-000MVN-2a
	for rohc@ietf.org; Fri, 26 Nov 2004 20:01:32 -0500
Received: from localhost (aboba@localhost)
	by internaut.com (8.10.2/8.10.2) with ESMTP id iAR11TO31018
	for <rohc@ietf.org>; Fri, 26 Nov 2004 17:01:30 -0800
Date: Fri, 26 Nov 2004 17:01:29 -0800 (PST)
From: Bernard Aboba <aboba@internaut.com>
To: rohc@ietf.org
Message-ID: <Pine.LNX.4.56.0411261659040.30341@internaut.com>
MIME-Version: 1.0
Content-Type: MULTIPART/Mixed;
	BOUNDARY="-1488819285-194129012-1101410422=:7703"
Content-ID: <Pine.LNX.4.56.0411261659041.30341@internaut.com>
X-Mail-Handler: MailHop Outbound by DynDNS.org
X-Originating-IP: 67.182.139.247
X-Report-Abuse-To: abuse@dyndns.org (see
	http://www.mailhop.org/outbound/abuse.html for abuse reporting
	information)
X-MHO-User: aboba
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 1fb4c76a9d88e8fb8b791f63f8d1b07f
X-Mailman-Approved-At: Mon, 29 Nov 2004 07:39:18 -0500
Subject: [rohc] Review of draft-bormann-rohc-over-802-00.txt
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: dd055ca905b7a8538e016a7989511901

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

---1488819285-194129012-1101410422=:7703
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.56.0411261659042.30341@internaut.com>

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

Also, as noted by Mike Moreton:

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

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

---1488819285-194129012-1101410422=:7703
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII;
	NAME="draft-bormann-rohc-over-802-00.txt"
Content-ID: <Pine.LNX.4.56.0411251120220.7703@internaut.com>
Content-Description: ICAR Review
Content-Disposition: ATTACHMENT; FILENAME="draft-bormann-rohc-over-802-00.txt"
Content-Transfer-Encoding: BASE64

DQoNClJvYnVzdCBIZWFkZXIgQ29tcHJlc3Npb24gICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgQy4gQm9ybWFubg0KSW50ZXJuZXQtRHJh
ZnQgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFVuaXZlcnNp
dGFldCBCcmVtZW4gVFpJDQpFeHBpcmVzOiBBcHJpbCAxNywgMjAwNSAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIE9jdG9iZXIgMTcsIDIwMDQN
Cg0KDQogICAgICAgICAgIFJvYnVzdCBIZWFkZXIgQ29tcHJlc3Npb24gKFJP
SEMpIG92ZXIgODAyIG5ldHdvcmtzDQogICAgICAgICAgICAgICAgICAgZHJh
ZnQtYm9ybWFubi1yb2hjLW92ZXItODAyLTAwLnR4dA0KDQpTdGF0dXMgb2Yg
dGhpcyBNZW1vDQoNCiAgIFRoaXMgZG9jdW1lbnQgaXMgYW4gSW50ZXJuZXQt
RHJhZnQgYW5kIGlzIHN1YmplY3QgdG8gYWxsIHByb3Zpc2lvbnMNCiAgIG9m
IHNlY3Rpb24gMyBvZiBSRkMgMzY2Ny4gIEJ5IHN1Ym1pdHRpbmcgdGhpcyBJ
bnRlcm5ldC1EcmFmdCwgZWFjaA0KICAgYXV0aG9yIHJlcHJlc2VudHMgdGhh
dCBhbnkgYXBwbGljYWJsZSBwYXRlbnQgb3Igb3RoZXIgSVBSIGNsYWltcyBv
Zg0KICAgd2hpY2ggaGUgb3Igc2hlIGlzIGF3YXJlIGhhdmUgYmVlbiBvciB3
aWxsIGJlIGRpc2Nsb3NlZCwgYW5kIGFueSBvZg0KICAgd2hpY2ggaGUgb3Ig
c2hlIGJlY29tZSBhd2FyZSB3aWxsIGJlIGRpc2Nsb3NlZCwgaW4gYWNjb3Jk
YW5jZSB3aXRoDQogICBSRkMgMzY2OC4NCg0KICAgSW50ZXJuZXQtRHJhZnRz
IGFyZSB3b3JraW5nIGRvY3VtZW50cyBvZiB0aGUgSW50ZXJuZXQgRW5naW5l
ZXJpbmcNCiAgIFRhc2sgRm9yY2UgKElFVEYpLCBpdHMgYXJlYXMsIGFuZCBp
dHMgd29ya2luZyBncm91cHMuICBOb3RlIHRoYXQNCiAgIG90aGVyIGdyb3Vw
cyBtYXkgYWxzbyBkaXN0cmlidXRlIHdvcmtpbmcgZG9jdW1lbnRzIGFzDQog
ICBJbnRlcm5ldC1EcmFmdHMuDQoNCiAgIEludGVybmV0LURyYWZ0cyBhcmUg
ZHJhZnQgZG9jdW1lbnRzIHZhbGlkIGZvciBhIG1heGltdW0gb2Ygc2l4IG1v
bnRocw0KICAgYW5kIG1heSBiZSB1cGRhdGVkLCByZXBsYWNlZCwgb3Igb2Jz
b2xldGVkIGJ5IG90aGVyIGRvY3VtZW50cyBhdCBhbnkNCiAgIHRpbWUuICBJ
dCBpcyBpbmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMg
cmVmZXJlbmNlDQogICBtYXRlcmlhbCBvciB0byBjaXRlIHRoZW0gb3RoZXIg
dGhhbiBhcyAid29yayBpbiBwcm9ncmVzcy4iDQoNCiAgIFRoZSBsaXN0IG9m
IGN1cnJlbnQgSW50ZXJuZXQtRHJhZnRzIGNhbiBiZSBhY2Nlc3NlZCBhdA0K
ICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pZXRmLzFpZC1hYnN0cmFjdHMudHh0
Lg0KDQogICBUaGUgbGlzdCBvZiBJbnRlcm5ldC1EcmFmdCBTaGFkb3cgRGly
ZWN0b3JpZXMgY2FuIGJlIGFjY2Vzc2VkIGF0DQogICBodHRwOi8vd3d3Lmll
dGYub3JnL3NoYWRvdy5odG1sLg0KDQogICBUaGlzIEludGVybmV0LURyYWZ0
IHdpbGwgZXhwaXJlIG9uIEFwcmlsIDE3LCAyMDA1Lg0KDQpDb3B5cmlnaHQg
Tm90aWNlDQoNCiAgIENvcHlyaWdodCAoQykgVGhlIEludGVybmV0IFNvY2ll
dHkgKDIwMDQpLg0KDQpBYnN0cmFjdA0KDQogICBWYXJpb3VzIHByb3Bvc2Fs
cyBoYXZlIGJlZW4gc3VibWl0dGVkIHRvIHRoZSBST0hDIHdvcmtpbmcgZ3Jv
dXAgZm9yDQogICBlbmFibGluZyB0aGUgdXNlIG9mIFJPSEMgW1JGQyAzMDk1
XSBoZWFkZXIgY29tcHJlc3Npb24gb3ZlciBFdGhlcm5ldCwNCiAgIDgwMi4x
MSBhbmQgb3RoZXIgODAyLWJhc2VkIGxpbmtzLg0KDQogICBQcmV2aW91cyBw
cm9wb3NhbHMgZ2VuZXJhbGx5IHN1ZmZlcmVkIGZyb20gYSBsYWNrIG9mIHN5
c3RlbXMNCiAgIHBlcnNwZWN0aXZlIG9uIDgwMiBuZXR3b3Jrcy4gIFRoZSBw
cmVzZW50IGRvY3VtZW50IGF0dGVtcHRzIHRvIHN1cHBseQ0KICAgc29tZSBz
eXN0ZW1zIHBlcnNwZWN0aXZlIGFuZCBwcm92aWRlcyBhIHJvdWdoIG91dGxp
bmUgZm9yIGEgc29sdXRpb24uDQoNCg0KDQoNCkJvcm1hbm4gICAgICAgICAg
ICAgICAgICBFeHBpcmVzIEFwcmlsIDE3LCAyMDA1ICAgICAgICAgICAgICAg
ICBbUGFnZSAxXQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICBS
T0hDIG92ZXIgODAyICAgICAgICAgICAgICAgICAgT2N0b2JlciAyMDA0DQoN
Cg0KICAgVGhpcyBpcyBhIHN1Ym1pc3Npb24gdG8gdGhlIElFVEYgUk9IQyBX
Ry4gIFBsZWFzZSBkaXJlY3QgZGlzY3Vzc2lvbg0KICAgdG8gaXRzIG1haWxp
bmcgbGlzdCwgcm9oY0BpZXRmLm9yZw0KDQpUYWJsZSBvZiBDb250ZW50cw0K
DQogICAxLiAgSW50cm9kdWN0aW9uIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDMNCiAgIDIuICBEaXNjdXNz
aW9uIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAgMw0KICAgICAyLjEgICBPdmVyYWxsIFJlcXVpcmVtZW50
cyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAzDQog
ICAgIDIuMiAgIEVsZW1lbnRzIG9mIGEgU29sdXRpb24gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDQNCiAgICAgMi4zICAgV2hvIFNo
b3VsZCBTdGFuZGFyZGl6ZT8gIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAgNA0KICAgICAyLjQgICBXaHkgbm90IGp1c3QgdXNlIFBQUG9F
PyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA0DQogICAz
LiAgSXNzdWVzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gIDUNCiAgICAgMy4xICAgRXRoZXJuZXQg
TWluaW11bSBGcmFtZSBTaXplICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAgNQ0KICAgICAzLjIgICBOZWdvdGlhdGlvbiBhbmQgdGhlIGV4aXN0
aW5nIElQLW92ZXItODAyIG1vZGVsIC4gLiAuIC4gLiAuICA2DQogICA0LiAg
Tm9uLUlzc3VlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gIDYNCiAgICAgNC4xICAgUmVvcmRlcmluZyAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAgNg0KICAgICA0LjIgICBQYWRkaW5nIGEgbm9uLWlzc3VlPyAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA2DQogICA1LiAgQSBQ
cm9wb3NhbCBmb3IgdGhlIEVuY2Fwc3VsYXRpb24gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gIDcNCiAgIDYuICBBIFdheSBGb3J3YXJkIGZvciB0
aGUgTmVnb3RpYXRpb24gIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg
Nw0KICAgNy4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zICAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA4DQogICA4LiAgUmVmZXJl
bmNlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gIDgNCiAgICAgICBBdXRob3IncyBBZGRyZXNzIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgOQ0K
ICAgQS4gIEFja25vd2xlZGdlbWVudHMgLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA5DQogICAgICAgSW50ZWxsZWN0
dWFsIFByb3BlcnR5IGFuZCBDb3B5cmlnaHQgU3RhdGVtZW50cyAuIC4gLiAu
IC4gLiAuIC4gMTANCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCkJvcm1hbm4gICAgICAgICAgICAgICAg
ICBFeHBpcmVzIEFwcmlsIDE3LCAyMDA1ICAgICAgICAgICAgICAgICBbUGFn
ZSAyXQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICBST0hDIG92
ZXIgODAyICAgICAgICAgICAgICAgICAgT2N0b2JlciAyMDA0DQoNCg0KMS4g
IEludHJvZHVjdGlvbg0KDQogICBSRkMgMzA5NSBbM10gZGVmaW5lcyBmb3Vy
IFJPSEMgcHJvZmlsZXMgZm9yIHRoZSBoZWFkZXIgY29tcHJlc3Npb24gb2YN
CiAgIElQLCBVRFAsIFJUUCwgRVNQLCBhbmQgcmVsYXRlZCBwcm90b2NvbCBo
ZWFkZXJzLCBhcyB3ZWxsIGFzIGENCiAgIGZyYW1ld29yayB0aGF0IGhhcyBi
ZWVuIHVzZWQgdG8gZGVmaW5lIGEgbnVtYmVyIG9mIHJlbGF0ZWQgcHJvZmls
ZXMNCiAgIChMTEEgWzVdLCBSLW1vZGUgTExBIFs2XSwgSVAgUk9IQyBbN10s
IGFuZCBVRFAtbGl0ZSBiYXNlZCBSVFAgUk9IQw0KICAgWzhdKS4NCg0KICAg
VG8gZW5hYmxlIHJvYnVzdCBoZWFkZXIgY29tcHJlc3Npb24gb3ZlciBhIHNw
ZWNpZmljIGxpbmsgbGF5ZXIsIHRoZQ0KICAgUk9IQyBwcm9maWxlIHNwZWNp
ZmljYXRpb25zIGhhdmUgdG8gYmUgY29tcGxlbWVudGVkIGJ5IGEgbGluay1s
YXllcg0KICAgc3BlY2lmaWMgc3BlY2lmaWNhdGlvbiwgdHlwaWNhbGx5IGNh
bGxlZCAiUk9IQy1vdmVyLVgiLiAgT25lIHN1Y2gNCiAgIHNwZWNpZmljYXRp
b24gaGFzIGJlZW4gZGVmaW5lZCBpbiB0aGUgSUVURiwgUk9IQyBvdmVyIFBQ
UCBbNF0uICBPdGhlcg0KICAgUk9IQy1vdmVyLVggc3BlY2lmaWNhdGlvbnMg
aGF2ZSBiZWVuIGRlZmluZWQgYnkgdGhlIG9yZ2FuaXphdGlvbnMNCiAgIGRl
ZmluaW5nIHNwZWNpZmljIGxpbmsgbGF5ZXJzLCBzdWNoIGFzIDNHUFAuDQoN
CiAgIE5vIHNwZWNpZmljYXRpb24gY3VycmVudGx5IGV4aXN0cyBmb3IgYXBw
bHlpbmcgcm9idXN0IGhlYWRlcg0KICAgY29tcHJlc3Npb24gdG8gSUVFRSA4
MDIgbmV0d29ya3Mgc3VjaCBhcyBFdGhlcm5ldCwgODAyLjExLCBvciA4MDIu
MTYuDQogICBBIG51bWJlciBvZiBwcm9wb3NhbHMgaGF2ZSBiZWVuIG1hZGUg
dG8gdGhlIElFVEYgUk9IQyBXRyBbW2xpc3QNCiAgIHRoZXNlXV0sIGJ1dCBp
dCBiZWNhbWUgb2J2aW91cyBxdWlja2x5IHRoYXQgdGhlIHNvbHV0aW9ucyB0
aGF0IHNlZW0NCiAgIHRvIHN1Z2dlc3QgdGhlbXNlbHZlcyBkbyBub3Qgd29y
ayBhdCB0aGUgZGVzaXJhYmxlIGxldmVsIG9mDQogICBlZmZpY2llbmN5Lg0K
DQogICBUaGlzIGRvY3VtZW50IGZpcnN0IGRpc2N1c3NlcyBzb21lIGlzc3Vl
cyBhYm91dCBST0hDLW92ZXItODAyLCB0aGVuDQogICBsaXN0cyBzb21lIHBv
dGVudGlhbCBub24taXNzdWVzLCBtYWtlcyBhIHJvdWdoIHByb3Bvc2FsIGZv
ciBhbg0KICAgZW5jYXBzdWxhdGlvbiBmb3JtYXQgZm9yIFJPSEMtb3Zlci04
MDIsIGFuZCBmaW5hbGx5IGRpc2N1c3NlcyBhIHdheQ0KICAgZm9yd2FyZCB0
b3dhcmRzIGFuIGFwcHJvcHJpYXRlIG5lZ290aWF0aW9uIG1lY2hhbmlzbS4N
Cg0KMi4gIERpc2N1c3Npb24NCg0KMi4xICBPdmVyYWxsIFJlcXVpcmVtZW50
cw0KDQogICBUaGVyZSBpcyBsaXR0bGUgbmVlZCBmb3Igcm9idXN0IGhlYWRl
ciBjb21wcmVzc2lvbiBpbiBhIGNsYXNzaWNhbA0KICAgRXRoZXJuZXQgKDgw
Mi4zKSBlbnZpcm9ubWVudCwgd2hpY2ggaXMgYm90aCByZWxhdGl2ZWx5IGhp
Z2gtc3BlZWQgYW5kDQogICAoYXQgbGVhc3QgYXQgdGhlIHNlZ21lbnQgbGV2
ZWwpIHZpcnR1YWxseSBlcnJvci1mcmVlLiAgSG93ZXZlciwgV0xBTg0KICAg
KDgwMi4xMSkgYW5kIFdQQU4gKDgwMi4xNSkgbGlua3MgYXJlIG9mdGVuIGJh
bmR3aWR0aCBsaW1pdGVkOyB0aGUNCiAgIHNhbWUgd2lsbCBob2xkIGZvciBX
TUFOICg4MDIuMTYpIGxpbmtzLiAgVGhleSBhbHNvIGhhdmUgdHlwaWNhbCBs
b3NzDQogICBhbmQgZGVsYXkgcGF0dGVybnMgdGhhdCB3b3VsZCBtb3RpdmF0
ZSB0aGUgdXNlIG9mIFJPSEMgaW4gc3VjaA0KICAgc2NlbmFyaW9zLiAgU2lu
Y2Ugdm9pY2Ugb3ZlciBJUCBpcyBhbmQgd2lsbCBiZSBjb21tb25seSB1c2Vk
IGluIHRoZXNlDQogICBuZXR3b3JrcywgaGVhZGVyIGNvbXByZXNzaW9uIHdp
bGwgY29udGludWUgdG8gYmUgdXNlZnVsLg0KDQpbQkFdIEFsbCA4MDIgbmV0
d29ya3MgbmVlZCB0byBmdWxmaWxsIHRoZSBJRUVFIDgwMiBpbnZhcmlhbnRz
LCB3aGljaCBpbmNsdWRlDQpzZXF1ZW5jZSBwcmVzZXJ2YXRpb24sIGhpZ2gg
YmFuZHdpZHRoL2xvdyBsYXRlbmN5LCBsb3cgbGV2ZWwgb2YgZXJyb3JzLCBl
dGMuIA0KRm9yIGV4YW1wbGUsIGluIGluZnJhc3RydWN0dXJlIG1vZGUsIDgw
Mi4xMSBzdGFuZGFyZHMgc3BlY2lmeSB0aGUgUy9OIHJhdGlvDQphdCB3aGlj
aCBhIEJFUiBvZiAxeDEwLTUgaXMgYWNoaWV2ZWQuICBTbyBJJ2QgbGlrZSB0
byB1bmRlcnN0YW5kIHdoYXQgdGhlDQoidHlwaWNhbCBsb3NzIGFuZCBkZWxh
eSBwYXR0ZXJucyIgZW50YWlsLiAgDQoNCiAgIEluIHRoZSBST0hDIGZyYW1l
d29yaywgaGVhZGVyIGNvbXByZXNzaW9uIGlzIHBlcmZvcm1lZCBhdCB0aGUN
CiAgIGJvdW5kYXJ5IGJldHdlZW4gTGF5ZXIgMyAoSVApIGFuZCBMYXllciAy
ICg4MDIsIGluIHRoZSBjYXNlIG9mDQogICBST0hDLW92ZXItODAyKS4gIDgw
MiBuZXR3b3JrcyBhcmUgb2Z0ZW4gYnJpZGdlZCwgaS5lLiAgbXVsdGlwbGUg
ODAyDQogICB0ZWNobm9sb2dpZXMgbWF5IGNvbnRyaWJ1dGUgdG8gYSBMYXll
ciAyIHBhdGggdGhhdCBjb25zdGl0dXRlcyB3aGF0DQogICBpcyBjb25zaWRl
cmVkIHRvIGJlICJ0aGUgbGluayIgZnJvbSBhIFJPSEMgZnJhbWV3b3JrIHBv
aW50IG9mIHZpZXcuDQogICBJbiBwcmFjdGljYWwgaW1wbGVtZW50YXRpb24s
IG5vZGVzIHN1Y2ggYXMgcm91dGVycyAob2Z0ZW4gb25lIGVuZCBvZg0KICAg
YSBST0hDIGNoYW5uZWwpIGluIG1hbnkgY2FzZXMgZG9uJ3QgY29ubmVjdCBk
aXJlY3RseSB0byA4MDIuMTEgbGlua3MsDQogICBidXQgc2VuZCBwYWNrZXRz
IG9uIDgwMi4zIChFdGhlcm5ldCkgbGlua3MgdGhhdCB0aGVuIGFyZSBicmlk
Z2VkIGJ5DQoNCg0KDQpCb3JtYW5uICAgICAgICAgICAgICAgICAgRXhwaXJl
cyBBcHJpbCAxNywgMjAwNSAgICAgICAgICAgICAgICAgW1BhZ2UgM10NCgwN
CkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgUk9IQyBvdmVyIDgwMiAg
ICAgICAgICAgICAgICAgIE9jdG9iZXIgMjAwNA0KDQoNCiAgICJBY2Nlc3Mg
UG9pbnRzIiB0byA4MDIuMTEgbGlua3MuICBTeXN0ZW0gYXJjaGl0ZWN0dXJl
cyBmb3Igb3RoZXIgODAyDQogICB0ZWNobm9sb2dpZXMgYWxzbyBvZnRlbiBt
YWtlIHVzZSBvZiBicmlkZ2luZy4NCg0KW0JBXSA4MDIuMTEgQWNjZXNzIFBv
aW50cyBhcmUgbm90IGJyaWRnZXMgYXMgZGVmaW5lZCBieSA4MDIuMUQuICBG
b3IgDQpleGFtcGxlLCB0aGV5IGFyZSBub3QgcmVxdWlyZWQgdG8gcnVuIHNw
YW5uaW5nIHRyZWUsIGRvIG5vdCBtYWludGFpbg0KbGVhcm5pbmcgdGFibGVz
IGFzIHNwZWNpZmllZCBpbiA4MDIuMUQsIGV0Yy4gDQoNCiAgIE9uZSBjYW4g
Y29uY2x1ZGU6IEl0IGlzIG5vdCBzdWZmaWNpZW50IHRvIGp1c3QgbG9vayBh
dCB0aGUgd2lyZWxlc3MNCiAgIGxpbmtzIC0tIFJPSEMtb3Zlci04MDIgYWxz
byBuZWVkcyB0byB3b3JrIG9uIDgwMi4zIG5ldHdvcmtzLiAgSW4NCiAgIGVm
ZmVjdCwgYSBzaW5nbGUgc29sdXRpb24gZm9yIGFwcGx5aW5nIFJPSEMgdG8g
YWxsIDgwMiBlbnZpcm9ubWVudHMNCiAgIG5lZWRzIHRvIGJlIGRlZmluZWQg
aW5kZXBlbmRlbnQgb2YgdGhlIHBoeXNpY2FsIGxheWVyIHRlY2hub2xvZ3ku
ICBBDQogICBuaWNlIHNpZGUgZWZmZWN0IGlzIHRoYXQgdGhpcyB3aWxsIHNp
bXBsaWZ5IGJvdGggc3RhbmRhcmRpemF0aW9uIGFuZA0KICAgaW1wbGVtZW50
YXRpb24uDQoNCltCQV0gV2hpbGUgdGhpcyBpcyBhIGdvb2QgcG9pbnQsIHRo
ZSBsYWNrIG9mIHVuaWZvcm0gZGlzY292ZXJ5IGZhY2lsaXRpZXMNCmluIElF
RUUgODAyIG1heSBtYWtlIGl0IGRpZmZpY3VsdCB0byBkZXZlbG9wIGEgc29s
dXRpb24gdGhhdCBhcHBsaWVzIHRvDQphbGwgSUVFRSA4MDIgbmV0d29ya3Mu
IA0KDQoyLjIgIEVsZW1lbnRzIG9mIGEgU29sdXRpb24NCg0KICAgQSBST0hD
LW92ZXItWCBzcGVjaWZpY2F0aW9uIG5lZWRzIHRvIGRlZmluZSB0d28gZWxl
bWVudHM6DQogICBvICBBbiBlbmNhcHN1bGF0aW9uIGZvciBST0hDIGZyYW1l
d29yayBwYWNrZXRzLCBhbmQNCiAgIG8gIGEgbmVnb3RpYXRpb24gbWVjaGFu
aXNtIGZvciBhZ3JlZWluZyBvbiB0aGUgdXNlIG9mIFJPSEMgYW5kIG9uIHRo
ZQ0KICAgICAgcGFyYW1ldGVycyBvZiB0aGUgUk9IQyBjaGFubmVsLg0KDQog
ICAoV2hpbGUgYSBuZWdvdGlhdGlvbiBtZWNoYW5pc20gaXMgbm90IHN0cmlj
dGx5IG5lZWRlZCBmb3IgZXZlcnkNCiAgIFJPSEMtb3Zlci1YIGRvY3VtZW50
LCBpdCBpcyBjbGVhcmx5IHRvbyBsYXRlIGZvciB0aGUgYWx0ZXJuYXRpdmUs
DQogICBpLmUuICBtYWtpbmcgUk9IQyBtYW5kYXRvcnkgYW5kIGRlZmluaW5n
IGZpeGVkIGNoYW5uZWwgcGFyYW1ldGVyDQogICB2YWx1ZXMgZm9yIGFueSB1
c2Ugb2YgSVAgb3ZlciA4MDIuKQ0KDQoyLjMgIFdobyBTaG91bGQgU3RhbmRh
cmRpemU/DQoNCiAgIEluIHByZXZpb3VzIGRpc2N1c3Npb25zLCB0aGUgcXVl
c3Rpb24gd2FzIHJhaXNlZCB3aGljaCBib2R5IHNob3VsZA0KICAgc3RhbmRh
cmRpemUgUk9IQy1vdmVyLTgwMi4gIEFzIG1lbnRpb25lZCBpbiB0aGUgaW50
cm9kdWN0aW9uLCBvbmUNCiAgIFJPSEMtb3Zlci1YIHByb3RvY29sIGhhcyBi
ZWVuIGRlZmluZWQgaW4gdGhlIElFVEYsIG90aGVyIG9uZXMgaGF2ZQ0KICAg
YmVlbiBkZWZpbmVkIGluIHRoZSBzdGFuZGFyZHMgYm9kaWVzIGRlZmluaW5n
IHRoZSBsaW5rIGxheWVycyB1bmRlcg0KICAgY29uc2lkZXJhdGlvbi4NCg0K
ICAgSW4gdGhlIHZpZXcgb2YgdGhlIGF1dGhvciwgYSBnb29kIHRlc3Qgd291
bGQgYmUgdG8gc2VlIHdobyBoYXMNCiAgIGRlZmluZWQgdGhlIElQLW92ZXIt
WCBzcGVjaWZpY2F0aW9uLiAgVGhlIFJPSEMtb3Zlci1QUFAgc3BlY2lmaWNh
dGlvbg0KICAgY2xlYXJseSBmaXRzIGluIHRoZSBJRVRGIGFzIGJvdGggdGhl
IElQLW92ZXItUFBQIHNwZWNpZmljYXRpb24gYW5kDQogICB0aGUgUFBQIHNw
ZWNpZmljYXRpb24gaXRzZWxmIGFyZSBJRVRGIHNwZWNpZmljYXRpb25zLiAg
Rm9yIDgwMg0KICAgbmV0d29ya3MsIHRoZSBJRVRGIGFsc28gaGFzIHNwZWNp
ZmllZCB0aGUgbGluayBsYXllciBtYXBwaW5nIG9mIElQLA0KICAgaW5jbHVk
aW5nIGEgbnVtYmVyIG9mIGFuY2lsbGFyeSBwcm90b2NvbHMgKEFSUCBhbmQg
TkQpIG5lY2Vzc2FyeSBmb3INCiAgIHRoZXNlIG1hcHBpbmdzLiAgSWYgdGhl
c2UgcHJvdG9jb2xzIG5lZWQgdG8gYmUgZXh0ZW5kZWQsIGl0IHdvdWxkIGJl
DQogICBtb3JlIGFwcHJvcHJpYXRlIGZvciB0aGUgSUVURiB0byBkbyBzby4g
IFRoZSBzeXN0ZW0gaXNzdWVzIG9mIGNvbXBsZXgNCiAgIDgwMiBuZXR3b3Jr
cyBkbyBoYXZlIGEgYmVhcmluZyBvbiBST0hDLW92ZXItODAyIGFuZCBhcmUg
aW4gdGhlIGRvbWFpbg0KICAgb2YgdGhlIElFRUU7IG9uIHRoZSBvdGhlciBo
YW5kLCBubyBnb29kIGFyZ3VtZW50cyBleGlzdCBjdXJyZW50bHkNCiAgIHRo
YXQgd291bGQgY2FsbCBmb3IgYW4gZXh0ZW5zaW9uIHRvIHRoZSA4MDIgcHJv
dG9jb2xzIGZvciBST0hDLiAgSW4NCiAgIHN1bW1hcnksIHRoZSBhdXRob3Ig
YmVsaWV2ZXMgdGhhdCBJRVRGIGlzIHRoZSByaWdodCBib2R5IHRvIHdvcmsg
b24NCiAgIFJPSEMtb3Zlci04MDIuDQoNCltCQV0gT3ZlcmFsbCwgSSBkb24n
dCB0aGluayB0aGF0IHRoaXMga2luZCBvZiBkaXNjdXNzaW9uIGJlbG9uZ3Mg
aW4gdGhlDQpzcGVjaWZpY2F0aW9uLiANCg0KU2V2ZXJhbCBjb25zaWRlcmF0
aW9ucyBnbyBpbnRvIHRoZSBkZWNpc2lvbiBvZiB3aGVyZSBhIHNwZWNpZmlj
YXRpb24NCnN1Y2ggYXMgdGhpcyBvbmUgYmVsb25nczoNCg0KYS4gV2hvIGlz
IHRoZSBjb21tdW5pdHkgb2YgaW50ZXJlc3Q/ICBXaGljaCBzdGFuZGFyZHMg
bWVldGluZ3MgZG8gdGhleSBhdHRlbmQ/DQpiLiBXaGljaCBib2R5IGhhcyB0
aGUgcmVxdWlyZWQgZXhwZXJ0aXNlPyANCmMuIFdoYXQgZXhpc3Rpbmcgd29y
ayBpcyB1bmRlcndheT8gIEFyZSB0aGVyZSBjb25mbGljdHMgYmV0d2VlbiB0
aGF0DQogICB3b3JrIGFuZCB0aGUgcHJvcG9zZWQgd29yaz8gDQoNCkZvciBx
dWVzdGlvbiBhKSB0aGUgYW5zd2VyIGFwcGVhcnMgdG8gYmUgdGhlIGdyb3Vw
IG9mIHBlb3BsZSB3aG8gcGFydGljaXBhdGUNCndpdGhpbiB0aGUgSUVURiBS
T0hDIFdHLiAgVGhpcyBncm91cCBhbHNvIGhhcyBkZW1vbnN0cmF0ZWQgZXhw
ZXJ0aXNlIGluDQpoZWFkZXIgY29tcHJlc3Npb24gaXNzdWVzLCBidXQgbm90
IG5lY2Vzc2FyaWx5IGluIHRoZSBkZXRhaWxzIG9mIGxpbmsgbGF5ZXINCmNh
cGFiaWxpdGllcyBuZWdvdGlhdGlvbiB0aGF0IG1heSBuZWVkIHRvIGJlIHBh
cnQgb2YgYSBzb2x1dGlvbi4gDQoNCklmIHdvcmsgaXMgcmVxdWlyZWQgb24g
dGhlIHN1YmplY3Qgb2YgbGluayBsYXllciBjYXBhYmlsaXRpZXMgbmVnb3Rp
YXRpb24NCihlLmcuIHVzZSBvZiBST0hDKSwgdGhpcyB3b3VsZCBmaXQgd2l0
aGluIHRoZSBjaGFydGVyIG9mIGV4aXN0aW5nIElFRUUgODAyDQpncm91cHMu
IA0KDQpUaGVyZWZvcmUsIHdoaWxlIHRoZSBST0hDIG92ZXIgODAyIGNvbXBv
bmVudCBzZWVtcyBiZXN0IHN1aXRlZCB0byBJRVRGLCANCnRoZXJlIG1heSBi
ZSBsaW5rIGxheWVyIGNvbXBvbmVudHMgdG8gdGhlIHdvcmsgdGhhdCBhcmUg
YmVzdCBkb25lIGluIA0KSUVFRSA4MDIuICBJJ2QgYWxzbyBzdWdnZXN0IHRo
YXQgcmV2aWV3IGJ5IElFRUUgODAyIGlzIGFkdmlzYWJsZSwgc2luY2UNCnRo
aXMgbWF5IGltcGFjdCB0aGUgZGVncmVlIHRvIHdoaWNoIHRoZSBnb2FscyBv
ZiB0aGUgd29yayBhcmUgYWNoaWV2YWJsZS4NCg0KDQoyLjQgIFdoeSBub3Qg
anVzdCB1c2UgUFBQb0U/DQoNCiAgIEFuIGluZm9ybWF0aW9uYWwgUkZDIHNw
ZWNpZmllcyBhIHdpZGVseSBkZXBsb3llZCBzcGVjaWZpY2F0aW9uIGZvcg0K
ICAgUFBQIG92ZXIgRXRoZXJuZXQgKFBQUG9FIFs5XSksIGFuZCwgYXMgbWVu
dGlvbmVkIHRoZXJlIGlzIGENCg0KDQoNCkJvcm1hbm4gICAgICAgICAgICAg
ICAgICBFeHBpcmVzIEFwcmlsIDE3LCAyMDA1ICAgICAgICAgICAgICAgICBb
UGFnZSA0XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICBST0hD
IG92ZXIgODAyICAgICAgICAgICAgICAgICAgT2N0b2JlciAyMDA0DQoNCg0K
ICAgc3BlY2lmaWNhdGlvbiBmb3IgUk9IQyBvdmVyIFBQUCBbNF0uICBGb3Ig
YSBudW1iZXIgb2YgcmVhc29ucywganVzdA0KICAgY29tYmluaW5nIHRoZXNl
IGFzIGEgUk9IQy1vdmVyLTgwMiBzb2x1dGlvbiB3b3VsZCBiZSBzdWJvcHRp
bWFsOg0KDQogICAxLiAgUFBQb0UncyBlbmNhcHN1bGF0aW9uIHRvZ2V0aGVy
IHdpdGggdGhlIFBQUCBlbmNhcHN1bGF0aW9uIGhhcyBhDQogICAgICAgZml4
ZWQgb3ZlcmhlYWQgb2YgZWlnaHQgYnl0ZXMgcGVyIHBhY2tldCwgbmVnYXRp
bmcgc29tZSBvZiB0aGUNCiAgICAgICBzYXZpbmdzIHByb3ZpZGVkIGJ5IGhl
YWRlciBjb21wcmVzc2lvbi4NCiAgIDIuICBQUFBvRSBkb2VzIG5vdCBzb2x2
ZSB0aGUgbWluaW11bS1zaXplIHBhZGRpbmcgcHJvYmxlbSAoc2VlDQogICAg
ICAgYmVsb3cpLg0KICAgMy4gIFBQUG9FIGhhcyBhIGRpZmZlcmVudCBtb2Rl
bCB0aGFuIHRoZSB1c3VhbCBJUC1vdmVyLTgwMiBtb2RlbCwNCiAgICAgICB3
aXRoIGRpc2NvdmVyeSBhbmQgc2Vzc2lvbiBzdGFnZXMsIGFuZCBwb3NzaWJs
eSBtdWx0aXBsZSBQUFANCiAgICAgICBzZXNzaW9ucy4gIFRoaXMgY29tcGxl
eGl0eSBpcyBvZnRlbiBub3QgcmVxdWlyZWQuDQoNCiAgIE9uIHRoZSBvdGhl
ciBoYW5kLCBpZiBQUFBvRSBpcyBpbiBhY3RpdmUgdXNlIG9uIGFuIDgwMiBs
aW5rLCBhZGRpbmcNCiAgIFJPSEMtb3Zlci1QUFAgbWF5IGJlIGEgc2ltcGxl
IHdheSB0byBhZGQgcm9idXN0IGhlYWRlciBjb21wcmVzc2lvbi4NCg0KMy4g
IElzc3Vlcw0KDQozLjEgIEV0aGVybmV0IE1pbmltdW0gRnJhbWUgU2l6ZQ0K
DQogICBEdWUgdG8gaXRzIHJvb3RzIGluIHRoZSBDU01BL0NEIHByb3RvY29s
LCBFdGhlcm5ldCAoSUVFRSA4MDIuMykNCiAgIGRlZmluZXMgYSBtaW5pbXVt
IGZyYW1lIHNpemUgb2YgNjQgYnl0ZXMuICBPZiB0aGVzZSwgMTQgYnl0ZXMg
YXJlDQogICB1c2VkIGZvciB0aGUgTUFDIGhlYWRlciBhbmQgNCBhcmUgdXNl
ZCBmb3IgdGhlIE1BQyB0cmFpbGVyIChmcmFtZQ0KICAgY2hlY2sgc2VxdWVu
Y2UpLCB3aGljaCBtZWFucyB0aGF0IHRoZSBtaW5pbXVtIHBheWxvYWQgb2Yg
YW4gRXRoZXJuZXQNCiAgIHBhY2tldCBpcyA0NiBieXRlcy4NCg0KICAgVGhl
IGV4aXN0aW5nIElQdjQtb3Zlci04MDIgWzEwXSBzcGVjaWZpY2F0aW9uIHVz
ZXMgdGhlICJ0b3RhbCBzaXplIg0KICAgZmllbGQgaW4gdGhlIElQIHBhY2tl
dCB0byBpbmRpY2F0ZSBob3cgbXVjaCBvZiB0aGUgODAyIHBhY2tldCBwYXls
b2FkDQogICBpcyBhY3R1YWxseSBhbiBJUCBwYWNrZXQ7IHRoaXMgaW5kaXJl
Y3RseSBpbmRpY2F0ZXMgdGhlIHByZXNlbmNlIG9mDQogICBwYWRkaW5nLCBp
ZiBhbnkuDQoNCiAgIFJPSEMgY29tcHJlc3NlcyBhd2F5IHRoZSAidG90YWwg
c2l6ZSIgZmllbGQuICBJbnN0ZWFkLCBpdCByZWxpZXMgb24NCiAgIHRoZSBs
aW5rIGxheWVyIChvciB0aGUgUk9IQy1vdmVyLVggcHJvdG9jb2wpIHRvIHBy
b3ZpZGUgYSBwYWNrZXQNCiAgIHNpemUuICBBIFJPSEMtb3Zlci04MDIgZW5j
YXBzdWxhdGlvbiBjb3VsZCB1c2UgYSBudW1iZXIgb2Ygd2F5cyB0bw0KICAg
cHJvdmlkZSB0aGlzIHBhY2tldCBzaXplOg0KDQogICAxLiAgSXQgc3RpbGwg
Y291bGQgcmVseSBvbiB0aGUgbGluayBsYXllciBzaXplIGFuZCB1c2UgUk9I
QyBwYWRkaW5nDQogICAgICAgc2NoZW1lcyB0byBhbHdheXMgaW5mbGF0ZSB0
aGUgc2l6ZSB0byBhdCBsZWFzdCA0NiBieXRlcy4NCiAgIDIuICBJdCBjb3Vs
ZCBhZGQgYSBsZW5ndGggZmllbGQuDQogICAzLiAgSXQgY291bGQgbWFrZSB1
c2Ugb2YgdGhlIGxlbmd0aC1maWVsZCB2YXJpYW50IG9mIHRoZSA4MDIgTUFD
DQogICAgICAgaGVhZGVyIGZvcm1hdDsgdGhpcyByZXF1aXJlcyBhIGRpZmZl
cmVudCB3YXkgb2YgZGVtdWx0aXBsZXhpbmcNCiAgICAgICBST0hDIHBhY2tl
dHMgZnJvbSBvdGhlciBMTEMgcGFja2V0cy4NCg0KICAgTm90ZSB0aGF0IHNv
bHV0aW9ucyAxIGFuZCAyIG1lYW4gdGhhdCBST0hDLWNvbXByZXNzZWQgcGFj
a2V0cyBzaG9ydGVyDQogICB0aGFuIDQ2IGJ5dGVzIHdpbGwgYmUgcGFkZGVk
IG91dCB0byB0aGlzIGxlbmd0aCBpZiB0aGV5IGV2ZXIgZ28gb3Zlcg0KICAg
YW4gODAyLjMgbGluay4gIFdvcnNlLCB0aGVyZSB3aWxsIGJlIG5vIHdheSBm
b3IgYW4gODAyLjMtdG8tODAyLngNCiAgIGJyaWRnZSB0byBpZGVudGlmeSB0
aGlzIHBhZGRpbmcgYW5kIHJlbW92ZSBpdCwgc28gdGhlIHBhZGRpbmcgd2ls
bA0KICAgcmVtYWluIG9uIGFueSB3aXJlbGVzcyBzZWdtZW50cyBvZiB0aGUg
bGluayBsYXllciBwYXRoLiAgR2l2ZW4gdGhhdA0KICAgbWFueSB2b2ljZSBv
dmVyIElQIHBhY2tldHMgd2lsbCBoYXZlIHBheWxvYWRzIG9mIDEwIHRvIDIw
IGJ5dGVzIGFuZA0KDQoNCg0KQm9ybWFubiAgICAgICAgICAgICAgICAgIEV4
cGlyZXMgQXByaWwgMTcsIDIwMDUgICAgICAgICAgICAgICAgIFtQYWdlIDVd
DQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgIFJPSEMgb3ZlciA4
MDIgICAgICAgICAgICAgICAgICBPY3RvYmVyIDIwMDQNCg0KDQogICBoZWFk
ZXJzIG9mdGVuIGNhbiBiZSBjb21wcmVzc2VkIGRvd24gdG8gMyBieXRlcyBv
ciBsZXNzLCB0aGlzIGVudGFpbHMNCiAgIGEgc2lnbmlmaWNhbnQgb3Zlcmhl
YWQuDQoNCiAgIFNvLCBhcGFydCBmcm9tIHRoZSBpc3N1ZSBvZiBwcm9wZXJs
eSBpbmRpY2F0aW5nIHBhZGRpbmcsIGEgbW9yZQ0KICAgaW50ZXJlc3Rpbmcg
cHJvcGVydHkgb2YgYSBST0hDLW92ZXItODAyIGVuY2Fwc3VsYXRpb24gaXMg
d2hldGhlciBpdA0KICAgYWxsb3dzIDgwMi4zLXRvLTgwMi54IGJyaWRnZXMg
dG8gcmVtb3ZlIGFueSBwYWRkaW5nIGluc2VydGVkIG9uIHRoZQ0KICAgODAy
LjMgc2VnbWVudHMuDQoNCjMuMiAgTmVnb3RpYXRpb24gYW5kIHRoZSBleGlz
dGluZyBJUC1vdmVyLTgwMiBtb2RlbA0KDQogICBJbiB0aGUgZXhpc3Rpbmcg
SVAtb3Zlci04MDIgbW9kZWwgKGFzIGV4ZW1wbGlmaWVkIGJ5IElQdjQtb3Zl
ci04MDINCiAgIFsxMF0pIGFzc3VtZXMgdGhhdCBvbmNlIHRoZSBNQUMgKGxp
bmsgbGF5ZXIpIGFkZHJlc3Mgb2YgYSBub2RlIGlzDQogICBrbm93biwgcGFj
a2V0cyBjYW4gYmUgc2VudCB0byBpdC4gIE5vIGNoYW5uZWwgc2V0dXAvdGVh
cmRvd24gaXMNCiAgIHByb3ZpZGVkIGZvci4gIEluIHBhcnRpY3VsYXIsIGEg
bm9kZSBjYW4gbG9zZSBpdHMgc3RhdGUgKGJlIHJlYm9vdGVkKQ0KICAgYW5k
IHBhY2tldHMgY2FuIHN0aWxsIGJlIHNlbnQgdG8gaXQgYmFzZWQgb24gdGhl
IGtub3dsZWRnZSBvZiB0aGUgTUFDDQogICBhZGRyZXNzLg0KDQpbQkFdIDgw
Mi4xMSBpbmNsdWRlcyBzZXR1cC90ZWFyZG93biAoQXNzb2NpYXRpb24vUmVh
c3NvY2lhdGlvbi9EaXNhc3NvY2lhdGUpLA0Kc28gaWYgdGhpcyB3ZXJlIHRy
dWUgdGhlbiBJUCBjb3VsZCBub3QgcnVuIG92ZXIgODAyLjExLiAgUmF0aGVy
LCBJUCBvdmVyDQo4MDIgYXNzdW1lcyB0aGF0IHBhY2tldHMgY2FuIGJlIHNl
bnQgdG8gYSBrbm93biBNQUMgYWRkcmVzcyBvbmNlIHRoZQ0KbGluayBpcyB1
cCAoZS5nLiBzdWl0YWJsZSBmb3IgdXNlIGJ5IHRoZSBJbnRlcm5ldCBsYXll
cikuICBUaGUgZGVmaW5pdGlvbg0Kb2YgImxpbmsgdXAiIG1heSB2YXJ5IHdp
dGhpbiBtZWRpYSwgYnV0IGl0IGluY2x1ZGVzIHRoZSBzZXR1cCBzdGVwcy4g
DQoNCiAgIFRoZSBST0hDIGNoYW5uZWwgbW9kZWwgWzExXSBhc3N1bWVzIHRo
YXQgY2hhbm5lbCBzdGF0ZSBpcyBtYWludGFpbmVkDQogICBleHBsaWNpdGx5
LCBhdCBsZWFzdCBpZiB0aGUgbW9yZSBhZHZhbmNlZCBPLSBhbmQgUi1tb2Rl
cyBhcmUgdG8gYmUNCiAgIHVzZWQuICBJbiBhZGRpdGlvbiwgdGhpcyBjaGFu
bmVsIHNldHVwIGlzIHVzZWQgdG8gbmVnb3RpYXRlDQogICBwYXJhbWV0ZXJz
IG9mIHRoZSBjaGFubmVsIChzdWNoIGFzIHZhcmlhbnRzIG9mIHRoZSBlbmNh
cHN1bGF0aW9uDQogICBmb3JtYXQgb3IgdGhlIG1heGltdW0gbnVtYmVyIG9m
IGNvbXByZXNzaW9uIGNvbnRleHRzIHN1cHBvcnRlZCkuDQoNCltCQV0gVGhp
cyBpcyB3aGVyZSBJIHRoaW5rIHlvdSBhcmUgZ29pbmcgdG8gbmVlZCBhc3Np
c3RhbmNlIGZyb20gSUVFRSA4MDIuIA0KVG9kYXksIHRoaXMga2luZCBvZiBj
aGFubmVsIHNldHVwIGlzIGRvbmUgcXVpdGUgZGlmZmVyZW50bHkgaW4gd2ly
ZWQgYW5kDQp3aXJlbGVzcyBuZXR3b3Jrcy4gIEZvciBleGFtcGxlLCBhbiA4
MDIuMTEgU1RBIHdpbGwgb2Z0ZW4gd2lzaCB0byBvYnRhaW4NCmluZm9ybWF0
aW9uIGFib3V0IGNhcGFiaWxpdGllcyAoaW5jbHVkaW5nIFJPSEMpIHN1cHBv
cnQgd2hpbGUgaW4gU3RhdGUgMQ0KKHVuYXV0aGVudGljYXRlZCwgdW5hc3Nv
Y2lhdGVkKS4gIFRoaXMgaW1wbGllcyB1c2Ugb2YgdGhlIDgwMi4xMSBkaXNj
b3ZlcnkNCmZhY2lsaXRpZXMgKEJlYWNvbiwgUHJvYmUgUmVxdWVzdC9SZXNw
b25zZSksIHdoaWNoIGhhdmUgbm8gZXF1aXZhbGVudCBpbg0KSUVFRSA4MDIu
IA0KDQogICBBbHNvLCB3aGlsZSB0aGVyZSBpcyBhIFJPSEMgY2hhbm5lbCBm
b3IgZWFjaCBkaXJlY3Rpb24sIGVhY2ggUk9IQw0KICAgY2hhbm5lbCBpdHNl
bGYgaXMgYmlkaXJlY3Rpb25hbCBpbiB0aGUgc2Vuc2UgdGhhdCAoYXQgbGVh
c3QgaWYgbm90DQogICBqdXN0IFUtbW9kZSBpcyB0byBiZSB1c2VkKSB0aGVy
ZSBuZWVkcyB0byBiZSBhIHdheSB0byByZXR1cm4NCiAgIGZlZWRiYWNrLg0K
DQogICBGaW5hbGx5LCBvbmx5IHRoZSByZWNlaXZpbmcgZW5kIG9mIGEgcGFj
a2V0IGZsb3cgbWF5IGJlIGF3YXJlIHRoYXQNCiAgIHRoZXJlIGlzIGEgYmVu
ZWZpdCBpbiB1c2luZyBoZWFkZXIgY29tcHJlc3Npb24gKGZvciBpbGx1c3Ry
YXRpb24sDQogICBjb25zaWRlciBhIFZvV0xBTiBwaG9uZSB0aGF0IGlzIHJl
Y2VpdmluZyBwYWNrZXRzIGZyb20gYSByb3V0ZXIgdGhhdA0KICAgaXMgZGlm
ZmVyZW50IHRoYW4gdGhlIHJvdXRlciBpdCBjaG9zZSBhcyBpdHMgZGVmYXVs
dCByb3V0ZXIgYW5kIHRodXMNCiAgIGZvciB0aGUgcmV2ZXJzZSBwYWNrZXQg
ZmxvdykuICBUaGVyZWZvcmUsIHRoZXJlIHNob3VsZCBiZSBhIHdheSB0bw0K
ICAgaW5pdGlhdGUgdGhlIHNldHVwIG9mIGEgUk9IQyBjaGFubmVsIGZyb20g
dGhlIHJlY2VpdmluZyBlbmQuDQoNCjQuICBOb24tSXNzdWVzDQoNCjQuMSAg
UmVvcmRlcmluZw0KDQogICBGb3J0dW5hdGVseSwgODAyIGxpbmtzIGFyZSBz
ZXF1ZW5jZS1wcmVzZXJ2aW5nLCBzbyB0aGVyZSBpcyBubyBuZWVkDQogICB0
byByZS1zZXF1ZW5jZSBwYWNrZXRzIHRvIGF2b2lkIHJlb3JkZXJpbmcgKGFz
IHdvdWxkIGJlIHJlcXVpcmVkIGJ5DQogICB0aGUgY3VycmVudCBST0hDIGZy
YW1ld29yaykuDQoNCltCQV0gTm90ZSB0aGF0IDgwMiBsaW5rcyBhcmUgb25s
eSByZXF1aXJlZCB0byBwcmVzZXJ2ZSBvcmRlcmluZyB3aXRoaW4NCmEgZ2l2
ZW4gODAyLjFwIHByaW9yaXR5IGdyb3VwLiANCg0KNC4yICBQYWRkaW5nIGEg
bm9uLWlzc3VlPw0KDQogICBPbmUgYXJndW1lbnQgY291bGQgYmUgdGhhdCB0
aGUgcGFkZGluZyBpc3N1ZSBvdXRsaW5lZCBpbiBTZWN0aW9uIDMuMQ0KICAg
Y2FuIGJlIGlnbm9yZWQgZm9yIG1vc3QgODAyIG5ldHdvcmtzLCBlaXRoZXIg
YmVjYXVzZSB0aGUgcGF5bG9hZHMNCiAgIHdpbGwgYmUgbGFyZ2VyIHRoYW4g
Zm9yIHRoZSBtb3N0IGhlYXZpbHkgY29tcHJlc3Npbmcgdm9pY2UgY29kZWNz
IG9yDQoNCg0KDQpCb3JtYW5uICAgICAgICAgICAgICAgICAgRXhwaXJlcyBB
cHJpbCAxNywgMjAwNSAgICAgICAgICAgICAgICAgW1BhZ2UgNl0NCgwNCklu
dGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgUk9IQyBvdmVyIDgwMiAgICAg
ICAgICAgICAgICAgIE9jdG9iZXIgMjAwNA0KDQoNCiAgIGJlY2F1c2UgdGhl
IGhlYWRlciBvdmVyaGVhZCBpcyBhbHJlYWR5IHJhdGhlciBoaWdoIChlLmcu
LCBmb3INCiAgIDgwMi4xMWIsIHRoZSBsaW5rLWxheWVyIGhlYWRlciBvdmVy
aGVhZCBpbiB0eXBpY2FsIGNvbmZpZ3VyYXRpb25zIGlzDQogICBhYm91dCBh
cyBsYXJnZSBhcyB0aGF0IG9mIHRocmVlLWRpZ2l0IG51bWJlcnMgb2YgYnl0
ZXMgaW4gdGhlDQogICBwYXlsb2FkKS4NCg0KICAgVGhlIGF1dGhvciB0YWtl
cyB0aGUgdmlld3BvaW50IHRoYXQgYSBzb2x1dGlvbiB0aGF0IGlzIGludGVu
ZGVkIHRvIGJlDQogICB1c2VkIHVuaXZlcnNhbGx5IHRocm91Z2ggdGhlIDgw
MiBzcGFjZSBkb2VzIG5lZWQgdG8gYWRkcmVzcyBwYWRkaW5nLg0KDQo1LiAg
QSBQcm9wb3NhbCBmb3IgdGhlIEVuY2Fwc3VsYXRpb24NCg0KICAgQmFzZWQg
b24gdGhlIGNvbnNpZGVyYXRpb25zIGFib3ZlLCB0aGlzIGRvY3VtZW50IHBy
b3Bvc2VzIHRvIHVzZSBMTEMNCiAgIGVuY2Fwc3VsYXRpb24gb2YgUk9IQyBw
YWNrZXRzLiAgU2V2ZXJhbCBhcHByb2FjaGVzIGFyZSBwb3NzaWJsZToNCg0K
ICAgMS4gIEFuIFNBUCB2YWx1ZSBpcyBhbGxvY2F0ZWQgdG8gUk9IQy4gIFRo
ZSBwZXItcGFja2V0IG92ZXJoZWFkIGlzDQogICAgICAgcmVkdWNlZCB0byB0
aHJlZSBieXRlcy4gIE5vdGUgdGhhdCB0aGlzIG1lYW5zIHRoZSBuZWdvdGlh
dGlvbg0KICAgICAgIHByb3RvY29sIG5lZWRzIHRvIGZpeCB0aGUgc21hbGwt
Q0lEIHZzLiAgbGFyZ2UtQ0lEIGNob2ljZQ0KICAgICAgIChhbHRlcm5hdGl2
ZWx5LCBST0hDLW92ZXItODAyIGNvdWxkIHNpbXBseSBhbHdheXMgdXNlIGxh
cmdlIENJRHMsDQogICAgICAgb3IgZXZlbiBhIHBhaXIgb2YgU0FQIHZhbHVl
cyBjb3VsZCBiZSBhbGxvY2F0ZWQpLg0KICAgMi4gIFNBUCAweEFBIGlzIHVz
ZWQuICBCeSBzZXR0aW5nIHRoZSBmaXJzdCBieXRlIG9mIHRoZSBPVUkgdG8g
YQ0KICAgICAgIHZhbHVlIGlsbGVnYWwgZm9yIGFuIE9VSSAobXVsdGljYXN0
L3ByaXZhdGUpLCB0aGUgcmVzdCBvZiB0aGUNCiAgICAgICBmcmFtZSBjYW4g
YmUgdXNlZCBmb3IgdGhlIFJPSEMgcGFja2V0LCByZWR1Y2luZyB0aGUgb3Zl
cmhlYWQgdG8NCiAgICAgICBmb3VyIGJ5dGVzLiAgVGhlIGZpcnN0IChpbGxl
Z2FsIE9VSSkgYnl0ZSBjYW4gYmUgdXNlZCB0bw0KICAgICAgIGRlbXVsdGlw
bGV4IHZhcmlhbnRzLCBlLmcuICBzbWFsbC1DSUQgYW5kIGxhcmdlLUNJRCBS
T0hDIHBhY2tldHMNCiAgICAgICBhcyB3ZWxsIGFzIHBvc3NpYmxlIG5lZ290
aWF0aW9uIHByb3RvY29sIHBhY2tldHMgKHNlZSBiZWxvdykuDQogICAgICAg
V2hhdCB3b3VsZCBiZSB0aGUgc2Vjb25kIGFuZCB0aGlyZCBPVUkgYnl0ZXMg
YXJlIGFscmVhZHkgdXNlZCBmb3INCiAgICAgICB0aGUgUk9IQyBwYWNrZXQu
DQogICAzLiAgQSBmdWxsIFNOQVAgaGVhZGVyIGlzIHVzZWQuICAoRnJvbSBh
biBvdmVyaGVhZCBwZXJzcGVjdGl2ZSwgdGhpcw0KICAgICAgIGlzIG5vdCBi
ZXR0ZXIgdGhhbiB0aGUgUFBQb0UgY2FzZSwgYnV0LCBsaWtlIHRoZSBwcmV2
aW91cw0KICAgICAgIHByb3Bvc2FscywgaXQgZG9lcyBhbGxvdyB0aGUgcmVt
b3ZhbCBvZiBwYWRkaW5nIGJ5IGJyaWRnZXMuKQ0KDQogICBUaGUgYXV0aG9y
IHByb3Bvc2VzIHRvIG9idGFpbiBhZGRpdGlvbmFsIGlucHV0IGZyb20gZW5j
YXBzdWxhdGlvbg0KICAgZ3JheWJlYXJkcyBhYm91dCB0aGlzLg0KDQpbQkFd
IExMQyBlbmNhcHN1bGF0aW9uIGRvZXMgbWFrZSBzZW5zZSB0byBtZSBzaW5j
ZSB0aGlzIGlzIG1vc3QgZ2VuZXJhbA0KKGUuZy4gd29ya3Mgb24gODAyLjEx
IGFzIHdlbGwgYXMgODAyLjMpLiAgSSdkIGxpa2UgdG8gZ2V0IG1vcmUgcmV2
aWV3DQpjb21tZW50cyBvbiB0aGlzIGZyb20gdGhlIElFRUUgODAyIGZvbGtz
LiAgDQoNCjYuICBBIFdheSBGb3J3YXJkIGZvciB0aGUgTmVnb3RpYXRpb24N
Cg0KICAgTmVnb3RpYXRpb24gb2YgUk9IQyBjaGFubmVscyBjYW4gZWl0aGVy
IGJlIHBpZ2d5LWJhY2tlZCBvbiB0aGUNCiAgIGV4aXN0aW5nIGFkZHJlc3Mg
cmVzb2x1dGlvbi9uZWlnaGJvciBkaXNjb3ZlcnkgcHJvdG9jb2xzIG9yIGEN
CiAgIGNvbXBsZXRlbHkgc2VwYXJhdGUgbmVnb3RpYXRpb24gcHJvdG9jb2wg
Y2FuIGJlIHVzZWQuDQoNCiAgIEZvciBJUHY0LCBleHRlbmRpbmcgQVJQIHNv
dW5kcyByYXRoZXIgZGlmZmljdWx0IGF0IHRoaXMgcG9pbnQgaW4gdGhlDQog
ICBldm9sdXRpb24gb2YgdGhpcyBwcm90b2NvbC4gIEZvciBJUHY2LCB3aGls
ZSBORCBpcyBwcm9iYWJseSBhIG1vcmUNCiAgIGV4dGVuc2libGUgcHJvdG9j
b2wsIGl0IGlzIG5vdCBjbGVhciB0aGF0IGl0IGlzIHRoZSByaWdodCBwbGFj
ZSBmb3INCiAgIG5lZ290aWF0aW5nIGxpbmstbGF5ZXIgY2hhcmFjdGVyaXN0
aWNzLg0KDQogICBJbnN0ZWFkLCBhIHNpbXBsZSBuZWdvdGlhdGlvbiBwcm90
b2NvbCBzaG91bGQgYmUgZGVmaW5lZCB0aGF0IGlzDQogICBiYXNlZCBvbiBy
ZWd1bGFybHkgcHJvYmluZyB0aGUgcGVlciBub2RlIGZvciBST0hDIGNhcGFi
aWxpdHkgYW5kDQogICBvZmZlcmluZyBhIGNhcGFiaWxpdHkgc2V0LiAgQSBt
YWdpYyBudW1iZXIgc2NoZW1lIGNhbiBiZSB1c2VkIGJvdGggdG8NCiAgIGVu
c3VyZSBsaXZlbmVzcyBvZiB0aGUgcGVlciBzdGF0ZSBhc3N1bWVkIGFuZCBh
cyBhIGJhc2ljIHNlY3VyaXR5DQoNCg0KDQpCb3JtYW5uICAgICAgICAgICAg
ICAgICAgRXhwaXJlcyBBcHJpbCAxNywgMjAwNSAgICAgICAgICAgICAgICAg
W1BhZ2UgN10NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgUk9I
QyBvdmVyIDgwMiAgICAgICAgICAgICAgICAgIE9jdG9iZXIgMjAwNA0KDQoN
CiAgIG1lYXN1cmUuDQoNCiAgIFRoZSBuZWdvdGlhdGlvbiBwcm90b2NvbCBz
aG91bGQgcHJlZmVyYWJseSBzaGFyZSBpdHMgZW5jYXBzdWxhdGlvbg0KICAg
d2l0aCB0aGUgUk9IQyBlbmNhcHN1bGF0aW9uIGl0c2VsZiB0byBlbnN1cmUg
cHJvYmVzIG9ubHkgYXJyaXZlIGlmDQogICB0aGVyZSBpcyBubyBvYnN0YWNs
ZSB0byBMTEMtc3R5bGUgZnJhbWVzLg0KDQpbQkFdIFNpbmNlIGl0IGNhbiBi
ZSBhcmd1ZWQgdGhhdCBrbm93bGVkZ2Ugb2YgUk9IQyBjYXBhYmlsaXRpZXMg
Y291bGQgYmUNCnJlbGV2YW50IHRvIDgwMi4xMSByb2FtaW5nIGRlY2lzaW9u
cywgaXQgbWF5IG5vdCBiZSBwb3NzaWJsZSB0byBoYW5kbGUNClJPSEMgY2Fw
YWJpbGl0eSBkaXNjb3ZlcnkgaW4gYSBnZW5lcmljIG1hbm5lciBmb3IgYWxs
IElFRUUgODAyIG1lZGlhLiANCg0KNy4gIFNlY3VyaXR5IENvbnNpZGVyYXRp
b25zDQoNCiAgIE1ha2luZyBhIG5vZGUgYmVsaWV2ZSBpdHMgcGVlciBub2Rl
IGlzIFJPSEMgY2FwYWJsZSB3aGVuIGl0IGlzbid0IGlzDQogICBvbmUgd2F5
IHRvIHN0YWdlIGEgZGVuaWFsIG9mIHNlcnZpY2UgYXR0YWNrLCBhcyBpcyBt
YWxpY2lvdXNseQ0KICAgdGVhcmluZyBkb3duIFJPSEMgc3RhdGUuICBUaGUg
Uk9IQyBuZWdvdGlhdGlvbiBwcm90b2NvbCBwcm9iYWJseQ0KICAgbmVlZHMg
dG8gaGF2ZSBzZWN1cml0eSB0aGF0IGlzIGNvbW1lbnN1cmF0ZSB0byB0aGF0
IG9mIHRoZSBhZGRyZXNzDQogICByZXNvbHV0aW9uL25laWdoYm9yIGRpc2Nv
dmVyeSBwcm90b2NvbCBpbiB1c2UuDQoNCltCQV0gVGhpcyBhcmd1ZXMgZm9y
IHRoZSBuZWVkIGZvciBwcm90ZWN0aW9uIG9mIHRoZSBST0hDIGNhcGFiaWxp
dGllcw0KZGlzY292ZXJ5IGZhY2lsaXR5LiAgR2l2ZW4gdGhhdCB0aGlzIHBy
b3RlY3Rpb24gaXMgYWxzbyBub3QgdW5pZm9ybQ0Kd2l0aGluIElFRUUgODAy
IChlLmcuIHZlcmlmaWNhdGlvbiBvZiBjYXBhYmlsaXRpZXMgaXMgc3VwcG9y
dGVkIGluDQpJRUVFIDgwMi4xMWksIGJ1dCBub3QgaW4gSUVFRSA4MDIgaW4g
Z2VuZXJhbCksIHRoaXMgaXMgcHJvYmFibHkgYW5vdGhlcg0KZXhhbXBsZSB3
aGVyZSB1bmlmb3JtaXR5IG1heSBub3QgYmUgYWNoaWV2YWJsZS4gDQoNCiAg
IFRoZSBST0hDIHByb3RvY29sIGl0c2VsZiBpcyBxdWl0ZSBzdXNjZXB0aWJs
ZSB0byBhdHRhY2tzLiAgVG8gcXVvdGUNCiAgIFJGQyAzMDk1IFszXToNCg0K
ICAgICAgRGVuaWFsLW9mLXNlcnZpY2UgYXR0YWNrcyBhcmUgcG9zc2libGUg
aWYgYW4gaW50cnVkZXIgY2FuDQogICAgICBpbnRyb2R1Y2UgKGZvciBleGFt
cGxlKSBib2d1cyBTVEFUSUMsIERZTkFNSUMgb3IgRkVFREJBQ0sgcGFja2V0
cw0KICAgICAgb250byB0aGUgbGluayBhbmQgdGhlcmVieSBjYXVzZSBjb21w
cmVzc2lvbiBlZmZpY2llbmN5IHRvIGJlDQogICAgICByZWR1Y2VkLiAgSG93
ZXZlciwgYW4gaW50cnVkZXIgaGF2aW5nIHRoZSBhYmlsaXR5IHRvIGluamVj
dA0KICAgICAgYXJiaXRyYXJ5IHBhY2tldHMgYXQgdGhlIGxpbmsgbGF5ZXIg
aW4gdGhpcyBtYW5uZXIgcmFpc2VzDQogICAgICBhZGRpdGlvbmFsIHNlY3Vy
aXR5IGlzc3VlcyB0aGF0IGR3YXJmIHRob3NlIHJlbGF0ZWQgdG8gdGhlIHVz
ZSBvZg0KICAgICAgaGVhZGVyIGNvbXByZXNzaW9uLg0KDQo4ICBSZWZlcmVu
Y2VzDQoNCiAgIFsxXSAgIEJyYWRuZXIsIFMuLCAiVGhlIEludGVybmV0IFN0
YW5kYXJkcyBQcm9jZXNzIC0tIFJldmlzaW9uIDMiLA0KICAgICAgICAgQkNQ
IDksIFJGQyAyMDI2LCBPY3RvYmVyIDE5OTYuDQoNCiAgIFsyXSAgIEJyYWRu
ZXIsIFMuLCAiS2V5IHdvcmRzIGZvciB1c2UgaW4gUkZDcyB0byBJbmRpY2F0
ZSBSZXF1aXJlbWVudA0KICAgICAgICAgTGV2ZWxzIiwgQkNQIDE0LCBSRkMg
MjExOSwgTWFyY2ggMTk5Ny4NCg0KICAgWzNdICAgQm9ybWFubiwgQy4sIEJ1
cm1laXN0ZXIsIEMuLCBEZWdlcm1hcmssIE0uLCBGdWt1c2hpbWEsIEguLA0K
ICAgICAgICAgSGFubnUsIEguLCBKb25zc29uLCBMLUUuLCBIYWtlbmJlcmcs
IFIuLCBLb3JlbiwgVC4sIExlLCBLLiwNCiAgICAgICAgIExpdSwgWi4sIE1h
cnRlbnNzb24sIEEuLCBNaXlhemFraSwgQS4sIFN2YW5icm8sIEsuLCBXaWVi
a2UsIFQuLA0KICAgICAgICAgWW9zaGltdXJhLCBULiBhbmQgSC4gWmhlbmcs
ICJST2J1c3QgSGVhZGVyIENvbXByZXNzaW9uIChST0hDKToNCiAgICAgICAg
IEZyYW1ld29yayBhbmQgZm91ciBwcm9maWxlczogUlRQLCBVRFAsIEVTUCwg
YW5kIHVuY29tcHJlc3NlZCIsDQogICAgICAgICBSRkMgMzA5NSwgSnVseSAy
MDAxLg0KDQogICBbNF0gICBCb3JtYW5uLCBDLiwgIlJvYnVzdCBIZWFkZXIg
Q29tcHJlc3Npb24gKFJPSEMpIG92ZXIgUFBQIiwgUkZDDQogICAgICAgICAz
MjQxLCBBcHJpbCAyMDAyLg0KDQogICBbNV0gICBKb25zc29uLCBMLUUuIGFu
ZCBHLiBQZWxsZXRpZXIsICJST2J1c3QgSGVhZGVyIENvbXByZXNzaW9uDQog
ICAgICAgICAoUk9IQyk6IEEgTGluay1MYXllciBBc3Npc3RlZCBQcm9maWxl
IGZvciBJUC9VRFAvUlRQIiwgUkZDDQogICAgICAgICAzMjQyLCBBcHJpbCAy
MDAyLg0KDQogICBbNl0gICBMaXUsIFouIGFuZCBLLiBMZSwgIlplcm8tYnl0
ZSBTdXBwb3J0IGZvciBCaWRpcmVjdGlvbmFsDQoNCg0KDQpCb3JtYW5uICAg
ICAgICAgICAgICAgICAgRXhwaXJlcyBBcHJpbCAxNywgMjAwNSAgICAgICAg
ICAgICAgICAgW1BhZ2UgOF0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICAg
ICAgICAgUk9IQyBvdmVyIDgwMiAgICAgICAgICAgICAgICAgIE9jdG9iZXIg
MjAwNA0KDQoNCiAgICAgICAgIFJlbGlhYmxlIE1vZGUgKFItbW9kZSkgaW4g
RXh0ZW5kZWQgTGluay1MYXllciBBc3Npc3RlZCBST2J1c3QNCiAgICAgICAg
IEhlYWRlciBDb21wcmVzc2lvbiAoUk9IQykgUHJvZmlsZSIsIFJGQyAzNDA4
LCBEZWNlbWJlciAyMDAyLg0KDQogICBbN10gICBKb25zc29uLCBMLUUuIGFu
ZCBHLiBQZWxsZXRpZXIsICJST2J1c3QgSGVhZGVyIENvbXByZXNzaW9uDQog
ICAgICAgICAoUk9IQyk6IEEgQ29tcHJlc3Npb24gUHJvZmlsZSBmb3IgSVAi
LCBSRkMgMzg0MywgSnVuZSAyMDA0Lg0KDQogICBbOF0gICBQZWxsZXRpZXIs
IEcuLCAiUk9idXN0IEhlYWRlciBDb21wcmVzc2lvbiAoUk9IQyk6UHJvZmls
ZXMgZm9yDQogICAgICAgICBVRFAtTGl0ZSIsIGRyYWZ0LWlldGYtcm9oYy11
ZHAtbGl0ZS0wNCAod29yayBpbiBwcm9ncmVzcyksIEp1bmUNCiAgICAgICAg
IDIwMDQuDQoNCiAgIFs5XSAgIE1hbWFrb3MsIEwuLCBMaWRsLCBLLiwgRXZh
cnRzLCBKLiwgQ2FycmVsLCBELiwgU2ltb25lLCBELiBhbmQNCiAgICAgICAg
IFIuIFdoZWVsZXIsICJBIE1ldGhvZCBmb3IgVHJhbnNtaXR0aW5nIFBQUCBP
dmVyIEV0aGVybmV0DQogICAgICAgICAoUFBQb0UpIiwgUkZDIDI1MTYsIEZl
YnJ1YXJ5IDE5OTkuDQoNCiAgIFsxMF0gIFBvc3RlbCwgSi4gYW5kIEouIFJl
eW5vbGRzLCAiU3RhbmRhcmQgZm9yIHRoZSB0cmFuc21pc3Npb24gb2YNCiAg
ICAgICAgIElQIGRhdGFncmFtcyBvdmVyIElFRUUgODAyIG5ldHdvcmtzIiwg
U1REIDQzLCBSRkMgMTA0MiwNCiAgICAgICAgIEZlYnJ1YXJ5IDE5ODguDQoN
CiAgIFsxMV0gIEpvbnNzb24sIEwtRS4sICJST2J1c3QgSGVhZGVyIENvbXBy
ZXNzaW9uIChST0hDKTogVGVybWlub2xvZ3kNCiAgICAgICAgIGFuZCBDaGFu
bmVsIE1hcHBpbmcgRXhhbXBsZXMiLCBSRkMgMzc1OSwgQXByaWwgMjAwNC4N
Cg0KDQpBdXRob3IncyBBZGRyZXNzDQoNCiAgIENhcnN0ZW4gQm9ybWFubg0K
ICAgVW5pdmVyc2l0YWV0IEJyZW1lbiBUWkkNCiAgIFBvc3RmYWNoIDMzMDQ0
MA0KICAgQnJlbWVuICBELTI4MzM0DQogICBHZXJtYW55DQoNCiAgIFBob25l
OiArNDkgNDIxIDIxOCA3MDI0DQogICBGYXg6ICAgKzQ5IDQyMSAyMTggNzAw
MA0KICAgRU1haWw6IGNhYm9AdHppLm9yZw0KDQpBcHBlbmRpeCBBLiAgQWNr
bm93bGVkZ2VtZW50cw0KDQogICBUaGUgaXNzdWUgb2YgZW5hYmxpbmcgcm9i
dXN0IGhlYWRlciBjb21wcmVzc2lvbiBvdmVyIDgwMiBuZXR3b3JrcyBoYXMN
CiAgIGJlZW4gYnJvdWdodCB1cCByZXBlYXRlZGx5LCBlLmcuICBieSBLcmlz
IEZsZW1pbmcgaW4gYSBjb250cmlidXRpb24NCiAgIGNhbGxlZCBST0hDb1dF
TSAoZHJhZnQtZmxlbWluZy1yb2hjLXdpcmVsZXNzLWV0aGVybmV0LW1lZCku
ICBUaGUNCiAgIHBhcnRpY2lwYW50IGNvbW1lbnRzIGF0IHRoZSBBdGxhbnRh
IElFVEYgUk9IQyBXRyBtZWV0aW5nIChOb3ZlbWJlcg0KICAgMjAwMikgcHJv
dmlkZWQgdGhlIGJhc2lzIGZvciB0aGUgYW5hbHl0aWNhbCBwYXJ0IG9mIHRo
aXMgZG9jdW1lbnQuDQoNCg0KDQoNCg0KDQoNCg0KDQoNCkJvcm1hbm4gICAg
ICAgICAgICAgICAgICBFeHBpcmVzIEFwcmlsIDE3LCAyMDA1ICAgICAgICAg
ICAgICAgICBbUGFnZSA5XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICAg
ICAgICBST0hDIG92ZXIgODAyICAgICAgICAgICAgICAgICAgT2N0b2JlciAy
MDA0DQoNCg0KSW50ZWxsZWN0dWFsIFByb3BlcnR5IFN0YXRlbWVudA0KDQog
ICBUaGUgSUVURiB0YWtlcyBubyBwb3NpdGlvbiByZWdhcmRpbmcgdGhlIHZh
bGlkaXR5IG9yIHNjb3BlIG9mIGFueQ0KICAgSW50ZWxsZWN0dWFsIFByb3Bl
cnR5IFJpZ2h0cyBvciBvdGhlciByaWdodHMgdGhhdCBtaWdodCBiZSBjbGFp
bWVkIHRvDQogICBwZXJ0YWluIHRvIHRoZSBpbXBsZW1lbnRhdGlvbiBvciB1
c2Ugb2YgdGhlIHRlY2hub2xvZ3kgZGVzY3JpYmVkIGluDQogICB0aGlzIGRv
Y3VtZW50IG9yIHRoZSBleHRlbnQgdG8gd2hpY2ggYW55IGxpY2Vuc2UgdW5k
ZXIgc3VjaCByaWdodHMNCiAgIG1pZ2h0IG9yIG1pZ2h0IG5vdCBiZSBhdmFp
bGFibGU7IG5vciBkb2VzIGl0IHJlcHJlc2VudCB0aGF0IGl0IGhhcw0KICAg
bWFkZSBhbnkgaW5kZXBlbmRlbnQgZWZmb3J0IHRvIGlkZW50aWZ5IGFueSBz
dWNoIHJpZ2h0cy4gIEluZm9ybWF0aW9uDQogICBvbiB0aGUgcHJvY2VkdXJl
cyB3aXRoIHJlc3BlY3QgdG8gcmlnaHRzIGluIFJGQyBkb2N1bWVudHMgY2Fu
IGJlDQogICBmb3VuZCBpbiBCQ1AgNzggYW5kIEJDUCA3OS4NCg0KICAgQ29w
aWVzIG9mIElQUiBkaXNjbG9zdXJlcyBtYWRlIHRvIHRoZSBJRVRGIFNlY3Jl
dGFyaWF0IGFuZCBhbnkNCiAgIGFzc3VyYW5jZXMgb2YgbGljZW5zZXMgdG8g
YmUgbWFkZSBhdmFpbGFibGUsIG9yIHRoZSByZXN1bHQgb2YgYW4NCiAgIGF0
dGVtcHQgbWFkZSB0byBvYnRhaW4gYSBnZW5lcmFsIGxpY2Vuc2Ugb3IgcGVy
bWlzc2lvbiBmb3IgdGhlIHVzZSBvZg0KICAgc3VjaCBwcm9wcmlldGFyeSBy
aWdodHMgYnkgaW1wbGVtZW50ZXJzIG9yIHVzZXJzIG9mIHRoaXMNCiAgIHNw
ZWNpZmljYXRpb24gY2FuIGJlIG9idGFpbmVkIGZyb20gdGhlIElFVEYgb24t
bGluZSBJUFIgcmVwb3NpdG9yeSBhdA0KICAgaHR0cDovL3d3dy5pZXRmLm9y
Zy9pcHIuDQoNCiAgIFRoZSBJRVRGIGludml0ZXMgYW55IGludGVyZXN0ZWQg
cGFydHkgdG8gYnJpbmcgdG8gaXRzIGF0dGVudGlvbiBhbnkNCiAgIGNvcHly
aWdodHMsIHBhdGVudHMgb3IgcGF0ZW50IGFwcGxpY2F0aW9ucywgb3Igb3Ro
ZXIgcHJvcHJpZXRhcnkNCiAgIHJpZ2h0cyB0aGF0IG1heSBjb3ZlciB0ZWNo
bm9sb2d5IHRoYXQgbWF5IGJlIHJlcXVpcmVkIHRvIGltcGxlbWVudA0KICAg
dGhpcyBzdGFuZGFyZC4gIFBsZWFzZSBhZGRyZXNzIHRoZSBpbmZvcm1hdGlv
biB0byB0aGUgSUVURiBhdA0KICAgaWV0Zi1pcHJAaWV0Zi5vcmcuDQoNCg0K
RGlzY2xhaW1lciBvZiBWYWxpZGl0eQ0KDQogICBUaGlzIGRvY3VtZW50IGFu
ZCB0aGUgaW5mb3JtYXRpb24gY29udGFpbmVkIGhlcmVpbiBhcmUgcHJvdmlk
ZWQgb24gYW4NCiAgICJBUyBJUyIgYmFzaXMgYW5kIFRIRSBDT05UUklCVVRP
UiwgVEhFIE9SR0FOSVpBVElPTiBIRS9TSEUgUkVQUkVTRU5UUw0KICAgT1Ig
SVMgU1BPTlNPUkVEIEJZIChJRiBBTlkpLCBUSEUgSU5URVJORVQgU09DSUVU
WSBBTkQgVEhFIElOVEVSTkVUDQogICBFTkdJTkVFUklORyBUQVNLIEZPUkNF
IERJU0NMQUlNIEFMTCBXQVJSQU5USUVTLCBFWFBSRVNTIE9SIElNUExJRUQs
DQogICBJTkNMVURJTkcgQlVUIE5PVCBMSU1JVEVEIFRPIEFOWSBXQVJSQU5U
WSBUSEFUIFRIRSBVU0UgT0YgVEhFDQogICBJTkZPUk1BVElPTiBIRVJFSU4g
V0lMTCBOT1QgSU5GUklOR0UgQU5ZIFJJR0hUUyBPUiBBTlkgSU1QTElFRA0K
ICAgV0FSUkFOVElFUyBPRiBNRVJDSEFOVEFCSUxJVFkgT1IgRklUTkVTUyBG
T1IgQSBQQVJUSUNVTEFSIFBVUlBPU0UuDQoNCg0KQ29weXJpZ2h0IFN0YXRl
bWVudA0KDQogICBDb3B5cmlnaHQgKEMpIFRoZSBJbnRlcm5ldCBTb2NpZXR5
ICgyMDA0KS4gIFRoaXMgZG9jdW1lbnQgaXMgc3ViamVjdA0KICAgdG8gdGhl
IHJpZ2h0cywgbGljZW5zZXMgYW5kIHJlc3RyaWN0aW9ucyBjb250YWluZWQg
aW4gQkNQIDc4LCBhbmQNCiAgIGV4Y2VwdCBhcyBzZXQgZm9ydGggdGhlcmVp
biwgdGhlIGF1dGhvcnMgcmV0YWluIGFsbCB0aGVpciByaWdodHMuDQoNCg0K
QWNrbm93bGVkZ21lbnQNCg0KICAgRnVuZGluZyBmb3IgdGhlIFJGQyBFZGl0
b3IgZnVuY3Rpb24gaXMgY3VycmVudGx5IHByb3ZpZGVkIGJ5IHRoZQ0KICAg
SW50ZXJuZXQgU29jaWV0eS4NCg0KDQoNCg0KQm9ybWFubiAgICAgICAgICAg
ICAgICAgIEV4cGlyZXMgQXByaWwgMTcsIDIwMDUgICAgICAgICAgICAgICAg
W1BhZ2UgMTBdDQoMDQo=

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

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

---1488819285-194129012-1101410422=:7703--



From rohc-bounces@ietf.org  Mon Nov 29 08:44:21 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20455
	for <rohc-web-archive@ietf.org>; Mon, 29 Nov 2004 08:44:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYluA-0001Q4-Gt
	for rohc-web-archive@ietf.org; Mon, 29 Nov 2004 08:49:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYllP-0007ei-OM; Mon, 29 Nov 2004 08:40:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYlfb-0006Dn-Fh
	for rohc@megatron.ietf.org; Mon, 29 Nov 2004 08:34:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19387
	for <rohc@ietf.org>; Mon, 29 Nov 2004 08:34:22 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYlkS-00018h-RE
	for rohc@ietf.org; Mon, 29 Nov 2004 08:39:25 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iATDY44R028135; Mon, 29 Nov 2004 14:34:05 +0100 (MET)
In-Reply-To: <3F2E01E1D7B04F4EBEC92D3FA324D8803857FC@rsys004a.roke.co.uk>
References: <3F2E01E1D7B04F4EBEC92D3FA324D8803857FC@rsys004a.roke.co.uk>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <550877E8-420B-11D9-82C1-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Date: Mon, 29 Nov 2004 14:34:02 +0100
To: "'rohc@ietf.org'" <rohc@ietf.org>,
        Stephen McCann <stephen.mccann@roke.co.uk>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
Cc: Mark West <mark.a.west@roke.co.uk>,
        Andrew McDonald <andrew.mcdonald@roke.co.uk>,
        "'Bernard Aboba'" <aboba@INTERNAUT.COM>,
        Carsten Bormann <cabo@tzi.org>,
        Robert Hancock <robert.hancock@roke.co.uk>,
        Eleanor Hepworth <eleanor.hepworth@roke.co.uk>
Subject: [rohc] Re: Review of draft-bormann-rohc-over-802-00.txt
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit

On Nov 29 2004, at 12:28 Uhr, McCann, Stephen wrote:

> Carsten,
> 	I've only had a short time to quickly look at your I-D, but
> one thing that I did want to ask, is the applicability of this
> scheme to both IEEE 802.5 and 802.17, in that these are not
> ethernet based systems.
>
> I know that the 'iporpr' wg is doing some work in this area, but
> I just wondered if your I-D only refers to 802 media which support
> the ethernet type?

Stephen,

thank you for that comment; I've completely stopped thinking about 
rings.
While the discussion is framed in terms of the more visible 802 
standards, the intention indeed is to cover all 802-style L2s that 
commonly might be concatenated by bridge-like L2-only units (including 
even the non-802 FDDI, as this may form part of a bridged L2 path that 
leads to a wireless access point).
Since the solution (subset) proposed uses an LLC-style length field, I 
believe it does apply to 802.5 (but then I've never actually worked 
with 802.5, so I'm not sure).
In particular, I don't know how source-routing would interact with any 
negotiation/announce protocol.

I don't know enough about 802.17 to comment (I was under the impression 
that 802.17 is ethertype-based, though).

> PS : I have the same problems on the IEEE 802 side with IEEE 802.21

How do these problems manifest themselves in 802.21?

Gruesse, Carsten


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


From rohc-bounces@ietf.org  Mon Nov 29 13:28:05 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17153
	for <rohc-web-archive@ietf.org>; Mon, 29 Nov 2004 13:28:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CYqKp-0008CW-QO
	for rohc-web-archive@ietf.org; Mon, 29 Nov 2004 13:33:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYq7t-0003AV-Ot; Mon, 29 Nov 2004 13:19:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYq7N-00034M-Q7
	for rohc@megatron.ietf.org; Mon, 29 Nov 2004 13:19:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16464
	for <rohc@ietf.org>; Mon, 29 Nov 2004 13:19:18 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYqCK-00081B-EG
	for rohc@ietf.org; Mon, 29 Nov 2004 13:24:28 -0500
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iATIJHo13261; Mon, 29 Nov 2004 20:19:18 +0200 (EET)
X-Scanned: Mon, 29 Nov 2004 20:22:41 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks001.ntc.nokia.com (8.12.9/8.12.9) id iATIMf2C031270;
	Mon, 29 Nov 2004 20:22:41 +0200
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks001.ntc.nokia.com 008cPvGT; Mon, 29 Nov 2004 20:22:39 EET
Received: from daebh001.NOE.Nokia.com (daebh001.americas.nokia.com
	[10.241.35.121])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iATIJ6a05162; Mon, 29 Nov 2004 20:19:06 +0200 (EET)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by
	daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Mon, 29 Nov 2004 12:18:08 -0600
content-class: urn:content-classes:message
Subject: RE: [rohc] The discussion on slope(s)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 29 Nov 2004 13:18:07 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B82891AA@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] The discussion on slope(s)
Thread-Index: AcTS3/E4ilFZbCiES4G6PWz9f3ocogDVn0IA
To: <lars-erik.jonsson@ericsson.com>, <rohc@ietf.org>
X-OriginalArrivalTime: 29 Nov 2004 18:18:08.0238 (UTC)
	FILETIME=[C6F400E0:01C4D63F]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Content-Transfer-Encoding: quoted-printable
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Content-Transfer-Encoding: quoted-printable

Lars-Erik and Others,

I'd like to propose to keep the implicit (or learned) slopes=20
in 3095 and clarify it in the implementer's guide. It's not
a waste of time.

1) This seemed to be the conclusion back in March/April, after=20
a long and good discussion among many people.

2) Resource limitation should not be a problem (if it has been).=20
I can volunteer to write the clarification text in the=20
implementer's guide. And I believe there are other people on
this list wanting to contribute.

3) Technically, the need of implicit slopes have been well explained
with many examples. The last email on that was between Pawel and me:
http://www1.ietf.org/mail-archive/web/rohc/current/msg02138.html.
Kamal also agreed with me.
http://www1.ietf.org/mail-archive/web/rohc/current/msg02100.html
After that, I don't see any emails of counter argument.=20

4) The confusion was not only about implicit slope. It is also
about the fundamental encoding of 3095, such as the separation=20
between scale and compression of scaled TS, the difference between=20
TS_STRIDE and slope. They should be clarified in the implementer's
guide. (I remember I have answered almost every question on the
list back in March/April.)

5) Many other issues have already been clarified in March/April =
discussion:
- The learned slope *was* part of RFC 3095, as agreed among authors:
http://www1.ietf.org/mail-archive/web/rohc/current/msg02078.html
- TS can be compressed after scaling or can be compressed without =
scaling:
http://www1.ietf.org/mail-archive/web/rohc/current/msg02077.html
- Why different interpretations didn't catch fire during inter-op tests?
http://www1.ietf.org/mail-archive/web/rohc/current/msg02122.html

BR, Zhigang

> -----Original Message-----
> From: rohc-bounces@ietf.org [mailto:rohc-bounces@ietf.org]On Behalf Of
> ext Lars-Erik Jonsson (LU/EAB)
> Sent: 25 November, 2004 05:08 AM
> To: 'rohc@ietf.org'
> Subject: [rohc] The discussion on slope(s)
>=20
>=20
> ROHCers,
>=20
> In Washington DC, we had a discussion about the 3095 slope
> problem, which still is an open issue for the implementer's
> guide to clarify, if we want to ensure interoperability. My
> initial opinion was that the previous discussions on the list
> indicated we would have to do a careful study of this to be
> able to get consensus, and write a draft explaining both
> operations (with and without implicit slopes). However, the
> sense of the room I got was that we should not waste too
> much effort on this, but actually declare implicit slopes as=20
> not to be part of 3095, and in the implementer's guide just
> point out the text parts of 3095 that caused this confusion
> and clarify accordingly. Although I personally agree with
> this approach and believe it is the only reasonable way to
> go, I will not propose any text for the implementer's guide
> before there is consensus to go with the proposed approach.
>=20
> Therefore, I ask for opinions on this, more or less
> elaborated. See it as a HUM, with possibility to provide
> more details.=20
>=20
> To find the previous ROHC list discussion on slopes, please
> refer to the archives from March 17 to April 16 this year.
>=20
> This is currently the only open issue for the implementer's
> guide and I need your help to get this resolved.
>=20
> Thanks!
> /L-E
>=20
> -----------------------------------
> Lars-Erik Jonsson, M.Sc.
> Senior Research Engineer
> Wireless IP Optimizations
> AWARE - Advanced Wireless Algorithm Research
> Ericsson Research, Corporate Unit
> Ericsson AB
> Box 920, S-971 28 Lule=E5, Sweden
> E-mail: lars-erik.jonsson@ericsson.com                      /"\
> Phone: +46 8 404 29 61                                      \ /
> Fax: +46 920 996 21               ASCII Ribbon Campaign      X
> Home: +46 920 999 57           against HTML email & vCards  / \
>=20
> My opinions are my personal opinions and should not be considered
> as the opinions of my employer, if not explicitly stated.
>=20
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
>=20

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


From rohc-bounces@ietf.org  Tue Nov 30 07:02:47 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09940
	for <rohc-web-archive@ietf.org>; Tue, 30 Nov 2004 07:02:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZ6nU-0001ZL-Lo
	for rohc-web-archive@ietf.org; Tue, 30 Nov 2004 07:08:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZ6Xu-0001q1-Fa; Tue, 30 Nov 2004 06:51:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZ6OC-0008C5-2R
	for rohc@megatron.ietf.org; Tue, 30 Nov 2004 06:41:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08791
	for <rohc@ietf.org>; Tue, 30 Nov 2004 06:41:45 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZ6T8-0001CS-3Q
	for rohc@ietf.org; Tue, 30 Nov 2004 06:47:04 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAUBfZR2011640 for <rohc@ietf.org>; Tue, 30 Nov 2004 12:41:35 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 30 Nov 2004 12:41:35 +0100
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service
	(5.5.2657.72) id <XVC4S0GQ>; Tue, 30 Nov 2004 12:41:35 +0100
Message-ID: <A943FD84BD9ED41193460008C79180500C57067B@ESEALNT419.al.sw.ericsson.se>
From: "Ghyslain Pelletier (LU/EAB)" <ghyslain.pelletier@ericsson.com>
To: "'zhigang.c.liu@nokia.com'" <zhigang.c.liu@nokia.com>,
        "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>,
        rohc@ietf.org
Subject: RE: [rohc] The discussion on slope(s)
Date: Tue, 30 Nov 2004 12:41:33 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 30 Nov 2004 11:41:35.0236 (UTC)
	FILETIME=[8BA1C440:01C4D6D1]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by eagle.ericsson.se id
	iAUBfZR2011640
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21be852dc93f0971708678c18d38c096
Content-Transfer-Encoding: quoted-printable
Cc: "'cabo@tzi.org'" <cabo@tzi.org>
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d
Content-Transfer-Encoding: quoted-printable

Carsten, Lars-Erik, Zhigang,

In addition to the discussions at the last IETF meeting, the mail discuss=
ions that occurred back in March/April referred to in the included mail i=
n my opinion rather suggests that implicit (or learned) slopes NOT be spe=
cified/added as they aren't today anyway present in RFC3095. I seem to re=
call that a number of opinions along this line were seen on the list, in =
addition to many technical issues behing raised.

In any case, my understanding of the previous discussions on this topic w=
as that we couldn't reach a conclusion, so I would say that the conclusio=
ns in the included mail are premature.

> 1) This seemed to be the conclusion back in March/April, after=20
> a long and good discussion among many people.

I certainly don't recall such an homogeneous conclusion.
I think many gave up the discussion because it started
being venomous.

> 2) Resource limitation should not be a problem (if it has been).=20

I don't think that was part of the main issues at all!?

> 3) Technically, the need of implicit slopes have been well explained

To clarify this, there is no _need_ for this, the current 3095 not having
implicit slopes works well. So it is not something that is missing in the
specification and that should now be added.

> 4) The confusion was not only about implicit slope. It is also

Implicit slope is what introduced the confusion, with the unfortunate hel=
p
of some unfortunate editorial mishaps.

> 5) Many other issues have already been clarified in=20
> March/April discussion:
> - The learned slope *was* part of RFC 3095, as agreed among authors:
> http://www1.ietf.org/mail-archive/web/rohc/current/msg02078.html

How can you refer to your own mail to state that authors agreed?
I have definitely heard the opposite from other authors, and I hope
they will contribute to this thread.

Best regards,

/Ghyslain



> -----Original Message-----
> From: rohc-bounces@ietf.org [mailto:rohc-bounces@ietf.org]On Behalf Of
> zhigang.c.liu@nokia.com
> Sent: den 29 november 2004 19:18
> To: Lars-Erik Jonsson (LU/EAB); rohc@ietf.org
> Subject: RE: [rohc] The discussion on slope(s)
>=20
>=20
> Lars-Erik and Others,
>=20
> I'd like to propose to keep the implicit (or learned) slopes=20
> in 3095 and clarify it in the implementer's guide. It's not
> a waste of time.
>=20
> 1) This seemed to be the conclusion back in March/April, after=20
> a long and good discussion among many people.
>=20
> 2) Resource limitation should not be a problem (if it has been).=20
> I can volunteer to write the clarification text in the=20
> implementer's guide. And I believe there are other people on
> this list wanting to contribute.
>=20
> 3) Technically, the need of implicit slopes have been well explained
> with many examples. The last email on that was between Pawel and me:
> http://www1.ietf.org/mail-archive/web/rohc/current/msg02138.html.
> Kamal also agreed with me.
> http://www1.ietf.org/mail-archive/web/rohc/current/msg02100.html
> After that, I don't see any emails of counter argument.=20
>=20
> 4) The confusion was not only about implicit slope. It is also
> about the fundamental encoding of 3095, such as the separation=20
> between scale and compression of scaled TS, the difference between=20
> TS_STRIDE and slope. They should be clarified in the implementer's
> guide. (I remember I have answered almost every question on the
> list back in March/April.)
>=20
> 5) Many other issues have already been clarified in=20
> March/April discussion:
> - The learned slope *was* part of RFC 3095, as agreed among authors:
> http://www1.ietf.org/mail-archive/web/rohc/current/msg02078.html
> - TS can be compressed after scaling or can be compressed=20
> without scaling:
> http://www1.ietf.org/mail-archive/web/rohc/current/msg02077.html
> - Why different interpretations didn't catch fire during=20
> inter-op tests?
> http://www1.ietf.org/mail-archive/web/rohc/current/msg02122.html
>=20
> BR, Zhigang
>=20
> > -----Original Message-----
> > From: rohc-bounces@ietf.org=20
> [mailto:rohc-bounces@ietf.org]On Behalf Of
> > ext Lars-Erik Jonsson (LU/EAB)
> > Sent: 25 November, 2004 05:08 AM
> > To: 'rohc@ietf.org'
> > Subject: [rohc] The discussion on slope(s)
> >=20
> >=20
> > ROHCers,
> >=20
> > In Washington DC, we had a discussion about the 3095 slope
> > problem, which still is an open issue for the implementer's
> > guide to clarify, if we want to ensure interoperability. My
> > initial opinion was that the previous discussions on the list
> > indicated we would have to do a careful study of this to be
> > able to get consensus, and write a draft explaining both
> > operations (with and without implicit slopes). However, the
> > sense of the room I got was that we should not waste too
> > much effort on this, but actually declare implicit slopes as=20
> > not to be part of 3095, and in the implementer's guide just
> > point out the text parts of 3095 that caused this confusion
> > and clarify accordingly. Although I personally agree with
> > this approach and believe it is the only reasonable way to
> > go, I will not propose any text for the implementer's guide
> > before there is consensus to go with the proposed approach.
> >=20
> > Therefore, I ask for opinions on this, more or less
> > elaborated. See it as a HUM, with possibility to provide
> > more details.=20
> >=20
> > To find the previous ROHC list discussion on slopes, please
> > refer to the archives from March 17 to April 16 this year.
> >=20
> > This is currently the only open issue for the implementer's
> > guide and I need your help to get this resolved.
> >=20
> > Thanks!
> > /L-E
> >=20
> > -----------------------------------
> > Lars-Erik Jonsson, M.Sc.
> > Senior Research Engineer
> > Wireless IP Optimizations
> > AWARE - Advanced Wireless Algorithm Research
> > Ericsson Research, Corporate Unit
> > Ericsson AB
> > Box 920, S-971 28 Lule=E5, Sweden
> > E-mail: lars-erik.jonsson@ericsson.com                      /"\
> > Phone: +46 8 404 29 61                                      \ /
> > Fax: +46 920 996 21               ASCII Ribbon Campaign      X
> > Home: +46 920 999 57           against HTML email & vCards  / \
> >=20
> > My opinions are my personal opinions and should not be considered
> > as the opinions of my employer, if not explicitly stated.
> >=20
> > _______________________________________________
> > Rohc mailing list
> > Rohc@ietf.org
> > https://www1.ietf.org/mailman/listinfo/rohc
> >=20
>=20
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www1.ietf.org/mailman/listinfo/rohc
>=20

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


From rohc-bounces@ietf.org  Tue Nov 30 12:39:40 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12125
	for <rohc-web-archive@ietf.org>; Tue, 30 Nov 2004 12:39:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZC3i-0001br-NM
	for rohc-web-archive@ietf.org; Tue, 30 Nov 2004 12:45:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZBpO-00074i-CG; Tue, 30 Nov 2004 12:30:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZBbc-0001c5-TW
	for rohc@megatron.ietf.org; Tue, 30 Nov 2004 12:16:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08491
	for <rohc@ietf.org>; Tue, 30 Nov 2004 12:15:58 -0500 (EST)
From: zhigang.c.liu@nokia.com
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZBgl-0000p7-N2
	for rohc@ietf.org; Tue, 30 Nov 2004 12:21:20 -0500
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAUHFov13171; Tue, 30 Nov 2004 19:15:51 +0200 (EET)
X-Scanned: Tue, 30 Nov 2004 19:15:25 +0200 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id iAUHFPXj015332;
	Tue, 30 Nov 2004 19:15:25 +0200
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks002.ntc.nokia.com 006K1Vl2; Tue, 30 Nov 2004 19:15:22 EET
Received: from daebh001.NOE.Nokia.com (daebh001.americas.nokia.com
	[10.241.35.121])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	iAUGfBS27870; Tue, 30 Nov 2004 18:41:11 +0200 (EET)
Received: from ajebe001.NOE.Nokia.com ([172.18.151.16]) by
	daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Tue, 30 Nov 2004 10:41:06 -0600
content-class: urn:content-classes:message
Subject: RE: [rohc] The discussion on slope(s)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Tue, 30 Nov 2004 11:41:05 -0500
Message-ID: <7B5AF06E216CB74DA8A5960A3181B5B82891AE@ajebe001.americas.nokia.com>
Thread-Topic: [rohc] The discussion on slope(s)
Thread-Index: AcTW0mvGQ9z6scU1QPub8FCYQCgsIgAHrGwQ
To: <ghyslain.pelletier@ericsson.com>, <lars-erik.jonsson@ericsson.com>,
        <rohc@ietf.org>
X-OriginalArrivalTime: 30 Nov 2004 16:41:06.0978 (UTC)
	FILETIME=[639FF820:01C4D6FB]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 25eb6223a37c19d53ede858176b14339
Content-Transfer-Encoding: quoted-printable
Cc: cabo@tzi.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 995b2e24d23b953c94bac5288c432399
Content-Transfer-Encoding: quoted-printable

Ghyslian,

> > 1) This seemed to be the conclusion back in March/April, after=20
> > a long and good discussion among many people.
>=20
> I certainly don't recall such an homogeneous conclusion.
> I think many gave up the discussion because it started
> being venomous.

I don't know why you call the discussion venomous. I have proposed
and most people have been sticking to the technical substance.=20
The discussion stopped because there were no more counter
arguments against learned slope.=20

> > 3) Technically, the need of implicit slopes have been well explained
>=20
> To clarify this, there is no _need_ for this, the current=20
> 3095 not having implicit slopes works well. So it is not something =
that is=20
> missing in the specification and that should now be added.

I'd suggest you to read the examples and comment directly on them.

It's clear that different people have different interpretations
of what is "current 3095". Some people implemented learned slope
while others didn't. However, learned slope is not something new.=20
It has been discussed and agreed when we wrote up RFC 3095 (see
below). Unfortunately, it was not written clearly enough.

> > 5) Many other issues have already been clarified in=20
> > March/April discussion:
> > - The learned slope *was* part of RFC 3095, as agreed among authors:
> > http://www1.ietf.org/mail-archive/web/rohc/current/msg02078.html
>=20
> How can you refer to your own mail to state that authors agreed?
> I have definitely heard the opposite from other authors, and I hope
> they will contribute to this thread.

My email has references to earlier email discussions between Mikael=20
and me. It demonstrates that learned slope was agreed upon when we were=20
writing up the encoding of 3095. We didn't hear disagreement at that
time on the mailing list, including those from other 3095 authors.

BR, Zhigang

> Best regards,
>=20
> /Ghyslain
>=20
>=20
>=20
> > -----Original Message-----
> > From: rohc-bounces@ietf.org=20
> [mailto:rohc-bounces@ietf.org]On Behalf Of
> > zhigang.c.liu@nokia.com
> > Sent: den 29 november 2004 19:18
> > To: Lars-Erik Jonsson (LU/EAB); rohc@ietf.org
> > Subject: RE: [rohc] The discussion on slope(s)
> >=20
> >=20
> > Lars-Erik and Others,
> >=20
> > I'd like to propose to keep the implicit (or learned) slopes=20
> > in 3095 and clarify it in the implementer's guide. It's not
> > a waste of time.
> >=20
> > 1) This seemed to be the conclusion back in March/April, after=20
> > a long and good discussion among many people.
> >=20
> > 2) Resource limitation should not be a problem (if it has been).=20
> > I can volunteer to write the clarification text in the=20
> > implementer's guide. And I believe there are other people on
> > this list wanting to contribute.
> >=20
> > 3) Technically, the need of implicit slopes have been well explained
> > with many examples. The last email on that was between Pawel and me:
> > http://www1.ietf.org/mail-archive/web/rohc/current/msg02138.html.
> > Kamal also agreed with me.
> > http://www1.ietf.org/mail-archive/web/rohc/current/msg02100.html
> > After that, I don't see any emails of counter argument.=20
> >=20
> > 4) The confusion was not only about implicit slope. It is also
> > about the fundamental encoding of 3095, such as the separation=20
> > between scale and compression of scaled TS, the difference between=20
> > TS_STRIDE and slope. They should be clarified in the implementer's
> > guide. (I remember I have answered almost every question on the
> > list back in March/April.)
> >=20
> > 5) Many other issues have already been clarified in=20
> > March/April discussion:
> > - The learned slope *was* part of RFC 3095, as agreed among authors:
> > http://www1.ietf.org/mail-archive/web/rohc/current/msg02078.html
> > - TS can be compressed after scaling or can be compressed=20
> > without scaling:
> > http://www1.ietf.org/mail-archive/web/rohc/current/msg02077.html
> > - Why different interpretations didn't catch fire during=20
> > inter-op tests?
> > http://www1.ietf.org/mail-archive/web/rohc/current/msg02122.html
> >=20
> > BR, Zhigang
> >=20
> > > -----Original Message-----
> > > From: rohc-bounces@ietf.org=20
> > [mailto:rohc-bounces@ietf.org]On Behalf Of
> > > ext Lars-Erik Jonsson (LU/EAB)
> > > Sent: 25 November, 2004 05:08 AM
> > > To: 'rohc@ietf.org'
> > > Subject: [rohc] The discussion on slope(s)
> > >=20
> > >=20
> > > ROHCers,
> > >=20
> > > In Washington DC, we had a discussion about the 3095 slope
> > > problem, which still is an open issue for the implementer's
> > > guide to clarify, if we want to ensure interoperability. My
> > > initial opinion was that the previous discussions on the list
> > > indicated we would have to do a careful study of this to be
> > > able to get consensus, and write a draft explaining both
> > > operations (with and without implicit slopes). However, the
> > > sense of the room I got was that we should not waste too
> > > much effort on this, but actually declare implicit slopes as=20
> > > not to be part of 3095, and in the implementer's guide just
> > > point out the text parts of 3095 that caused this confusion
> > > and clarify accordingly. Although I personally agree with
> > > this approach and believe it is the only reasonable way to
> > > go, I will not propose any text for the implementer's guide
> > > before there is consensus to go with the proposed approach.
> > >=20
> > > Therefore, I ask for opinions on this, more or less
> > > elaborated. See it as a HUM, with possibility to provide
> > > more details.=20
> > >=20
> > > To find the previous ROHC list discussion on slopes, please
> > > refer to the archives from March 17 to April 16 this year.
> > >=20
> > > This is currently the only open issue for the implementer's
> > > guide and I need your help to get this resolved.
> > >=20
> > > Thanks!
> > > /L-E
> > >=20
> > > -----------------------------------
> > > Lars-Erik Jonsson, M.Sc.
> > > Senior Research Engineer
> > > Wireless IP Optimizations
> > > AWARE - Advanced Wireless Algorithm Research
> > > Ericsson Research, Corporate Unit
> > > Ericsson AB
> > > Box 920, S-971 28 Lule=E5, Sweden
> > > E-mail: lars-erik.jonsson@ericsson.com                      /"\
> > > Phone: +46 8 404 29 61                                      \ /
> > > Fax: +46 920 996 21               ASCII Ribbon Campaign      X
> > > Home: +46 920 999 57           against HTML email & vCards  / \
> > >=20
> > > My opinions are my personal opinions and should not be considered
> > > as the opinions of my employer, if not explicitly stated.
> > >=20
> > > _______________________________________________
> > > Rohc mailing list
> > > Rohc@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/rohc
> > >=20
> >=20
> > _______________________________________________
> > Rohc mailing list
> > Rohc@ietf.org
> > https://www1.ietf.org/mailman/listinfo/rohc
> >=20
>=20

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


From rohc-bounces@ietf.org  Tue Nov 30 21:54:11 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16752
	for <rohc-web-archive@ietf.org>; Tue, 30 Nov 2004 21:54:10 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZKiO-00037X-Ua
	for rohc-web-archive@ietf.org; Tue, 30 Nov 2004 21:59:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZKZH-00070m-HG; Tue, 30 Nov 2004 21:50:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZKYW-0006Yj-7u
	for rohc@megatron.ietf.org; Tue, 30 Nov 2004 21:49:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16023
	for <rohc@ietf.org>; Tue, 30 Nov 2004 21:49:22 -0500 (EST)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZKdk-0002ye-Jz
	for rohc@ietf.org; Tue, 30 Nov 2004 21:54:49 -0500
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	iB12nCO7002454; Wed, 1 Dec 2004 03:49:14 +0100 (MET)
In-Reply-To: <7B5AF06E216CB74DA8A5960A3181B5B82891AE@ajebe001.americas.nokia.com>
References: <7B5AF06E216CB74DA8A5960A3181B5B82891AE@ajebe001.americas.nokia.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <946FF734-4343-11D9-82C1-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rohc] The discussion on slope(s)
Date: Wed, 1 Dec 2004 03:49:11 +0100
To: <zhigang.c.liu@nokia.com>
X-Mailer: Apple Mail (2.619)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, rohc@ietf.org,
        lars-erik.jonsson@ericsson.com, ghyslain.pelletier@ericsson.com
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>,
	<mailto:rohc-request@ietf.org?subject=subscribe>
Sender: rohc-bounces@ietf.org
Errors-To: rohc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit

> It's clear that different people have different interpretations
> of what is "current 3095". Some people implemented learned slope
> while others didn't. However, learned slope is not something new.
> It has been discussed and agreed when we wrote up RFC 3095 (see
> below). Unfortunately, it was not written clearly enough.

Zhigang,

as far as I understand the current discussion, it is not about whether 
3095 is clear about dynamic slopes (it clearly isn't) -- it is about 
whether dynamic slopes made it into 3095 at all.
We have discussed many mechanisms during the development of 3095, not 
all of which made it into the specification.

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

Gruesse, Carsten


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


