RE: [rohc] query: encoding of IP-ID for RND=0 in extn3

Remi Pelland <remi.pelland@octasic.com> Tue, 02 September 2003 13:35 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 JAA23536 for <rohc-archive@odin.ietf.org>; Tue, 2 Sep 2003 09:35:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19uBIn-00011v-LU for rohc-archive@odin.ietf.org; Tue, 02 Sep 2003 09:34:35 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h82DYXhW003950 for rohc-archive@odin.ietf.org; Tue, 2 Sep 2003 09:34:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19uBIn-00011V-0H for rohc-web-archive@optimus.ietf.org; Tue, 02 Sep 2003 09:34:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23318 for <rohc-web-archive@ietf.org>; Tue, 2 Sep 2003 09:34:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19uBIk-0007O1-00 for rohc-web-archive@ietf.org; Tue, 02 Sep 2003 09:34:30 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19uBIg-0007Np-00 for rohc-web-archive@ietf.org; Tue, 02 Sep 2003 09:34:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19uBIf-0000xT-Lq; Tue, 02 Sep 2003 09:34:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19uBID-0000l0-0q for rohc@optimus.ietf.org; Tue, 02 Sep 2003 09:33:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23056 for <rohc@ietf.org>; Tue, 2 Sep 2003 09:33:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19uBIA-0007I1-00 for rohc@ietf.org; Tue, 02 Sep 2003 09:33:54 -0400
Received: from exchsvr.octasic.com ([216.208.79.4]) by ietf-mx with esmtp (Exim 4.12) id 19uBHj-0007GJ-00 for rohc@ietf.org; Tue, 02 Sep 2003 09:33:27 -0400
Received: by EXCHSVR with Internet Mail Service (5.5.2653.19) id <RAYNR9MV>; Tue, 2 Sep 2003 09:30:38 -0400
Message-ID: <F54085DA4E90D511B80B00B0D0D007D26BA7B3@EXCHSVR>
From: Remi Pelland <remi.pelland@octasic.com>
To: "'Alan Kennington'" <ak1.rohc@topology.org>, ROHC mailing list <rohc@ietf.org>
Subject: RE: [rohc] query: encoding of IP-ID for RND=0 in extn3
Date: Tue, 2 Sep 2003 09:30:37 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>

Here's my understanding on this:

The IP-ID field in extension 3 follows the same rules as the IP-ID fields in
base headers: it is encoded based on its offset to the RTP SN and based on
its associated NBO setting.  When the base header conveying the extension 3
contains an IP-ID field (i.e. UO-1-ID in your example), then the IP-ID bits
in the base header become irrelevant since all 16-bits are already available
in the extension (based on the rule defined in RFC 3095, section 4.5.7).

Note also that IP-ID can either be the inner or the outer IP Identification
field.  This is based on the version of the inner and outer (if present) IP
headers and on their respective RND settings.


Anyone, 
	is this correct?


Salut,
Remi.

-----Original Message-----
From: Alan Kennington [mailto:ak1.rohc@topology.org]
Sent: Saturday, August 30, 2003 6:56 AM
To: ROHC mailing list
Subject: [rohc] query: encoding of IP-ID for RND=0 in extn3


I am having some difficulty in interpreting RFC 3095, 5.7, page 75.

============================================================
   IP-ID: A compressed IP-ID field.

      IP-ID fields in compressed base headers carry the compressed IP-ID
      of the innermost IPv4 header whose corresponding RND flag is not
      1.  The rules below assume that the IP-ID is for the innermost IP
      header.  If it is for an outer IP header, the RND2 and NBO2 flags
      are used instead of RND and NBO.

      If value(RND) = 0, hdr(IP-ID) is compressed using Offset IP-ID
      encoding (see section 4.5.5) using p = 0 and default-slope(IP-ID
      offset) = 0.

      If value(RND) = 1, IP-ID is the uncompressed hdr(IP-ID).  IP-ID is
      then passed as additional octets at the end of the compressed
      header, after any extensions.

      If value(NBO) = 0, the octets of hdr(IP-ID) are swapped before
      compression and after decompression.  The value of NBO is ignored
      when value(RND) = 1.
=============================================================

Suppose I have RND=0 and I send a UO-1-ID packet with extension 3.
Suppose also that I include the 16-bit IP Identification field in
the extension 3. This is in 5.7.5, p.85.

Then the IP-ID field is clearly not compressed. But RND = 0.
But sometimes the IP-ID field in the IP packets does not follow the
established pattern. Therefore I may have to send all 16 bits even
when RND = 0.

The above rules tell me what happens when RND = 0 and the IP-ID is
compressed. But here the IP-ID is _not_ compressed.

Question:
Now should I swap the bytes of IP-ID according to NBO?
Should I subtract SN from the IP Identification field before I write
it into the type 3 extension?

I think that it is equally credible that the IP-ID is encoded
(1) without SN offset and bytes swap (i.e. verbatim) or
(2) with SN offset and bytes swap.

Can anyone tell me what the majority view on this is?

Cheers,
Alan Kennington.

PS. The ROHC implementer's guide, version 3, 4.8, page 7, says that
the 16-bit IP Identification field in an IR/IR-DYN packet must be
sent verbatim because it is called "Identification", not IP-ID.
This tends to make me think that the extn 3 IP-ID _may_ be the
swapped/offset version of IP-ID. But it is still unclear to me.

_______________________________________________
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