Re: [Roll] [6lo] [6tisch] Call to confirm a rough consensus on RPL info

"Turner, Randy" <> Wed, 22 October 2014 04:20 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id B02811A8A8D; Tue, 21 Oct 2014 21:20:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id wFCQJ2GcQLWX; Tue, 21 Oct 2014 21:20:47 -0700 (PDT)
Received: from ( [IPv6:2a01:111:f400:fe00::795]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2668C1A8A89; Tue, 21 Oct 2014 21:20:47 -0700 (PDT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1054.13; Wed, 22 Oct 2014 04:13:35 +0000
Received: from ([]) by ([]) with mapi id 15.00.1054.004; Wed, 22 Oct 2014 04:13:35 +0000
From: "Turner, Randy" <>
To: Randy Turner <>
Thread-Topic: [6lo] [6tisch] [Roll] Call to confirm a rough consensus on RPL info
Thread-Index: Ac/oQa0i5HZn0oJrT3qpZBX3hHGwVAAAfziAAVMzxgD//8E8AIAAWlSAgAAgGQCAAAB8ww==
Date: Wed, 22 Oct 2014 04:13:34 +0000
Message-ID: <>
References: <> <> <> <> <>, <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [2601:0:8ec0:4a:c1e5:ade5:1c08:b976]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR01MB0431;
x-forefront-prvs: 037291602B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(41574002)(24454002)(189002)(199003)(377454003)(377424004)(31966008)(16236675004)(33656002)(120916001)(82746002)(15975445006)(561944003)(40100003)(101416001)(93886004)(85306004)(99396003)(76482002)(122556002)(16799955002)(20776003)(64706001)(4396001)(21056001)(86362001)(92726001)(76176999)(54356999)(87936001)(107046002)(80022003)(83716003)(50986999)(2656002)(46102003)(95666004)(36756003)(19580395003)(19580405001)(19617315012)(105586002)(85852003)(110136001)(92566001)(106356001)(104396001)(24704002)(3826002); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR01MB0431;; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
Content-Type: multipart/alternative; boundary="_000_2B22B1729DF34317B7245B1E8538C0C1landisgyrcom_"
MIME-Version: 1.0
Cc: Routing Over Low power and Lossy networks <>, "" <>, "" <>
Subject: Re: [Roll] [6lo] [6tisch] Call to confirm a rough consensus on RPL info
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: Wed, 22 Oct 2014 04:20:52 -0000

Forgot to reply to lists as well :)...see my reply to Thomas below

On Oct 22, 2014, at 12:11 AM, "Randy Turner" <<>> wrote:

Yes, in Pascal's call for consensus he only mentions 6553... Just curious if the phone call consensus was only about requiring compression of 6553 options...or are there any other compression methods that the minimal draft must include


Sent from my iPad

On Oct 21, 2014, at 10:16 PM, Thomas Watteyne <<>> wrote:

Are you alluding to 6554?

On Tue, Oct 21, 2014 at 5:56 PM, Turner, Randy <<>> wrote:

I think I’m +1 on the proposal – was compression of 6553 options the ONLY required compression in the “minimal” case ? (apologies…I wasn’t on the call) I did a quick search of minimal-02 and didn’t see the word compression anywhere.


From: Thomas Watteyne <<>>
Reply-To: "<>" <<>>
Date: Tuesday, October 21, 2014 at 8:38 PM
To: "<>" <<>>
Cc: "<>" <<>>, "<>" <<>>, "<>" <<>>, "<>" <<>>, "<>" <<>>
Subject: Re: [Roll] Call to confirm a rough consensus on RPL info

+1 on the proposal.

On Tue, Oct 14, 2014 at 11:45 PM, Xavier Vilajosana <<>> wrote:

I fully support that approach. Hope to contribute and make it happen as soon as possible.


2014-10-15 8:32 GMT+02:00 Pascal Thubert (pthubert) <<>>:

Dear all:

During the 6TiSCH bi-weekly virtual interim on Friday, we agreed that the minimal I-D (draft-ietf-6tisch-minimal) must indicate the compression method for the RPL Information (see RFC 6553), so as to ensure interoperation between 6TiSCH devices.

We discussed our options, basically either a 6lo approach or a Flow Label approach. The rough consensus at the call was to try and focus on a 6lo approach and evaluate where that leads us.

Because this means that the minimal draft will have a normative reference on a WIP I-D, we recognized that this approach may delay the publication of the final RFC. Per IETF procedures, the minimal draft will be stalled in the RFC editor queue in MISREF state until the 6lo work completes. So the consensus was also to support the 6lo work so as to expedite it as much as possible.

The idea would be to republish a standard track draft-ietf-6lo- ASAP, based on the existing proposals (which are rapidly converging); then, Xavi would include a normative reference to that work in the minimal I-D before its publication to IESG, which is scheduled in November (yes, this is aggressive).

This is a call to confirm the rough consensus on the ML, open till the next interim call on October 24th. Please provide us with any relevant comment (and participate to the 6lo discussions in the meantime!).

If the result is positive:
- we plan to call for a 6lo WG doc adoption in Hawaii
- we are looking for an aggressive schedule to limit the impact on the publication of the minimal RFC

6TiSCH may host the 6lo discussion so as to:
- benefit from the early morning schedule
- attract more 6TiSCH people to the discussion

More the published minutes:
- Webex recording:
- Wiki:
- Slides:



Roll mailing list<>

Roll mailing list<>


This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.

6tisch mailing list<>

6lo mailing list<>