Re: [6tsch] What is missing slides -- input needed

[Kris Pister <[e-mail]>]

Xavi -
  regarding the existing industrial implementations of TSCH, I'd say 
things a little differently.
1) they are based on TSCH, but not IEEE 802.15.4e TSCH.  4e did not 
adopt either WiHART or ISA100, rather we/it came up with its own way of 
doing things.
2) I don't think that even the IETF gets to say that either of these 
protocols is semi-proprietary anymore.  they are both IEC standards, and 
they are interoperable across many vendors (of the wireless part).
3) all of the blocks are defined, and there aren't any missing.
These are complete standards-based solutions, they just aren't based 
(completely) on IETF/IEEE standards.

ksjp

On 7/15/2013 4:03 PM, Xavier Vilajosana Guillen wrote:
> Dear all,
>
> I am working on what is missing? presentation slides. I want to go 
> deep on the description of the following points. From what we listed 
> last webex I developed the content but I need further input. Please 
> update the following points with your thoughts: (all ideas are 
> welcome, I will filter later!)
>
>
> Deterministic wireless over TSCH is demonstrated and available but 
> semi-proprietary (TSMP, ISA100.11a, WiHART)
>    - Vendors have semi proprietary solutions as there are some blocks 
> missing:
>        -These blocks are mainly on the upper Data Link Layer and its 
> integration with the network layer.
>        -These blocks are mainly for the management and operation of 
> the network
>        -missing blocks limit interoperability and mass scale adoption 
> of the technology
>        -...
> (give me some feedback here please)
>
>
> Same for RPL/TSCH with scalability to *1000s
>    -Vendor specific RPL proved to scale to 1000s (need info about that 
> please!)
>    -TSCH networks proved to scale to 1000s
>    -Missing junction between both. RPL on TSCH.
>    -....
>
> (give me some feedback here please)
>
> Most IETF components exist (ZigbeeIP)
>     - ZigBee IP Supports 6LoWPAN for header compression, IPv6, PANA 
> for authentication, RPL for routing, and TLS and EAP-TLS for security, 
> TCP and UDP transport protocols.
>      -the building blocks exist but need to be fit to TSCH nature. 
> Slotted and deterministic MAC layer, mapping of RPL routes to TSCH 
> schedules (that globally build tracks.) -- Coexistence of Tracks and 
> routes.
>
> (give me some feedback here please)
>
>
> Missing IETF architecture to put it all together
>    - Pascal Picture from architecture draft.
>    - Coexistence==Support of PCE/ Distributed in same architecture
>
> (give me some feedback here please)
>
> Thanks!
> Xavi
>
>
> _______________________________________________
> 6tsch mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/6tsch