[rohc] Query regarding the LSB encoding in TCP Profile

Anil Maguluri <Anil.Maguluri@lntinfotech.com> Fri, 26 March 2010 05:50 UTC

Return-Path: <Anil.Maguluri@lntinfotech.com>
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B30B3A6945 for <rohc@core3.amsl.com>; Thu, 25 Mar 2010 22:50:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.472
X-Spam-Level:
X-Spam-Status: No, score=-1.472 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yVff3AYpiZlC for <rohc@core3.amsl.com>; Thu, 25 Mar 2010 22:50:19 -0700 (PDT)
Received: from mail96.messagelabs.com (mail96.messagelabs.com [216.82.254.19]) by core3.amsl.com (Postfix) with ESMTP id 8F4AF3A68E0 for <rohc@ietf.org>; Thu, 25 Mar 2010 22:50:12 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: Anil.Maguluri@lntinfotech.com
X-Msg-Ref: server-5.tower-96.messagelabs.com!1269581958!78100771!11
X-StarScan-Version: 6.2.4; banners=lntinfotech.com,-,-
X-Originating-IP: [203.101.96.7]
Received: (qmail 16952 invoked from network); 26 Mar 2010 05:50:31 -0000
Received: from unknown (HELO BLRINMSHTCAS01.bglrodc.lntinfotech.com) (203.101.96.7) by server-5.tower-96.messagelabs.com with AES128-SHA encrypted SMTP; 26 Mar 2010 05:50:31 -0000
Received: from blrinmsmbx01.bglrodc.lntinfotech.com ([169.254.1.247]) by BLRINMSHTCAS01.bglrodc.lntinfotech.com ([172.28.0.81]) with mapi; Fri, 26 Mar 2010 11:15:54 +0530
From: Anil Maguluri <Anil.Maguluri@lntinfotech.com>
To: "rohc@ietf.org" <rohc@ietf.org>
Date: Fri, 26 Mar 2010 11:15:49 +0530
Thread-Topic: Query regarding the LSB encoding in TCP Profile
Thread-Index: AcrMp5aIBrYaQgwRThO66og0wqhV2Q==
Message-ID: <C7232BDB534C6241BE85C96D129205D002F41D1A91@BLRINMSMBX01.bglrodc.lntinfotech.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C7232BDB534C6241BE85C96D129205D002F41D1A91BLRINMSMBX01b_"
MIME-Version: 1.0
Cc: Anil Maguluri <Anil.Maguluri@lntinfotech.com>, Anil Kumar Maguluri <anilmaguluri@gmail.com>
Subject: [rohc] Query regarding the LSB encoding in TCP Profile
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2010 05:50:23 -0000

HI All,

Please clarify me the below queries regarding the LSB encoding in TCP Profile.

The below statements in RFC 4996 are confusing, please clarify me.

Statement-1
In RFC 4996, Page 43, under TCP Sequence Number:
" Also, for ROHC-TCP to be robust to losses, two additional bits are added to the LSB encoding of the sequence number. This
means that the base headers should contain at least 14 bits of LSB-encoded sequence number when present. According to the
logic above, the LSB offset value is set to be as large as the positive offset, i.e., p = 2^(k-1)-1. "

Statement-2
In RFC 4996, Page 81, in the compressed packet formats are represented as below:
// Send LSBs of sequence number
COMPRESSED rnd_1 {
Discriminator    =:= '101110' [ 6 ];
seq_number      =:= lsb(18, 65535) [ 18 ];
msn                       =:= lsb(4, 4) [ 4 ];
psh_flag               =:= irregular(1) [ 1 ];
header_crc         =:= crc3(THIS.UVALUE, THIS.ULENGTH) [ 3 ];
ENFORCE((ip_id_behavior.UVALUE == IP_ID_BEHAVIOR_RANDOM) ||
(ip_id_behavior.UVALUE == IP_ID_BEHAVIOR_ZERO));
}

As per my understanding, we have to use offset param value (RFC 4997, page 27) as 65535 to compress the seq_number to select
The rnd_1 packet. Is it right? If my understanding is right, then what is the use of p=2^(k-1)-1?

Also please explain me the below statement which is present in RFC 4997, page 27.
For example, the TCP sequence number:
tcp_sequence_number =:= lsb(14, 8192);
This takes up 14 bits, and can communicate any value that is between 8192 lower than the value of the field stored in context and 8191
above it.

Thanks for your support.

Regards,
Anil Kumar Maguluri

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

______________________________________________________________________