Re: [Roll] [6tisch] Support of flow label to carry the RPL information in data packets

Xavier Vilajosana <xvilajosana@eecs.berkeley.edu> Thu, 17 April 2014 07:59 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 0A5A01A00FD; Thu, 17 Apr 2014 00:59:45 -0700 (PDT)
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 MTzOplubUmPI; Thu, 17 Apr 2014 00:59:40 -0700 (PDT)
Received: from mail-vc0-x22c.google.com (mail-vc0-x22c.google.com [IPv6:2607:f8b0:400c:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id D7D4C1A0160; Thu, 17 Apr 2014 00:59:37 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id la4so107647vcb.31 for <multiple recipients>; Thu, 17 Apr 2014 00:59:34 -0700 (PDT)
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=gIv3/P5I16A0XPX16QRfAyjceLDGnjUslThT/QwyGTg=; b=vZbQD3uSAsQvWu6Y1xViBxZK7H8TR5dDMhFRZxXiiq31N26tay1wUaVnCsA5V/ksIG UAorWxNHceSxJl8ieCH129wGU3Jqt3/8hysypWcvt7LlDOnLGWo2AkXlrLCO4Sm+/qRR MqPP6fM9Iv3L2ndtZZT9RmH+lDhqQKI9f+Sh9jDziC6/oVkYNUA6XYHhpemCASwoC5Gv 752t73KcpkTP4kBmdzo8b0oUaej3tRfgRTQbkre1hGHEDz0LvkyHrxC+iTnjY1R/TZYo yudnO2BJyj2ETrGIrMM8pTrLbSjUeSYNjUpx4EZN00zg8+VhI+8NNi2fHpZSnUICmXpT r5tQ==
MIME-Version: 1.0
X-Received: by 10.58.219.233 with SMTP id pr9mr10753108vec.10.1397721574128; Thu, 17 Apr 2014 00:59:34 -0700 (PDT)
Sender: xvilajosana@gmail.com
Received: by 10.58.85.196 with HTTP; Thu, 17 Apr 2014 00:59:34 -0700 (PDT)
In-Reply-To: <CAP+sJUfx6=-22+A_=M_v3iSf6piGeyHkF2_BPm2ntbWnCEhTSw@mail.gmail.com>
References: <534D4F7A.3040605@cox.net> <CAH7SZV9WeQmuaHvUZ35_ySL4ak4+SDfbmpMbXgqQL+C833sTGw@mail.gmail.com> <1397607559.92815.YahooMailNeo@web120004.mail.ne1.yahoo.com> <CAP+sJUfx6=-22+A_=M_v3iSf6piGeyHkF2_BPm2ntbWnCEhTSw@mail.gmail.com>
Date: Thu, 17 Apr 2014 09:59:34 +0200
X-Google-Sender-Auth: TAEnB_EUwpb1RMmCuJRXY77Xpc8
Message-ID: <CAMsDxWRgNoWdaRaZz=tOuWQ+ucCfFE7EnHxbbjBvBR64xoF_dQ@mail.gmail.com>
From: Xavier Vilajosana <xvilajosana@eecs.berkeley.edu>
To: Ines Robles <mariainesrobles@googlemail.com>
Content-Type: multipart/alternative; boundary="047d7bdc1632ebc08f04f73869d4"
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/dyYo4XODlvHjNWrbFK6hSulPJps
Cc: roll <roll@ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>
Subject: Re: [Roll] [6tisch] Support of flow label to carry the RPL information in data packets
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, 17 Apr 2014 07:59:45 -0000

+1 I think this is more than needed. In addition RFC 6282 defines how
header compression needs to be handled together with extension headers. I
think this is not clear and leads to confusions (afecting already some
wireshark dissectors). The use of flow label will solve several problems at
once.

X.




2014-04-16 22:44 GMT+02:00 Ines Robles <mariainesrobles@googlemail.com>:

> +1
>
> Ines
>
> 2014-04-15 21:19 GMT-03:00 Qin Wang <qinwang6top@yahoo.com>:
>
>> +1
>>
>> Qin
>>   On Wednesday, April 16, 2014 1:47 AM, Prof. Diego Dujovne <
>> diego.dujovne@mail.udp.cl> wrote:
>>  +1 !
>>
>>
>> 2014-04-15 12:25 GMT-03:00 Tom Phinney <tom.phinney@cox.net>:
>>
>>  +1 for sure. The flow label has always been the preferable method for
>> me, and I suspect for others with knowledge of how it is used in ISA100.11a.
>> ===
>>
>> On 2014.04.15 07:25, Pascal Thubert (pthubert) wrote:
>>
>>  Dear all:
>>
>> As some of you remember, the RPL specification has changed over time WRT
>> to the location of the information that RPL places in the data packets. We
>> started with the flow label but these were the days when what became RFC
>> 6437 was being defined at 6MAN, so we shied away and defined the HbH
>> technique that is now specified as RFC 6553.
>>
>> We’ll note that the RPL option defined in RFC 6553 takes 6 octets, and
>> with the HbH hdr we end up with 8 extra octets. An extra IP-in-IP
>> encapsulation is required on top of that unless both endpoints are in the
>> same RPL domain. All this overhead may be acceptable when power is
>> available and the PHY allows for larger frames, but in traditional
>> battery-operated 15.4 with ~ 80 bytes usable per frame, my experience from
>> integrating 6LoWPAN HC with ISA100.11a says that all these extra bytes will
>> be on the way of the 6TiSCH adoption.
>>
>> Still, both RFC 6550 and RFC 6552 are designed to allow for an alternate
>> technique and in particular for the use of the flow label, as is elaborated
>> in http://tools.ietf.org/html/draft-thubert-roll-flow-label-02 . Using
>> the flow label reduces the cost of the RPL information dramatically, down
>> to a level that is probably acceptable for the target SDOs.
>>
>> So my plan for now is to move the flow label draft to 6MAN and prepare
>> for a hot season, and I’m looking for support from both 6TiSCH and ROLL to
>> back me up from the start.  Yes, you can help!
>>
>> Please +1 if you agree we need this work to happen, and/or provide any
>> suggestion.
>>
>> Cheers,
>>
>> Pascal
>>
>>
>> _______________________________________________
>> 6tisch mailing list6tisch@ietf.orghttps://www.ietf.org/mailman/listinfo/6tisch
>>
>>
>>
>> _______________________________________________
>> 6tisch mailing list
>> 6tisch@ietf.org
>> https://www.ietf.org/mailman/listinfo/6tisch
>>
>>
>>
>>
>> --
>> DIEGO DUJOVNE
>> Académico Escuela de Ingeniería en Informática y Telecomunicaciones
>> Facultad de Ingeniería UDP
>> www.ingenieria.udp.cl
>> (56 2) 676 8125
>>
>> _______________________________________________
>> 6tisch mailing list
>> 6tisch@ietf.org
>> https://www.ietf.org/mailman/listinfo/6tisch
>>
>>
>>
>> _______________________________________________
>> Roll mailing list
>> Roll@ietf.org
>> https://www.ietf.org/mailman/listinfo/roll
>>
>>
>
> _______________________________________________
> 6tisch mailing list
> 6tisch@ietf.org
> https://www.ietf.org/mailman/listinfo/6tisch
>
>