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

Xavier Vilajosana <xvilajosana@eecs.berkeley.edu> Thu, 18 December 2014 20:28 UTC

Return-Path: <xvilajosana@gmail.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC3461A1B7A; Thu, 18 Dec 2014 12:28:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 YWgeJmXyhvWd; Thu, 18 Dec 2014 12:28:51 -0800 (PST)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2B721AC3F9; Thu, 18 Dec 2014 12:28:41 -0800 (PST)
Received: by mail-wg0-f48.google.com with SMTP id y19so2660363wgg.7; Thu, 18 Dec 2014 12:28:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=hIRdE8WI4FJwTfMEpT5TZGahsmDDneGgC0rNJ2pDyaA=; b=Srs9ysLOIApyQXD/sXF74uwNSQyzegwf/GxKPdyseecrAjdtUkCIPdg3oASRjHrZP4 0Xd9nlvZpC2sPwKWkAg+oLuxgO/U8IDEzVBkjA8wc7I3L3C30damVCxIMYZ5d6FYGNu8 5fv8oNbTuZVMgSKVlnEnLZpHxd9eGDbjZRRdJiAGkm8hN0bn8d/NTtYhtmNsRdveaG9+ iZnJH20NISI9ObFMcdX5NbshF2vXVM9aaoJWMtimJMvsc5vOV4+/OSygCiNqvYc1RiR7 Qi3l6yonIQw4c9mcdTHHEH/GzOeKlYBGVx/3Lj8dlFhVMXWq/i/8SSQf2AwN6OEKHNEI R4Vg==
MIME-Version: 1.0
X-Received: by 10.194.81.1 with SMTP id v1mr7050418wjx.50.1418934520326; Thu, 18 Dec 2014 12:28:40 -0800 (PST)
Sender: xvilajosana@gmail.com
Received: by 10.27.210.201 with HTTP; Thu, 18 Dec 2014 12:28:40 -0800 (PST)
In-Reply-To: <10328.1418920757@sandelman.ca>
References: <E045AECD98228444A58C61C200AE1BD848AC2314@xmb-rcd-x01.cisco.com> <10328.1418920757@sandelman.ca>
Date: Thu, 18 Dec 2014 21:28:40 +0100
X-Google-Sender-Auth: skuxZQptV3U3LMYTQ7SBzIJYQ6I
Message-ID: <CAMsDxWS8FWA-fBzE8QCon7OUGdC-UQvOiGY6An5Miib-TKJCmw@mail.gmail.com>
From: Xavier Vilajosana <xvilajosana@eecs.berkeley.edu>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=047d7bb048760b315d050a83700f
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/HcvcYCyRdOhy28WbEe2R3h5aQjo
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "int-ads@tools.ietf.org" <int-ads@tools.ietf.org>, Routing Over Low power and Lossy networks <roll@ietf.org>, "6lo-chairs@tools.ietf.org" <6lo-chairs@tools.ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>
Subject: Re: [Roll] [6tisch] call for consensus for the RPL RPI / RH3 compression
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Dec 2014 20:28:53 -0000

Hi,

my 5 cents. I like flow label, but we (at 6tisch) discussed for a very long
time the approach to be taken (NHC and lately the new draft that also
compresses RH3). I will support it (flow label) but IMHO we have to make
sure there is no other thing we can do to make the current proposal at 6lo
to move forward or at least get strong arguments against it. In terms of
coherence, NHC it seems a more natural way to go as we are extending the
use of the dispatch and headers are all parsed following a coherent rule.

regards,
Xavi



2014-12-18 17:39 GMT+01:00 Michael Richardson <mcr+ietf@sandelman.ca>ca>:
>
>
> Pascal Thubert (pthubert) <pthubert@cisco.com> wrote:
>     > We are now in last call for draft-ietf-6tisch-minimal-04 which
>     > describes an interoperable operation of RPL over 802.15.4e TSCH.
>
> ...
>
>     > My personal take is lex parsimoniae. By default, we should fall back
> to
>     > the simplest to implement, which is also the least change in existing
>     > implementations, and that is the original flow label approach; and
> I'm
>     > calling the group for consensus on that default approach.
>
>     > What do you think?
>
> Not wearing any hat: I'm personally happy with the flow label approach.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>
> _______________________________________________
> 6tisch mailing list
> 6tisch@ietf.org
> https://www.ietf.org/mailman/listinfo/6tisch
>
>