Re: [6tisch] Time to Live - ASN in a packet

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Thu, 25 August 2016 11:45 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3F7412D807 for <6tisch@ietfa.amsl.com>; Thu, 25 Aug 2016 04:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.068
X-Spam-Level:
X-Spam-Status: No, score=-15.068 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 zH6Md6zYBZs9 for <6tisch@ietfa.amsl.com>; Thu, 25 Aug 2016 04:44:58 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B22A012D5E7 for <6tisch@ietf.org>; Thu, 25 Aug 2016 04:44:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=67452; q=dns/txt; s=iport; t=1472125497; x=1473335097; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=7jrKTLraGSEoZn87wZzQ7XDypeXM+C4b3xRTaU88f24=; b=eqlzjtfj11nIRiJukQPjfG8O6ZiqnZH+fqssz+qhhGNYN4lyWPR0MVDU MGjkolQEtEybTVl1HjxhL3xqv7sPa2akauIKhLtq+zBsNhWQthsX/+rBM /viHoY7yILQ9Stgae2lSVMyvwaDLTScs1tTJaWLLPF0bbxHnFB/3obx5V 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AcAgBk2b5X/5hdJa1dgnYzAQEBAQEeVnwHuBaBfCaFLUoCHIE4OBQCAQEBAQEBAV4nhGEBAQUBARgJChwfBgsQAgEIBwoDAQEBIQEGAwICAiULFAkIAgQBDQUIDAYBiBcOsQ6PaAEBAQEBAQEBAQEBAQEBAQEBAQEBARyGLoRNhBILAwMBGCQWCIIMOIJaBYZhgUuLV4VHAYU1aoh/gXSEXYkHhU+BG4Fmg3GDeAEeNoN9cAGEUwENFweBAn8BAQE
X-IronPort-AV: E=Sophos;i="5.28,575,1464652800"; d="scan'208,217";a="144390511"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Aug 2016 11:44:55 +0000
Received: from XCH-ALN-007.cisco.com (xch-aln-007.cisco.com [173.36.7.17]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u7PBitJW005175 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 25 Aug 2016 11:44:55 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-ALN-007.cisco.com (173.36.7.17) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 25 Aug 2016 06:44:54 -0500
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1210.000; Thu, 25 Aug 2016 06:44:54 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Thomas Watteyne <thomas.watteyne@inria.fr>, "Shwetha Bhandari (shwethab)" <shwethab@cisco.com>
Thread-Topic: [6tisch] Time to Live - ASN in a packet
Thread-Index: AQHR/pW6BnJKeA2FsE6040VpHft3XKBZiisA///AqxCAAHzUAIAABJSAgAAQlID//6+7EA==
Date: Thu, 25 Aug 2016 11:44:43 +0000
Deferred-Delivery: Thu, 25 Aug 2016 11:44:15 +0000
Message-ID: <623ebceb059a4c78868f762b9cb59918@XCH-RCD-001.cisco.com>
References: <831143327.491.1472104637789.JavaMail.open-xchange@webmail.cdac.in> <CADJ9OA8JFyfNy-w==eS6NyJrQFt-jU+6B_EW=Q4rXHu-4o9mzQ@mail.gmail.com> <43558bc9ae794dc388b38fb4338fa92b@XCH-RCD-001.cisco.com> <1723708107.31.1472119658999.JavaMail.open-xchange@webmail.cdac.in> <D3E4C3BE.39EDAA%shwethab@cisco.com> <CADJ9OA-ic9mfOjGHw5g1GxEdiGw9pzqJtXgSLE0dF3s363Tpvw@mail.gmail.com>
In-Reply-To: <CADJ9OA-ic9mfOjGHw5g1GxEdiGw9pzqJtXgSLE0dF3s363Tpvw@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.228.216.10]
Content-Type: multipart/alternative; boundary="_000_623ebceb059a4c78868f762b9cb59918XCHRCD001ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/ohiOok2mvfaP3gf1WKZr5Xtq4vU>
Cc: Lijo Thomas <lijo@cdac.in>, "6tisch@ietf.org" <6tisch@ietf.org>, "Frank Brockners (fbrockne)" <fbrockne@cisco.com>
Subject: Re: [6tisch] Time to Live - ASN in a packet
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2016 11:45:01 -0000

Exactly!

Keeping in mind that this is an open hand as opposed to “prove yourself and come back (expecting not)”.

One path is: define the HbH header option you rneed, see how you can converge with what Shwetha is showing us (which I was refering to), pick a code that extends 6LoRH https://tools.ietf.org/html/draft-ietf-roll-routing-dispatch-00#section-9.2, work out the compressed form, and go for it with your experimentation…

… and please keep this group in the loop. A personal submissions will not do harm!

Pascal

From: Thomas Watteyne [mailto:thomas.watteyne@inria.fr]
Sent: jeudi 25 août 2016 13:23
To: Shwetha Bhandari (shwethab) <shwethab@cisco.com>
Cc: Lijo Thomas <lijo@cdac.in>; Pascal Thubert (pthubert) <pthubert@cisco.com>; 6tisch@ietf.org; Frank Brockners (fbrockne) <fbrockne@cisco.com>
Subject: Re: [6tisch] Time to Live - ASN in a packet

Lijo,
That's great, indeed. My naive response is that, if you find out that there is real value in doing this, we will find a way to fit that information somwhere.
Looks like Shwetha's pointers go in that direction. Some HbH header seems suitable, we just have to find a mechanism for matching that those TSCH ASN.
My recommendation would be to measure/prove the value first, and embark in standardization after.
Thomas

On Thu, Aug 25, 2016 at 12:24 PM, Shwetha Bhandari (shwethab) <shwethab@cisco.com<mailto:shwethab@cisco.com>> wrote:
Hi Lijo,

We are trying something similar with In-band OAM – defining HbH options to collect timestamps, node, interface information as the packet traverses the nodes. Please take a look at the following:
https://tools.ietf.org/html/draft-brockners-inband-oam-data-01#section-3.1<https://tools.ietf.org/html/draft-brockners-inband-oam-data-01>
https://tools.ietf.org/html/draft-brockners-inband-oam-transport-01#section-3.1

Thanks,
Shwetha

From: 6tisch <6tisch-bounces@ietf.org<mailto:6tisch-bounces@ietf.org>> on behalf of Lijo Thomas <lijo@cdac.in<mailto:lijo@cdac.in>>
Reply-To: Lijo Thomas <lijo@cdac.in<mailto:lijo@cdac.in>>
Date: Thursday, August 25, 2016 at 3:37 PM
To: Thomas Watteyne <thomas.watteyne@inria.fr<mailto:thomas.watteyne@inria.fr>>, "Pascal Thubert (pthubert)" <pthubert@cisco.com<mailto:pthubert@cisco.com>>
Cc: "6tisch@ietf.org<mailto:6tisch@ietf.org>" <6tisch@ietf.org<mailto:6tisch@ietf.org>>

Subject: Re: [6tisch] Time to Live - ASN in a packet


Hi Pascal & Thomas,

The problem is inline with Pascal's comment on "looking for per packet information to as to monitor and maybe influence the forwarding and delivery"

We are proposing a debt based distributed scheduling scheme where nodes make forwarding decisions based on the PDR and end-to-end delay requirement
of flows.

We simulated our algorithm using 6tisch simulator and got encouraging results. For this, we plugged in ASN value in the application payload and the intermediate node updates the ASN value before forwarding.

Now we are implementing the algorithm on the hardware using OpenWSN environment and intend to do inline with the standard.

We are actually contemplating on HbH at L3, similar to RPL RPI as described in RFC 6553

But we would like to understand that if any options is available in the 6tisch framework.
Expecting your valuable comments..!!!!!!!!!!

Thanks & Regards
Lijo Thomas



On August 25, 2016 at 1:39 PM "Pascal Thubert (pthubert)" <pthubert@cisco.com<mailto:pthubert@cisco.com>> wrote:
Hello Lijo:

Like Thomas, I’d love to understand what your case and solution approach is. Is asynchronous OAM like the openWSN application enough for you? Or else are you looking for per packet information to as to monitor and maybe influence the forwarding and delivery?

In the latter case, your work may be related to other efforts, and if your experimentation is successful then why not consider a more general applicability?

All in all I have this feeling that time-aware forwarding is on the way, in which exact shape and form is left TBD:

-        DetNet is discussing validating the end-to-end latency of individual packets to make sure that the delivery was within bounds. Is that similar to your need?

-        I’ve participated to work where the QoS of the packet was estimated at each hop depending on whether the packet was early or late vs. a predefined schedule. This makes things much simpler but slightly less deterministic than a tight scheduling.

-        There’s also OAM work that uses HbH headers to monitor the packets as they flow along the network (IOW, in band as opposed to asynchronous OAM packets)

My understanding is that you want HbH behavior.

-        If you are doing a mesh, you can probable hack a mesh header.

-        But if you are considering a larger applicability (I hope so!) then you probably want to hack at L3.

You can find tons of ideas of what can be done at L3 in various environments in https://tools.ietf.org/html/draft-dt-detnet-dp-alt-03, which is pending adoption call.

But if you narrow down to 6TiSCH, then you probably want to design you own option in the HbH header and incode it in a 6LoRH similar to the RPL RPI. You may use ASN to start with, but when going standard you’ll have to abstract that a little bit, even if the data in the packet is unchanged.

Very keen to hear more!

Pascal

From: 6tisch [mailto:6tisch-bounces@ietf.org] On Behalf Of Thomas Watteyne
Sent: jeudi 25 août 2016 08:28
To: Lijo Thomas <lijo@cdac.in<mailto:lijo@cdac.in>>
Cc: 6tisch@ietf.org<mailto:6tisch@ietf.org>
Subject: Re: [6tisch] Time to Live - ASN in a packet

Lijo,

It looks like you are describing two things: the TTL (or hop limit in IPv6 parlance) which decrements by one by each router, and some timestamp which can be used to measure end -to-end latency. I'm assuming the latter.

I'm also assuming you are doing this as part of an experiment, to look at the end-to-end/hop-by-hop latency. In that context, you probably aren't looking for standardizing that (or even standards-compliance during your experiment), but more at an implementation technique to keep that information.

Of course, the answer depends entirely on the information we are missing. But assuming you are playing with the OpenWSN implementation, there is already an application called rrt which sends the ASN as application payload at the source, and records the ASN when the DAGroot has received that. You can then substract one by the other and do some stats. Please ask further questions to the OpenWSN community [1] as such technical discussion on a particular implementation doesn't belong on the 6TiSCH WG ML.

If you are using the commercial SmartMesh IP solution by Linear Tech [2], good news, all of that is already built in. The manager (~DAGroot) keeps track of timing and can send you average latencies for each of your nodes. If you're interested, you can look at these numbers "live" on deployments in Argentina [3,4] or California [5]. As you might imagine, latency/throughput/lifetime trade-off for one another, so there is a handy "performance estimator" tool you can use [6,7]. For further question on this topic, please use www.dustcloud.org<http://www.dustcloud.org>.

Finally, looking at lowering latency in 6TiSCH has been an important research topic in the last year or so. Look for example at the "Low-Latency Scheduling Function" [8] work which lowers the per-hop latency to 10's of ms withing the 6TiSCH framework.

Thomas

[1] www.openwsn.org<http://www.openwsn.org>
[2] www.linear.com/dust<http://www.linear.com/dust>
[3] http://www.savethepeaches.com/
[4] PEACH: Predicting Frost Events in Peach Orchards Using IoT Technology. Thomas Watteyne, Ana Laura Diedrichs, Keoma Brun-Laguna, Javier Emilio Chaar, Diego Dujovne, Juan Carlos Taffernaberry, Gustavo Mercado. EAI Endorsed Transactions on the Internet of Things, to appear in 2016.
[5] http://www.snowhow.io/
[6] http://www.linear.com/docs/42452
[7] Industrial IEEE802.15.4e Networks: Performance and Trade-offs. Thomas Watteyne, Joy Weiss, Lance Doherty, Jonathan Simon. IEEE International Conference on Communications (IEEE ICC), Internet of Things Symposium, London, UK, 8-12 June 2015.
[8] LLSF: Low Latency Scheduling Function for 6TiSCH Networks. Tengfei Chang, Thomas Watteyne, Qin Wang, Xavier Vilajosana. IEEE International Conference on Distributed Computing in Sensor Systems (DCOSS), Washington, DC, USA, 26-28 May 2016.

On Thu, Aug 25, 2016 at 7:57 AM, Lijo Thomas <lijo@cdac.in<mailto:lijo@cdac.in>> wrote:
Hi all,

We are working on problem which needs the Time to Live (TTL) information in terms of ASN  to be included as part of the Packet.

We require the intermediate nodes to update TTL at each hop.

How this information can be passed in a 6tisch framework.

Suggestions are welcome..

Thanks & Regards
Lijo Thomas



-------------------------------------------------------------------------------------------------------------------------------
[ C-DAC is on Social-Media too. Kindly follow us at:
Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]

This e-mail is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies and the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
is strictly prohibited and appropriate legal action will be taken.
-------------------------------------------------------------------------------------------------------------------------------

_______________________________________________
6tisch mailing list
6tisch@ietf.org<mailto:6tisch@ietf.org>
https://www.ietf.org/mailman/listinfo/6tisch


--
_______________________________________

Thomas Watteyne, PhD
Research Scientist & Innovator, Inria
Sr Networking Design Eng, Linear Tech
Founder & co-lead, UC Berkeley OpenWSN
Co-chair, IETF 6TiSCH

www.thomaswatteyne.com<http://www.thomaswatteyne.com>
_______________________________________



-------------------------------------------------------------------------------------------------------------------------------
[ C-DAC is on Social-Media too. Kindly follow us at:
Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]

This e-mail is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies and the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
is strictly prohibited and appropriate legal action will be taken.
-------------------------------------------------------------------------------------------------------------------------------



--
_______________________________________

Thomas Watteyne, PhD
Research Scientist & Innovator, Inria
Sr Networking Design Eng, Linear Tech
Founder & co-lead, UC Berkeley OpenWSN
Co-chair, IETF 6TiSCH

www.thomaswatteyne.com<http://www.thomaswatteyne.com>
_______________________________________