IETF Logo Mail Archive

[rohc] IP-ID of ROHCv2

"Lee, Jiwoong" <jiwoongl@qualcomm.com> Wed, 22 July 2009 18:15 UTC

Return-Path: <jiwoongl@qualcomm.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 99C6B3A68AE for <rohc@core3.amsl.com>; Wed, 22 Jul 2009 11:15:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level:
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 aTttAfRjovuh for <rohc@core3.amsl.com>; Wed, 22 Jul 2009 11:15:12 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id CE1203A6891 for <rohc@ietf.org>; Wed, 22 Jul 2009 11:15:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=jiwoongl@qualcomm.com; q=dns/txt; s=qcdkim; t=1248286513; x=1279822513; h=from:to:date:subject:thread-topic:thread-index: message-id:accept-language:content-language: x-ms-has-attach:x-ms-tnef-correlator:acceptlanguage: content-type:mime-version:x-ironport-av; z=From:=20"Lee,=20Jiwoong"=20<jiwoongl@qualcomm.com>|To: =20"rohc@ietf.org"=20<rohc@ietf.org>|Date:=20Wed,=2022=20 Jul=202009=2011:13:20=20-0700|Subject:=20IP-ID=20of=20ROH Cv2|Thread-Topic:=20IP-ID=20of=20ROHCv2|Thread-Index:=20A coK+Bg4hdhQs9fbTZiN3PNp8rKNpQ=3D=3D|Message-ID:=20<29F077 0B56D6A94794A647432F9A9EF06B2A7D501C@NALASEXMB14.na.qualc omm.com>|Accept-Language:=20en-US|Content-Language:=20en- US|X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20multipart/alternative=3B=0D=0A =09boundary=3D"_000_29F0770B56D6A94794A647432F9A9EF06B2A7 D501CNALASEXMB14na_"|MIME-Version:=201.0|X-IronPort-AV: =20E=3DMcAfee=3Bi=3D"5300,2777,5684"=3B=20a=3D"21074917"; bh=Boc5SCZgMJlTHpqyW32AoAo7KfhEVRzj1exduuxBXmA=; b=IjQEl6uGSI77I3mKfw10cSDOlIdY7JR/saJa6OEjU2Y5G0L93TXJIezx SC3kxnNPLKW2Nw3PwZsdDuLmrP7Vg1CaFQmbSWvxv2MJMa6vaYGBj7rlx mnHE0IZhawkVzmsSKlgHKV5M2EF8QdY4+anvMnfKKBSfix7KnvBQVqpEp c=;
X-IronPort-AV: E=McAfee;i="5300,2777,5684"; a="21074917"
Received: from pdmz-ns-mip.qualcomm.com (HELO ithilien.qualcomm.com) ([199.106.114.10]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 22 Jul 2009 11:13:22 -0700
Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158]) by ithilien.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n6MIDLHU005620 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <rohc@ietf.org>; Wed, 22 Jul 2009 11:13:22 -0700
Received: from nasanexhub05.na.qualcomm.com (nasanexhub05.na.qualcomm.com [129.46.134.219]) by totoro.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n6MIDLcN014509 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rohc@ietf.org>; Wed, 22 Jul 2009 11:13:21 -0700 (PDT)
Received: from nalasexhub03.na.qualcomm.com (10.47.130.45) by nasanexhub05.na.qualcomm.com (129.46.134.219) with Microsoft SMTP Server (TLS) id 8.1.358.0; Wed, 22 Jul 2009 11:13:21 -0700
Received: from NALASEXMB14.na.qualcomm.com ([10.47.5.251]) by nalasexhub03.na.qualcomm.com ([10.47.130.45]) with mapi; Wed, 22 Jul 2009 11:13:21 -0700
From: "Lee, Jiwoong" <jiwoongl@qualcomm.com>
To: "rohc@ietf.org" <rohc@ietf.org>
Date: Wed, 22 Jul 2009 11:13:20 -0700
Thread-Topic: IP-ID of ROHCv2
Thread-Index: AcoK+Bg4hdhQs9fbTZiN3PNp8rKNpQ==
Message-ID: <29F0770B56D6A94794A647432F9A9EF06B2A7D501C@NALASEXMB14.na.qualcomm.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_29F0770B56D6A94794A647432F9A9EF06B2A7D501CNALASEXMB14na_"
MIME-Version: 1.0
Subject: [rohc] IP-ID of ROHCv2
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, 22 Jul 2009 18:15:16 -0000

Dear ROHC WG,

Today I want to raise a concern and learn your comments about one section of RFC 5225. I see a potential violation of transparency and integrity concept of compression in red colored sentence.

Basically IP-ID of tunneling headers is decided by the tunnel ingress/egress nodes but not by a compressor/decompressor pair in the middle of transit.  Does the red colored sentence require the overwriting of IP-ID field?

I guess it shouldn't. Otherwise it may cause non-conformance to security protocols.

Thank you,
Jiwoong


6.3.3.  IP-ID Behavior
   ...
   ROHCv2 profiles MUST NOT assign a sequential behavior (network byte
   order or byte-swapped) to any IP-ID but the one in the innermost IP
   header when compressing more than one level of IP headers.  This is
   because only the IP-ID of the innermost IP header is likely to have a
   sufficiently close correlation with the MSN to compress it as a
   sequentially changing field.  Therefore, a compressor MUST assign
   either the constant zero IP-ID or the random IP-ID behavior to
   tunneling headers.

v2.23.0 | Report a Bug | By Email