Re: [Roll] [6lo] FW: New Version Notification for draft-thubert-6lo-routing-dispatch-00.txt

Robert Cragie <> Mon, 01 December 2014 18:17 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 4882D1A87CD; Mon, 1 Dec 2014 10:17:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id HybeBeDVtunT; Mon, 1 Dec 2014 10:17:21 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1B0EC1A87D2; Mon, 1 Dec 2014 10:16:47 -0800 (PST)
Received: from mailscanlb0.hi.local ([] by mailscan-g67.hi.local with esmtp (Exim 4.80.1) (envelope-from <>) id 1XvVWf-00061M-68; Mon, 01 Dec 2014 18:16:45 +0000
Received: from mailscanlb0.hi.local ([] by with esmtps (UNKNOWN:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.80.1) (envelope-from <>) id 1XvVWd-0003SA-AJ; Mon, 01 Dec 2014 18:16:45 +0000
Received: from ([] helo=[]) by with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.80.1) id 1XvVWb-0004hs-RW; Mon, 01 Dec 2014 18:16:42 +0000
Message-ID: <>
Date: Mon, 01 Dec 2014 18:16:53 +0000
From: Robert Cragie <>
Organization: Gridmerge Ltd.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: "Pascal Thubert (pthubert)" <>, "" <>
References: <> <>
In-Reply-To: <>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms020600050303060302020402"
X-Extend-Src: mailout
Cc: Routing Over Low power and Lossy networks <>, "" <>
Subject: Re: [Roll] [6lo] FW: New Version Notification for draft-thubert-6lo-routing-dispatch-00.txt
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: Mon, 01 Dec 2014 18:17:25 -0000

Hi Pascal,

I agree that with hindsight it could be considered a bit greedy of 
RFC4944 to allocate 1/3 of the dispatch code space to the mesh header 
(especially when the definition of it itself is questionable) but what 
you are advocating is a replacement, not a framework extension. RFC6282 
only deprecated an ESC code, i.e. something which had not yet been used, 
which is not quite the same. This effectively makes this at best a new 
version of 6lowpan (which is difficult to distinguish) or at worst 
arguably a whole new protocol.

Whilst hindsight is a wonderful thing, it can lead to the situation 
where a standard never stands still and keeps evolving. This makes it 
very difficult to develop products as there is always the fear that 
something will change the next year. Upgrading products is often quite a 
difficult process, especially in the case where there could quite 
feasibly be thousands of deployed devices which may have limited upgrade 

I would like to hear what other people think about this.

Also a comment re. section 8, I think the 'I' field needs to be 1, as 
'Size' represents the HopsLft field, not the size of the header. It also 
doesn't seem to cover the Deep Hops Left concept in RFC4944.


On 27/11/2014 2:03 PM, Pascal Thubert (pthubert) wrote:
> Dear all:
> This is a response to the question about the compression of RFC 6553 on top of RFC 6554.
> It seems exaggerated to consume a dispatch type for the RPL option only.
> But here, we introduce a routing header which is the equivalent of the mesh header in RFC 4944; we propose a compressed TLV format that can encode RH3, RPL option, IP-in-IP, and is further extensible, for instance for upcoming  BIER.
> As it goes, the mesh header consumes 1/3 of all the 6LoWPAN addressable space for application only in Mesh-under.
> This draft reuses that space in Route-over with the assumption that Route-over will not co-exist in a sma enetwork with Mesh-under encoded in the RFC 4944 fashion.
> If there is effectively a need for co-existence, devices have to implement the new Mesh-under format that is also proposed in the draft.
> Comments welcome,
> Pascal
> -----Original Message-----
> From: []
> Sent: jeudi 27 novembre 2014 14:36
> To: Pascal Thubert (pthubert); Pascal Thubert (pthubert); Laurent Toutain; Carsten Bormann; Laurent Toutain; Dr. Carsten Bormann
> Subject: New Version Notification for draft-thubert-6lo-routing-dispatch-00.txt
> A new version of I-D, draft-thubert-6lo-routing-dispatch-00.txt
> has been successfully submitted by Pascal Thubert and posted to the IETF repository.
> Name:		draft-thubert-6lo-routing-dispatch
> Revision:	00
> Title:		A Routing Header Dispatch for 6LoWPAN
> Document date:	2014-11-25
> Group:		Individual Submission
> Pages:		19
> URL:  
> Status:
> Htmlized:
> Abstract:
>     This specification provides a new 6LoWPAN dispatch type for use in
>     Route-over and mixed Mesh-under and Route-over topologies, that
>     reuses the encoding of the mesh type defined in RFC 4944 for pure
>     Mesh-under topologies.  This specification also defines a method to
>     compress RPL Option (RFC6553) information and Routing Header type 3
>     (RFC6554), an efficient IP-in-IP technique and opens the way for
>     further routing techniques.  This extends 6LoWPAN Transmission of
>     IPv6 Packets (RFC4944), and is applicable to new link-layer types
>     where 6LoWPAN is being defined.
> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at
> The IETF Secretariat
> _______________________________________________
> 6lo mailing list