Subject: Re: [6tsch] doodle poall for a call

From: "Wei.Min" <[email-masked]>
Date: Tue, 05 Feb 2013 10:36:08 +0800

Dear Pacscal,
 
I would like to be volunteer to participate in both 1 and 2.
I agree that some on-line meetings should be arranged before the Orlando meeting.
 Best regards Wei [email-masked] or [email-masked]
Automation College
Key Laboratory of Industrial Internet of Things & Networked Control, Ministry of Education
Chongqing University of Posts and Telecommunications (CQUPT)2 Chongwen Road, Chongqing, China  

---------- Origin message ----------
>From："Pascal Thubert (pthubert)" <[email-masked]>
>To："[email-masked]" <[email-masked]>
>Subject：[6tsch] doodle poall for a call
>Date：2013-02-05 01:24:31

Hi :

In order to prepare for Orlando, it would be good that we have an open call and discuss goals. Ideally that would help us figure a content for a Bar Bof. Short term, we probably need to clarify:

1) what TSCH is. A draft (a few pages) would be useful to explain where is plays, and where it could play in the future. What's so specific and why it's so important that we work on it. This would ultimately be a reference to support a WG creation. This doc must be very clear on what the real problem is. The way I read it the root problem is the TS aspect, while the CH can be probably be hidden in a sublayer, which we need to specify and provide interface with for routing and forwarding. And we have goals of 1) enabling deterministic flows, 2) maintaining budgets of jitter and latency 3) optimizing energy consumption.

Volunteers?

2) A scope for the work items. That's a (set of) 802.15.4e TSCH LLNs and a probably backbone to scale the cases like industrial - we can point to / reuse the problem and applicability statements from ROLL as a source of information -. In turn, a bar bof in Orlando would help us figure the real deliverables. We already got a lot of feedback from the list. So far I've seen that we want:

a) an architecture that shows how the existing standards work together. Includes the likes of PANA, RPL (OF), 6LoWPAN, FoRCES...
Various flows must be described if they need different handlings. The architecture will show missing pieces and overlaps. I think we want to start discussing those in our first round so that we can solve them later.
b) a link model. Probably split in generic (IPv6 abstraction) and specific (4e implementation).
Probably the link local protocols (often mcast, eg NA or DIA) will use a shared slot and traffic will use dedicated slot but routing does not need to know.
c) a sublayer specification to implement that model, including IE level exchange information and IP based interface to negotiate bandwidth from fwd plane. This could be handled as a simple congestion feedback from fwd plane. Or a knowledge of throughput like in slot/s as was mentioned on the list but I do not see that L3 really needs that visibility.
d) a RPL OF that leverages that sublayer. RPL base should be transparent. But the OF handles the peerings and the metrics so it will definitely know.

Who's coming?

Also (later?):
e) a reservation protocol to optimize a sequence of hops from/to the root. Optimizing relays implies a common sense of time along the path so that what comes in goes out rapidly.
f) an openflow type of approach if the central computer needs to control both the path and the channel/slot sequence.
g) filling the gaps, like fragment handling, DAD across a backbone, ...

I created a doodle to get your availability. From there, I'll schedule a weekly call and we'll see if that is an efficient tool or not...

Please go to
http://doodle.com/9vq5qmxzdg6w63t7

Cheers,

Pascal

Pascal Thubert
IPv6 Engineering

[email-masked]<mailto:[email-masked]>
Phone :+33 497 23 26 34
Mobile :+33 619 98 29 85

Cisco Systems
Village d'Entreprises Green Side bat. T3
400, Avenue Roumanille
06410 Biot - Sophia Antipolis
France
Cisco.com<http://www.cisco.com/global/FR/>

[Description: http://www.cisco.com/web/europe/images/email/signature/vertical04.jpg]

For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/index.html
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message.