
From tellviveks@gmail.com  Sun Mar 27 19:22:28 2011
Return-Path: <tellviveks@gmail.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 2BA973A6783 for <rohc@core3.amsl.com>; Sun, 27 Mar 2011 19:22:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 uKzfZ8MIpSqY for <rohc@core3.amsl.com>; Sun, 27 Mar 2011 19:22:25 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 9752E3A677C for <rohc@ietf.org>; Sun, 27 Mar 2011 19:22:25 -0700 (PDT)
Received: by iwn39 with SMTP id 39so2987258iwn.31 for <rohc@ietf.org>; Sun, 27 Mar 2011 19:24:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=BL2+tQZNGqzDyAedTyJLa5pxQY2uMzOSlOlVwbjaG6s=; b=xfkuhfQ6RtEXslVWs1wyPx5Vot1iAgrr4cLYbM527QFydKoi8RwDQ+QZP2IDZMn1ax Z1Pn7eTg/d1vg0iGn+18iwMJhWtnqaadD2qZtDEB9YxLN7YTvM9mHu2jZpdsNFy7cqt+ FavzV+pJ157PMf0PvvohGrZgcg2WP9+EO5K94=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=bAv0GOXkCeV+cTjMx9APK+ea82ez256cC3ncHX7VBvTBty01stCKcUynLQcioZZzdn EhGkwnDLlEeqXL9hoiaDRgYaekFxEbGJtgOAFcalEfD7RI8QQjjXdRNW450JzldUHXkI +M75AwWkyLYzOhYUJDVhRV9VocKaQO4MlacVY=
MIME-Version: 1.0
Received: by 10.42.115.199 with SMTP id l7mr3483280icq.308.1301279042395; Sun, 27 Mar 2011 19:24:02 -0700 (PDT)
Received: by 10.231.79.9 with HTTP; Sun, 27 Mar 2011 19:24:02 -0700 (PDT)
Date: Mon, 28 Mar 2011 11:24:02 +0900
Message-ID: <BANLkTi==k+rYcygxuPxM_-_ajCWnBEUhgA@mail.gmail.com>
From: Vivek Soni <tellviveks@gmail.com>
To: rohc@ietf.org
Content-Type: multipart/alternative; boundary=20cf303ea6ea135fca049f81a3a7
X-Mailman-Approved-At: Sun, 27 Mar 2011 23:58:32 -0700
Subject: [rohc] RoHC Profile 4 Static chain termination
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: Mon, 28 Mar 2011 02:24:41 -0000

--20cf303ea6ea135fca049f81a3a7
Content-Type: text/plain; charset=ISO-8859-1

Hello,

I understand that the compressor can terminate the static chain at any
header by explicity setting the MSB of version field. But I am not clear
when exactly should compressor do this.

My understanding is that it is applicable only when there are multiple IP
headers and compressor decides to compress only few of them.

Whereas in other cases for example
1. The packet has only one IP header ("Protocol"/"next header" field is
other than IPinIP or IPv6)
2. The packet has multiple IP headers and the compressor compresses all of
them.

In both these cases, the static chain termination is implicit. Therefore the
compressor need not (SHOULD NOT)
indicate the end of static chain explicitly by setting MSB of version field.

Is this understanding of mine correct. In that case, would be it be better
if RFC is more clear about it by using
stronger text like "SHOULD NOT" instead of "Alternatively".

Regards,
Vivek

--20cf303ea6ea135fca049f81a3a7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hello,</div><div><br></div><div><div>I understand that the compressor =
can terminate the static chain at any header by explicity setting=A0the MSB=
 of version field. But I am not clear when exactly should compressor do thi=
s.=A0</div>
<div><br></div><div>My understanding is that it is applicable only when the=
re are multiple IP headers and compressor decides to=A0compress only few of=
 them.=A0</div><div><br></div><div>Whereas in other cases for example</div>
<div>1. The packet has only one IP header (&quot;Protocol&quot;/&quot;next =
header&quot; field is other than IPinIP or IPv6)</div><div>2. The packet ha=
s multiple IP headers and the compressor compresses all of them.</div><div>
<br></div><div>In both these cases, the static chain termination is implici=
t. Therefore the compressor need not (SHOULD NOT)=A0</div><div>indicate the=
 end of static chain explicitly by setting MSB of version field.</div><div>
<br></div><div>Is this understanding of mine correct. In that case, would b=
e it be better if RFC is more clear about it by using</div><div>stronger te=
xt like &quot;SHOULD NOT&quot; instead of &quot;Alternatively&quot;.</div>
<div><br></div><div>Regards,</div><div>Vivek</div></div><div><br></div>

--20cf303ea6ea135fca049f81a3a7--

From carl.knutsson@effnet.com  Mon Mar 28 06:41:58 2011
Return-Path: <carl.knutsson@effnet.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 A01F03A690D for <rohc@core3.amsl.com>; Mon, 28 Mar 2011 06:41:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 SZMWu3JDG5Tu for <rohc@core3.amsl.com>; Mon, 28 Mar 2011 06:41:57 -0700 (PDT)
Received: from lists.levonline.com (lists.levonline.com [217.70.33.37]) by core3.amsl.com (Postfix) with ESMTP id BE8063A6878 for <rohc@ietf.org>; Mon, 28 Mar 2011 06:41:53 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by lists.levonline.com (Postfix) with ESMTP id 35ECF2682CE for <rohc@ietf.org>; Mon, 28 Mar 2011 15:43:30 +0200 (CEST)
Received: from lists.levonline.com ([127.0.0.1]) by localhost (lists.levonline.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3f3vbYVTCim5 for <rohc@ietf.org>; Mon, 28 Mar 2011 15:43:29 +0200 (CEST)
Received: from traktor2.skognet.levonline.com (webhotel.fordon.levonline.com [217.70.32.2]) by lists.levonline.com (Postfix) with ESMTP id 538CB26823B; Mon, 28 Mar 2011 15:43:29 +0200 (CEST)
Received: from [192.168.101.21] (c-b10171d5.04-205-6c756c1.cust.bredbandsbolaget.se [213.113.1.177]) (authenticated bits=0) by traktor2.skognet.levonline.com (8.13.8/8.13.8) with ESMTP id p2SDhS5s008941 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Mar 2011 15:43:28 +0200
Message-ID: <4D90907A.4000405@effnet.com>
Date: Mon, 28 Mar 2011 15:43:22 +0200
From: Carl Knutsson <carl.knutsson@effnet.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Vivek Soni <tellviveks@gmail.com>
References: <BANLkTi==k+rYcygxuPxM_-_ajCWnBEUhgA@mail.gmail.com>
In-Reply-To: <BANLkTi==k+rYcygxuPxM_-_ajCWnBEUhgA@mail.gmail.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: rohc@ietf.org
Subject: Re: [rohc] RoHC Profile 4 Static chain termination
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: Mon, 28 Mar 2011 13:41:58 -0000

Hi Vivek,

I guess you are referring to profile 0x0004 in RFC 3843 section 3.1.

I don't think I understand exactly what you are trying to change or
clarify with your suggestion.

The version field MSB is used to terminate the static chain when it
isn't implicitly given by the next header/protocol field. For example if
you want to compress only the IPv4 header for an IPv4/IPv6 packet. Or do
you want to disqualify the use of the version field static chain
termination in those cases were the end is implicitly given by the
protocol field? In that case the MSB in the IP version field may be
redundant but the compression will function correctly.
In any case I can't really see that this requires a correction or
clarification to the RFC.

Note that this RFC that was published some years ago, so we are not
likely to change it for smaller editorial fixes. We could file an
errata, but at this point I can't see anything in the static chain
termination section that needs a clarification or correction.

cheers,

/Calle


On 03/28/2011 04:24 AM, Vivek Soni wrote:
> Hello,
> 
> I understand that the compressor can terminate the static chain at any
> header by explicity setting the MSB of version field. But I am not clear
> when exactly should compressor do this. 
> 
> My understanding is that it is applicable only when there are multiple
> IP headers and compressor decides to compress only few of them. 
> 
> Whereas in other cases for example
> 1. The packet has only one IP header ("Protocol"/"next header" field is
> other than IPinIP or IPv6)
> 2. The packet has multiple IP headers and the compressor compresses all
> of them.
> 
> In both these cases, the static chain termination is implicit. Therefore
> the compressor need not (SHOULD NOT) 
> indicate the end of static chain explicitly by setting MSB of version field.
> 
> Is this understanding of mine correct. In that case, would be it be
> better if RFC is more clear about it by using
> stronger text like "SHOULD NOT" instead of "Alternatively".
> 
> Regards,
> Vivek
> 
> 
> 
> _______________________________________________
> Rohc mailing list
> Rohc@ietf.org
> https://www.ietf.org/mailman/listinfo/rohc

