[rohc] TCP/IP EPIC profile

"Maja" <kiki@fesb.hr> Mon, 04 March 2002 16:32 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01212 for <rohc-archive@odin.ietf.org>; Mon, 4 Mar 2002 11:32:40 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA08740; Mon, 4 Mar 2002 11:27:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA08713 for <rohc@ns.ietf.org>; Mon, 4 Mar 2002 11:27:56 -0500 (EST)
Received: from marjan.fesb.hr (root@marjan.fesb.hr [161.53.166.3]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00889 for <rohc@ietf.org>; Mon, 4 Mar 2002 11:27:49 -0500 (EST)
Received: (from root@localhost) by marjan.fesb.hr (8.9.3/8.9.3) id RAA25435 for rohc@ietf.org; Mon, 4 Mar 2002 17:27:45 +0100 (MET)
Received: from laris5 (laris5.fesb.hr [161.53.166.253]) by marjan.fesb.hr (8.9.3/8.9.3) with SMTP id RAA25426; Mon, 4 Mar 2002 17:27:36 +0100 (MET)
Message-ID: <005b01c1c39a$512f2a70$fda635a1@fesb.hr>
From: "Maja" <kiki@fesb.hr>
To: "rohc" <rohc@ietf.org>
Cc: "Surtees, Abigail" <abigail.surtees@roke.co.uk>, "West, Mark \(ITN\)" <mark.a.west@roke.co.uk>
Date: Mon, 4 Mar 2002 17:33:29 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0058_01C1C3A2.B2C72B40"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Virus-Scanned: by AMaViS perl-11
Subject: [rohc] TCP/IP EPIC profile
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Robust Header Compression <rohc.ietf.org>
X-BeenThere: rohc@ietf.org

Hi all,
some points in the latest TCP/IP Header Compression for ROHC (ROHC-TCP) 
draft from January are not clear (OK. Not clear to me ).

First is the definition of the U ( ) method called for TCP options, for example:
 
  tcp-options-co  =    ROTATE(3,1) ; get TCP data offset 
                        LIST(4,1,32,-160,8, 
                           U(OPTIONAL(tcp-sack-co)), 
                           U(OPTIONAL(tcp-timestamp-co)), 
                           U(OPTIONAL(tcp-mss)), 
                           U(OPTIONAL(tcp-end)), 
                           U(OPTIONAL(tcp-wscale)), 
                           U(OPTIONAL(sack-permitted)), 
                           U(OPTIONAL(tcp-generic-co)), 
                           U(OPTIONAL(tcp-generic-co)), 
                           5,8,2,0,3,4) 
 
We couldn't find it in none of the EPIC or ROHC drafts.
And the second point is why is it, in the method LIST, twice included tcp-generic-co ( OR for IR/DYN tcp-generic-dyn).
We suppose that is the method which is called if the value in 8 bits is none of 6 values stated at the end of method, but why twice?
 
Cheers,

Maja & Ivana