Re: [6tisch] [6lo] Proposed improvement in RH3-6LoRH

"Pascal Thubert (pthubert)" <> Wed, 20 January 2016 07:48 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 69B121A906A; Tue, 19 Jan 2016 23:48:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id XDWQPczbaId1; Tue, 19 Jan 2016 23:48:45 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 980FE1A905C; Tue, 19 Jan 2016 23:48:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=2781; q=dns/txt; s=iport; t=1453276125; x=1454485725; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=dpzn3MpAiFaWbEr2qAYyLW3abc0BMTKaVuVhyvmPX6s=; b=KGSXNcSDuEDzS7XBCPsyvBgq3dgBzad9i5d0cuSqv2h+CtXMN4dZqrjC oiXUKKkkxUit3V4M9c7Hfqgu6s2vcceuWpxEqSGQvNahjXWJCxW3YlCbS fDdo+I7jip4Ces7axKrMSfu4O1eH+yAmyDBGzNkBPJmVK4BYTFFuzlm/O c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.22,320,1449532800"; d="scan'208";a="227970855"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Jan 2016 07:48:44 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id u0K7miGe026833 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 20 Jan 2016 07:48:44 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 20 Jan 2016 01:48:44 -0600
Received: from ([]) by ([]) with mapi id 15.00.1104.009; Wed, 20 Jan 2016 01:48:44 -0600
From: "Pascal Thubert (pthubert)" <>
To: Michael Richardson <>, Simon Duquennoy <>
Thread-Topic: [6tisch] [6lo] Proposed improvement in RH3-6LoRH
Thread-Index: AQHRU1b1SkfOy9CXX0O87LiotLoJRA==
Date: Wed, 20 Jan 2016 07:48:31 +0000
Deferred-Delivery: Wed, 20 Jan 2016 07:47:51 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
Cc: "" <>, "" <>, Routing Over Low power and Lossy networks <>, Tengfei Chang <>
Subject: Re: [6tisch] [6lo] Proposed improvement in RH3-6LoRH
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" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 20 Jan 2016 07:48:47 -0000

Well, if there is such interaction, it does not come from the RH3 compression but from the IP in IP compression that allows to elide a well-known root. This means that if the root is not that well-known, like the node participate to multiple DODAGs, then the RPI must be included together with RH3. Which is mandated by RPL for that reason, nothing very new there. 

With the current specs, for a packet with a RH3, the source in the IPv6 header when uncompressed is always the root. When 6LoWPAN decompresses the packet, it has to restore the root address first. 

And the proposal says use that as reference for decompression of the next entries in the RH3, as opposed to the final destination in the (inner) IP header.

The change is a slight improvement, since it addresses the case where the leaf does not belong to the same compression domain as the RPL mesh nodes, and avoids having to dig into the inner IP header.
IOW, with the change, the intermediate routers can process a packet without looking at the inner IP in IP.

In the future, if we allow nodes that are different from the root to write an RH3, then we'll have to decide if we use the source of the packet or the  root as reference. I'd probably still use the root so we can compress the source using the root as reference.



> -----Original Message-----
> From: Michael Richardson []
> Sent: mardi 19 janvier 2016 23:06
> To: Simon Duquennoy <>
> Cc: Pascal Thubert (pthubert) <>om>;;
> Routing Over Low power and Lossy networks <>rg>; Tengfei Chang
> <>om>;
> Subject: Re: [6tisch] [6lo] Proposed improvement in RH3-6LoRH
> Simon Duquennoy <> wrote:
>     > Not really. It was rather my view of the architecture that differs a
>     > bit from what you describe in your previous mail.
> okay.
>     > For me RPL produces the RH3 and then passes the packet down the
> stack
>     > for compression. Or for incoming packets, first there is
>     > decompression, then the IPv6 packet with its headers and extension
>     > headers are passed up to RPL etc. If find it odd to force upper layers
>     > to work on 6lowpan compressed formats.
> RPL is the thing in RFC6550, a routing protocol, that runs over ICMP ND
> messages.
> I think the thing you are describing is the IPv6 stack, and you don't like that
> the IPv6 stack has to interact with the link adaptation layer.
> --
> Michael Richardson <>ca>, Sandelman Software Works
> IETF ROLL WG co-chair.