Re: [Roll] call for consensus for the RPL RPI / RH3 compression

"Pascal Thubert (pthubert)" <> Tue, 06 January 2015 06:22 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 2582F1A90FD; Mon, 5 Jan 2015 22:22:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ABbNr6NBIwpQ; Mon, 5 Jan 2015 22:22:14 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 006D71A90F8; Mon, 5 Jan 2015 22:22:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=1942; q=dns/txt; s=iport; t=1420525334; x=1421734934; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=1/LBeTUmCA01mnZ2R2VSzpESjcU+V0d22LhwWHixWfU=; b=PBQT9ExkPzmc2R88IVrBIG6a5uKBvaDvdYolJtXD81OLKhtmcUO2xWpq +GzQtg4EZ4FVNVfe5OVU1SOSQOgTm1pR0tKtJ0FgbY0Ty/W9DChKR8YYV PaQiub16Kgp1xTPwq6t5lzNq9NKb0NE6Vidna9OJ9DKsw9b144kyJS31Q g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.07,705,1413244800"; d="scan'208";a="110626681"
Received: from ([]) by with ESMTP; 06 Jan 2015 06:22:13 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id t066MDEv014842 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 6 Jan 2015 06:22:13 GMT
Received: from ([]) by ([]) with mapi id 14.03.0195.001; Tue, 6 Jan 2015 00:22:13 -0600
From: "Pascal Thubert (pthubert)" <>
To: Routing Over Low power and Lossy networks <>
Thread-Topic: [Roll] call for consensus for the RPL RPI / RH3 compression
Thread-Index: AQHQKTccIER4yneI6UuQFsYm6imsn5yyn8j8
Date: Tue, 06 Jan 2015 06:22:11 +0000
Message-ID: <>
References: <>, <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "" <>, "" <>, "" <>, "" <>, " WG" <>
Subject: Re: [Roll] call for consensus for the RPL RPI / RH3 compression
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <>
List-Id: Routing Over Low power and Lossy networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 06 Jan 2015 06:22:16 -0000

Hello Ralph 

You certainly got it all right.

To your question we started through the NHC and found that path less efficient than Laurent's initial suggestion to place all the LLN routing artifacts in a different header/dispatch whatever the correct term is for that object.

One additional concern that doesn't show in your mail is the need for IP encapsulation when the artifacts are added by a router on the way or must be removed at LLN egress. By leaving the original IPv6 packet intact we simplify that matter and optimize the overall result by providing an improved compression for the outter header.

The new proposal also reopens the dispatch space (1/3 of the total) that is used is mesh under for mesh header, so it can also be use AND extended as TLV in route over.

Makes sense?


> Le 5 janv. 2015 à 23:29, Ralph Droms <> a écrit :
> Do I have it right that:
> 1) draft-thubert-roll-flow-label-02 compresses RPL RPI but not RH3
> 2) draft-thubert-6lo-rpl-nhc-02 compresses RPL RPI and might be extended to compress RH3
> 3) draft-thubert-6lo-routing-dispatch-01 compresses both RPL RPI and RH3
> In discussion during the IETF-91 6lo working group meeting, a concern was raised about further consumption of NHC codepoints beyond what is defined in draft-thubert-6lo-rpl-nhc-02 for a future RH3 compression scheme.
> Pascal, Carsten - as you have devised a mechanism for RH3 compression in draft-thubert-6lo-routing-dispatch-01, would you be able to retrofit a version of that mechanism into draft-thubert-6lo-rpl-nhc-02?  This extension to NHC compression would provide an explicit proposal for evaluation of RPL header compression in NHC.
> - Ralph
> _______________________________________________
> Roll mailing list