Re: [rohc] Clarification regarding the ESP SN Encoding

Klaus Warnke <klaus.warnke@acticom.de> Wed, 16 June 2010 11:03 UTC

Return-Path: <klaus.warnke@acticom.de>
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 C89E928C10F for <rohc@core3.amsl.com>; Wed, 16 Jun 2010 04:03:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, OBSCURED_EMAIL=0.001]
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 EsJBVfax9jI7 for <rohc@core3.amsl.com>; Wed, 16 Jun 2010 04:03:35 -0700 (PDT)
Received: from mail.acticom-networks.com (mail.acticom-networks.com [87.106.254.214]) by core3.amsl.com (Postfix) with ESMTP id 9BCDE28C10D for <rohc@ietf.org>; Wed, 16 Jun 2010 04:03:35 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.acticom-networks.com (Postfix) with ESMTP id 7F9851C00174; Wed, 16 Jun 2010 13:03:39 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at acticom-networks.com
Received: from mail.acticom-networks.com ([127.0.0.1]) by localhost (mail.acticom-networks.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fmkm17IrVexO; Wed, 16 Jun 2010 13:03:38 +0200 (CEST)
Received: from godfather.bln.acticom.de (mail.oosoft.net [212.99.204.33]) by mail.acticom-networks.com (Postfix) with ESMTP id CC64C1C00420; Wed, 16 Jun 2010 13:03:38 +0200 (CEST)
Received: from TORNADO.acticom.de (tornado.bln.acticom.de [192.168.33.27]) by godfather.bln.acticom.de (Postfix) with ESMTP id 46DC6F3AD0; Wed, 16 Jun 2010 13:03:38 +0200 (CEST)
Date: Wed, 16 Jun 2010 13:03:38 +0200
Message-ID: <usk4n9r3p.wl%klaus.warnke@acticom.de>
From: Klaus Warnke <klaus.warnke@acticom.de>
To: Anil Maguluri <Anil.Maguluri@lntinfotech.com>
In-Reply-To: <903D13EA90218E43BA0881BC8B569C7D230903D6@BLRINMSMBX01.bglrodc.lntinfotech.com>
References: <903D13EA90218E43BA0881BC8B569C7D230903D6@BLRINMSMBX01.bglrodc.lntinfotech.com>
User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.7 Emacs/22.2 (i386-mingw-nt6.0.6002) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: "rohc@ietf.org" <rohc@ietf.org>, 'Anil Kumar Maguluri' <anilmaguluri@gmail.com>
Subject: Re: [rohc] Clarification regarding the ESP SN Encoding
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: Wed, 16 Jun 2010 11:03:36 -0000

Hello Anil,

if I remember correct, RoHCv1 requires, that the link layer delivers
all packets in order (RoHCv2 not).

For p see 5.12.:

  The interpretation interval (value of p) for the ESP-based SN is as
  with ROHC RTP (profile 0x0001).

Therefore p is as 5.7.:

  p = 1                   if bits(SN) <= 4
  p = 2^(bits(SN)-5) - 1  if bits(SN) >  4

Regards, Klaus

At Wed, 16 Jun 2010 12:32:18 +0530,
Anil Maguluri wrote:
> Currently I am working on ROHCv1 Profile-3 (ESP/IP).
> 
> Please let me know whether my understanding is right or not
> regarding the ESP SN Encoding.
> 
> As per RFC 3095, 4.5.1, " The parameter p is introduced so that the
> interpretation interval can be shifted with respect to v_ref.
> Choosing a good value for p will yield a more efficient encoding for
> fields with certain characteristics. Below are some examples:
> 
> - P = -1           if the field value is expected to increase always
> 
> - p = 0            if the field value is constant or increase
> 
> - p = 2^(k-1) - 1, if the field value is expected to deviate
>                    slightly from a constant
> 
> - p = 2^(k-2) - 1, if the field value is expected to undergo small
>                    negative changes or larger positive changes "
> 
> Also RFC 3095, 5.7, " SN: The compressed RTP Sequence Number.
> Compressed with W-LSB. The interpretation intervals, see section
> 4.5.1, are defined as follows:
>
> p = 1                  if bits(SN) <= 4
> p = 2^(bits(SN)-5) - 1 if bits(SN) > 4 "
> 
> As per my understanding, we should use the below 'p' values at
> compressor [for SN Encoding]
> 
> - p = -1,                if packets are received in-order
> 
> - p = 2^(k-2)-1,         if packets are received out-of-order at 
>                          decompressor
> 
> - p = 1                  if bits(SN) <= 4
> 
> - p = 2^(bits(SN)-5) - 1 if bits(SN) > 4
> 
> 
> Queries
> 
> 1. Is my understanding is right?
> 
> 2. What is the value of 'p' for Profile-3 at compressor and
>    decompressor?  Is it same as above?
> 
> 
> Thanks for your support.
> 
> Regards,
> Anil Kumar Maguluri