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

Ines Robles <mariainesrobles@googlemail.com> Wed, 16 April 2014 20:44 UTC

Return-Path: <mariainesrobles@googlemail.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 8573D1A0339; Wed, 16 Apr 2014 13:44:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.377
X-Spam-Level:
X-Spam-Status: No, score=-1.377 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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 YXbmZWTBNw0h; Wed, 16 Apr 2014 13:44:10 -0700 (PDT)
Received: from mail-vc0-x230.google.com (mail-vc0-x230.google.com [IPv6:2607:f8b0:400c:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 20BC61A0348; Wed, 16 Apr 2014 13:44:10 -0700 (PDT)
Received: by mail-vc0-f176.google.com with SMTP id lc6so11194953vcb.21 for <multiple recipients>; Wed, 16 Apr 2014 13:44:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GvgQB5i5nbaMtLmr8oudw5ohBxMI34c+qy75i1kdAZM=; b=tdLo24qwvFxkiH6iHFSW1SMgeP3wFQ0XVh6avwTpJsm/d7wIKqIHGUOZkrkqFSKlXL SQ37UmfG3PNbpsy2PMjfxDEc8rJZ6w+eHpn4bU4aPpVVE6gOeWYrmSjtwARphP/mSsMy +ddU3D+yDEPsm9CSELQektgsNUos9/fAyotEt2RPK4toxaK4oHQ+aC5pkoY+AHGQW9nL SIW3GhJh+zcmxu8ZcpoAi9x6zY/TIQrDXDV2KYBm5TTi+4SyUmkbbmBomYdenwKKywqi hMTQxd0f7vwsStE3/V90UGX5uc2Mia20ot8DUgw0T6nt3pDQsMZ7n8zLRn33rwsYRAqI GQiQ==
MIME-Version: 1.0
X-Received: by 10.58.211.69 with SMTP id na5mr2447640vec.30.1397681046639; Wed, 16 Apr 2014 13:44:06 -0700 (PDT)
Received: by 10.221.16.3 with HTTP; Wed, 16 Apr 2014 13:44:06 -0700 (PDT)
In-Reply-To: <1397607559.92815.YahooMailNeo@web120004.mail.ne1.yahoo.com>
References: <534D4F7A.3040605@cox.net> <CAH7SZV9WeQmuaHvUZ35_ySL4ak4+SDfbmpMbXgqQL+C833sTGw@mail.gmail.com> <1397607559.92815.YahooMailNeo@web120004.mail.ne1.yahoo.com>
Date: Wed, 16 Apr 2014 17:44:06 -0300
Message-ID: <CAP+sJUfx6=-22+A_=M_v3iSf6piGeyHkF2_BPm2ntbWnCEhTSw@mail.gmail.com>
From: Ines Robles <mariainesrobles@googlemail.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Content-Type: multipart/alternative; boundary=047d7bd6c21a4b5abc04f72efa53
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/ksYUthIfORhe-F9SwtxHrBHPUeA
Cc: "6tisch@ietf.org" <6tisch@ietf.org>, roll <roll@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: Wed, 16 Apr 2014 20:44:14 -0000

+1

Ines

2014-04-15 21:19 GMT-03:00 Qin Wang <qinwang6top@yahoo.com>om>:

> +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>et>:
>
>  +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
>
>