Re: [6tisch] [6lo] Compression Reference and Coalescence

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Tue, 26 January 2016 17:07 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D01D1A9055; Tue, 26 Jan 2016 09:07:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cwbr4Fb-hs7w; Tue, 26 Jan 2016 09:07:20 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D5871A0027; Tue, 26 Jan 2016 09:06:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=26104; q=dns/txt; s=iport; t=1453828010; x=1455037610; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=SG8iDBuOo/T5i+rAXrkReAHLjlvKyKROqUZ2XNH7U6o=; b=bimCvnz19KWPvt86ksDBGmdiabl1+Mb1J7IdWBCQHrDPKKPoYTVFnWax cr2+cKEIPaMfq337xkUnIe1Sl+lOa17+yg2xBvgwJflddEVpKnz+sp8rB PadA17HM8VTEWxwonxQH3czfTYvpUNKUcTXS7+7ici18xbZ7rt8qgCBSf c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D/AQBQp6dW/5ldJa1egm5MUm0GiFGyH?= =?us-ascii?q?AENgWKGDwIcgS84FAEBAQEBAQGBCoRBAQEBBCMEBkwQAgEIEQQBASgDAgICHxE?= =?us-ascii?q?UCQgCBA4FCId+AxKvUIsKDYQQAQEBAQEBAQEBAQEBAQEBAQEBAQEBFYYyhG2CS?= =?us-ascii?q?YFwKCCCS4E6BYdZjyABi12BcYFljRuHAYNvg1IBHgEBQoF+AxiBUGqHSHwBAQE?=
X-IronPort-AV: E=Sophos; i="5.22,350,1449532800"; d="scan'208,217"; a="70022235"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Jan 2016 17:06:36 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u0QH6agb004331 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 26 Jan 2016 17:06:36 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 26 Jan 2016 11:06:36 -0600
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1104.009; Tue, 26 Jan 2016 11:06:36 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Tengfei Chang <tengfei.chang@gmail.com>
Thread-Topic: [6lo] Compression Reference and Coalescence
Thread-Index: AQHRWFp9t08kYDUUHE+JUPXG1+5Hup8OBKBg
Date: Tue, 26 Jan 2016 17:06:29 +0000
Deferred-Delivery: Tue, 26 Jan 2016 17:05:34 +0000
Message-ID: <e190aab2d05f41dc900df82faa3a6fdd@XCH-RCD-001.cisco.com>
References: <CAAdgstTGw=YV0bAe60H1VLaA1ikKZX41OiQTKRPrXkEM3_LtfQ@mail.gmail.com> <078cb52ea1904304b32f2936e24e19a4@XCH-RCD-001.cisco.com> <CAAdgstTQcg5gHbrgy5RABVK9oHRzYY8XpTXBrkHUs0ShvR3TvQ@mail.gmail.com>
In-Reply-To: <CAAdgstTQcg5gHbrgy5RABVK9oHRzYY8XpTXBrkHUs0ShvR3TvQ@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.71.115]
Content-Type: multipart/alternative; boundary="_000_e190aab2d05f41dc900df82faa3a6fddXCHRCD001ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/4pBW6QUKWDzO_Hv4_rLJrOp7KNI>
Cc: "6tisch@ietf.org" <6tisch@ietf.org>, "6lo@ietf.org" <6lo@ietf.org>
Subject: Re: [6tisch] [6lo] Compression Reference and Coalescence
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jan 2016 17:07:23 -0000

I see, and yes, that is misleading.

I need to change that to say the reference to the first is the source of the packet and then the reference for each entry is the previous one when uncompressed (not the first as you suggest but, the one just before it).
So you uncompress an address and it becomes reference to the next that you uncompress, etc… I will raise an ticket. . You’ll find that the algorithm in “5.4.  Popping Headers” decodes exactly that (well hopefully).

Do we agree?

Pascal

From: Tengfei Chang [mailto:tengfei.chang@gmail.com]
Sent: mardi 26 janvier 2016 17:56
To: Pascal Thubert (pthubert) <pthubert@cisco.com>
Cc: 6tisch@ietf.org; 6lo@ietf.org
Subject: Re: [6lo] Compression Reference and Coalescence

Nice to hear that's what you intended to do!

In  the beginning of section 4.3:
...


   Once the address of the source of the packet is determined, it

   becomes the reference for the compression of the addresses that are

   located in compressed RH3 headers that are present inside the IP-in-

   IP encapsulation in the uncompressed form.

...

When I am understanding the sentence, I am feeling like all the compression of addresses in RH3 will be compressed according to source address in IPinIP, which only the first 8 bytes can be elided.

If agree with the reasonable one, it should be the first address in first RH3 is compressed according to the source address in IPinIP.
Then, all rest address in RH3 will be compressed according to the first address in RH3.

Make sense?
Tengfei

On Tue, Jan 26, 2016 at 5:23 PM, Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>> wrote:
Hello Tengfei:

The draft is meant to express exactly what your reasonable case shows.
There is an example of that in appendix.
What exactly did I write improperly that it can be understood otherwise?

Take care ;

Pascal

From: 6lo [mailto:6lo-bounces@ietf.org<mailto:6lo-bounces@ietf.org>] On Behalf Of Tengfei Chang
Sent: lundi 25 janvier 2016 12:00
To: 6tisch@ietf.org<mailto:6tisch@ietf.org>; 6lo@ietf.org<mailto:6lo@ietf.org>
Subject: [6lo] Compression Reference and Coalescence

Dear all,

I have some concern on the compression Reference and Coalescence.

In the 6lorh draft, all the hops in RH3 are compressed according to the compression reference (the source address, root usually). And when doing Coalescence, the process is kind of like taking the first address in first RH3 as the reference. The inconsistency between compression reference and Coalescense may waste some bytes in some cases.

For example:
A packet is issued by root with a compressed RH3 along an A->B->C->D source route path.

The nodes address are:
root:      bbbb::0000:0000:0000:0001
node A: bbbb::1111:2222:3333:0001
node B: bbbb::1111:2222:3333:0002
node C: bbbb::1111:2222:3333:0003
node D: bbbb::1111:2222:3333:0004

According to the 6lorh draft: all hops in RH3 will be compressed according to reference, which is the root. The  Packet received by node A is:
----------------------------
Type 3 RH3-6LoRH Size = 2  1111 2222 3333 0001
                                           1111 2222 3333 0002
                                           1111 2222 3333 0003

And which maybe more reasonable packet would be like :
----------------------------
Type 3 RH3-6LoRH Size = 0  1111 2222 3333 0001
Type 0 RH3-6LoRH Size = 1  02
                                            03
Which means the first hop in first RH3 entry is compressed according to the reference(which is the root in this case) and the rest hops are compressed according to the first hop in first RH3 entry. For me, this compression way is more consistent  with the way when doing coalescence.

What do you think?
Tengfei