Dear all : ChongGang pointed out that the charter text for item 3 (OTF) was not specific that we address L2 peer operation, not and end to end reservation ala RSVP.
I modified item 3 again as follwos: 3. Produce an "On-the-fly" (OTF) specification to enable a distributed dynamic scheduling of time slots, negotiated between adjacent peers, with the capability for IoT routers to appropriate chunks of the Time/frequency matrix without starving, or interfering with, other 6TiSCH nodes. This particular work will focus on IP traffic since the work on tracks is not yet advanced enough to specify their requirements for OTF operations. What do you think? Pascal
_______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
