[rohc] RFC5225 IP-ID with co_common and Random behavior and tos_tc changes

Klaus Warnke <klaus.warnke@acticom.de> Tue, 04 September 2012 10:48 UTC

Return-Path: <klaus.warnke@acticom.de>
X-Original-To: rohc@ietfa.amsl.com
Delivered-To: rohc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF94321F85ED for <rohc@ietfa.amsl.com>; Tue, 4 Sep 2012 03:48:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0QdjF+ex75hz for <rohc@ietfa.amsl.com>; Tue, 4 Sep 2012 03:48:18 -0700 (PDT)
Received: from mail.acticom-networks.com (mail.acticom-networks.com [87.106.254.214]) by ietfa.amsl.com (Postfix) with ESMTP id 0B12E21F85E6 for <rohc@ietf.org>; Tue, 4 Sep 2012 03:48:17 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.acticom-networks.com (Postfix) with ESMTP id 221881C00F54 for <rohc@ietf.org>; Tue, 4 Sep 2012 12:48:16 +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 r+2rlIGFp-BX for <rohc@ietf.org>; Tue, 4 Sep 2012 12:48:15 +0200 (CEST)
Received: from godfather.bln.acticom.de (backupsrv [87.139.237.181]) by mail.acticom-networks.com (Postfix) with ESMTP id 559781C00F4B for <rohc@ietf.org>; Tue, 4 Sep 2012 12:48:15 +0200 (CEST)
Received: from [192.168.33.27] (tornado.bln.acticom.de [192.168.33.27]) by godfather.bln.acticom.de (Postfix) with ESMTP id EABD4F3AD0 for <rohc@ietf.org>; Tue, 4 Sep 2012 12:48:14 +0200 (CEST)
Message-ID: <5045DC6E.3050302@acticom.de>
Date: Tue, 04 Sep 2012 12:48:14 +0200
From: Klaus Warnke <klaus.warnke@acticom.de>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: "rohc@ietf.org" <rohc@ietf.org>
Content-Type: text/plain; charset="ISO-8859-15"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [rohc] RFC5225 IP-ID with co_common and Random behavior and tos_tc changes
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 04 Sep 2012 10:48:19 -0000

Hello everybody,

if the ip-id has a random behavior, it is sent in the irregular chain
as defined in ipv4() encoding method and ipv4_innermost_irregular format.
This encoding method has a DEFAULT section, which also defines that
tos_tc is encoded static (and other).
If I understand den ROHC FN right, the format
ipv4_innermost_irregular could not be used,
if the tos_tc could not encoded by the static encoding method.
But then I can not use co_common format to transmit tos_tc changes,
because the ip_id is not included in co_common if the behavior is random.
Is this correct?

Regards,
Klaus

-- 
Klaus Warnke		klaus.warnke@acticom.de
http://www.acticom.de
Tel +49-30-4849.6891

acticom GmbH
Schwedter Str. 9b, 10119 Berlin, Germany
Managing Directors:  Olaf Kehrer, Gerrit Schulte
Commercial Register: Berlin-Charlottenburg HRB 73245
VAT-ID DE205131766